CCIE Collaboration Exam: Troubleshooting MOH on Cisco IOS SIP Gateway

Determining Call Hold Status in SIP Messages - Exam Question Answer

Prev Question Next Question

Question

A collaboration engineer is troubleshooting an MOH problem on a Cisco IOS SIP gateway in searching through a debug CCSIP massage output.

Which three parameters in the SIP massages can be used to determine if the call was placed on hold? (Choose three)

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D. E. F.

BCE.

When troubleshooting MOH (Music on Hold) problems on a Cisco IOS SIP gateway, debug CCSIP messages output can provide valuable information. To determine if the call was placed on hold, the following three parameters in the SIP messages can be used:

A. OPTIONS WITH 301 CALLHOLD: This message indicates that a 301 Moved Permanently response has been received for an OPTIONS request with Call Hold support.

B. INVITE WITH a=INACTIVE: This message indicates that the session description includes the attribute "a=inactive" in the "m=" line, indicating that the media stream is inactive.

C. INVITE WITH a=SENDONLY: This message indicates that the session description includes the attribute "a=sendonly" in the "m=" line, indicating that the endpoint is sending media but not receiving it.

Note that options D, E, and F are not correct:

D. OPTION WITH c=INACTIVE: This message indicates that the session description includes the attribute "c=inactive" in the "m=" line, indicating that the media stream is inactive. However, this does not necessarily indicate that the call was placed on hold.

E. c=IN IP4 0.0.0.0: This message indicates that the session description includes the attribute "c=IN IP4 0.0.0.0" in the "m=" line, indicating that the endpoint is not receiving media.

F. BYE WITH A = CALLHOLD: This message does not exist in the SIP protocol and is therefore not a valid parameter for determining if the call was placed on hold.