To accommodate on-going development of the Session Initiation Protocol (SIP), you might want to allow traffic containing new SIP message types. The unknown SIP message type feature enables you to configure the device to accept SIP traffic containing unknown message types in both NAT and route modes.
Before You Begin |
|---|
For background information, read |
This feature enables you to specify how unidentified SIP messages are handled by the device. The default is to drop unknown (unsupported) messages. We do not recommend permitting unknown messages because they can compromise security. However, in a secure test or production environment, this command can be useful for resolving interoperability issues with disparate vendor equipment. Permitting unknown SIP messages can help you get your network operational. so 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 messages, use either the J-Web or CLI configuration editor.
This topic covers:
In this example, you configure the device to allow unknown message types in SIP traffic in both route and NAT modes.
