provisioning dial plans with the cisco vspt cisco mgc software release 9.5(1) chapter 3...

Cisco MGC Software Release 9.5(1)

C H A P T E R 3
Provisioning Dial Plans with the Cisco VSPT
Revised: January 20, 2011, Cisco MGC Software Release 9.5(1)

This chapter shows you how to use the Cisco Voice Services Provisioning Tool (VSPT) to provision a dial plan on the Cisco PGW 2200 Softswitch. This chapter contains the following sections:

• Provisioning Dial Plans, page 3-1

• Performing an Integrity Check, page 3-46

• Provisioning Examples, page 3-47

When provisioning dial plans, you must first ensure that all system components have been provisioned as described in the Cisco PGW 2200 Softswitch Release 9.8 Provisioning Guide.

Tip Before you begin provisioning your dial plan, you should have a list of the trunks that are available, including their names, properties, and other parameters. This list should already have been created in Chapter 2, “Preparing for Dial Plan Provisioning.” You should review this list before you begin provisioning your dial plan and keep it available to refer to for information.

Provisioning Dial PlansThe Cisco VSPT provides a graphical user interface (GUI) that allows you to provision dial plans and then deploy them to the Cisco PGW 2200 Softswitch. The Cisco VSPT

• Lets you create dial plan files across multiple Cisco PGW 2200 Softswitches.

• Helps you avoid common errors when provisioning dial plans.

• Eliminates having to repeatedly enter duplicate dial plan data.

• Allows you to import and export dial plans to and from the Cisco PGW 2200 Softswitch.

• Lets you perform an integrity check prior to deployment, to prevent possible errors.

• Creates the Man-Machine Language (MML) files and the trunk group, bearer channel, and dial plan files used to provision the Cisco PGW 2200 Softswitch.

After you finish a provisioning session and click File, Save, then As Working, the Cisco VSPT saves your dial plan as the active or working dial plan.

Note After you have deployed the active dial plan, you cannot modify it. To change an active dial plan, you must save it using a different name, start a new provisioning session to edit it, then redeploy it.

3-1<<Marketing-Approved Feature Name>>

http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/9.8/Provisioning/Guide/prvgde98.html

http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/9.8/Dial_Plan/Guide/DP_Dial.html

Chapter 3 Provisioning Dial Plans with the Cisco VSPTProvisioning Dial Plans

The following sections provide examples of the Cisco VSPT screens you use in creating a dial plan:

• Importing a Dial Plan File, page 3-2

• Adding a Dial Plan, page 3-4

• Adding Dial Plan Details, page 3-5

You don’t have to add all the components in your dial plan. Your dial plan configuration depends on your needs in an actual network.

Importing a Dial Plan FileYou can enter MML commands for a dial plan in a text file and then import the text file.

Caution Consider importing a dial plan text file for initial provisioning only. When you import a dial plan file, all existing dial plan data is replaced by the dial plan data in the file you import.

Note Before migrating a dial plan created with Cisco PGW 2200 Softswitch software release 9.7(3) to release 9.8(1), first install the base version of release 9.8(1). Then, before starting the software, install release 9.8(1) patch S7P7 or later.

To import a dial plan text file, complete the following steps:

Step 1 From the File menu, click Import.

You see a screen similar to the one in Figure 3-1.

Figure 3-1 Importing Dial Plan Files

Step 2 Click From File, then on the File type pull-down menu choose Dialplan File.




Step 3 Enter the name of the dial plan file that you want to import in the File name data entry box.

If you do not know the name of the file, click Select to specify the file to import.

Step 4 Locate the file you want to import, select it, and click Open.




Step 5 Click OK.

The dial plan file you indicated is imported.

Adding a Dial PlanIf you do not choose to import a dial plan, you can create one by completing the following steps:

Step 1 From the main provisioning screen of the Cisco VSPT, click the Number Analysis radio button on the left side of the screen.


Figure 3-2 Adding a Dial Plan

Step 2 Enter a customer group ID, which is a unique four-character alphanumeric identifier for your dial plan.

Step 3 Click Add.

The customer group ID you added appears under Number Analysis on the left of the screen.




Adding Dial Plan DetailsA dial plan includes results, triggers, and shared global items. Results and triggers are associated with each dial plan which is identified by a customer group ID. Global items are shared by all the dial plans in the current configuration.

You can provision the results under the Results hierarchical menu, and the triggers under the Triggers hierarchical menu for each dial plan. For global items, you can provision them under the Global Items hierarchical menu.

You add details to your dial plan by specifying information in the following tables:

Results

• Adding Digit Modification String Data, page 3-6

• Adding Bearer Capability (BC) Data, page 3-8

• Adding High Layer Capability (HLC) Data, page 3-9

• Adding a Customer VPN ID, page 3-10

• Adding Domain Modification String Data, page 3-10

• Adding a Result Set, page 3-11

• Adding or Modifying a Default Result Set, page 3-13

• Adding Screening Data, page 3-15

• Adding Service Data, page 3-16

• Adding Source Black Data, page 3-17

• Adding a Domain Routing Policy (DRP) Table, page 3-18

• Adding Route Selection Data, page 3-18

• Adding Destination Translation Data, page 3-19

Triggers

• Adding A-number Charge Origin Data, page 3-20

• Adding A-Digit Tree Data, page 3-21

• Adding A-number Dial Plan Selection, page 3-22

• Adding B-Digit Tree Data, page 3-23

• Adding Cause Data, page 3-25

• Adding Calling Line Identification Prefix, page 3-27

• Adding CLI IP Address, page 3-28

• Adding Calling Party Category, page 3-29

• Adding Dial Plan Selection Data, page 3-30

• Adding H.323 ID, page 3-30

• Adding Location Data, page 3-31

• Adding Nature of Address (NOA) Data of A-number and B-number, page 3-32

• Adding Numbering Plan Indicator (NPI) Data of A-number and B-number, page 3-33

• Adding Route Holiday, page 3-34




• Adding Transmission Medium Requirement (TMR) Data, page 3-35

• Adding Transit Network Selection (TNS) Information, page 3-36

Global Items

• Adding Announcements, page 3-37

• Adding Ported Number Table Data, page 3-39

• Adding Script, page 3-41

• Adding Full Number Translation Data, page 3-42

• Adding Term Table Data, page 3-43

• Adding Test Line Data, page 3-45

Adding Digit Modification String Data

The digit modification string is used to modify numbers in either the A-number (calling party number) or the B-number (called party number).

If you need to perform digit modifications, you must add the digit modification table where you define a digit modification string to apply to an A-number or a B-number.

For example, if you want to insert the string 86 before the A-number, define a digit modification string 86 with the name DigMod1.

For more information on digit modification strings, see Chapter 1, “Dial Plan and Routing.”

To add a digit modification string, complete the following steps:

Step 1 From the main provisioning screen of the Cisco VSPT, choose the Number Analysis radio button on the left side of the screen.

Step 2 To expand the Number Analysis hierarchical menu, click the icon to the left of the appropriate customer group ID.

Step 3 Click Digmodstring in the Results hierarchical menu.





Figure 3-3 Adding a Digit Modification String

Step 4 Click the Add button at the bottom of the screen.


Figure 3-4 Defining a Digit Modification String

Step 5 Enter the digit modification name and the digit modification string. Then Click OK.

You return to the screen in Figure 3-3, which displays the digit modification string you added.

Step 6 Repeat Steps 1 to 3 until all of the necessary digit modification strings have been added.




Adding Bearer Capability (BC) Data

When you change the BC information elements (IEs) in the outgoing Initial Address Message (IAM), an ISUP call from the PSTN can be translated to a fax call in the Global System for Mobile Communications (GSM) network based on the dialed called party number. You need to create the BC table and add a BCMOD result to change the BC IEs in the outgoing IAM.

To add a BC table entry, complete the following steps:


Step 2 To expand the Number Analysis hierarchical menu, click the icon to the left of the appropriate customer group ID. Then click BC.


Figure 3-5 Adding a BC Table Entry






Figure 3-6 Adding a BC Table Entry Name

Step 4 Enter a name for this BC table entry in the Name field.

Step 5 Choose a BC coding option from the BC Name drop-down list.

The drop-down list gives all the available BC coding options which indicate the bearer channel characteristics as being either fax or data and a baud rate.

Step 6 Click OK.

Adding High Layer Capability (HLC) Data

When you change the HLC IE in the outgoing IAM, the Cisco PGW 2200 Softswitch translates an ISUP call from the PSTN to a data call in the GSM network. You need to create the HLC table and add the HLCMOD result to change the HLC IEs in the outgoing IAM.

To add an HLC table entry, complete the following steps:


Step 2 To expand the Number Analysis hierarchical menu, click the icon to the left of the appropriate customer group ID, then click HLC.



Figure 3-7 Adding a HLC Entry Name




Step 4 Enter a name for this HLC table entry in the Name field.

Step 5 Choose an HLC coding option from the HLC Name drop-down list.

The drop-down list gives all the available HLC coding options which indicate the high layer compatibility characteristics as being either fax or data and a baud rate.

Step 6 Click OK.

Adding a Customer VPN ID

The customer VPN ID overwrites the configured VPN ID in the incoming trunk groups or sigPaths.

To add a customer VPN ID, complete the following steps:


Step 2 To expand the Number Analysis hierarchical menu, click the icon to the left of the appropriate customer group ID. Then click Customervpnid.



Figure 3-8 Defining a Customer VPN ID

Step 4 Enter the customer VPN ID in the Name field.

Step 5 Click OK.

Adding Domain Modification String Data

The domain modification string table defines the string modifications on the domain names.

To add a domain modification string, complete the following steps:


