https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25965 --- Comment #33 from Lari Strand <lmstrand@gmail.com> ---
When you say "manage stunnels for all devices", do you mean stunnel for the SIP client (e.g. client software in self-check machine)? Or do you mean stunnel for the Koha SIP server? Or both?
Setting up stunnel for the Koha SIP server should be very simple, but I could see how setting up stunnel for all the SIP clients could be challenging. But then if the self-check provider added support for SIP over HTTPS, then why couldn't they just add support for SIP over TLS? Surely that would've been easier as well.
In any case, it's cool that you've got it all working! I'm just keen to understand is all :)
I haven't worked with the stunnels myself on our systems or even asked one to be set up, but as far as I understand it needs work from both our server's host/provider's support personnel (which is not us) + the municipalities' IT personnel for each library and they have to work together to set up a tunnel. We can only ask them to enable an stunnel to be set up between a self check machine's network and out server host. So it's out of our hands how they manage to set them up and in what time (+upkeep). So naturally we wanted to get rid of all that hassle. I haven't looked at SIP over TLS so I have no experience of that. Does Koha's SIP server support it natively? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.