25-9
Cisco Security Appliance Command Line Configuration Guide
OL-10088-01
Chapter 25 Configuring Application Layer Protocol Inspection
CTIQBE Inspection
Step 6 To activate the policy map on one or more interfaces, enter the following command:
hostname(config)# service-policy policymap_name {global | interface interface_name}
Where global applies the policy map to all interfaces, and interface applies the policy to one interface.
By default, the default policy map, “global_policy,” is applied globally. Only one global policy is
allowed. You can override the global policy on an interface by applying a service policy to that interface.
You can only apply one policy map to each interface.
CTIQBE Inspection
This section describes CTIQBE application inspection. This section includes the following topics:
• CTIQBE Inspection Overview, page 25-9
• Limitations and Restrictions, page 25-10
• Verifying and Monitoring CTIQBE Inspection, page 25-10
CTIQBE Inspection Overview
CTIQBE protocol inspection supports NAT, PAT, and bidirectional NAT. This enables Cisco IP
SoftPhone and other Cisco TAPI/JTAPI applications to work successfully with Cisco CallManager for
call setup across the security appliance.
TAPI and JTAPI are used by many Cisco VoIP applications. CTIQBE is used by Cisco TSP to
communicate with Cisco CallManager.
skinny [map_name] If you added a Skinny inspection policy map according to
“Configuring a Skinny (SCCP) Inspection Policy Map for
Additional Inspection Control” section on page 25-69,
identify the map name in this command.
snmp [map_name] If you added an SNMP inspection policy map according to
“SNMP Inspection” section on page 25-72, identify the map
name in this command.
sqlnet —
sunrpc The default class map includes UDP port 111; if you want to
enable Sun RPC inspection for TCP port 111, you need to
create a new class map that matches TCP port 111, add the
class to the policy, and then apply the inspect sunrpc
command to that class.
tftp —
xdmcp —
Table 25-2 Protocol Keywords
Keywords Notes