Feedback
|
Table Of Contents
Query Verification Tool and Translation Verification Tool Featurette
Query LIDB Response Parameters
AIN 0.1 Query Attempted for IN/1 Configuration
IN/1 Query Attempted for AIN 0.1 Configuration
Query Verification Tool and Translation Verification Tool Featurette
This document describes the Query Verification Tool (QVT) and the Translation Verification Tool (TVT) and is organized into the following sections:
•
Translation Verification Tool
Tool Requirements
The following requirements are supported in the QVT and TVT:
•
TVT—Provide a tool to find, diagnose, and trace call flow path decisions.
•
Query Local Routing Number (QLRN) Tool—Provide the ability to enter a ten- digit directory number and launch a query to the service control point (SCP) as though it was a called number from the service switching point (SSP).
•
Query Tool E800VER Command—Send a database query to the SCP as if it was an 800 called number from the SSP without initiating a call.
•
Query Tool CNAMDVER and TESTSS CNAMD Commands—Provide the ability to query the SCP database for the CNAM display and privacy status associated with the name without initiating a call.
Query Verification Tool
This section describes the QVT and includes the following sections:
Overview
The Query Verification Tool (QVT) enables a user to generate TCAP queries to external databases through the CLI interface. The types of queries supported are:
•
Line Information Database (LIDB)—Generated by the POTS Feature Server
•
Toll-Free—Generated by the AIN Feature Server
•
Local Number Portability (LNP)—Generated by the AIN Feature Server
Command Format
The QVT command uses the following format:
query <lidb|toll-free|lnp> parameter=value;Examples
query lidb calling-dn=8005550102; opc-id=opc;Syntax Description
* OPC-Id
Origination Point Code ID
* Calling-DN
The caller's directory number.
Table-Info
Specifies whether or not you want to see the tables accessed when processing the query. Y/N; default=N
Examples
query toll-freeSyntax Description
Examples
query lnp;Syntax Description
Response Format
The system response to a query is in the following format:
Reply: <success|failure>; parameter=value;Common Response Parameters
Successful reponse parameters include the following:
•
OPC—Origination Point Code
•
SSN—Subsystem Number
•
TT—Translation Type
•
SCP-Point-Code—Point Code of the SCP
•
ACG Component Received
•
ACG-Control-Code-Length
•
GAP-Duration
•
GAP-Interval
•
Announcement-Cause-Code
An error message will be displayed if the query is not successful. For more information about error messages and problem resolution, see the "Query Errors" section.
Query LIDB Response Parameters
Additional parameters returned in response to a query lidb command include:
•
Calling-DN
•
Caller-ID Name String
•
Caller-ID Name Privacy
Query Toll-Free Parameters
The following additional parameters are returned in response to a query toll-free command:
•
Message-Type
•
Original Number
•
Translated Number
•
Carrier
•
Send-Notification-Received
Query LNP Parameters
The following additional parameters are returned in response to a query lnp command:
•
Original Number
•
Translated Number
Query Errors
An error can occur when a query command fails. This section specifies error responses and possible resolutions for problems.
Request Timeout
A query is sent to the Feature Server, but no response is received. The error response is similar to the following example:
query lidb; calling-dn=123247238723; opc-id=opc;QUERY ON FEATURE SERVER FSPTC235 IS ...->FSPTC235 -> No Reply received!Reply : Failure:The Feature Server did not respond to the query before a timeout occurred. Take the following steps to resolve the problem:
•
If it was an LIDB query, execute the nodestat command on the POTS Feature Server to confirm that it is Active.
•
If it was a Toll-Free or LNP query, execute the nodestat command on the AIN Feature Server to confirm that it is Active.
•
If the platform is Active, execute the following command to confirm that the SCA process is running:
ps -aef | grep scaIf the process is not running, start it through the Platform Debug Monitor (PDM) or by stopping and restarting the platform.
•
If the platform is Active, execute the following command to confirm that the TSA process is running:
ps -aef | grep tsaIf the process is not running, start it through PDM or by stopping and restarting the platform.
•
If the SCA and TSA processes are running on the Active platform, check the trace files for errors associated with the query.
SCP Timeout
The SCP does not respond to a query. The error response is similar to the following example:
query lidb; calling-dn=1232472387283; opc-id=opc;QUERY ON FEATURE SERVER FSPTC235 IS...->RESULT ->QVT query has timed outQUERYSTATUS -> Miscellaneous FailureReply : Success:Contact the SCP provider to find out why there is no error response returned from the SCP.
Missing Mandatory Parameter
The user performs a query but does not provide all required parameters. The error response is similar to the following example:
query toll-free; called-dn=8005550102; user-type=calling-dn; user-id=2182640018; lata=100; bearer-capability=speech; trigger-criteria=9;Required attributes missing:opc_idSupply all required parameters for the query. To view a list of parameters required for a command, enter a question mark (?) after the partial command. For example, query lidb? will display a list of required parameters for a LIDB query.
AIN 0.1 Query Attempted for IN/1 Configuration
An AIN 0.1 Toll-Free query has been performed, but the system specifies that the Toll-Free subsystem is IN/1. The error response is similar to the following example:
>query toll-free; called-dn=8005550102; user-type=calling-dn; user-id=2182640018; lata=100; bearer-capability=speech; trigger-criteria=9, opc-id=opc;Reply : Failure: Missing CALLING_DN for the IN/1 queryReissue the command in the IN/1 format. To see what message type is specified for the Toll-Free subsystem, enter the following command:
query toll-free-msg-type; opc-id=opc;MESSAGE-TYPE=IN1Reply : Success:IN/1 Query Attempted for AIN 0.1 Configuration
An IN/1 Toll-Free query has been performed, but the system specifies that the Toll-Free subsystem is AIN 0.1. The error response is similar to the following example:
query toll-free; called-dn=8005550102; calling-dn=2182640018; lata=100; trigger-criteria=9; opc-id=opc;Reply : Failure: Missing USER_TYPE for the AIN 0.1 queryReissue the command in the AIN 0.1 format. To see what message type is specified for the Toll-Free subsystem, enter the following command:
query toll-free-msg-type; opc-id=opc;MESSAGE-TYPE=AIN01Reply : Success:Parameter Boundary Error
The query can fail if you enter invalid data for a specific parameter. In the following example, a value outside the boundary of expected values for the trigger-criteria parameter has been specified:
query toll-free; called-dn=8005550102; calling-dn=2182640018; lata=100; trigger-criteria=12; opc-id=opc;Invalid parameter value.trigger_criteria=12; Enter one of the following values: [3,6,7,8,9,10].To resolve this error, enter a valid value for the specified parameter.
Record Does Not Exist
In the following example, a value has been entered for a LATA that has not been provisioned:
query toll-free; called-dn=8005550102; calling-dn=2182640018; lata=101; trigger-criteria=9; opc-id=opc;Reply : Failure: LATA 101 does not existTo resolve this error, enter a provisioned LATA.
Local Network Failure
When communication is lost between the Cisco BTS 10200 Softswitch and the ITP gateway, a local network failure may occur. The most likely reason for this error is that the SCTP association is Out Of Service. The error response is similar to the following example:
query toll-free; called-dn=8005550102; calling-dn=2182640018; lata=100; trigger-criteria=9; opc-id=opc;QUERY ON FEATURE SERVER FSAIN205 IS...->RESULT->MTP failure - occurs at SP (PC7-44-1, SSN=254)QUERYSTATUS -> Network FailureReply : Success:Perform the following to diagnose the problem:
•
Execute the query again with the table-info option set to yes
•
Determine the status of the SCTP associations used for this command. If the associations are Out Of Service, control the associations back into service.
Remote Network Failure
A failure has occurred at a point code other than the OPC. The query response will specify what problem has occurred and at which point code the problem is detected. In the following example, the point code of the STP is reporting a failure because there is no Global Title Translation entry in the STP GTT database for the calling-dn.
query lidb; calling-dn=9823456789; opc-id=opc;QUERY ON FEATURE SERVER FSPTC235 IS...->RESULT ->No translation for this specific address - occurs at SP (PC=1-101-0, SSN=0)QUERYSTATUS -> Network FailureReply : Success:status sctp-assoc;To resolve this error, add an entry to the STP GTT database to translate the calling-dn and route the query request to the LIDB subsystem on the SCP.
QVT Measurements
Table 1 identifies the measurements generated by the AIN Feature Server for the QVT featurette.
Table 2 identifies the measurements generated by the POTS Feature Server for the QVT featurette.
Translation Verification Tool
This section describes the Translation Verification Tool (TVT) and includes the following sections:
Overview
The TVT is a diagnostic tool that simulates a call from the originator to a specific destination based on dialed digits. It enables a user to check system translations and determine if routing will occur as expected without making a call.
Command Format
The TVT command uses the following format:
translate <line|trunk>; parameter=value;
Examples
translate line calling-dn=2189722345; called-dn=8005550102Syntax Description
* Calling-DN
The caller's directory number.
VARCHAR(10): 10 digits in the format npaxxxxxxx.
Called-DN
The called directory number.
translate trunk tgn-id= 1; called-dn=7034321234;Syntax Description
Response Format
Translation is the process of determining the destination of a call based on the dialed digits. The TVT performs translations and returns the tables traversed in order to reach the destination number. The TVT does not complete a call but only allows you to view the route of the call.
The following example illustrates an incoming line call terminating to a trunk.
translate line calling-dn=9722331286;called-dn=7034321234;TABLE: SUBSCRIBERID=sub1_ata2;CATEGORY=INDIVIDUAL;NAME=sub1;STATUS=ACTIVE;DN1=9722331003;PRIVACY=NONE;RING_ TYPE_DN1=1;TERM_ID=a00/1;MGW_ID=ata2;PIC1=NONE;PIC2=NONE;PIC3=NONE;GRP=N;USAGE_SENS=Y;SUB_ PROFILE_ID=northtexas;TERM_TYPE=TERM;IMMEDIATE_RELEASE=N;TERMINATING_IMMEDIATE_REL=N;SEND_ BILLING_DN=N;SEND_BDN_AS_CPN=N;SEND_BDN_FOR_EMG=N;TABLE: SUBSCRIBER_PROFILEID=northtexas;DIAL_PLAN_ID=dp1;LOCAL_PFX1_OPT=NR;TOLL_PFX1_OPT=RQ;POP_ID=1;OLI=0;EA_USE_PI C1=Y;TABLE: DIAL_PLAN_PROFILEID=dp1;DESCRIPTION=dialingplanprofile;NANP_DIAL_PLAN=Y;DNIS_DIGMAN_ID=dp1;TABLE: DIAL_PLANID=dp1;DIGIT_STRING=408555;DEST_ID=ssp1dest;SPLIT_NPA=NONE;DEL_DIGITS=0;MIN_DIGITS=10;MAX_ DIGITS=10;NOA=NATIONAL;TABLE: DESTINATIONDEST_ID=ssp1dest;CALL_TYPE=LOCAL;ROUTE_TYPE=ROUTE;ROUTE_GUIDE_ID=ssp1rg;ZERO_PLUS=N;INTRA_ STATE=Y;GAP_ROUTING=N;CLDPTY_CTRL_REL_ALWD=N;TABLE: ROUTE_GUIDEID=ssp1rg;POLICY_TYPE=ROUTE;POLICY_ID=ssp1route;TABLE: ROUTEID=ssp1route;TGN1_ID=1;DEL_DIGITS1=0;DEL_DIGITS2=0;DEL_DIGITS3=0;DEL_DIGITS4=0;DEL_DIGITS5 =0;DEL_DIGITS6=0;DEL_DIGITS7=0;DEL_DIGITS8=0;DEL_DIGITS9=0;DEL_DIGITS10=0;TG_SELECTION=RR;TABLE: TRUNK_GRPID=1;CALL_AGENT_ID=CA146;TG_TYPE=SS7;NUM_OF_TRUNKS=24;DPC=1-12-1;TG_PROFILE_ID=ssp1-tg-pro f;STATUS=INS;DIRECTION=BOTH;SEL_POLICY=ASC;GLARE=EVEN;ALT_ROUTE_ON_CONG=N;SIGNAL_PORTED_NU MBER=N;POP_ID=1;REMOTE_SWITCH_LRN=2122129999;DIAL_PLAN_ID=dp19;DESCRIPTION=TG to BTS12;DEL_DIGITS=0;OPER_STATUS=NF;TRAFFIC_TYPE=TANDEM;ANI_BASED_ROUTING=N;CLLI=DAL177DS3;C ALL_CTRL_ROUTE_ID=bts12-ccroute1;MGCP_PKG_TYPE=T;ANI_SCREENING=N;SEND_RDN_AS_CPN=N;Reply :Success:TVT Measurements
Table 3 identifies the measurements generated by the TVT.
Using QVT and TVT Together
It may be necessary to use both QVT and TVT queries to diagnose routing of a call. If the results of a translate command indicate that a Toll-Free or LNP query is generated, execute the QVT query. Use the results of the QVT query to generate another TVT query.
The following example illustrates verifying routing of a call from (972) 233-1286 to (800)555-3002:
Step 1
Execute a TVT translate command:
translate line calling-dn=9722331286; called-dn=8005553002;TRANSLATE LINE ON CALL AGENT CA146 IS...->TABLEINFO ->******TOLL FREE CALL NEEDS AN 800 QUERY******Reply : Success:The translate command indicates that a Toll-Free query is required.
Step 2
Perform the QVT query to do the number translation.
query toll-free called-dn=8005553002; calling-dn=9722331286; lata=100; opc-id=opc;TOLL FREE QUERY ON FEATURE SERVER FSAIN520 IS...->RESULT->OPC=7-2-1SSN=254TT-254SCP-Point-Code=1-101-0Message-Type=IN/1Called Number=8005553002Translated Number=7034323002Carrier=0000Reply : Success:Step 3
The translated number returned by the QVT query can now be used in a TVT translate command to verify call routing.
translate line calling-dn=9722331286;called-dn=7034323002;TRANSLATE LINE ON CALL AGENT CA146 IS... ->TABLEINFO ->TABLE: SUBSCRIBERID=sub_1_6;CATEGORY=INDIVIDUAL;NAME=sub16;STATUS=ACTIVE;ADDRESS1=1651 n glenville suite 200;ADDRESS2=Richardson tx 75081;BILLING_DN=9722331286;DN1=9722331286;PRIVACY=NONE;RING_TYPE_DN1=1;TERM_ID=aaln/S1/6; MGW_ID=c2421_1;PIC1=NONE;PIC2=NONE;PIC3=NONE;GRP=N;USAGE_SENS=Y;SUB_PROFILE_ID=sub_pmlhg_p rof1;TERM_TYPE=TERM;IMMEDIATE_RELEASE=N;TERMINATING_IMMEDIATE_REL=N;SEND_BILLING_DN=N;SEND _BDN_AS_CPN=N;SEND_BDN_FOR_EMG=N;TABLE: SUBSCRIBER_PROFILEID=sub_pmlhg_prof1;DIAL_PLAN_ID=dp1;LOCAL_PFX1_OPT=NR;TOLL_PFX1_OPT=RQ;LSA=9;POP_ID=1;OLI= 0;EA_USE_PIC1=N;TABLE: DIAL_PLAN_PROFILEID=dp1;DESCRIPTION=dialing plan profile ID 1;NANP_DIAL_PLAN=Y;DNIS_DIGMAN_ID=dp_svc;TABLE: DIAL_PLANID=dp1;DIGIT_STRING=703432;DEST_ID=ssp1-dest;SPLIT_NPA=NONE;DEL_DIGITS=0;MIN_DIGITS=7;MAX_ DIGITS=10;NOA=NATIONAL;TABLE: DESTINATIONDEST_ID=ssp1-dest;CALL_TYPE=LOCAL;ROUTE_TYPE=ROUTE;ROUTE_GUIDE_ID=ssp1-rg;ZERO_PLUS=N;INTR A_STATE=Y;GAP_ROUTING=N;CLDPTY_CTRL_REL_ALWD=N;TABLE: ROUTE_GUIDEID=ssp1-rg;POLICY_TYPE=ROUTE;POLICY_ID=ssp1-route;TABLE: ROUTEID=ssp1-route;TGN1_ID=3;DEL_DIGITS1=0;DEL_DIGITS2=0;DEL_DIGITS3=0;DEL_DIGITS4=0;DEL_DIGITS 5=0;DEL_DIGITS6=0;DEL_DIGITS7=0;DEL_DIGITS8=0;DEL_DIGITS9=0;DEL_DIGITS10=0;TG_SELECTION=RR ;TABLE: TRUNK_GRPID=3;CALL_AGENT_ID=CA146;TG_TYPE=SS7;NUM_OF_TRUNKS=24;DPC=1-12-1;TG_PROFILE_ID=ssp1-tg-pro f;STATUS=INS;DIRECTION=BOTH;SEL_POLICY=ASC;GLARE=EVEN;ALT_ROUTE_ON_CONG=N;SIGNAL_PORTED_NU MBER=N;POP_ID=1;REMOTE_SWITCH_LRN=2122129999;DIAL_PLAN_ID=dp19;DESCRIPTION=TG to BTS12;DEL_DIGITS=0;OPER_STATUS=NF;TRAFFIC_TYPE=TANDEM;ANI_BASED_ROUTING=N;CLLI=DAL177DS3;C ALL_CTRL_ROUTE_ID=bts12-ccroute1;MGCP_PKG_TYPE=T;ANI_SCREENING=N;SEND_RDN_AS_CPN=N;Reply : Success:
Feedback