|Summary:||ASTERISK-15978: MOH+Madplay when going from one to another the second stream is not started|
|Date Opened:||2010-04-20 07:38:02||Date Closed:||2011-01-13 15:27:54.000-0600|
|Environment:||Attachments:||( 0) 770_wabc.sh|
( 1) a7_english.sh
( 2) extensions.conf
( 3) mysql.log
If I use MadPlay+MOH+RT in a queue. When the user enters you hear the stream. If you do ps aux you see the script for MadPlay that MOH calls. If the user exits that queue and goes in to a new one that is playing a different stream the caller hears nothing. If you do ps aux you still see the first stream there (the first URL) and not the second one. The caller hears nothing. Once you hang up and do ps aux you do not see either streams there. I will upload all config files.
|Comments:||By: dovid (dovid) 2010-04-22 06:31:16|
FTI: Upgraded to 184.108.40.206 and I still have the same issue.
By: dovid (dovid) 2010-05-11 02:15:18
By: Brett Bryant (bbryant) 2010-09-10 11:33:58
Dovid, I setup your queue environment and was unable to reproduce the issue with the current 1.6.2 branch. If this issue is still occurring, could you send me console logs of when the problem happens and describe how the caller is being transfered from one queue to another?
This is the dialplan test that I used to try and replicate your issue.
exten => 100,1,Answer
exten => 100,n(q770),Queue(770_wabc,n,,,10)
exten => 100,n,Goto(streamer,101,qa7)
exten => 101,1,Answer
exten => 101,n(qa7),Queue(a7_english,n,,,10)
exten => 101,n,Goto(streamer,100,q770)
By: dovid (dovid) 2010-09-12 14:50:43
Will the latest 1.6.2 do or should I grab 1.6.2 branch ? If the latter can you send me the URL for it ? I will try to re-produce.
I wonder if it is related to: https://issues.asterisk.org./view.php?id=17202
By: Brett Bryant (bbryant) 2010-09-20 16:28:15
Dovid, try the 1.6.2 branch. If you can reproduce it please give me all configuration files involved as well as instructions on exactly what you did so I can try to help you get it fixed.
By: Brett Bryant (bbryant) 2011-01-13 10:34:39.000-0600
Thank you for the bug report. However I am unable to reproduce this issue. We are now going to close this report - please feel free to reopen when you have more information at hand.