[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:                     new
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:              06-27-2008 16:34 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.

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

---------------------------------------------------------------------- 
 Corydon76 - 06-27-08 16:34  
---------------------------------------------------------------------- 
I'm not sure how this is different from 1.2.  Realtime peers are never
loaded from the database until they are requested by a registration. 
Perhaps when you were running with 1.2, you had your SIP phone registration
timeout set much lower? 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-27-08 16:34  Corydon76      Note Added: 0089382                          
======================================================================