Panasonic Section 520 manual Maintenance Troubleshooting Alarm Log Entries, Fatal Messages

Page 25

Chapter 5. Maintenance and

Troubleshooting

Alarm Log Entries

Telephony Services Administration allows for the logging and displaying of messages from a Telephony Services driver. Panadrvr takes advantage of this service. Note that the actual messages logged, displayed, etc., depend upon current Novell Tserver settings.

Each message has the following format:

Module ID: The NLM generating the message, in our case ‘Panadrvr’.

Level: The importance of the alarm. Telephony Services allows the following levels:

FATAL:

FATAL condition (calling module aborting)

WARNING:

non-service-affecting condition

CAUTION:

unexpected software error (non-fatal)

ERROR:

non-fatal, service-affecting condition

AUDIT_TRAIL: important (normal) event

TRACE:

trace message for debugging

Location: The source code location from where the alarm was generated. Panadrvr uses the following algorithm:

((Source_Code_Line_Number * 1000) + (Module_ID_Number)).

Thus, for any given alarm the least 3 significant digits represent the Internal Source Code Module ID while the most significant bits represent the line number within this module. This selection is intended for Panasonic Technical Support use only.

Error Code: Panadrvr uses this value as a cumulative alarm count.

“FATAL” Messages:

These alarms indicate Panadrvr is shutting down.

TDILOGERROR(dname, FATAL, ALMLOC, alarmcnt++, "Unloading via user request.").

The user has selected the Panadrvr shutdown driver option from the Panadrvr Menu and Panadrvr is exiting.

DBS-92-520

Issued April 2000

19

Image 25
Contents Page Tsapi Installation and Feature Description Contents Table of Contents Tsapi Tsapi Table of Contents Table of Contents Tsapi Overview of Telephony Services for the DBS Ovell Telephony Server DBS/Telephony Services Item Capacity Limitations and SpecificationsThis page intentionally left blank Telephone System Installation InstallationInstalling the API Circuit Card/Connector API Serial Port Connector API Circuit Card Connector Power on the DBS Programming the DBS = Standard API protocol defaultInstallation DBS Driver InstallationOverview Library DependenciesLoad Options Loading PanadrvrOption port= Option clearcall= Option c= Setting up Users Setting up Telephony Services UsersTsapi Installation This page intentionally left blank Basic Call Control Services Driver FeaturesDriver Features Tsapi Fatal Messages Maintenance Troubleshooting Alarm Log EntriesMaintenance and Troubleshooting Tsapi Error Messages Maintenance and Troubleshooting Tsapi Audit Trail Messages Maintenance and Troubleshooting Tsapi Display DBS Extension/Port Tables Panadrvr Menu SystemItem 2 Display Port to Extension Tables Item 1 Display Extension to Port TablesDBS Display Error CountersBad/No Resp to Select Req Naks to Select RequestMisc DriverDisplay Status Counters Commands Received Commands SentPackets Received Bytes SentDisplay ACS Info Display Resource InfoStream Open Confirms Stream Other RequestsStream Open Denies Peak Opened StreamsDisplay Csta Stats/Info Lost Negative Confs Lost Positive ConfsLost Query Confirmations Answer CallQuery LNR Query FWDRetr. Call Set MWIDisplay DBS Status/Info Display Resource Names/IDS ShutDownPort Monitor Info Display Driver QueuesCall Processing Toggles Change Max Call Time ValueDisplay Call Processing Stats Display API Control SignalsPresent Active Connections Present Active CallsPeak Active Calls Peak Active ConnectionsSet Debug Trace Level ErrorTrace DebugDisplay Active Call List Change MWI ActivatorDisplay Transfer Tables Open Close Log File N/ADisplay Monitor IDs Display Runtime Config StructureDisplay Conference Tables Insert Comment into log file N/ADisplay Call Times Index Issued April DBS-92-520