[asterisk-bugs] [Asterisk 0018420]: Meetme doesn't detect peer unreachable

[Asterisk Bug Tracker]

The following issue has been UPDATED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18420 
====================================================================== 
Reported By:                nowatel
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18420
Category:                   Applications/app_meetme
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     closed
Asterisk Version:           1.6.2.14 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 no change required
Fixed in Version:           
====================================================================== 
Date Submitted:             2010-12-03 11:53 CST
Last Modified:              2010-12-07 13:10 CST
====================================================================== 
Summary:                    Meetme doesn't detect peer unreachable
Description: 
We have a simple scenario:

Peer '1' is joining the meetme room (with qualify options enabled). If we
reboot the peer and it looses the connections, it goes unreachable (with
proper peer '1' is unreachable info) but it is still shown as a member of
the meetme room (on the 'core show channels')

It looks like it stays forever and if we won't hangup properly, it won't
disappear from the channel list.
====================================================================== 

---------------------------------------------------------------------- 
 (0129418) lmadsen (administrator) - 2010-12-07 13:10
 https://issues.asterisk.org/view.php?id=18420#c129418 
---------------------------------------------------------------------- 
This is more of a configuration issue. You need to use session-timers in
sip.conf in order to track this stuff appropriately. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-12-07 13:10 lmadsen        Note Added: 0129418                          
2010-12-07 13:10 lmadsen        Status                   new => closed       
2010-12-07 13:10 lmadsen        Resolution               open => no change
required
======================================================================