Message Interception

SRF-based MNP processing involves the “intercepting” of existing MAP messages to check for ported numbers. For call-related messages, IGM acts as an “NP HLR” in the case where the number has been exported, by responding to the switch with an SRI, SRI-SM, LOCREQ, and SMSREQ ack messages. For non-migrated calls, IGM performs message relay.

Routing Options

Number Lengths

Number lengths vary among countries and may even vary within a country. As a result, IGM supports numbers of varying length in a flexible way without necessitating software modifications. A maximum number length of 15 digits for ported numbers is supported.

Supported Messages

IGM uses the EPAP RTDB to derive the portability status of a subscriber.

IGM supports LOCREQ messages as well as SMSREQ messages, if the option is selected, for number portability handling. LOCREQ messages generate a LOCREQ response if the mobile dialed number (MDN) is migrated and relays the LOCREQ if the MDN is not ported (non-ported or ported in are handled the same way).

SMSREQ messages generate a SMSREQ NAK if access is denied and relays the SMSREQ if SMSREQ BYPASS is set to false. SRI generates an ACK if the MSISDN is migrated, and relays the message if the dialed number is not migrated. SRI-SM generates an ACK if the dialed number is migrated, and relays the message if it is not.

MTP Routed SCCP Traffic

When the MTP Msgs for SCCP Apps feature is turned on, all MTP routed UDT/non-segmented XUDT SCCP messages are routed to Service Module cards. When the MTP Routed GWS Stop Action feature is turned on, messages are filtered based on the provisioned Gateway Screening rules on a per linkset basis. The MTP Routed GWS Stop Action feature forwards only UDT, UDTS, XUDT and XUDTS SCCP messages to the Service Module cards for processing.The Service Module cards then perform SCCP decode and verification on the MTP routed messages.

MNP Circular Route Prevention

The MNP Circular Route Prevention (MNPCRP) feature detects circular routing caused by incorrect information in one or more of the network number portability databases. For example, a subscriber may have ported from network A to network B. Network A has the correct routing information, indicating the subscriber now belongs to network B. However, network B may have incorrect routing information, indicating that the subscriber still belongs to network A. In this case, network A routes the call to network B, based on its portability data, but network B routes the call back to network A, based on its incorrect data. The result is a circular route. The MNPCRP feature provides logic to prevent the circular routing from occurring.

MNP Circular Route Prevention is not valid when only IS41 GSM Migration (IGM) is turned on. ANSI-41 Mobile Number Portability (A-Port) or GSM Mobile Number Portability (G-Port) must be turned on for MNP Circular Route Prevention processing to be valid. Circular route prevention for only ITU MAP messages is supported when only IGM is turned on.

The MNP Circular Route Prevention feature (MNPCRP) allows Circular Route Prevention based on the Translation Type (TT) of the SCCP CdPA to be performed for SRI messages when a Home Routing Number (HomeRN) is not present. For the Circular Route Prevention on Translation Type processing to be performed, the crptt parameter of the chg-gsmopts command must be set to a value between 0 and 255. If the crptt parameter of the chg-gsmopts command is set to the default value of none, then no Circular Route Prevention on Translation Type processing is performed. The MNP Circular Route Prevention feature cannot be turned off if the crptt parameter is provisioned to any value other than none. If a message is processed for Circular Route Prevention based on HomeRN, then Circular Route Prevention on Translation Type processing does not occur.

SRI messages must meet these criteria to be eligible for Circular Route Prevention on Translation Type:

• The message is selected for G-Port or IS41 GSM Migration processing.

• The message is not identified as G-Port SRI Query for Prepaid.

• The message is not MTP-routed. (The CdPA is Route-on-GT.)

• The translation type of the SCCP CdPA matches the provisioned translation type (crptt).

• The ITU TCAP Package type is ITU Begin.

• The OpCode is an SRI (hexadecimal 16).

• The Optimal Routing Interrogation Parameter (Tag = 0x04) is not present.

• The MSISDN is not assigned to the subscriber's network provider.

DigitAction Expansion

The DigitAction Expansion feature provides more flexibility to formulate the SCCP Called Party Address (SCCP) Global Title Address (GTA) field of the MAP messages relayed by IGM.

