[Home]

Summary:ASTERISK-16824: Music on hold not released after answer of bridged call
Reporter:Bruce McAlister (asgaroth)Labels:
Date Opened:2010-10-18 08:48:53Date Closed:2021-09-28 13:29:22
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Resources/res_musiconhold
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) ivanmcshane-failed.cap
( 1) ivanmcshane-working.cap
( 2) messages-failing.txt
( 3) messages-working.txt
Description:When bridging two calls after one has been put on hold, the called person hears both music on hold along with the original callers voice. This is occurring more often than not. After several tests we are seeing 5 out of 7 calls "failing" whereby music on hold is not released when the called party has answered.

h5. Steps to Reproduce

This is difficult to reliably reproduce. We have tried this over 3 different carriers, trying with either IAX or SIP and the problem still persists.

h5. Additional Information

I've not classified this problem as I'm not too sure where the issue lies. I'm assuming, for the moment, that it may be related to music on hold.

I've attached 2 messages files one of a working call and one of a "failed" call, where the music on hold is not released.

The messages files contain the following output:

* core set verbose 10
* core set debug 10
* sip set debug on

I have tried this with Asterisk version 1.6.2.13 standalone, and with asterisk version 1.6.2.13 with the patch from ASTERISK-16583 applied.
Comments:By: Bruce McAlister (asgaroth) 2010-10-20 08:31:36

This issue also presents itself with v1.8.0-rc5 on Solaris.

I will be testing this on Linux (v1.8.0-rc5) shortly to see if it us a Solaris specific issue.

By: Bruce McAlister (asgaroth) 2010-10-20 15:55:27

I've just attempted this on CentOS 5.5 with asterisk 1.6.2.13 and the issue still presents itself

By: Bruce McAlister (asgaroth) 2010-10-20 16:26:58

I've attached a sip trace of one working call and one failed call if that will help try to track down where the issue lies.

By: Leif Madsen (lmadsen) 2010-10-29 09:05:25

I dropped this to minor because I thought it was just solaris, but if you're getting this with linux as well, I'll leave it at the major you originally had it set to.

By: Bruce McAlister (asgaroth) 2010-10-29 09:15:02

Thats correct yes, the versions tested thus far are:

1.8.0-rc5 on Solaris 10 32-bit
1.8.0-rc5 on CentOS 5.5 64-bit
1.8.0 on Solaris 10 32-bit
1.8.0 on CentOS 5.5 64-bit
1.6.2.13 on CentOS 5.5 64-bit
1.6.2.13 on Solaris 10 32-bit

All the above variants exhibit the same problem. It is intermittent and difficult to track any difference in the calls.

The SIP traces I have above are one successfull call and on failed call. The traces are taken from a 1.6.2.13 server running on CentOS 5.5 64-bit.

By: Bruce McAlister (asgaroth) 2010-11-30 05:09:33.000-0600

Hi, any recommendations on how to proceed with this bug?

By: André Emerich (aemerich) 2012-11-21 10:01:57.159-0600

I have the same problem on Linux.

When the called party answer, I hear it and the Music On Hold at same time..

Follow below my CLI messages:
   -- Executing [1234@HOTLINE:20] Dial("Local/99999999@HOTLINE_DIAL-e559;1", "SIP/CallManagerTF01/5401,,rR") in new stack
 == Using SIP RTP CoS mark 5
   -- Called CallManagerTF01/5678
   -- SIP/CallManagerTF01-00000210 is ringing
   -- Remote UNIX connection disconnected
   -- Call on SIP/CallManagerTF01-00000210 placed on hold
   -- Started music on hold, class 'default', on SIP/AsteriskCBM02-0000020f
   -- SIP/CallManagerTF01-00000210 answered SIP/AsteriskCBM02-0000020f
   -- Stopped music on hold on SIP/AsteriskCBM02-0000020f
   -- Native bridging SIP/AsteriskCBM02-0000020f and SIP/CallManagerTF01-00000210
   -- Started music on hold, class 'default', on SIP/AsteriskCBM02-0000020f

AFTER HANGUP
   -- Stopped music on hold on SIP/AsteriskCBM02-0000020f
 == Spawn extension (HOTLINE, 5188, 20) exited non-zero on 'SIP/AsteriskCBM02-0000020f'

By: Sean Bright (seanbright) 2020-09-18 15:14:38.587-0500

Is anyone able to reliably reproduce this on a current release version of Asterisk?

By: Sean Bright (seanbright) 2021-09-28 13:29:22.145-0500

If you can reproduce on a supported version of Asterisk, commenting on this issue will re-open it. Thank you.