Table of Contents
Advertisement
Grey Headline (continued)
Status
Searches
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.
The type of search message that is sent will depend 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:
•
For 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
request to the device asking it to accept the call. Each
message shows up as a separate search in the
history
page, but only the
Setup
message will be associated
with a particular call.
•
For H.323 searches originating from external zones, an
will appear in the
Search history
page.
•
for SIP, a single message is sent in order to place a call: this
will either be a SIP
INVITE
or a SIP OPTIONS.
Each search has an individual
Search
an individual
Call
Tag.
Overview and
Introduction
Getting started
status
D14049.05
February 2009
The
Search history
have taken place since the VCS was last restarted.
To view the
Search history
•
Status > Search history
The page displays the following information:
Start time
Search Type
Source
Destination
which sends a
Search
Found
LRQ
Actions
Filter
To limit the list of calls, enter one or more characters in the
ID; each call has
field and select Filter. Only those calls that contain (in any of the
displayed fields) the characters you entered will be shown.
To return to the full list of calls, click Reset.
System
VCS
configuration
configuration
Search history
page lists the most recent 255 searches that
page:
The date and time at which the search was
initiated.
The type of message being sent.
The alias of the endpoint that initiated the call.
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.
Indicates whether or not the search was
successful.
Click
View
to go to the
Search details
page
which lists full details of this call.
Zones and
Call
Bandwidth
neighbors
processing
control
37
TANDBERG
Search details
The
Search details
page
(Status > Search
View
for a particular search) lists full information about either
an individual search, or all searches associated with a single
call (depending on how you reached the page). The information
shown includes the subzones and zones that were searched and
any transforms that were applied to the alias being searched for.
Other information associated with the search and (if it was
successful) the resulting call can be viewed using the links in
the
Related tasks
section at the bottom of the page.
•
View all events associated with this call tag
Event Log
page, filtered to show only those events associated
with the Call Tag relating to this search.
•
View call information associated with this call tag
you to the
Call summary
page, where you can view overview
information about the call.
•
View all searches associated with this call tag
if you are viewing details of an individual search and there are
other searches associated with the same call. It takes you to
a new
Search details
page which lists full information about
all the searches associated with the call's Call Tag.
Filter
Firewall
Applications
traversal
VIDEO COMMUNICATIONS SERVER
ADMINISTRATOR GUIDE
history, then click
takes you to the
takes
will be shown
Maintenance
Appendices
Advertisement
Table of Contents
