My Oracle Support Banner

What is the New Feature and How to Disable: "Common Codec support fro Transcoded SIPREC Calls" in ECZ810 (Doc ID 2509434.1)

Last updated on AUGUST 27, 2020

Applies to:

Acme Packet 4600 - Version E-Cz8.1.0 and later
Information in this document applies to any platform.
Before ECZ810 version, such as in ECZ730, SBC did not support common Codec for the transcoded SIPREC Calls. Here is an example.

Assume there is real transcoded call as following:

Calling A==>G711==>SBC==> G729==>called B

1) In ECZ730, for above transcoded call flow, SBC will have following SDP for this session recording call:

m=audio 10010 RTP/AVP 0
a=rtpmap:0 PCMU/8000
a=sendonly
m=audio 10014 RTP/AVP 18
a=rtpmap:18 G729/8000

2) However, in ECZ810, it will have following m line in the SDP by default. As can see, both m line have same codec which is same as called side m line of the real call.
m=audio 10002 RTP/AVP 18
a=rtpmap:18 G729/8000
m=audio 10006 RTP/AVP 18
a=rtpmap:18 G729/8000

3) To change the default behavior in ECZ810, there is hidden sip options in sip-config to disable such default behavior.

In sip-config, add following options:
# options +disable-srs-xcode

Goal

In ECZ810 release, there is new feature introduced for transcoded siprec calls. By this new feature, the E-SBC supports SIPREC on all transcoded call flows by capturing the same codec type from the "called" party side of the session on both legs of the call. This feature is enabled by default. 

By configuring one hidden option under sip-config can disable this feature

 

Solution

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
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.