Page C-14
Appendix C — CP Server
INTER-TEL
®
AXXESS
®
MANUAL VERSION 11.0 – May 2008
Service Logs
17. SERVICE LOGS
17.1 The CP Server writes various service and debug information to a service log file. Some
of the data found in the service log are thread status, such as starting and stopping, socket
thread logons, file read and write errors, mutex errors, etc. The default name is icp.log. This
file and its backups are kept in the working directory by default. The name and location of the
service logs are programmable through the configuration utility.
17.2 When a system freeze is performed, as described on page C-12, the icp.log file and
all of its backups are frozen along with the CP History. The backup files are named
freeze_xx_ icp_yyy.log, where xx is the freeze number (01-99) and yyy is the backup
file number. The active icp.log file is named freeze_xx_icp.log.
17.3 If using an ATM Switch, you can use the chassis Log Utility to obtain log information,
in a text file format, from the remote equipment chassis. This utility, which runs independently
of the Inter-Tel Call Processing and Watchdog service, is automatically loaded with the CP
Server software. Because it starts up automatically whenever the PC is turned on, you do not
have to log on to Windows to start it. With this utility, you can maintain up to five different log
files, up to 256 Kb each, for every remote chassis.
17.4 To obtain the log information, the chassis Log Service attempts to establish an ATM
SVC (Switched Virtual Circuit) socket connection to the remote equipment chassis. After a
valid SVC connection has been established, the equipment chassis Log Utility sends its login
(carriage return). It then waits for a response from the remote equipment chassis. If the utility
does not get a response within one second, it sends another login command. If the remote chas-
sis does not respond to ten such login attempts, the utility assumes that the connection to the
remote chassis has failed and tries to re-connect. If the connections to all the remote chassis
fail, then the utility waits for 20 seconds before trying to re-establish SVC connections.
17.5 If the login to the remote equipment chassis is successful, the Utility attempts to log all
the information it receives from that socket connection. The log is then stored in a file named
Remote_KSU_($Number)_log.log, where $Number indicate the remote equipment
chassis number. This log is located on the Call Processing Server (CPS) hard drive in the
Icp\KSULog directory, which is where the service utility is installed. If the connection to a
particular remote equipment chassis is lost, logging for that particular chassis is terminated
until the utility can re-connect successfully.
NOTE: If the system is not ATM-based, the chassis Log Utility will start up and then immedi-
ately terminate.
To Next Page
Loading...
