Monitoring TPO/PLAD connections
SNMP data
TPO service publishes the following SNMP data to report the activity and the status of the TPO places associated to PLAD lines
OID
|
iptrade.TPO.callcontrol.pladLineTable(.1.3.6.1.4.1.30191.2.2.18)
|
|
Fields
|
Type
|
Description
|
|
pladLineIndex
|
Numerical
|
Index in the SNMP table
|
|
pladLinePlaceName
|
String
|
Place name as per TPO place configuration
|
|
pladLinePladLine
|
String
|
TDM line name as per PLAD configuration e.g. tdm.line.0.name
|
|
pladLinePladName
|
String
|
PLAD group name
|
|
pladLineActive
|
Boolean
|
true indicates that the place is started; false otherwise
|
|
pladLineProxyAddr
|
String
|
PLAD IP address
|
|
pladLineConnected
|
Boolean
|
true indicates that TPO is connected to the line using the IP address in pladLineProxyAddr; false otherwise
|
|
pladLineLastStatus
|
String
|
The last SIP status of the PLAD line. See “Status codes” for further information
|
TPO generates an SNMP trap when PLAD line connection failure or restore is detected.
OID
|
iptrade.TPO.callcontrol.callControlTraps.pladLineErrorState (.1.3.6.1.4.1.30191.2.2.512.3)
|
|
Fields
|
Type
|
Description
|
|
Same as above but limited to one PLAD line.
|
|
Monitoring Turret/TPO connections
SNMP data
Turrets publishes the following SNMP data to report the activity and the status of their connections to TPO place(s).
OID
|
iptrade.turret.callcontrol.TPOTable (.1.3.6.1.4.1.30191.2.2.18)
|
|
Fields
|
Type
|
Description
|
|
TPOIndex
|
Numerical
|
Index in the SNMP table
|
|
TPOGroupName
|
String
|
Name of the TPO group as per Boot Settings (Turrets)
|
|
TPOActive
|
Boolean
|
true indicates that there is an active connection to the TPO group mentioned by TPOGroupName; false otherwise
|
|
TPOProxyAddr
|
String
|
TPO IP address
|
|
TPOConnected
|
Boolean
|
true indicates that there is an active connection to the TPO mentioned in TPOProxyAddr; false otherwise
|
|
TPOLastStatus
|
String
|
The last SIP status of the TPO line.
|
TPO generates an SNMP trap when PLAD line connection failure or restore is detected.
OID
|
iptrade.turret.callcontrol.callControlTraps.TPOErrorState (.1.3.6.1.4.1.30191.1.2.512.2)
|
|
Fields
|
Type
|
Description
|
|
Same as above but limited to one places line.
|
|
Syslog trace
Following error codes are traced by the turret on TPO connectivity events
CODE
|
Meaning
|
CCL!E0027
|
TPO control session failed to open
|
CCL!E0029
|
TPO connectivity is down
|
CCL!E0031
|
TPO connectivity is up
|
Following error codes are traced by TPO on Fail-Over events
CODE
|
Meaning
|
ORC!E0016
|
This message indicates that the failover has started and the original causes. TPO swings the permanent MRD placed to the secondary PLAD.
|
ORC!W0003
|
This message indicates the Fail-Over proceeding. TPO swaps to the MRD line of the secondary PLAD.
|
Status codes
Turrets and TPOs use the same status codes to report the status of the connection as per the table below.
CODE
|
Meaning
|
-1
|
Turret is unable to contact TPO
|
0
|
No attempt has been done yet
|
200
|
OK
|
404
|
PLAD could not be found at place startup because it is down or stopped
|
420
|
PLAD has been contacted but the line is not configured
|
486
|
Line is busy on PLAD
|
500
|
PLAD has accepted in the past the call from TPO but a RTP time out has occurs on PLAD. PLAD does not receive the stream from TPO
|
502
|
PLAD is contacted but PLAD encounter an error on TDM side. Call is not able to establish.
|
503
|
PLAD cannot be contacted to establish the call
|
504
|
PLAD has accepted in the past the call from TPO but a RTP time out has occurs on TPO. TPO does not receive the stream from PLAD
|
506
|
TPO service shut down
|
507
|
TPO service is starting up is not ready to accept turret connections yet
|
508
|
TPO is not able to ensure PLAD fail over and requires Turrets to fail over the second TPO
|
509
|
Turret has detected an RTP timeout on call with the TPO
|
510
|
PLAD has run but has been properly stopped
|
603
|
PLAD has accepted in the past the call from TPO but the line is in error state.
|
|
