Guest

Cisco BTS 10200 Softswitch

Split NPA

  • Viewing Options

  • PDF (128.1 KB)
  • Feedback
Cisco BTS 10200 Softswitch Split NPA Feature Module

Table Of Contents

Cisco BTS 10200 Softswitch Split NPA Feature Module

Understanding the Split NPA Feature

Feature Interactions

Screening List Features

Multiple Directory Numbers Feature

Limitations

Industry Standards

Provisioning

Operating

Duplicating Records

Sample SPLIT_NPA Commands

Record Duplication in the NDC Table

Record Duplication in the EXCHANGE_CODE Table

Record Duplication in the OFFICE_CODE Table

Record Duplication in the PORTED_OFFICE_CODE Table

Record Duplication in the DIAL_PLAN Table

Record Duplication in the LSA Table

Record Duplication in the POLICY_ODR Table

Record Duplication in the REGION_PROFILE Table

Record Duplication in the NATIONAL_WB_LIST Table

Record Duplication in the ANI Table

Record Duplication in the ANI_SCREENING Table

Record Duplication in the ANI_WB_LIST Table

Record Duplication in the CHANGED_NUMBER Table

Record Duplication in the LATA_MAP Table

Updating ANI Records

Sample SPLIT_NPA Commands

Updating Records in the SUBSCRIBER Table

Updating Records in the SUBSCRIBER_FEATURE_DATA Table

Updating Records for the DIAL_PLAN Table

Updating Records for the POLICY_NXX Table

Updating Records for the DN2CUST_GRP Table

Updating Records for the CUST_GRP Table

Updating Records for the SC1D Table

Updating Records for the SC2D Table

Updating Records for the SLE Table

Updating Records for the CA_CONFIG Table

Updating Records for the CHANGED_NUMBER Table

Cleanup

Internal Cleanup Processing


Cisco BTS 10200 Softswitch Split NPA Feature Module


Revised: September 03, 2008

This document describes the Split NPA feature for Release 4.5.1 of the Cisco BTS 10200 Softswitch and explains how to use it. It includes the following topics:

Understanding the Split NPA Feature

Provisioning

Operating


Note The Split NPA feature is introduced in Release 4.5.1 of the Cisco BTS 10200 Softswitch and is available in all subsequent releases.


Understanding the Split NPA Feature

When a service provider exhausts all DNs within a numbering plan area (NPA), the service provider commonly adds another NPA to the region. The service provider can allocate the new NPA as an overlay over the existing NPA. This action does not have a major impact on the Cisco BTS 10200 Softswitch. However, the impact on the Cisco BTS 10200 is significant if the service provider assigns the new NPA to support a geographical split of the region. The result of assigning a new NPA based on a geographical split is referred to as a split NPA.

The Split NPA feature affects both the provisioning and call processing subsystems in the Cisco BTS 10200. You must perform several provisioning tasks to introduce a new NPA into a region. These tasks include:

Duplicating records (tasks to be performed before a permissive period)

Updating Automatic Number Identification (ANI) records (tasks to be performed during a permissive period)

Cleaning up (tasks to be performed after a permissive period)


Note A permissive period is time during which a caller can dial both an old NPA and the new NPA to reach subscribers who are affected by the processing of the split-NPA feature.


Before a permissive period begins, a caller can reach the subscribers who will be affected by the Split NPA only through the old NPA. You must use Split NPA to duplicate records for both the old and new NPAs before the permissive period begins.

During the permissive period, a caller can dial both the old and new NPAs (10-digit dialing is required to reach a subscriber in the affected NPA). Split NPA updates the appropriate SUBSCRIBER table and SUBSCRIBER_FEATURE_DATA table tokens to the new NPA during the permissive period.

When the permissive period ends, a caller can reach subscribers who were affected by the Split NPA only through the new NPA. This duration of time for the new NPA is referred to as the mandatory dialing period. After the mandatory dialing period begins, Split NPA cleans up the duplicated records that were created before the permissive period.

