[asterisk-bugs] [JIRA] (ASTERISK-21933) DTMF feature hook triggered for both caller and peer when peer initiates blind transfer

Matt Jordan (JIRA) noreply at issues.asterisk.org
Thu Jun 20 15:10:03 CDT 2013


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

Matt Jordan updated ASTERISK-21933:
-----------------------------------

    Component/s: Core/Bridging
    
> DTMF feature hook triggered for both caller and peer when peer initiates blind transfer
> ---------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-21933
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21933
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Bridging
>    Affects Versions: 12
>         Environment: Asterisk SVN-trunk-r392279
>            Reporter: Matt Jordan
>         Attachments: full.2
>
>
> Scenario:
> # Alice calls Bob with feature options {{hHkKtT}}
> # Bob Answers
> # Bob initiates a blind transfer by pressing {{#1}}
> # Both Alice and Bob hear {{pbx-transfer}}
> # Bob dials {{700}} to transfer Alice to parking
> # Alice hears {{pbx-invalid}}
> # Bob hears the parking extension
> # Bob gets hung up
> Clearly Alice shouldn't have heard anything...
> In the log files attached, Alice is SIP/digium02-0000000f; Bob is SIP/digium01-00000010.
> Bridging starts at:
> {noformat}
> [Jun 20 15:00:11] DEBUG[30930][C-00000006] bridging.c: Bridge technology holding_bridge does not have any capabilities we want.
> {noformat}
> Issue appears here:
> {noformat}
> [Jun 20 15:00:12] DEBUG[30930][C-00000006] res_rtp_asterisk.c: Creating BEGIN DTMF Frame: 35 (#), at 10.24.19.80:4052
> [Jun 20 15:00:12] DTMF[30930][C-00000006] channel.c: DTMF begin '#' received on SIP/digium01-00000010
> [Jun 20 15:00:12] DTMF[30930][C-00000006] channel.c: DTMF begin passthrough '#' on SIP/digium01-00000010
> [Jun 20 15:00:12] DEBUG[30930][C-00000006] res_rtp_asterisk.c: Setting the marker bit due to a source update
> [Jun 20 15:00:12] DEBUG[30930][C-00000006] res_rtp_asterisk.c: Creating END DTMF Frame: 35 (#), at 10.24.19.80:4052
> [Jun 20 15:00:12] DTMF[30930][C-00000006] channel.c: DTMF end '#' received on SIP/digium01-00000010, duration 150 ms
> [Jun 20 15:00:12] DTMF[30930][C-00000006] channel.c: DTMF end accepted with begin '#' on SIP/digium01-00000010
> [Jun 20 15:00:12] DTMF[30930][C-00000006] channel.c: DTMF end passthrough '#' on SIP/digium01-00000010
> [Jun 20 15:00:12] DEBUG[30930][C-00000006] bridging.c: DTMF feature string on 0x7fdbb8024df8(SIP/digium01-00000010) is now '#'
> [Jun 20 15:00:12] DEBUG[30898][C-00000006] res_rtp_asterisk.c: Creating BEGIN DTMF Frame: 35 (#), at 10.24.19.55:4000
> [Jun 20 15:00:12] DTMF[30898][C-00000006] channel.c: DTMF begin '#' received on SIP/digium02-0000000f
> [Jun 20 15:00:12] DTMF[30898][C-00000006] channel.c: DTMF begin passthrough '#' on SIP/digium02-0000000f
> [Jun 20 15:00:12] DEBUG[30898][C-00000006] res_rtp_asterisk.c: Setting the marker bit due to a source update
> [Jun 20 15:00:12] DEBUG[30898][C-00000006] res_rtp_asterisk.c: Creating END DTMF Frame: 35 (#), at 10.24.19.55:4000
> [Jun 20 15:00:12] DTMF[30898][C-00000006] channel.c: DTMF end '#' received on SIP/digium02-0000000f, duration 60 ms
> [Jun 20 15:00:12] DTMF[30898][C-00000006] channel.c: DTMF end accepted with begin '#' on SIP/digium02-0000000f
> [Jun 20 15:00:12] DTMF[30898][C-00000006] channel.c: DTMF end '#' detected to have actual duration 59 on the wire, emulation will be triggered on SIP/digium02-0000000f
> [Jun 20 15:00:12] DTMF[30898][C-00000006] channel.c: DTMF end passthrough '#' on SIP/digium02-0000000f
> [Jun 20 15:00:12] DEBUG[30898][C-00000006] bridging.c: DTMF feature string on 0x7fdbb80735b8(SIP/digium02-0000000f) is now '#'
> {noformat}
> The DTMF '#' should never have been passed through the bridge from SIP/digium01 to SIP/digium02.

--
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