|Summary:||ASTERISK-17419: Asterisk 126.96.36.199: Quiet mode doesn't work in dyanmic MeetMe|
|Reporter:||Nicholas Blasgen (nblasgen)||Labels:|
|Date Opened:||2011-02-17 00:29:16.000-0600||Date Closed:||2011-02-18 13:58:54.000-0600|
|Description:||This is a follow-up to bug # 15292 which was closed for being unable to be reproduced.|
Oddly enough, I've had this "bug" forever and never thought about it as being a bug until today. Now I see that it is a bug.
exten => 5000,1,Answer()
exten => 5000,n,MeetMe(|AqMdeF)
Plays the audio recording "You are entering conference number Zero" or something similar to that.
I haven't tried in the newest version. Been too happy with the stability of 188.8.131.52 to go any higher.
|Comments:||By: Leif Madsen (lmadsen) 2011-02-18 13:58:53.000-0600|
I still can't reproduce this. Please test on a development server with the latest 1.4 and 1.8 branches. You can reopen this issue if you can reproduce there.
By: Nicholas Blasgen (nblasgen) 2011-06-20 16:10:09.027-0500
-- Executing [5100@meetme:1] Answer("Local/blasgen@realtimedb-a094,1", "") in new stack
-- Executing [5100@meetme:2] SetMusicOnHold("Local/blasgen@realtimedb-a094,1", "nomusic") in new stack
-- Executing [5100@meetme:3] MeetMe("Local/blasgen@realtimedb-a094,1", "|AqMdeF") in new stack
-- <Local/blasgen@realtimedb-a094,1> Playing 'conf-enteringno' (language 'en')
== Spawn extension (dialer, 6194879672, 2) exited non-zero on 'Local/6194879672@dialer-27dc,2'
== Spawn extension (realtimedb, blasgen, 3) exited non-zero on 'Local/blasgen@realtimedb-a094,2'
-- <SIP/rdialer-0000392f> Playing 'digits/0' (language 'en')
-- Created MeetMe conference 1023 for conference '0'
-- Started music on hold, class 'default', on channel 'SIP/rdialer-0000392f'
I've opened another bug due to the SetMusicOnHold not properly working, but it does seem that in Asterisk 1.4.41 the issue is still present.
exten => 5100,1,Answer()
exten => 5100,n,SetMusicOnHold(nomusic)
exten => 5100,n,MeetMe(|AqMdeF)
By: Paul Belanger (pabelanger) 2011-06-20 16:29:29.435-0500
In the future, please attach debug output to the issue tracker, not in the comments field. This will help to keep the comments readable.