Step 2 To expand the Number Analysis hierarchical menu, click the icon to the left of the appropriate customer group ID. Then click Dmnmodstring.






Figure 3-9 Defining a Domain Modification String

Step 4 Enter the source modification name in the Domain Name field.

Step 5 Enter the domain name to be modified (for example, cisco.com) in the Domain String field.

Step 6 Click OK.

Step 7 Repeat Steps 2 through 5 until all of the necessary domain modification strings have been added.

Adding a Result Set

The result of analysis might require that an action be taken. For example, the last number in each digit string might not have a node number associated with it. When there is no next node associated with the last number in a digit string, an action must be taken and a result set defines that action. Different types of result tables are valid for the triggers, for example, Adigtree, Bdigtree, NOA, NPI, Cause, and Location tables.

For more information on result tables, see Chapter 1, “Dial Plan and Routing.”

To add a result set, complete the following steps:


Step 2 To expand the Number Analysis hierarchical menu, click the icon to the left of the appropriate customer group ID. Then click Resultset.





Figure 3-10 Adding a Result Set

Step 3 Click the Add button near the center of the screen.


Figure 3-11 Result Set Name

Step 4 Enter the result set name.

Step 5 Click OK.

You return to the screen in Figure 3-10, which displays the name of the result set you just added.

Step 6 Highlight the result set you just added. Then click the Add button at the bottom of the screen.




Step 7 From the Result Type drop-down list, choose the desired result type.

A result type indicates a certain action you want the Cisco PGW 2200 Softswitch to perform. For example, the result type BMODDIG indicates the B-number modification. You need to provide additional information for the chosen result type as described in Step 8.

Step 8 Enter the required information.

In this example, enter the result name. Then choose the route list from the Route list name drop-down list.

Figure 3-12 shows the definition of a ROUTE result for the result set testResultset.

Figure 3-12 Defining a Result Set

For more information on result tables, see Chapter 1, “Dial Plan and Routing.”

Step 9 Click OK.

You see the screen in Figure 3-10, which displays the result type you just defined.

Step 10 Repeat Steps 5 through 8 to add another result type to the result set.

Repeat Steps 1 through 8 to provision another result set.

Note If you define more than one result for a result set, you can select a result then use the arrow buttons on the right to rearrange the order of the results. See Figure 3-10.

Adding or Modifying a Default Result Set

The default result set allows you to configure an action to occur if no result sets have been associated with the call.




Only one default result set is allowed for each customer group ID. Creating a new default result type overwrites the previous default result type. Only one of the following result types is allowed for the default result set at any time:

• BLACKLIST—Analysis of the B-number reveals that it is on the black list and the call is released.

• ROUTE—Analysis of the B-number reveals that the call is to be routed elsewhere.

• CAUSE—Analysis of the B-number reveals that the call is to be released with a specified cause.

To add or modify a default result set, complete the following steps:


Step 2 To expand the Number Analysis hierarchical menu, click the icon to the left of the appropriate customer group ID. Then click DefResultSet.


Figure 3-13 Adding a Default Result Set

Step 3 Choose the default result set from the Result Type drop-down list.

Step 4 Complete the settings under the Result Type drop-down list. Then click Modify.

These settings vary depending on your choice in Step 2.




Adding Screening Data

Call screening is a type of analysis done on the digit string to determine whether the call is accepted or rejected. There are four tables for the call screening.

• A-number Whitelist

• A-number Blacklist

• B-number Whitelist

• B-number Blacklist

Note The Screening component is moved to Tools > Advanced Number Editor on the menu bar in Cisco VSPT Release 2.8(1).

To add call screening data, complete the following steps:

Step 1 Choose Tools > Advanced Number Editor from the menu bar.


Figure 3-14 Adding Screening Data

Step 2 Click the tab of the desired file type (AWhite, ABlack, BWhite, or BBlack).

Step 3 If you are editing an exiting screening file, choose File > Open to select an existing file from a pop-up menu and click Open.

Step 4 Choose Edit > Add new item to add new screening data.




Figure 3-15 Add New Numbers Window

Step 5 Enter the customer group ID of the dial plan that you want to add new numbers to in the Dialplan field.

Step 6 Enter the screening numbers in Screening numbers field.

Step 7 Choose the action you want to perform on this entry.

• Add—Add this entry to the list

• DLT—Remove this entry from the list

Note You can add, modify, and remove a selected screening entry using options in the Edit menu.

Step 8 Click OK.

Step 9 Choose File > Save this panel to save the screening file.

Step 10 Choose a deployment option in the Command menu to deploy the screening file.

• Send selected—Deploy the selected numbers.

• Send items in this panel—Deploy the screening data in this tab.

• Send items in all panels—Deploy the screening data in all the tabs.

• Rtrv all from VSC—Retrieve screening numbers from the Cisco PGW 2200 Softswitch and replace all current numbers.

Adding Service Data

The service names in the Service table are defined by the user to indicate services for screening that are available to the users. You must define a service before you add a B-number-triggered call screening.

To add service data, complete the following steps:


Step 2 To expand the Number Analysis hierarchical menu, click the icon to the left of the appropriate customer group ID. Then click Service.

Step 3 Click Add.





Figure 3-16 Defining Service Data

Step 4 Enter the Service name and click OK.

Adding Source Black Data

The Source Blacklist Screening table allows you to screen calls based on their source domain names.

To add source black data, complete the following steps:


Step 2 To expand the Number Analysis hierarchical menu, click the icon to the left of the appropriate customer group ID. Then click SourceBlack.

Step 3 Click Add.


Figure 3-17 Defining Source Black Data

Step 4 Enter the domain name to be screened (such as example.com) in the Domain String field.

Step 5 From the Service Name drop-down list, choose a service.

Step 6 Click OK.




Adding a Domain Routing Policy (DRP) Table

The DRP table allows you to configure the Cisco PGW 2200 Softswitch to analyze calls based on user and domain names rather than E.164 numbers. The DRP table is a sequential list of up to six steps, each of which contain the name of a result set. You can define the result sets that the Cisco PGW 2200 Softswitch executes at a given step in the DRP table according to your need.

To add a DRP table, complete the following steps:


Step 2 To expand the Number Analysis hierarchical menu, click the icon to the left of the appropriate customer group ID. Then click DRPTable.

Step 3 Click Add.


Figure 3-18 Defining DRP Table

Step 4 Enter the step number (1 through 6) in the DRP table.

Step 5 From the Result Set drop-down list, choose a result set.

The Cisco PGW 2200 Softswitch runs the specific result set at a given step in the DRP table.

Step 6 Click OK.

Adding Route Selection Data

The route selection table allows the Cisco PGW 2200 Softswitch to route calls based on the source and destination domain names.

To add route selection data, complete the following steps:


Step 2 To expand the Number Analysis hierarchical menu, click the icon to the left of the appropriate customer group ID. Then click RouteSel.

Step 3 Click Add.





Figure 3-19 Defining Route Selection Data

Step 4 Enter the destination username (such as [email protected]) or domain name (such as cisco.com) in the Destination Domain String field.

Step 5 Enter the source username (such as [email protected]) or domain name (such as example.com) in the Source Domain String field.


Step 7 From the Route List Name drop-down list, choose a route list.

Step 8 Click OK.

Adding Destination Translation Data

The destination username/domain translation table translates the non-E.164 destinations to E.164 destinations (domains to phone numbers).

To add destination translation data, complete the following steps:


Step 2 To expand the Number Analysis hierarchical menu, click the icon to the left of the appropriate customer group ID. Then click DestTrans.

Step 3 Click Add.





Figure 3-20 Defining Destination Translation Data

Step 4 Enter the username or domain name to be translated in the Destination Domain String field.


Step 6 Enter the display name for the user in the Display Name field.

Step 7 Enter the new user name in the User Name field.

Step 8 Enter the new domain name in the Domain Name field.

Step 9 Enter the URI parameters that the Cisco PGW 2200 Softswitch adds to the header in the URI Parameters field.

Note The URI parameters value must start with a semicolon, such as ;USER=phone.

Step 10 Click OK.

Adding A-number Charge Origin Data

The Cisco PGW 2200 Softswitch returns a result with CHARGEORIGIN result type during the A-number analysis if the Advice of Charge (AOC) feature is enabled on the ingress trunk group or sigpath. You need to add A-number charge origin data before you add a result with CHARGEORIGIN result type.

To add A-number charge origin data, complete the following steps:


Step 2 To expand the Number Analysis hierarchical menu, click the icon to the left of the appropriate customer group ID. Click Triggers. Then click Achgorigin.

Step 3 Click Add.





Figure 3-21 A-number Charge Origin Data Window

Step 4 Enter the calling line identity (CLI) in the CLI String field.

The valid value for this field is a digit string (from 1 to 20 digits), A to F allowed if the dial plan supports overdecadic.

Note The CLI String value is a per call configuration. If there is no match between the provisioned CLI value and the incoming CLI value, the Cisco PGW 2200 Softswitch cannot activate the requested AOC supplementary service.

Step 5 Enter the call origin value in the Corigin field.

The valid value for this field is an integer in the range from 1 to 9999.

Step 6 Click OK to add the new value.

Adding A-Digit Tree Data

The Adigtree table is the analysis table for calling numbers (A-numbers). You add data to it by defining an entry for each digit in the digit string. The output of this table is an index that points to the result table or an indication that analysis is complete. For more information on creating the Adigtree table, see Chapter 1, “Dial Plan and Routing.”

To add Adigtree data, complete the following steps:


Step 2 To expand the Number Analysis hierarchical menu, click the icon to the left of the appropriate customer group ID. Click Triggers. Then click Adigtree.

Step 3 Click Add.





