Symptoms

- Loading configuration will Fail if the SIP session 'Do Not Connect Back' is disabled. - Make sure while configuring the SIP session with IPS profile 'Do Not Connect Back' must be enabled otherwise the configuration will not be loaded.

Impact

- If you do not enable 'Do Not Connect Back' in the SIP Profile, the configuration will not be loaded while configuring and upgrading.

Conditions

The dependency 'Do Not Connect Back' is applicable if the Protocol Inspection has a SIP profile enabled.

Workaround

Enable 'Do Not Connect Back' option in the SIP profile

Fix Information

Added MCP validation for Do Not Connect back configured with Protocol-Inspection.

Behavior Change