Summary:ASTERISK-13186: misdn trunk meetme user gets dialtone after entering conference
Reporter:Thomas Stein (himbeere)Labels:
Date Opened:2008-12-09 09:47:03.000-0600Date Closed:2011-06-07 14:07:53
Versions:Frequency of
Environment:Attachments:( 0) meetme-debug.txt
Description:app_meetme behaves somewhat strange on my asterisk installation. It's asterisk 1.4.22, misdn-1.1.8 and dahdi 2.0.0. The problem occurs as soon as a third user enters the conference room. After entering the conf-pin he gets a dialtone followed by the "invalid" message. I have no idea why this happens. This error does not occur if i use a sip trunk for the same conference room. The problem also disappears if no "I" option is configured for the meetme extension. Let me know if you need more information.

best regards
Comments:By: Joshua C. Colp (jcolp) 2009-01-26 15:21:59.000-0600

This issue needs an attachment with the complete console output that shows this issue plus configuration minus any passwords if present.

By: Thomas Stein (himbeere) 2009-01-27 00:56:50.000-0600

conf => 2345,xxxx

exten => 12,1,Ringing
exten => 12,n,Wait(3)
exten => 12,n,MeetMe(2345,pM)
exten => 12,n,Playback(vm-goodbye)
exten => 12,n,Hangup

By: Jeff Peeler (jpeeler) 2009-08-17 16:18:11

The dialplan snipet is not console output. I'd like to see that with asterisk invoked with a verbosity of at least 3. I haven't been able to reproduce this yet.

EDIT: Oops, missed the attachment. Still need the verbosity turned up though.

By: Leif Madsen (lmadsen) 2009-10-08 10:34:23

This is being reported against a pretty old version of Asterisk now. Any chance of retesting on the latest version so we can verify if we still need to review this? Thanks!

By: Leif Madsen (lmadsen) 2009-10-26 10:24:19

Closed due to lack of feedback. If the reporter is able to provide the requested information, please reopen this issue. Thanks!