Figure 3-22 Specifying Adigtree Data

Step 4 Enter all the digits or part of the digits in a calling number in the Digit String field.


Note If the calling number of an incoming call begins with this digit string, the Cisco PGW 2200 Softswitch performs the actions defined in the result set you chose in Step 4.

Step 5 From the Call side drop-down list, choose originating.

Step 6 From the Result set drop-down list, choose the result set.

Step 7 Click OK.

Adding A-number Dial Plan Selection

The dial plan selection table provides the functionality to select a new dial plan based on the customer group ID and the full A-number.

To add A-number dial plan selection data, complete the following steps:


Step 2 To expand the Number Analysis hierarchical menu, click the icon to the left of the appropriate customer group ID. Click Triggers. Then click A Num DpSelection.

Step 3 Click Add.





Figure 3-23 Specifying A-number Dial Plan Selection

Step 4 Enter the calling line identification value (the full A-number) in the CLI String field.

The valid value for the this field is a digit string (from 1 to 20 digits), A to F allowed if the dial plan supports overdecadic.

Step 5 Choose one dial plan name from the DialPlan Name drop-down list.

This value specifies the new dial plan that you want to divert to.


Adding B-Digit Tree Data

The Bdigtree table is the analysis table for called numbers. You add data to it by defining an entry for each digit in the digit string. The output of this table is an index that points to the result table or an indication that the analysis is complete. For information on creating the Bdigtree table, see Chapter 1, “Dial Plan and Routing.”

To add Bdigtree data, complete the following steps:


Step 2 To expand the Number Analysis hierarchical menu, click the icon to the left of the appropriate customer group ID. Click Triggers and then click Bdigtree.





Figure 3-24 Adding Bdigtree Data

Step 3 Click Add.


Figure 3-25 Specifying Bdigtree Data

Step 4 Enter all the digits in a calling number in the Digit String field.





Note The digit string you enter can be either a part of the B-number or the full B-number. If the called number (B-number) of an incoming call begins with this digit string, the Cisco PGW 2200 Softswitch performs the actions defined in the result set you chose in Step 6.

Step 5 From the Call side drop-down list, choose originating.

Step 6 From the Result set drop-down list, choose the result set. Click OK.

You return to the screen in Figure 3-24, with the Bdigtree added.

Adding Cause Data

Cause Analysis is performed when a release message is received, or when a failure of some kind (for example, number screen fail) has occurred that implies the call must be released. The Cause Code value or the combined Cause Code and/or Location Code values are used to provide an internal Cause Code that provokes a number of different results including re-routing of the call to another route, or return to analysis to find a different destination.

The Cause table lists the cause codes generated when a call is either rejected or cleared by the system. The cause for release can be from either a result type (from either B-number analysis or cause analysis) or a failure (generated during call processing).

The Cause table contains either a location index or a result set index. The location index is used to identify the analysis into the location block. If the location index is set to 0, no analysis is performed based on the location. The result set index in the cause table is used to associate a result set. If the result set index is set to 0, then no action is to be taken at this time. It is only possible to have a location index or a result set index configured on the cause table, not both. However, if both the location index and the result set index are set to 0, no analysis is performed.

For more information on creating the Cause table, see Chapter 1, “Dial Plan and Routing.”

To add Cause data, complete the following steps:


Step 2 To expand the Number Analysis hierarchical menu, click the icon to the left of the appropriate customer group ID. Click Triggers. Then click Cause.





Figure 3-26 Adding Cause Data

Step 3 Click Add.


Figure 3-27 Specifying Cause Data

Step 4 Enter the cause value in the Cause value field.

Cause values are a subject of standardization. The valid value for this field is a integer in the range of 0 to 300. The value 0 indicates the wildcard value.

Step 5 Do one of the following:

• In the Location block drop-down list, choose the location block.

• In the Result set drop-down list, choose the result set.




Step 6 Click OK.

You return to the screen in Figure 3-27, with the cause data added.

Adding Calling Line Identification Prefix

Advanced screening on the Cisco PGW 2200 Softswitch requires the provisioning of the calling line identification prefix table. The CLI prefix parameter allows you to associate a CLI prefix with a specific customer group. If an incoming call matches the CLI prefix parameter, you can apply certain dial plan functions to it.

To add CLI prefix, perform the following steps:


Step 2 To expand the Number Analysis hierarchical menu, click the icon to the left of the appropriate customer group ID. Click Triggers. Then click Cliprefix.

Step 3 Click Add.


Figure 3-28 Specifying CLI Prefix

Step 4 Enter CLI set name in the Cliset Name field.

The valid value for this field is a four-digit string.

Note This CLI set name is used when you are adding advanced screening and modification for H.323 messages coming from different call managers or for source IP address of the call manager. See the “Adding CLI IP Address” section on page 3-28 and the “Adding H.323 ID” section on page 3-30 for more information on the advanced screening and modification provisioning.

Step 5 Enter CLI prefix value in the Cli Prefix String field.





Note A DEFAULT CLI prefix entry must be configured for each CLI set name. If an incoming call matches the CLI prefix parameter you provisioned in Cli Prefix String field, the Cisco PGW 2200 Softswitch selects this dial plan customer group ID for this call.

Step 6 Click OK.

Adding CLI IP Address

The CLI IP address parameter allows you to associate an IP address with a cliset name. If the source IP address of the incoming call message matches the provisioned IP address, the Cisco PGW 2200 Softswitch selects the CLI set. If that incoming call matches an CLI prefix defined in that cliset, the Cisco PGW 2200 Softswitch selects the customer group ID of that CLI prefix entry to continue the number analysis.

To add an CLI IP address to a customer group, perform the following steps:


Step 2 To expand the Number Analysis hierarchical menu, click the icon to the left of the appropriate customer group ID. Click Triggers. Then click CliIpAddr.

Step 3 Click Add.


Figure 3-29 Specifying CLI IP Address

Step 4 Enter the IP address in the IP Addr field.

The valid value for the IP Addr field is a string (host name or IP address with the format x.x.x.x where x is from 0 to 255). The maximum length for this string is 255 alphanumerical letters.

Step 5 Enter the subnet mask in the SubNet Mask field.

The valid value for this field is a digit string (from 7 to 15 digits) in the format of x.x.x.x where x is from 0 to 255.

Step 6 In the Cliset Name drop-down list, choose the desired CLI set.




Note If the source IP of the incoming call message matches the address you provisioned in Step 3 and 4, the Cisco PGW 2200 Softswitch selects an CLI set. If the incoming call matches an CLI prefix defined in that CLI set, the Cisco PGW 2200 Softswitch selects the customer group ID of that CLI prefix entry to continue the number analysis.

Step 7 Click OK.

Adding Calling Party Category

Pre-analysis is the first phase in the Cisco PGW 2200 Softswitch number analysis. CPC analysis is the first stage of the pre-analysis. Users configure a CPC table so that it links CPC values received from the incoming call setup message to a result.

To add a calling party category (CPC) value in the CPC list, complete the following steps:


Step 2 To expand the Number Analysis hierarchical menu, click the icon to the left of the appropriate customer group ID. Click Triggers. Then click CPC.

Step 3 Click Add.


Figure 3-30 Specifying CPC

Step 4 Enter the CPC value in the CPC value field.

The valid value for this field is an integer in the range of 0 to 255. The default value is 0.

Step 5 In the Result set drop-down list, choose a result set.

Step 6 Click OK.




Adding Dial Plan Selection Data

The dial plan selection functionality enables the Cisco PGW 2200 Softswitch to divert from one dial plan to another one under specific conditions. You need to add dial plan selection data before you use this function.

To add dial plan selection data, complete the following steps:


Step 2 To expand the Number Analysis hierarchical menu, click the icon to the left of the appropriate customer group ID. Click Triggers. Then click DpSelection.

Step 3 Click Add.

You see a screen similar to Figure 3-31.

Figure 3-31 Specifying Dial Plan Selection

Step 4 Choose another dial plan in the Dialplan Name drop-down list.

This value indicates the diverted-to dial plan.


Adding H.323 ID

The h323iddivfrom parameter allows you to associate an H.323 ID with a specific customer group. If an incoming call matches the H.323 ID parameter, you can apply certain dial plan functions to it.

To add an H.323 ID to a customer group, perform the following steps:


Step 2 To expand the Number Analysis hierarchical menu, click the icon to the left of the appropriate customer group ID, then click h323iddivfrom.

Step 3 Click Add.

You see a window similar to the one in Figure 3-32.




Figure 3-32 Specifying H323IdDiv

Step 4 Enter H.323 ID in the Name field.

The valid value for this field is an alphanumeric string (1 to 32 letters in length).

Step 5 Choose a CLI set from the Cliset Name drop-down list.

Note If the incoming call matches the H.323 ID parameter you provisioned in Step 3, the Cisco PGW 2200 Softswitch selects an CLI set. If the incoming call matches an CLI prefix defined in that CLI set, the Cisco PGW 2200 Softswitch selects the customer group ID of that CLI prefix entry to continue the number analysis.


Adding Location Data

The Location table is used to identify an associated result set. This table is accessed from the cause table through the location index. The location index is used to refer to a block of 16 entries in the location table. The location value is used as an offset into the location block. An action can be associated with a specific location value by associating a result set with the value in the location block.

For more information on the Location table, see Chapter 1, “Dial Plan and Routing.”

To add Location data, complete the following steps:


Step 2 To expand the Number Analysis hierarchical menu, click the icon to the left of the appropriate customer group ID. Click Triggers. Then click Location.

Step 3 Click Add.





Figure 3-33 Defining Location Data

Step 4 Enter the location block in the Location block field.

