|Summary:||ASTERISK-17337: [regression] When caller sent to queue, MoH stops, only ringback tone|
|Date Opened:||2011-02-02 09:58:29.000-0600||Date Closed:||2011-02-16 08:22:37.000-0600|
|Description:||I have the same Problem as in Bug 0018517 (https://issues.asterisk.org/bug_view_advanced_page.php?bug_id=18517)|
The summary pretty much says it all. Asterisk says its starting MoH but really you just get a split second of it, then you get ringback tone for the rest of the waiting time.
This happens with MoH classes stored in both musiconhold.conf and in RT. This looks awfully like as if I was using Queue()'s option 'R' (give caller a ringback tone when an agent is ringing), which I am not.
Agent logged in with (AgentCallBackLogin)
LOG (see Additional Informations):
Now i found the Reason.
If you revert the following patch, the Problem is solved.
Remove the link:
****** ADDITIONAL INFORMATION ******
[Feb 2 16:12:20] VERBOSE logger.c: -- Executing [YYYYYYYYYYYYYYY@sipin:7] Set("SIP/XXXXXXXXXXXX-00000009", "CALLERID(all)=XXX <+AAAAA>") in new stack
[Feb 2 16:12:20] VERBOSE logger.c: -- Executing [YYYYYYYYYYYYYYY@sipin:8] Queue("SIP/XXXXXXXXXXXX-00000009", "qtestit") in new stack
[Feb 2 16:12:20] VERBOSE logger.c: -- Started music on hold, class 'default', on SIP/XXXXXXXXXXXX-00000009
[Feb 2 16:12:20] VERBOSE logger.c: -- outgoing agentcall, to agent '20', on 'Local/20@user-a936,1'
[Feb 2 16:12:20] VERBOSE logger.c: -- Executing [20@user:1] Dial("Local/20@user-a936,2", "SIP/20|60") in new stack
[Feb 2 16:12:20] VERBOSE logger.c: -- Called 20
[Feb 2 16:12:20] VERBOSE logger.c: -- SIP/20-0000000a is ringing
[Feb 2 16:12:20] VERBOSE logger.c: -- Agent/20 is ringing
[Feb 2 16:12:20] VERBOSE logger.c: -- Stopped music on hold on SIP/XXXXXXXXXXXX-00000009
|Comments:||By: Sébastien Couture (sysreq) 2011-02-02 10:11:05.000-0600|
Hi, I'm the one who opened issue 18517.. and I still have the issue on SVN 1.6.2 r302833.
Good job catching that line! I'll try it out tonight and report back. Thanks!
By: Leif Madsen (lmadsen) 2011-02-16 08:22:36.000-0600
Closed as the duplicate issue of this was also marked closed.