DigitAction Expansion is provisioned via the PDBI Enter Network Entity or Update Network Entity commands. DigitAction Expansion can also be modified via the Add an NE and Update an NE GUI screens.

Digit Action DELCCPREFIX

The Digit Action to delete country code if present and prefix database entity feature allows the DELCCPREFIX Digit Action to be applied to the Called Party Global Title Address (CdPA GTA) when the GTA has a National format, as well as when the GTA has an International format. The DELCCPREFIX option in the SCCPOPTS table specifies how the DELCCPREFIX digit action is applied to a Called Party Global Title Address (CdPA GTA).

• When the SCCPOPTS:DELCCPREFIX option is set to PFXWCC, the DELCCPREFIX digit action is applied to the CdPA GTA only when the address has a International format. The Country Code is deleted and the GTA is prefixed with the Entity ID.
• When the SCCPOPTS:DELCCPREFIX option is set to PFX4ALL, the DELCCPREFIX digit action is applied to the CdPA GTA in all cases. For an International format, the Country Code is deleted and the GTA is prefixed with the Entity ID. For a National format, the GTA is prefixed with the Entity ID.

The chg-sccpopts command is used to specify the delccprefix parameter value to configure the DELCCPREFIX Digit Action functionality.

MNP SCCP Service Re-Route

The MNP SCCP Service Re-Route feature is used when the IGM subscriber database is incoherent with MPS data and the GTT data is valid. The MNP SCCP Service Re-Route feature provides the capability to re-route the traffic from the EAGLE to other IGM subscriber database nodes and inform the originating nodes to re-route the IGM service related traffic to other IGM service nodes.

The MNP SCCP Service Re-Route feature is designed to handle and control re-routing of IGM traffic from an affected node to alternate nodes within an operators network. This feature is an optional feature and does not affect the normal IGM function. This feature also provides the option to mark IGM offline to perform a controlled re-routing during this state.

ROP Support

The IS41 GSM Migration (IGM) feature allows Small Geographic Areas (CNLs) to be grouped into Large Geographic Areas (ROPs). This grouping simplifies the routing and allows a call to be delivered as close to the interconnection destination as possible. ROP information is stored in the generic routing number (GRN) field. Both CNL and ROP information can be provisioned for a single subscriber entry; however, only one of the CNL or ROP fields can be selected for the outgoing message

The G-Port, G-Port SRI Query for Prepaid, GSM MAP SRI Redirect, AINPQ, INP, and ATINP features also support ROP.

Include Optional CUG Parameter in SRI Ack Messages

The Include Optional CUG Parameter in SRI Ack Messages functionality allows an existing Closed User Group-CheckInfo (CUG-CheckInfo) parameter in an incoming SRI message to be included in the outgoing SRI Ack message.

The Include Optional CUG Parameter in SRI Ack Messages functionality is controlled by the encodecug option of the chg-gsmopts command off and on parameters. The encodecug option of the chg-gsmopts off/on parameter can be changed only if the G-Port or IGM feature is enabled.

The CUG-CheckInfo parameter in an incoming SRI message is copied in the original sequence to the outgoing SRI Ack message when these conditions are met:

• The encodecug option of the chg-gsmopts command is set to on.

• The CUG-CheckInfo parameter is present in an incoming SRI message.

• The CUG-CheckInfo parameter in an incoming SRI message is encoded in definite length format that is less than or equal to 30 bytes.

If the three conditions described above are met, the original CUG-CheckInfo sequence from the incoming SRI message is copied into the SRI Ack message. If encoded in the SRI Ack message, the CUG-CheckInfo parameter is located after the MSRN (Tag = 0x04) and before the MSISDN (Tag = 0x8C) or NPS parameter (Tag = 0x8D), if either MSISDN or NPS parameter is present. The CUG-CheckInfo parameter in an SRI Ack message uses Tag = 0xA3.

If the CUG-CheckInfo parameter is greater than 30 bytes and all other conditions for encoding are met, then only the CUG-Interlock and CUG-OutgoingAccess parameters are copied from an incoming SIR message to the outgoing SRI Ack message. The ExtensionContainer is omitted.

When the encodecug option is set to off, the CUG-CheckInfo parameter is not encoded in the SRI Ack message.

