TANDBERG Gatekeeper/Border Controller API D14172.01 User Manual page 13

Tandberg gatekeeper/border controller api user guide
Table of Contents

Advertisement

Example 1.13
The Dial command in the above example may return the following response structure:
<Command>
<DialResult item="1" status="OK">
<callSrc item="1">alice@example.com</callSrc>
<callDst item="1">bob@example.com</callDst>
<Bandwidth item="1">384</Bandwidth>
<CallSerialNumber item="1">1</CallSerialNumber>
<EncryptionMode item="1">Auto</EncryptionMode>
<EncryptionType item="1">Auto</EncryptionType>
</DialResult>
</Command>
The response structure for the Dial command, DialResult, states that the command was accepted
by the system. In addition to stating that the command was accepted, the Dial command returns the
element CallSerialNumber. This lets the user identify/trace the call in the Status documents
(status.xml and history.xml).
Example 1.14
Below is an example of the Dial command not being accepted by the system because the same alias
has been specified for both the callSrc and callDst:
<Command>
<DialResult item="1" status="Error">
<Cause item="1">89</Cause >
<Description item="1"> callSrc and callDst must have different
aliases</Description>
</DialResult>
</Command>
D14172.01
TANDBERG Gatekeeper/Border Controller API User Guide
page 13 of 84

Advertisement

Table of Contents
loading

This manual is also suitable for:

Gatekeeper/border controller

Table of Contents