Installation guide

12-33
Device Manager Guide, Cisco ACE 4700 Series Application Control Engine Appliance
OL-26645-02
Chapter 12 Configuring Traffic Policies
Setting Match Conditions for Class Maps
Step 6 Do the following:
• Click Deploy Now to deploy this configuration on the ACE and to return to the Match Condition
table.
Note If you click Deploy Now, the ACE drops the traffic and then restarts it, even if you have not
made changes. If you have not altered existing match conditions, click Cancel instead of
Deploy Now to ensure uninterrupted traffic.
• Click Cancel to exit this procedure without saving your entries and to return to the Match Condition
table.
• Click Next to configure another match condition for this class map.
Related Topics
• Configuring Virtual Context Class Maps, page 12-8
• Configuring Virtual Context Policy Maps, page 12-34
Third Party A third party who is authorized to register other users on their behalf is used to establish a match
condition.
In the Third Party Registration Entities field, enter a regular expression that identifies a privileged
user authorized for third-party registrations for this match condition. Valid entries are unquoted
text strings with no spaces and a maximum of 255 alphanumeric characters. The ACE supports
regular expressions for matching string expressions. Table 12-33 lists the supported characters that
you can use for matching string expressions.
URI Length A SIP URI or user identifier is used to establish a match condition.
1. In the URI Type field, select the type of URI to use:
– SIP URI—The calling party URI is used for this match condition.
– Tel URI—A telephone number is used for this match condition.
2. In the URI Operator field, confirm that Greater Than is selected.
3. In the URI Length field, enter the maximum length of the SIP URI or Tel URI in bytes. Valid
entries are integers from 0 to 254 bytes.
Table 12-14 Layer 7 SIP Deep Packet Inspection Class Map Match Conditions (continued)
Match Condition Description