The valid value for the location block is an integer.

Step 5 Enter the block value in the Block value field.

The value defines the offset in the location block specified in Step 3. The valid value for this field is an integer in the range of 0 to 15.

Step 6 From the Result set drop-down list, choose the result set. Then click OK.

The result set you chose is associated with the value (defined in Step 4) in the location block (defined in Step 3).

Adding Nature of Address (NOA) Data of A-number and B-number

The NOA table is used to define actions to be taken, based on the incoming NOA. The two fields in the NOA table are the NPI index and the result set index. The NPI index is used to identify the analysis into the unique NPI block. If the NPI index is set to 0, no analysis is performed based on the NPI. The result set index in the NOA table is used to associate a result set. If the result set index is set to 0, then no action is to be taken at this time. It is only possible to have a result set index on the NOA table configured or have an NPI index. However, if both the NPI index and the resultset index are set to 0, no analysis is performed.

The procedures for adding NOA of A-number and B-number are similar. Here is a procedure for adding NOA data of A-number.

For more information on creating the NOA table, see Chapter 1, “Dial Plan and Routing.”

To add NOA data for A-number, complete the following steps:


Step 2 To expand the Number Analysis hierarchical menu, click the icon to the left of the appropriate customer group ID. Click Triggers. Then click Anoa.

Note If you are adding NOA for B-number, click Bnoa.

Step 3 Click Add.





Figure 3-34 Defining NOA Data of A-number

Step 4 Enter the NOA value for A-number in the ANOA Value field.

The valid value for the location block is an integer.

Note If you are adding NOA value for B-number, enter the value in the BNOA Value field.

Step 5 Do one of the following:

• From the ANPI block drop-down list, choose the NPI block for A-number.

Note If you are adding NOA value for B-number, choose the NPI block for B-number from the BNPI drop-down list.

• In the Result set drop-down list, choose the result set.

Step 6 Click OK.

Adding Numbering Plan Indicator (NPI) Data of A-number and B-number

The NPI table is used to identify an associated result set. This table is accessed from the NOA table through the NPI block. The NPI block is used to refer to a block of 16 entries in the NPI table. The NPI value contained in the IAM is used as an offset into the NPI block. An action can be associated with an NPI value by associating a result set with the NPI value.

The procedures for adding NPI data of A-number and B-number are similar. Here is a procedure for adding NPI data of A-number.

For more information on creating the NPI table, see Chapter 1, “Dial Plan and Routing.”

To add NPI data of A-number, complete the following steps:





Step 2 To expand the Number Analysis hierarchical menu, click the icon to the left of the appropriate customer group ID. Click Triggers. Then click Anpi.

Note If you are adding NPI data of B-number, click Bnpi.

Step 3 Click Add.


Figure 3-35 Defining NPI Data of A-number

Step 4 Enter the NPI block for A-number in the ANPI block field.

The value in this field is the value specified in the NPI Block column of the NOA. The valid value for this field is an integer in the range of 1 to 1000.

Note If you are adding the NPI data for B-number, enter the value in the BNPI block field.

Step 5 Enter the block offset value in the Block value field.

The value defines NPI block offset of a certain NPI block which is specified in Step 3.

Step 6 In the Result set drop-down list, choose the result set. Click OK.

The result set you chose is associated with the NPI value of the NPI block.

Adding Route Holiday

The holiday table allows you to select specific days of the year to be routed differently from the actual day of the week that a holiday occurs on.

To add route holiday data, complete the following steps:


Step 2 To expand the Number Analysis hierarchical menu, click the icon to the left of the appropriate customer group ID. Click Triggers. Then click RTE Holiday.

Step 3 Click Add.




You see a screen similar to the one shown in Figure 3-36.

Figure 3-36 Defining Route Holiday Data

Step 4 Enter a holiday date by choosing the month (January through December) from the drop-down list.

Step 5 Enter the year or click the arrows on the right to increase or decrease the value.

Step 6 Choose the day from those displayed.

Step 7 Choose the holiday type from the Holiday Type drop-down list.

Step 8 Click OK to add the new holiday.

Adding Transmission Medium Requirement (TMR) Data

The TMR analysis is the second stage in Pre-analysis that enables analyzing the TMR value in the IAM or Setup message. For example, this would allow the Cisco PGW 2200 Softswitch to set different media gateway bearer capabilities within the network.

In this Pre-analysis stage, the provisioned TMR value is matched by the TMR value received in the IAM or Setup message on the originating side. If there is a match, the Cisco PGW 2200 Softswitch performs the actions defined in the result set you choose.

To add transmission medium requirement data, complete the following steps:


Step 2 To expand the Number Analysis hierarchical menu, click the icon to the left of the appropriate customer group ID. Click Triggers. Then click TMR.

Step 3 Click Add.





Figure 3-37 Defining TMR Data

Step 4 Enter the TMR value in the TMR value field.

The valid value for this field is an integer in the range of 0 to 255.

Note The TMR value you enter here is an internal TMR value. The Cisco PGW 2200 Softswitch maps the external TMR values to the internal TMR values differently for the Q.761, Q.767, and ANSI protocol variants. See Appendix A, “NOA and NPI Codes, CPC and TMR Values” for more information.

Step 5 Choose an result set from the Result set drop-down list.

Step 6 Click OK to add the TMR.

Adding Transit Network Selection (TNS) Information

The TNS analysis is the fourth stage in Pre-analysis that enables analyzing the transit network selection parameter information (or the Carrier Selection parameter information) as received in the incoming message.

In this Pre-analysis stage, the internal TNS value is matched against the provisioned TNS value. The TNS value contains a digit string representing a carrierId. If the string is a match, then the associated result set is processed.

To add transit network selection data, complete the following steps:


Step 2 To expand the Number Analysis hierarchical menu, click the icon to the left of the appropriate customer group ID. Click Triggers. Then click TNS.

Step 3 Click Add.





Figure 3-38 Defining TNS Data

Step 4 Enter the TNS value in the TNS value field.

The valid value for this field is a digit string (from 000 to FFFFFFFF).

Step 5 Choose an result set from the Result set drop-down list.

Note The result set is associated with the TNS value. If there is a match between this TNS value and the TNS value in the incoming message, the Cisco PGW 2200 Softswitch performs the actions defined in the result set you chose.

Step 6 Click OK to add the TNS.

Adding Announcements

The ToneAndAnnouncement database table contains all the announcement details. An announcement ID identifies the announcement.

To add an announcement, perform the following steps:

Step 1 From the main provisioning screen of the Cisco VSPT, click the Number Analysis button on the left side of the screen.

Step 2 Expand the Number Analysis menu by click the icon before it. Click Global Items. Then click Announcement.





Figure 3-39 Adding Announcement Table

Step 3 Click Add.


Figure 3-40 Specifying the Announcement

Step 4 Enter the announcement ID in the Announcement Id field.

This parameter indicates the announcement identity, which is an access key for which the announcement table is searched for a match. The valid value for this field is an integer.




Step 5 Choose the gateway type from the Gateway type drop-down list.

This parameter identifies the gateway type for this side of the call.

Step 6 Enter the intended duration (measured in seconds) in the Play Duration field.

This parameter indicates the intended duration for which the announcement or tone is played. The valid value for this field is an integer in the range of 0 to 120. The default value is 60.

Step 7 Enter the intended number of times to play the announcement in the Repeat field.

This parameter indicates the number of times the announcement or tone is repeated; or indicates if it must be played continuously for the specified duration. A value of 0 indicates continuous playing. The valid value for this field is an integer in the range of 0 to 5. The default value is 1.

Step 8 Enter the intended silence interval (measured in milliseconds) in the Interval field.

This parameter indicates the silence interval duration between re-playing an announcement or tone. The valid value for this field is an integer in the range of 0 to 5000. The default value is 3000.

Step 9 Enter the location string in the Location String field.

Step 10 This location string indicates to the gateway the audio file to be loaded for announcement playing. The string format varies according to the gateway type and its configuration. The string information is part of a URL string that the Cisco PGW 2200 Softswitch sends by MGCP to the gateway. The maximum length of string is 128-characters.

Adding Ported Number Table Data

The ported number table determines if the B-number has been ported to another network.

Note The ported number table component is moved to Tools > Advanced Number Editor on the menu bar in Cisco VSPT Release 2.8(1).

To add data in the ported number table, complete the following steps:


Step 2 Click the Porttbl tab.





Figure 3-41 Ported Number Table

Note When the Cisco VSPT imports a configuration from the Cisco PGW 2200 Softswitch, it does not automatically load the ported database. Sometimes the ported database could be very large, and the Cisco VSPT might run out of memory when loading the whole database. You can choose Command > Rtrv all from VSC from the menu bar to import all these tables to the Cisco VSPT.

Step 3 Choose Edit > Add new item.


Figure 3-42 Defining Ported Number

Step 4 Enter a called number value in the Called number field.




The valid value for this field is a digit string (from 1 to 20), A to F allowed if the dial plan supports overdecadic. This digit string is the B-number digits (can be post normalization or modification).

Step 5 Enter a routing number in the Routing number field.

The valid value for this field is a digit string (from 1 to 20), A to F allowed if the dial plan supports overdecadic. This digit string is the Routing number prefix for ported numbers.

Step 6 Enter the minimum and maximum length for call origination from this traffic path.

The valid value for these two fields is an integer in the range of 0 to 20.

Note The minimum length and maximum length values being created here relate to the B-Number post database reading. They do not relate to the incoming digits received from line.

Step 7 Choose Add or DLT from the Add/Remove drop-down list.


Adding Script

To support the MGCP scripting feature on Cisco PGW 2200 Softswitch, you need to provision a script table.

To add the script data in the script table, complete the following steps:


Step 2 Expand the Number Analysis menu by click the icon before it. Click Global Items, then Script.

Step 3 Click Add.


Figure 3-43 Defining the Script

Step 4 Enter the script identification in the Script ID field.

This integer corresponds to the ID referenced in dw1 for the SCRIPT result type.




Step 5 From the GW Type drop-down list, choose the gateway type.

Note The Script ID and the GW Type fields are the keys to the script table.

Step 6 From the Script Type drop-down list, choose the script type to be invoked and is used as the language type in the signal request parameter S: for the script invocation. (For example, S:script/tcl or S:script/java, is based on this definition.)

Step 7 Enter the location of the script in the Script Location field.

The valid value for this field is a string no longer than 128 alphanumeric characters.

Step 8 (Optional) Enter the script parameters in the Script Parameters field.

The information provided in this string is used as is in the script invocation command to the gateway. The string format and the information provided here conform to the specific gateway script requirements. This field is limited to 128 alphanumeric characters.

Adding Full Number Translation Data

The full number translation table is used for the result type NUM_TRANS. The NUM_TRANS result type is returned from A-number (the calling number) or B-number analysis (the called number) indicating that one or more numbers encountered require full replacement. The full number translation table contains all the replacement information.

To add full number translation, complete the following steps:


Step 2 Expand the Number Analysis menu by click the icon before it. Click Global Items. Then click FullNumberTrans.

Step 3 Click Add.


Figure 3-44 Defining the Full Number Translation




Step 4 Enter the service name in the Service Name field.

The value is a string representing the previously provisioned service name in the Service table.

Step 5 Enter an integer (1 through 4) indicating the number type to be translated in the Num Type field.

• 1—called party number

• 2—calling party number

• 3—redirecting number

• 4—calling party number and redirecting number

Step 6 Enter the digit string that is to be translated in the Dig String field. Maximum length of integers: 20 digits.

Step 7 Enter the translated digit string in the Translated Num field. Maximum length of integers: 20 digits.

Step 8 Click OK.

Adding Term Table Data

The TERMTBL list contains B-numbers. If the presented B-number is found in this list, the call is routed to the RouteID associated with the corresponding digit string.

Note The term table component is moved to Tools > Advanced Number Editor on the menu bar in Cisco VSPT Release 2.8(1).

To add term table data, complete the following steps:


Step 2 Click the Termtbl tab.





Figure 3-45 Term Number Table

Note When the Cisco VSPT imports a configuration from the Cisco PGW 2200 Softswitch, it does not automatically load the term table database. Sometimes the database could be very large, and the Cisco VSPT might run out of memory when loading the whole database. You can choose Command > Rtrv all from VSC from the menu bar to import all these tables to the Cisco VSPT.

Step 3 Choose Edit > Add new item from the menu bar.


Figure 3-46 Defining Term Table Data

Step 4 Enter a called number value, then choose a route list name.

The RouteID is associated with the called number you entered.

Step 5 Choose Add or DLT from the ADD/Remove drop-down list.





Adding Test Line Data

The test line table is used to specify the delay, loop requirement, duration, and other parameters for test calls.

To add test line data, complete the following steps:

Step 1 From the main provisioning screen of the Cisco VSPT, click the Number Analysis button on the left side of the screen.

Step 2 Expand the Number Analysis menu by click the icon before it. Click Global Items, then click Testline.

Step 3 Click Add.


Figure 3-47 Defining Test Line Data

Step 4 Enter the name in the Test Line Name field for the test call.

This string can be up to 20 alphanumeric characters.

Step 5 Enter the delay value (measured in milliseconds) for the test call.

Step 6 Choose Yes in the loopreqField if you want loop required on. Otherwise, choose No.

Step 7 Enter the first tone type and its duration.

Step 8 Enter the second tone type and its duration.

Note In this example, the test line Test2 is added. First the Cisco PGW 2200 Softswitch delays 300 milliseconds and plays the first tone, old milliwatt (1000Hz), for a duration of 1000 milliseconds. Then it plays the second tone, really new milliwatt (1013.8Hz), for a duration of 2000 milliseconds. The Cisco PGW 2200 Softswitch repeats the whole process until the call is released or it releases the call when the TestLineDuration times out.



Chapter 3 Provisioning Dial Plans with the Cisco VSPTPerforming an Integrity Check

Step 9 Click Add to add the new test line entry.

Performing an Integrity CheckWhen provisioning is complete, you can perform an integrity check to prevent possible configuration errors. The integrity check involves examining the following:

• Integrity of Cisco PGW 2200 Softswitch signaling configuration

• Traffic against Cisco PGW 2200 Softswitch configuration

• Dial plan results

You can run an individual test, any combination of two tests, or all the tests each time. For more information on the integrity check, see Chapter 3 in the Cisco Voice Services Provisioning Tools User Guide, Release 2.8(1).

To perform an integrity check of your dial plan, complete the following steps:

Step 1 From the Tools menu, choose Integrity Check. You see a screen similar to the one in Figure 3-48.

Figure 3-48 Integrity Check

Step 2 Click the Run individual tests radio button and check the Check dialplan results check box.

Step 3 Click Start.

The tests run. When they finish, you see a screen similar to the one in Figure 3-49.



Chapter 3 Provisioning Dial Plans with the Cisco VSPTProvisioning Examples

Figure 3-49 Integrity Check Results

Provisioning ExamplesThis section presents an example showing the typical provision of a dial plan with Cisco VSPT (see Figure 3-50). This dial plan example is for illustration purpose only. The provisioning might vary in an actual network.




Figure 3-50 A Dial Plan Example




Provisioning OutlinePerform the following steps to provision the sample configuration with Cisco VSPT 2.8(1).

Step Action Section and Page

Get Started with Cisco VSPT

Step 1 Start a provisioning session Starting a Provisioning Session, page 3-50

Step 2 Stop and save a configuration Saving the Cisco VSPT Configuration, page 3-51

Import or Add a Dial Plan

Step 1 (Optional) Import a Cisco VSPT dial plan file Importing a Dial Plan File, page 3-2

Step 2 Add a dial plan Adding a Dial Plan, page 3-4

Add Dial Plan Selection

Step 1 Add multiple dial plans Adding Multiple Dial Plans, page 3-52

Step 2 Add the dial plan selection Adding the Dial Plan Selection, page 3-52

Add Call Screening

Step 1 Add call screening triggered by A-number analysis Adding Whitelist Screening Triggered by A-number Analysis, page 3-55

Step 2 Add call screening triggered by B-number analysis Adding Blacklist Screening Triggered by B-number Analysis, page 3-58

Add Digit Modification

Step 1 Add the digit modification in dial plans Adding the Digit Modification in the Dial Plans, page 3-60

Add Routing Analysis

Step 1 Add time of day Routing Adding Time of Day Routing, page 3-63

Step 2 Add percentage routing Adding Percentage Routing, page 3-67

Add Local Number Portability (LNP)

Step 1 Create a TCAP subsystem Adding a TCAP Subsystem, page 3-68

Step 2 Create an IN Trigger to process LNP numbers Adding an IN Trigger, page 3-69

Add Cause Analysis

Step 1 Add the call retry, reattempt, or route advance Adding Call Retry, Reattempt, and Route Advance, page 3-70

Step 2 Add the announcement Adding Announcement, page 3-72

Add Call Limiting

Step 1 Adding the location label Adding the Location Label, page 3-73

Step 2 Add the call limiting function Adding the Call Limiting Result, page 3-73

Deploy the Configuration

Step 1 Deploy Deploy the Configuration, page 3-75




Get Started with Cisco VSPT

Starting a Provisioning Session

You can either start a new provisioning session or open a previous provisioning session in Cisco VSPT.

• Starting a New Provisioning Session, page 3-50

• Opening a Previous Provisioning Session, page 3-51

Starting a New Provisioning Session

To start a new configuration, complete the following steps:

Step 1 From the File menu, click New.


Figure 3-51 Adding a New Dial Plan Configuration

Step 2 Enter the configuration name and click OK. You see a screen similar to the one in Figure 3-1.

Figure 3-52 New Configuration Wizard

Step 3 Click the Perform manual configuration radio button at the bottom of the screen. Then click OK.




Opening a Previous Provisioning Session

To open a previous provisioning session, complete the following steps:

Step 1 From the File menu, click Open.

Step 2 Highlight the entry with your previously selected configuration name from the configuration list. Then click OK.

Saving the Cisco VSPT Configuration

You can save the current configuration by completing the following steps.

Step 1 From the File menu, click Save.


Figure 3-53 Save Options

Save the current configuration:

• As Working: Use to save a new configuration, either a configuration imported from the Cisco PGW 2200 Softswitch or a configuration created in Cisco VSPT. Use also to save modifications to an existing configuration, overwriting the last version. The configuration is saved in the /var/opt/CSCOvsp27/data/mgc/mistral directory.

• As Snapshot: Use to save modifications to an existing configuration under a new name in the ARCHIVE directory. The snapshot configuration is saved in /var/opt/CSCOvsp27/data/mgc/mistral/configname/ARCHIVE.

• As New Config: Use to save a modified configuration under a new name, leaving the original intact.

Step 2 Enter the name for the configuration if you choose save as snapshot or new config in Step 1.




Importing or Adding a Dial PlanTo use Cisco VSPT to provision a dial plan, you can either import or add a dial plan.

See Importing a Dial Plan File, page 3-2 and Adding a Dial Plan, page 3-4 for information on importing and adding a dial plan.

The corresponding MML commands for adding a dial plan 1111 is as follows:

numan-add:dialplan:custgrpid="1111",overdec="NO"

Adding Multiple Dial PlansPerform the steps described in Adding a Dial Plan, page 3-4 to add multiple dial plans.

For example, add dial plan 2222, 3333 in this configuration.


Figure 3-54 Multiple Dial Plans Added

The corresponding MML commands for this procedure are as follows:

numan-add:dialplan:custgrpid="2222",overdec="NO"numan-add:dialplan:custgrpid="3333",overdec="NO"

Adding the Dial Plan SelectionTo select different dial plans according to the B-number, perform the following steps:

Step 1 Expand the dial plan 1111 and click Dp Selection in the Trigger menu.

Step 2 Click Add in the bottom of the screen.




Step 3 Choose 2222 in the Dialplan Name drop-down list and click OK.

Figure 3-55 Specifying the Dial Plan Selection

Step 4 Repeat Step 1 to Step 3 to add a dial plan selection for 3333.

Step 5 Click the ResultSet under Results menu of the dial plan 1111.

Figure 3-56 Result Set Window

Step 6 Click Add in the middle of the screen and enter the result set name. Then click OK.

In this example, enter DpSelResultSet1 for the result set name.




Step 7 Highlight the newly added DpSelResultSet1 and click Add in the bottom of the screen.

Figure 3-57 Adding a Result

Step 8 Enter the DpSelResult1 as the result name. Then click OK.

Step 9 Repeat Step 5 to Step 8 to add a new result set DpSelResultSet2 and a new result DpSelResult2.

Step 10 Click Bdigtree under the Triggers menu and click Add in the bottom of the screen.

Step 11 Enter the required information as shown in Figure 3-58. Then click OK.

Figure 3-58 Add Bdigtree

Step 12 Repeat Step 10 and Step 11 to associate 202 digit string with DpSelResultSet2.


numan-add:dpsel:custgrpid="1111",newdp="2222"numan-add:resultset:custgrpid="1111",name="DpSelResultSet1"




numan-add:resulttable:custgrpid="1111",setname="DpSelResultSet1",resulttype="NEW_DIALPLAN",name="DpSelResult1",dw1="2222",dw2="2"numan-add:bdigtree:custgrpid="1111",callside="originating",setname="DpSelResultSet1",digitstring="101"numan-add:dpsel:custgrpid="1111",newdp="3333"numan-add:resultset:custgrpid="1111",name="DpSelResultSet2"numan-add:resulttable:custgrpid="1111",setname="DpSelResultSet2",resulttype="NEW_DIALPLAN",name="DpSelResult2",dw1="3333",dw2="2"numan-add:bdigtree:custgrpid="1111",callside="originating",setname="DpSelResultSet2",digitstring="202"

Adding Call ScreeningCall screening is one type of analysis performed on the calling number (A-number) and the called number (B-number) to determine if a call is to be accepted or rejected. The Cisco PGW 2200 Softswitch supports whitelist call screening that allows listed numbers and blocks all others, and blacklist call screening that blocks listed numbers and allows all others.

Whitelist or blacklist screening triggered by A-number analysis or B-number analysis results in four different ways to trigger call screening. The following two examples are for illustration purposes only.

• Adding Whitelist Screening Triggered by A-number Analysis, page 3-55

• Adding Blacklist Screening Triggered by B-number Analysis, page 3-58

Adding Whitelist Screening Triggered by A-number Analysis

The A-number analysis can trigger the whitelist and blacklist screening on calling number.

To add the whitelist screening triggered by A-number analysis, complete the following steps:

Step 1 Click the Resultset under the Results menu for the dial plan 2222.

Step 2 Add a result set and add a result in that result set.

In this example, add the result set Resultset2222 and add the result WhitelistResult as shown in Figure 3-59.




Figure 3-59 Adding the SCREENING Result Type

Step 3 Click Adigtree under the Triggers menu of the dial plan 2222.

Step 4 Add the Adigtree with the desired A-number trigger.

In this example, add 301648 as the A-number trigger as shown in Figure 3-60. If the calling number starts with 301648, the Cisco PGW 2200 Softswitch performs the actions defined in the result set Resultset2222.

Figure 3-60 Specifying the Adigtree with WhitelistResultSet Associated






Figure 3-61 Advanced Number Editor

Step 6 Choose Add new item in the Edit menu.

You can create a new screening file or open an existed screening file to edit. You can access these options in the File menu.

Step 7 Enter the required information as shown in Figure 3-62. Then click OK.

Figure 3-62 Specifying the A-number Whitelist New Number

Step 8 Choose Save this panel in the File menu and specify the name and the folder.

The working configuration is saved in /var/opt/CSCOvsp27/data/mgc/mistral/"Configuration Name"/WORKING.





Adding Blacklist Screening Triggered by B-number Analysis

The B-number analysis can trigger the whitelist and blacklist screening on calling number.

To add the blacklist screening triggered by B-number analysis, complete the following steps:

Step 1 Click the Service under the Results menu for the dial plan 3333.

Step 2 Add a service entry.

In this example, add a service entry Washington.

Note The service provides additional call screening capabilities. See Chapter 1, “Dial Plan and Routing.” for details.

Step 3 Click the Resultset.

Step 4 Add a result set and add a result in that result set.

In this example, add the result set Resultset3333. Then add the result BlacklistResult as shown in Figure 3-63.

Figure 3-63 Adding the SCREENING Result Type

Step 5 Click Bdigtree under the Triggers menu of the dial plan 3333.

Step 6 Add the Bdigtree with the desired B-number trigger.

In this example, add 703483 as the B-number trigger as shown in Figure 3-63. If the called number starts with 703483, the Cisco PGW 2200 Softswitch performs the actions defined in the result set Resultset3333.




Figure 3-64 Specifying the Bdigtree with BlacklistResultSet Associated


Step 8 Click the BBlack tab.

Step 9 Choose Add new item in the Edit menu.

Step 10 Add a new number entry as shown in Figure 3-65. Then click OK.

Figure 3-65 Specifying the B-number Blacklist New Number

Step 11 Choose Save this panel in the File menu and specify the name and the folder.

The working configuration is saved in /var/opt/CSCOvsp27/data/mgc/mistral/"Configuration Name"/WORKING.


The corresponding MML commands for these two procedures are as follows:

numan-add:resultset:custgrpid="2222",name="Resultset2222"numan-add:resulttable:custgrpid="2222",name="WhitelistResult",resulttype="SCREENING",setname="Resultset2222",dw1="1",dw3="1111",dw4="1111"numan-add:adigtree:custgrpid="2222",callside="originating",setname="Resultset2222",digitstring="301648"numan-add:awhite:custgrpid="2222",cli="3016484444"

numan-add:service:custgrpid="3333",name="Washington"




numan-add:resultset:custgrpid="3333",name="Resultset3333"numan-add:resulttable:custgrpid="3333",name="BlacklistResult",resulttype="SCREENING",setname="Resultset3333",dw1="1",dw2="Washington",dw3="1111",dw4="1111"numan-add:bdigtree:custgrpid="3333",callside="originating",setname="Resultset3333",digitstring="703483"

numan-add:bblack:custgrpid="3333",svnname="Washington",cli="3016484444"

Adding the Digit Modification in the Dial PlansThe digit modification string is used to insert numbers into either the A-number (calling party number) or B-number (called party number).

If you must perform digit modifications, you must add the digit modification table where you define a digit modification string to apply to an A-number or B-number.

To add a digit modification string, complete the following steps:

Step 1 Expand the dial plan 2222 and expand the Results menu under it.

Step 2 Click the component Digmodstring.


Step 4 Then enter the required information as shown in Figure 3-66. Click OK.

Figure 3-66 Defining a Digit Modification String

Step 5 Expand the dial plan 3333 and expand the Results menu under it.

Step 6 Repeat Steps 2 through 4 for dial plan 3333 to add the DigitMod1 with the digit modification string 70.

Step 7 Add a result AddDigitResult with the result type BMODDIG for dial plan 2222 to insert 86 before the incoming called number.

Enter the required information as shown in the Figure 3-67.




Figure 3-67 Adding BMODDIG Result for Dial Plan 2222

Step 8 Add a result RemoveDigitResult with the result type BMODDIG for dial plan 3333 to remove 70 at the beginning of the incoming called number.

Enter the required information as shown in the Figure 3-68.

Figure 3-68 Adding BMODDIG Result for Dial Plan 3333

Step 9 For dial plan 2222, add a result set RouteResultSet.

Step 10 Add a result RouteResult with the result type ROUTE as shown in Figure 3-69.




Note In result sets that are associated with A-number analysis triggers, like Adigtree, you cannot add routing information. The A-number analysis results are saved and used in the following analyses, like B-number analysis. In result sets that are associated with B-number analysis triggers, like Bdigtree, you can add routing information. In this example, you add a Bdigtree to contain routing information for dial plan 2222.

Figure 3-69 Adding a Route Result in a Result Set for Dial Plan 2222

Step 11 For dial plan 2222, add a Bdigtree trigger with the associated result set to RouteResultSet as shown in Figure 3-70.

Figure 3-70 Specifying the Bdigtree Trigger for the Routing

Step 12 Add a result with result type ROUTE in the Resultset3333 result set in dial plan 3333.




Note As mentioned previously, the result sets that are associated with B-number analysis triggers can contain routing information. In this example, Resultset 3333 is associated with Bdigtree which is one of the B-number analysis triggers. So you can add a result with the result type ROUTE in Resultset3333.


