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

noreply at bugs.digium.com noreply at bugs.digium.com
Mon Feb 11 01:51:02 CST 2008


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 01:51 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 01:51  
---------------------------------------------------------------------- 
James, thanks to fixing the first issue, I will test today..
ad second) udp registrations are stored in asterisk databaze 
'database show SIP/Registry'
so, after restarting asterisk server, udp peers are immeadiatelly
qualified as OK, but seems, that tcp/tls peers are not stored here, so this
peers are qualified as unreachable after restart, until all peers
reregisers itself after their registry timeout expires. 
I think it should be changed, because now, I must lower maxexpiry timeout
globally in asterisk, because with default registry expiry timeout (3600s)
will stay tcp/tls peers even one hour unregistered! 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
02-11-08 01:51  pj             Note Added: 0081993                          
======================================================================




More information about the asterisk-bugs mailing list