If the encodecug option is set to on but the CUG-CheckInfo parameter in an incoming SRI message uses an indefinite length format, the CUG-CheckInfo parameter is not encoded in the SRI Ack message.

Route SRI_SM and ReportSMSDeliveryStatus for Non-local or Ported-out Subscribers using GTT

The Route SRI_SM and ReportSMSDeliveryStatus for Non-local or Ported-out Subscribers using GTT functionality modifies SRI_SM and ReportSMSDeliveryStatus messages to allow routing of the message to an alternate network using Global Title Translation (GTT). This functionality allows processing to occur when the Directory Number (DN) in the database is associated with both the Service Point (SP) and Generic Routing Number (GRN) network elements and the GRN is not present in the EAGLE HomeRN table, or when the subscriber is ported out and associated with the Routing Number (RN).

The message is altered by changing the SCCP Called Party Address (CdPA) to the Country Code (CC) + GRN + DN or to CC + RN + DN. This alteration allows GTT to redirect the query to an alternate network. If a CC is not located in the DN, then the SCCP CdPA is converted to a GRN + DN or RN + DN format.

This conversion is performed only on ITU TCAP Begin MSUs with Op Code of SRI_SM or ReportSMSDeliveryStatus delivered to the GPort or MNP service selector for processing. If the MT-Based GSM SMS NP or the IS41 GSM Migration (IGM) feature generates a response for the SRI_SM message, then this functionality is not applicable.

The Route SRI_SM and ReportSMSDeliveryStatus for Non-local or Ported-out subscribers using GTT functionality is controlled by the srismgttrtg option of the chg-gsmopts command off and on parameters. The srismgttrtg option of the chg-gsmopts off/on parameter can be changed only if the G-Port or IGM feature is enabled.

Option to Suppress NumberPortabilityStatusIndicator in SRI Ack

The Option to Suppress NumberPortabilityStatusIndicator in SRI Ack functionality allows the Number Portability Status Indicator (NPSI) to be omitted from all SRI Ack messages.

The Option to Suppress NumberPortabilityStatusIndicator in SRI Ack functionality is controlled by the encodenps option of the chg-gsmopts command off and on parameters. The encodenps option of the chg-gsmopts off/on parameter can be changed only if the G-Port or IGM feature is enabled.

The NumberPortabilityStatusIndicator parameter is encoded in an SRI Ack message when these conditions are met:

• The encodenps option of the chg-gsmopts command is set to on.

• SRI is considered MAP Phase 2+.

• DN Portability Type is 0, 1, 2, or 36. (Portability Type = 36 is encoded as Portability Type = 0.)

The NumberPortabilityStatusIndicator parameter is not encoded in any SRI Ack message if the encodenps option of the chg-gsmopts command is set to off.

Message Discrimination

Because IGM provides translation of migrated and non-migrated numbers, it provides a method to identify which messages need migration handling versus GTT. This task of identification is provided via a service selector table where the user defines the service for a combination of selectors.

Operation Code Discrimination

IGM handles ANSI Loc_Req, SMSREQ, GSM SRI, and SRI_SM differently than other ANSI/GSM operation codes. The Portability type field is only considered for these operation codes. Message relay is performed for all other operation codes based on IGM Translation data.

Number Conditioning

The RTDB stores International MSISDN only. IGM provides the capability to condition incoming numbers to be international MSISDN (Insert CC or/and NDC) for the database look up. IGM removes the GSM prefix from GSM SRI messages and then conditions the non-international numbers to international numbers, if needed, before performing any database lookup.

IS412GSM

IGM generates a Loc_Req Return Result Response, when the MDN in the Loc_Req is a Migrated with one handset subscriber. When formulating a Loc_Req response, IGM uses the IS412GSM prefix in GSMOPTS to build the Routing Digits. If the IS412GSM prefix is not provisioned, IGM issues UIM 1130 IS412GSM not provisioned and falls through to GTT.

GSM2IS41

The GSM2IS41 prefix is used in the SRI Ack message if the message received is SRI and DN lookup has RN and PT = 0 assigned. If MIGRPFX = MULTPLE, then the RN from the RTDB is used as the prefix in the SRI Ack message. If MIGRPFX = SINGLE and GSM2IS41 prefix is NONE, then the SRI Ack message issues UIM 1341 SRI rcvd GSM2is41 prefix not provisioned and the message falls through to GTT.

