[asterisk-bugs] [Asterisk 0009314]: Improper response on receiving duplicated packets

[noreply at bugs.digium.com]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=9314 
====================================================================== 
Reported By:                Dan_Lukes
Assigned To:                oej
====================================================================== 
Project:                    Asterisk
Issue ID:                   9314
Category:                   Channels/chan_sip/Registration
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
Asterisk Version:            1.2.13 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        No 
Request Review:              
Resolution:                 suspended
Fixed in Version:           
====================================================================== 
Date Submitted:             03-18-2007 17:23 CDT
Last Modified:              10-30-2007 10:17 CDT
====================================================================== 
Summary:                    Improper response on receiving duplicated packets
Description: 
SIP protocol handler improperly handle the REGISTER message that has been
duplicated in transmit.
The "Additional Information" section contain the dump od debug messages. I
attached the timestamps related to each packet (obtained from tcpdump). 

The Asterisk sends REGISTER. Server responds "401 Unauthorized".
Unfortunately, this packet arrived three times (it has been replicated
somewhere on the network).
In my humble opinion, Asterisk shall respond to the first then ignore
replicants (resending the same response as in the first case).
Unfortunatelly, it doesn't. It respond to every of them using separate
response (different CSeq). In advance, it can't handle three "OK" that
arrive later claiming he got OK/REGISTER to nonregister request which is
not true (the reauest has been REGISTER request).

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

---------------------------------------------------------------------- 
 file - 10-30-07 10:17  
---------------------------------------------------------------------- 
I'm suspending this since it's a 1.2 bug, plus as oej mentioned while it
isn't elegant... it doesn't cause any issues and will hopefully be fixed in
newer versions. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-30-07 10:17  file           Status                   assigned => resolved
10-30-07 10:17  file           Resolution               open => suspended   
10-30-07 10:17  file           Note Added: 0072738                          
======================================================================