Feature Interactions

Split NPA affects some screening list features and the Multiple Directory Numbers feature.

Screening List Features

The Split NPA feature affects screening list-related features such as Selective Call Rejection (SCR), Distinctive Ringing/Call Waiting (DRCW), and Selective Call Acceptance (SCA). The screening features perform the following Split NPA checks:

1. If a screening list feature is active, the Cisco BTS 10200 performs normal screening based on the calling party number. If a match is found, Split NPA does not affect the feature.

2. If the Cisco BTS 10200 does not find a match, it checks the CA_CONFIG table for a record in which the TYPE token is set to split-npa-active and the VALUE token is set to Y. If it finds such a record, the Cisco BTS 10200 compares the NPA-NXX (6 digits) of the calling party number to the values specified for both the OLD_NPA and NEW_NPA tokens. If the Cisco BTS 10200 finds a match, Split NPA is active.

3. If the calling party number is based on the OLD_NPA, the Cisco BTS 10200 changes the NPA of the calling party number to the NEW_NPA value. If the calling party number is based on the NEW_NPA, the Cisco BTS 10200 changes the NPA of the calling party number to the OLD_NPA.

4. The Cisco BTS 10200 performs screening against the SLE table based on the new Calling Party Number string and processes the call based on the new result. That is, if the original calling party number was based on the old npa, then the Cisco BTS 10200 converts the calling party number to the new npa. If the calling party number was based on the new npa, the Cisco BTS 10200 converts it to the old npa before performing the screening again.

Multiple Directory Numbers Feature

During the permissive period, it is possible that a dialed DN may not match with FDN1, FDN2, or FDN3, which are identified in the SUBSCRIBER_FEATURE_DATA table. Split NPA performs the following checks:

1. If the Cisco BTS 10200 does not find a match, it checks the CA_CONFIG table for a record in which the TYPE token is set to split-npa-active. If the VALUE token in the same record is set to Y, the Cisco BTS 10200 checks the SPLIT_NPA table for the NPA_NXX of the dialed DN. During this query of the SPLIT_NPA table, the Cisco BTS 10200 compares the NPA_NXX (6 digits) of the dialed DN to both the OLD_NPA and NEW_NPA.

2. If a dialed DN is based on the OLD_NPA, the Cisco BTS 10200 changes the NPA of the dialed DN to the NEW_NPA. If the dialed DN is based on the NEW_NPA, the Cisco BTS 10200 changes the NPA of the dialed DN to the OLD_NPA.

3. The Cisco BTS 10200 compares the newly-formed dialed DN with FDN1, FDN2, and FDN3 to determine the Ring/Call Waiting Type.


Note The Multiple Directory Numbers feature applies only to Cisco BTS 10200 Softswitch Release 4.5.1.


Limitations

This section lists limitations. These are conditions for which the feature is not designed to work.

The Forward to Numbers for CENTREX subscribers are not updated.

Speed Call List entries with prefix digits such as 1, 101XXXX, etc., are not updated.

Industry Standards

Standard
Title

INC97-0404-016 NPA Code Relief Planning & Notification Guidelines

NPA Code Relief Planning & Notification Guidelines

GR-1251-CORE, Issue 1, June 2000

LSSGR: CLASSSM Feature: Numbering Plan Area Split Management (FSD 30-29-0000), Telcordia Technologies Generic Requirements


Provisioning

Split NPA enables the service provider to convert a specific NPA or a NPA-NXX to a new NPA by completing a series of four command steps. With Split NPA, you can divide an area served by one NPA into smaller areas served by different NPAs. You might divide an NPA area when it runs out of telephone numbers based on a particular NPA.

