300-835 · Question #63
An administrator must test a Cisco collaboration room device. Drag and drop the code snippets from the bottom onto the blanks in the code to perform a test call using the xAPI. Some options may be…
Note: Missing Code Snippets The Options: {} field in your question is empty - the code snippets that should appear in the drag-and-drop exercise were not included. I'll explain the concept and the typical correct procedure based on xAPI knowledge, so you're prepared regardless…
Question
Explanation
Note: Missing Code Snippets
The Options: {} field in your question is empty - the code snippets that should appear in the drag-and-drop exercise were not included. I'll explain the concept and the typical correct procedure based on xAPI knowledge, so you're prepared regardless.
Overall Goal
The Cisco xAPI (Collaboration Endpoint API) is the programmatic interface for controlling Cisco room devices (Webex Room Kit, Codec Pro, DX, SX series, etc.). A test call verifies that a device can successfully place outbound calls - confirming network connectivity, dial plan, codec function, and SIP/H.323 registration.
Using xAPI (rather than the UI) is the administrator's tool for automation, scripting, and remote diagnostics.
Typical xAPI Test Call Structure
A test call via xAPI (over SSH or HTTP) follows this pattern:
xCommand Dial Number: <destination> Protocol: <SIP|H323> CallRate: <kbps>
Step-by-Step Breakdown
1. Access the xAPI interface
Connect to the device via:
- SSH (port 22) - most common for CLI access
- HTTPS + REST - for HTTP-based xAPI
- Serial console - for physical access
Why necessary: You must have an authenticated session before any command is accepted. Skipping this means no command reaches the device.
2. Issue the xCommand Dial command
xCommand Dial Number: "[email protected]"
Why necessary: xCommand Dial is the specific API command that instructs the endpoint to place a call. Other xCommand namespaces (like xCommand Audio) do different things and won't initiate a call.
3. Specify Protocol:
Protocol: SIP
Options: SIP, H323, Spark (Webex)
Why necessary: The device must know which signaling protocol to use. A mismatch with the registered protocol causes an immediate call failure. If omitted, the device uses its default, which may not be what you intend.
4. Specify CallRate:
CallRate: 1920
(Value in kbps, e.g., 384, 768, 1920, 6000)
Why necessary: Defines the maximum bandwidth for the call. Too high a value on a constrained link causes poor quality; too low may be rejected by the far end.
5. Verify the response
A successful dial returns:
*r DialResult (status=OK):
*r DialResult CallId: 1
A failure returns a status of Error with a reason code.
Why necessary: The command being accepted doesn't guarantee the call connected - you must check the result to confirm success.
What Goes Wrong If Steps Are Skipped
| Skipped Step | Consequence |
|---|---|
| Authentication | Commands rejected with 401 Unauthorized |
Protocol: parameter | Wrong protocol used; call may fail silently |
CallRate: parameter | Default used; may not match network policy |
| Checking the result | You assume success when the call may have failed |
Memory Tip
Think of the xAPI dial command like making a phone call:
"Dial the Number, pick a Protocol (the 'language'), set the CallRate (the 'quality'), then check if it rang."
xCommand Dial Number: Protocol: CallRate: - three required parameters, one command.
If you can share the actual code snippet options from the exam, I can give you the exact answer with the correct placement for each blank.
Topics
Community Discussion
No community discussion yet for this question.