SDP Compliance Enforcement

You can configure the ESBC to enforce SDP compliance on incoming messages and reject non-compliant messages and change the non-compliant SDP in ensuing messages. By default, the ESBC forwards response message even if the Content-Length is greater than the SDP size and the SDP does not have mandatory parameters. You enable the sip-strict-compliance option when the ESBC is operating in environments where it is expected to monitor and validate these aspects of SDP.

When you enable the sip-strict-compliance option in the sip-config, the ESBC:

• Ignores/drops any response message if the SDP Content-Length header value is greater than the SDP size. The system also increments the "Invalid Responses" statistic.
• Forwards any response message without any SDP if the message does not include mandatory SDP parameters. Mandatory parameters include:
  • version
  • origin
  • session-name
  • connection
  • timer

  The ESBC provides an "SDP Stripped Responses" statistic in the sip-errors HDR group to track SDP stripped responses system-wide. Enable this HDR group to obtain statistics on SDP responses the ESBC has removed because the original message violated the mandatory SDP parameter requirements.