To start the Split NPA procedure, first you must establish a permissive period. During the permissive period, the numbers that you determine will be served by a new NPA must be reachable by a caller who dials either the old NPA or the new NPA. When the permissive period ends, a caller should be able to reach a number serviced by the new NPA only. That is, a caller cannot reach a number in the old NPA. The Split NPA procedure vacates the old NPA dialing plan, after which you can assign the old NPA dialing plan to different subscribers.

In the following example of the Split NPA procedure, NXX code (516) in NPA 972 is moved to another NPA (214):


Step 1 Add the split NPA to the Cisco BTS 10200 system, and specify start and end dates for the split.

add split-npa old-npa=972-516; new-npa=214-516; start-date=2003-10-01; 
end-date=2003-12-01;

Step 2 Duplicate records on the NPA. In tables that contain records whose digit strings are present in the old NPA, the Cisco BTS 10200 duplicates those records.

change split-npa old-npa=972-516; duplicate_records=Y;

Step 3 After the start date, issue the command that initiates the update-ani operation, which updates the subscriber directory numbers to the new NPA. (see the "Updating ANI Records" section).

change split-npa old-npa=972-516; update-ani=Y;

Step 4 After the end date, issue the command that initiates the cleanup action. The records duplicated in Step 2 are removed.

change split-npa old-npa=972-516; cleanup=Y;


Operating

The processing of Split NPA affects a significant number of the Cisco BTS CLI database tables from the initiation of the feature through the final cleanup process. This section describes how Split-NPA alters the contents of the effected database tables.

Duplicating Records

When the Cisco BTS 10200 processes Split NPA, it must duplicate records in several of the Cisco BTS CLI Database tables. As stated previously, records must be duplicated to enable a caller to direct a call to a subscriber by way of the old or new NPA during the permissive period. When you issue a command that sets the DUP_RECORDS token in the SPLI_NPA table to Y, the Cisco BTS 10200 changes the value of the DUP_RECORDS_STATUS token to IN_PROGRESS.

The Cisco BTS 10200 starts to duplicate records in the following tables when it changes the records in the SPLIT_NPA table:

NDC Table (National Destination Code)

EXCHANGE_CODE Table

OFFICE_CODE Table

PORTED_OFFICE_CODE Table

DIAL_PLAN Table

LSA Table (Local Service Area)

POLICY_ODR Table (Policy Origin Dependent Routing)

REGION_PROFILE Table

NATIONAL_WB_LIST Table (National White Black List)

ANI Table (Automatic Number Identification)

ANI_SCREENING Table (Automatic Numbering Identification Screening)

ANI_WB_LIST Table (Automatic Numbering Identification White Black List)

CA_CONFIG Table (Call Agent Configuration)

CHANGED_NUMBER Table

LATA_MAP Table (Local Access And Transport Area Map)

When the Cisco BTS 10200 completes duplicating records in the preceding tables, it sets the DUP_RECORDS_STATUS token in the SPLIT_NPA table to COMPLETED.

Sample SPLIT_NPA Commands

Example 1

The following command duplicates records for only one NPANXX (in this example, 214-671).

change split_npa old_npa=214-671; dup_records=y;

Example 2

The following command duplicates records for all NXXs that are specified in the SPLIT_NPA table and that belong to the specified NPA (in this example, 214)

change split_npa old_npa=214; dup_records=y;

Record Duplication in the NDC Table

When the Cisco BTS 10200 begins to process the Split NPA feature, it queries the NDC table. If the value specified for the token DIGIT_STRING matches the value specified for the token OLD_NPA in the SPLIT_NPA table, the Cisco BTS 10200 retains that record and adds another DIGIT_STRING record to match the value specified for NEW_NPA in the SPLIT_NPA table.

Since this is applicable to North America, the DIGIT_STRING value specified in the NDC record represents the NPA portion of the value set for the NEW_NPA token in the SPLIT_NPA table.

Record Duplication in the EXCHANGE_CODE Table

