Call History - Cisco TelePresence Video Communication Server Administrator's Manual

Field Description
Bandwidth Shows the amount of bandwidth assigned to the call by the VCS. This may be different
allocated to the amount 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.
Actions Click View to go to the
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
n
the call.
SIP to SIP calls: the Disconnect command will cause the VCS to release all resources used for the
n
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.
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.

Call history

The Call history page (Status > Calls >
taken place since the VCS was last restarted. If the VCS is part of a cluster, all calls that have taken
place through any VCS in the cluster are shown.
The following information is displayed:
Field Description
Start time The date and time at which 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).
Protocol Shows whether the call used H.323, SIP, or both protocols.
Cisco VCS Administrator Guide (X6.1)
Call summary page, which lists further details of this call.
History) lists all the calls that are no longer active that have
Overview and status information
Page 33 of 401