|
|
TeleRouter processing (TRT) messages describe system error conditions associated with call routing. Some messages specify two codes, in hexadecimal format:
Cause codes are described in Table 9-1, and point of origination codes are described in Table 9-2.
| Code (Hex) | Description |
|---|---|
01 | Routing action was successful. |
08 | Action requested by standby side, but can only be processed on the active side. |
0D | Invalid resource group number. |
10 | Invalid incoming port address (not in valid range). |
12 | Port address in command is not a line or trunk. |
18 | Port address specified in command is the wrong type, resource group, or class of service. |
1F | Unable to find an available port in resource group specified in command or internal resource group implied by the command type. |
21 | Line/trunk port not off hook. |
22 | Port of this type or group is already linked into this call's resource chain. |
24 | Port address specified in command is for a port or card that is not active. |
25 | All tone channels are busy. |
26 | Port is in an uncontrollable state (CP_MBUSY, CP_GARD, CP_RDR, CP_DISC). |
29 | Internal error—command cannot be completed. |
2B | The inpulse or outpulse rule number specified in the command is invalid. Valid range is 1 to 30. |
37 | Both an inpulse and outpulse rule were specified for execution. |
39 | Resource group specified for hunting is of the wrong resource type. |
| Code (Hex) | Description |
|---|---|
01 | Reason for change is unknown; caused by host. |
02 | Reason for change is unknown; caused by system. |
12 | Port busied out via system administration's Card Maintenance screen. |
22 | Port busied out via system administration's Set Path screen. |
32 | Port busied out from far end. |
42 | Port busied out because auto makebusy error threshold achieved. |
52 | Port busied out due to internal card error (currently SRC only). |
TRT messages are described in the following manner:
TRTnn: Message
Explanation An explanation of the message.
Action A description of the action the user should take.
TRT01: Route Failure: Code XX, ICT XX, Table t, Route X, Attempt n
Explanation A route attempt (n) failed for the specified incoming port and route information (X) on routing table (t). The call could not be routed as desired.
Action Refer to Table 9-1 and Table 9-2 for the routing error code identifying the reason for the failure.
TRT02: Rule Failure: Code XX, ICT XX, Table t, Route X, Attempt n
Explanation An attempt (n) to execute an inpulse rule has failed for the specified incoming port and route information (X) on routing table (t). The call could not be routed as desired.
Action Refer to Table 9-1 and Table 9-2 for the routing error code that provides the reason for the failure.
TRT03: Teardown Failure: Code XX, ICT XX
Explanation An attempt to release the specified incoming port has failed. The incoming port may be in an unusable state.
Action Refer to Table 9-1 and Table 9-2 for the routing error code that provides the reason for the failure.
TRT10: Overlay Transmit Overrun Encountered: Buffer XX
Explanation An overflow condition has occurred during message transmission to the call routing overlay. Call processing using TeleRouter may be delayed or interrupted.
Action A series of such errors indicates a possible system failure.
TRT11: Overlay Receive Buffer Deallocation Error - XX
Explanation The call routing overlay could not return the allocated buffer space back to the memory pool. Call processing using TeleRouter may be delayed or interrupted.
Action A series of such errors indicates a possible system failure.
TRT12: Overlay Message Parsing Error - XX
Explanation The message received by the call routing overlay cannot be processed and is discarded. Call processing using TeleRouter may be delayed or interrupted.
Action A series of such errors indicates an internal processing problem.
TRT20: PSC Exists On Port $XX - Code XX, Group X
Explanation The port in the resource group specified is undergoing permanent signal condition (PSC) processing. The outgoing port could not be used. Call processing may be delayed or interrupted.
Action The code value (XX) indicates the reason for the permanent signal condition (PSC). This value corresponds to the PSC code of the Permanent Signal Condition ($D2) report. Convert the value from hex to binary and refer to the Cisco VCO/4K Extended Programming Reference for interpretation.
TRT21: PSC Clear On Port $XX - Code 00, Group X
Explanation The permanent signal condition (PSC) has cleared on the port in the specified resource group (X).
Action None required.
TRT22: Port $XX Is Online - Code XX, Group X
Explanation The specified port in the resource group indicated has returned to service.
Action The code value (XX) indicates the reason that the port was originally taken out-of-service (OOS). Refer to Table 9-2 for OOS point of origination code values.
TRT23: Port $XX Is Offline - Code XX, Group X
Explanation The specified port in the resource group indicated has been removed from service. Call processing may be delayed or interrupted.
Action The code value (XX) indicates why the port was taken out-of-service (OOS). Refer to Table 9-2 for OOS point of origination code values.
TRT24: Supervision Error Detected - Port $XX, Group X, Code XXXX
Explanation A supervision error has occurred on the port in the specified resource group. Call processing may be delayed or interrupted.
Action The code values (XXXX) correspond to the Answer Supervision Code bytes in the Outgoing Port Change of State ($DA) report assuming the Change byte is 20. Refer to the Cisco VCO/4K Extended Programming Reference for detailed error descriptions.
TRT25: Inpulse Rule Aborted - Port $XX, Rule X
Explanation The inpulse rule (X) that was being performed on the port specified (XX) has been aborted. The outgoing call cannot be completed. Call processing may be delayed or interrupted.
Action Examine the Inpulse Rule Complete ($DD) report to determine the cause of the aborted inpulse rule. Refer to the Cisco VCO/4K Extended Programming Reference for detailed error descriptions.
TRT26: Resource Limitation Exists for Group X (MIN ALRM SET)
Explanation No ports are currently available in the resource group specified (X). A minor alarm has been set. Call processing is delayed until resources are available.
Action Wait for the system to free resources. Add additional resources to the indicated resource group.
TRT27: Resource Limitation Clear For Group X
Explanation The resource limitation condition that existed for the resource group specified (X) has been cleared.
Action None required.
TRT28: WARNING - 3/4 Of Resource Group X Has Been Busied Out (MIN ALRM SET)
Explanation A resource limitation is pending for the group specified (X). An excess of ports within the resource group (75 percent or more) have been removed from service, either via system administration or by the auto makebusy function.
Action Return ports to the in service state.
TRT29: Resource Group X Warning Condition Has Cleared
Explanation The resource limitation warning has been cleared for the resource group specified. Indicates the amount of ports out-of-service in the resource group has dropped below 50 percent (at least half the ports in the group are now available).
Action None required.
Posted: Sat Sep 28 15:32:38 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.