Sccp Inspection Configuration Considerations; Creating An Sccp Parameter Map - Cisco 4700M Configuration Manual

Chapter 3 Configuring Application Protocol Inspection

SCCP Inspection Configuration Considerations

Creating an SCCP Parameter Map

OL-16202-01
Be aware of the following considerations when you configure SCCP inspection
on the ACE:
If the ACE resides between the Cisco CallManager (CCM) and the IP phones,
•
then explicit security ACLs are required to permit the TFTP traffic between
the CCM and the phones because the ACE does not support TFTP fixup.
If the IP address of an internal CCM is configured for NAT or PAT to a
•
different IP address or port, registrations for external Cisco IP phones fail
because the ACE does not support NAT or PAT of the file content transferred
over TFTP. Although the ACE supports NAT of TFTP messages, it does not
open a secure port for TFTP. In addition, the ACE cannot translate the CCM
IP address and port that are embedded in the Cisco IP phone configuration
files. The configuration files are transferred using TFTP during phone
registration.
You can configure SCCP packet inspection by using the parameter-map type
skinny command in configuration mode. The syntax of this command is as
follows:
parameter-map type skinny name
The name argument is the identifier assigned to the parameter map. Enter an
unquoted text string with no spaces and a maximum of 32 alphanumeric
characters.
For example, enter:
host1/Admin(config)# parameter-map type skinny SCCP_PARAMMAP
host1/Admin(config-parammap-skinny)#
To remove the parameter map from the configuration, enter:
host1/Admin(config)# no parameter-map type skinny SCCP_PARAMMAP
Cisco 4700 Series Application Control Engine Appliance Security Configuration Guide
Configuring an SCCP Parameter Map
3-113