350-801 · Question #320
An administrator uses the Cisco Unified Real-Time Monitoring Tool to investigate recent calls on a Cisco UCM cluster. The SIP trace for an on-net. direct-media call shows two 180 Ringing and two 11…
The correct answer is D. The destination phone signals back to the Cisco UCM that it is ringing, and the Cisco UCM. In a Cisco UCM direct-media call, UCM acts as a back-to-back user agent (B2BUA) for signaling even though media flows directly between endpoints. This means every SIP message travels in two legs: one leg between the destination phone and UCM, and one leg between UCM and the…
Question
An administrator uses the Cisco Unified Real-Time Monitoring Tool to investigate recent calls on a Cisco UCM cluster. The SIP trace for an on-net. direct-media call shows two 180 Ringing and two 11 BYE messages. Why are there multiples of each message type in the trace?
Options
- AThe source phone sends a 180 Ringing signal to the Cisco UCM, which sends a 180 Ringing
- BThe source phone must signal to the destination phone that it is ringing, and the destination
- CThe calls have an MTP in the call path due to different codec support. The calls are
- DThe destination phone signals back to the Cisco UCM that it is ringing, and the Cisco UCM
How the community answered
(40 responses)- A3% (1)
- B8% (3)
- C5% (2)
- D85% (34)
Explanation
In a Cisco UCM direct-media call, UCM acts as a back-to-back user agent (B2BUA) for signaling even though media flows directly between endpoints. This means every SIP message travels in two legs: one leg between the destination phone and UCM, and one leg between UCM and the source phone. When the destination phone rings, it sends a '180 Ringing' to UCM, and UCM then sends its own '180 Ringing' to the source phone - producing two 180 messages in the trace. The same applies to BYE: the terminating side sends a BYE to UCM, and UCM sends a BYE to the other party. This hairpin signaling is normal UCM behavior regardless of direct media.
Topics
Community Discussion
No community discussion yet for this question.