Call Status; Current Calls - Cisco TelePresence Administrator's Manual

Call status

Current calls

The Call status page (Status > Calls >
registered with the VCS, or that are passing through the VCS. If the VCS is part of a cluster, all calls taking
place through any VCS in the cluster are shown.
The following information is displayed:
Field Description
Start time The date and time when the call was placed.
Source The alias of the device that placed the call.
Destination The alias dialed from the device. This may be different from the alias to which the call was placed,
which may have been transformed (due to pre-search transforms, zone transforms or User Policy).
Bandwidth Shows the amount of bandwidth assigned to the call by the VCS. This may be different to the amount
allocated of bandwidth originally requested by the endpoint that placed the call.
Route The subzone or zone from which the call was received and the subzone or zone to which the call
was placed. To see the complete route taken by the call within the VCS, including intermediary
subzones, click View.
Protocol Shows whether the call used H.323, SIP, or both protocols.
Peer Identifies the cluster peer through which the call is being made.
Type If the Microsoft OCS/Lync B2BUA service
separate calls, and are distinguished by their call type:
B2BUA: this entry shows details for the leg of the call between the B2BUA and the OCS/Lync
device.
VCS: this entry shows details for the leg of the call routed by the VCS through the "To Microsoft
OCS/Lync server via B2BUA" zone.
Actions Allows you to click View to go to the
call routed via the B2BUA), which lists overview details of this call.
Filtering the list
To limit the list of calls, enter one or more characters in the Filter field and click Filter. Only those calls that
contain (in any of the displayed fields) the characters you entered are shown.
To return to the full list of calls, click Reset.
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.
Cisco VCS Administrator Guide (X7.1)
Calls) lists all the calls currently taking place to or from devices
is enabled, calls routed via the B2BUA appear as 2
Call summary page (or the
Overview and status information
B2BUA calls page if it is the leg of a
Page 33 of 479