Cisco Cisco TelePresence Video Communication Server Expressway 관리 매뉴얼
Dial plan and call processing
Disconnecting calls
Disconnecting a call using the web interface
To disconnect one or more existing calls using the web interface:
1. Go to the Calls page (
Status > Calls
).
2. If you want to confirm the details of the call, including the Call Serial Number and Call Tag, click
View. Click the back button on your browser to return to the Calls page.
3. Select the box next to the calls you want to terminate and click Disconnect.
Note that if your Cisco VCS is part of a cluster you have to be logged into the peer through which the
call is associated to be able to disconnect the call.
call is associated to be able to disconnect the call.
Disconnecting a call using the CLI
To disconnect an existing call using the CLI, you must first obtain either the call ID number or the call
serial number (see
serial number (see
). Then use either one of the following commands as appropriate:
n
xCommand DisconnectCall Call: <ID number>
n
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 Cisco VCS also allows you to reference the call using the longer but unique call serial
number.
in the meantime the call has already been disconnected and the call ID assigned to a new call. For this
reason, the Cisco VCS also allows you to reference the call using the longer but unique call serial
number.
Note: when disconnecting a call, only the call with that Call Serial Number is disconnected. Other
calls with the same Call Tag but a different Call Serial Number may not be affected.
calls with the same Call Tag but a different Call Serial Number may not be affected.
Limitations when disconnecting SIP calls
Call disconnection works differently for H.323 and SIP calls due to differences in the way the
protocols work.
protocols work.
For H.323 calls, and interworked calls, the Disconnect command actually disconnects the call.
For SIP calls, the Disconnect command causes the Cisco VCS to release all resources used for the
call; the call will appear as disconnected on the Cisco VCS. SIP calls are peer-to-peer, and as the
Cisco VCS is a SIP proxy it has no authority over the endpoints. Releasing the resources on the Cisco
VCS may have the side-effect of disconnecting the SIP call, but the call signaling, media or both may
call; the call will appear as disconnected on the Cisco VCS. SIP calls are peer-to-peer, and as the
Cisco VCS is a SIP proxy it has no authority over the endpoints. Releasing the resources on the Cisco
VCS may have the side-effect of disconnecting the SIP call, but the call signaling, media or both may
Cisco VCS Administrator Guide (X6)
Page 154 of 295