AudioCodes Mediant 800 User Manual page 831

CHAPTER 34 Routing SBC
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
0
1
2. In the IP Groups table, add the following IP Groups:
Index
1
2
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.
Destination Username
Pattern
333
1111
Source URI Input
-
P-Called-Party-ID
- 791 -
Mediant 800 Gateway & E-SBC | User's Manual
Destination
Pattern
-
2000 10.10.10.10
Destination URI Input
Source IP
Host Group
- 1
2
-
Route