Cisco Cisco Customer Voice Portal Downloads
2-15
Cisco Internet Service Node (ISN) Product Description
OL-1250-03
Chapter 2 ISN Solution Components
ISN System Administration
Service Control Database Reporting
The Service Control Interface reports termination call detail records, service, trunk group, and peripheral
real-time records. The VRU PG derives the real-time statistics from the Service Control Messages
exchanged with ISN.
real-time records. The VRU PG derives the real-time statistics from the Service Control Messages
exchanged with ISN.
ISN Error Handling
ISN error handling and reporting generate information the system can use to:
•
Diagnose a system remotely.
•
Automatically report service-affecting events.
Some logging is controlled by the user; some logging–such as entries related to error conditions–is
always reported.
always reported.
There are a variety of methods the ISN uses to calculate metrics and handle and report errors:
•
Standalone Distributed Diagnostics and Services Network (SDDSN) provides a mechanism for
remote diagnosis of component failures.
remote diagnosis of component failures.
•
Voice Browser and Application Server log files—accessible through the remote
connections—enable local diagnosis.
connections—enable local diagnosis.
Trace Message Levels
Trace levels are defined during ISN installation and configuration. Some trace messages—such as
catastrophic and service-effecting events—will always be logged, regardless of the current trace level
settings.
catastrophic and service-effecting events—will always be logged, regardless of the current trace level
settings.
Note
It is the customer’s responsibility to purchase and configure a server of sufficient capacity for their
logging volumes.
logging volumes.
Trace messages can be grouped into two categories:
•
Those intended to help diagnose problems caused by configuration or network errors, for example,
informational, error, and basic call detail messages.
informational, error, and basic call detail messages.
•
Those intended solely for use by your support organization or Cisco software developers to diagnose
problems which may be software bugs, for example, component-level call detail and debug.
problems which may be software bugs, for example, component-level call detail and debug.
Log files
Log files provide trace messages for information, error logging, and—optionally—for component
metrics. Both the Voice Browser and Application Server generate log files. The Application Server files
are plain text, accessible through standard means or through the Application Administration Web pages.
metrics. Both the Voice Browser and Application Server generate log files. The Application Server files
are plain text, accessible through standard means or through the Application Administration Web pages.
The Voice Browser logs can be viewed using the dumplog.exe utility.
shows a sample log file.