Interworking Miscellaneous Media Handling; Interworking Dtmf Methods; Interworking Rtp Redundancy; Interworking Rtp-Rtcp Multiplexing - AudioCodes Mediant 4000 SBC User Manual

CHAPTER 22 SBC Overview
The device transparently forwards Binary Floor Control Protocol (BFCP) signaling over UDP
between IP entities (RFC 4582). BFCP is a signaling protocol used by some third- party
conferencing servers to share content (such as video conferencing, presentations or documents)
between conference participants (SIP clients supporting BFCP). The SDP offer/answer exchange
model is used to establish (negotiate) BFCP streams between clients. The BFCP stream is
identified in the SDP as 'm=application <port> UDP/BFCP' and a dedicated UDP port is used for
the BFCP streams.

Interworking Miscellaneous Media Handling

This section describes various interworking features relating to media handling.

Interworking DTMF Methods

The device supports interworking between various DTMF methods such as RFC 2833, In-Band
DTMF's, and SIP INFO (Cisco\Nortel\Korea). By default, the device allows the remote user agents
to negotiate (in case of RFC 2833) and passes DTMF without intervention. However, if two user
agents (UA) support different DTMF methods, the device can interwork these different DTMF
methods at each leg.
This DTMF interworking feature is enabled using IP Profiles (ini file parameter IPProfile):
■ SBCRFC2833Behavior - affects the RFC 2833 SDP offer-answer negotiation:
● [0]: (default) the device does not intervene in the RFC 2833 negotiation.
● [1]: each outgoing offer-answer includes RFC 2833 in the offered SDP (the device adds
RFC 2833 only if the incoming offer does not include RFC 2833).
● [2]: the device removes RFC 2833 from the incoming offer.
■ SBCAlternativeDTMFMethod – the device's first priority for DTMF method at each leg is RFC
2833. Therefore, if a specific leg negotiates RFC 2833 successfully, then the chosen DTMF
method for this leg is RFC 2833. For legs where RFC 2833 is not negotiated successfully, the
device uses the parameter to determine the DTMF method for the leg.
The chosen DTMF method determines (for each leg) which DTMF method is used for sending
DTMF's. If the device interworks between different DTMF methods and one of the methods is In-
band\RFC 2833, detection and generation of DTMF methods requires DSP allocation.

Interworking RTP Redundancy

The device supports interworking of RTP redundancy (according to RFC 2198) between SIP
entities. Employing IP Profiles, you can configure RTP redundancy handling per SIP entity:
■ Generate RFC 2198 redundant packets (IpProfile_RTPRedundancyDepth parameter).
■ Determine RTP redundancy support in the RTP redundancy negotiation in SDP offer/answer
(IpProfile_SBCRTPRedundancyBehavior parameter). If not supported, the device discards
RTP redundancy packets (if present) received from or sent to the SIP entity.
For more information, see the above parameters in

Interworking RTP-RTCP Multiplexing

The device supports interworking of RTP- RTCP multiplexing onto a single, local UDP port
(according to RFC 5761) between SIP entities. Employing IP Profiles, you can configure RTP
multiplexing per SIP entity, using the IPProfile_SBCRTCPMux parameter (see
Profiles).
Configuring IP Profiles.
- 512 -
Mediant 4000 SBC | User's Manual
Configuring IP