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: |
|
Index |
Source Username Pattern |
Destination Username Pattern |
Destination Host |
Source IP Group |
|---|---|---|---|---|
|
0 |
333 |
- |
- |
1 |
|
1 |
1111 |
2000 |
10.10.10.10 |
2 |
| 2. | In the IP Groups table, add the following IP Groups: |
|
Index |
Source URI Input |
Destination URI Input |
|---|---|---|
|
1 |
- |
- |
|
2 |
P-Called-Party-ID |
Route |
In the example, a match exists only for Classification Rule #1. This is because the source (1111) and destination (2000) username prefixes match those in the INVITE's P-Called-Party-ID header (i..e., "<sip:1111@10.33.38.1>") and Route header (i.e., "<sip:2000@10.10.10.10.10>"), respectively. These SIP headers were determined in IP Group 2.