Cisco BTS 10200 Softswitch Routing and Dial Plan Guide, Release 7.0

Subsciber and Sub-Profile

Step 2 Get the subscriber table (sub-profile identification (ID)).

Step 3 Get the subscriber-profile table (dial-plan-identification (DP-ID)).

Example:

Step 4 Go to the dial-plan (based on DP-ID).

Step 5 Go to destination table and get the call type and destination.

Example:

Step 6 Determine the call type. If the call type is toll free, 900, or 500, proceed to Step 7. If the call type is casual, proceed to Step 8. If the call type is via a presubscribed interexchange carrier (PIC), proceed to Step 9.

Examples:

Step 7 If the call type is toll free, 900, or 500, the Cisco BTS 10200 will use the dial plan to select the call route and to route the call.

Step 8 If the call type is casual, the Cisco BTS 10200 will use the carrier routing information to select the call route and to route the call.

Step 9 If the call type is via a PIC, the Cisco BTS 10200 will user the PIC carrier routing information to select the call route and to route the call.

Figure 6-1 Basic Subscriber Routing

Basic Trunk Routing

This section provides a detailed description of the Cisco BTS 10200 basic trunk routing and provides CLI examples. For detailed information on the CLI, refer to the Cisco BTS 10200 Softswitch CLI Database. Refer to Figure 6-2 for visual representation of basic trunk routing flow and review the following detailed basic trunk routing flow.

Step 1 Trunk group (TG) call received or placed.

Example:

Trunk-grp 6969

Step 2 Get the DP-ID from the TG.

Example:

Trunk-grp 6969

Step 3 Go to the dial-plan and get the destination based on the digits and DP-ID.

Example:

Step 4 Go to the destination table and get the call type and the route.

Example:

Step 5 Determine the call type. If the call type is toll free, 900, or 500, proceed to Step 6. If the call type is local traffic, proceed to Step 7. If the call type is casual service provider (SP), proceed to Step 8. If the call type is transit network selection (TNS), proceed to Step 9. If the call type is TG carrier, proceed to Step 10. If the call type is TG SP, proceed to Step 11.

Example:

Step 6 If the call type is toll free, 900, or 500, the Cisco BTS 10200 will use the dial plan to select the call route and to route the call.

Examples:

Step 7 If the call type is local traffic, the Cisco BTS 10200 will use the dial plan to select the call route and to route the call.

Examples:

Trunk-grp 6969

Step 8 If the call type is casual SP, the Cisco BTS 10200 will use the SP routing to select the call route and to route the call. If the SP routing is not found, the Cisco BTS 10200 will user the dial plan to select the call route and to route the call.

Examples:

Step 9 If the call type is TNS, the Cisco BTS 10200 will use the carrier routing to select the call route and to select the call route and to route the call. If the carrier routing is not found, the Cisco BTS 10200 will user the dial plan to select the call route and to route the call.

Examples:

Step 10 If the call type is TG carrier, the Cisco BTS 10200 will use the carrier routing to select the call route and to route the call. If the carrier routing is not found, the Cisco BTS 10200 will user the dial plan to select the call route and to route the call.

Step 11 If the call type is TG SP, the Cisco BTS 10200 will the SP routing to select the call route and to route the call. If the SP routing is not found, the Cisco BTS 10200 will user the dial plan to select the call route and to route the call.

Examples:

Carrier 9999 Use Dial-Plan "N"

Figure 6-2 Basic Trunk Routing

Carrier Based Routing

This section provides a detailed description of the Cisco BTS 10200 carrier based routing and provides CLI examples. For detailed information on the CLI, refer to the Cisco BTS 10200 Softswitch CLI Database. Refer to Figure 6-3 for visual representation of carrier based routing flow and review the following detailed carrier based routing flow.

Additionally, LNP-QUERY has been added to the call flow. LNP-QUERY specifies whether to perform a local number portability (LNP) query on the call type. LNP_QUERY applies only if the ALL-CALL-QUERY flag in the LNP-PROFILE table is set to Y and the ACQ-LNP-QUERY token in the Destination table is set to ACQ-BASED-ON-CALL-TYPE. For complete LNP-QUERY details, refer to the Cisco BTS 10200 Softswitch CLI Database and the "NOA Routing (ITU Local Number Portability)" section on page 2-12.

