Table of Contents
Advertisement
Grey Headline (continued)
Status
Message details field
tvcs
For all messages logged from the
process, the
details
field, which contains the body of the message,
consists of a number of human-readable
separated by a space.
Field
Description
Event
The event which caused the log message to be generated. See
list of all events that are logged by the VCS, and the level at which they are logged.
User
The username that was entered when a login attempt was made.
ipaddr
The source IP address of the user who has logged in.
Protocol
Specifies which protocol was used for the communication. Valid values are:
•
TCP
•
UDP
•
TLS.
Reason
Textual string containing any reason information associated with the event.
Service
Specifies which protocol was used for the communication. Will be one of:
•
H323
•
SIP
•
H.225
•
H.245
•
LDAP
•
Q.931
•
NeighbourGatekeeper
•
Clustering
•
ConferenceFactory.
Message Type
Specifies the type of the message.
ResponseCode
SIP response code or, for H.323 and interworked calls, a SIP equivalent response
code.
Src-ip
Specifies the source IP address (the IP address of the device attempting to establish
communications). This can be an IPv4 address or an IPv6 address.
Dst-ip
Specifies the destination IP address (the IP address of the destination for a
communication attempt).
The destination IP is recorded in the same format as Src-ip.
Dst-port
Specifies the destination port: the IP port of the destination for a communication
attempt.
Overview and
Introduction
Getting started
status
D14049.05
February 2009
The first field within the
Event
and the last field is always Level.
message _
The table below shows all the possible fields within the
message _ details
name=value
pairs,
appear, along with a description of each.
Events and Levels
System
VCS
configuration
configuration
Event Log
message _ details
field is always
field, in the order that they would normally
Field
Description
Src-port
for a
Specifies the source port: the IP port of the device attempting to establish
communications.
Src-Alias
If present, the first H.323 Alias associated with the originator of the message.
If present, the first E.164 Alias associated with the originator of the message.
Dst-Alias
If present, the first H.323 Alias associated with the recipient of the message.
If present, the first E.164 Alias associated with the recipient of the message.
Detail
Descriptive detail of the Event.
Auth
Whether the call attempt has been authenticated successfully.
Method
SIP method (INVITE, BYE, UPDATE, REGISTER, SUBSCRIBE, etc).
Contact
Contact: header from REGISTER.
AOR
Address of record.
Call-Id
The Call-ID header field uniquely identifies a particular invitation or all registrations of a
particular client.
Call-Serial-
The VCS-local Call Serial Number that is common to all protocol messages for a
Number
particular call.
Tag
The Tag is common to all searches and protocol messages across a VCS network for
all forks of a call.
To
•
for REGISTER requests: the AOR for the REGISTER request
•
for INVITEs: the original alias that was dialed
•
for all other SIP messages: the AOR of the destination.
RequestURI
The SIP or SIPS URI indicating the user or service to which this request is being
addressed.
NumBytes
The number of bytes sent/received in the message.
Duration
Request/granted registration expiry duration.
Time
A full UTC timestamp in YYYY/MM/DD-HH:MM:SS format. Using this format permits
simple ASCII text sorting/ordering to naturally sort by time. This is included due to the
limitations of standard syslog timestamps.
Level
The level of the event as defined in
Zones and
Call
Bandwidth
neighbors
processing
control
44
TANDBERG
VIDEO COMMUNICATIONS SERVER
In addition to the events described below, a
syslog.info
event containing the string
logged after each hour of inactivity to provide confirmation
that logging is still active.
Log
Levels.
Firewall
Applications
Maintenance
traversal
ADMINISTRATOR GUIDE
MARK
will be
Appendices
Advertisement
Table of Contents