When the Cisco BTS 10200 begins to process the Split NPA feature, it queries the EXCHANGE_CODE table. If the concatenated values specified for the NDC and EC tokens matches the value specified for OLD_NPA in the SPLIT_NPA table, the Cisco BTS 10200 retains the present values of NDC and EC and adds another NDC record to match the value specified for NEW_NPA in the SPLIT_NPA table.

Record Duplication in the OFFICE_CODE Table

When the Cisco BTS 10200 begins to process the Split NPA feature, it queries the OFFICE_CODE table. If the value specified for the DIGIT_STRING token matches the value specified for the token OLD_NPA in the SPLIT_NPA table, the Cisco BTS 10200 retains that record and adds another DIGIT_STRING record to match the value specified for NEW_NPA in the SPLIT_NPA table.

Record Duplication in the PORTED_OFFICE_CODE Table

When the Cisco BTS 10200 begins to process the Split NPA feature, it queries the PORTED_OFFICE_CODE table. If the value specified for the DIGIT_STRING token matches the value specified for the token OLD_NPA in the SPLIT_NPA table, the Cisco BTS 10200 retains that record and adds another DIGIT_STRING record to match the value specified for NEW_NPA in the SPLIT_NPA table.

Record Duplication in the DIAL_PLAN Table

When the Cisco BTS 10200 begins to process the Split NPA feature, it queries the DIAL_PLAN table. If the value specified for the DIGIT_STRING token matches the value specified for the token OLD_NPA in the SPLIT_NPA table, the Cisco BTS 10200 retains that record and adds another DIGIT_STRING record to match the value specified for NEW_NPA in the SPLIT_NPA table.


Note The Cisco BTS 10200 adds a record with DIGIT_STRING set to match the value of NEW_NPA only if the NOA token in the DIAL_PLAN table is set to NATIONAL.



Note The digits specified for the OLD_NPA token in the SPLIT_NPA table should match the value specified for DIGIT_STRING in the DIAL_PLAN table. However, if more that 6 digits are specified for the DIGIT_STRING token in the DIAL_PLAN table, but the first 6 digits match the digits in the OLD_NPA value in the SPLIT_NPA table, the Cisco BTS 10200 considers the values a match.


The DIAL_PLAN table includes a SPLIT_NPA token that can be set to one of three values: NONE, OLD_NPA, NEW_NPA. When the Cisco BTS 10200 processes the Split NPA feature and queries the DIAL_PLAN table, if the SPLIT_NPA token is set to NONE, the Cisco BTS 10200 changes the record so that the SPLIT_NPA token is set to OLD_NPA. Similarly, the Cisco BTS 10200 also adds a record in which the SPLIT_NPA token is set to NEW_NPA and the DIGIT_STRING token is set to match the value specified for NEW_NPA in the SPLIT_NPA table.

The following sample records show the record processing described in the preceding paragraph.

If DIAL_PLAN table contains the record:

id=1; digit_string=214-671; reqd_digits=10; dest_id=d671; split-npa=none; 
del-digits=3; pfx-digits=NULL;

The Cisco BTS 10200 changes the existing record as follows:

change id=1; digit_string=214-671; split_npa=old_npa; 

The Cisco BTS 10200 inserts the following records in the DIAL_PLAN table to match the values specified for OLD_NPA and NEW_NPA in the SPLIT_NPA table:

add id=1; digit_string=972-671; reqd_digits=10; dest_id=D671; split-npa=new_npa; 
del-digits=3; pfx-digits=NULL;

Record Duplication in the LSA Table

When the Cisco BTS 10200 begins to process the Split NPA feature, it queries the LSA table. If the value specified for the DIGIT_STRING token matches the value specified for the token OLD_NPA in the SPLIT_NPA table, the Cisco BTS 10200 retains that record and adds another DIGIT_STRING record to match the value specified for NEW_NPA in the SPLIT_NPA table.

Record Duplication in the POLICY_ODR Table

