[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:                jamesgolovich
====================================================================== 
Project:                    Asterisk
Issue ID:                   11930
Category:                   Channels/chan_sip/Registration
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
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 02:31 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)


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

---------------------------------------------------------------------- 
 pj - 02-11-08 02:31  
---------------------------------------------------------------------- 
sorry for mistake, I mix two things together, so forget...
it seems, that only way to improve behaviour is from asterisk as client
side, it can try to start reregistering (eg. reset registry timer) after
asterisk client detect, that tcp session was closed. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
02-11-08 02:31  pj             Note Added: 0081996                          
======================================================================