[asterisk-bugs] [Asterisk 0012859]: realtime support and qualify (sip_poke_all_peers) after restart

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12859 
====================================================================== 
Reported By:                deti
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12859
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 122043 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             06-14-2008 11:04 CDT
Last Modified:              07-01-2008 02:29 CDT
====================================================================== 
Summary:                    realtime support and qualify (sip_poke_all_peers)
after restart
Description: 
When realtime support for chan_sip is enabled (sipusers,sippeers) and
qualify is set to yes after a restart all sippeers remain in state UNKNOWN
until they are restarted too. 
This behavior is completely different from Asterisk 1.2 and leaves the
qualify function unusable.
SIP accounts defined in sip.conf are properly scheduled for
sip_poke_peer.

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

---------------------------------------------------------------------- 
 oej - 07-01-08 02:29  
---------------------------------------------------------------------- 
We don't store the qualify state at restart and thus must re-initialize
everything. Qualify support for realtime objects is really something that
the design doesn't support, much like the 1.4 MWI system. To support
restarts properly, I think we need a major redesign. It will cause severe
issues in situations where we have multiple servers with the same realtime
database, in that case we need to store which server that had the active
registration and activate it in the proper server at restart - which will
cause issues with failover scenarios... Ouch. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-01-08 02:29  oej            Note Added: 0089455                          
======================================================================