[asterisk-bugs] [Asterisk 0013602]: [patch] Bad handling of Contact header, which should not be present in 1XX responses to REGISTER, but also in several other case

[Asterisk Bug Tracker]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=13602 
====================================================================== 
Reported By:                hjourdain
Assigned To:                mnicholson
====================================================================== 
Project:                    Asterisk
Issue ID:                   13602
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.4.22 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2008-10-02 07:42 CDT
Last Modified:              2009-02-06 10:20 CST
====================================================================== 
Summary:                    [patch] Bad handling of Contact header, which should
not be present in 1XX responses to REGISTER, but also in several other case
Description: 
When Asterisk sends a response to a UA, the algorithm to include the
Contact header that's use in resprep is flawed.
This leads to sending the contact header in 100 Trying responses to
REGISTER.
But this is also true in many other cases, depending on the type of
response (1xx, 2xx, 3xx 485 or other) and the type of request.
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-02-06 10:20 svnbot         Status                   assigned => resolved
2009-02-06 10:20 svnbot         Resolution               open => fixed       
======================================================================