[asterisk-bugs] [JIRA] (ASTERISK-19499) ConfBridge MOH is not working for transferee after attended transfer
Matt Jordan (JIRA)
noreply at issues.asterisk.org
Fri Mar 28 13:54:34 CDT 2014
[ https://issues.asterisk.org/jira/browse/ASTERISK-19499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Jordan updated ASTERISK-19499:
-----------------------------------
Target Release Version/s: 11.9.0
> ConfBridge MOH is not working for transferee after attended transfer
> --------------------------------------------------------------------
>
> Key: ASTERISK-19499
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-19499
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Applications/app_confbridge, Applications/app_meetme, Channels/chan_sip/Transfers, Resources/res_musiconhold
> Affects Versions: 10.1.3, 11.7.0
> Environment: Linux, pure SIP environment
> Reporter: Timo Teräs
> Assignee: Timo Teräs
> Severity: Minor
> Target Release: 1.8.27.0, 11.9.0
>
> Attachments: confbridge.conf, conf_bridge_full, full, log
>
>
> Bug observed with two SIP accounts and ConfBridge with MOH.
> 1. SIP A calls SIP B
> 2. B initiates attended transfer; A is placed on hold, MOH works
> 3. B calls ConfBridge service in "waiting for marked user" state, B is placed on hold, MOH works
> 4. B finalizes attended transfer: A is transferred to ConfBridge in waiting state
> EXPECTED:
> SIP A gets MOH from ConfBridge which B was getting just before transfer
> ACTUAL RESULT:
> No MOH. SIP B hangs up and apparently bridging code stops MOH on all parties. SIP B does get transferred to ConfBridge but does not hear MOH. Additionally, if from this state SIP B invokes an in-conference dtmf action, MOH is (re)started after the action completes and MOH is heard again.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list