Grey Headline (continued)
Event Log
TANDBERG VIDEO COMMUNICATIONS SERVER ADMINISTRATOR GUIDE
Events and Levels
Event |
| Description |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Level | ||
Message Received | An incoming RAS message has been received. |
|
|
|
|
|
|
|
|
|
|
|
| 2 | |||||||
Message Received | An incoming RAS NSM Keepalive, H.225 or H.245 message has been received. |
|
|
|
|
|
|
|
| 3 | |||||||||||
Message Received | (SIP) An incoming message has been received. |
|
|
|
|
|
|
|
|
|
|
|
| 4 | |||||||
Message Rejected | This could be for one of two reasons: |
|
|
|
|
|
|
|
|
|
|
|
| 1 | |||||||
|
|
| 1. 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. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |||
|
|
| 2. Clustering is enabled but bandwidth across the cluster has not been configured identically, and the VCS has received a message relating to an unknown | ||||||||||||||||||
|
|
| Peer, Link, Pipe, Subzone or Zone. Use TMS to synchronize configuration across Peers. |
|
|
|
|
|
|
| |||||||||||
Message Sent |
| An outgoing RAS message has been sent. |
|
|
|
|
|
|
|
|
|
|
|
| 2 | ||||||
Message Sent |
| An outgoing RAS NSM Keepalive, H.225 or H.245 message has been sent. |
|
|
|
|
|
|
|
| 3 | ||||||||||
Message Sent |
| (SIP) An outgoing message has been sent. |
|
|
|
|
|
|
|
|
|
|
|
| 4 | ||||||
Policy Change |
| A policy file has been updated. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 | ||||
Registration Accepted | A registration request has been accepted. |
|
|
|
|
|
|
|
|
|
|
|
| 1 | |||||||
Registration Refresh | A request to refresh or keep a registration alive has been accepted. |
|
|
|
|
|
|
|
| 3 | |||||||||||
Accepted |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Registration Refresh | A request to refresh a registration has been rejected. |
|
|
|
|
|
|
|
|
|
| 1 | |||||||||
Rejected |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Registration Refresh | A request to refresh or keep a registration alive has been received. |
|
|
|
|
|
|
|
|
|
| 3 | |||||||||
Requested |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Registration Rejected | A registration request has been rejected. The Reason event parameter contains the H.225 cause code. Optionally, the Detail event parameter may | 1 | |||||||||||||||||||
|
|
| contain a textual representation of the H.225 additional cause code. |
|
|
|
|
|
|
|
|
| |||||||||
Registration Removed | A registration has been removed by the VCS. The Reason event parameter specifies the reason why the registration was removed. This is one of: | 1 | |||||||||||||||||||
|
|
| • Authentication change |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |||
|
|
| • Conflicting zones |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |||
|
|
| • Operator forced removal |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |||
|
|
| • Operator forced removal (all registrations removed) |
|
|
|
|
|
|
|
|
|
|
| |||||||
|
|
| • Registration superseded. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |||
Registration Requested | A registration has been requested. |
|
|
|
|
|
|
|
|
|
|
|
| 1 | |||||||
Request Received | A |
|
|
|
|
|
|
|
|
|
|
|
| 2 | |||||||
Request Received | A |
|
|
|
|
|
|
|
|
|
|
|
| 3 | |||||||
Introduction |
| Getting Started | Overview and |
| System |
| VCS |
| Zones and |
| Call |
| Bandwidth |
| Firewall |
| Applications |
| Maintenance |
| Appendices |
| Status |
| Configuration |
| Configuration |
| Neighbors |
| Processing |
| Control |
| Traversal |
|
|
| |||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
D14049.04 |
|
|
|
|
|
|
| 50 |
|
|
|
|
|
|
|
|
|
| |||
JULY 2008 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ||||