Step 1 Carrier based routing call is received.

Step 2 Determine if the carrier is being screened. If the carrier is being screened, proceed to Step 3. If the carrier is not being screened, proceed to Step 4.

Example:

Step 3 If the carrier is being screened, the Cisco BTS 10200 will determine if the carrier call processing is being remotely blocked (RTM_CP_BLOCK). If the carrier call processing is being remotely blocked, the call cannot be completed and will be dropped.

Step 4 If the carrier is not being screened, the Cisco BTS 10200 will determine if the carrier is a recognized service provider. If the carrier is a recognized service provider, proceed to Step 5. If the carrier is not a recognized service provider, proceed to Step 6.

Example:

Carrier - Service-Provider

Step 5 If the carrier is a recognized service provider, the Cisco BTS 10200 will use the service provider routing to select the call route and to route the call.

Example:

Service Provider

Step 6 If the carrier is not a recognized service provider, the Cisco BTS 10200 will determine if a carrier dial plan is configured. If a carrier dial plan is configured, proceed to Step 7. If a carrier dial plan, is not configured proceed to Step 8.

Example:

Carrier Use Dial-Plan "Y"

Carrier 9999 Use Dial-Plan "N"

Step 7 If a carrier dial plan is configured, the Cisco BTS 10200 will use the carrier dial plan to select the call route and to route the call.

Step 8 If a carrier dial plan is not configured, the Cisco BTS 10200 will determine if a carrier remote call processing to local exchange carrier operations support system is available (RTM_CP_CARRIER_2_LECOSS). If the RTM_CP_CARRIER_2_LECOSS is available, proceed to Step 9. If the RTM_CP_CARRIER_2_LECOSS is not available, proceed to Step 10.

Note Step 8 is skipped for toll traffic. If the traffic is toll traffic, proceed to Step 10.

Step 9 If the RTM_CP_CARRIER_2_LECOSS is available and if the traffic is not toll traffic, the Cisco BTS 10200 will use the RTM_CP_CARRIER_2_LECOSS to select the call route and to route the call.

Example:

Carrier All=N

Step 10 If the RTM_CP_CARRIER_2_LECOSS is not available, the Cisco BTS 10200 will use the carrier guide index to select the call route and to route the call.

Example:

Carrier All=Y

Figure 6-3 Carrier Based Routing

Basic Dial Plan Routing

This section provides a detailed description of the Cisco BTS 10200 basic dial plan routing and provides CLI examples. For detailed information on the CLI, refer to the Cisco BTS 10200 Softswitch CLI Database. Refer to Figure 6-4 for visual representation of basic dial plan routing flow and review the following detailed basic dial plan routing flow.

Step 1 Basic dial plan routing call received.

Step 2 Determine if the nature of address (NOA) for the received call is an international call. If the call is an international call, the Cisco BTS 10200 uses the international dial plan to select the call route and to route the call. If the call is not an international call, proceed to Step 3.

Example:

Dial-Plan Ca-Config

Step 3 Determine if the call destination is found. If the call destination is not found, the Cisco BTS 10200 returns a destination not found response (not found) and drops the call. If the call destination is found, proceed to Step 4.

Step 4 Determine if a call destination subscriber is found. If a call destination subscriber is found, the Cisco BTS 10200 returns a subscriber (SUB) response and uses the subscriber information to select the call route and to route the call. If a call destination subscriber is not found, proceed to Step 5.

Example:

Destination SUB

Step 5 Determine if a call destination route is found. If a call destination route is found, the Cisco BTS 10200 returns a destination (DEST) response and uses the route guide index to select the call route and to route the call. If a call destination route is not found, proceed to Step 6.

Example:

Destination ROUTE

Step 6 Determine if a call destination route identification (RID) is found. If a call destination RID is found, the Cisco BTS 10200 returns a DEST response and uses the route index to select the call route and to route the call. If a call destination RID is not found, proceed to Step 7.

Example:

Destination RID

Step 7 Determine if a destination carrier is found. If a destination carrier is found, proceed to the Step 8. If a destination carrier is not found, the Cisco BTS 10200 returns an error and drops the call.

Example:

Destination Carrier

Step 8 Determine the call type. If the call type is toll free, 900, or 500, the Cisco BTS 10200 selects the call route and routes the call using the destination carrier routing. If the call type is not toll free, 900, or 500, the Cisco BTS 10200 returns an error and drops the call.