Database Lookup

IGM performs the RTDB database lookup using the international MSISDN.

The individual number database is searched first:

• If the number is not found, the number range database is searched.
• If a match is not found in the individual and range-based database, the GTT is performed on the message.

In the event of the MSISDN numbers in the RTDB database being odd and CDPA GTI of the incoming message being ‘2’, and the last digit of the number is 'zero':

• IGM first performs database lookup one time using the even number.
• If no match is found, IGM again performs the database lookup, using the odd number (without last digit).

Since a DN may be the target of the A-Port, G-Port, or IGM message processing in a hybrid network (where an operator owns both GSM and IS41 network), message processing call disposition is based on what applications are in service. Table 2-1 through Table 2-4 show call dispositions for the following configurations:

• IGM Only (Table 2-1)
• IGM and G-Port (Table 2-2)
• IGM and A-Port (Table 2-3)
• A-Port, G-Port, and IGM (Table 2-4

  The following notations apply to Table 2-1 through Table 2-4.

  PT = Portability Type for the DN

  Values:

  • 0 – Not known to be ported
  • 1 – Own number ported out
  • 2 – Foreign number ported to foreign network
  • 3 – Prepaid 1 (used by PPSMS)
  • 4 – Prepaid 2 (used by PPSMS)
  • 5 – Migrated with one handset
  • 6 – Prepaid 3 (used by PPSMS)

    through

  • 32 – Prepaid 35 (used by PPSMS)
  • 36 – Not identified to be ported
  • FF – No status, No Portability Type

  NE = Network Entity

  PPSMSPT = Prepaid1 through Prepaid 35 used by PPSMS

  RN = Routing Number

  SP = Signaling Point

  SRI = Send Routing Information

  SP* : This row refers to DN is assigned with SP, with or without PT. SP**: This row refers to DN is assigned with SP without PT. DN blocks are commonly assigned with SP and without PT.

  Table 2-1 IGM Customer Message Processing

  NE/PT	SRI	SRI_SM	Other GSM	LOCREQ	SMSREQ	Other IS41
  RN and PT = 0	MIGRPFX = single: ACK, use GSM2IS41 prefix MIGRPFX = multiple: ACK, RN from RTDB	Based on provisioned option: a) SRI_SM_NACK with Return Error Component b) Relay to configured default CDMA SMSC	Relay	Relay	Relay	Relay
  RN and PT ≠ 0	GTT	GTT	GTT	GTT	GTT	GTT
  SP and PT = 5	Relay	Relay	Relay	ReturnResult with IS412GSM prefix	If SMSREQBYPASS = true, then Relay; else ReturnResult with SMS Access Denied Reason = 5	Relay
  SP and PT ≠ 5	Relay	Relay	Relay	Relay	Relay	Relay
  No NE and PT = 0	ACK (no NE)	GTT	GTT	GTT	GTT	GTT
  No NE and PT=1, 2, 36, or No PT	GTT	GTT	GTT	GTT	GTT	GTT
  No NE and PT = 5	GTT	GTT	GTT	ReturnResult with IS412GSM prefix	If SMSREQBYPASS = true, then GTT; else ReturnResult with SMS Access Denied Reason = 5	GTT
  No NE and PT = PPSMSPT	GTT	GTT	GTT	GTT	GTT	GTT
  No DN entry found	GTT	GTT	GTT	GTT	GTT	GTT

  Table 2-2 IGM and G-Port Customer Message Processing

  NE/PT	SRI	SRI_SM	Other GSM	LOCREQ	SMSREQ	Other IS41
  RN and PT = 0	MIGRPFX = single: ACK, use GSM2IS41 prefix MIGRPFX = multiple: ACK, RN from RTDB	Based on provisioned option: a) SRI_SM_NACK with Return Error Component b) Relay to configured default CDMA SMSC	Relay	Relay	Relay	Relay
  RN and PT ≠ 0 or No PT	ACK (RN from RTDB) for PT = 0, 1, 2: Existing Encode NPS for PT = 36: maps to 0	Relay	Relay	GTT	GTT	GTT
  SP and PT = 5	Relay	Relay	Relay	ReturnResult with IS412GSM prefix	If SMSREQBYPASS = true, then Relay; else ReturnResult with SMS Access Denied Reason = 5	Relay
  SP and PT ≠ 5	Relay	Relay	Relay	Relay	Relay	Relay
  No NE and PT = 5	GTT	GTT	GTT	ReturnResult with IS412GSM prefix	If SMSREQBYPASS = true, then GTT; else ReturnResult with SMS Access Denied Reason = 5	GTT
  No NE and PT= 0, 1, 2, 36, or No PT	ACK (no NE) for PT = 0: Existing Encode NPS for PT = 36: maps to 0 if needed	GTT	GTT	GTT	GTT	GTT
  No NE and PT = PPSMSPT	GTT	GTT	GTT	GTT	GTT	GTT
  No DN entry found	GTT	GTT	GTT	GTT	GTT	GTT

  Table 2-3 IGM and A-Port Message Processing

  NE/PT	SRI	SRI_SM	Other GSM	LOCREQ	SMSREQ	Other IS41
  RN and PT = 0	MIGRPFX = single: ACK, use GSM2IS41 prefix MIGRPFX= multiple: ACK, RN from RTDB	Based on provisioned option: a) SRI_SM_NACK with Return Error Component b) Relay to configured default CDMA SMSC	Relay	Relay	Relay	Relay
  RN and PT≠ 0	GTT	GTT	GTT	ReturnResult with RN from RTDB	Relay	Relay
  SP and PT= 5	Relay	Relay	Relay	ReturnResult with IS412GSM prefix	If SMSREQBYPASS = true, then Relay; else ReturnResult with SMS Access Denied Reason = 5	Relay
  SP and PT≠ 5	Relay	Relay	Relay	Relay	Relay	Relay
  No NE and PT = 5	GTT	GTT	GTT	ReturnResult with IS412GSM prefix	If SMSREQBYPASS = true, then GTT; else ReturnResult with SMS Access Denied Reason = 5	GTT
  No NE and PT = 0	ACK (no NE)	GTT	GTT	ReturnResult (no NE)	GTT	GTT
  No NE and PT = 1, 2, 36, or No PT	GTT	GTT	GTT	ReturnResult (no NE)	GTT	GTT
  No NE and PT = PPSMSPT	GTT	GTT	GTT	GTT	GTT	GTT
  No DN entry found	GTT	GTT	GTT	GTT	GTT	GTT

  Table 2-4 IGM, A-Port, and G-Port Customer Message Processing

  NE/PT	SRI	SRI_SM	Other GSM	LOCREQ	SMSREQ	Other IS41
  RN and PT = 0	MIGRPFX = single: ACK, use GSM2IS41 prefix MIGRPFX = multiple: ACK, RN from RTDB	Based on provisioned option: a) SRI_SM_NACK with Return Error Component b) Relay to configured default CDMA SMSC	Relay	Relay	Relay	Relay
  RN and PT ≠ 0	ACK (RN from RTDB) for PT = 0, 1,2: Existing Encode NPS for PT = 36: mps to 0	Relay	Relay	ReturnResult with RN from RTDB	Relay	Relay
  SP and PT = 5	Relay	Relay	Relay	ReturnResult with IS412GSM prefix	If SMSREQBYPASS = true, then Relay; else ReturnResult with SMS Access Denied Reason = 5	Relay
  SP and PT ≠ 5	Relay	Relay	Relay	Relay	Relay	Relay
  No NE and PT = 5	GTT	GTT	GTT	ReturnResult with IS412GSM prefix	If SMSREQBYPASS = true, then GTT; else ReturnResult with SMS Access Denied Reason = 5	GTT
  No NE and PT = 0 or 36	ACK (no NE) for PT = 0: Existing Encode NPS for PT = 36: maps to 0	GTT	GTT	ReturnResult (no NE)	GTT	GTT
  No NE and PT = 1, 2 or No PT	ACK (no NE)	GTT	GTT	ReturnResult (no NE)	GTT	GTT
  No NE and PT = PPSMSPT	GTT	GTT	GTT	GTT	GTT	GTT
  No DN entry found	GTT	GTT	GTT	GTT	GTT	GTT

