[Home]

Summary:ASTERISK-09386: MeetMe members stay forever if softphone killed
Reporter:Dmitry Andrianov (dimas)Labels:
Date Opened:2007-05-04 15:33:36Date Closed:2011-06-07 14:08:05
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Channels/chan_sip/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Situation: using softphone (X-Lite 3.0) i start MeetMe conference. Then I kill softphone (just forcibly terminate application using Windows Task Manager). After some time Asterisk detects this:

[May 3 17:01:00] NOTICE[31911]: chan_sip.c:15197 sip_poke_noanswer: Peer '1001' is now UNREACHABLE! Last qualify: 106

but even an hour after that moment, shows participant:

line*CLI> meetme list 1234
User #: 01 1001 John Smith Channel: SIP/1001-084c21f0 (unmonitored) 01:36:30
1 users in that conference.


****** ADDITIONAL INFORMATION ******

It is 100% reproducible. I probably can not make good dumps on production system (because other channels will polute logs) but it also reproduces on VMware so all possible debug info can be collected.

Also I'm not sure if it is related to the problem, but 'sip show channels' shows only one channel after softphone was just killed:

Peer             User/ANR    Call ID      Seq (Tx/Rx)  Form  Hold     Last Message  
192.168.7.213    1001        MjFmMTE5NmE  00101/00002  ulaw  No       Rx: ACK                  
1 active SIP channel

but some time later it shows more channels although I'm pretty sure softphone was not started.

Peer             User/ANR    Call ID      Seq (Tx/Rx)  Form  Hold     Last Message  
192.168.7.213    (None)      6570211134e  00102/00000  unkn  No       Init: OPTIONS            
192.168.7.213    1001        MjFmMTE5NmE  00101/00002  ulaw  No       Rx: ACK                  
192.168.7.213    1001        MTRlNzRmZDY  00102/00002  unkn  No       Tx: NOTIFY                
3 active SIP channels
Comments:By: Dmitry Andrianov (dimas) 2007-05-04 15:34:43

Sorry, forgot to chose proper catagory :(
By: Jason Parker (jparker) 2007-05-04 15:47:57

You'll need to set rtptimeout in sip.conf to some sane value.

Closing.  Configuration issue (sort of..)