Figure 6-4 Basic Dial Plan Routing

Cluster Routing

This section provides an overview of CLI commands that you need to implement the Cluster Network/Routing supported by the Cisco BTS 10200 in Release 5.0.

The CLI commands provided in the following sections are not in any particular sequence, and could be executed in any order as long as dependencies of the table in question are already in place. The main intention of this document is to summarize the CLI commands that would be needed to implement cluster networking.

Creating a Cluster Network with Three CMS/MGCs

Figure 6-5 illustrates creation of a cluster network with three CMS/MGCs.

Figure 6-5 Creating a Cluster Network with Three CMS/MGC

1. Clustering requires switches to have their individual point codes and here we are assuming the existing three switches to already have point codes of OPC10, OPC11 and OPC12.

2. The Cisco BTS 10200 switches have an Intra-cluster TG (SIP TG) connected between each of them as shown in the diagram. (Basically each CMS/MGC in the network needs to have direct connectivity with the other switches.)

add trunk-grp id=sip_1_2 ;tg-type=sip;dial-plan-id=cluster-dial-plan;

tsap-addr=CMS2;

add trunk-grp id=sip_1_3 ;tg-type=sip;dial-plan-id=cluster-dial-plan;

tsap-addr=CMS3;

add trunk-grp id=sip_2_3 ;tg-type=sip;dial-plan-id=cluster-dial-plan;

tsap-addr=CMS3;

add trunk-grp id=sip_2_1 ;tg-type=sip;dial-plan-id=cluster-dial-plan;

tsap-addr=CMS1;

add trunk-grp id=sip_3_1 ;tg-type=sip;dial-plan-id=cluster-dial-plan;

tsap-addr=CMS1;

add trunk-grp id=sip_3_2 ;tg-type=sip;dial-plan-id=cluster-dial-plan;

tsap-addr=CMS2;

Make sure the POI flag in the trunk-grp table for each of the trunk-grp's added above is set to INTRA-CLUSTER.

3. Decide on a CLRN (assuming it to be 972-999-9999 in this case) and provision the CLRN into each of the CMS/MGCs. The CLRN also needs to be registered in the LNP database.

On CMS1/CMS2/CMS3:

add ndc digit-string=972;

add exchange-code ndc=972;ec=999;office-code-index=1;

add office-code ndc=972;ec=999;call-agent-id=CA146;dn-group=xxxx;

add dn2subscriber office_code_index=1;dn=9999;status=CLRN;

4. Each CMS/MGC needs to have a separate NPA-NXX.

This basically means each CMS needs to handle a separate NPA-NXX, so as shown in the diagram we have CMS1 handling 972-233, CMS2 handling 469-255 and CMS3 handling 214-265.

5. Provision the cluster dial plan (NPA-NXX routing) in each of the CMS/MGCs to reach each other.

On CMS1:

add cluster-dial-plan-profile id=cdpp;

add route id=CMS3;tgn1_id=sip_1_3;

add route id=CMS2;tgn1_id=sip_1_2;

add destination dest-id=CMS3;route-type=ROUTE-ID;route-id=CMS3;call-type=LOCAL;

add destination dest-id=CMS2;route-type=ROUTE-ID;route-id=CMS2;call-type=LOCAL;

add dial-plan id=cdpp;digit-string=214-265;dest-id=CMS3;

add dial-plan id=cdpp;digit-string=469-255;dest-id=CMS2;

add ca-config;cluster-dial-plan id=cdpp;

For CMS2:

add cluster-dial-plan-profile id=cdpp;

add route id=CMS1;tgn1_id=sip_2_1;

add route id=CMS3;tgn1_id=sip_2_3;

add destination dest-id=CMS1;route-type=ROUTE-ID;route-id=CMS1;call-type=LOCAL;

add destination dest-id=CMS3;route-type=ROUTE-ID;route-id=CMS3;call-type=LOCAL;

add dial-plan id=cdpp;digit-string=972-233;dest-id=CMS1;

add dial-plan id=cdpp;digit-string=214-265;dest-id=CMS3;

add ca-config;cluster-dial-plan id=cdpp;

For CMS3:

add cluster-dial-plan-profile id=cdpp;

add route id=CMS1;tgn1_id=sip_3_1;

