ACS Status response can include incorrect timeout in Multiplex mode
Bug #1927542 reported by
Galen Charlton
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SIPServer |
New
|
Medium
|
Unassigned |
Bug Description
If the Multiplex Net::Server personality is in use, the ACS Status response message (98) can return 000 for both the timeout and the number of retries allowed after the SIP terminal has successfully authenticated to the ILS.
Per the SIP2 specification, reporting a zero timeout in the ACS Status response indicates that the ACS is offline. Some SIP2 clients instead interpret such a response as indicating that there's effectively no time for the ACS to respond before the SIP client should give up on the request. Either way, SIP2 clients that take the ACS Status timeout seriously are left out in the cold by this bug.
To post a comment you must log in.
A patch is available in the working repository:
user/gmcharlt/ lp1927542_ fix_acs_ status_ in_multiplex / https:/ /git.evergreen- ils.org/ ?p=working/ SIPServer. git;a=shortlog; h=refs/ heads/user/ gmcharlt/ lp1927542_ fix_acs_ status_ in_multiplex