Interworking Call Hold; Interworking Sip Via Headers; Interworking Sip User-Agent Headers; Interworking Sip Record-Route Headers - AudioCodes Mediant 800 User Manual

Gateways & session border controllers
Hide thumbs Also See for Mediant 800:
Table of Contents

Advertisement

CHAPTER 30    SBC Overview

Interworking Call Hold

The device supports the interworking of call hold / retrieve requests between SIP entities
supporting different call hold capabilities:
Interworking SDP call hold formats. This is configured by the IP Profile parameter, 'SBC
Remote Hold Format'.
Interworking the play of the held tone for IP entities that cannot play held tones locally. This is
configured by the IP Profile parameter, 'Play Held Tone'.
Interworking generation of held tone where the device generates the tone to the held party
instead of the call hold initiator. This is configured by the IP Profile parameter, 'SBC Reliable
Held Tone Source'.
To configure IP Profiles, see

Interworking SIP Via Headers

The device supports the interworking of SIP Via headers between SIP entities. For the outgoing
message sent to a SIP entity, the device can remove or retain all the Via headers received in the
incoming SIP request from the other side. Employing IP Profiles, you can configure this
interworking feature per SIP entity, using the IpProfile_ SBCKeepVIAHeaders parameter (see
Configuring IP

Interworking SIP User-Agent Headers

The device supports the interworking of SIP User-Agent headers between SIP entities. For the
outgoing message sent to a SIP entity, the device can remove or retain all the User-Agent headers
received in the incoming SIP request/response from the other side. Employing IP Profiles, you can
configure this interworking feature per SIP entity, using the IpProfile_SBCKeepUserAgentHeader
parameter (see

Interworking SIP Record-Route Headers

The device supports the interworking of SIP Record-Route headers between IP entities. For the
outgoing message sent to a SIP entity, the device can remove or retain all the Record-Route
headers received in the incoming SIP request/response from the other side. Employing IP Profiles,
you can configure this
SBCKeepRoutingHeaders parameter (see

Interworking SIP To-Header Tags in Multiple SDP Answers

The device supports the interworking of SIP To-header tags in call forking responses (i.e., multiple
SDP answers) between IP entities. The device can either use the same To-header tag value for all
SDP answers sent to the SIP entity, or send each SDP answer with its original tag. Employing IP
Profiles, you can configure this interworking feature per SIP entity, using the IpProfile_
SBCRemoteMultipleEarlyDialogs parameter (see

Interworking In-dialog SIP Contact and Record-Route Headers

The device supports the interworking of in-dialog, SIP Contact and Record-Route headers between
SIP entities. Employing IP Profiles, you can configure this interworking feature per SIP entity,
using the IpProfile_SBCRemoteRepresentationMode parameter (see
Configuring IP
Profiles).
Configuring IP
Profiles).
interworking feature per SIP
Mediant 800 Gateway & E-SBC | User's Manual
Profiles.
Configuring IP
Profiles).
Configuring IP
Profiles).
- 774 -
entity,
using the IpProfile_
Configuring IP
Profiles).

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

E-sbc

Table of Contents