add route id=CMS2;tgn1_id=sip_3_2;

add destination dest-id=CMS1;route-type=ROUTE-ID;route-id=CMS1;call-type=local;

add destination dest-id=CMS2;route-type=ROUTE-ID;route-id=CMS2;call-type=local;

add dial-plan id=cdpp;digit-string=972-233;dest-id=CMS1;

add dial-plan id=cdpp;digit-string=469-255;dest-id=CMS2;

add ca-config;cluster-dial-plan id=cdpp;

Ported-In Sub from PSTN into CMS1

Imagine a subscriber from PSTN (972-384-1234) ported into one of the CMSs in the cluster—say CMS1. If a subscriber on any of the CMSs makes a call to that ported number this is the provisioning needed.

On CMS1:

add ported-office-code digit-string=972-384;

add dn2subscriber office-code-index=1;dn=1234;;status=assigned;lnp_trigger=y;

On CMS2:

add ported-office-code digit-string=972-384;

add dial-plan id=cdpp;digit-string=972-384;dest-id=CMS1;

On CMS3:

add ported-office-code digit-string=972-384;

add dial-plan id=cdpp;digit-string=972-384;dest-id=CMS1;

If the call comes in from the PSTN for this ported number, it would have already come in with a CLRN number. It depends on which CMS in the cluster receives the call ffirst. Assume that CMS3 received the call (since it's a CLRN), CMS3 would look up the GAP and route the call to CMS1 as specified in the cluster dial plan entries.

Adding One More CMS/MGC to a Cluster Network

Figure 6-6 illustrates adding one more CMS/MGC to a cluster network.

Figure 6-6 Adding One More CMS/MGC to the Cluster Network

1. Assign separate point codes for the new CMS/MGC switch.

add opc id=13; point-code=4-4-4; description=CMS 04 ; (On CMS4)

add dpc id=PSTN;point-code=x-x-x; description= PSTN conn from CMS4;

2. Have an Intra-cluster TG (SIP TG) connected between each of them as shown in the diagram.

On CMS4:

add trunk-grp id=sip_4_1 ;tg-type=sip;dial-plan-id=cluster-dial-plan; tsap-addr=CMS1;

add trunk-grp id=sip_4_2 ;tg-type=sip;dial-plan-id=cluster-dial-plan; tsap-addr=CMS2;

add trunk-grp id=sip_4_3 ;tg-type=sip;dial-plan-id=cluster-dial-plan; tsap-addr=CMS3;

On CMS1:

add trunk-grp id=sip_1_4 ;tg-type=sip;dial-plan-id=cluster-dial-plan; tsap-addr=CMS4;

On CMS2:

add trunk-grp id=sip_2_4 ;tg-type=sip;dial-plan-id=cluster-dial-plan; tsap-addr=CMS4;

On CMS3:

add trunk-grp id=sip_3_4 ;tg-type=sip;dial-plan-id=cluster-dial-plan; tsap-addr=CMS4;

3. Add an entry in dn2sub table for the CLRN of the cluster which is 972-999-9999.

add ndc digit-string=972;

add exchange-code ndc=972;ec=999;office-code-index=1;

add office-code ndc=972;ec=999;call-agent-id=CA146;dn-group=xxxx;

add dn2subscriber office_code_index=1;dn=9999;status=CLRN;

4. Each switch needs to have its own NPA-NXX, so let's assume CMS4 handles 972-682-xxxx.

5. Provision the cluster dial plan (NPA-NXX routing) in each of the CMS/MGC switches to reach the others.

On CMS4:

add cluster-dial-plan-profile id=cdpp;

add route id=CMS1;tgn1_id=sip_4_1;

add route id=CMS2;tgn1_id=sip_4_2;

add route id=CMS3;tgn1_id=sip_4_3;

add destination dest-id=CMS1;route-type=ROUTE-ID;route-id=CMS1;call-type=local;

add destination dest-id=CMS2;route-type=ROUTE-ID;route-id=CMS2;call-type=local;

add destination dest-id=CMS3;route-type=ROUTE-ID;route-id=CMS3;call-type=local;

add dial-plan id=cdpp;digit-string=972-233;dest-id=CMS1;

add dial-plan id=cdpp;digit-string=469-255;dest-id=CMS2;

add dial-plan id=cdpp;digit-string=214-265;dest-id=CMS3;

add ca-config;cluster-dial-plan id=cdpp;

On CMS1:

add route id=CMS4;tgn1_id=sip_1_4;

add destination dest-id=CMS4;route-type=ROUTE-ID;route-id=CMS4;call-type=local;

add dial-plan id=cdpp;digit-string=972-682;dest-id=CMS4;

On CMS2:

add route id=CMS4;tgn1_id=sip_2_4;

add destination dest-id=CMS4;route-type=ROUTE-ID;route-id=CMS4;call-type=local;

add dial-plan id=cdpp;digit-string=972-682;dest-id=CMS4;

On CMS3:

add route id=CMS4;tgn1_id=sip_3_4;

add destination dest-id=CMS4;route-type=ROUTE-ID;route-id=CMS4;call-type=local;

add dial-plan id=cdpp;digit-string=972-682;dest-id=CMS4;

Call Types

This section provides detailed information on CLI usage for the Cisco BTS 10200 call types. CLI information on the following call types is provided:

•Ported-In Call Processing

For additional information on call types, refer to Appendix A, "Call Types and Subtypes."

1+ InterLATA Call

This section describes the Cisco BTS 10200 routing and call flow for 1+ interLATA calls and provides some CLI examples. For information on the CLI, refer to the Cisco BTS 10200 Softswitch CLI Database. Refer to Figure 6-7 for visual representation of the 1+ interLATA call routing flow and review the following detailed 1+ interLATA call routing flow.

Step 1 A 1+ interLATA call is received.

Examples:

Subsciber and Sub-Profile

Dp50 Digit-String=202

Step 2 Determine if a 101XXXX number has been dialed. If a 101XXXX number has been dialed, the Cisco BTS 10200 selects the call route and routes the call based on the carrier access code (CAC). If a 101XXXX number has not been dialed, proceed to Step 3.

Step 3 Check the subscriber table to determine if a PIC is defined. If a PIC is defined, the Cisco BTS 10200 selects the call route and routes the call based on the PIC information. If a PIC is not defined, proceed to Step 4.

Example:

Step 4 Check the point of presence (POP) table. If a block-eawopic is configured, the Cisco BTS 10200 blocks the call. If a block-eawopic is not configured, proceed to Step 5.

Examples:

POP 50 No Block

POP 50 Block

Step 5 Determine if a local exchange carrier operations support system (LECOSS) is defined in the POP table. If a LECOSS is defined in the POP table, the Cisco BTS 10200 selects to route the call through use of the LECOSS. If a LECOSS is not defined in the POP table, the Cisco BTS 10200 blocks the call.

Examples:

POP 50 No Block

Figure 6-7 1+ InterLATA Call

1+ IntraLATA Call

This section provides a detailed description of the Cisco BTS 10200 routing and call flow for 1+ intraLATA calls and provides some CLI examples. For information on the CLI, refer to the Cisco BTS 10200 Softswitch CLI Database. Refer to Figure 6-8 for visual representation of the 1+ intraLATA call routing flow and review the following detailed 1+ intraLATA call routing flow.

Step 1 An 1+ intraLATA call is received.

Examples:

Sub DP Dest IntraLATA

Step 2 Determine if 101XXXX number has been dialed. If a 101XXXX number has been dialed, proceed to Step 3. If a 101XXXX number has not been dialed, proceed to Step 4.

Step 3 Check the Carrier table for a CAC. If a CAC is available, the Cisco BTS 10200 selects the call route and route the call based on the CAC. If a CAC is not available, proceed to Step 3a.

Example:

Carrier Intra=Y

Determine if a LECOSS is defined in the POP table. If a LECOSS is defined in the POP table, the Cisco BTS 10200 selects the call route and routes the call through use of the LECOSS. If a LECOSS is not defined in the POP table, the Cisco BTS 10200 blocks the call.

Step 4 Check the POP table for a configured IP transfer point (ITP). If an ITP is configured, proceed to Step 4a. If an ITP is not configured, the Cisco BTS 10200 routes the call through use of the dial plan routing.

Example:

POP ITP=Y

a. Check the subscriber table for a specified PIC. If a PIC is specified, proceed to Step 4b. If a PIC is not specified, the Cisco BTS 10200 routes the call to the announcement server and checks the POP table for a specified PIC. If a PIC is not specified, the Cisco BTS 10200 blocks the call or if a dial plan is available, the Cisco BTS 10200 selects the call route and routes the call according to the dial plan routing information.

Examples:

Sub DP Dest IntraLATA

b. Check the intra-carrier table for a specified PIC. If a PIC is specified in the intra-carrier table, the Cisco BTS 10200 selects the call route and routes the call based on the PIC information. If a PIC is not specified in the intra-carrier table, proceed to Step 4c.

Example:

Carrier Intra=Y

c. Determine if a LECOSS is defined in the POP table. If a LECOSS is defined in the POP table, the Cisco BTS 10200 selects the call route and routes the call through the LECOSS. If a LECOSS is not defined in the POP table, the Cisco BTS 10200 blocks the call.

Example:

Figure 6-8 1+ IntraLATA Call

0+ InterLATA Call

This section describes the Cisco BTS 10200 routing and call flow for 0+ interLATA calls and provides CLI examples. For detailed information on the CLI, refer to the Cisco BTS 10200 Softswitch CLI Database. Refer to Figure 6-9 for visual representation of the 0+ interLATA call routing flow and review the following detailed 0+ interLATA call routing flow.

Step 1 A 0+ interLATA call is received.

Examples:

Sub DP Dest InterLATA

Step 2 Determine if a 101XXXX number has been dialed. If a 101XXXX number has been dialed proceed to Step 3. If a 101XXXX number has not been dialed, proceed to Step 5.

Step 3 Check the Carrier table for a CAC. If a CAC is available, the Cisco BTS 10200 selects the call route and routes the call based on the CAC. If a CAC is not available, proceed to Step 4.

Example:

Carrier Op-Serv=Y

Step 4 Check the POP table for a defined LECOSS. If a LECOSS is defined in the POP table, the Cisco BTS 10200 routes the call through the LECOSS. If a LECOSS is not defined in the POP table, the Cisco BTS 10200 blocks the call.

Example:

Step 5 Check the subscriber table for a defined PIC. If a PIC is defined in the subscriber table, proceed to Step 6. If a PIC is not defined in the subscriber table, proceed to Step 7.

Example:

Step 6 Check the subscriber profile for an ea-use-pic entry. If the subscriber profile contains an ea-use-pic entry, the Cisco BTS 10200 selects the call route and routes the call based on the PIC information. If the subscriber profile does not contain an ea-use-pic entry, return to Step 4.

Examples:

Ea-Use=Y

POP Ea-use=N

Step 7 Check the POP table for a block-eawopic entry. If the POP table contains a block-eawopic entry, the Cisco BTS 10200 blocks the call. If the POP table does not contain a block-eawopic entry, return to Step 4.

Examples:

POP Block-ea=N

POP Block-ea=Y

Figure 6-9 0+ InterLATA Call

0+ IntraLATA Call

This section describes the Cisco BTS 10200 routing and call flow for 0+ intraLATA calls and provides CLI examples. For information about the CLI, refer to the Cisco BTS 10200 Softswitch CLI Database. Refer to Figure 6-10 for visual representation of the 0+ intraLATA call routing flow and review the following detailed 0+ intraLATA call routing flow.

Step 1 A 0+ intraLATA call is received.

Examples:

Sub DP Dest IntraLATA

Step 2 Determine if a 101XXXX number was dialed. If a 101XXXX number was dialed, proceed to Step 3. If a 101XXXX number was not dialed, proceed to Step 5.

Step 3 Check the Carrier table for a CAC. If a CAC is available, the Cisco BTS 10200 selects the call route and routes the call based on the CAC. If a CAC is not available, proceed to Step 4.

Example:

Carrier Op-Serv=Y

Example:

Step 5 Check the POP table for a configured ITP. If an ITP is configured, proceed to Step 6. If an ITP is not configured return to Step 4.

Example:

POP ITP=Y

Step 6 Check the subscriber table for a specified PIC. If a PIC is specified, proceed to Step 7. If a PIC is not specified, the Cisco BTS 10200 routes the call to the announcement server. Additionally, if a PIC is not specified in the subscriber table, the Cisco BTS 10200 checks the POP table for a specified PIC. If a PIC is specified in the POP table, the Cisco BTS 10200 blocks the call. If a PIC is not specified in the POP table, return to Step 4.

Examples: