|
|
The following sections contain the result type definitions for the result types listed in Table 2-44 and Table 2-47.
This result indicates insufficient digits for analysis to provide a meaningful result with which the call can be continued. The result type returns an indication to the call module of how many more digits are required for analysis to be completed (that is, it subtracts the number of digits returned in the analysis result type from the number of digits that have been received).
This result type gives a route list identity that is used as a startindex to the routing analysis process.
This result type returns information regarding the incoming trunk group side (OCC). This information sets the numbering criteria, (that is, overlap or en bloc) and the minimum and maximum permitted digits for that side.
Numbering Type —0 = Closed numbering (en bloc), 1 = Open numbering (overlap).
Minimum and Maximum digits—This refers to the minimum and maximum number lengths. (In the case of closed numbering, these values should be equal.)
This result type is for digit modification on either the A-number or B-number. The capability exists to remove x digits from any point in the digit string and replace them with whatever is required. An example of this is as follows:
If we get result type 4 to modify B-number, we receive the following fields:
Application point—The point in the digit string to apply modification (in the range from 1 through the length of the digit string).
Number of digits to remove—Removes x digits (if required), the range is from 1 to the length of the digit string.
Modification index—If required, entry to the table containing digit strings to insert at the application point.
If the application point is set to 1, then begin at the start of the digit string and remove digits from there, if required.
Application point 1, remove = 5, mod index gives a result of 1321.
B number received pre-analysis: 01444 567891
B number post analysis: 1321 567891
It is possible to provide a release cause code as a result from analysis which then will be used in REL and cleardown messages as the call is cleared. This result type provokes a negative result from analysis, and the cause will be identified. Currently, the given cause value is passed into the new cause analysis process and by table analysis the decision is made whether or not to:
1. Reattempt the call on an alternate route.
2. Return an announcement, (that is, route to the announcement server).
3. Clear the call down, writing the cause value returned into call context for protocol use.
The cause code corresponds to any provisioned value that complies with the range of cause values permitted in call context. Refer to "NOA and NPI Codes," for cause code values.
This result type provides an announcement ID, local or remote indication, and route ID. These fields are defined as follows:
This result type indicates that the calling party category has not been supplied and is required for the outgoing side. Where the originating protocol supports backward requests, this information can be retrieved by an internal request signal. If the protocol does not support backward requests, then the call progresses without this information and it is left to the succeeding exchange to determine if it is required, and thus determines the call's fate.
This result type indicates that the calling line identity has not been supplied and is required for the outgoing side. Where the originating protocol supports backward requests, this information can be retrieved by an internal request signal. If the protocol does not support backward requests, then the call progresses without this information, and it is left to the succeeding exchange to decide if it is required, and thus determines the call's fate.
This result type indicates that the basic service markings have not been supplied and are required for the outgoing side. Where the originating protocol supports backward requests, this information can be retrieved by an internal request signal. If the protocol does not support backward requests, then the call progresses without this information, and it is left to the succeeding exchange to decide if it is required, and thus determines the call's fate.
This result type indicates that the facility service markings have not been supplied and are required for the outgoing side. Where the originating protocol supports backward requests, this information can be retrieved by an internal request signal. If the protocol does not support backward requests, then the call progresses without this information, and it is left for the succeeding exchange to determine if it is required, and thus determines the call's fate.
This result type provides the capability to change the A-number or B-number type from that presented in the setup message. The value given as data in the result type (Data Word 1) will be the internal call context value for the nature of address (NOA) relating to either the A-number or B-number. This field is explained as follows:
This result type returns information regarding the outgoing trunk group side (Terminating Call Control). This information sets the numbering criteria (that is, overlap or en bloc), and the minimum and maximum permitted digits for that side.
Numbering Type—0 = Closed numbering (en bloc), 1 = Open numbering (overlap).
Minimum and Maximum digits—This refers to the minimum number length and the maximum number length. (In the case of closed numbering, these values should be equal.)
This result type provides a basic capability to be able to call screen A-numbers by digit tree analysis. The possible result types (screening criteria) and their application are as follows:
Screening criteria—1 = CLI, 2 = Dialed address, 3 = CPC, 4 = NOA
If such a result is received, the call will be released with cause IC_BLACKLIST_CLI_MATCHED being applied.
This result type basically indicates that the calling line identity has the incorrect number of digits. The Numbering Type field is not processed, but the maximum and minimum digit fields are used to determine if the CLI is too long or too short. If so, a negative result is returned, cause is set to IC_BLACKLIST_CLI_LENGTH_INVALID, and the call is released.
This result type delivers a result from A-number analysis. The data provided (route preference) is set according to the internal call context values for route preferences and is used during the routing process to bias the selection of trunk groups made. The possible values are as follows:
Route pref—This can take one of the following values:
This result type delivers a result from B-number analysis indicating that further analysis by an SCP is required (IN call). The data provided identifies the service required (for example, LNP) and if necessary an SCP index for use when the TCAP call is made.
Service Type—This returned value is provisioned in the $TriggerTable (a table within an external file used to configure the handling of IN requests by the trigger module). The value returned is not processed within analysis, but is retrieved and passed back to the call module for action. This value is an indication of the type of IN service that needs to be invoked to advance this call (for example, LNP, 800, 900, and so on).
SCP/STP Index—Index value to be used in the trigger module for selection of the SCP for TCAP query.
This result type delivers a result from either A-number or B-number analysis indicating that a call must be made to the main memory database to carry out call screening on the A-number. Data Word 1 (Screen Type) identifies the type of screening that must be requested.
ScreenType—1 = White list, 2 = Black list
ServiceID—This is an integer value used to identify the particular database list of A-numbers that are appropriate to this B-number (that is, when this B-number is called, the A-numbers that must be screened). This value is used as an index to read the service table from where a provisioned servicename (string) can be obtained. The service name is then passed as read into the database when the screening request is made.
Examples of service name string values are as follows:
Call screening is a type of analysis done on the digit string to determine if the call is accepted or rejected.
In the case of white list screening, the call is completed if the digit string is configured, or the call is terminated if the digit string is not configured. See Figure A-1 for an example of white list screening from the A-digit tree.
In the dial plan, the digit string 301 was connected to the SCREENING result type from the A-digit tree. When the digit string was connected, it was associated with white list screening. When a customer dials with a calling number 301, the calling number is screened to see if it is configured. In the white list example, the call is allowed through if it is configured, or the call is terminated if it is not configured.
In the example shown in Figure A-1, if the calling number is 301648444, the call is terminated because it is not configured in the white list. However, if the calling number is 3016485555, it is connected because it is configured in the white list.
In the case of black list screening, the call is terminated if the digit string is configured or completed if the digit string is not configured. See Figure A-2 for an example of black list screening from the A-digit tree.
In the dial plan, the digit string 301 was connected to the SCREENING result type from the A-digit tree. While the digit string was connected, it was associated and with black list screening. In this example, when a customer dials with a calling number 301, the calling number is screened to see if it is configured for the Washington service. In the black list example, the call is terminated if the called number is configured in the black list. However, the call is completed if it is not configured in the black list.
In the example shown in Figure A-2, if the calling number is 301648444, the call is connected because it is not configured in the black list. However, if the calling number is 3016485555, it is terminated because it is configured in the black list.
Number screening is used to verify if a call can be completed. In the case of white list screening, the call is completed if the called digit string is configured with a service and the calling number is associated with the same service in the screening table; otherwise, the call is terminated. See Figure A-3 for an example of white list screening from the B-digit tree.
In the dial plan, the digit string 7034 was connected to the SCREENING result type from the B-digit tree. When the digit string was connected, it was associated with the Washington service and white list screening. In this example, when a customer dials a called number with 7034, the calling number is screened to see if it is configured for the Washington service. In the white list example, when the calling number is screened, the call is connected if it is configured for the Washington service. However, when the calling number is screened, the call is terminated if it is not configured for the Washington service.
In the example shown in Figure A-3, if the calling number is 301648444, the call is terminated because it is not configured in the white list for the Washington service. However, if the calling number is 3016485555, it is connected because it is configured in the white list for the Washington service.
In the case of black list screening, the call is terminated if the called digit string is configured with a service and the calling number is associated with the same service in the screening table; otherwise, the call is connected. See Figure A-4 for an example of black list screening from the B-digit tree.
In the dial plan, the digit string 7034 was connected to the SCREENING result type from the B-digit tree. When the digit string was connected, it was associated with the Washington service and black list screening. In this example, when a customer dials a called number with the 7034, the calling number is screened to see if it is configured for the Washington service. In the black list example, when the calling number is screened, the call is terminated if it is configured for the Washington service. However, when the calling number is screened, the call is connected if it is not configured for the Washington service.
In the example shown in Figure A-4, if the called number is 301648444, the call is connected because it is not in the black list for the Washington service. However, if the called number is 3016485555, it is terminated because it is configured in the black list for the Washington service.
This result type delivers a result from B-number analysis indicating that there are actions required to move certain data from one call context location to another. For example, if the result indicates a home-based local routing number (LRN), then the called party number and the generic address parameter (GAP) number must be exchanged, and then new B-number analysis is invoked. The associated field "ActionType" indicates the type of action that is required.
ActionType—Currently the only value is:
This number is a home LRN, that is, local to this MGC. This signifies that the MGC must complete the call to the dialed number contained in the GAP (not the number in the called party number). Consequently the GAP and called party numbers must be exchanged.
Posted: Wed Sep 27 12:55:49 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.