Dialogic 4000 Media Gateway Series, Справочное руководство

Страница: 60 / 108

Event Logging With The Dialogic® Diva® SIPcontrolTM Software
page 60
Event Logging With The Dialogic
®
Diva
®
SIPcontrol
TM
Software
A computer with the Diva SIPcontrol software installed may write the following types of events into the System
Event Log:
• Errors
• Warnings
• Informational messages
You can view the events in the Windows
®
Event Viewer. To do so, click Programs > Settings > Control Panel
> Administrative Tools . In the Administrative Tools window, double-click Event Viewer and then
Application , where the Diva SIPcontrol software stores the events.
Errors
An error is a significant problem such as loss of data or loss of functionality. For example, if a service fails to
load, an error event will be logged.
See below for possible error events. Variables are enclosed in angle brackets. Parameters enclosed in square
brackets are optional:
Warnings
A warning is an event that is not necessarily significant but may indicate a possible future problem.
See the following table for possible warnings. Variables are enclosed in angle brackets:
Event ID Event Text Event Description
2000 Service could not start. <Reason> The <Reason> is text that explains why the service could not start.
2001 Service could not stop. <Reason> The <Reason> is text that explains why the service could not stop.
2002 Updating configuration failed. <Reason> The new configuration could not be activated, probably due to invalid
configuration data.
2003 Cannot bind to IP address.
<IP address>:<port> [<protocol>].
The service cannot be bound to the IP address.
2004 TLS initialization failed, call attempt
aborted. The configured TLS settings are invalid, or a required file is missing.
For calls to SIP only: the call is aborted unless an alternate
destination without TLS encryption is available.
Event ID Event Text Event Description
3000 SIP peer <Host Name> is not available. The SIP peer does not respond to keep-alive check requests, and
has therefore been marked as inactive. It will receive no calls from
SIPcontrol until the ongoing keep-alive check receives valid
responses.
3001 Cannot process call from <Calling Number>
to <Called Number>. No more licenses
available. The number of currently active calls has reached the number of
licensed channels and a further call has been declined thereof.
The <Calling Number> and <Called Number> of the PSTN call are
inserted as signaled from the line.
3002 Cannot process outgoing PSTN call to
<Called Number> from <Calling Number>.
No free PSTN channel available. The <Called Number> and <Calling Number> are inserted. It can
be a PSTN or SIP address.
3003 Call transfer to <Called Number> failed.
<Optional Reason> The <Called Number> is the PSTN-based number. The reason is
optional and may contain any text.
3004 Registration to <Registrar Host Name> with
user<User Host Name> failed. The Registration to a Registrar with the user to register failed.
3005 SIP peer <Host Name> is available again. An inactive SIP peer is alive again (has responded to alive check
request)