When the Cisco BTS 10200 begins to process the Split NPA feature, it queries the POLICY_ODR table. If the value specified for the DIGIT_STRING token matches the value specified for the token OLD_NPA in the SPLIT_NPA table, the Cisco BTS 10200 retains that record and adds another DIGIT_STRING record to match the value specified for NEW_NPA in the SPLIT_NPA table.

Record Duplication in the REGION_PROFILE Table

When the Cisco BTS 10200 begins to process the Split NPA feature, it queries the REGION_PROFILE table. If the value specified for the DIGIT_STRING token matches the value specified for the token OLD_NPA in the SPLIT_NPA table, the Cisco BTS 10200 retains that record and adds another DIGIT_STRING record to match the value specified for NEW_NPA in the SPLIT_NPA table.

Record Duplication in the NATIONAL_WB_LIST Table

When the Cisco BTS 10200 begins to process the Split NPA feature, it queries the NATIONAL_WB_LIST table. If the value specified for the DIGIT_STRING token matches the value specified for the token OLD_NPA in the SPLIT_NPA table, the Cisco BTS 10200 retains that record and adds another DIGIT_STRING record to match the value specified for NEW_NPA in the SPLIT_NPA table.

Record Duplication in the ANI Table

When the Cisco BTS 10200 begins to process the Split NPA feature, it queries the ANI table. If the value specified for the ID token matches the value specified for the token OLD_NPA in the SPLIT_NPA table, the Cisco BTS 10200 retains that record and adds another ID record to match the value specified for NEW_NPA in the SPLIT_NPA table.

Record Duplication in the ANI_SCREENING Table

To support the Split NPA feature, in the ANI_SCREENING table, you must manually reprovision records in which you want to set the FROM_DN token or TO_DN token to match the OLD_NPA in the SPLIT_NPA table. You may not create records in which you set the FROM_DN token or TO_DN token to match the NEW_NPA in the SPLIT_NPA table if either the FROM_DN or TO_DN belongs to a different NPA. Instead, you must duplicate all of the ANI_SCREENING table records in which the FROM_DN or TO_DN matches the OLD_NPA. Then you must create records for which you want the FROM_DN or TO_DN to match the NEW_NPA.

Record Duplication in the ANI_WB_LIST Table

When the Cisco BTS 10200 begins to process the Split NPA feature, it queries the ANI_WB_LIST table. If the value specified for the DIGIT_STRING token matches the value specified for the token OLD_NPA in the SPLIT_NPA table, the Cisco BTS 10200 retains that record and adds another DIGIT_STRING record to match the value specified for NEW_NPA in the SPLIT_NPA table.

Record Duplication in the CHANGED_NUMBER Table

When the Cisco BTS 10200 begins to process the Split NPA feature, it queries the CHANGED_NUMBER table. If the value specified for the OLD_DN token matches the value specified for the token OLD_NPA in the SPLIT_NPA table, the Cisco BTS 10200 retains that record and adds another OLD_DN record to match the value specified for NEW_NPA in the SPLIT_NPA table.

Record Duplication in the LATA_MAP Table

When the Cisco BTS 10200 begins to process the Split NPA feature, it queries the LATA_MAP table. If the value specified for the DIGIT_STRING token matches the value specified for the token OLD_NPA in the SPLIT_NPA table, the Cisco BTS 10200 retains that record and adds another DIGIT_STRING record to match the value specified for NEW_NPA in the SPLIT_NPA table.

Updating ANI Records

When the Cisco BTS 10200 processes Split NPA, its major task is to convert data records in the SUBSCRIBER and SUBSCRIBER_FEATURE_DATA tables to include records for the new NPA. The Cisco BTS 10200 begins this data conversion when an operator issues a command that sets the UPDATE_ANI token in the SPLIT_NPA table to Y.

When the UPDATE_ANI token is set to Y, the Cisco BTS 10200 updates the UPDATE_ANI_STATUS token to IN_PROGRESS and begins to modify records in the following Cisco BTS CLI Database tables:

