Summary:ASTERISK-16539: Dropped calls when entering meetme conference
Reporter:Daniel Knoll (kenji)Labels:
Date Opened:2010-08-10 12:36:15Date Closed:2011-06-07 14:10:16
Versions:Frequency of
Environment:Attachments:( 0) issue_0017828_full_log_snipped.txt
Description:Sometimes but often, a call dropped when another entering in the same conference.
I have no idea, what the problem is, but in the Logfile i attached, you can see, that in the same second as a caller entering the conference room, another caller is dropped, he is in the same conference room.
If I correctly interpret the log file, the other Caller get an "#" DTMF tone, that forcing the call to hangup
(you can see that in Logfile with Timestamp [Aug  3 22:18:24])

I run a conference platform with hundreds of callers simultaneously and slowly my customers are not amused if i can't fix that.


I can't reproduce this and have no more ideas and i hope and pray you to help me with the problem.

I use the asterisk Version with MeetMe Patch from  ASTERISK-1726502
Comments:By: Leif Madsen (lmadsen) 2010-08-11 12:33:18

Looks like Asterisk is doing exactly at you tell it:

[Aug  3 22:18:23] DTMF[9727] channel.c: DTMF begin '#' received on SIP/sipprovider-in-000003f0
[Aug  3 22:18:23] DTMF[9727] channel.c: DTMF begin ignored '#' on SIP/sipprovider-in-000003f0

   p[(keys)]: Allow user to exit the conference by pressing '#' (default)
   or any of the defined keys. If keys contain '*' this will override option

Pretty sure this is because someone is dialing the conference extension followed by a # (which is typically interpreted to mean "I'm don't entering this extension").

I suggest you modify your dialplan to accept that DTMF in addition to the extension number so that it is "eaten" by the system and not entered into the conference.

This could probably be done in a couple of ways:  either catch the # in the dialplan in addition to accepting it without the #, or add a Wait(2) or something prior to entering the conference.