Hi.

Thanks for the response. So far we have done: nothing really! It's an 
installation in the US, some 6000 miles and 9 hours time difference from where 
I'm at, and we usually don't participate in the ILS installations - normally, 
our devices use SIP protocol and there's not much else for us to do. I'm just 
looking into this now because there is a slight case of "your hardware doesn't 
work" and I would like to at least attempt to figure it out *before* flying 
there ;-)

I did receive a part of a log file, which looks like this:


osrfsys.16.log:2013-06-20 16:52:08 192.168.80.55 SIPServer.pm: [ERR 
:12423:EX.pm:66:] Exception: OpenSRF::EX::ERROR 2013-06-20T16:52:08 
OpenSRF::AppRequest /usr/local/share/perl/5.10.1/OpenSRF/AppSession.pm:1064 
System ERROR: Exception: OpenSRF::DomainObject::oilsMethodException 
2013-06-20T16:52:08 OpenSRF::AppRequest 
/usr/local/share/perl/5.10.1/OpenSRF/AppSession.pm:1064 <500> *** Call to 
[open-ils.circ.checkin] failed for session [1371761527.01478448.158959383084], 
thread trace [1]:
osrfsys.16.log:2013-06-20 16:52:08 192.168.80.55 SIPServer.pm: [ERR 
:12423:EX.pm:66:] Exception: OpenSRF::EX::ERROR 2013-06-20T16:52:08 
OpenILS::Application::AppUtils /usr/local/share/perl/5.10.1/O
penILS/Application/AppUtils.pm:186 System ERROR: Call to open-ils.circ for 
method open-ils.circ.checkin
osrfsys.16.log:2013-06-20 16:52:08 192.168.80.55 SIPServer.pm: 
[INFO:12423:ScriptRunner.pm:14:] script_runner: destroying self: 
OpenILS::Utils::ScriptRunner=HASH(0x5346410)


I don't have much clue as to what I'm looking at there. I think it is saying 
that a call to a check in method (open-ils.circ.checkin) failed, but to me it 
doesn't seem to say why...?

I'll try to get more information, and also ask them to check the 
/var/log/syslog as per Jason Stephenson's advice.



With best regards,

Antti Kurenniemi
P.V. Supa Oy
[email protected]
+358 50 386 9899

-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of Kivilahti 
Olli-Antti
Sent: 20. kesäkuuta 2013 13:36
To: [email protected]
Subject: Re: [OPEN-ILS-DEV] Assistance request with a SIP connection problem

Hello Mr. Kurenniemi.

I think we could help you better if you described in more detail what you have 
tried so far.
How are you testing the connection?
Do you have a development Evergreen installation, where you can prod away 
freely?
If not, then it might be best to work together with the system administrators 
of your client.

I can assure you learning Evergreen is not the easiest of things. I cannot give 
you an estimate about SIP modifications, but our experience of a learning curve 
is atleast 1 month (>120h) before you start to be able to do some 
modifications. Presuming your focus is on the SIP aspect, things might be 
easier (~60h) as it is kind of a separate module and presumably you have a 
strong background with SIP and linux, and know a little Perl.
All my time estimates are WAG's and will vary!
Try googling "open-ils sip" and you get some nice results, such as:
http://www.open-ils.org/dokuwiki/doku.php?id=evergreen-admin:sip
but dokuwikis can easily be outdated.

If you don't feel like linux servers is your piece of cake, you could try 
contracting someone on this very list.

We here in Joensuu are yet to take a peek at Evergreen's SIP2 implementation, 
but are looking forward to cooperating with you.

Olli-Antti Kivilahti
Open Library 2014
Joensuu Regional Library

Date: Thu, 20 Jun 2013 06:19:43 +0000
From: Antti Kurenniemi <[email protected]>
Subject: [OPEN-ILS-DEV] Assistance request with a SIP connection
        problem
To: "[email protected]"
        <[email protected]>
Message-ID:
        
<bb75624fd9b645fb9ddb87f89efe9...@db3pr01mb091.eurprd01.prod.exchangelabs.com>

Content-Type: text/plain; charset="us-ascii"

Hello all.


My name is Antti Kurenniemi, I work for P.V. Supa Oy Ltd 
(www.pv-supa.com<http://www.pv-supa.com>), a library automation company. We 
make self-service stations and sorters and the likes, and also the software to 
those. We are based in Finland (as am I), and have delivered sorters to the US 
for over a decade already.

For about a year now, we have seen our customers using Evergreen as their ILS. 
For the most part we have not had any problems, but right now we have one 
sorter installation in the US with a fairly annoying issue.

Our devices communicate with ILS's via SIP protocol (SIP 1 or 2, typically 2), 
normally over a TCP/IP connection. In this particular case, the SIP connection 
is broken quite often, about once or twice an hour. The network connection 
stays live, but the SIP connection just closes. It comes up automatically after 
a few minutes and our device can then continue normal operations, but obviously 
if a patron is using the machine when the connection breaks, they can't return 
their books.

I have between zero and zilch experience with Evergreen server, so I'm looking 
for help and advice as to where to start looking. We have logs in our device 
with timestamps, so if there is logging in the Evergreen server that we could 
compare these to, that would be a good place to start, right? Now if only I 
knew how to get to any logs... ;-)

So, any help and tips would be greatly appreciated.


With best regards,

Antti Kurenniemi
P.V. Supa Oy Ltd
[email protected]<mailto:[email protected]>

Reply via email to