Table Of Contents
Call Processing Troubleshooting
Introduction
Call Processing Events and Alarms
CALLP (1)
CALLP (2)
CALLP (3)
CALLP (4)
CALLP (5)
CALLP (6)
CALLP (7)
CALLP (8)
CALLP (9)
CALLP (10)
CALLP (11)
CALLP (12)
CALLP (13)
CALLP (14)
CALLP (15)
CALLP (16)
CALLP (17)
CALLP (18)
CALLP (19)
CALLP (20)
CALLP (21)
CALLP (22)
CALLP (23)
CALLP (24)
CALLP (25)
CALLP (26)
CALLP (27)
CALLP (28)
CALLP (29)
CALLP (30)
CALLP (31)
CALLP (32)
CALLP (33)
CALLP (34)
CALLP (35)
CALLP (36)
CALLP (37)
CALLP (38)
CALLP (39)
CALLP (40)
CALLP (41)
CALLP (42)
CALLP (43)
CALLP (44)
CALLP (45)
Monitoring Call Processing Events
Test Report—Call Processing (1)
No Route Available for Called Number—Call Processing (8)
No Route Available for Carrier Dialed—Call Processing (9)
Feature Server One Link Down—Call Processing (11)
Feature Server Both Links Down—Call Processing (12)
Network Access Server Create Connection Error—Call Processing (13)
Network Access Server Authentication Failure—Call Processing (14)
Cable Modem Termination System Easily Recognizable Identification Not Found in Media Gateway Table—Call Processing (15)
Route Index has No Trunk Group Assigned—Call Processing (16)
Invalid Route Index Used—Call Processing (17)
Unable to Play Announcement—Call Processing (18)
Call Routed to Unprovisioned Subscriber—Call Processing (19)
No Route or Trunk Group Available to Route Call—Call Processing (20)
Call Released Due to Maximum Hop Counts Exceeded—Call Processing (21)
Trunk Group Index Read Failure—Call Processing (22)
Routing Error: Termination is Not a Subscriber—Call Processing (23)
Invalid Route for Subscriber Index—Call Processing (24)
Invalid Route Group for Subscriber Routing—Call Processing (25)
Invalid Trunk Group for Subscriber Routing—Call Processing (26)
Unable to Route: Blocked by Destination Subscriber Status—Call Processing (27)
Route Name Does Not Exist—Call Processing (28)
Routing Selection Failure—Call Processing (29)
Customer-Originated Trace Test Failed—Call Processing (30)
Call Authorization Failure—Call Processing (31)
Country Code Dialing Plan Error—Call Processing (32)
Invalid Call—Call Processing (33)
Dial Plan Information Not Found for Digits Received—Call Processing (34)
Dial Plan Information for Test Call Not Found—Call Processing (35)
Invalid or Unknown Nature of Address—Call Processing (36)
Call Failure—Call Processing (37)
Release Cause 25 Exchange Routing Error Received—Call Processing (38)
Test Call Blocked Due to Congestion or Isolation—Call Processing (39)
Interactive Voice Response Real Time Transport Protocol Session Fail—Call Processing (40)
INVITE Message From Unauthorized Call Agent—Call Processing (41)
Call Failed after Local Number Portability Query with Location Routing Number of this BTS 10200 and the Directory Number—Call Processing (42)
Call Processing Session Initiation Protocol Trigger Provisioning Error—Call Processing (43)
Call Processing No Session Initiation Protocol Trigger Context Found—Call Processing (44)
Context in call from Application Server not Found—Call Processing (45)
Troubleshooting Call Processing Alarms
Feature Server One Link Down—Call Processing (11)
Feature Server Both Links Down—Call Processing (12)
Release Cause 25 Exchange Routing Error Received—Call Processing (38)
INVITE Message From Unauthorized Call Agent—Call Processing (41)
Call Processing Troubleshooting
Revised: December 11, 2008, OL-8723-17
Introduction
This chapter provides the information needed to monitor and troubleshoot call processing events and alarms. This chapter is divided into the following sections:
•
Call Processing Events and Alarms—Provides a brief overview of each call processing event and alarm.
•Monitoring Call Processing Events—Provides the information needed to monitor and correct the call processing events.
•Troubleshooting Call Processing Alarms—Provides the information needed to troubleshoot and correct the call processing alarms.
For additional call processing routing and translations information refer to the Cisco BTS 10200 Softswitch Routing, Translations, and Dial Plan Guide.
Note The following billing records are created when a call is rejected due to overload conditions:
· SS7 termination cause code 42
· Cable signaling stop event cause code "resource unavailable"
Calls rejected by the signaling adapter will not generate a billing record.
Call Processing Events and Alarms
This section provides a brief overview of the call processing events and alarms for the BTS 10200 in numerical order. Table 4-1 lists all of the call processing events and alarms by severity.
Note Click the call processing message number in Table 4-1 to display information about the event.
CALLP (1)
For additional information, refer to the "Test Report—Call Processing (1)" section.
DESCRIPTION
|
Test Report
|
SEVERITY
|
Information (INFO)
|
THRESHOLD
|
10000
|
THROTTLE
|
0
|
CALLP (2)
CALLP (2) is not used.
CALLP (3)
CALLP (3) is not used.
CALLP (4)
CALLP (4) is not used.
CALLP (5)
CALLP (5) is not used.
CALLP (6)
CALLP (6) is not used.
CALLP (7)
CALLP (7) is not used.
CALLP (8)
To monitor and correct the cause of the event, refer to the "No Route Available for Called Number—Call Processing (8)" section.
DESCRIPTION
|
No Route Available for Called Number
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
500
|
DATAWORDS
|
Orig Type (Trunk or S-ONE_BYTE
Orig Sub or TG ID-EIGHT_BYTES
Calling Party Number-STRING [20]
Called Party Number-STRING [20]
|
PRIMARY
CAUSE
|
The call originated from a subscriber or trunk for a called party number that has no route available.
|
PRIMARY
ACTION
|
The data words in the event report indicate what parameters that need to be corrected. Refer to the office records for the subscriber.
|
SECONDARY
CAUSE
|
Parameter(s) in the subscriber and/or dial-plan table are missing or incorrect for the dialed number.
|
SECONDARY
ACTION
|
Determine whether the routing parameters (such as digit-string) were entered correctly in the subscriber and dial-plan tables.
|
TERNARY
ACTION
|
If the called party is a subscriber, verify that the subscriber-type is listed as subscriber in the dial-plan table.
|
SUBSEQUENT
ACTION
|
If the call is long distance using a presubscribed interexchange carrier (PIC), check that the PIC for this subscriber is properly provisioned in the dial-plan table. If necessary, edit these files using the change dial-plan or change subscriber commands.
|
CALLP (9)
For additional information, refer to the "No Route Available for Carrier Dialed—Call Processing (9)" section.
DESCRIPTION
|
No Route Available for Carrier Dialed
|
SEVERITY
|
INFO
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Orig Type (Trunk or S-ONE_BYTE
Orig Sub or TG ID-EIGHT_BYTES
Calling Party Number-STRING [20]
Called Party Number-STRING [20]
Carrier Code Dialed-STRING [20]
|
PRIMARY
CAUSE
|
No route is available for the interexchange carrier (IXC) dialed.
|
PRIMARY
ACTION
|
The data words in the event report indicate the parameters that need to be corrected. Refer to the office records for the carrier.
|
SECONDARY
CAUSE
|
Parameter(s) in the carrier and/or route-grp table are missing or incorrect for the carrier.
|
SECONDARY
ACTION
|
Determine whether the routing parameters were entered correctly in the carrier and/or route-grp tables.
|
TERNARY
ACTION
|
If the carrier-identification (ID) or route-grp-ID are not specified, or are incorrect, in the dial-plan table, enter the correct values. Use the change carrier or change route-grp command.
|
CALLP (10)
CALLP (10) is not used.
CALLP (11)
To troubleshoot and correct the cause of the alarm, refer to the "Feature Server One Link Down—Call Processing (11)" section.
DESCRIPTION
|
Feature Server One Link Down
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Interface Name-STRING [65]
Interface IP Address-STRING [65]
|
PRIMARY
CAUSE
|
The hardware is broken.
|
PRIMARY
ACTION
|
Check the link interfaces.
|
CALLP (12)
To troubleshoot and correct the cause of the alarm, refer to the "Feature Server Both Links Down—Call Processing (12)" section.
DESCRIPTION
|
Feature Server Both Links Down
|
SEVERITY
|
CRITICAL
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Interface Name-STRING [65]
Interface IP Address-STRING [65]
Interface Name-STRING [65]
Interface IP Address-STRING [65]
|
PRIMARY
CAUSE
|
The hardware is broken.
|
PRIMARY
ACTION
|
Check the link interfaces.
|
CALLP (13)
For additional information, refer to the "Network Access Server Create Connection Error—Call Processing (13)" section.
DESCRIPTION
|
Network Access Server Create Connection Error (NAS CRCX Error)
|
SEVERITY
|
INFO
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
PRIMARY
CAUSE
|
A pre-authentication failure has occurred.
|
PRIMARY
ACTION
|
None
|
CALLP (14)
For additional information, refer to the "Network Access Server Authentication Failure—Call Processing (14)" section.
DESCRIPTION
|
Network Access Server Authentication Failure (NAS Authentication Failure)
|
SEVERITY
|
INFO
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
PRIMARY
CAUSE
|
The authentication, authorization, and accounting (AAA) server denied the request.
|
PRIMARY
ACTION
|
Check the calling and called numbers.
|
CALLP (15)
For additional information, refer to the "Cable Modem Termination System Easily Recognizable Identification Not Found in Media Gateway Table—Call Processing (15)" section.
DESCRIPTION
|
Cable Modem Termination System Easily Recognizable Identification Not Found in Media Gateway Table (CMTS ER ID Not Found in MGW Table)
|
SEVERITY
|
INFO
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
MGW-NAME-STRING [80]
|
PRIMARY
CAUSE
|
The cable modem termination system (CMTS)/easily recognizable (ER) entry was not found in the Media Gateway Table.
|
PRIMARY
ACTION
|
Provision the CMTS-ER index in the Media Gateway Table.
|
CALLP (16)
To monitor and correct the cause of the event, refer to the "Route Index has No Trunk Group Assigned—Call Processing (16)" section.
DESCRIPTION
|
Route Index has No Trunk Group Assigned.
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Route Index-FOUR_BYTES
|
PRIMARY
CAUSE
|
A trunk group was not assigned to the given route.
|
PRIMARY
ACTION
|
Provision a trunk group for the associated route index.
|
CALLP (17)
To monitor and correct the cause of the event, refer to the "Invalid Route Index Used—Call Processing (17)" section.
DESCRIPTION
|
Invalid Route Index Used
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Route Index-FOUR_BYTES
|
PRIMARY
CAUSE
|
An invalid route index was used.
|
PRIMARY
ACTION
|
Correct the provisioning and assign a valid route index.
|
CALLP (18)
To monitor and correct the cause of the event, refer to the "Unable to Play Announcement—Call Processing (18)" section.
DESCRIPTION
|
Unable to Play Announcement
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Announcement Index-FOUR_BYTES
|
PRIMARY
CAUSE
|
An announcement was not provisioned correctly.
|
PRIMARY
ACTION
|
Provision the announcement.
|
CALLP (19)
To monitor and correct the cause of the event, refer to the "Call Routed to Unprovisioned Subscriber—Call Processing (19)" section.
DESCRIPTION
|
Call Routed to Unprovisioned Subscriber
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Subscriber Index-FOUR_BYTES
Directory Number Dia-STRING [20]
|
PRIMARY
CAUSE
|
A subscriber was not provisioned correctly.
|
PRIMARY
ACTION
|
Provision the subscriber.
|
CALLP (20)
To monitor and correct the cause of the event, refer to the "No Route or Trunk Group Available to Route Call—Call Processing (20)" section.
DESCRIPTION
|
No Route or Trunk Group Available to Route Call
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Calling Number-STRING [20]
Called Number-STRING [20]
Route Index-FOUR_BYTES
Trunk Group ID-FOUR_BYTES
|
PRIMARY
CAUSE
|
A Trunk Group was not provisioned correctly in the route.
|
PRIMARY
ACTION
|
Verify the route and trunk group provisioning.
|
CALLP (21)
To monitor and correct the cause of the event, refer to the "Call Released Due to Maximum Hop Counts Exceeded—Call Processing (21)" section.
DESCRIPTION
|
Call Released Due to Maximum Hop Counts Exceeded
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Calling Number-STRING [20]
Called Number-STRING [20]
Hop Count-FOUR_BYTES
|
PRIMARY
CAUSE
|
The number of hops between destinations is excessive.
|
PRIMARY
ACTION
|
Reduce number of hops between destinations.
|
CALLP (22)
To monitor and correct the cause of the event, refer to the "Trunk Group Index Read Failure—Call Processing (22)" section.
DESCRIPTION
|
Trunk Group Index Read Failure
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Trunk Group Index-FOUR_BYTES
Call Index-FOUR_BYTES
|
PRIMARY
CAUSE
|
The Trunk Group Index could not be retrieved from call data.
|
PRIMARY
ACTION
|
Check the provisioning.
|
CALLP (23)
To monitor and correct the cause of the event, refer to the "Routing Error: Termination is Not a Subscriber—Call Processing (23)" section.
DESCRIPTION
|
Routing Error: Termination is Not a Subscriber
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Termination Index-FOUR_BYTES
Termination Type-FOUR_BYTES
|
PRIMARY
CAUSE
|
The destination termination is not provisioned as a subscriber.
|
PRIMARY
ACTION
|
Check the provisioning.
|
CALLP (24)
To monitor and correct the cause of the event, refer to the "Invalid Route for Subscriber Index—Call Processing (24)" section.
DESCRIPTION
|
Invalid Route for Subscriber Index
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Route-STRING [20]
Subscriber Index-FOUR_BYTES
|
PRIMARY
CAUSE
|
The route is not provisioned correctly for the specified subscriber.
|
PRIMARY
ACTION
|
The check provisioning.
|
CALLP (25)
To monitor and correct the cause of the event, refer to the "Invalid Route Group for Subscriber Routing—Call Processing (25)" section.
DESCRIPTION
|
Invalid Route Group for Subscriber Routing
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Route-STRING [20]
Subscriber Index-FOUR_BYTES
|
PRIMARY
CAUSE
|
The route group is not provisioned correctly for the specified subscriber.
|
PRIMARY
ACTION
|
Check the provisioning.
|
CALLP (26)
To monitor and correct the cause of the event, refer to the "Invalid Trunk Group for Subscriber Routing—Call Processing (26)" section.
DESCRIPTION
|
Invalid Trunk Group for Subscriber Routing
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Trunk Group Index-FOUR_BYTES
Subscriber Index-FOUR_BYTES
|
PRIMARY
CAUSE
|
The trunk group is not provisioned correctly for the specified subscriber.
|
PRIMARY
ACTION
|
Check the provisioning.
|
CALLP (27)
To monitor and correct the cause of the event, refer to the "Unable to Route: Blocked by Destination Subscriber Status—Call Processing (27)" section.
DESCRIPTION
|
Unable to Route: Blocked by Destination Subscriber Status
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Subscriber Index-FOUR_BYTES
Subscriber Status-STRING [20]
|
PRIMARY
CAUSE
|
The subscriber provisioning is not in the correct state.
|
PRIMARY
ACTION
|
Check the provisioning.
|
CALLP (28)
To monitor and correct the cause of the event, refer to the "Route Name Does Not Exist—Call Processing (28)" section.
DESCRIPTION
|
Route Name Does Not Exist
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Route Name-STRING [40]
|
PRIMARY
CAUSE
|
The route is not correctly provisioned.
|
PRIMARY
ACTION
|
Check the provisioning.
|
CALLP (29)
To monitor and correct the cause of the event, refer to the "Routing Selection Failure—Call Processing (29)" section.
DESCRIPTION
|
Routing Selection Failure
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Route Index-FOUR_BYTES
Calling Number-STRING [20]
Called Number-STRING [20]
|
PRIMARY
CAUSE
|
The route is not correctly provisioned.
|
PRIMARY
ACTION
|
Check the provisioning.
|
CALLP (30)
To monitor and correct the cause of the event, refer to the "Customer-Originated Trace Test Failed—Call Processing (30)" section.
DESCRIPTION
|
Customer-Originated Trace Test Failed (COT Test Failed)
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Termination Index-FOUR_BYTES
|
PRIMARY
CAUSE
|
A customer-originated trace (COT) test has failed.
|
PRIMARY
ACTION
|
Contact Cisco for information on how to further debug the problem. (Contact Cisco Technical Assistance Center (TAC).)
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
CALLP (31)
To monitor and correct the cause of the event, refer to the "Call Authorization Failure—Call Processing (31)" section.
DESCRIPTION
|
Call Authorization Failure
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Calling Number-STRING [20]
Called Number-STRING [20]
|
PRIMARY
CAUSE
|
Due to incorrect provisioning the call cannot be completed.
|
PRIMARY
ACTION
|
Contact Cisco for more information. (Contact Cisco TAC.)
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
CALLP (32)
To monitor and correct the cause of the event, refer to the "Country Code Dialing Plan Error—Call Processing (32)" section.
DESCRIPTION
|
Country Code Dialing Plan Error
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Called Number-STRING [20]
Dial Plan Index-FOUR_BYTES
|
PRIMARY
CAUSE
|
The country code was not found in the dial plan.
|
PRIMARY
ACTION
|
Check the provisioning.
|
CALLP (33)
To monitor and correct the cause of the event, refer to the "Invalid Call—Call Processing (33)" section.
DESCRIPTION
|
Invalid Call
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Calling Number-STRING [20]
Called Number-STRING [20]
|
PRIMARY
CAUSE
|
The call could not be completed because the number entered was invalid.
|
PRIMARY
ACTION
|
Check the provisioning and the number dialed.
|
CALLP (34)
To monitor and correct the cause of the event, refer to the "Dial Plan Information Not Found for Digits Received—Call Processing (34)" section.
DESCRIPTION
|
Dial Plan Information Not Found for Digits Received
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Calling Number-STRING [20]
Called Number-STRING [20]
Dial Plan Index-FOUR_BYTES
|
PRIMARY
CAUSE
|
The call could not be completed because the number entered could not be located in the dial-plan.
|
PRIMARY
ACTION
|
Check the provisioning and the number dialed.
|
CALLP (35)
To monitor and correct the cause of the event, refer to the "Dial Plan Information for Test Call Not Found—Call Processing (35)" section.
DESCRIPTION
|
Dial Plan Information for Test Call Not Found
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Dial Plan Index-FOUR_BYTES
|
PRIMARY
CAUSE
|
The test call could not be completed because the number entered could not be located in the dial-plan.
|
PRIMARY
ACTION
|
Check the provisioning and the number tested.
|
CALLP (36)
To monitor and correct the cause of the event, refer to the "Invalid or Unknown Nature of Address—Call Processing (36)" section.
DESCRIPTION
|
Invalid or Unknown Nature of Address (Invalid or Unknown NOA)
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
NOA Received-FOUR_BYTES
Calling Number-STRING [20]
Called Number-STRING [20]
|
PRIMARY
CAUSE
|
The nature of address (NOA) was incorrect in the dial-plan.
|
PRIMARY
ACTION
|
Check the provisioning.
|
CALLP (37)
To monitor and correct the cause of the event, refer to the "Call Failure—Call Processing (37)" section.
DESCRIPTION
|
Call Failure
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Type of Call-FOUR_BYTES
Calling Number-STRING [20]
Called Number-STRING [20]
Failure Indication-STRING [40]
|
PRIMARY
CAUSE
|
The call failed for the indication listed in the Failure Indication dataword.
|
PRIMARY
ACTION
|
Call Cisco for more information. (Contact Cisco TAC.)
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
Prior to contacting Cisco TAC, collect a billing-record for the failed call using the following:
report billing-record orignumber=<string>
CALLP (38)
To troubleshoot and correct the cause of the alarm, refer to the "Release Cause 25 Exchange Routing Error Received—Call Processing (38)" section.
DESCRIPTION
|
Release Cause 25 Exchange Routing Error Received
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
CIC-FOUR_BYTES
TGN-ID-FOUR_BYTES
DPC-STRING [64]
OPC-STRING [64]
|
PRIMARY
CAUSE
|
Received release (REL) with cause number 25.
|
PRIMARY
ACTION
|
Log and map the cause to number 31.
|
CALLP (39)
To monitor and correct the cause of the event, refer to the "Test Call Blocked Due to Congestion or Isolation—Call Processing (39)" section.
DESCRIPTION
|
Test Call Blocked Due to Congestion or Isolation
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
CIC- TWO_BYTES
TGN-ID-EIGHT_BYTES
DPC-STRING [20]
OPC-STRING [20]
|
PRIMARY
CAUSE
|
The initial address message (IAM) for test call was blocked due to congestion or isolation.
|
PRIMARY
ACTION
|
Correct the congestion or isolation problem and place the test call again from a remote system.
|
CALLP (40)
To monitor and correct the cause of the event, refer to the "Interactive Voice Response Real Time Transport Protocol Session Fail—Call Processing (40)" section.
DESCRIPTION
|
Interactive Voice Response Real Time Transport Protocol Session Fail (IVR RTP Session Fail)
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Route Guide ID-STRING [17]
Trunk Group Index-FOUR_BYTES
|
PRIMARY
CAUSE
|
The interactive voice response (IVR) server is not ready, or the connection failed.
|
PRIMARY
ACTION
|
Check IVR server. The related route guide ID and/or trunk group index are provided if known at the time the event report is issued.
|
CALLP (41)
To troubleshoot and correct the cause of the alarm, refer to the "INVITE Message From Unauthorized Call Agent—Call Processing (41)" section.
DESCRIPTION
|
INVITE Message From Unauthorized Call Agent (INVITE Message From Unauthorized CA)
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Unauthorized Call Agent DN-STRING [128]
Platform Name-STRING [32]
|
PRIMARY
CAUSE
|
The call-agent table is not configured properly.
|
PRIMARY
ACTION
|
Reconfigure the call-agent table to have the authorized call agent (CA).
|
SECONDARY
CAUSE
|
A potential intrusion has occurred if the network-ID is mismatched from the local-network.
|
SECONDARY
ACTION
|
Configure the network to block the unauthorized network-ID.
|
CALLP (42)
For additional information, refer to "Call Failed after Local Number Portability Query with Location Routing Number of this BTS 10200 and the Directory Number—Call Processing (42)" section.
DESCRIPTION
|
Call Failed after Local Number Portability Query with Location Routing Number of this BTS 10200 and the Directory Number (Call Failed after LNP Query with LRN of this switch and the DN)
|
SEVERITY
|
INFO
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Calling Number-STRING [20]
Called Number (GAP)-STRING [20]
Location Routing Number (LRN)-STRING [20]
Jurisdiction Information Parameter-STRING [20]
|
PRIMARY
CAUSE
|
The provisioning of the ported-in subscriber has not been completed.
|
PRIMARY
ACTION
|
Verify whether the given DN has been provisioned correctly in the reporting BTS. If there is an error in the LNP database (SCP) or other switch, then notify the appropriate administrators. Note that porting of the subscriber and DN from the donor switch to the recipient switch, and the associated updates of the Location Routing Number (LRN) in all the SCP databases, may not all occur at exactly the same time. Therefore it must be expected that some call failures may occur until the porting process has completed at all network nodes. Once the porting process is completed, if mis-routing still occurs, then the listed actions should be taken to resolve the issue.
|
SECONDARY
CAUSE
|
The LNP database (SCP) has an incorrect location routing number (LRN) for the given directory number (DN).
|
CALLP (43)
To monitor and correct the cause of the event, refer to the "Call Processing Session Initiation Protocol Trigger Provisioning Error—Call Processing (43)" section.
DESCRIPTION
|
Call Processing Session Initiation Protocol Trigger Provisioning Error (CALLP SIP Trigger Provisioning Error)
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Calling Party Number-STRING [64]
Called Party Number-STRING [64]
Call ID- FOUR_BYTES
OBCSM/TBCSM SIP Trigger-STRING [8]
|
PRIMARY
CAUSE
|
A provisioning data discrepancy between the Application Server (AS) and the BTS 10200 has occurred.
|
PRIMARY
ACTION
|
Modify the provisioning data either in the BTS 10200 or the AS.
|
CALLP (44)
To monitor and correct the cause of the event, refer to the "Call Processing No Session Initiation Protocol Trigger Context Found—Call Processing (44)" section.
DESCRIPTION
|
Call Processing No Session Initiation Protocol Trigger Context Found (CALLP No SIP Trig Context Found)
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Calling Party Number-STRING [64]
Called Party Number-STRING [64]
Call ID- FOUR_BYTES
Inbound Context String-STRING [64]
|
PRIMARY
CAUSE
|
An invalid service_ref in the SIP INVITE message coming from the AS has occurred.
|
PRIMARY
ACTION
|
Report the BTS 10200 and the AS with the received service_ref string to Cisco TAC. (Contact Cisco TAC.)
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
CALLP (45)
To monitor and correct the cause of the event, refer to the "Context in call from Application Server not Found—Call Processing (45)" section.
DESCRIPTION
|
Context in Call from Application Server not Found (Context in Call from App Server not Found)
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
PRIMARY
CAUSE
|
The BTS 10200 has received an INVITE from an AS which contains a context ID in the route header which is invalid. It may be that the AS has not properly returned the Route Header.
|
PRIMARY
ACTION
|
Get the AS to return the BTS 10200 route header correctly
|
SECONDARY
CAUSE
|
It is possible that the BTS 10200 cleared the call and removed the context before the AS returned an INVITE to the BTS 10200.
|
SECONDARY
ACTION
|
Check timing for the calls returned to the BTS 10200 from the AS.
|
Monitoring Call Processing Events
This section provides the information needed to monitor and correct call processing events. Table 4-2 lists all of the call processing events in numerical order and provides cross reference to each subsection in this section.
