[OPEN-ILS-DEV] SIP Server testing

[Joe Atzberger]

If he can get in via telnet and test, then his machines should be able to
also.  The trick if you are targetting the actual "telnet" port (8023) is
tuning the expect scripts than handle the initial login prompts.  More
modern implementations tend to target the "raw" port (6001).  You said you
used telnet clients, but which port were you targeting?

Also, it looks like #021#015 would be (octal for) XON then CR.  See if he
can skip the XON part of the handshaking.  I'm not sure how that ends up
becoming "q" though.

Hopefully you can find a terminal configuration that works.  Otherwise we
probably revisit the issue of line-endings and whitespace handling that is a
perennial SIP topic.

--Joe

On Thu, Sep 2, 2010 at 3:12 PM, Soulliere, Robert <
robert.soulliere at mohawkcollege.ca> wrote:

> Hi Everyone,
>
> We were able to connect to our SIP server and run the tests successfully
> from the localhost and another machine on our network. I was able to run the
> command to pull in patron data using the telnet test.
>
> However, our 3M rep was unable to connect from the self-check station from
> offsite.
>
> The  logs on his end are as follows:
>
> 09/02/10 14:35:21 - 1 SIP 39 33 30 30 43 4E 53 49 50 55 73 65 72 31 7C 43
> 4F 53 49 50 55 73 65 72 31 7C 43 50 46 45 4E 4E 45 4C 4C 7C 0D
> 09/02/10 14:35:51 - 1 SIP SIP: Passing Timeout message to SIP thread.
> 09/02/10 14:35:51 - 1 SIP SIP: Calling com_send to pass a SIP message to
> the COM thread.
>
> The error messages in our SIP log on the server are:
>
> Sep  2 13:36:08 libdog opensrf_sip[26158]: read_SIP_packet, INPUT MSG:
> '#021#015'
> Sep  2 13:36:10 libdog opensrf_sip[26158]: read_SIP_packet, INPUT MSG:
> 'q#015'
> Sep  2 13:36:10 libdog opensrf_sip[26158]: read_SIP_packet, INPUT MSG: 'q'
> Sep  2 13:36:10 libdog opensrf_sip[26158]: read_SIP_packet, trimmed 1
> character(s) (after chomps).
> Sep  2 13:36:10 libdog opensrf_sip[26158]: INPUT MSG: 'q'
> Sep  2 13:36:10 libdog opensrf_sip[26158]:
> Sip::MsgType::new('Sip::MsgType', 'q', 'q'): msgtag '0'
> Sep  2 13:36:10 libdog opensrf_sip[26158]: new Sip::MsgType: Skipping
> message of unknown type 'q' in 'q'
>
>
> The 3M contact was able to connect via the telnet test successfully from
> offsite. Anything in the logs that jump out at anyone or are there any thing
> about the self check station itself that could be an issue?
>
> Thanks,
> Robert
> ________________________________________
> From: open-ils-dev-bounces at list.georgialibraries.org [
> open-ils-dev-bounces at list.georgialibraries.org] On Behalf Of Soulliere,
> Robert [robert.soulliere at mohawkcollege.ca]
> Sent: September 1, 2010 3:53 PM
> To: atz at esilibrary.com; Evergreen Development Discussion List
> Subject: Re: [OPEN-ILS-DEV] SIP Server testing
>
> Thanks Joe!
>
> Updating the Perl module solved the problem.
>
> Regards,
> Robert
>
> From: open-ils-dev-bounces at list.georgialibraries.org [mailto:
> open-ils-dev-bounces at list.georgialibraries.org] On Behalf Of Joe Atzberger
> Sent: Tuesday, August 31, 2010 5:41 PM
> To: Evergreen Development Discussion List
> Subject: Re: [OPEN-ILS-DEV] SIP Server testing
>
> Update your version of Test::More.  More recent versions (from cpan,
> probably) include the "note" subroutine.
>
> --Joe
> On Tue, Aug 31, 2010 at 3:32 PM, Soulliere, Robert <
> robert.soulliere at mohawkcollege.ca<mailto:robert.soulliere at mohawkcollege.ca>>
> wrote:
> Hi all,
>
> I was setting up a SIP server and had an error during the testing phase.
> When I run the status test PERL5LIB=../ perl 01patron_status.t, I get the
> error:
>
> Undefined subroutine &SIPtest::note called at SIPtest.pm line 200.
>
> Is this telling me that I am probably missing some of the prerequisite Perl
> modules? I was able to complete the tests on or test server running
> Evergreen 1.6.1.1 but the same  tests failed on our live server running
> 1.6.0 + booking.
>
> Thanks,
> Robert
>
>
>
> ________________________________
> This E-mail contains privileged and confidential information intended
> only for the individual or entity named in the message. If the reader
> of this message is not the intended recipient, or the agent responsible
> to deliver it to the intended recipient, you are hereby notified that
> any review, dissemination, distribution or copying of this communication
> is prohibited. If this communication was received in error, please
> notify the sender by reply E-mail immediately, and delete and destroy
> the original message.
>
>
> ________________________________
> This E-mail contains privileged and confidential information intended
> only for the individual or entity named in the message. If the reader
> of this message is not the intended recipient, or the agent responsible
> to deliver it to the intended recipient, you are hereby notified that
> any review, dissemination, distribution or copying of this communication
> is prohibited. If this communication was received in error, please
> notify the sender by reply E-mail immediately, and delete and destroy
> the original message.
>
> This E-mail contains privileged and confidential information intended
> only for the individual or entity named in the message.  If the reader
> of this message is not the intended recipient, or the agent responsible
> to deliver it to the intended recipient, you are hereby notified that
> any review, dissemination, distribution or copying of this communication
> is prohibited.  If this communication was received in error, please
> notify the sender by reply E-mail immediately, and delete and destroy
> the original message.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://libmail.georgialibraries.org/pipermail/open-ils-dev/attachments/20100902/09a7b755/attachment-0001.htm