Classification Based On Uri Of Selected Header Example - AudioCodes Mediant 4000 SBC User Manual

Hide thumbs Also See for Mediant 4000 SBC:
Table of Contents

Advertisement

Parameter
[Classification_IpProfileName]

24.1.1 Classification Based on URI of Selected Header Example

The following example describes how to configure classification of incoming calls to IP
Groups, based on source URI in a specific SIP header. The example assumes the
following incoming INVITE message:
INVITE sip:8000@10.33.4.226 SIP/2.0
Via: SIP/2.0/UDP 10.33.4.226;branch=z9hG4bKVEBTDAHSUYRTEXEDEGJY
From: <sip:100@10.33.4.226>;tag=YSQQKXXREVDPYPTNFMWG
To: <sip:8000@10.33.4.226>
Call-ID: FKPNOYRNKROIMEGBSSKS@10.33.4.226
CSeq: 1 INVITE
Contact: <sip:100@10.33.4.226>
Route: <sip:2000@10.10.10.10.10>,<sip:300@10.10.10.30>
Supported: em,100rel,timer,replaces
P-Called-Party-ID: <sip:1111@10.33.38.1>
User-Agent: Sip Message Generator V1.0.0.5
Content-Length: 0
1.
In the Classification table, add the following classification rules:
Source Username
Index
Prefix
0
333
1
1111
2.
In the IP Groups table, add the following IP Groups:
Index
1
2
User's Manual
Therefore, assigning an IP Profile during classification allows you to
assign different IP Profiles to specific users (calls) that belong to the
same IP Group (User or Server type).
For example, you can configure two Classification rules to classify
incoming calls to the same IP Group. However, one Classification
rule is a regular rule that doesn't specify any IP Profile (IP Profile
assigned to IP Group is used), while the second rule is configured
with an additional matching characteristic for the source hostname
prefix (e.g., "abcd.com") and with an additional action that assigns a
different IP Profile.
By default, no value is defined.
Note: For User-type IP Groups, if a user is already registered with
the device (from a previous, initial classification process), the device
classifies subsequent INVITE requests from the user according to
the device's users database instead of the Classification table. In
such a scenario, the same IP Profile that was previously assigned to
the user by the Classification table is also used (in other words, the
device's users database stores the associated IP Profile).
Destination
Username Prefix
-
2000
Source URI Input
-
P-Called-Party-ID
Description
Destination Host
-
10.10.10.10
Destination URI Input
462
Mediant 4000 SBC
Source IP Group
1
2
-
Route
Document #: LTRT-41729

Advertisement

Table of Contents
loading

Table of Contents