[asterisk-bugs] [JIRA] Created: (ASTERISK-20314) In certain scenarios, asterisk can send rtp in an unsupported payload type to an endpoint

[Matt Jordan (JIRA)]

In certain scenarios, asterisk can send rtp in an unsupported payload type to an endpoint
-----------------------------------------------------------------------------------------

                 Key: ASTERISK-20314
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20314
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
    Affects Versions: 11.0.0-beta1
         Environment: OS: Debian squeeze distribution x86_64 architecture
            Reporter: NITESH BANSAL


SIP caller A supports alaw/ulaw

Asterisk is configured to support alaw,ulaw,g729 and places all 3 in the offer to B

SIP called B supports g729,alaw,ulaw putting all 3 in the 200 OK.

Asterisk sees that there is one common codec between A and B, it sets up a packet to packet bridge

If B sends audio in G.729, it gets forwarded to A without transcoding which is expecting alaw/ulaw. Asterisk does not check the incoming payload from the peer and forwards to another peer
even if the payload received was different from the payload expected on the bridge.



--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira