Grey Headline (continued)
Event Log
TANDBERG VIDEO COMMUNICATIONS SERVER ADMINISTRATOR GUIDE
| Events Logged at Level 1 |
|
|
Event | Description |
Admin Session Finish | An administrator has logged off the system. |
Admin Session Login Failure | An unsuccessful attempt has been made to log in as an administrator. This could be because either the username “admin” was not used, or an incorrect |
| password was entered (or both). |
Admin Session Start | An administrator has logged onto the system. |
Application Failed | The VCS application is out of service due to an unexpected failure. |
Application Start | The VCS has started. |
Call Answer Attempted | Further detail may be provided in the event data Detail field. |
An attempt to answer a call has been made. | |
Call Attempted | A call has been attempted. |
Call Bandwidth Changed | The bandwidth of a call has changed. |
Call Connected | A call has been connected. |
Call Disconnected | A call has been disconnected. |
Call Rejected | A call has been rejected. |
Decode Error | The Reason event parameter contains a textual representation of the H.225 additional cause code. |
A syntax error was encountered when decoding a SIP or H.323 message. | |
Eventlog Cleared | An operator cleared the event log. |
External Server Communication | Communication with an external server failed unexpectedly. The event detail data should differentiate between ‘no response’ and ‘request rejected’. |
Failure | Servers concerned are: |
| • DNS |
| • LDAP servers |
| • Neighbor Gatekeeper |
| • NTP servers |
Hardware Failure | There is an issue with the VCS hardware. If the problem persists, contact your TANDBERG support representative. |
License Limit Reached | Licensing limits for a given feature have been reached. |
The event detail field specifies the facility/limits concerned. Possible values for the detail field are:
•Non Traversal Call Limit Reached
•Traversal Call Limit Reached
Message Rejected |
| The VCS Authentication mode is set to On, and an endpoint has unsuccessfully attempted to send a message (such as a registration request) to the VCS. | ||||||||||||||||||
|
|
| This could be either because the endpoint has not supplied any authentication credentials, or because its credentials do not match those expected by the | |||||||||||||||||
|
|
| VCS. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Introduction | Getting Started | Overview and |
| System |
| VCS |
| Zones and |
| Call |
| Bandwidth |
| Firewall |
| Maintenance |
| Appendices |
| |
Status |
|
| Configuration |
| Configuration |
| Neighbors |
| Processing |
| Control |
| Traversal |
|
|
| ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
| |||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
D14049.03 |
|
|
|
|
|
|
|
| 44 |
|
|
|
|
|
|
|
|
| ||
MAY 2008 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |||
