[asterisk-bugs] [Asterisk 0018882]: [patch] allow storing TCP peers in ast db & alllow rtupdate=no to use them

[Asterisk Bug Tracker]

The issue 0019323 has been set as DUPLICATE OF the following issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18882 
====================================================================== 
Reported By:                cmaj
Assigned To:                bbryant
====================================================================== 
Project:                    Asterisk
Issue ID:                   18882
Category:                   Channels/chan_sip/TCP-TLS
Reproducibility:            always
Severity:                   tweak
Priority:                   normal
Status:                     closed
Asterisk Version:           1.8.3-rc2 
JIRA:                       SWP-3202 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2011-02-24 12:35 CST
Last Modified:              2011-05-19 14:28 CDT
====================================================================== 
Summary:                    [patch] allow storing TCP peers in ast db & alllow
rtupdate=no to use them
Description: 
A nasty comment about not keeping track of TCP peers was deleted and simple
workaround offered in attached patch. It is safe to store TCP peers in AST
DB just like UDP peers.

Additionally, this patch covers situations with read-only realtime
storage, which is great with LDAP backends because they are very much
read-friendly. But without writing to the backend (when rtupdate="no" in
sip.conf) you lose track of where the peers are during a restart of
Asterisk - not good.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
has duplicate       0019323 Registration info lost after "sip ...
related to          0019318 [patch] [regression] SIP peers unregist...
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-05-19 14:28 lmadsen        Relationship added       has duplicate 0019323
======================================================================