[asterisk-bugs] [JIRA] (ASTERISK-24518) Avaya Asterisk sip trunk DTMF mis negotiated

[Matt Jordan (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-24518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=223567#comment-223567 ] 

Matt Jordan commented on ASTERISK-24518:
----------------------------------------

The negotiation looks correct in 11.12.0.

If the DTMF isn't being detected, we'll need a full debug log with 'sip set debug on' and 'rtp set debug on' enabled showing a call negotiating DTMF and the digits being received.

Instructions for gathering a debug log can be found on the Asterisk wiki:

https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information

> Avaya Asterisk sip trunk DTMF mis negotiated
> --------------------------------------------
>
>                 Key: ASTERISK-24518
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24518
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_read
>    Affects Versions: 11.12.0
>         Environment: Centos 6.4
>            Reporter: Jonathan White
>            Assignee: Matt Jordan
>         Attachments: new.log, new show sip.txt, V1.12.0 Not Working.pcapng, V1.5.1 Working.pcapng
>
>
> I am upgrading from Asterisk ver 11.5.1 to 11.12.0
> An existing sip trunk is built from an Avaya Session Manager V6 to Asterisk
> rfc2833 is configured in sip.conf
> Asterisk V 11.5.1 negotiates and receives DTMF correctly (RTP type 101)
> Asterisk V 11.12.0 Does not receive DTMF but shows (RTP type 127)
> The Sip.conf and rtp.conf files are the same. There is no change to the Avaya configuration
> I have tried auto and inband in the sip.conf to see if I can match type 127 but this does not work either.



--
This message was sent by Atlassian JIRA
(v6.2#6252)