Oracle AP SBC forwards rfc2833 RTPevent with Incorrect Payload Type
(Doc ID 2161096.1)
Last updated on MAY 15, 2017
Applies to:Acme Packet 3820 - Version E-Cz7.3.0 and later
Information in this document applies to any platform.
We had a call-flow, where an external number calls in and sends invite to IVR after which call was transferred to an agent. In this call flow invite and offer negotiation was done successfully with payload type 97.
Issue happens when SBC one sip-interface receives payload-type 97, and it incorrectly forwards it as payload-type 101. (It should forward it as 97 only, as this was the payload negotiated in signaling).
SBC is incorrectly taking this value '101' from parameter : "rfc2833-payload" which was set as 101 in calling side sip-interface configuration. A quick workaround here could be to set this rfc2833-payload to 97. This is just for this call-flow to avoid SBC using any other value except from what is used in negotiations.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document