[Koha] SIP 2 connection (RAW 6001) only function to 1 machine ONLY

[Alvaro Cornejo]

Hi

Never worked with Koha and SIP, but TCP connections only accept one
permanent connection at a time on the same port. If the port is used, next
connection is refused and times out. This seems your issue.

You should assign a different port for each device 6001, 6002, 6003....

There are other type of apps, like apache that "listens" on one port but
once it receives a connection requests, it opens a "secondary/child
connection" on a different port so main port is always available for
receiving new connections. Koha SIP seems not doing this.

Regards,

Alvaro

|-----------------------------------------------------------------------------------------------------------------|
Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier
celular y Nextel
en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS
y GPRS online
              Visitenos en www.perusms.com


Le lun. 28 janv. 2019 à 03:23, BITE <halim4977 at gmail.com> a écrit :

> Hi There,
> Our koha version 17.11 (ubuntu 14.04) able to connect with SIP2 to one
> machine ONLY.
> FYI, we have 2 machines (Self-check, Book Drop) and a Tagging Workstation
> that needed to be connected concurrently.
> If I activated Selfcheck, Book Drop and tagging workstation will be
> disconnected from SIP2 .
> All 3 above need to be connected from port 6001 (RAW) service.
> How do I do that? Please assist me.
> Thank you.
>
> Regards
> Halim
>
> Our current settings is a s follows :
>  <service
>       port="192.168.14.15:8023/tcp"
>       transport="telnet"
>       protocol="SIP/2.00"
>       timeout="60" />
>
>     <service
>       port="192.168.14.15:6001/tcp"
>       transport="RAW"
>       protocol="SIP/2.00"
>       client_timeout="600"
>       timeout="60" />
> <!--- client_timeout times out active connections which have not received
>      input from the client. Many persistent connections will send a status
> request
>      every 5-7 mins so setting this to less than that will add instability
> to the connection
>      if explicitly set to zero, no timeout is applied to the connection.
>      NB the parameter timeout applies to the login process only and should
> be set to a lower value
>      to time out failed connections
> -->
>   </listeners>
>
>   <accounts>
>       <login id="term1"  password="1234567890" delimiter="|"
> error-detect="enabled" institution="Main Library" encoding="ascii"
> checked_in_ok="1" />
>       <login id="koha"   password="koha"  delimiter="|"
> error-detect="enabled" institution="kohalibrary" encoding="utf8" />
>       <login id="koha2"  password="koha" institution="kohalibrary2"
> terminator="CR" />
>       <login id="lpl-sc" password="1234" institution="LPL" />
>       <login id="lpl-sc-beacock" password="xyzzy"
>              delimiter="|" error-detect="enabled" institution="LPL"
>              send_patron_home_library_in_af="1"
>              av_field_template="[% accountline.description %] [%
> accountline.amountoutstanding | format('%.2f') %]" >
>           <screen_msg_regex find="Greetings from Koha." replace="Welcome to
> your library!" />
>           <screen_msg_regex find="Invalid patron barcode." replace="Barcode
> not found, are you sure this is your library card?" />
>       </login>
>   </accounts>
>
> <!--
> Institution tags are for enabled branches.  There needs to be one
> institution stanza for each institution named in the accounts above.
> The implementation attribute is actually used to find the code to run,
> in our case "ILS".
> -->
>
> <institutions>
>     <institution id="Main Library" implementation="ILS" parms="">
>           <policy checkin="true" renewal="true" checkout="true"
>             status_update="false" offline="false"
>           timeout="100"
>             retries="5" />
>     </institution>
> _______________________________________________
> Koha mailing list  http://koha-community.org
> Koha at lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>