To accommodate on-going development of the Media Gateway Control Protocol (MGCP), you might want to allow traffic containing new MGCP message types. The unknown SIP message type feature enables you to configure the Juniper Networks device to accept MGCP traffic containing unknown message types in both NAT and route modes.
Before You Begin |
|---|
For background information, read Understanding the MGCP ALG. |
This feature enables you to specify how unidentified MGCP messages are handled by the Juniper Networks device. The default is to drop unknown (unsupported) messages. Unknown messages can compromise security. However, in a secure test or production environmnet, this command can be useful for resolving interoperability issues with disparate vendor equipment. Permitting unknown MGCP 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 the CLI configuration editor.
This topic covers:
In this example, you configure the device to allow unknown MGCP message types in both route and NAT modes.
- user@host# set security alg mgcp application-screen
unknown-message permit-nat-applied permit-routed