Cisco Cisco TelePresence Video Communication Server Expressway 관리 매뉴얼
Overview and status information
Cisco VCS Administrator Guide (X7.0)
Page 43 of 488
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.
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.
n
SIP calls via the B2BUA: as the B2BUA can control the state of a call, if you disconnect the leg of the
call 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
call 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
Call status
page — you may have to
refresh the page on your browser.
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.
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 > History
) lists all the calls that are no longer active that have
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.
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).
User Policy).
Protocol
Shows whether the call used H.323, SIP, or both protocols.
Duration
Shows the length of time of the call.
Status
Shows the reason the call was terminated.
Peer
Identifies the cluster peer through which the call was made.
Type
If the
is enabled, calls routed via the B2BUA appear as 2
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.
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.
OCS/Lync server via B2BUA" zone.
Actions
Allows you to click View to go to the
page (or the
page if it is the leg
of a call routed via the B2BUA), which lists overview details of this call.