[asterisk-bugs] [Asterisk 0012763]: chan_sip creates a new local tag (from-tag) for every register message

noreply at bugs.digium.com noreply at bugs.digium.com
Sun Jun 1 14:57:29 CDT 2008


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12763 
====================================================================== 
Reported By:                urtho
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12763
Category:                   Channels/chan_sip/Registration
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             05-30-2008 15:32 CDT
Last Modified:              06-01-2008 14:57 CDT
====================================================================== 
Summary:                    chan_sip creates a new local tag (from-tag) for
every register message
Description: 
refreshing from-tag for each register message - even within the same dialog
is against RFC. 
====================================================================== 

---------------------------------------------------------------------- 
 rjain - 06-01-08 14:57  
---------------------------------------------------------------------- 
That section of RFC 3261 talks about how a UAC should construct a
subsequent request on receiving some particular kinds of 4XX responses. It
does not talk about registration refresh requests. You probably meant to
refer to a scenario where Asterisk receives a 401/407 response to an
outbound REGISTER request and then when it resubmits the REGISTER, it
changes the from-tag in it. 

Technically, it's a SHOULD clause on the UAC so if a UAS/Proxy is not able
to handle from-tag change then the bug is in that entity. However, I agree
that this is something that can be improved upon in Asterisk. This just
doesn't apply to REGISTER method but other methods as well. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-01-08 14:57  rjain          Note Added: 0087615                          
======================================================================




More information about the asterisk-bugs mailing list