[asterisk-bugs] [Asterisk 0018366]: [patch] SIP/TCP phones are not added to astdb - causes sip reload problems

Asterisk Bug Tracker noreply at bugs.digium.com
Wed Mar 16 04:29:19 CDT 2011


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18366 
====================================================================== 
Reported By:                MKemner
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18366
Category:                   Channels/chan_sip/TCP-TLS
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           1.8.1-rc1 
JIRA:                       SWP-2648 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-11-24 05:46 CST
Last Modified:              2011-03-16 04:29 CDT
====================================================================== 
Summary:                    [patch] SIP/TCP phones are not added to astdb -
causes sip reload problems
Description: 
Phones that are registered via TCP are not added to the
/SIP/Registry database.  As a result, these phones "vanish" (become
unregistered) after a sip reload and can not be called by asterisk until
they re-register.

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

---------------------------------------------------------------------- 
 (0132948) -KeX- (reporter) - 2011-03-16 04:29
 https://issues.asterisk.org/view.php?id=18366#c132948 
---------------------------------------------------------------------- 
I've tested with 1.8.3. With the patch, a sip reload doesn't kick all
peers, but: When the Server gets restartet this occures:

ERROR[25526]: tcptls.c:375 ast_tcptls_client_start: Unable to connect SIP
socket to IP:Port: Connection refused

As mentioned in the 'Additional Information' the Asterisk DB entires for
the SIP peers are useless on a Asterisk restart. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-03-16 04:29 -KeX-          Note Added: 0132948                          
======================================================================




More information about the asterisk-bugs mailing list