Database lookup results in the following:

1. Applying normal routing or
2. Relaying the message to the destination as noted in the database or
3. Returning an acknowledge message to the originating switch.

Message Relay

The rules for formatting the SCCP CdPA GTA field are based on the value specified in the DigitAction field. In the case where a received IS41 message is relayed, the EAGLE formulates the SCCP CdPA GTA field of the outgoing message according to DigitAction specified. If DigitAction = none, the EAGLE does not overwrite the SCCP CdPA GTA. For all other values, the EAGLE formats the SCCP CdPA GTA according to the value assigned to DigitAction. Table 2-5 identifies the required DigitAction options as well as the samples of how the SCCP CdPA GTA of an outgoing message is formatted for each of the options. The illustration assumes the RN/SP ID is 1404 and default country code is 886.

Returning Acknowledgement

When a LOCREQ Ack is returned, the EAGLE follows the LOCREQ encoding rules along with the following enhancements for added flexibility:

1. Allow users to specify which TCAP LOCREQ parameter (TCAP Outgoing Called Party parameter) shall encode the RN (and/or DN) information
2. Allow users to specify the DigitType value to encode the TCAP Outgoing Called Party parameter
3. Allow users to specify the value to encode the Nature of Number field of the TCAP Outgoing Called Party parameter
4. Allow users to specify the value to encode the Numbering Plan field of the TCAP Outgoing Called Party parameter
5. Allow users to specify the digit encoding format of the locreq TCAP Outgoing Called Party parameter
6. Allow users to specify the MSCID values to be encoded in the locreq message
7. Allow users to specify the ESN values to be encoded in the locreq message
8. Allow users to specify how the digits of the locreq MIN parameter shall be encoded.