SUBSCRIBER Table

SUBSCRIBER_FEATURE_DATA Table

DIAL_PLAN Table

POLICY_NXX Table

DN2CUST_GRP Table (DN2 Customer Group)

CUST_GRP Table (Customer Group)

SC1D Table (Speed Call One Digit)

SC2D Table (Speed Call Two Digit)

SLE Table (Screening List Editing)

CA_CONFIG Table (Call Agent Configuration)

CHANGED_NUMBER Table

When the Cisco BTS 10200 completes updating records in the SUBSCRIBER and SUBSCRIBER_FEATURE_DATA tables, it sets the UPDATE_ANI_STATUS token in the SPLIT_NPA table to COMPLETED.

Sample SPLIT_NPA Commands

During the permissive period, the Cisco BTS 10200 begins to convert ANI records in the SUBSCRIBER and SUBSCRIBER_FEATURE_DATA tables when the UPDATE_ANI token is set to Y.

Example

The following command updates subscriber records for only one NPANXX (214-671):

change split_npa old_npa=214-671; update_ani=y;

The following command updates subscriber records for all NXXs specified in the SPLIT_NPA table that belong to the specified NPA (214):

change split_npa old_npa=214; update_ani=y;

Updating Records in the SUBSCRIBER Table

To update records, the Cisco BTS 10200 searches the SUBSCRIBER table for all DN values that are included in the old NPA (DN1, DN2, DN3, etc.). The Cisco BTS 10200 updates the records for the relevant DNs and for the associated BILLING_DN. The following commands represent the internal processing that the Cisco BTS 10200 performs to update SUBSCRIBER table records for a DN1 and a BILLING_DN.

change subscriber id=* (for example, dn1=214-671-xxxx is updated to dn1=972-671-xxxx)

change subscriber id=* (for example, billing-dn=214-671-xxxx is updated to billing-dn=972-671-xxxx)


Note The Cisco BTS 10200 processes the updating of ANI records internally. The service provider does not need to perform any task.


When the Cisco BTS 10200 completes updating records in the SUBSCRIBER and SUBSCRIBER_FEATURE_DATA tables, it sets the UPDATE_ANI_STATUS token in the SPLIT_NPA table to COMPLETED.

Updating Records in the SUBSCRIBER_FEATURE_DATA Table

The Split NPA feature can affect the following features that can be provisioned in the SUBSCRIBER_FEATURE_DATA table:

Selective Call Acceptance (SCA)

Multiple Directory Number (MDN)

Hotline

Warmline


Note During Split NPA processing, the Cisco BTS 10200 modifies records only for POTS subscribers. The Cisco BTS 10200 does not modify data for CENTREX subscribers.


To update records, the Cisco BTS 10200 searches the SUBSCRIBER_FEATURE_DATA table for FNAME and TYPE pairs that are set to digit values that are included in the old NPA. The Cisco BTS 10200 updates records associated with the old NPA to records that are correctly associated with the new NPA.

The following sample command represents the internal processing that the Cisco BTS 10200 performs to update SUBSCRIBER_FEATURE_DATA table records for a subscriber that is provisioned for CFU:

