Refer to the exhibit. An administrator has configured a SIP trunk between two Cisco UCM clusters. For calls that should use the trunk, the calls fail with a fast busy. The administrator checks the Cis

Question

Options

• AThe administrator must associate the route pattern with a calling search space the device can dial.
• BThe administrator needs to enable OPTIONS pings on the SIP trunks for both clusters.
• CThe administrator must allow connectivity so that TCP connections do not fail between the nodes.
• DThe administrator needs to disable OPTIONS pings on the SIP trunks for both clusters.

• A
  3% (1)
• B
  11% (4)
• C
  78% (29)
• D
  8% (3)

Explanation

The SDL trace shows the calling cluster never sends an INVITE, even though all nodes are powered on and CallManager service is running. This points to a network-layer problem preventing the SIP trunk from establishing TCP connections between the two clusters (e.g., a firewall blocking the SIP TCP port). Without a successful TCP connection, the trunk is effectively down and UCM will not attempt to send an INVITE. Restoring TCP connectivity between the cluster nodes allows the SIP trunk to come in-service and pass calls. Options A (calling search space) and B/D (OPTIONS ping) would not cause the calling cluster to silently drop the INVITE without ever attempting to send it.

No community discussion yet for this question.