AudioCodes Mediant 800B - Classification Based on URI of Selected Header Example

User's Manual 708 Document #: LTRT-10632
Mediant 800B Gateway & E-SBC
Parameter Description
Source IP Group
src-ip-group-name
[Classification_SrcIPGroupName]
Assigns an IP Group to the matched incoming SIP dialog.
By default, no value is defined.
To configure IP Groups, see 'Configuring IP Groups' on
page 365.
Note: The IP Group must be associated with the assigned
SRD (see the 'SRD' parameter in the table).
IP Profile
ip-profile-id
[Classification_IpProfileName]
Assigns an IP Profile to the matched incoming SIP dialog.
The assi
gned IP Profile overrides the IP Profile assigned to
the IP Group (in the IP Groups table) to which the SIP
dialog is classified. 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).
34.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