To disconnect an existing call using the CLI, you must first obtain either the call ID number or the
call serial number. Then use either one of the following commands as appropriate:

xCommand DisconnectCall Call: <ID number

•

xCommand DisconnectCall CallSerialNumber: <serial number

•

While it is quicker to use the call ID number to reference the call to be disconnected, there is a risk
that in the meantime the call has already been disconnected and the call ID assigned to a new call.
For this reason, the VCS also allows you to reference the call using the longer but unique call serial
number.

Disconnecting a Call via the CLI

The call disconnection API works differently for H.323 and SIP calls due to differences in the way
the protocols work.
For H.323 calls, and interworked calls, the

Disconnect

command will actually disconnect the call.

For SIP calls, the

Disconnect

command will cause the VCS to release all resources used for the

call and the call will appear on the system as disconnected. However, SIP calls are peer-to-peer
and as a SIP proxy the VCS has no authority over the endpoints. Although releasing the resources
may have the side-effect of disconnecting the SIP call, it is also possible that the call signaling,
media or both may stay up (depending on the type of call being made). The call will not actually
disconnect until the SIP endpoints involved have also cleared their resources.

Issues when Disconnecting SIP Calls

Endpoints that support

RFC 4028 [14]

have a call refresh timer which should cause them to

clear the resources of any hung SIP calls after a certain period of time. This includes all
TANDBERG endpoints.

Disconnect

Check the box next to the call(s) you wish to terminate and select

Disconnect

Advertising

Popular Brands

Popular manuals