| Summary: | ASTERISK-27676: Attended Transfer Music On Hold | ||||
| Reporter: | Martin Nyström (martin.nystrom) | Labels: | |||
| Date Opened: | 2018-02-15 06:01:52.000-0600 | Date Closed: | 2018-02-15 06:10:47.000-0600 | ||
| Priority: | Minor | Regression? | No | ||
| Status: | Closed/Complete | Components: | Bridges/bridge_simple Channels/chan_sip/General | ||
| Versions: | 13.16.0 | Frequency of Occurrence | Occasional | ||
| Related Issues: |
| ||||
| Environment: | Linux DECEC 3.10.0-693.2.2.el7.x86_64 #1 SMP Tue Sep 12 22:26:13 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux CentOS Linux release 7.4.1708 (Core) | Attachments: | ( 0) 5e991c32705ace554e0da4676ffc4f79.pcap ( 1) transfer_moh.log | ||
| Description: | When performing an attended transfer and the transferee target is put into the bridge, music on hold starts playing.
Transfer Scenario A calls B B answers A B holds A B calls C C answers B B transfer A to C Issue: MusicOnHold starts for C and A is still on hold once the transfer has been performed Unable to replicate on demand, random occurrence. Looking at the logs you may notice the following [2018-02-15 10:12:05] VERBOSE[3169][C-00013ed2] bridge_channel.c: Channel SIP/margareta.brun-00022a38 swapped with SIP/fredrik.bergqvist-00022a2c into 'simple_bridge' basic-bridge <4379d469-5d98-4f37-8483-8ccb8ce35c0e> [2018-02-15 10:12:05] VERBOSE[8624][C-00013ed9] bridge_channel.c: Channel SIP/fredrik.bergqvist-00022a37 left 'simple_bridge' basic-bridge <11056989-9a07-44f9-82c5-c7a5944e24f0> [2018-02-15 10:12:05] VERBOSE[8627][C-00013ed9] res_musiconhold.c: Started music on hold, class 'default', on channel 'SIP/margareta.brun-00022a38' A: foobar_sip_trunk-00022a25 B: fredrik.bergqvist-00022a37 C: margareta.brun-00022a38 See attachments | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2018-02-15 06:01:52.886-0600 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Martin Nyström (martin.nystrom) 2018-02-15 06:02:40.625-0600 Logs attached By: Martin Nyström (martin.nystrom) 2018-02-15 06:03:39.625-0600 pcap between agent and asterisk By: Joshua C. Colp (jcolp) 2018-02-15 06:10:47.713-0600 This appears to be the same underlying problem as ASTERISK-27071 which is linked to chan_sip logic, and is open. | ||||