[asterisk-bugs] [JIRA] (ASTERISK-22789) chan_sip SDP incorrect negotiation for RTP payload types causes DTMF recognization failure and appears to violate RFC

[J. DARIO ALVAREZ (JIRA)]

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

J. DARIO ALVAREZ commented on ASTERISK-22789:
---------------------------------------------

David:

Trace is provided in the forums case:

<------------>
This is rtp TYPE 101 not detecting DTMF:

[Oct 28 13:03:26] VERBOSE[3982][C-00000035] res_rtp_asterisk.c: Sent RTP packet to 10.8.53.18:17490 (type 00, seq 063767, ts 109280, len 000160)
[Oct 28 13:03:26] VERBOSE[3982][C-00000035] res_rtp_asterisk.c: Got RTP packet from 10.8.53.18:17490 (type 101, seq 023155, ts 2225409544, len 000004)
[Oct 28 13:03:26] VERBOSE[3982][C-00000035] res_rtp_asterisk.c: Sent RTP packet to 10.8.53.18:17490 (type 00, seq 063768, ts 109440, len 000160)
[Oct 28 13:03:26] VERBOSE[3982][C-00000035] res_rtp_asterisk.c: Got RTP packet from 10.8.53.18:17490 (type 101, seq 023156, ts 2225409544, len 000004)
[Oct 28 13:03:26] VERBOSE[3982][C-00000035] res_rtp_asterisk.c: Sent RTP packet to 10.8.53.18:17490 (type 00, seq 063769, ts 109600, len 000160)
[Oct 28 13:03:26] VERBOSE[3982][C-00000035] res_rtp_asterisk.c: Got RTP packet from 10.8.53.18:17490 (type 101, seq 023157, ts 2225409544, len 000004)
[Oct 28 13:03:26] VERBOSE[3982][C-00000035] res_rtp_asterisk.c: Sent RTP packet to 10.8.53.18:17490 (type 00, seq 063770, ts 109760, len 000160)
----------------------------------------------------------------------------------------------------------------

Packets with payload type 101 were received but Asterisk didn't accepted them as DTMF because it was waiting for type 97 (the original proposal).  

I think that correct solution is to accept 97(the value proposed by the peer) on incoming calls and 101 in outgoing calls, as previous version 1.8.11 did. 
                
> chan_sip SDP incorrect negotiation for RTP payload types causes DTMF recognization failure and appears to violate RFC
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-22789
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22789
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Channels/chan_sip/General, Channels/chan_sip/Interoperability
>    Affects Versions: 11.5.1, 11.6.0, 11.7.0
>            Reporter: Pawel Kuzak
>         Attachments: A10_sdp.txt, A11_sdp_1_log.txt, A11_sdp_1.txt, A11_sdp_2_log.txt, A11_sdp_2.txt, sip.conf
>
>
> After upgrading from Asterisk 10 to Asterisk 11 DTMF recognition does not work as expected. I've attached some SDP examples from test calls. 
>  # A10_sdp.txt (Callee is Asterisk 10.12.1)
> Caller sends INVITE with telephone-event 99, Callee answers with telephone-event 99, Caller sends RTP event with 99, DTMF recognition works, everything is fine
>  # A11_sdp_1.txt (Callee is Asterisk 11.5.1)
> Caller sends INVITE with telephone-event 99, Callee answers with telephone-event 101, Caller sends RTP event with 118 (!), DTMF recognition does not work (here the caller is obviously misbehaving as well)
>  # A11_sdp_2.txt (Callee is Asterisk 11.5.1)
> Caller sends INVITE with telephone-event 106, Callee answers with telephone-event 101, Caller sends RTP event with 101, DTMF recognition does not work (note that the payload type 101 in the 200 OK is also assigned for G726-32(!))
> Could you please take a look at it?

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