[asterisk-bugs] [Asterisk 0013599]: [patch] When unregistering a UA, 200 OK response from Asterisk is not SIP compliant

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13599 
====================================================================== 
Reported By:                hjourdain
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13599
Category:                   Channels/chan_sip/Registration
Reproducibility:            sometimes
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.22 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-10-02 01:04 CDT
Last Modified:              2008-10-09 01:03 CDT
====================================================================== 
Summary:                    [patch] When unregistering a UA, 200 OK response
from Asterisk is not SIP compliant
Description: 
When Asterisk is used as a registrar, and a registered UA is sending a
REGISTER with Expires header set to 0, then usually Asterisk will send back
a 200 OK response, containing a Contact header with the contact to be
removed, and an expires parameter that is set to the previous expiration
value!!!
This is not compliant with RFC 3261!
====================================================================== 

---------------------------------------------------------------------- 
 (0093400) hjourdain (reporter) - 2008-10-09 01:03
 http://bugs.digium.com/view.php?id=13599#c93400 
---------------------------------------------------------------------- 
It's section 10.3, item 8, p.66.
It states that the 200 OK must contain contact header field values
enumerating all current bindings.
If there is no binding, there should be none! Or maybe if the binding is
set in the contact, then the expires parameter should be set to 0.
I think most implementations I've seen - including previous versions of
Asterisk - don't send back a contact parameter...

The current behaviour is causing some problems with one of the stacks I
use, since it checks the content of the contact header to see if
de-registration has been complete - a little pedantic maybe, but quite
compliant...

That's why I came up with this patch. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-10-09 01:03 hjourdain      Note Added: 0093400                          
======================================================================