Disconnecting Calls; B2Bua Calls - Cisco TelePresence Administrator's Manual

You can view full details of each call component by clicking on the Local call serial number associated
with each component. This will open the
including all call legs and sessions. It also provides further links to the
individual media channels (audio, video, data and so on) for the most relevant session for a traversal call.
If the VCS is part of a cluster and the call passes through two cluster peers, you can click on View
associated call on other cluster peer to see the details of the other leg of the call.

Disconnecting calls

Click Disconnect to disconnect the selected calls. Note that if your 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 disconnection works differently for H.323 and SIP calls due to differences in the way the protocols work:
H.323 calls, and interworked H.323 to SIP calls: the Disconnect command will actually disconnect the
n
call.
SIP to SIP calls: the Disconnect command will cause the VCS to release all resources used for the call
n
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.
SIP calls via the B2BUA: as the B2BUA can control the state of a call, if you disconnect the leg of the call
n
that is passing through the B2BUA (where the Type is B2BUA), the call will fully disconnect. Note that the
call may take a few seconds to disappear from the
on your browser.

B2BUA calls

The B2BUA calls page (Status > Calls > Calls
particular B2BUA call) provides overview information about a call routed through the B2BUA.
Calls are routed through the B2BUA if:
a media encryption policy
n
the Microsoft OCS/Lync B2BUA service
n
OCS/Lync server via B2BUA neighbor zone
Note that for Microsoft OCS/Lync B2BUA calls, you can click the Corresponding VCS call link to see
details of the leg passing through the VCS.
B2BUA call media details
The B2BUA call media
channels (audio and video) that made up the call passing through the B2BUA. For calls using the Microsoft
OCS/Lync B2BUA, this comprises legs between the VCS, the OCS/Lync server and, if applicable, the
transcoder.
Cisco VCS Administrator Guide (X7.2)
Call details
or
(any encryption setting other than Auto) has been applied to the call
is enabled and the call has been routed through the To Microsoft
page (accessed from the
page which lists full information about that component,
Call media
Call status page — you may have to refresh the page
Status > Calls > History, then click View for a
B2BUA calls page) shows information about the media
Overview and status information
page which lists the
Page 34 of 498