[asterisk-bugs] [JIRA] (ASTERISK-25079) AMI bridge of channels configured with direct_media=no results in MOH not destroyed and robotic audio on one channel
Rusty Newton (JIRA)
noreply at issues.asterisk.org
Thu Jun 4 19:52:33 CDT 2015
[ https://issues.asterisk.org/jira/browse/ASTERISK-25079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rusty Newton updated ASTERISK-25079:
------------------------------------
Component/s: Resources/res_pjsip
Core/Bridging
> AMI bridge of channels configured with direct_media=no results in MOH not destroyed and robotic audio on one channel
> --------------------------------------------------------------------------------------------------------------------
>
> Key: ASTERISK-25079
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-25079
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Core/Bridging, Resources/res_pjsip
> Affects Versions: 13.3.2, 13.4.0
> Reporter: Zane Conkle
> Assignee: Rusty Newton
> Attachments: issue_25979.log, ps_endpoints.csv, rusty_extensions.txt, rusty_full.txt, rusty_messages.txt, rusty_pjsip.txt, rusty_reproduction.pcap
>
>
> There is an issue with MOH not stopping when bridging channels.
> Lets assume PJSIP/205 is me. Steps to reproduce:
> PJSIP/205 Answers inbound call
> PJSIP/205 dials PJSIP/200 -> inbound call is placed on hold
> via AMI:
> {code}
> Action: Bridge
> ActionID: 1234
> Channel1: SIP/carrier-000000be
> Channel2: PJSIP/200-00000100
> Tone: no
> {code}
> The SIP/carrier channel still has hold music playing. I have tried this with PJSIP/PJSIP and SIP/PJSIP combinations and the issue happens both ways. I was thinking for a while it may have been due to mixing the technologies. One thing I have noticed is every so often the bridge will work. I cant find out what causes it.. It seems to be when I have the call held for an extended period of time before bridging. Also, if I set tone to "Both" the MOH will stop after the beep but you cannot hear the other party. There is a similar issue that was closed earlier this year reporting the same thing. I am not sure if this is a regression or if it was just assumed fixed.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list