https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42770 Lari Strand <lmstrand@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lmstrand@gmail.com --- Comment #1 from Lari Strand <lmstrand@gmail.com> --- We've been using this plugin for over 5 years in our production environment in Finland with hundreds of self check machines and door systems (self service libraries): https://github.com/KohaSuomi/koha-plugin-SIPoHTTP It talks with Koha's SIP server on a per-message basis (every message will be authenticated with 93/94) and uses sockets to connect with the SIP server. Lyngsoe Systems, Bibliotheca and Mikroväylä self check system suppliers support this implementation and are all using it here. It has been proven to be very stable. We got rid of the need to have to maintain proxies/tunnels. Unstable internet connection is not a problem anymore with the devices since they don't rely on an always-on connection to Koha's SIP server anymore to be "online". It communicates with the Koha SIP server through a REST API endpoint and supports this unofficial XML schema proposed by Axiell back in the day as a protocol: https://github.com/KohaSuomi/kohasuomi.github.io/blob/master/sipschema.xsd We have already started getting the plugin ready for the integration of the SIP server being controlled from the intranet that was released in version 25.11. I would like to work on this if you think our REST-implementation is the way to go (still relying on the SIP server running in the background). We'd need to add the REST endpoint that parses/passes on messages to SIP2 server + some log4perl/Apache configuration to Koha. Obviously some changes to our plugin code needs to be made, since we have some specific code added just for our needs + we don't have the UI controlled SIP server stuff yet integrated and all SIP account data for authentication is being fetched from the sipconfig.xml file. The link you shared has the SIP messages wrapped in a JSON structure. I'm thinking of how we could support multiple variations of data being passed to the SIPOHTTPS endpoint, since we seem to have multiple data wrapping methods across the world... -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.