AudioCodes E-SBC User Manual page 378

CHAPTER 18 Core Entities
'Direct Media'
sbc-direct-media
[SIPInterface_SBCDirectMedia]
Security
'TLS Context Name'
tls-context-name
[SIPInterface_TLSContext]
Parameter
Mediant 1000 Gateway & E-SBC | User's Manual
Description
Enables direct media (RTP/SRTP) flow (i.e., no
Media Anchoring) between endpoints associated with
the SIP Interface.
■ [0] Disable = (Default) Media Anchoring is
employed, whereby the media stream traverses
the device (and each leg uses a different coder or
coder parameters).
■ [1] Enable = No Media Anchoring. Media stream
flows directly between endpoints (i.e., does not
traverse the device - no Media Anchoring).
■ [2] Enable when Same NAT = No Media
Anchoring. Media stream flows directly between
endpoints if they are located behind the same
NAT.
For more information on direct media, see
Media.
Note:
■ If the parameter is enabled for direct media and
the two endpoints belong to the same SIP
Interface, calls cannot be established if the
following scenario exists:
✔
One of the endpoints is defined as a foreign
user (for example, "follow me service")
✔
and one endpoint is located on the WAN and
the other on the LAN.
The reason for the above is that in direct media,
the device does not interfere in the SIP signaling
such as manipulation of IP addresses, which is
necessary for calls between LAN and WAN.
■ To enable direct media for all calls, use the global
parameter SBCDirectMedia. If enabled, even if
the SIP Interface is disabled for direct media,
direct media is employed for calls belonging to the
SIP Interface.
■ If you enable direct media for the SIP Interface,
make sure that your Media Realm provides
sufficient ports, as media may traverse the device
for mid-call services (e.g., call transfer).
■ The parameter is applicable only to the SBC
application.
Assigns a TLS Context (SSL/TLS certificate) to the
SIP Interface.
The default TLS Context ("default" at Index 0) is
assigned to the SIP Interface by default.
Note:
- 340 -
Direct