[asterisk-bugs] [JIRA] (ASTERISK-19499) ConfBridge MOH is not working for transferee after attended transfer

Bryan Walters (JIRA) noreply at issues.asterisk.org
Wed Jan 8 14:57:03 CST 2014


     [ https://issues.asterisk.org/jira/browse/ASTERISK-19499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Walters updated ASTERISK-19499:
-------------------------------------

    Attachment: full

I'm able to reproduce this with both app_confbridge and app_meetme. The attached log is using app_meetme but let me know if you want one for app_confbridge. 
                
> 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, Resources/res_musiconhold
>    Affects Versions: 10.1.3
>         Environment: Linux, pure SIP environment
>            Reporter: Timo Teräs
>            Assignee: Timo Teräs
>            Severity: Minor
>         Attachments: confbridge.conf, 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list