[Koha-bugs] [Bug 25965] Create SIP2 client daemon with HTTPS API endpoint

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Wed Sep 23 08:23:06 CEST 2020


https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25965

--- Comment #18 from Lari Strand <lmstrand at gmail.com> ---
(In reply to David Cook from comment #17)

> > I think this would be much better suited as an API plugin.
> 
> This sounds reasonable to me as well. 
> 

I've been studying the plugins and indeed it would be fairly painless to build
it into a plugin. I'm not sure if I have the time to do a plugin version, since
my traineeship period is coming to it's end soon. Maybe on my free time.

> I think that Lari has already implemented this locally (in testing) at
> Koha-Suomi in Finland, but I think that they'd probably benefit from doing
> it as an API plugin too. 
> 
> I suggested sharing the work on Bugzilla anyway though in case anyone else
> finds the work interesting. It also gives a chance to get some community
> feedback. 
> 
> Lari, is there a reason the vendor isn't using NCIP? (I admit that I've
> never used it so didn't even think of it. Cheers, Kyle!)

I've never heard of NCIP as well. I was tasked to come up with a solution like
this, based on the Axiell guideline I've posted in the first comment by Koha
Finland so I did. So from what I can figure, there are already numerous sip
device manufacturers that use this method of communication, at least here in
the Nordics.
The point was not to touch the sip server or the way we currently talk with sip
devices, but to introduce and add a new simpler way to pass messages to sip
servers with no need for intermediate tunneling setups or VPN solutions since
we use https (I have no idea how tunneling works, but I know it and VPN both
need extra setup and management and VPN is not free?).
Here every passed message to the sip server/s would also be authenticated on a
message by message basis. One need for this kind of a solution would be in the
library buses with spotty and unreliable internet connections.

I'm not familiar with NCIP or how the security of the communications has been
resolved with NCIP. Couldn't find anything with a quick google. If it makes
tunneling/VPN stuff obsolete, then that's great. Just what we were after.

3M SIP2 protocol is now NISO property? Cool. Maybe it will now get updated to
reflect current needs.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.


More information about the Koha-bugs mailing list