[asterisk-bugs] [Asterisk 0010550]: SIP Notify on Snom phones causes Asterisk to stop responding (not crash)

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10550 
====================================================================== 
Reported By:                ramonpeek
Assigned To:                qwell
====================================================================== 
Project:                    Asterisk
Issue ID:                   10550
Category:                   Channels/chan_sip/Interoperability
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.11  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             08-24-2007 05:35 CDT
Last Modified:              10-09-2007 17:27 CDT
====================================================================== 
Summary:                    SIP Notify on Snom phones causes Asterisk to stop
responding (not crash)
Description: 
Due to the revisions 79902-79904 which removes the semi-column in SIP
NOTIFY messages asterisk will stop responding after a Snom phones is
rebooted or check-synced through the SIP-NOTIFY command. 

However Snom phones use the semi-column in their NOTIFY messages to reboot
or load configuration. (they can't do without!)

Please note that the default SIP Notify message defined in sip_notify.conf
still shows an escaped semi-column ;
   [snom-check-cfg]
   Event=>check-sync\;reboot=false
   Content-Length=>0

Not escaping the semi-column does not work, since the phone doesn't
receive teh correct NOTIFY message and this reboots.. instead of just
reloading it's configuration.

Simply reverting the revisions solves the problem..
But is that really the solution?
There must be a good reason for trying to remove that semi-column?

====================================================================== 

---------------------------------------------------------------------- 
 ramonpeek - 10-09-07 17:26  
---------------------------------------------------------------------- 
We wrote the attached patch to revert back to the old functionality.
Offcourse this is a dirty thing, because we ignore all the changes that
most likely have been made by other purposly.
However it gives us the ability to run our asterisk server.

Obviuosly we should handle this correctly.
I hope this small and dirty revert-patch will interest someone to look
abit further.. since I couldn't understand why they made those changes and
also where exactly. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-09-07 17:27  ramonpeek      Note Added: 0071739                          
======================================================================