[asterisk-dev] [Code Review] 3225: Asterisk doesn't support the dynamic payload change in rtp mapping in the 200 OK response

[Nitesh Bansal]

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/3225/#review10918
-----------------------------------------------------------

Ship it!


Ship It!

- Nitesh Bansal


On Feb. 14, 2014, 9:45 a.m., Nitesh Bansal wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviewboard.asterisk.org/r/3225/
> -----------------------------------------------------------
> 
> (Updated Feb. 14, 2014, 9:45 a.m.)
> 
> 
> Review request for Asterisk Developers.
> 
> 
> Bugs: ASTERISK-23279
>     https://issues.asterisk.org/jira/browse/ASTERISK-23279
> 
> 
> Repository: Asterisk
> 
> 
> Description
> -------
> 
> Scenario:
> Asterisk sends the INVITE proposing alaw and telephone-event, it proposes rtpmap:101 for telephone-event.
> Peer responds with 2xx, it answers with alaw and telephone-event also, but it proposes a different rtpmap number(rtpmap:103) for telephone-event.
> 
> Expected Behaviour: Asterisk should honour the rtpmapping in the response and send DTMF packets using 103 as payload type for DTMF.
> 
> Actual Behaviour: Asterisk sends DTMF packets using payload type 101.
> 
> 
> Diffs
> -----
> 
>   http://svn.asterisk.org/svn/asterisk/branches/11/main/rtp_engine.c 408068 
> 
> Diff: https://reviewboard.asterisk.org/r/3225/diff/
> 
> 
> Testing
> -------
> 
> 
> Thanks,
> 
> Nitesh Bansal
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20140221/5e197160/attachment.html>