The following encoding rules are followed when an SRI Ack is returned:

1. When an SRI Ack is returned, the EAGLE follows the SRI Ack encoding rules along with the following enhancements for added flexibility
2. Allow users to specify which SRI parameter (the TCAP MSRN parameter) encodes the RN (and/or DN) information
3. Allow users to specify the value to encode the Nature of Address field of the TCAP MSRN parameter
4. Allow users to specify the value to encode the Numbering Plan field of the TCAP MSRN parameter.

MNP SCCP Service Re-Route Capability

This feature is designed to handle and control re-routing of MNP traffic from an affected node to alternate nodes within an operators network. This feature is an optional feature and does not affect the normal MNP functionality. This feature consists of the following main functions:

• Service State
• MNP Re-Routing
• MNP Capability Point Codes

Service State

Service state is part of the MNP SCCP Service Re-Route Capability. Service state is used to indicate the current state of MNP, either ONLINE or OFFLINE . Service state also gives the user the option to mark MNP as OFFLINE or ONLINE based on the current behavior. If a MNP problem is identified, MNP can be marked OFFLINE to initiate the re-routing procedure. When the Service Module cards need to be reloaded, MNP can be marked OFFLINE until enough cards are in-service and then bring MNP ONLINE in a controlled fashion. This feature also provides the option to mark MNP OFFLINE to perform a controlled re-routing during this state.

MNP Re-Routing

MNP Re-Routing is an optional feature and is enabled by defining a list of alternate PCs or by defining the GTT option. MNP re-routing is activated by marking MNP OFFLINE . When MNP is OFFLINE and alternate PCs are provisioned, any messages destined for MNP are re-routed to the available alternate PCs that are defined for MNP. If alternate PCs are not provisioned or none are available, then the GTT option is used. If the GTT option is set to YES, then messages destined for MNP will fall through to GTT as part of the re-routing procedure.

Re-Routing is applied to all MNP messages (based on SRVSEL). There is no distinction of DPC of the messages. The DPC of the message can be either True, Secondary, or Capability Point code.

MNP Capability Point Codes

Capability Point Codes (CPC) are also supported for MNP. The use of MNP capability point code aids the adjacent nodes in knowing about MNP outages. When MNP is brought down though administrative commands, all traffic destined to this MNP node will generate a Transfer Prohibited (TFP) message to the adjacent node about the MNP CPC. The TFP response to the adjacent node causes the traffic originating nodes to stop sending MNP traffic to this node. All MNP traffic coming into this node is sent to the alternate MNP nodes. Adjacent nodes will initiate route-set-test procedures after receipt of the TFP response.

