Line-endings have been a longstanding problem because of variations in implementations. But we should still tryto default to the correct thing, according to what standards are available.
Created attachment 2956 [details] [review] Proposed patch
Pushed to new/bug_5586 (not merged to master yet) Please test with a wide range of SIP devices and report your findings here.
Tested on Bluesocket, Userful, Envisionware and Cassie successfully.
Note, this is also the line-ending used by the Evergreen version of the SIP code, so all SIP devices connecting to EG are also compatible w/ the change.
Works ok with the test scripts I've used to diagnose line ending problems in the past. Should work ok both with strictly compliant and CRLF units
You can add 3M to the list of units tested against
Merged to master, please test on master then mark resolved
Patch is causing problems with latest 3M units if connecting over telnet. Looks like unit is not always recognizing the response causing timeouts. Reverting the patch solved problem. Investigating with 3M
(In reply to comment #8) > Patch is causing problems with latest 3M units if connecting over telnet. Looks > like unit is not always recognizing the response causing timeouts. Reverting > the patch solved problem. Investigating with 3M I suspect this is something where they had to configure in non-compliant line-endings (to match what we were doing). If they just connect using "raw" setting and port, is there still a problem? Please identify the models specifically so we can correlate information.
Cause of problem identified. When printing with \n the output buffer is flushed even though you are on a buffered file handle. But \r does not do this for you therefore autoflush needs to be set on stdout
This bug is mentioned in: Bug 5586: Set SIP line-endings to proper SPEC-compliant \r http://lists.koha-community.org/pipermail/koha-patches/2011-January/013538.html
There is a problem with 3M self-checkout systems that we use in France. The problem has been confirmed also by Frederic Demians, and the patch on bug 7619 solve it.