4.2.10 MSRN Analysis
I. Description
MSRN is a flag of the location where the subscriber of the local network is roaming. The MSC where the subscriber of the local network is roaming can be known by MSRN. There are four types of MSRN to be
conFigured in local MSC according to different roaming locations of the local MS:
1) MSRN allocated by the local MSC: the subscriber active within the local MSC.
2) MSRN allocated by other MSCs of the local network: the subscriber active within other MSCs of the local network.
3) MSRN allocated by MSCs of other national networks: the subscriber is roaming in one of other domestic networks.
4) MSRN allocated by MSC of international other networks: the subscriber is roaming in the network other than that in the home country.
Among the above-mentioned four types of numbers, only MSRN of 1) type does not need to be sent out to other office and can page the mobile subscriber after number analysis. MSRNs of other three types will be sent out after number analysis.
All MSRN must be conFigured in [Called Number Analysis] table.
II. Example
The principle for configuring MSRN in the [Called Number Analysis] table:
MSRN allocated by the local MSC is generally conFigured as NDC + SN. MSRN allocated by MSC of international other network is conFigured as International Prefix + International number. The format of MSRN allocated by other MSCs of the local network and MSCs of other national network must be conFigured as required by the peer office.
Precondition:
The number format of MSRN in SRI Ack message is CC + NDC + SN (the number attribute is INT). After Black Box conversion described in TP-004, the number format of MSRN before querying [Called Number Analysis] is:
National MSRN: NDC + SN
International MSRN: International Prefix + International number.
The following will introduce the configurations in [Called Number Analysis]:
1) MSRN allocated by the local MSC: Send the number directly to its destination after number analysis in the local MSC. Therefore, conFigure the table as follows: "Service property" = "PLMN local office", and "Called number type" = "MSRN/HON". The
"route selection code" is not required to be conFigured, because it is unnecessary to send the number out.
2) MSRN allocated by other MSCs of the local network and MSCs of other national networks: valid "route selection code" must be conFigured for outgoing route selection. In addition, "Service property" must be conFigured as required by the peer end, i.e. if the peer end requires that the number property should be NAT, it can be conFigured as "PLMN national toll office", and "Called number type" = "MSRN/HON".
3) MSRN allocated by MSC of international other networks: conFigure "Number prefix set" = 9 (The value is defined in "MAP prefix set" in the [Software Parameter] table and the default value is 9). Valid "route selection code" must be conFigured for outgoing route selection. "Service property" is recommended to be conFigured as "PLMN international toll office", and "Called number type" = "MSRN/HON". Moreover, valid "Service index" must be conFigured. When this value is indexed to the [Call Barring Service] table, no items in the "call barring service of caller" field is selected, i.e. no call barring check is performed. The purpose of such configuration is not to perform call barring check to MSRN. For example, although the caller has subscribed to ODB_BOIC service, i.e. international calls barred, this subscriber is still allowed to call a subscriber roaming outside of its home country.
Note:
If the local office is interconnected with the peer office through ISUP, the value of "Nature of address indicator" in IAM message must be correct. This value can be SUB, NAT, INT and UNKNOWN, depending on the configuration of "Service property" in [Called Number Analysis], as shown in the following table:
If the "Nature of address indicator" of the outgoing call cannot meet the requirement of the peer end, it can be changed with the help of the [Outgoing Number Format] table and [Number Change] table.
4.2.11 MSISDN Number Analysis
I. Description
Three types of MSISDN must be conFigured at the local office:
1) MSISDN of local subscribers
2) MSISDN of MS of other national network
3) MSISDN of MS of international network
Among the above-mentioned three types of numbers, only 1) does not need to be sent out of the local MSC and can be directly sent to its home HLR to obtain MSRN. Other two types will be sent out of the local MSC after number analysis.
Since the [Called Number Analysis] table is the core for number analysis, MSISDN analysis is also done in this table.
II. Example
Principle for configuring data in the [Called Number Analysis] table:
MSISDN of MS of the local network is generally conFigured as NDC + SN. MSISDN of MS of international network is conFigured as International Prefix + International number, while the number format of MSISDN of MS of other national networks must be conFigured as required by the peer MSC.
Precondition:
The local office may receive MSISDN from two directions, one from the mobile subscriber side and one from other office direction. After number normalization in number pre-analysis described in TP-003 and TP-004, the number format of MSISDN before querying [Called Number Analysis] should be:
MSISDN of MS of the local network: NDC + SN
MSISDN of MS of other national networks: conFigure it as required by the peer end
MSISDN of MS of international network: International Prefix + International number
The following will introduce configurations in [Called Number Analysis]:
1) MSISDN of MS of the local network: Obtain MSRN after number analysis. ConFigure it as below: "Service property" = "PLMN local office", and "Called number type" = "MSISDN". "Route selection code" is not required, because the call is not necessary to be sent out of the local MSC.
2) MSISDN of MS of other national networks: valid "route selection code" must be conFigured for outgoing route selection. In addition, "Service property" must be conFigured as required by the peer end, i.e. if the opposite end requires that the number property should be NAT, it can be conFigured as "PLMN national toll office". If
other properties are required, conFigure with reference to the description in "Note" in TP-010, and "Called number type" = "PSTN".
3) MSISDN of MS of international network: conFigure "Number prefix set" as the value defined in the [Call Source] table. Valid "route selection code" should be conFigured for outgoing route selection. "Service property" is recommended to be conFigured as "PLMN international toll office"; and "Called number type" = "PSTN"."
4.2.12 Analysis of PSTN and Special Number
I. Description
Since PSTN and Special numbers do not belong to local MSC, the local MSC will route them to other MSCs if it receives these numbers.
Since the [Called Number Analysis] table is the core of number analysis, analysis of PSTN and Special number should also be conducted in this table.
After number pre-analysis described in TP-003 and TP-004, generally the number formats of PSTN and Special number before querying [Called Number Analysis] should be:
1) Local PSTN: SN format or Domestic Prefix + Area Code + SN
2) Special number: SN format
3) National toll PSTN: Domestic Prefix + Area Code + SN
4) International toll PSTN: International Prefix + International number
These formats are applicable to common cases. For specific requirements, conFigure them as required.
The property of the outgoing number must be correct. For configuration methods, please refer to the description in the "Notes" in "MSRN Analysis".
II. Example
None.
4.2.13 Number Conversion during Number Analysis
I. Description
Number conversion can be carried out flexibly in many phases according to the complexity of data configurations, either number pre-analysis phase, number analysis phase or sending number phase.
The following introduces how to conduct number conversion during number analysis.
The core of number analysis is to query [Called Number Analysis], where all numbers must be conFigured. The query sequence is:
Figure 4-27 Query sequence of number analysis
If the caller number is to be changed, conFigure "CLI analysis flag" in the [Called Number Analysis] table as YES and then conFigure the [Caller Number Analysis] table, in which both the caller number and the called number can be changed. If the called number is to be changed, number prefix analysis is recommended, i.e. conFigure "Prefix processing flag" in the [Called Number Analysis] table as YES and then conFigure the [Number Prefix Processing] table, in which both the caller number and the called number can be changed. In addition, function of number analysis is also added to this table, such as disconnecting the call and number re-analysis (note) after number change, etc.
Note:
Re-analysis means querying [Called Number Analysis] table again.
II. Example
In Example section of TP-008, the [DN Pre-analysis] table is used for number conversion. Since numbers can also be converted in the [Number Prefix Processing] table according to the call source code, number conversion mentioned above can also be implemented in this table.
Data configurations are as follows:
Figure 4-28 [LAI and GCI] table
Figure 4-29 [Call Source] table
Figure 4-30 [Called Number Analysis] table
Figure 4-31 [Number Prefix Processing] table
Figure 4-32 [Number Change] table
4.2.14 Sending Number Analysis
I. Description
This part is divided into four sub-modules: CDR number processing module, call line identification presentation (CLIP) processing module, outgoing trunk number processing module and other number processing module.
- CDR number processing module is to process the formats of the caller number, called number and the third party number in the bill.
- CLIP processing module is to process the number presentation requirements of different countries.
- Outgoing trunk number processing module is to meet various requirements for number formats in the signaling of different countries.
- Other number processing module is to normalize the numbers infrequently used.
The table-querying sequence of the sending number processing part is shown in the following diagram:
Figure 4-33 Sending number processing
Number processing of this part has the following features:
1) Number conversion of respective processing modules only converts the output number formats, not the input number formats. For example, after number analysis, caller numbers should be sent respectively to the billing center and the called mobile subscriber for CLIP, so they should be converted to meet the respective requirements of the billing center and CLIP for caller number formats. [CDR Number Format] table and [CLI Presentation] table should be used for caller number conversion. Although the caller number to be converted is the same, the conversions are done separately, i.e. when the caller number has been converted in [CDR Number Format] table, only the caller numbers sent to the billing center is changed.
2) There are two number conversion modes for all the processing modules:
- Basic conversion: With the number conversion index, conversion is implemented through the [Number Change] table, in which numbers can be added, deleted, changed and extracted, and number types and attributes can also changed when necessary.
- Convert to a specific number format: Optional number output formats are the following six: subscriber format, national number format with prefix, national number without prefix, international number format with prefix, international number without prefix and unspecified number format. After specifying an output number format, number format conversion can be automatically implemented.
In these tables for sending number conversion, the above two methods, basic conversion and convert to a specific number format, cannot be implemented simultaneously.
4.2.15 Changing Calling Party number for CLIP
I. Description
Requirement for number identification presentation varies from country to country. For example, when the caller is an mobile subscriber, the following identification presentation format is required in Russia and Thailand: prefix of area code + NDC + SN, while that in China is NDC + SN. [CLI Presentation] is conFigured to meet the requirements for CLIP.
II. Example
1) Example of CLIP in Russia
For national MSISDN, the following identification presentation format is required: prefix of the area code + NDC + SN, while for fixed telephones: prefix of the area code + area code + SN. The NDC Russia include 095, 902, 916 and 910, and the configuration results are shown in the following table:
Figure 4-34 CLI presentation table
The caller and called are not required to be associated, so the [Called Info Indicator] is blank.
For all the MSs of national network, make sure that the number attribute of an MS with NDC is NAT, then specify the number as "NAT with prefix" in the [Number Format] field in the table.
In the [Caller Analysis] table, caller number conversion and specified number format processing are found coexistent, and their sequence relationship is described here. The program performs number conversion first, converting a number into one with uniform format and attributes, then it processes them into specified format (i.e., sent-number processing table, other number sending processing tables and CDR number processing table). For fixed numbers, the program configuration by default is area code prefix + area code + SN, and an international number is an international number by default, therefore, it is unnecessary to conFigure these numbers.
2) Example of CLIP in Thailand
If the called subscriber is an international roaming one, the caller identification presentation format is the international number, that is, country code + access number (area code) + SN. Configuration is shown in the following Figure:
Figure 4-35 CLI presentation
As the caller and called should be associated, the [Called Info Indicator] is 0, which associates this table with the [CLD Info for CLI Presentation] table, thus associating the caller and called numbers.
Figure 4-36 CLD info for CLI presentation
ConFigure two records in [CLD Info for CLI Presentation] table. The first one is used when the called is an international roaming subscriber, and 810 is the prefix of an international number, displayed as the international format without any prefix (e.g.: + 86139*******). The second one is a common called number, displayed as the national format with a prefix ("E" in the column represents wildcard).
4.2.16 Converting the Number Sent to Billing Center
I. Description
CDR is crucial, and incorrect CDR number format will bring confusion in the billing center conversion. The CDR number processing requirements can be met by configuring [CDR number Format] table and [Number Change Table].
II. Example
1) Case 1
In a certain country, the following identification presentation format is required for CDR numbers: prefix of the area code + access number + SN, while for the fixed telephones: prefix of area code + area code + SN. The access numbers of this country include 095, 902, 916 and 910, and the configuration is shown in the following table:
Figure 4-37 Configuration of CDR number format table
Figure 4-37 shows part of the data table. For all the MSs of national network, the MS number is specified as a national number with a prefix, regardless of the number of caller CDRs (MOC), called CDRs(MTC), forwarding CDRs(CFW), roaming CDRs(GWI) and out-gateway CDRs(GWO).
2) Case 2
Numbers in a short message CDR are required to be in the format of national format with a prefix or international format with a prefix, and the configuration examples are as follows:
Figure 4-38 Configuration of CDR number format table
Only the processing of the CDR of the called in a short messages (MT_SMS) is listed here. Because no number attribute but a number is transmitted when the short message center sends short messages to MSC, the default program processing is as follows: First check whether the prefix of this number includes any international number, if any, it proves that this number is in the international format. Otherwise, check whether the prefix includes any access number, if any, it is a national number, and others are unknown numbers. The international number table includes all the numbers, therefore, when querying the CDR number processing table, both the caller number and called number in a short message CDR are in the international format. All called numbers of a called CDR in a short message (MT_SMS) are in the international format (the caller numbers of a caller CDR in a short message (MO_SMS) are also in the international format). Therefore specify the format as the international number with a prefix. A caller number may include national numbers with prefixes, therefore the number attribute is changed from the INT into NAT after number conversion " the index number is 198".
4.2.17 Convert Caller/Called Numbers Sent to Trunk
I. Description
The formats of caller numbers and called numbers transmitted on the signaling vary from country to country and from operator to operator. For example, the requirement in Thailand is: national numbers are transmitted in the national number format and international numbers are transmitted in the international number format without any prefix. The requirement in Russia is: international numbers are transmitted in the international number with prefix.
To meet the above requirements for outgoing trunk number processing, a table is created to implement only the processing of the caller and called numbers on ISUP, TUP and R2 signaling, and [Outgoing Trunk Number Format Table], [Caller Info For Outgoing Trunk Table] and [Number Change Table] will be queried during the processing.
II. Example
Requirements for the numbers being transmitted is like this in an MSC: national numbers are to be transmitted in the national number format, and international numbers are to be transmitted in the international number format without any prefix. The table should be conFigured as follows:
Figure 4-39 Outgoing trunk number format
The caller and called are not required to be associated in the table, so the [Called Info Indication] in the table is left blank, and its value can be obtained by querying [Outgoing Trunk Number Format] table.
In the above table, the first record is an international called number (001 is the international number prefix), and is specified as in the format of the international numbers without prefix, and the program will automatically remove its national prefix. The second record in the table is a called number of other type, and is specified as in the format of national number with prefixes.
4.2.18 Processing of Other Number Sending
I. Description
Requirements are different on the formats of redirected numbers, Org called numbers and connected numbers for different countries.
Numbers that are not closely associated and whose configurations are seldom changed can be combined into one table to facilitate operator’s configuration. And the processing can be accomplished by the configuration of the above-mentioned table and by querying [Other Number Format] and [Number Change] table.
Configuration combinations in the table can satisfy the requirements for number change in various conditions, that is:
1) Change the format of connected number.
2) Change the format of numbers which are sent to SCP in the INITIAL_DP message.
Remarks: Before [Other Number Format] table is queried, system will perform a default number conversion to automatically normalize numbers so as to simplify data configuration. Now the default processing is as follows: All the numbers reported to SCP are normalized into the international number format, and the number attribute is INT.
3) In case of number forwarding, the format of the redirection number carried when the call forwarding notification is sent to the originating office is as the following.
4) When the call is forwarding to other MSC, the sending out format of Redirecting number and the Org called number can be changed as the following:
5) The format of MSISDN carried when requesting from HLR for MSRN is as the following:
II. Example
- Change of outgoing numbers
When the outgoing numbers of trunk signaling are processed, i.e. the numbers of IAM message are processed, only Redirecting number and Org called number are processed.
1) The Redirecting number and Org called number in the outgoing trunk IAM message can be conFigured in the international format with the following configurations:
Figure 4-40 [Other Number Format] table configuration
As shown in the above table, Redirecting numbers and Org called numbers of all the office directions are specified as in the international format.
2) In an MSC, if forwarding takes place in the mobile network for the IAM message to the analog network, "0001" should be added to Org called number.
Suppose the office direction to the analog network is 1, the record with the number change table index being 200 should be added with "0001" at the end of the number, as shown in the following Figure.
Figure 4-41 [Other Number Format] table configuration
- Conversion of incoming numbers
The Redirection numbers in forwarding notification and connected numbers in the ANM can be handled during the incoming number processing.
An MSC requires Redirection numbers and Connected numbers in the international format, so the configurations are as follows:
Figure 4-42 [Other Number Format] table configuration
- Number conversion at MS side
When numbers are sent to the MS side, connected numbers in the "connect" message of the ANM can be processed. Data configurations are as the following:
Figure 4-43 [Other Number Format] table configuration
- Number Conversion at HLR side
When the numbers sent to HLR are processed, Called numbers obtaining routes and the numbers switched when obtaining called data can be processed.
Called numbers obtaining routes at HLR and the switched numbers obtaining called data at VDB are in international formats by default, so it is unnecessary to conFigure them. If called numbers obtaining routes are required to be in the national formats, modify the software parameters of MAP and conFigure [Other Number Format] table, as shown in Figure 4-44:
Figure 4-44 [Other Number Format] table configuration
- Number conversion at SCP side
For the processing of the numbers sent to SCP, process the caller numbers, Org called numbers, Redirecting numbers and User define1 (the BCD Called number).
The numbers sent to SCP are in international formats by default, so it is unnecessary to conFigure them. If any number format is found incorrect, conFigure it according to the above Figure, but change the destination into SCP.
4.2.19 Insert a Number
I. Description
Number conversion can be performed by the following method:
1) Change the attribute and type of the number
2) Number insertion, number deletion (in positive/inverted sequence), number change (in positive/inverted sequence), and number extraction (in positive/inverted sequence) at/after/before specified positions.
3) Number insertion, number deletion (in positive/inverted sequence), number change (in positive/inverted sequence), and number extraction (in positive/inverted sequence) at/after/before specified character.
Each type of number conversion method is detailed in Interface Reference Manual. The method of inserting numbers is described in detail below, similar with that of number change and number deletion.
II. Example
There are four modes to insert a segment of numbers at a specific position of a number.
- Insert Numbers at a Specified Position
When the value of "Change type" is "Insert at X pos", the system will insert a segment of numbers specified by the value of "New number" and "Other number source" at the position specified by the parameter "Start position". To insert numbers at a specified position, the fields to be conFigured are: Number change index, Change type, Start position, New number first, New number and Other number source. The valid value range of "Start position" is 0~number length (including 0 and number length).
Suppose the number to be changed are the called number 11893543 and its calling number is 865556, conFigure the fields as follows:
Figure 4-45 [Number Change] table configuration
The number change results are:
When the number change index is 1, after successful number change, change result is 90913823344056.
When the number change index is 2, after successful number change, change result is 138233440567532066.
When the number change index is 3, after successful number change, change result is 139097532066823344056.
When the number change index is 4, after successful number change, change result is 137532066909823344056.
When the number change index is 5, after successful number change, change result is 1313823344056823344056. This configuration is not recommended although it is supported by the system.
When the number change index is 6, the value at Start position is greater than the number length 11, so number change fails, and the change result is 13823344056.
When the number change index is 7, the number length after change is 28, which is beyond the maximum length of the called number, so number change fails, and the change result is 13823344056.
- Insert Numbers at the End of the Number to be Changed
When the value of "Change type" is "Insert in the end", the system will insert a segment of numbers specified by "New number" and "Other number source" at the end of the number to be changed. To insert numbers at the end of the number to be changed, the fields to be conFigured are: Number change index, Change type, New number first, New number and Other number source.
Suppose the number to be changed is the called number 13823344056 and its calling number is 7532066, conFigure the fields as follows:
Figure 4-46 [Number Change] table configuration
The change results are:
When the number change index is 1, after successful number change, change result is 13823344056909.
When the number change index is 2, after successful number change, change result is 138233440567532066.
When the number change index is 3, after successful number change, change result is 138233440569097532066.
When the number change index is 4, after successful number change, change result is 138233440567532066909.
When the number change index is 5, after successful number change, change result is 1382334405613823344056. This configuration is not recommended although it is supported by the system.
When the number change index is 6, the number length after change is 28, which is beyond the maximum length of the called number, so change fails, and the change result is 13823344056.
- Insert Numbers after the Specified Character
When the value of "Change type" is "Insert after char", the system will insert a segment of numbers specified by "New number" and "Other number source" after the first character equal to the "Specified character". To insert numbers after the specified character, the fields to be conFigured are: Number change index, Change type, Specified character, New number first, New number and Other number source. The valid value range of "Specified character" is 0~E (including 0 and E), of which, 0~9 are most often used.
Suppose the numbers to be changed is the called number 13823344056, and its calling number is 7532066, conFigure the fields as follows:
Figure 4-47 [Number Change] table configuration
The change results are:
When the number change index is 1, after successful number change, change result is 13909823344056.
When the number change index is 2, after successful number change, change result is 138275320663344056.
When the number change index is 3, after successful number change, change result is 138233490975320664056.
When the number change index is 4, after successful number change, change result is 138233475320669094056.
When the number change index is 5, after successful number change, change result is 1382334138233440564056. This configuration is not recommended although it is supported by the system.
When the number change index is 6, the specified character "7" does not exist in the number to be changed, so change fails, and the change result is 13823344056.
When the number change index is 7, the number length after change is 28, which is beyond the maximum length of the called number, so change fails, and the change result is 13823344056.
- Insert Numbers before the Specified Character
When the value of "Change type" is "Insert before char", the system will insert a segment of numbers specified by "New number" and "Other number source" before the first character equal to the "Specified character". To insert numbers before the specified character, the fields to be conFigured are: Number change index, Change type, Specified character, New number first, New number and Other number source. The valid value range of "Specified character" is 0~E (including 0 and E), of which, 0~9 are most often used.
Suppose the number to be changed are the called number 13823344056, and its calling number 7532066, conFigure the fields as follows:
Figure 4-48 [Number Change] table configuration
The change results are:
When the number change index is 1, after successful number change, the number will be 19093823344056.
When the number change index is 2, after successful number change, the number will be 138753206623344056.
When the number change index is 3, after successful number change, the number will be 138233909753206644056.
When the number change index is 4, after successful number change, the number will be 138233753206690944056.
When the number change index is 5, after successful number change, the number will be 1382331382334405644056. This configuration is not recommended although it is supported by the system.
When the number change index is 6, the specified character "7" does not exist in the number to be changed, so change fails, and the number will be 13823344056.
When the number change index is 7, the number length after change is 28, which is beyond the maximum length of the called number, so change fails, and the number will be 13823344056.
4.2.20 Number Extraction
I. Description
Number extraction means to extract part of a specific number and store it in the switch, and to add it to a specific position of other numbers when necessary. The system defines a Special number for storing the numbers extracted from other numbers. Currently one number can be extracted in the system.
II. Example
For calls between the analog network and GSM digital network, additional number CAC (Charge Area Code) should be transferred as the last 4 digits of the number.
Suppose the local office is an MSC tandem exchange, the preceding exchange is a VMSC linked via ISUP singling, while the destination exchange is analog network MSC, linked via TUP signaling:
CAC should be extracted from the called number of an incoming call, and then be added after the last digit of the calling number of the outgoing signaling.
Example: Suppose 1-185XXXX is an analog network subscriber number, 1-199-XXXX is a GSM digital network subscriber number, of which 1 is NDC.
Data configurations are as follows:
Figure 4-49 [DN Pre-analysis] table configuration
Figure 4-50 [Number Change] table configuration
Note:
"Change type" as "Get before & including x pos" means extracting numbers leftward from the specified position.
Figure 4-51 [Outgoing Trunk Number Format] table configuration
Figure 4-52 [Caller info for outgoing trunk] table configuration
Figure 4-53 [Number Change] table configuration
4.2.21 Assign Number Attribute
I. Description
In ISUP signaling, each kind of numbers carried in the message has one "Nature of address indicator (Number attribute)", which indicates the attribute of the number such as SUB, NAT, INT and UNKNOWN. Some exchanges will abort the call if the "Nature of address indicator" in the message received from the opposite exchange is not consistent with the number content. Therefore, flexible assignment of "nature of address indicator", applicable to all phases of number conversion, is provided to address this problem. If the "Nature of address indicator" by default does not meet the requirements of the opposite end, flexible assignment is carried out when the number is being sent out of the local MSC.
The mapping between the number content and Nature of address indicator is shown in the following table.
II. Example
Suppose a number 902XXXXXXX in IAM is transmitted to the opposite MSC with correct number content, but the Nature of address indicator is not in the NAT format as required by the opposite end, data should be conFigured as follows:
Figure 4-54 [Outgoing Trunk Number Format] table configuration
Figure 4-55 [Number Change] table configuration
4.2.22 Number Replacement
I. Description
Number replacement means a type of numbers can be replaced by another, not a single number can be replaced by another. Currently, there are four kinds of numbers available for replacing other types of numbers: Caller number, Called number, Original Called number and Redirecting number.
II. Example
In an MSC, International prefix = 001, when local MS dials an MS roaming outside the home network, the CallingPartyNumber in the IAM signaling sent to international gateway is replaced by the MSISDN of the called MS. But if it dials an MS of the network outside its home country, there is no such a requirement.
Data configurations for these cases:
Under the two cases, the international MSRN and international MS number are to be sent to international gateway in the format of International Prefix + International MS number. The system differentiates the two cases by [Number Prefix Set] in [Called Number Analysis] table, i.e., [Number Prefix Set] = 9 means international MSRN, and otherwise it means international subscriber number. After the international MSRN and international subscriber number can be differentiated, conFigure [Called Number Analysis] table as follows:
Figure 4-56 [Called Number Analysis] table configuration
[Destination Code for Call] in the above Figure is used to differentiate the international MSRN and international MS number with prefix as 001 in [Outgoing Trunk Number Format] table. For [Destination Code for Call], refer to TP-025. [Outgoing Trunk Number Format] table is conFigured as follows:
Figure 4-57 [Outgoing Trunk Number Format] table configuration
For calls whose Destination Code for Call is 1 and whose Called Number Prefix is 001, i.e., international MS number, they can be directly sent out without any conversion.
For calls whose Destination Code for Call is 2 and whose Called Number Prefix is 001, i.e., international MSRN, conFigure [Caller Info Indicator] field with valid value for querying auxiliary tables to convert numbers (refer to TP-023 for the configuration of auxiliary tables).
Figure 4-58 [Caller Info for Outgoing Trunk] table configuration
Figure 4-59 [Number Change] table configuration
