SCCP:GTT Association Configuration
From TBwiki
(Difference between revisions)
(initial clean-up) |
(clean up) |
||
Line 1: | Line 1: | ||
− | The | + | The GTT Association Configuration step is used to configure associations for Global Title Translation of the SCCP layer. An association specifies the translation procedure to be used for a particular type of global title. The user configures an association for each global title type in SCCP. |
− | The following enumeration lists the different configuration parameters and their | + | |
+ | The following enumeration lists the different configuration parameters and their descriptions: | ||
*The '''Network identifier''' parameter specifies the ID of the network | *The '''Network identifier''' parameter specifies the ID of the network | ||
− | *The '''Protocol variant''' parameter specifies the SCCP protocol variant. Allowable values: see | + | *The '''Protocol variant''' parameter specifies the SCCP protocol variant. Allowable values: see the SCCP protocol variant table in [[Toolpack:Create a SSCP network]]. |
Line 11: | Line 12: | ||
*The '''Global title format''' parameter specifies the SCCP GT format. Allowable values are: | *The '''Global title format''' parameter specifies the SCCP GT format. Allowable values are: | ||
+ | |||
{| class="wikitable" border="1" | {| class="wikitable" border="1" | ||
− | ! width="150" style="background:#efefef;" | | + | ! width="150" style="background:#efefef;" |Global Title Format Type |
! width="350" style="background:#efefef;" |Description | ! width="350" style="background:#efefef;" |Description | ||
|- | |- | ||
− | | | + | | Not used|| Indicates that no global title is used |
+ | |- | ||
+ | | Type 0|| Indicates that no global title is used | ||
+ | |- | ||
+ | | Type 1|| Global title format 1 | ||
+ | |- | ||
+ | | Type 2|| Global title format 2 | ||
+ | |- | ||
+ | | Type 3|| Global title format 3 | ||
|- | |- | ||
− | | | + | | Type 4|| Global title format 4 |
|} | |} | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
---- | ---- | ||
Line 63: | Line 43: | ||
=== Action-specific configuration parameters === | === Action-specific configuration parameters === | ||
− | |||
*The action type parameter (ActionType) specifies the type of action for this association. Allowable values: | *The action type parameter (ActionType) specifies the type of action for this association. Allowable values: | ||
+ | |||
{| class="wikitable" border="1" | {| class="wikitable" border="1" | ||
− | ! width="150" style="background:#efefef;" | | + | ! width="150" style="background:#efefef;" |SSN value to identify SCCP user |
! width="350" style="background:#efefef;" |Description | ! width="350" style="background:#efefef;" |Description | ||
|- | |- | ||
− | | | + | | Fix|| Use a fixed range of digits to perform GTT. For example, use first 3 digits. |
+ | |- | ||
+ | | Ascending|| Use variable number of digits GTT in ascending order. For example, use digits 4 to 6 in a variable fashion to perform GTT. In this case, variable means match the fourth digit, and if no match, then match the fourth and fifth digits, and so on. | ||
+ | |- | ||
+ | | Descending|| Use variable number of digits GTT in descending order. For example, use digits 4 to 6 in a variable fashion to perform GTT. In this case, variable means match the sixth digit, and if no match, then match the fifth and sixth digits, and so on. | ||
|- | |- | ||
− | | | + | | GT to PC|| Use digits in incoming GT as the point code for routing purposes. This type of GTT is used in ISNI. |
+ | |- | ||
+ | | Constant|| Always translate the incoming GT to a fixed address | ||
+ | |- | ||
+ | | Insert PC|| Insert DPC before incoming GTAI and change TT, ES and NAI, leaving GTAI unchanged. This action is for modifying calling party address at an international Gateway, when message is entering international network, originating form a national network and having calling address in national specific format with Generic Numbering Plan. DPC inserted is the point code of the international Gateway, having capability to translate back the international address format to national specific address in response message. The DPC inserted, need not be the self point code of the international Gateway modifying the calling party address. | ||
+ | |- | ||
+ | | Strip PC|| If first six digits are self point code in international format, strip off first six digits from the GTAI. Then do the translation and replace TT, ES, and NAI. Examine the DPC of the translated address, if it is self, do translation of the resulting address again else message will be forwarded to DPC for further translation without changing GTAI of the called address. | ||
|} | |} | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
Line 137: | Line 97: | ||
=== GT Format 1-specific parameters === | === GT Format 1-specific parameters === | ||
*The '''Odd even''' parameter specifies the odd or even indicator. Used to encode the odd or even indicator bit in the address parameter of an SCCP message. Allowable values are: | *The '''Odd even''' parameter specifies the odd or even indicator. Used to encode the odd or even indicator bit in the address parameter of an SCCP message. Allowable values are: | ||
+ | |||
{| class="wikitable" border="1" | {| class="wikitable" border="1" | ||
− | ! width="150" style="background:#efefef;" | | + | ! width="150" style="background:#efefef;" |GT Odd/Even Type |
! width="350" style="background:#efefef;" |Description | ! width="350" style="background:#efefef;" |Description | ||
|- | |- | ||
− | | | + | | Not used|| Not used |
|- | |- | ||
− | | | + | | Odd|| Odd number of address signals |
+ | |- | ||
+ | | Even|| Even number of address signals | ||
|} | |} | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
Line 173: | Line 118: | ||
{| class="wikitable" border="1" | {| class="wikitable" border="1" | ||
− | ! width="150" style="background:#efefef;" | | + | ! width="150" style="background:#efefef;" |GT Nature of Address Indicator |
! width="350" style="background:#efefef;" |Description | ! width="350" style="background:#efefef;" |Description | ||
|- | |- | ||
− | | | + | | Not used|| Not used |
+ | |- | ||
+ | | Subscriber|| Subscriber number | ||
+ | |- | ||
+ | | National|| National significant number | ||
|- | |- | ||
− | | | + | | International|| International number |
|} | |} | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
Line 210: | Line 135: | ||
=== GT Format 2-specific parameters === | === GT Format 2-specific parameters === | ||
− | *The '''Use type value''' parameter specifies whether or not to use the translation type value. Note that the translation type value is required for GTT address map configuration and also to send data using GT but it is optional for GTT association configuration. When setting the use translation type value parameter to 'False' then type value is ignored ( | + | *The '''Use type value''' parameter specifies whether or not to use the translation type value. Note that the translation type value is required for GTT address map configuration and also to send data using GT but it is optional for GTT association configuration. When setting the use translation type value parameter to 'False' then type value is ignored (i.e., do not care) for GTT association operation |
− | *The '''Type value''' parameter specifies the translation type value. Used to encode the 8-bit translation type field in the address parameter of an SCCP message. Allowable values: 0 to 255 | + | *The '''Type value''' parameter specifies the translation type value. Used to encode the 8-bit translation type field in the address parameter of an SCCP message. Allowable values: 0 to 255 |
Line 218: | Line 143: | ||
=== GT Format 3-specific parameters === | === GT Format 3-specific parameters === | ||
− | |||
*The '''Use type value''' parameter; see GT Format 2 explanation | *The '''Use type value''' parameter; see GT Format 2 explanation | ||
*The '''Type value''' parameter; see GT Format 2 explanation | *The '''Type value''' parameter; see GT Format 2 explanation | ||
Line 230: | Line 154: | ||
{| class="wikitable" border="1" | {| class="wikitable" border="1" | ||
− | ! width="150" style="background:#efefef;" | | + | ! width="150" style="background:#efefef;" |GT Numbering Plan Type |
! width="350" style="background:#efefef;" |Description | ! width="350" style="background:#efefef;" |Description | ||
|- | |- | ||
− | | | + | | Not used|| Not used |
|- | |- | ||
− | | | + | | Unknown|| Unknown |
+ | |- | ||
+ | | ISDN|| ISDN/telephony numbering plan | ||
+ | |- | ||
+ | | Telephony|| Telephony numbering plan (Not valid in ITU96, ANSI96 and TELCORDIA) | ||
+ | |- | ||
+ | | Data|| Data numbering plan | ||
+ | |- | ||
+ | | Telex|| Telex numbering plan | ||
+ | |- | ||
+ | | Maritime mobile|| Maritime Mobile numbering plan | ||
+ | |- | ||
+ | | Land mobile|| Land Mobile numbering plan | ||
+ | |- | ||
+ | | ISDN mobile|| ISDN Mobile numbering plan | ||
+ | |- | ||
+ | | Private|| Private network or network specific numbering plan. (For ITU96, ANSI96 and TELCORDIA) | ||
|} | |} | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
Line 297: | Line 182: | ||
− | *The | + | *The '''Encoding scheme''' parameter specifies the encoding scheme. Used to encode the encoding scheme nibble in the address parameter of an SCCP message (supports only BCD encoding scheme). Allowable values include: |
{| class="wikitable" border="1" | {| class="wikitable" border="1" | ||
− | ! width="150" style="background:#efefef;" | | + | ! width="150" style="background:#efefef;" |GT Encoding Scheme Type |
! width="350" style="background:#efefef;" |Description | ! width="350" style="background:#efefef;" |Description | ||
|- | |- | ||
− | | | + | | Not used|| Not used |
|- | |- | ||
− | | | + | | BCD odd || BCD odd |
+ | |- | ||
+ | | BCD even|| BCD even | ||
+ | |- | ||
+ | | National ES || National-specific ES (Allowed only in ITU96) | ||
|} | |} | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
Line 342: | Line 206: | ||
=== GT Format 4-specific parameters === | === GT Format 4-specific parameters === | ||
− | *The | + | *The '''Use type value''' parameter; see GT Format 2 explanation |
− | *The | + | *The '''Type value''' parameter; see GT Format 2 explanation |
− | *The | + | *The '''Numbering plan''' parameter; see GT Format 3 explanation |
− | *The | + | *The '''Encoding scheme''' parameter; see GT Format 3 explanation |
*The '''Nature of address''' parameter; see GT Format 1 explanation | *The '''Nature of address''' parameter; see GT Format 1 explanation | ||
[[category:Needs revising]] | [[category:Needs revising]] |
Revision as of 12:49, 8 September 2009
The GTT Association Configuration step is used to configure associations for Global Title Translation of the SCCP layer. An association specifies the translation procedure to be used for a particular type of global title. The user configures an association for each global title type in SCCP.
The following enumeration lists the different configuration parameters and their descriptions:
- The Network identifier parameter specifies the ID of the network
- The Protocol variant parameter specifies the SCCP protocol variant. Allowable values: see the SCCP protocol variant table in Toolpack:Create a SSCP network.
- The Global title format parameter specifies the SCCP GT format. Allowable values are:
Global Title Format Type | Description |
---|---|
Not used | Indicates that no global title is used |
Type 0 | Indicates that no global title is used |
Type 1 | Global title format 1 |
Type 2 | Global title format 2 |
Type 3 | Global title format 3 |
Type 4 | Global title format 4 |
- The Number of actions parameter specifies the number of actions configured for this association. Allowable values: 0 - 7.
- The Array of actions parameter contains the actions for this association. Allowable values: see Actions structure definition below.
Contents |
Action-specific configuration parameters
- The action type parameter (ActionType) specifies the type of action for this association. Allowable values:
SSN value to identify SCCP user | Description |
---|---|
Fix | Use a fixed range of digits to perform GTT. For example, use first 3 digits. |
Ascending | Use variable number of digits GTT in ascending order. For example, use digits 4 to 6 in a variable fashion to perform GTT. In this case, variable means match the fourth digit, and if no match, then match the fourth and fifth digits, and so on. |
Descending | Use variable number of digits GTT in descending order. For example, use digits 4 to 6 in a variable fashion to perform GTT. In this case, variable means match the sixth digit, and if no match, then match the fifth and sixth digits, and so on. |
GT to PC | Use digits in incoming GT as the point code for routing purposes. This type of GTT is used in ISNI. |
Constant | Always translate the incoming GT to a fixed address |
Insert PC | Insert DPC before incoming GTAI and change TT, ES and NAI, leaving GTAI unchanged. This action is for modifying calling party address at an international Gateway, when message is entering international network, originating form a national network and having calling address in national specific format with Generic Numbering Plan. DPC inserted is the point code of the international Gateway, having capability to translate back the international address format to national specific address in response message. The DPC inserted, need not be the self point code of the international Gateway modifying the calling party address. |
Strip PC | If first six digits are self point code in international format, strip off first six digits from the GTAI. Then do the translation and replace TT, ES, and NAI. Examine the DPC of the translated address, if it is self, do translation of the resulting address again else message will be forwarded to DPC for further translation without changing GTAI of the called address. |
- The Start digit parameter specifies the starting digit of the range for this action
Note: Used only with action of type:
- Fix
- Variable ascending
- Variable descending
- The End digit parameter specifies the ending digit of the range for this action
Note: Used only with action of type:
- Fix
- Variable ascending
- Variable descending
GT Format 1-specific parameters
- The Odd even parameter specifies the odd or even indicator. Used to encode the odd or even indicator bit in the address parameter of an SCCP message. Allowable values are:
GT Odd/Even Type | Description |
---|---|
Not used | Not used |
Odd | Odd number of address signals |
Even | Even number of address signals |
- The Nature of address parameter specifies the nature of address indicator. Used to encode the 7-bit nature of address indicator in the address parameter of an SCCP message. Allowable values are:
GT Nature of Address Indicator | Description |
---|---|
Not used | Not used |
Subscriber | Subscriber number |
National | National significant number |
International | International number |
GT Format 2-specific parameters
- The Use type value parameter specifies whether or not to use the translation type value. Note that the translation type value is required for GTT address map configuration and also to send data using GT but it is optional for GTT association configuration. When setting the use translation type value parameter to 'False' then type value is ignored (i.e., do not care) for GTT association operation
- The Type value parameter specifies the translation type value. Used to encode the 8-bit translation type field in the address parameter of an SCCP message. Allowable values: 0 to 255
GT Format 3-specific parameters
- The Use type value parameter; see GT Format 2 explanation
- The Type value parameter; see GT Format 2 explanation
- The Numbering plan parameter specifies the numbering plan. Used to encode the numbering plan nibble in the address parameter of an SCCP message. Allowable values:
GT Numbering Plan Type | Description |
---|---|
Not used | Not used |
Unknown | Unknown |
ISDN | ISDN/telephony numbering plan |
Telephony | Telephony numbering plan (Not valid in ITU96, ANSI96 and TELCORDIA) |
Data | Data numbering plan |
Telex | Telex numbering plan |
Maritime mobile | Maritime Mobile numbering plan |
Land mobile | Land Mobile numbering plan |
ISDN mobile | ISDN Mobile numbering plan |
Private | Private network or network specific numbering plan. (For ITU96, ANSI96 and TELCORDIA) |
- The Encoding scheme parameter specifies the encoding scheme. Used to encode the encoding scheme nibble in the address parameter of an SCCP message (supports only BCD encoding scheme). Allowable values include:
GT Encoding Scheme Type | Description |
---|---|
Not used | Not used |
BCD odd | BCD odd |
BCD even | BCD even |
National ES | National-specific ES (Allowed only in ITU96) |
GT Format 4-specific parameters
- The Use type value parameter; see GT Format 2 explanation
- The Type value parameter; see GT Format 2 explanation
- The Numbering plan parameter; see GT Format 3 explanation
- The Encoding scheme parameter; see GT Format 3 explanation
- The Nature of address parameter; see GT Format 1 explanation