![](/images/new-backgrounds/1267867/267867365x1.webp)
Chapter 8 TSPLogger
Events
The following lists the currently defined events. Others may be added or existing ones modified as necessary.
[TSP NAME] TSP Initializing.......
The TSP application has just been started and is going through its initializa- tion phase.
[TSP NAME] *** TSP Started. Ver. CPS_TSP500.xx.xxx ***.
The TSP application has completed its initialization phase and is up and run- ning. It is now safe to connect the Call Manager/Gateway.
[TSP NAME] *** TSP Stopped ***
The TSP application has been stopped via the Admin Terminal command “stoptsp”
[TSP NAME] CTI Connection Established.
A Call Manger or Gateway has connected to the TSP.
[TSP NAME] CTI Connection Failed.
An attempt by a Call Manager or Gateway to connect to the TSP has failed.
[TSP NAME] CTI Connection Closed.
The connection between the Call Manager or Gateway to the TSP has closed.
[TSP NAME] Stopped Receiving Heartbeats.
The TSP has stopped receiving heartbeats form the Call Manager or Gateway.
[TSP NAME] Duplicate Connection Attempted from IP xx.xx.xx.xx.
Another Call Manager or Gateway (or some device) is attempting to connect
to the TSP that is already connected. The IP address is that of the 2nd Call Manager or Gateway.
[TSP NAME} Adjunct shutting down.
The Call Manger or Gateway is performing an orderly shutdown. (example: “cmshut”)
[TSP NAME] T1/E1 Span xx Failed To Initialize.
CPSEE_TSP500 User Guide | Version 4.0 | Page |
This document is confidential and proprietary to SER Solutions and is not for external use. |
|