[asterisk-bugs] [JIRA] (ASTERISK-24459) Asterisk 12 dosent do dtmf transcoding from inband to rfc4733
Matt Jordan (JIRA)
noreply at issues.asterisk.org
Thu Nov 13 17:33:29 CST 2014
[ https://issues.asterisk.org/jira/browse/ASTERISK-24459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=223534#comment-223534 ]
Matt Jordan commented on ASTERISK-24459:
----------------------------------------
The problem here is the following:
{noformat}
[Oct 27 14:48:47] DEBUG[3932][C-0000000e] bridge_native_rtp.c: Locally RTP bridged 'PJSIP/KAMnet_BK-00000017' and 'PJSIP/KAMnet_BK_out-00000018' in stack
[Oct 27 14:48:47] DEBUG[3932][C-0000000e] bridge.c: Bridge 4c83cd57-4ebd-4046-be0e-f99c2b37c3b5: calling native_rtp technology start
[Oct 27 14:48:47] DEBUG[3932][C-0000000e] bridge.c: Bridge 4c83cd57-4ebd-4046-be0e-f99c2b37c3b5: calling simple_bridge technology destructor
[Oct 27 14:48:47] DEBUG[3923][C-0000000e] bridge.c: Bridge technology holding_bridge does not have any capabilities we want.
[Oct 27 14:48:47] DEBUG[3923][C-0000000e] bridge.c: Bridge technology softmix does not have any capabilities we want.
[Oct 27 14:48:47] DEBUG[3923][C-0000000e] bridge.c: Bridge technology simple_bridge has less preference than native_rtp (50 <= 90). Skipping.
[Oct 27 14:48:47] DEBUG[3923][C-0000000e] bridge.c: Chose bridge technology native_rtp
[Oct 27 14:48:47] DEBUG[3923][C-0000000e] bridge.c: Bridge 4c83cd57-4ebd-4046-be0e-f99c2b37c3b5 is already using the new technology.
[Oct 27 14:48:47] DEBUG[3932][C-0000000e] bridge.c: Bridge technology holding_bridge does not have any capabilities we want.
[Oct 27 14:48:47] DEBUG[3932][C-0000000e] bridge.c: Bridge technology softmix does not have any capabilities we want.
[Oct 27 14:48:47] DEBUG[3932][C-0000000e] bridge.c: Bridge technology simple_bridge has less preference than native_rtp (50 <= 90). Skipping.
[Oct 27 14:48:47] DEBUG[3932][C-0000000e] bridge.c: Chose bridge technology native_rtp
[Oct 27 14:48:47] DEBUG[3932][C-0000000e] bridge.c: Bridge 4c83cd57-4ebd-4046-be0e-f99c2b37c3b5 is already using the new technology.
[Oct 27 14:48:48] DEBUG[3932][C-0000000e] res_rtp_asterisk.c: 0x1793d70 -- Probation learning mode pass with source address 10.9.15.1:38346
{noformat}
We've ended up choosing a native RTP bridge when we shouldn't, as the channels support incompatible DTMF types.
That being said, can you provide the {{pjsip.conf}} for the two endpoints in question? The output of {{DumpChan}} does not include the DTMF mode types.
> Asterisk 12 dosent do dtmf transcoding from inband to rfc4733
> -------------------------------------------------------------
>
> Key: ASTERISK-24459
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-24459
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: pjproject/pjsip
> Affects Versions: 12.2.0, 12.3.2
> Environment: Centos 6.4
> Reporter: Yaniv Simhi
> Assignee: Matt Jordan
> Attachments: messages_in_rfc4733.log
>
>
> Asterisk don't make DTMF transcoding for this senario : call from endpoit A with inband DTMF mode to endpoint B with rfc4733 DTMF mode.
> RTP forced to pass through Asterisk.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list