4.39 chg-atinpqopts
Use this command to provision ATINP-specific data. This command updates the ATINPQOPTS table.
Parameters
- atiackimsi (optional)
-
ATIACK IMSI parameter for ATI ACK response message. This parameter specifies formatting of IMSI digits in the ATI ACK response message. The result of formatting determines whether the IMSI parameter will be included in the response.
- Range:
-
- srfimsi
- If an entity was found during RTDB lookup, and SRFIMSI was provisioned in the EPAP entity, then include the IMSI parameter and encode the IMSI digits as the SRFIMSI.
- asd
- If an entity was found during RTDB lookup and ASD (Additional Subscriber Data) was provisioned in the EPAP entity, then include the IMSI parameter and encode the IMSI digits as ASD.
- grn
- If an entity was found during RTDB lookup, and GRN (Generic Routing Number) was provisioned in the EPAP entity, then include the IMSI parameter and encode the IMSI digits as GRN.
- none
- Do not include the IMSI parameter in the response message.
- Default:
- none
- atiackmsisdn (optional)
- MSISDN parameter for ATI ACK response message. This parameter specifies the formatting of MSISDN parameter in the ATI ACK response message. The result of formatting determines whether the MSISDN parameter will be included in the response.
- Range:
-
- msisdn
- Include the MSISDN parameter in the ATI ACK response and encode MSISDN digits as the MSISDN from the incoming ATI query.
- asd
- If an entity was found during RTDB lookup and ASD (Additional Subscriber Data) was provisioned in the entity, then include the MSISDN parameter and encode the MSISDN digits as ASD.
- asddlmmsisdn
- Include the MSISDN parameter in the ATI ACK response and encode MSISDN digits as ASD + delimiter (atidlm) + MSISDN. ASD is encoded if an entity is found and ASD is provisioned. The specified outbound message digits delimiter (atidlm) value is encoded if the value is not none. MSISDN is encoded as the MSISDN from the incoming ATI query.
- grn
- If an entity was found during RTDB lookup and GRN (Generic Routing Number) was provisioned in the EPAP entity, then include the IMSI parameter and encode the IMSI digits as GRN.
- grndlmmsisdn
- Include the MSISDN parameter in the ATI ACK response and encode MSISDN digits as GRN + delimiter (atidlm) + MSISDN. GRN is encoded if GRN entity is found. The specified outbound message digits delimiter (atidlm) value is encoded if the value is not none. MSISDN is encoded as the MSISDN from the incoming ATI query.
- none
- Do not include the MSISDN parameter in the response message.
- Default:
- msisdn
- atiackrn (optional)
- Routing number parameter for ATI ACK response message. This parameter specifies the formatting of the routing number parameter in the ATI ACK response message. The result of formatting determines whether the routing number parameter will be included in the response.
- Range:
-
- rn
- Routing number.
- If an entity was found in RTDB lookup and the entity type was RN, include the routing number parameter and encode routing number digits as found in the entity ID.
- If MSISDN was found in RTDB lookup, but no entity was found and the default routing number parameter value (atidfltrn) is not none, include the routing number parameter and encode routing number digits as the atidfltrn value.
- If MSISDN was not found in RTDB lookup and the default routing number parameter value (atidfltrn) is not none, include the routing number parameter and encode routing number digits as the atidfltrn value.
- If an entity was found in RTDB lookup, the entity type is SP, and the atidfltrn value is not none, include the routing number parameter and encode routing number digits as the atidfltrn value.
- rnsp
- Routing number or signaling point.
- If an entity was found in RTDB lookup and the entity type was either SP or RN, include routing number parameter and encode routing number digits as found in the entity ID.
- If MSISDN was found in RTDB lookup but no entity was found and the default routing number parameter value (atidfltrn) is not none, include the routing number parameter and encode routing number digits as the atidfltrn value.
- If MSISDN was not found in RTDB lookup and the default routing number parameter value (atidfltrn) is not none, include the routing number parameter and encode routing number digits as the atidfltrn value.
- If an entity was found in RTDB lookup and the entity type was not SP or RN and the default routing number parameter value (atidfltrn) is not none, include the routing number parameter and encode routing number digits as the atidfltrn Entity.
- asddlmrnsp
- ASD, delimiter and routing number or signaling point.
Format routing number digits as ASD (if supported and available from lookup entity) + atidlm (if not none) + entity digits (as described in the atiackrn=rnsp parameter).
- If this format results in 0 digits (no ASD, atidlm=none, and no entity digits), the routing number will not be included in the response message.
- If the formatting results only in the specified outbound message digits delimiter (atidlm) digits, the routing number parameter will not be encoded in the response.
- If no entity digits (atiackrn=rnsp) are found, the result is ASD + delimiter digits.
- rnspdlmasd
- Routing number or signaling point, delimiter, ASD
Format routing number digits as entity digits (as described in atiackrn=rnsp) + delimiter (if atidlm is not none) + ASD (if supported and available from lookup entity).
- If this formatting results in 0 digits (no ASD, atidlm=none, and no RN digits, the routing number will not be included in the response message.
- If the formatting results only in delimiter digits, the routing number will not be encoded in the response.
-
If there are outbound message delimiter digits (the atidlm value is not none) and ASD digits are available, the delimiter will be included even if entity digits are not found (resulting in delimiter + ASD).
- srfimsi
- Encode routing number digits as SRFIMSI configured in the entity data.
If SRFIMSI was not found (MSISDN not found in RTDB lookup, or MSISDN found but no entity found, or entity found but SRFIMSI not configured) then the routing number will not be included in the response message.
- srfimsidlmasd
- SRFIMSI, delimiter, ASD
Encode routing number digits as SRFIMSI + delimiter (if atidlm is not none) + ASD (if supported and available from lookup entity). SRFIMSI is encoded as described in the atiackrn=srfimsi option.
- If this formatting results in 0 digits, the routing number parameter will not be included in the response message.
- If the formatting results only in delimiter digits, the routing number parameter will not be encoded in the response message.
- asddlmsrfimsi
- ASD, delimiter, SRFIMSI
Encode routing number as ASD (if supported and available from lookup entity) + delimiter (if atidlm is not none) + SRFIMSI(encoded as specified in the atiackrn=srfimsi parameter).
- If this format results in 0 digits, the routing number parameter will not be included in the response message.
- If the formatting results only in delimiter digits, the routing number parameter will not be encoded in the response.
- If the outbound message digits delimiter value (atidlm) is not none and ASD digits are available, the delimiter will be included even if SRFIMSI does not have any digits (resulting in ASD + delimiter).
- grndlmrnsp
- GRN, delimiter, Routing number or signaling point
Encode routing number as GRN (if supported and available from RTDB lookup) + delimiter (if atidlm is not none) + RNSP (encoded as specified in the atiackrn=rnsp parameter).
- If this format results in 0 digits, the routing number parameter will not be included in the response message.
- If the formatting results only in delimiter digits, the routing number parameter will not be encoded in the response.
- If the outbound message digits delimiter value (atidlm) is not none and GRN digits are available, the delimiter will be included even if RNSP does not have any digits (resulting in GRN + delimiter).
- rnspdlmgrn
- Routing number or signaling point, delimiter, GRN
Encode routing number as entity digits (as described in atiackrn=rnsp) + delimiter (if atidlm is not none) + GRN (if supported and available from RTDB lookup).
- If this format results in 0 digits, the routing number parameter will not be included in the response message.
- If the formatting results only in delimiter digits, the routing number parameter will not be encoded in the response.
- If the outbound message digits delimiter value (atidlm) is notnoneand GRN digits are available, the delimiter will be included even if RNSP does not have any digits (resulting in delimiter + GRN).
- srfimsidlmgrn
- SRFIMSI, delimiter, GRN
Encode routing number as SRFIMSI (encoded as specified in the atiackrn=srfimsi parameter) + delimiter (if atidlm is not none) + GRN (if supported and available from RTDB lookup).
- If this format results in 0 digits, the routing number parameter will not be included in the response message.
- If the formatting results only in delimiter digits, the routing number parameter will not be encoded in the response.
- If the outbound message digits delimiter value (atidlm) is not none and GRN digits are available, the delimiter will be included even if SRFIMSI does not have any digits (resulting in delimiter + GRN).
- grndlmsrfimsi
- GRN, delimiter, SRFIMSI
Encode routing number as GRN (if supported and available from RTDB lookup) + delimiter (if atidlm is not none) + SRFIMSI (encoded as specified in the atiackrn=srfimsi parameter).
- If this format results in 0 digits, the routing number parameter will not be included in the response message.
- If the formatting results only in delimiter digits, the routing number parameter will not be encoded in the response.
- If the outbound message digits delimiter value (atidlm) is not none and GRN digits are available, the delimiter will be included even if SRFIMSI does not have any digits (resulting in GRN + delimiter).
- none
- Do not include the Routing Number field in the response message.
- Default:
- rn
- atiackvlrnum (optional)
-
The formatting of the VLR-number in the ATI ACK response message.
- Range:
-
- rn
- routing number
- If an RN entity was found in RTDB lookup, the VLR-number is formatted as RN.
- If RN entity was found in RTDB lookup, the portability type is zero, and the S-Port feature is enabled or the IGM feature is on, the VLR-number is formatted as GRN (if provisioned).
- If MSISDN was found in RTDB lookup, no entity was found, and the atidfltrn value is not none, the VLR-number is formatted as the atidfltrn value.
- If MSISDN was not found in RTDB lookup, atinptype=always and the atidfltrn value is not none, the VLR-number is formatted as the atidfltrn value.
- If an SP entity was found in RTDB lookup, and the atidfltrn value is not none, the VLR-number is formatted as the atidfltrn value.
- If the format results in 0 digits (no entity digits), the VLR-number is formatted as the incoming MSISDN.
- rnsp
- Routing number or signaling point.
- If an RN or SP entity was found in RTDB lookup, the VLR-number is formatted as the entity ID.
- If MSISDN was found in RTDB lookup, no entity was found, and the atidfltrn value is not none, the VLR-number is formatted as the atidfltrn value.
- If MSISDN was not found in RTDB lookup, atinptype=always, and the atidfltrn value is not none, the VLR-number is formatted as the atidfltrn value.
- If an entity was found in RTDB lookup, the entity type was not RN or SP, and the atidfltrn value is not none, the VLR-number is formatted as the atidfltrn value.
- If the format results in 0 digits (no entity digits), the VLR-number is formatted as the incoming MSISDN.
- asddlmrnsp
- ASD, delimiter and routing number or signaling point.
Format the VLR-number as ASD (if provisioned) + atidlm (if not none) + entity digits (RN or SP).
- If the formatting results in 0 digits (no ASD, atidlm=none, and no entity digits), the VLR-number is formatted as the incoming MSISDN.
- If the formatting results only in atidlm digits, the VLR-number is formatted as the incoming MSISDN.
- If no entity digits are found, the VLR-number is formatted as ASD + delimiter digits.
- rnspdlmasd
- Routing number or signaling point, delimiter, ASD
- If the formatting results in 0 digits (no ASD, atidlm=none, and no RN digits), the VLR-number is formatted as the incoming MSISDN.
- If the formatting results only in delimiter digits, the VLR-number is formatted as the incoming MSISDN. If there are outbound message delimiter digits (the atidlm value is not none) and ASD digits are available, the delimiter is included even if entity digits are not found (resulting in delimiter + ASD).
- srfimsi
- Format the VLR-number as SRFIMSI configured in the entity data.
If SRFIMSI was not found (MSISDN not found in RTDB lookup, or MSISDN found but no entity found, or entity found but SRFIMSI not configured) then the VLR-number is formatted as the incoming MSISDN.
- srfimsidlmasd
- SRFIMSI, delimiter, ASD
Format the VLR-number as SRFIMSI + delimiter (if atidlm is not none) + ASD (if provisioned).
- If the formatting results in 0 digits, the VLR-number is formatted as the incoming MSISDN.
- If the formatting results only in delimiter digits, the VLR-number is formatted as the incoming MSISDN.
If atidlm value is not none and ASD digits are available, the delimiter is included even if SRFIMSI does not have any digits (resulting in delimiter + ASD).
- asddlmsrfimsi
- ASD, delimiter, SRFIMSI
Format the VLR-number as ASD (if provisioned) + delimiter (if atidlm is not none) + SRFIMSI.
- If the formatting results in 0 digits, the VLR-number is formatted as the incoming MSISDN.
- If the formatting results only in delimiter digits, the VLR-number is formatted as the incoming MSISDN.
If the atidlm value is not none and ASD digits are available, the delimiter is included even if SRFIMSI does not have any digits (resulting in ASD + delimiter).
- grndlmrnsp
- GRN, delimiter, Routing number or signaling point
Format VLR-number as GRN (if provisioned) + delimiter (if atidlm is not none) + entity digits (RN or SP).
- If the formatting results in 0 digits, the VLR-number is formatted as the incoming MSISDN.
- If the formatting results only in delimiter digits, the VLR-number is formatted as the incoming MSISDN.
If the atidlm value is not none and GRN digits are available, the delimiter is included even if RNSP does not have any digits (resulting in GRN + delimiter).
- rnspdlmgrn
- Routing number or signaling point, delimiter, GRN
Format VLR-number as entity digits (RN or SP) + delimiter (if atidlm is not none) + GRN (if provisioned).
- If the formatting results in 0 digits, the VLR-number is formatted as the incoming MSISDN.
- If the formatting results only in delimiter digits, the VLR-number is formatted as the incoming MSISDN.
If the atidlm is not none and GRN digits are available, the delimiter is included even if RNSP does not have any digits (resulting in delimiter + GRN).
- srfimsidlmgrn
- SRFIMSI, delimiter, GRN
Format VLR-number as SRFIMSI + delimiter (if atidlm is not none) + GRN (if provisioned).
- If the formatting results in 0 digits, the VLR-number is formatted as the incoming MSISDN.
- If the formatting results only in delimiter digits, the VLR-number is formatted as the incoming MSISDN.
If the atidlm is not none and GRN digits are available, the delimiter is included even if SRFIMSI does not have any digits (resulting in delimiter + GRN).
- grndlmsrfimsi
- GRN, delimiter, SRFIMSI
Format VLR-number as GRN (if provisioned) + delimiter (if atidlm is not none) + SRFIMSI.
- If the formatting results in 0 digits, the VLR-number is formatted as the incoming MSISDN.
- If the formatting results only in delimiter digits, the VLR-number is formatted as the incoming MSISDN.
If the atidlm value is not none and GRN digits are available, the delimiter is included even if SRFIMSI does not have any digits (resulting in GRN + delimiter).
- rnmsisdn
-
- If an RN entity was found in RTDB lookup, the VLR-number is formatted as RN + incoming MSISDN.
- If an SP entity was found in RTDB lookup, and the atidfltrn value is not none, the VLR-number is formatted as atidfltrn + incoming MSISDN
- If MSISDN was found in RTDB lookup, but no entity was found and the atidfltrn value is not none, then VLR-number is formatted as atidfltrn value + incoming MSISDN.
- If MSISDN was not found in RTDB lookup, atinptype=always, and the atidfltrn value is not none, the VLR-number is formatted as atidfltrn value + incoming MSISDN.
- If RN/PT=0 is found in RTDB lookup, the S-Port feature is enabled or the IGM feature is on, and the atidfltrn value is not none, the VLR-number is formatted as atidfltrn + incoming MSISDN. RN/PT=0 is treated as an SP entity.
- rnspmsisdn
-
- If an RN or SP entity was found in RTDB lookup, the VLR-number is formatted as entity digits + incoming MSISDN.
- If MSISDN was found in RTDB lookup, but no entity was found and the atidfltrn value is not none, the VLR-number is formatted as atidfltrn value + incoming MSISDN.
- If an entity was found in RTDB lookup, the entity type was not RN or SP, and the atidfltrn value is not none, then the VLR-number is formatted as the atidfltrn value + incoming MSISDN.
- If MSISDN was not found in RTDB lookup, atinptype=always, and the atidfltrn value is not none, then the VLR-number in the ATI ACK response is formatted as atidfltrn value + incoming MSISDN.
- msisdn
- Format the VLR-number as incoming MSISDN
- asd
- Format the VLR-number in the ATI ACK message as ASD (if provisioned).
If the formatting results in 0 digits, the VLR-number is formatted as incoming MSISDN.
- asdmsisdn
- Format the VLR-number in the ATI ACK message as ASD (if provisioned) + incoming MSISDN.
- Default:
- rnspmsisdn
- atidfltrn (optional)
- Default Routing Number. The routing number to be used in outgoing message formats while encoding outgoing digit formats in the ATI ACK response in cases where an RN is not returned from an RTDB lookup.
- atidlm (optional)
- Outbound message digits delimiter. This delimiter is used in outgoing message formats while encoding outbound digits in the ATI ACK response.
- atinptype (optional)
- Number Portability Type. The criteria for a successful RTDB lookup.
- entitylen (optional)
- Entity Length. The maximum number of digits to be used from entity data (SRFIMSI or entity ID) in the specified encoding format.
- off
- Disables or turns off the specified feature options. A comma-separated list of feature options that are requested to be turned off. Up to 8 feature options can be specified in the list.
- on
- Disables or turns on the specified feature options. A comma-separated list of feature options that are requested to be turned off. Up to 8 feature options can be specified in the list.
- snai (optional)
- Service NAI. The number conditioning that is performed on the MSISDN digits in the incoming ATI query message before RTDB lookup is performed.
- Range:
-
- intl
- Number conditioning is not performed.
- nat
- The default country code (defined in the
chg-stpopts:defcc=
command) is pre-pended to the MSISDN before RTDB lookup. - nai
- The NAI from the MSISDN in the incoming ATI query is used to perform number conditioning.. If the message NAI is International (0x1) or Network Specific Number (0x3), then no conditioning is performed. In all other cases, the default country code (defined in the
chg-stpopts:defcc=
command) is pre-pended to the MSISDN before RTDB lookup.
- Default:
- nai
- sporttype (optional)
- Service Portability type. The application of Service Portability that is applied to the associated feature.
The S-Port feature must be enabled before this parameter can be specified. The S-Port feature must be turned on before any change to the parameter will impact the associated feature.
If Service Portability is performed, then the Service Portability prefix (RTDB ‘GRN’ entity id) is applied.
Example
This example specifies that the outbound message delimiter will not be used in outgoing message formats:
chg-atinpqopts:atidlm=noneThis example specifies that the NAI of the incoming MSISDN digits will be considered to be National, and that the IMSI parameter will not be included in the ATI ACK response message:
chg-atinpqopts:snai=nai:atiackimsi=noneThis example specifies that the lookup is always considered to be successful and that the NAI of the incoming MSISDN digits will be considered to be National:
chg-atinpqopts:atinptype=always:snai=natThis example specifies that the Routing Number field will not be included in the response, and that the MSISDN in the ATI ACK response will be encoded as the ASD.
chg-atinpqopts:atiackrn=none:atiackmsisdn=asdThe example specifies that the Routing Number field will not be included in the response:
chg-atinpqopts:atiackrn=noneThis example specifies that the IMSI and MSISDN in the ATI ACK response will be encoded as GRN:
chg-atinpqopts:atiackimsi=grn:atiackmsisdn=grnThis example specifies that the Location information request in ATI query is supported and the VLR-number in the ATI ACK response will be encoded as rnspmsisdn :
chg-atinpqopts:atiackvlrnum=rnspmsisdn:on=atisupplocinfoDependencies
At least one optional parameter must be specified.
The ATINP feature must be enabled before this command can be entered.
The EGLEOPTS table is corrupt or cannot be found.
The Service Portability feature must be enabled before the sporttype parameter can be specified.
The same value cannot be specified for the on and off parameters.
Notes
- The ATINP feature must be turned on
- The on=atisupplocinfo parameter must be specified.
Output
chg-atinpqopts:atiackimsi=grn:atiackmsisdn=grndlmmsisdn:atiackrn=grndlmrnsp
tekelecstp 09-06-05 12:40:16 EST EAGLE 41.1.0
CHG-ATINPQOPTS: MASP A - COMPLTD
;