EasyManuals Logo
Home>AudioCodes>Gateway>Mediant 3000

AudioCodes Mediant 3000 User Manual

AudioCodes Mediant 3000
1070 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #621 background imageLoading...
Page #621 background image
Version 7.0 621 Mediant 3000
User's Manual 34. SBC Manipulations
34 SBC Manipulations
This section describes the configuration of the manipulation rules for the SBC application.
Note: For additional manipulation features, see the following:
''Configuring SIP Message Policy Rules''.
''Configuring SIP Message Manipulation'' on page 371.
The device supports SIP URI user part (source and destination) manipulations for inbound
and outbound routing. These manipulations can be applied to a source IP group, source
and destination host and user prefixes, and/or user-defined SIP request (e.g., INVITE,
OPTIONS, SUBSCRIBE, and/or REGISTER). Since outbound manipulations are
performed after routing, the outbound manipulation rule matching can also be done by
destination IP Group. Manipulated destination user and host are performed on the following
SIP headers: Request-URI, To, and Remote-Party-ID (if exists). Manipulated source user
and host are performed on the following SIP headers: From, P-Asserted (if exists), P-
Preferred (if exists), and Remote-Party-ID (if exists).
Figure 34-1: SIP URI Manipulation in IP-to-IP Routing
You can also restrict source user identity in outgoing SIP dialogs in the Outbound
Manipulation table (using the column PrivacyRestrictionMode). The device identifies an
incoming user as restricted if one of the following exists:
From header user is 'anonymous'.
P-Asserted-Identity and Privacy headers contain the value 'id'.
All restriction logic is done after the user number has been manipulated.
Host name (source and destination) manipulations are simply host name substitutions with
the names defined for the source and destination IP Groups respectively (if any, in the IP
Group table).
Below is an example of a call flow and consequent SIP URI manipulations:
Incoming INVITE from LAN:
INVITE sip:1000@10.2.2.3;user=phone;x=y;z=a SIP/2.0
Via: SIP/2.0/UDP 10.2.2.6;branch=z9hGLLLLLan
From:<sip:7000@10.2.2.6;user=phone;x=y;z=a>;tag=OlLAN;paramer1
=abe
To: <sip:1000@10.2.2.3;user=phone>
Call-ID: USELLLAN@10.2.2.3

Table of Contents

Other manuals for AudioCodes Mediant 3000

Questions and Answers:

Question and Answer IconNeed help?

Do you have a question about the AudioCodes Mediant 3000 and is the answer not in the manual?

AudioCodes Mediant 3000 Specifications

General IconGeneral
BrandAudioCodes
ModelMediant 3000
CategoryGateway
LanguageEnglish

Related product manuals