If the messages are destined to the EAGLE true point code, then TFP messages are not generated when the MNP service is OFFLINE . The originator would not be aware of the outage.

Once MNP is back in service on the EAGLE, a Transfer Allowed (TFA) message is sent to the traffic adjacent nodes in response to route-set-test message. The traffic originating nodes will then start sending MNP traffic to the original MNP node.

MNP Capability point codes can be provisioned when the MNP feature is ON. There can be more than one Capability Point Code assigned to MNP CPCType.

When the MNP feature is turned ON and the MNP service state is set to OFFLINE , the user can change the service to ONLINE at any point. Once the feature is turned ONLINE , MNP will start processing messages if at least one Service Module card is IS-NR.

The MNP service can be set to OFFLINE at any point. This causes the EAGLE to stop processing MNP traffic and re-routing is performed.

The MNP service state is persistent. Booting the OAM or all the Service Module cards will not change the service state. Commands must be used to change the service state.

MNP supports up to seven alternate PCs per domain. All six domains (ANSI, ITU-I, ITU-N, ITU-N spare, ITU-I spare, and ITU-N24) are supported. An entire set of alternate PCs is considered as a re-route set. A GTT option is supported for MNP re-route. When the MNP service is OFFLINE , MNP messages fall though to GTT based on the GTT option. This option is set to YES by default.

MNP SCCP Service Re-Route Capability Summary

If the MNP service is not normal (because the RTDB is not in sync with MPS or if cards are misrouting MNP messages) then the MNP service state should be changed to OFFLINE .

Before changing MNP service to OFFLINE , it should be decided what kind of re-routing will be used during the outage. The EAGLE supports re-routing data to alternate point codes or falling through to GTT as two possible options. Re-routing to alternate point code has priority over falling though to GTT. Examples of the two options follow:

Option 1

Define alternate point codes to re-route MNP traffic. This is the recommended option. Up to 7 alternate MNP nodes can be provisioned to re-route all the incoming MNP traffic. Once provisioned, the MNP service can be changed to OFFLINE . This example has any incoming being MNP traffic being load-shared to point codes based on the relative cost.

chg-sccp-serv:serv=mnp:pci1=1-1-1:rc1=10:pci2=2-2-2:rc2=10:pci3=3-3-3:rc3=10:pci4=4-4-4:rc4=10

chg-sccp-serv:serv=mnp:pci1=1-1-1:rc1=10:pci2=2-2-2:rc2=10:pci3=3-3-3:rc3=10:pci4=4-4-4:rc4=10

chg-sccp-serv:serv=mnp:pci1=5-5-5:rc1=10:pci2=6-6-6:rc2=10:pci3=7-7-7:rc3=10:pci4=8-8-8:rc4=10

chg-sccp-serv:serv=mnp:state=offline

Option 2

With this option default GTT translations are provisioned for MNP service. Then the chg-sccp-serv command is used to provision GTT=YES. All MNP messages will fall through to GTT. An example command follows:

Once the MNP re-routing data is provisioned, MNP service can be changed to OFFLINE . At this point all MNP traffic will be re-routed. The use can take necessary steps to correct the MNP service on the node. Until all the cards or enough cards are in active state with valid MNP subscriber database, MNP service should not be changed to ONLINE .

Table 2-6 shows the actions taken when the MNP service is offline, a message arrives at the affected node requiring MNP service, and the Service Module cards are available.

Numbers with fewer than five digits after the above conditioning are not used for IGM. In this case, a UIM is issued, and the message falls through to GTT.

Numbers with more than fifteen digits after the above conditioning are not used for IGM. In this case, a UIM is issued, and the message falls through to GTT.

EPAP-related features that perform an RTDB lookup require Service Module cards (E5-SM4G, E5-SM8G-B, or SLIC cards) running the SCCPHC application. The EAGLE can be equipped with up to 32 (31+1) Service Module cards.

Features that do not perform an RTDB lookup require Service Module cards only for GTT processing that might be performed for the feature. These features can coexist in systems with EPAP, but do not require an EPAP connection.