Session Border Controller (SBC) Transcoding DTMF Telephone-events From 102/99 To 101
(Doc ID 2434242.1)
Last updated on OCTOBER 09, 2020
Applies to:Acme Packet 4500 - Version S-Cz7.2.0 and later
Information in this document applies to any platform.
Intermittent issue where DTMF is failing due to the SBC sending the RTP packet for DTMF with the wrong Payload type.
1. One issue reported as SBC transcoding DTMF ( RTP packet ) telephone-events from 102 to 101
2. For another failed scenario there is a Reinvite from the far end which did not change the SDP (increased the version only) agreed to use telephone event 99. Again DTMF 1 was sent to the SBC as Payload type: telephone-event (99) but in this case the SBC sent to the far end Payload type: DynamicRTP-Type-101 (101) in the RTP packet causing the far end not to recognize the DTMF.
Basically it happens for the dynamic plaods.
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