Symptom

When CUBE is configured with outbound-proxy dns: globally and session server-group on the outbound dial-peer, CUBE fails to respond to "SIP 404 Not found" returned by the proxy. This causes a call loop on the CUBE which results in 100% CPU usage until the call times out or is ended. Calls may not be processed by the CUBE while facing this problem. The CLI of the device will be unresponsive while the call is still processed by the CUBE. CUBE could take up to 30 minutes to recover depending on normal CPU usage and call volume. Multiple calls that hit the outbound dial-peer facing this problem will result in longer recovery time. The CUBE may recover if receiving a CANCEL from the calling party.

Conditions

CUBE is configured with outbound-proxy dns: globally and session server-group on the outbound dial-peer.

Workaround

Configure the outbound dial-peer with no voice-class sip outbound-proxy. Do not use outbound-proxy dns: on a dial-peer configured with session server-group.

Further Problem Description