change subscriber_feature_data sub_id=* (for example, fname=cfu, type1=fdn1, 
value1=214-671-xxxx is updated to value1=972-671-xxxx;

Updating Records for the DIAL_PLAN Table

The Cisco BTS 10200 searches the DIAL_PLAN table for a value set for the DIGIT_STRING token that matches the NXX portion of the value specified for OLD_NPA, and a value specified for the PFX_DIGITS token that matches the NPA portion of OLD_NPA. When it finds a match, the Cisco BTS 10200 updates the value specified for PFX_DIGITS to the NPA portion of NEW_NPA.


Note The Cisco BTS 10200 updates records for the DIAL_PLAN table only if the NOA token is set to SUBSCRIBER.


Updating Records for the POLICY_NXX Table

The Cisco BTS 10200 searches the POLICY_NXX table for values specified for the TRANSLATED_DN token that match values specified for the OLD_NPA token in the SPLIT_NPA table. When it finds a match, the Cisco BTS 10200 updates the value specified for TRANSLATED_DN to the new NPA.

Updating Records for the DN2CUST_GRP Table

The Cisco BTS 10200 searches the DN2CUST_GRP table for values specified for the TRANSLATED_DN token that match values specified for the OLD_NPA token in the SPLIT_NPA table. When it finds a match, the Cisco BTS 10200 updates the value specified for TRANSLATED_DN to the new NPA.

Updating Records for the CUST_GRP Table

The Cisco BTS 10200 searches the CUST_GRP (Customer Group) table for values specified for the OVERFLOW_POTS token that match values specified for the OLD_NPA token in the SPLIT_NPA table. When it finds a match, the Cisco BTS 10200 updates the value specified for OVERFLOW_POTS to the new NPA.

Updating Records for the SC1D Table

The Cisco BTS 10200 searches the SC1D (Speed Call One Digit) table for values specified for the DN token that match the value specified for the OLD_NPA token in the SPLIT_NPA table. When it finds a match, the Cisco BTS 10200 updates the value specified for DN to the new NPA.

Updating Records for the SC2D Table

The Cisco BTS 10200 searches the SC2D (Speed Call Two Digit) table for values specified for the DN token that match the value specified for the OLD_NPA token in the SPLIT_NPA table. When it finds a match, the Cisco BTS 10200 updates the value specified for DN to the new NPA.

Updating Records for the SLE Table

The Cisco BTS 10200 searches the SLE (Screening List Editing) table for values specified for the DN token that match the value specified for the OLD_NPA token in the SPLIT_NPA table. When it finds a match, the Cisco BTS 10200 updates the value specified for DN to the new NPA.

Updating Records for the CA_CONFIG Table

The Cisco BTS 10200 searches the CA_CONFIG (Call Agent Configuration) table for values specified for the VALUE token that match the value specified for the OLD_NPA token in the SPLIT_NPA table. For the CA_CONFIG table, the Cisco BTS 10200 searches for a value set for the TYPE token such as ivr-dn. The DN digits are set with the VALUE token.(These DNs are used to access the Interactive Voice Response (IVR) feature.) When it finds a match, the Cisco BTS 10200 updates the value specified for VALUE to the new NPA.

Updating Records for the CHANGED_NUMBER Table

The Cisco BTS 10200 searches the CHANGED_NUMBER table for values specified for the NEW_DN token that match the value specified for the OLD_NPA in the SPLIT_NPA table. When it finds a match, the Cisco BTS 10200 updates the value specified for NEW_DN to the new NPA.

Cleanup

When the Split NPA permissive period ends, the Cisco BTS 10200 must cleanup the database records that remain associated with the old NPA. The following command performs cleanup for only one NPANXX (214-671).

change split_npa old_npa=214-671; cleanup=y;

The following command performs cleanup for all NXXs specified in the SPLIT_ NPA table belonging to the specified NPA (214).

change split_npa old_npa=214; cleanup=y;

When the CLEANUP token in the SPLIT_NPA table is set to Y, the Cisco BTS 10200 updates the status of the CLEANUP token to IN_PROGRESS and removes records from the following tables that point to the old NPA:

EXCHANGE_CODE Table

DIAL_PLAN Table

OFFICE_CODE Table

PORTED_OFFICE_CODE Table

LSA Table (Local Service Area)

POLICY_ODR Table (Policy Origin Dependent Routing)

REGION_PROFILE Table

NATIONAL_WB_LIST Table (National White Black List)

ANI Table (Automatic Number Identification)

ANI_SCREENING Table (Automatic Numbering Identification Screening)

ANI_WB_LIST Table (Automatic Numbering Identification White Black List)

CHANGED_NUMBER Table

LATA_MAP Table (Local Access And Transport Area Map)

CA_CONFIG Table (Call Agent Configuration)

When the Cisco BTS 10200 completes the cleanup process, it sets the status of the CLEANUP token to COMPLETED. When the cleanup process is complete, the Cisco BTS 10200 deletes the Split NPA records.

Internal Cleanup Processing

No action is required by the service provider for the Split NPA cleanup process.

EXCHANGE_CODE Table Cleanup

The Cisco BTS 10200 deletes EXCHANGE_CODE table records in which the value specified for the NDC token match the value of the OLD_NPA token in the SPLIT_NPA table.

DIAL_PLAN Table Cleanup

The Cisco BTS 10200 deletes DIAL_PLAN table records in which the value specified for the DIGIT_STRING token matches the value specified for the OLD_NPA token in the SPLIT_NPA table.

The Cisco BTS 10200 also updates the value of the SPLIT_NPA token to NONE, when the value of the DIGIT_STRING token matches the value specified for the NEW_NPA token in the SPLIT_NPA table.

OFFICE_CODE Table Cleanup

The Cisco BTS 10200 deletes OFFICE_CODE table records in which the value specified for the DIGIT_STRING token matches the value specified for the OLD_NPA token in the SPLIT_NPA table.

PORTED_OFFICE_CODE Table Cleanup

The Cisco BTS 10200 deletes PORTED_OFFICE_CODE table records in which the value specified for the DIGIT_STRING token matches the value specified for the OLD_NPA token in the SPLIT_NPA table.

LSA Table Cleanup

The Cisco BTS 10200 deletes LSA table records in which the value specified for the DIGIT_STRING token matches the value specified for the OLD_NPA token in the SPLIT_NPA table.

POLICY_ODR Table Cleanup

The Cisco BTS 10200 deletes POLICY_ODR table records in which the value specified for the DIGIT_STRING token matches the value specified for the OLD_NPA token in the SPLIT_NPA table.

REGION_PROFILE Table Cleanup

The Cisco BTS 10200 deletes REGION_PROFILE table records in which the value specified for the DIGIT_STRING token matches the value specified for the OLD_NPA token in the SPLIT_NPA table.

NATIONAL_WB_LIST Table Cleanup

The Cisco BTS 10200 deletes NATIONAL_WB_LIST table records in which the value specified for the DIGIT_STRING token matches the value specified for the OLD_NPA token in the SPLIT_NPA table.

ANI Table Cleanup

The Cisco BTS 10200 deletes ANI table records in which the value specified for the DIGIT_STRING token matches the value specified for the OLD_NPA token in the SPLIT_NPA table.

ANI_SCREENING Table Cleanup

For the records you manually duplicated in the ANI_SCREENING table, you must manually delete all records in which the FOR_DN token or TO_DN token was set to match the OLD_NPA in the SPLIT_NPA table.

ANI_WB_LIST Table Cleanup

The Cisco BTS 10200 deletes ANI_WB_LIST table records in which the value specified for the DIGIT_STRING token matches the value specified for the OLD_NPA token in the SPLIT_NPA table.

CHANGED_NUMBER Table Cleanup

The Cisco BTS 10200 deletes CHANGED_NUMBER table records in which the value specified for the OLD_DN token matches the value specified for the OLD_NPA token in the SPLIT_NPA table.

LATA_MAP Table Cleanup

Records in the LATA_MAP table are not affected in the cleanup phase.


Note Upon examination, if an operator detects record entries that are not required, the operator should remove them manually.


CA_CONFIG Table Cleanup

During the cleanup stage, when there are no more records in the SPLIT_ NPA table that must be cleaned up, the Cisco BTS 10200 changes the setting of the VALUE token in the split-npa-active record in the CA_CONFIG table to N.