To accommodate on-going development of the Skinny Client Control Protocol (SCCP), you might want to allow traffic containing new SCCP message types. The unknown SCCP message type feature enables you to configure the J-series device to accept SCCP traffic containing unknown message types in both NAT and route modes.
Before You Begin |
|---|
For background information, read Understanding the SCCP ALG. |
This feature enables you to specify how unidentified SCCP messages are handled by the J-series device. The default is to drop unknown (unsupported) messages. We do not recommend permitting unknown messages because they can compromise security and is not recommended. However, in a secure test or production environment, this command can be useful for resolving interoperability issues with disparate vendor equipment. Permitting unknown SCCP messages can help you get your network operational so that you can later analyze your VoIP traffic to determine why some messages were being dropped.
Note that this command applies only to received packets identified as supported VoIP packets. If a packet cannot be identified, it is always dropped. If a packet is identified as a supported protocol and you have configured the device to permit unknown message types, the message is forwarded without processing.
To allow unknown message types, use either the J-Web or CLI configuration editor.
This topic covers:
In this example, you configure the device to allow unknown SCCP message types in both route and NAT modes.
- user@host# set security alg sccp application-screen
unknown-message permit-nat-applied permit-routed