Cisco Cisco TelePresence Video Communication Server Expressway 관리 매뉴얼
■
is enabled and the call has been routed through the To Microsoft Lync
server via B2BUA neighbor zone
Note that for Microsoft Lync B2BUA calls, you can click the Corresponding VCS call link to see details of the leg
passing through the VCS.
passing through the VCS.
Viewing B2BUA Call Media Details
page by clicking View media statistics for this call)
shows information about the media channels (audio and video) that made up the call passing through the B2BUA. For
calls using the Microsoft Lync B2BUA, this comprises legs between the VCS, the Lync server and, if applicable, the
transcoder.
calls using the Microsoft Lync B2BUA, this comprises legs between the VCS, the Lync server and, if applicable, the
transcoder.
Search History
The Search history page (Status > Search history) lists the most recent 255 searches that have taken place since
the VCS was last restarted.
the VCS was last restarted.
About searches
Before a call can be placed, the endpoint being called must be located. The VCS sends and receives a series of
messages during its attempt to locate the endpoint being called; these messages are each known as searches. An
individual call can have one or more searches associated with it, and these searches can be of different types.
messages during its attempt to locate the endpoint being called; these messages are each known as searches. An
individual call can have one or more searches associated with it, and these searches can be of different types.
The type of search message that is sent depends on whether the call is for SIP or H.323, and whether the call request
was received locally or from an external zone, as follows:
was received locally or from an external zone, as follows:
■
H.323 calls that are placed locally: two messages are sent - the first is an ARQ which locates the device being
called, and the second is the call Setup which sends a request to the device asking it to accept the call. Each
message shows up as a separate search in the Search history page, but only the Setup message is
associated with a particular call.
called, and the second is the call Setup which sends a request to the device asking it to accept the call. Each
message shows up as a separate search in the Search history page, but only the Setup message is
associated with a particular call.
■
H.323 searches originating from external zones: an LRQ will appear in the Search history page.
■
SIP: a single message is sent in order to place a call: this is either a SIP INVITE or a SIP OPTIONS.
Note that an individual call can have one or more searches associated with it, and these searches can be of different
types. Each search has an individual Search ID; each call has an individual Call Tag (see
types. Each search has an individual Search ID; each call has an individual Call Tag (see
).
The VCS supports up to 500 concurrent searches.
Search history list
The search history summary list shows the following information:
Field
Description
Start time
The date and time at which the search was initiated.
Search
type
type
The type of message being sent.
Source
The alias of the endpoint that initiated the call.
Destination The alias that was dialed from the endpoint. This may be different from the alias to which the call was
actually placed, as the original alias may have been transformed either locally or before the neighbor
was queried.
was queried.
Status
Indicates whether or not the search was successful.
Actions
328
Cisco TelePresence Video Communication Server Administrator Guide