![](/images/new-backgrounds/1267248/26724895x1.webp)
Grey Headline (continued)
Event Log
TANDBERG VIDEO COMMUNICATIONS SERVER ADMINISTRATOR GUIDE
Interpreting the Event Log
Message Details Field
For all messages logged from the tvcs process, the message _ details field, which contains the body of the message, consists of a number of
The first field within the message _ details field is always Event and the last field is always Level.
The table below shows all the possible fields within the message _ details field, in the order that they would normally appear, along with a description of each.
In addition to the events described below, a
syslog.info event containing the string MARK will be
logged after each hour of inactivity to provide confirmation that logging is still active.
Field | Description |
Event | The event which caused the log message to be generated. See Events and Levels for a |
| 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. |
| 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. |
| 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 |
Specifies the destination port: the IP port of the destination for a communication | |
| attempt. |
Field | Description |
Specifies the source port: the IP port of the device attempting to establish | |
| communications. |
| 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. |
| 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. |
| The |
| particular client. |
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. |
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 |
| 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 Log Levels. |
Introduction | Getting Started | Overview and | System |
| VCS |
| Zones and |
| Call |
| Bandwidth |
| Firewall |
| Applications |
| Maintenance |
| Appendices |
Status | Configuration |
| Configuration |
| Neighbors |
| Processing |
| Control |
| Traversal |
|
|
| |||||
|
|
|
|
|
|
|
|
|
|
|
|
| |||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
D14049.04 |
|
|
|
|
|
| 48 |
|
|
|
|
|
|
|
|
|
| ||
JULY 2008 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|