[asterisk-bugs] [Asterisk 0011930]: sip reload should not unregister tcp/tls peers

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11930 
====================================================================== 
Reported By:                pj
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   11930
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):  trunk 
SVN Revision (number only!): 102037 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             02-05-2008 14:35 CST
Last Modified:              02-11-2008 01:25 CST
====================================================================== 
Summary:                    sip reload should not unregister tcp/tls peers
Description: 
after reloading sip configuration, peers that using tcp or tls transport
are unregistered (even in case, when sip.conf isn't changed). 
peers are registered back when registry timeout expires. I think:
1) should not be unregistered when reloading sip.conf
2) when tcp session is closed (eg. stop/start asterisk server), tcp
clients should attempt to reregister immediatelly (not wait until
registration expires)


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

---------------------------------------------------------------------- 
 jamesgolovich - 02-11-08 01:25  
---------------------------------------------------------------------- 
I reviewed the SIP RFC to see if it said anything about it, looked at what
we do with UDP, and looked how other clients handled it and I've come to
the conclusion that we shouldn't really change anything.  In order to not
overwhelm a server we should wait for the registration to timeout

I'm going to close out this issue, if someone feels the re-registration
needs to be addressed a new bug should be opened on it since it would also
apply to UDP and not just TCP and TLS. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
02-11-08 01:25  jamesgolovich  Note Added: 0081991                          
======================================================================