numan-add:digmodstring:custgrpid="2222",name="DigitMod1",digstring="86"numan-add:resulttable:custgrpid="2222",name="AddDigitResult",resulttype="BMODDIG",setname="Resultset2222",dw1="1",dw2="0",dw3="DigitMod1"numan-add:digmodstring:custgrpid="3333",name="DigitMod1",digstring="70"numan-add:resulttable:custgrpid="3333",name="RemoveDigitResult",resulttype="BMODDIG",setname="Resultset3333",dw1="1",dw2="2",dw3="DigitMod1"numan-add:resultset:custgrpid="2222",name="RouteResultSet"numan-add:resulttable:custgrpid="2222",name="RouteResult",resulttype="ROUTE",setname="RouteResultSet",dw1="rtlist111stim"numan-add:resulttable:custgrpid="3333",name="RouteResult",resulttype="ROUTE",setname="Resultset3333",dw1="rtlist222stim"

Adding Time of Day RoutingTime of day routing provides the capability for the user to select a route list or an entry point into the percentage based routing based on the time of day, and day of week.

To add time of day routing, you need to add conditional route description and conditional routing.

Perform the following steps to add time of day routing:

Step 1 From the main provisioning screen of the Cisco VSPT, click the Traffic button on the left side of the screen. Expand the Traffic hierarchical menu by clicking the icon to the left of Traffic. Expand the Routing menu and click Description.





Figure 3-71 Conditional Route Description

Step 2 Click Add in the bottom of the right pane.

The right pane looks similar to the one shown in Figure 3-72.




Figure 3-72 Specifying the Conditional Route Description

Step 3 Enter the name for the conditional route description in the Name field.

Step 4 Enter the T1 time and choose the desired route in the Route drop-down list between the T0 and T1 fields.

You are defining that between the time 00:00 and 09:00 of the day (in 1200 format for 12:00), the Cisco PGW 2200 Softswitch uses PBXrtelst as shown in the Figure 3-73. Continue the route definition of the remaining time periods for the whole day.

Figure 3-73 Conditional Route Descriptions

Step 5 Repeat the Step 2 through 4 to add another conditional route description Cond2.




Figure 3-74 Adding the Conditional Route Description Cond2

Step 6 Click Conditional Routing component in the Routing menu.


Step 8 Enter the required information as shown in Figure 3-74.

Figure 3-75 Adding Conditional Route


prov-add:condRteDesc:name="Cond1",rtlistname="ISPrtelst",ovrFlwSet="on"prov-ed:condRteDesc:name="Cond1",rtlistname="PBXrtelst",startTime="0900",endTime="1400"prov-ed:condRteDesc:name="Cond1",rtlistname="PGW2rtelst",startTime="1400",endTime="2200"prov-ed:condRteDesc:name="Cond1",rtlistname="SIPrtelst",startTime="2200",endTime="0000"prov-add:condRteDesc:name="Cond2",rtlistname="PGW3rtelst",ovrFlwSet="on"prov-ed:condRteDesc:name="Cond2",rtlistname="PBXrtelst",startTime="0500",endTime="1200"prov-ed:condRteDesc:name="Cond2",rtlistname="SIPrtelst",startTime="1200",endTime="1900"prov-ed:condRteDesc:name="Cond2",rtlistname="PGW2rtelst",startTime="1900",endTime="0000"prov-add:condRte:name="ConRte1",dow="Default",condRteDesc="Cond1"prov-ed:condRte:name="ConRte1",dow="Monday",condRteDesc="Cond2"




prov-ed:condRte:name="ConRte1",dow="Tuesday",condRteDesc="Cond1"prov-ed:condRte:name="ConRte1",dow="Wednesday",condRteDesc="Cond2"prov-ed:condRte:name="ConRte1",dow="Thursday",condRteDesc="Cond1"prov-ed:condRte:name="ConRte1",dow="Friday",condRteDesc="Cond2"prov-ed:condRte:name="ConRte1",dow="Saturday",condRteDesc="Cond1"prov-ed:condRte:name="ConRte1",dow="Hol2",condRteDesc="Cond1"

Adding Percentage RoutingTo add percentage routing, perform the following examples:

Step 1 Click Routing > Percentage Routing in the left pane of the main Cisco VSPT window.


Step 3 Enter required information as shown in Figure 3-76.

Figure 3-76 Adding Percentage Routing


prov-add:percRte:name="one",rtlistname="ISPrtelst",ovrFlwSet="on"prov-ed:percRte:name="one",rtlistname="PBXrtelst",load=25prov-ed:percRte:name="one",rtlistname="PSTNrtelst",load=50prov-add:percRte:name="two",rtlistname="HSI1rtelst",ovrFlwSet="on"prov-ed:percRte:name="two",rtlistname="PSTNrtelst",load=25prov-ed:percRte:name="two",rtlistname="PBXrtelst",load=25prov-ed:percRte:name="two",rtlistname="PGW3rtelst",load=25prov-ed:percRte:name="two",rtlistname="SIPrtelst",overflow="on"




Adding Local Number Portability (LNP)To add LNP in the dial plan, you need to add a Transaction Capabilities Application Part (TCAP) subsystem and an Intelligent Network (IN) trigger.

• Adding a TCAP Subsystem, page 3-68

• Adding an IN Trigger, page 3-69

Adding a TCAP Subsystem

Use the following procedure to create a subsystem for TCAP LNP queries:

Step 1 Click the MGC Config radio button of Cisco VSPT.

Step 2 Click the SS7 Subsystems component under the Signaling component.


Figure 3-77 Specifying the SS7 Subsystem




The TCAPIP or APC drop-down menu is used to specify the point code to be used to access the STP/SCP pair. Choose the stp-1 in this example.

In this example, enter 123 for the Local SSN which identifies the subsystem to use for the TCAP message. Enter 1 for the STP/SCP index which provides the unique index for SCP.

Adding an IN Trigger

To use the IN_Trigger result set to initiate a TCAP message to the Intelligent Network, complete the following steps:

Step 1 Click the Number Analysis radio button to return to number analysis provisioning.

Step 2 Click the Resultset component under dial plan 1111 and add a result set Resultset1111.

Step 3 Add the result LNPdip with the result type IN_TRIGGER in the Resultset1111 result set as shown in the Figure 3-78.

Figure 3-78 Adding a IN_TRIGGER Result Type

Step 4 Click Bdigtree under the Triggers menu.

Step 5 Add an B-number digit tree as shown in the Figure 3-79.




Figure 3-79 Specifying the Bdigtree


prov-add:ss7subsys:name="Ss7ss-lnp",desc="SS7 Subsystem for LNP",svc="stp-1", proto="SS7-ANSI",pri=1,localssn=123,stpscpind=1,transproto="SCCP",opc="opc-pgw",remotessn=123nuam-add:resultset:custgrpid="1111",name="Resultset1111"numan-add:resulttable:custgrpid="1111",name="LNPdip",resulttype="IN_TRIGGER",setname="Resultset1111",dw1="2",dw2="1"

numan-add:bdigtree:custgrpid="1111",callside="originating",setname="Resultset1111",digitstring="5551234"

Adding Cause AnalysisCause analysis is performed when a release (REL) message is received, or when a failure of some kind has occurred implying that the call must be released. The cause code value or the combined cause code and location code values are analyzed to provide a cause code that provokes rerouting of the call to another switch by the preceding switch, rerouting of the call to an announcement server, reattempt and redirecting, or call release.

In this example, you add call retry and announcement.

• Adding Call Retry, Reattempt, and Route Advance, page 3-70

• Adding Announcement, page 3-72

Adding Call Retry, Reattempt, and Route Advance

To add call retry, reattempt, or route advance in the dial plan, complete the following steps:

Step 1 Click Resultset under Results menu of dial plan 1111.

Step 2 Add a result set CallRetry.

Step 3 Add a result with the RETRY_ACTION result type in the result set CallRetry.

Enter the required information as shown in Figure 3-80.




Note Reattempt—Reattempts take place up to the limit provisioned in trunk group data. If the counter is exceeded, a trunk group advance takes place.Redirect—Redirect to a new trunk group to attempt circuit selection.TGAdvance—Reroute the call on an alternate route.

Figure 3-80 Add a Result with RETRY_ACTION Result Type

Step 4 Choose the Reattempt in the Retry type drop-down list. Then click OK.

Step 5 Click Cause under the Triggers menu of dial plan 1111.

Step 6 Click Add at the bottom of the screen.


Figure 3-81 Specifying the Cause




Adding Announcement

To generate an announcement in the event that a cause value is received indicated that all circuits are busy, complete the following steps:

Step 1 Click Resultset under the Results menu of dial plan 1111.

Step 2 Highlight the result set CallRetry you just added.

Step 3 Add a result with ANNOUCEMENT as the result type as shown in Figure 3-82.

Note Announcement ID—Four digit number identifying the announcement on the announcement server.Announce. type—Identifies whether the server is locally connected to the Cisco PGW 2200 Softswitch via ethernet or connected remotely via a PRI through the Cisco PGW 2200 Softswitch. Route List ID—Route group name used to route to the announcement server.Announcement data—Enables the switching off of a trunk group property Announcement for certain A-numbers or B-numbers. Not applicable when the announcement type is remote.

Figure 3-82 Add the Announcement


nuam-add:resultset:custgrpid="1111",name="CallRetry"numan-add:resulttable:custgrpid="1111",name="CallRetryResult",resulttype="RETRY_ACTION",setname="CallRetry",dw1="1"numan-add:cause:custgrpid="1111",causevalue="34",setname="CallRetry"numan-add:resulttable:custgrpid="1111",name="Announcement",resulttype="ANNOUNCEMENT",setname="CallRetry",dw1="1234",dw2="1",dw3="rtlist111stim",dw4="2"




Adding Call LimitingTo add call limiting, you need to specify a call limiting requirement and then add a LOC_LABEL result with this call limiting requirement associated.

