[asterisk-bugs] [Asterisk 0013309]: [patch] chan_sip does not always create regexten for registering peers

[Asterisk Bug Tracker]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=13309 
====================================================================== 
Reported By:                dimas
Assigned To:                svnbot
====================================================================== 
Project:                    Asterisk
Issue ID:                   13309
Category:                   Channels/chan_sip/Registration
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.4.21.2 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2008-08-15 10:04 CDT
Last Modified:              2008-10-14 18:00 CDT
====================================================================== 
Summary:                    [patch] chan_sip does not always create regexten for
registering peers
Description: 
parse_register_contact contact function only calls register_peer_exten in
the case peer's IP/port changes. This is wrong because peer regexten may
not be re-created under some circumstances. Scenario

1. Realtime SIP peers database
2. Peer registers with Asterisk.
3. ipaddr and port columns in the database receive peer's real ip+port
4. regexten is created for the peer
5. Asterisk resterted
6. Peer re-registers.
7. This time, peer's data (including ipaddr+port) loaded from the DB
8. Assuming that address and port are the same, Asterisk won't create
regexten (because of if (inaddrcmp(&peer->addr, &oldsin)) check in the
parse_register_contact)
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-10-14 18:00 svnbot         Status                   new => resolved     
2008-10-14 18:00 svnbot         Resolution               open => fixed       
2008-10-14 18:00 svnbot         Assigned To               => svnbot          
======================================================================