• Adding the Location Label, page 3-73

• Adding the Call Limiting Result, page 3-73

Adding the Location Label

The location label specifies a call limiting requirement.

To add a location label, complete the following steps:

Step 1 Click the MGC Config radio button and expand the Signaling menu.

Step 2 Click Location Label and enter the required information as shown in Figure 3-83.

Figure 3-83 Specifying an Location Label

Note The call limit number in this example is 3000.

Step 3 Click Add in the bottom of the screen.

Adding the Call Limiting Result

To add a LOC_LABEL result associated with the location label you just added, complete the following steps:

Step 1 Click the Number Analysis radio button and expand the dial plan 1111.

Step 2 Add a new result set CallLimitingSet.

Step 3 Add a new result CallLimitingRes as shown in Figure 3-84.




Figure 3-84 Specifying an Result with LOC_LABEL Result Type

Step 4 Click OK in the bottom of the screen.

Step 5 Add Adigtree trigger associated with the CallLimitingSet result set as shown in Figure 3-85.

Figure 3-85 Adding a Adigtree Trigger for Call Limiting


prov-add:Loclabel:name="LOCLABEL-1",desc="Call Limiting",calllimit=3000numan-add:resultset:custgrpid="1111",name="CallLimitingSet"numan-add:resulttable:custgrpid="1111",name="CallLimitingRes",resulttype="loc_label", dw1="LOCLABEL",setname="CallLimitingSet"numan-add:adigtree:custgrpid="1111",callside="originating",digitstring="303",setname="CallLimitingSet"




Deploy the ConfigurationTo deploy the configuration in the Cisco VSPT, perform the following steps:

Step 1 Click Deploy in the Tools menu.


Figure 3-86 Deployment Selection

Step 2 Enter the destination configuration name on the Cisco PGW 2200 Softswitch.

Step 3 Click the radio button before the desired deployment action.

The corresponding MML commands for this procedure is as follows:

prov-stp

MML Commands ReferenceThis section provides the corresponding MML commands for this example.

________________________________________; Start the Provisioning Session;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;prov-sta::srcver="new",dstver="test",confirm

________________________________________; Add Dial Plans

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

numan-add:dialplan:custgrpid="1111",overdec="NO"numan-add:dialplan:custgrpid="2222",overdec="NO"




numan-add:dialplan:custgrpid="3333",overdec="NO"

________________________________________; Provision Dial Plan Selection;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;numan-add:dpsel:custgrpid="1111",newdp="2222"numan-add:resultset:custgrpid="1111",name="DpSelResultSet1"numan-add:resulttable:custgrpid="1111",setname="DpSelResultSet1",resulttype="NEW_DIALPLAN",name="DpSelResult1",dw1="2222",dw2="2"numan-add:bdigtree:custgrpid="1111",callside="originating",setname="DpSelResultSet1",digitstring="101"numan-add:dpsel:custgrpid="1111",newdp="3333"numan-add:resultset:custgrpid="1111",name="DpSelResultSet2"numan-add:resulttable:custgrpid="1111",setname="DpSelResultSet2",resulttype="NEW_DIALPLAN",name="DpSelResult2",dw1="3333",dw2="2"numan-add:bdigtree:custgrpid="1111",callside="originating",setname="DpSelResultSet2",digitstring="202”

________________________________________; Provision an A-number Whitelist Call Screening;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;numan-add:resultset:custgrpid="2222",name="Resultset2222"numan-add:resulttable:custgrpid="2222",name="WhitelistResult",resulttype="SCREENING",setname="Resultset2222",dw1="1",dw3="1111",dw4="1111"numan-add:adigtree:custgrpid="2222",callside="originating",setname="Resultset2222",digitstring="301648"numan-add:awhite:custgrpid="2222",cli="3016484444"

________________________________________; Provision a B-number Blacklist Call Screening;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;numan-add:service:custgrpid="3333",name="Washington"numan-add:resultset:custgrpid="3333",name="Resultset3333"numan-add:resulttable:custgrpid="3333",name="BlacklistResult",resulttype="SCREENING",setname="Resultset3333",dw1="1",dw2="Washington",dw3="1111",dw4="1111"numan-add:bdigtree:custgrpid="3333",callside="originating",setname="Resultset3333",digitstring="703483"numan-add:bblack:custgrpid="3333",svnname="Washington",cli="3016484444"

________________________________________; Provision Digit Modification;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;numan-add:digmodstring:custgrpid="2222",name="DigitMod1",digstring="86"numan-add:resulttable:custgrpid="2222",name="AddDigitResult",resulttype="BMODDIG",setname="Resultset2222",dw1="1",dw2="0",dw3="DigitMod1"numan-add:digmodstring:custgrpid="3333",name="DigitMod1",digstring="70"numan-add:resulttable:custgrpid="3333",name="RemoveDigitResult",resulttype="BMODDIG",setname="Resultset3333",dw1="1",dw2="2",dw3="DigitMod1"numan-add:resultset:custgrpid="2222",name="RouteResultSet"numan-add:resulttable:custgrpid="2222",name="RouteResult",resulttype="ROUTE",setname="RouteResultSet",dw1="rtlist111stim"numan-add:resulttable:custgrpid="3333",name="RouteResult",resulttype="ROUTE",setname="Resultset3333",dw1="rtlist222stim"

________________________________________; Provision Time of Day Routing;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;prov-add:condRteDesc:name="Cond1",rtlistname="ISPrtelst",ovrFlwSet="on"prov-ed:condRteDesc:name="Cond1",rtlistname="PBXrtelst",startTime="0900",endTime="1400"prov-ed:condRteDesc:name="Cond1",rtlistname="PGW2rtelst",startTime="1400",endTime="2200"prov-ed:condRteDesc:name="Cond1",rtlistname="SIPrtelst",startTime="2200",endTime="0000"prov-add:condRteDesc:name="Cond2",rtlistname="PGW3rtelst",ovrFlwSet="on"prov-ed:condRteDesc:name="Cond2",rtlistname="PBXrtelst",startTime="0500",endTime="1200"prov-ed:condRteDesc:name="Cond2",rtlistname="SIPrtelst",startTime="1200",endTime="1900"




prov-ed:condRteDesc:name="Cond2",rtlistname="PGW2rtelst",startTime="1900",endTime="0000"prov-add:condRte:name="ConRte1",dow="Default",condRteDesc="Cond1"prov-ed:condRte:name="ConRte1",dow="Monday",condRteDesc="Cond2"prov-ed:condRte:name="ConRte1",dow="Tuesday",condRteDesc="Cond1"prov-ed:condRte:name="ConRte1",dow="Wednesday",condRteDesc="Cond2"prov-ed:condRte:name="ConRte1",dow="Thursday",condRteDesc="Cond1"prov-ed:condRte:name="ConRte1",dow="Friday",condRteDesc="Cond2"prov-ed:condRte:name="ConRte1",dow="Saturday",condRteDesc="Cond1"prov-ed:condRte:name="ConRte1",dow="Hol2",condRteDesc="Cond1"

________________________________________; Provision Percentage Routing;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;prov-add:percRte:name="one",rtlistname="ISPrtelst",ovrFlwSet="on"prov-ed:percRte:name="one",rtlistname="PBXrtelst",load=25prov-ed:percRte:name="one",rtlistname="PSTNrtelst",load=50prov-add:percRte:name="two",rtlistname="HSI1rtelst",ovrFlwSet="on"prov-ed:percRte:name="two",rtlistname="PSTNrtelst",load=25prov-ed:percRte:name="two",rtlistname="PBXrtelst",load=25prov-ed:percRte:name="two",rtlistname="PGW3rtelst",load=25prov-ed:percRte:name="two",rtlistname="SIPrtelst",overflow="on"

________________________________________; Provision Local Number Portability (LNP);;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;prov-add:ss7subsys:name="Ss7ss-lnp",desc="SS7 Subsystem for LNP",svc="stp-1", proto="SS7-ANSI",pri=1,localssn=123,stpscpind=1,transproto="SCCP",opc="opc-pgw",remotessn=123nuam-add:resultset:custgrpid=”1111”,name="Resultset1111"numan-add:resulttable:custgrpid="1111",name="LNPdip",resulttype="IN_TRIGGER",setname="Resultset1111",dw1="2",dw2="1"numan-add:bdigtree:custgrpid="1111",callside="originating",setname="Resultset1111",digitstring="5551234"

________________________________________; Provision Call Retry;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;nuam-add:resultset:custgrpid="1111",name="CallRetry"numan-add:resulttable:custgrpid="1111",name="CallRetryResult",resulttype="RETRY_ACTION",setname="CallRetry",dw1="1"numan-add:cause:custgrpid="1111",causevalue="34",setname="CallRetry"

________________________________________; Provision an Announcement;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;numan-add:resulttable:custgrpid="1111",name="Announcement",resulttype="ANNOUNCEMENT",setname="CallRetry",dw1="1234",dw2="1",dw3="rtlist111stim",dw4="2"

________________________________________; Provision Call Limiting;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;prov-add:loclabel:name="LOCLABEL-1",desc="Call Limiting",calllimit=3000numan-add:resultset:custgrpid="1111",name="CallLimitingSet"numan-add:resulttable:custgrpid="1111",name="CallLimitingRes",resulttype="loc_label", dw1="LOCLABEL",setname="CallLimitingSet"numan-add:adigtree:custgrpid="1111",callside="originating",digitstring="303",setname="CallLimitingSet"

________________________________________; Choose the Deployment Action (Send Configuration to MGC Only);;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;prov-stp



provisioning dial plans with the cisco vspt cisco mgc software release 9.5(1) chapter 3...

Documents