This node has one entry and three exits. The number of exits cannot be changed.

Follow these steps to configure the Account Code Entry node, to set or amend the Main Account Number Announcement.

1. The main announcement is the announcement that will be played to prompt for an Account number.

   In the Main Announcement area, select the Announcement Set which contains the main announcement you want to play to the caller.

   Result: The Announcement Entry field becomes available.

2. From the Announcement Entry drop-down list, select the main announcement you want to play to the caller.

3. Set the Repetition field to the number of times you wish to repeat the announcement, by increasing or decreasing the value in the spin box. The allowable values are from 1 (default) to 127. If set to zero, the announcement will be repeated for the length of the duration set.

4. Set the Duration field to the length of time in seconds that the announcement is to be played. The allowable values are from 0 (default) to 32767. If set to zero, the announcement will be played for its full length.

5. Amending the Retry announcement on Invalid Entry.

   The retry announcement will be played if the Account Number entered after the main announcement is not valid.

   In the Retry Announcement area, select one of the following as described in steps 1 - 4:

   • Announcement Set which contains the retry announcement

   • Announcement Entry for the retry announcement you want to play, and set

   • Repetition to the number of times to repeat the retry announcement

   • Duration to the length of time, in seconds, that the retry announcement is to be played.

6. Set the Number of Retries field to the number of times that the node will attempt to collect the correct Account Number from the caller, before routing the call to the Not Allowed branch. This value may be between 0 and 10.

7. Click Save.

   Note: Save is not available until all the required information has been selected or entered.

Note: The announcement set and announcement entry lists are populated with data that is specified using the Announcements tab of the ACS Configuration screen.

For more information about configuring announcement sets and announcement entries, see the Announcements tab of the ACS Configuration screen.

This node has one entry and three exits. The number of exits cannot be changed.

Follow these steps to configure the Activate Control Plan node.

1. From the Main Announcement area, select the Announcement Set which contains the main announcement you want to play to the caller. The main announcement will be played to prompt for a Control Plan ID (MF identifier).

   Result: The Announcement Entry field becomes available.

2. From the Announcement Entry drop-down list, select the main announcement you want to play to the caller.

3. Set the Repetition field to the number of times to repeat the main announcement while the system waits for the caller to take an action. If set to zero, the announcement will be repeated for the length of the duration set.

4. Set the Duration field to the length of time, in seconds, that the announcement is to be played. If set to zero, the announcement will be played for its full length.

5. The retry announcement contains the announcement you want to play to the caller if an invalid ID is entered after the main announcement.

   In the Retry Announcement area, select one of the following as described in steps 1 - 4:

   • Announcement Set which contains the retry announcement

   • Announcement Entry for the retry announcement you want to play, and set the

   • Repetition to the number of times to repeat the retry announcement

   • Duration to the length of time, in seconds, that the retry announcement is to be played

6. Set the Number of Retries field to the number of times that the node will attempt to collect the correct ID from the caller, before routing the call to the Not Updated branch. This value may be between 0 and 10.

7. If you:

   • want to prompt the caller to set an activation date, tick the Prompt for Activation Time? check box.

   • do not want to prompt the caller to set an activation date, go to step 11.

8. From the Timezone Type drop-down list, select the timezone you want to use.

   If you select the Explicit Unix TZ option, you need to select a specific region from the Unix Timezone field.

   For more Time zone information, see Time Zones.

9. The Date Announcement area contains the announcement you want to play to the caller. Select one of the following as described in steps 1 - 4:

   • Date Announcement Set which contains the main announcement

   • Date Announcement Entry for the main announcement you want to play, and set the

   • Repetition to the number of times to repeat the announcement

   • Duration to the length of time, in seconds, that the announcement is to be played.

10. The Retry Date Announcement area contains the announcement you want to be repeat while the system waits for the caller to take an action. Select one of the following as described in steps 1 - 4:

    • Date Announcement Set which contains the retry announcement

    • Date Announcement Entry for the retry announcement you want to play, and set the

    • Repetition to the number of times to repeat the announcement

    • Duration to the length of time, in seconds, that the announcement is to be played.

11. Click Save.

    Note: Save is not available until all the required information has been selected or entered.

Note: The announcement set and announcement entry lists are populated with data that is specified using the Announcements tab of the ACS Configuration screen.

For more information about configuring announcement sets and announcement entries, see the Announcements tab of the ACS Configuration screen.

Here is an example of using the Activate Control Plan Node to activate a Control Plan for a Service Number or CLI.

For detailed information on the ACS Management Control Plan, see the chapter - Dial-up Control Plan Management in ACS.

1. A customer is set up with an 0800 number and the self management screens.

2. The customer creates 2 control plans.

3. The customer phones a number attached to the ACS management control plan to change which control plan is active for the number.

Here is an example of a Configure Activate Control Plan screen in ACS management control plan that does this. See the ACS Management Control Plan example in ACS User's Guide to see the entire control plan.

Description of the illustration cpeconfigureactivatecontrolplanex_2-4-2.jpg

In this example, the caller is prompted to enter the:

• Control Plan ID (MF Identifier) and the

• Date to activate the Control Plan.

The shortcut keys to add an Attempt Termination to Pending TN node are Alt+Shift+A

This node has one entry and six exits. The number of exits cannot be changed.

Some nodes require telephony (that is, Play Announcement, Unconditional Termination, Disconnect, Attempt Termination, Selection Dependant Routing, Unconditional Terminate to Pending TN). Such nodes may follow Exits 2 and 3 of the Attempt Terminate to Pending TN node. They may not follow exits 1, 4, 5 and 6.

Follow these steps to configure the Attempt Terminate to Pending TN node.

1. From the National/International Prefix Location drop down lists, select the profile Data Type and Location to read Least Cost Routing configuration from.

   The location list displays all available fields for the data type selected.

   For more information about profile blocks, see Profile Blocks and Tags.

   If you do not want to use Least Cost Routing on this destination number, select:None Selected.

2. You must set the Timeout value for the node. This is the number of seconds that is allowed to pass before the call is routed down the No Answer branch. The Timeout value may be between 0 and 180 seconds.

3. Click Save.

This node has one entry and eight exits. The number of exits cannot be changed.

Note: These exit descriptions are specific to the responses received from an Oracle VWS billing engine. For specific information about how responses from other billing engines map to these exits, see the technical guide for the interface for billing engine being used.

Follow these steps to configure the node.

1. In the No Answer Timeout field, specify the number of seconds the switch should wait for the called party to accept the connection before assuming there was no answer. Value range: 0-2047
2. In the Maximum Call Duration field, specify the maximum number of 'deci-seconds' before the call is disconnected.
3. Tick Record Call in CDR if you wish to generate a 'Call Information' report at the end of the call. This call information can then be used in the EDR.

   Note: Selecting this option may impact other nodes within this control plan. If the Record Call in CDR check box is ticked, all subsequent attempt termination nodes will request a CIR.

4. From the Profile IdentifierData Type and Location drop down lists, select the profile to read Least Cost Routing configuration from.

   The location list displays all available fields for the data type selected.

   For more information about profile blocks, see Profile Blocks and Tags.

   If you do not want to use Least Cost Routing on this destination number, select None Selected.

5. Click Save.

The shortcut keys to add an Attempt Termination node are Alt+A.

This node has one entry and six exits. The number of exits cannot be changed.

Some nodes require telephony (that is, Play Announcement, Unconditional Termination, Disconnect, Attempt Termination, Selection Dependant Routing, Unconditional Terminate to Pending TN). Such nodes may follow Exits 2 and 3 of the Attempt Termination node. They may not follow exits 1, 4, 5 and 6.

Follow these steps to edit the Attempt Termination node.

1. To specify a termination number for the node, select the range in which the number lies from the ranges shown.

   Result: The prefix digits will be entered into the Termination Number entry field.

2. Use the Termination Number entry field to complete the number.

   The Xs in the range signify the minimum number of digits that are required and the Ys signify the maximum number of digits in the range.

3. Type the number of seconds that the call is to ring at the termination number before it is routed down the No Answer branch of the node.

4. Click Save to commit that termination number to the node.

   Note: The Save button will only become available when a number that is within the selected range is displayed in the Termination Number entry field.

This node has one entry and may have 4 through 10 exits. You can configure the number of exits within this range as required, using the Edit Node Exits option on the shortcut menu. See Editing Feature Node Exits.

Node exits 1 through 3 are set by the system and may not be changed.

Follow these steps to edit the Branch on Bearer node.

1. Edit the node exits to add exits as required. See Editing node exits for details.

   Note: The new number of exits is represented on the node icon, but not on the configuration screen exit list.

2. Open the Configure Branch on Bearer screen.

   Result: The Bearer Type Branching tree lists all the exits that have been added, as in the example below, showing 7 exits.

   By default, Branch 1 and Branch 2 are pre-configured.

   
   Description of the illustration cpeconfigurebranchonbearer_ex_notconfig_2-4-2.jpg

   Note: The number of branches to configure will always be the total number of exits configured, minus the three pre-configured branches. In this example node, there are 7 exits, therefore there are 4 configurable branches.

3. In the Bearer Component frame, select the option on which to branch.

   • Layer 1 Protocol -

   • Info Transfer Rate -

   • Info Tran capability -

   • Transfer Mode -

   • Coding Standard -

   • High Layer Character - matches on Octet 4 of the High Layer Characteristics bearer field.

4. Branches are made up of rules. A rule is either a range of bearer types or a single value.

   The maximum number you can enter in the rules is 256. Before you can add rules to any other branches, you must edit the rules for Branch 2 (that is, 1-256) and change 256 to the number appropriate to the branch. This will allow you to add rules to the branches.

   To edit a rule, right-click on a rule and click Edit.

   Result: The Edit Rules dialog will appear.

   To create a rule:

   • Of a single value, you can enter the value in the left hand field only, or the same number in both fields.

   • For a range of numbers, enter values in both fields. The 'from' value must be lower than the 'to' value.

   Note: The numbers must not overlap any other rule ranges. Make the change and click OK.

5. To add rules to a branch, right-click on the branch. From the pop-up menu displayed, select Add. You see the Add Rules screen.

6. Create the rule as required.

7. Click OK.

   Result: One of the following will occur:

   • The new rule will be added to the rule list.

   • If a rule conflicts with an existing rule, a warning dialog box will appear providing more detail about the conflict.

   Note: You may create as many rules per Branch as you require.

8. Edit or delete rules under each branch.

   To delete a rule, right-click on a rule and click Delete.

   Result: The rule is deleted from the branch.

9. When rules have been added to all branches, the Save button will become available.

   Click Save.

   Result: The node data is saved.

Notes:

• After configuration, you may add or remove exits for the node using Edit Node Exits, then edit the node branches again.

• If you remove exits, when you open the Configure Branch on Bearer screen again you will see a warning, such as this example.

  Click OK to continue, then edit the node.

This node has one entry and two exits. The number of exits cannot be changed.

This node requires no configuration data. You may change the Node name, if required.

This node has one entry and initially five exits. You can manually add up to another five exits, making a total of 10 exits.

Note: The call-forwarded exit scenario for this node is identical to that of the Call Forwarded Branching node. Refer to the section on the Call Forwarded Branching node; in particular the node exits.

Branches are made up of Cause code rules. A rule is either a range of Event Report Request BCSM Codes or a single value. Each branch can have as many rules as required, provided that the cause code has not been configured in another rule within this node.

Cause codes are defined in the following two documents.

• ETS 300 374-1

  Intelligent Network (IN):

  Intelligent Network Capability Set 1 (CS1);

  Core Intelligent Network Application Protocol (INAP);

  Part 1: Protocol specification

  European Telecommunications Standards Institute

  In particular, see EventSpecificInformationBCSM on page 47.

• ITU-T Recommendation Q.850

  Usage of Cause and Location

  in the Digital Subscriber Signalling

  System No. 1 and the Signalling

  System No. 7 ISDN User Part

  International Telecommunications Union

Follow these steps to edit the Branch on ERRB Cause Code node.

1. Edit the node exits to add up to another five exits as required. See Editing node exits for details.

   Note: The new number of exits is represented on the node icon, but NOT on the configuration screen exit list.

2. Open the Configure Branch on ERRB Cause Code screen.

   Result: The ERRB Cause Code Branching tree lists all the exits that have been added, as in the example below, showing 7 exits.

   
   Description of the illustration cpeconfigurebranchonerrbcc_ex_notconfig_2-4-2.jpg

   Note: The number of branches to configure will always be the total number of exits configured, minus the 4 pre-configured branches. In this example node, there are 7 exits, therefore there are 3 configurable branches.

3. To add rules to a branch, right-click on the Branch. From the pop-up menu displayed, select Add. You see the Add Rules screen.

4. Create the rule as required.

   To create a rule:

   1. of a single value, you can enter the value in the left hand field only, or the same number in both fields.

   2. for a range of numbers, enter values in both fields. The 'from' value must be lower than the 'to' value.

   Note: The numbers must not overlap any other rule ranges. The maximum value of a rule is 256.

5. Click OK.

   Result: Either:

   • the new rule will be added to the rule list, or

   • if a rule conflicts with an existing rule, a warning dialog box will appear providing more detail about the conflict.

   Note: You may create as many rules per Branch as you require.

6. Edit or delete rules under each branch. To:

   • edit a rule, right-click on a rule and click Edit.

     Result: The Edit Rules dialog will appear.

     Make the change and click OK

   • delete a rule, right-click on a rule and click Delete.

     Result: The rule is deleted from the branch.

7. When rules have been added to all branches, the Save button will become available.

   Click Save.

   Result: The node data is saved.

Note: After configuration, you may add or remove exits for the node using Edit Node Exits, then edit the node branches again.

If you remove exits, when you open the Configure Branch on Bearer screen again you will see a warning, such as this example.

Description of the illustration acsbearertypebranchingwarning.jpg

Click OK to continue, then edit the node.

For a terminating call, suppose you want to select the following outcomes, depending on the values of cause numbers.

• If ACS was notified of call-forwarding, you want to play an announcement about call-forwarding.

• For cause number 1, you want to play an announcement about the telephone number being unallocated.

• For cause numbers 17 through 20, you want to play an announcement about the telephone number being either busy, unresponsive, unanswered or unanswerable because the telephone is switched off.

• For all other cause numbers, you want to simply disconnect the call.

To implement this scenario, you could set up the control plan shown below.

Description of the illustration cpecontrolplaneditorexamplecontrolplanerrbrouting_2-4-2.jpg

You would set up the configurable exits of the branch on ERRB Cause Code node as shown below.

Description of the illustration cpeconfigurebranchonerrbcausecodecroperrbcausecodebranching_2-4-2.jpg

The non-configurable exit branches would remain as shown below.

Description of the illustration cpeconfigurebranchonerrbcausecodecropexits1-4_2-4-2.jpg

This node has one entry and five exits. The number of exits cannot be changed.

The interpretation of the value depends on the indicator selected.

Follow these steps to edit the node configuration.

1. Select the indicator option:

   • Presentation Restricted

   • Screening

   • Number Incomplete

2. Select the number from the drop down list.

   • CallingPartyNumber

   • AdditionalCallingPartyNumber

   • OriginalCalledPartyID

   • RedirectingPartyID

   • LocationNumber

   • LocationInformationLocationNumber

3. Click Save.

This table describes the meaning of each value, depending on the indicator selected.

This node has one entry and six exits. The number of exits cannot be changed.

This node requires no configuration data. You may change the Node name, if required.

This feature node can have between three and ten exits. You can configure the number of exits within this range as required, using the Edit Node Exits option on the shortcut menu. See Editing Feature Node Exits.

Exits 1 and 2 are set by the system and may not be changed by the user.

Follow these steps to edit the feature node configuration.

1. Edit the number of feature node exits to create one or more additional exits. See Editing node exits for details.

   Note: The new number of exits is represented on the feature node icon, but NOT in the exit list in the feature node configuration window.

2. Open the Configure Branch on Service Key window.

   The Service Key Branching tree displays, listing all the configurable exit branches. This will be the total number of feature node exits, minus the two pre-configured exits. You configure the feature node by specifying the branching rules for each exit, where a rule is either a range of service keys or a single value.

   For example, the following diagram shows the service key rules configured for two exit branches.

   
   Description of the illustration cpeconfigurebranchonservicekey_exitbranches_2-4-2.jpg

3. Add the rules to each branch by performing the following steps:

   1. Right-click on the branch, and select Add from the pop-up menu. The Add Rules dialog displays.

   2. Specify the service key values for the rule. To specify:

      • A single value, enter the value in the left hand field only, or the same number in both fields. A service key number can have up to 10 digits and must be less than or equal to 2147483647.

      • A range of numbers, enter values in both fields. The 'from' value must be lower than the 'to' value.

      • ClickOkay. The rule is added to the list of rules for the selected branch.

        If a rule conflicts with an existing rule or the rule is invalid, an Invalid Rule dialog box appears informing you about the error.

   Note: You can add multiple rules to a branch, but you must specify at least one rule for each branch.

4. To edit a previously configured rule, perform the following steps:

   1. Right-click on the rule you want to change and select Edit from the pop-up menu.

      The Edit Rules dialog appears, displaying the previously configured rule values.

   2. In the text fields enter the new rule values. The numbers for the rule must not overlap any other rule range.

   3. Click Okay.

5. To delete a previously configured rule, right-click on the rule and select Delete from the pop-up menu.

6. Click Save to save the feature node configuration.

   Note: You must configure at least one rule for each branch before you will be able to save the feature node configuration.

Note: You can configure additional exits for, or remove exits from the feature node, at any time. If you remove an exit then the next time you open the Configure Branch on Service Key window, a warning message displays:

Description of the illustration cpeservicekeybranchingwarning_2-4-2.jpg

This node has one entry and three exits. The number of exits cannot be changed.

Follow these steps to configure the node.

1. In the First Number section, specify the input value for your mathematical calculation by performing the following steps:

   1. From the Profile Value Data Type list, select the type of value for your mathematical calculation. Depending on your selection, different options for Profile Value Location will be available to you.

   2. From the Profile Value Location list, select the location of the value for your mathematical calculation.

   3. From the Profile Value Field list, select the field that contains the value for your mathematical calculation.

2. In the Operation section, select the mathematical operation you wish to perform (Multiply, Divide, Add, Subtract, or Modulus).

3. In the Second Number section, specify the input value needed to complete your mathematical calculation by performing the following steps:

   1. From the Profile Value Data Type list, select the type of value of the second number needed to complete your mathematical calculation.

   2. If your profile value data type is a fixed value: In the Profile Value Fixed Value section, enter the number by which you wish to add, subtract, multiply, or divide. Otherwise, leave Profile Value Fixed Value blank.

4. In the Rounding section, select the option for the type of rounding you prefer (Truncate, Ceiling, Median Up, Bankers, or Floor).

5. In the Destination section, specify the profile field in which to store the calculation result by performing the following steps:

   1. From the Destination Profile Data Type list, select the type of value of the profile field.

   2. From the Destination Profile Location list, select the profile, database, or storage associated with your destination profile field.

   3. From the Destination Profile Field list, select the profile field in which to store the calculation result.

6. Click Save.

This feature node has one entry and three exits. The number of exits cannot be changed.

To edit the Call Filtering feature node:

1. From the lists in the Compare With Which Buffer area, select the buffer that contains the number to check in the allowed or barred numbers list. You specify the number list to use in the location fields.

2. From the Location Of List Type lists, select the profile field that sets whether the list type is allowed or barred.

3. From the Location Of List Data lists, select the prefix tree profile field that contains the list of allowed or barred numbers.

4. From the Location Of Ignore Flag lists, select the profile field that sets whether the list should be used or ignored. When the value in the profile field is set to true, the list is ignored and all numbers are allowed.

5. Click Save.

The Call Forwarded Branching node has one entry and two exits. The number of exits is fixed and cannot be changed.

Note: ACS is advised that a terminating call has been forwarded when an EventReportBCSM is received from the SSP. EventReportBCSM indicates to ACS's tBusy and tNoAnswer detection points that a "call forwarded" has been received.

This node requires no configuration data. You may change the Node name, if required.

For a terminating call, you may want to play an announcement if the call has been call-forwarded and simply terminate the call if it has not been call-forwarded.

To implement this scenario, you could set up the control plan shown below.

Description of the illustration cpecontrolplaneditorexamplecallforwardcp_5-0-0.jpg

This node has one entry and six exits. The number of exits cannot be changed.

For each combo box combination on this screen, there are two methods of entering a value:

1. Use the drop down lists in the Data Type, Location and Field boxes, as in this example, to select the relevant values:

   
   Description of the illustration cpe_node_profile_fields_example_ncc5-0-0.jpg

2. Select Fixed Value in the Data Type box.

   Result: The fields will change, as in this example, and you can type the required value in the Fixed Value field.

   
   Description of the illustration cpe_node_fixed_example_ncc5-0-0.jpg

Follow these steps to edit the node configuration.

1. In the Switch area, select the Name of the network entity for the ICA destination from the drop down list .

2. (Optional) In the Calling Party frame, specify the value for the Calling Party ICA. Specify either an ACS termination number or an ACS buffer.

3. (Optional) In the Prefix Calling Party field, type a prefix for the calling party. This could be used, for example, so that the switch will not be re-triggered on the terminating leg.

4. (Required) In the Party to call frame, specify the value for the Called Party ICA. Specify either an ACS termination number or an ACS buffer.

5. In the No Answer Timeout field, type the number of seconds the switch should wait for the called party to accept the connection before assuming there was no answer. The No Answer Timeout value must be greater than zero.

   Note: The wait time is automatically increased by a configurable amount defined in acs.conf. See ACS Technical Guide for details.

6. (Optional) In the Controller area, enter the Service Key for the IDP.

7. For each IDP, specify the values for the following optional fields:

   • callingPartyNumber

   • calledPartyNumber

   • redirectingPartyID

   • locationNumber

   • additionalCallingPartyNumber

8. Click Save.

Note: The list of data types is fixed at installation time for each feature node or screen.

Further reference:

• For information about profile blocks (data type, location, and field) and how to use them, see Profile Blocks and Tags.

• The primary tag lists are configured in the SMS > Services > ACS Service > Configuration >Profile Tag Details and Profile Tag Mapping tabs (see ACS User's Guide, Profile Tag Details for more information).

This node has one entry and two exits. The number of exits cannot be changed.

Follow these steps to edit the node configuration.

1. Select the Suppress Ann check box to suppress switch announcements in the outgoing Connect message.

2. Select the OCSIApplicable check box to set the OCSIApplicable parameter in the outgoing Connect message.

3. Click Save.

The shortcut keys to add a Calling Party node are Alt+C.

This node has one entry and may have two through 20 exits. You can configure the number of exits within this range as required, using the Edit Node Exits option on the shortcut menu. See Editing Feature Node Exits.

Follow these steps to configure the node.

1. Edit the node exits to add up to another eighteen exits as required. See Editing node exits for details.

2. Click Add Prefix.

   Result: A highlighted entry appears in the display grid. This creates the new Prefix entry, and is edited in the following steps.

3. Type the prefix in the entry field to the left of the Branch box.

   Calls made from numbers with this prefix are routed to the exit specified in this step.

4. Use the Branch box to select the exit these calls should be routed to.

5. Click Change.

   Result: The Prefix appears in the display grid, with the exit displayed in brackets.

6. Repeat Steps 1 – 4 for as many prefix additions as required.

7. Set the default branch for all calls which do not match a specified prefix.

8. Click Save.

   Note: Save is not available until all the required information has been selected or entered.

The shortcut keys to add a Calling Party Category node are Alt+Shift+C.

This node has one entry and may have two through seven exits. You can configure the number of exits within this range as required, using the Edit Node Exits option on the shortcut menu. See Editing Feature Node Exits.

Follow these steps to edit the Calling Party Category node.

1. Edit the node exits to add up to another five exits as required. See Editing node exits for details.

2. Select the default branch.

   Where the system is not configured to process calling party category data, the system will use the default branch for any calls using a Control Plan containing this node.

3. Click Add Entry.

   Result: A highlighted entry appears in the display grid. This creates the new entry, and is edited in the following steps.

4. Use the Calling Party Type spin box to select the category number of the required type of phone.

   Any value from 0 – 255 may be used to indicate any given category of phone. These values are network-specific, so they may be set to reflect the needs of the market. The table below details the standard values used for ISUP.

   Result: Calls from phones of the selected calling party type will route down the selected branch.

   Example: If values are selected from the ITU/ETSI CS1 standards, category 4 represents calls from the Russian language operator, and category 15 represents calls from payphones.

   If the incoming call is from an undefined category, or if the system is not configured to process calling party category data, the call will be routed down the default branch.

5. Use the Branch spin box to select the exit.

   This is the exit to which calls made from phones of this category are routed.

6. Click Change.

   Result: The Category appears in the display grid, with the exit displayed in brackets.

7. Repeat Steps 1 – 4 for as many category additions as required.

8. Click Save.

   Note: Save is not available until all the required information has been selected or entered.

The table below details the standard values.

The following table shows values for the IS-41 NP(MSID) type.

For more information about the Calling Party Category, see ITU-T standard Q763.

This is a list of the system-generated tags. These may be used in the Change CDR node, but their values will not be changed, a new tag of the same name will be added to the end of the EDR instead.

CID, OA, OTI, CUST, SN, TN, CGN, CLI, SK, TCS, TCE, LPN, LAC, CS, CPC, CC, CPNI, PCNA, TPNI, PTNA, CGNA, TGNA, TFN, LGID, CPN, CAET, CCET, CA, RELC, OCPI, CPNN, CGNN, CPPI, NOAT, CBAT, FATS, CCTS, HTS, AIDL, EXTn

This node has one entry and two exits. The number of exits cannot be changed.

Follow these steps to edit the node configuration.

1. Select the ForceAppend check box to force the specified EDR tag to be appended to the EDR. If the tag already exists in the EDR, it will not be altered and the EDR will end up with the same tag in multiple places. The tag values in this case will not necessarily be the same.

   If this box is not selected and the EDR already includes the tag configured in the node, then the tag in the EDR is modified to have the value defined in the node. If the tag does not exist in the EDR, then the tag/value pair is added to the EDR. This means the tag defined in the node is always included in the EDR..

2. The value in the CDRTag field must be between 1 - 50 characters long.

   It defines the EDR tag to modify or add to the EDR. Any character may be used in this field, however the following rules apply:

   • Use only uppercase A-Z characters.

   • Do not use the characters | and =

   Warning: The use of any of the system generated tags causes the original to remain unchanged and a second tag added to the end of the EDR, as if ForceAppend had been selected.

3. Select the Tag Value source, Options are:

   • Fixed Value - from CDRValue field when this option selected.

   • Profile Value - from profile location when this option selected.

4. If Fixed Value selected, enter the CDRValue field, this must be between 1 - 50 characters long.

   It specifies the EDR value for the defined EDR tag. You may use any character in this field, except the characters | and =.

   Note: If the profile value is selected, this field is grayed out.

5. If Profile Value selected, select the location from the Data Type, Location and Field drop down lists.

   Note: If the fixed value is selected, these fields are grayed out.

6. Click Save.

This node has one entry and two exits. The number of exits cannot be changed.

Follow these steps to edit the node configuration.

1. Select the Operation Type option:

   • Add Entry

   • Update Entry

   • Remove Entry

   Result: The field availability changes as listed:

   For Add Entry:

   • Ordered Prefix Tree fields

   • Number Source fields

   For Update Entry:

   • Ordered Prefix Tree fields

   • Entry to be Updated/Removed fields

   • Number Source fields

   For Remove Entry

   • Ordered Prefix Tree fields

   • Entry to be Updated/Removed fields

2. In the Ordered Prefix Tree area, using the drop down lists, select the Prefix Tree.

3. For Update or Remove options, in the Entry to be Updated/Removed area, using the drop down lists, select the required Prefix Tree entry.

4. For Add or Update options, in the Number Source area, using the drop down lists, select the entry value to use.

5. Click Save.

Note: The list of data types is fixed at installation time for each feature node or screen.

Further reference:

• For information about profile blocks (data type, location, and field) and how to use them, see Profile Blocks and Tags.

The primary tag lists are configured in the SMS > Services > ACS Service > Configuration > Profile Tag Details and Profile Tag Mapping tabs (see ACS User's Guide, Profile Tag Details for more information).

This node has one entry and five exits. The number of exits cannot be changed.

Exits 2 through 4 are all types of "Error".

Follow these steps to edit the node configuration.

1. From the Source Primary Tag drop down list, select the limitation to use.

   Note: The available limitation types for this feature node are:

   • Limited Ordered Prefix Tree

   • Limited Number String

2. From the drop down lists in the Number Source area, select the Source Data Type, Location and Field containing the number to compare against the selected limitation type.

3. Click Save.

Note: The list of data types is fixed at installation time for each feature node or screen.

Further reference:

• For information about profile blocks (data type, location, and field) and how to use them, see Profile Blocks and Tags.

The primary tag lists are configured in the SMS > Services > ACS Service > Configuration > Profile Tag Details and Profile Tag Mapping tabs (see ACS User's Guide, Profile Tag Details for more information).

This node has one entry and four exits. The number of exits cannot be changed.

Follow these steps to edit the node configuration.

1. Select the Play Announcement check box to play the capacity result.

   Result: The Play Capacity Announcement Set and Announcement Entry fields become available and the Save button becomes unavailable.

2. Select the Prefix Tree Type.

   Result: If you selected:

   • Normal, the Source fields in the Source Prefix Tree area and the Target fields in the Capacity Storage area become available. Go to step 4.

   • Limited Order, in addition, the Capacity Type options and the rest of the fields in the Source Prefix Tree area become available. Go to step 3.

3. Select the Capacity Type option to use for capacity calculations:

   • Entries count - the number of entries available,

   • Entries left - the number of entries used, or

   • Capacity - the maximum number of entries for the tree.

4. In the Source Prefix Tree area select the source limited ordered prefix tree to query using the Source drop down lists.

5. If you selected Limited Order:

   • From the Limit drop down lists, select where the limit (value of the maximum capacity of prefix trees) is stored.

   • From the Alternate Limit drop down lists, select an alternate location if the limit is empty (optional fields).

6. In the Capacity Storage area, using the drop down lists, select the capacity store target.

7. In the Play Capacity area, select the announcement to play for the selected capacity type.

   Result: The Save button becomes available.

8. Click Save.

Note: The list of data types is fixed at installation time for each feature node or screen.

Further reference:

• For information about profile blocks (data type, location, and field) and how to use them, see Profile Blocks and Tags.

• The primary tag lists are configured in the SMS > Services > ACS Service > Configuration >Profile Tag Details and Profile Tag Mapping tabs (see ACS User's Guide, Profile Tag Details for more information).

This node has one entry and three exits. The number of exits cannot be changed.

When collecting date and /or time from a subscriber, there are defaults used if the complete date or time are not entered.

The defaults for dates are:

• The month value must be entered by the subscriber.

• Missing year is substituted by the current sysdate year value.

• Missing day is substituted by "01".

• When time only collected, date is defaulted to "01/01/1970"

The defaults for times are:

• The hour value must be entered by the subscriber.

• Missing minutes are substituted by "00".

• Missing seconds are substituted by "00".

• When date only collected, time is defaulted to "00240000".

To configure User Interaction:

1. Select User Interaction for the source profile tag.

2. Select what data is to be requested from the subscriber. The options are:

   • Collect Date Only

   • Collect Time Only

   • Collect Date + Time

   Result: The relevant date/time fields are available or grayed out.

3. Select Maximum number of retries from the scroll box.

   Notes:

   • Each announcement also has a number of allowed retries, collectively these may be greater than the Maximum number of retries.

   • If there is a timeout, or an invalid date or time selected by the user, the Retry prompt is played to invite the user to provide another date or time.

   • After the announcement Repetition or Maximum number of retries failures, the feature node branches to Error.

   • When the Collect Date + Time option has been selected and the date is valid before running out of allowed retries, then the number of retries for the time selections are set to the Maximum number of retries value.

4. For the option:

   • Collect Date Only: Follow the procedure for Configuring the date only interaction.

   • Collect Time Only: Follow the procedure for Configuring the time only interaction.

   • Collect Date + Time:

     1. Follow the procedure for Configuring the date only interaction.

     2. Follow the procedure for Configuring the time only interaction.

5. Follow the steps for Target Selection.

6. Click Save.

To configure Profile Tag:

1. Select ProfileTag for the source profile tag..

2. Select the Source Profile Tag from the Data Type, Location and Field drop down lists.

3. Select the date and time format from the Source Tag Mask drop down list.

4. Follow the steps for Target Selection.

5. Click Save.

Note: The list of data types is fixed at installation time for each feature node or screen.

Further reference:

• For information about profile blocks (data type, location, and field) and how to use them, see Profile Blocks and Tags.

• The primary tag lists are configured in the SMS > Services > ACS Service > Configuration >Profile Tag Details and Profile Tag Mapping tabs (see ACS User's Guide, Profile Tag Details for more information).

This node has one entry and three exits. The number of exits cannot be changed.

Follow these steps to edit the feature node.

1. The Type of Digits to Collect field is only relevant if you are going to select CC Pending Termination Number from the Buffer Field list. See Step 2.

   If relevant, select a value for this field; otherwise ignore it.

2. From the lists in the Buffer frame, select the location to use to store the collected digits.

   Notes:

   • If you want to copy the type of digits data to Pending TN Type, select the Pending Termination Number buffer.

3. From the Main Announcement frame, select:

   • The announcement set that contains the main announcement you want to play to the caller from the Announcement Set list.

   • The announcement to play from the Announcement Entry list.

4. Set the Repetition field to the number of times to repeat the main announcement while the system waits for the caller to take an action. If set to zero, the announcement will be repeated for the length of the duration set.

5. Set the Duration field to the length of time in seconds that the announcement is to be played. If set to zero, the announcement will be played for its full length.

6. The retry announcement contains the announcement you want to play to the caller if the number of digits collected is not within the range specified.

   In the Retry Announcement frame, select the:

   • Announcement Set that contains the retry announcement.

   • Announcement Entry for the retry announcement you want to play.

   Then set:

   • Repetition to the number of times to repeat the retry announcement.

   • Duration to the length of time, in seconds, that the retry announcement is to be played.

7. In the Number of Retries field, set the number of times that the feature node will attempt to collect data from the caller, before routing the call to the Not Updated branch. This value may be between 0 and 10.

8. In the Minimum Number of digits field, set the minimum number of digits that must be collected. The value set must be between 1 and 32.

   The minimum number of digits must be less than, or equal to, the maximum number of digits.

9. In the Maximum Number of digits field, set the maximum number of digits that must be collected. The value set must be between 1 and 32.

   The maximum number of digits must be greater than, or equal to, the minimum number of digits.

10. (Optional) To include a prefix before the digits collected value, enter the prefix in the Digit Prefix field.

    The prefix may be up to 32 valid characters. Valid characters include 0-9, A-F.

11. From the Cancel Character options, select the character that the caller can use to cancel the digit collection.

    The switch on the answering device is used by default.

12. From the End Character options, select the character that the caller can use to indicate the end of the digit collection.

    The switch on the answering device is used by default.

13. (Optional) To check that the collected digits are within the TN ranges for this client, select the Verify Against TN Ranges? check box.

    This will check the termination number range rules set up for this customer (through the New or the Edit Customer screen in ACS) and verify according to the rules set. For more information, see the discussion on Adding customers in ACS User's Guide.

14. Click Save.

    Note: The Save button becomes available when you have entered all the required information.

    Result: The feature node data will be saved.

Note: The announcement set and announcement entry lists are populated with data that is specified using the Announcements tab of the ACS Configuration screen.

For more information about configuring announcement sets and announcement entries, see the Announcements tab of the ACS Configuration screen.

This node has one entry and three exits. The number of exits cannot be changed.

Follow these steps to edit the feature node.

1. Select the Type of Digits to Collect from the drop-down list. The type may be:

   • Off Net

   • On Net

   • Speed Dial

   • Service Number

   • CLI

2. From the Main Announcement frame, select the Announcement Set that contains the main announcement you want to play to the caller.

   Result: The Announcement Entry drop-down box will become available.

3. From the Announcement Entry drop-down list, select the main announcement you want to play to the caller.

4. Set the Repetition field to the number of times to repeat the main announcement while the system waits for the caller to take an action. If set to zero, the announcement will be repeated for the length of the duration set.

5. Set the Duration field to the length of time in seconds that the announcement is to be played. If set to zero, the announcement will be played for its full length.

6. The retry announcement contains the announcement you want to play to the caller if the number of digits collected is not within the range specified.

   In the Retry Announcement frame, select one of the following as described in steps 2 - 5:

   • Announcement Set which contains the retry announcement

   • Announcement Entry for the retry announcement you want to play

   • Set the Repetition to the number of times to repeat the retry announcement

   • Set the Duration to the length of time, in seconds, that the retry announcement is to be played.

7. In the Number of Retries field, set the number of times that the node will retry collecting data from the caller (after an initial failure), before routing the call to the Not Updated branch. This value may be between 0 and 10.

8. In the Minimum Number of digits field, set the minimum number of digits that must be collected. This box accepts values between 1 and 32.

   The minimum number of digits must be less than, or equal to, the maximum number of digits.

9. In the Maximum Number of digits field, set the maximum number of digits that must be collected. This box accepts values between 1 and 32. The maximum number of digits must be greater than, or equal to, the minimum number of digits.

10. If a prefix is to be included before the digits collected, enter this in the Digit Prefix field.

    The prefix may be up to 32 valid characters. Valid characters include 0-9, A-F.

11. From the Cancel Character options, select the character which the caller can use to cancel the digit collection.

    The default option will use the switch on the answering device.

    Notes:

    • If the caller uses this digit and the maximum number of retries has not been met, it will return the caller to the retry prompt and add one to the retry count.

    • If the caller uses this digit and the maximum number of retries has been met, it will take the Not Updated branch.

12. From the End Character options, select the character which the caller can use to indicate the end of the digit collection.

    The default option will use the switch on the answering device.

13. If you want to check that the collected digits are within the TN ranges for this client, tick the Verify Against TN Ranges? check box.

    This will check the Termination Number Range Rules set up for this customer (via the New/Edit Customer screen in ACS) and verify according to the setting. For more information, refer to Adding customers in the ACS Customer screen.

14. Click Save.

    Note: Save is not available until all the required information has been selected or entered.

    Result: The node data will be saved.

Note: The announcement set and announcement entry lists are populated with data that is specified using the Announcements tab of the ACS Configuration screen.

For more information about configuring announcement sets and announcement entries, see the Announcements tab of the ACS Configuration screen.

This node has one entry and three exits. The number of exits cannot be changed.

Follow these steps to edit the Collect Digits to Sub-Tag node.

1. From the Main Announcement area, select the Announcement Set that contains the main announcement you want to play to the caller. The main announcement will be played to prompt for digits to enter into a sub-tag.

   Result: The Announcement Entry drop-down box will become available.

2. From the Announcement Entry drop-down list, select the main announcement you want to play to the caller.

3. Set the Repetition field to the number of times to repeat the main announcement while the system waits for the caller to take an action. If set to zero, the announcement will be repeated for the length of the duration set.

4. Set the Duration field to the length of time in seconds that the announcement is to be played. If set to zero, the announcement will be played for its full length.

5. The retry announcement contains the announcement you want to play to the caller if the sub-tag value is not within the range specified in step 7.

   In the Retry Announcement area, select one of the following as described in steps 1 - 4:

   • Announcement Set which contains the retry announcement

   • Announcement Entry for the retry announcement you want to play, and set the

   • Repetition to the number of times to repeat the retry announcement

   • Duration to the length of time, in seconds, that the retry announcement is to be played.

6. In the Number of Retries field, set the number of times that the node will attempt to collect data from the caller, before routing the call to the Not Updated branch. This value may be between 0 and 10.

7. In the Minimum Sub Tag Value and Maximum Sub Tag Value fields, set the minimum and maximum sub-tag value to be collected. This is the range of values that the user can set, for example, speed dial numbers between 10 and 20.

8. Click Save.

   Note: Save is not available until all the required information has been selected or entered.

Note: The announcement set and announcement entry lists are populated with data that is specified using the Announcements tab of the ACS Configuration screen.

For more information about configuring announcement sets and announcement entries, see the Announcements tab of the ACS Configuration screen.

This node has one entry and five exits. The number of exits cannot be changed.

This table describes how the field contents are compared when the two field lengths are equal.

Follow these steps to edit the node configuration.

1. Select the profile field type for the comparison from the Type drop down list.

   Note: Not all the list items are valid for comparison. See the Content comparison rules table.

2. Using the drop down lists in the Profile Field A area, select the first profile field to compare.

3. Using the drop down lists in the Profile Field B area, select the other profile field to compare.

4. Click Save.

Note: The list of data types is fixed at installation time for each feature node or screen.

Further reference:

• For information about profile blocks (data type, location, and field) and how to use them, see Profile Blocks and Tags.

The primary tag lists are configured in the SMS > Services > ACS Service > Configuration > Profile Tag Details and Profile Tag Mapping tabs (see ACS User's Guide, Profile Tag Details for more information).

This node has no entries or exits, as it is not connected to other nodes within a control plan.

Follow these steps to add a note to a control plan.

1. Drag the node on to the canvas and drop into place.

   The Control Plan Notes feature node icon appears in the canvas.

2. Double click the Control Plan Notes feature node icon.

   The Edit Comments window displays.

3. Click inside the editable area and type the text that is to appear in the control plan note.

   Note: All text appears in the note exactly as it is entered. To ensure that text does not appear in a long line, break it up with manual line breaks.

4. Click Ok.

   The text appears in the note box.

This table lists the types of conversions and the corresponding conversion rules used by the Copy feature node to convert profile field data to and from character strings.

This node has one entry and two exits. The number of exits cannot be changed.

The Include PendingTN Type check box appears when the Source Field selection is CC Pending Termination Number, as shown in this example of part of the screen.

Description of the illustration cpeconfigurecopypendingtn_2-4-3.jpg

The Use Source as Prefix check box appears when the Source Field and Target Field selections are of type string or number string, as shown in this example of part of the screen.

Description of the illustration 100689.png

The Use Stored Sub-Tag check box appears when the Target Field selection contains sub-tags (for example, the Speed Dial Block contains the sub-tag list of speed dial numbers. For more information, see Sub-tags), as shown in this example of part of the screen.

Description of the illustration cpeconfigurecopyusestoredsub-tag_2-4-3.jpg

In this example, earlier in the control plan, the sub-tag (e.g. the speed dial number, let's say 50) has been specified using the Collect Digits to Sub-tag node. The telephone number, e.g. 08001234567, to associate with it has then been stored in the CC Pending TN buffer using the Collect Digits to Pending TN node. Using the Copy node, that number is copied into the Speed Dial block, so that the speed dial number 50 is set to call 08001234567.

Follow these steps to configure the Copy node.

1. From the drop down lists in the Source Profile area, select the source stored data location.

   Notes: If you set a customer-specific profile, the profile set in this field must belong to the customer who will be running the Control Plan.

   If the Control Plan is owned by the Boss user:

   • the profile must be set to Control Plan, or

   • a customer id must be specified at an earlier point in the Control Plan.

2. From the drop down lists in the Target Profile area, select the target that the data is to be copied to.

3. If the Include Pending TN Type check box is displayed, then either:

   • tick: the node will save the Pending TN to the profile with the Pending TN Type prefixed.

   • Clear: the node will save just the Pending TN to the profile.

4. If the Use Source as Prefix check box is displayed, then either:

   • tick: the node will prefix the target value with the source value.

   • Clear: the node will copy the source value to the target value.

5. If the Use Stored Sub-Tag check box is displayed, select the required target field format from the Target sub-tag Storage Format drop down list. The node will save the sub-tag value with the required format in the target field.

6. Click Save.

   Note: Save is not available until all the required information has been selected or entered.

Note: The list of data types is fixed at installation time for each feature node or screen.

Further reference:

• For information about profile blocks (data type, location, and field) and how to use them, see Profile Blocks and Tags.

The primary tag lists are configured in the SMS > Services > ACS Service > Configuration > Profile Tag Details and Profile Tag Mapping tabs (see ACS User's Guide, Profile Tag Details for more information).

For information about using the Call Context Profile, refer to ACS Buffers.

This node has one entry and four exits. The number of exits cannot be changed.

Follow these steps to configure the node.

1. In the Hunting list panel set the hunting list to be copied, to copy:

   • the hunting list chosen by the hunting planner, select the Use planner list option

   • a specified list, select the Use list below option and type the hunting list name in the List name box.

2. If required, set the override for the No answer timeout. To use:

   • the current No Answer Timeout value, ensure Leave unchanged is selected

   • the highest timer within the hunting list, select the Use max from list option, or

   • a value from a profile tag, select the Read from profile option and set the Data Type, Location and Field holding the timer using the drop down lists.

   Note: If you selected Read from profile and the node cannot find the specified profile field, then the No Answer Timeout will not be overridden.

3. Click Save.

Note: The list of data types is fixed at installation time for each feature node or screen.

Further reference:

• For information about profile blocks (data type, location, and field) and how to use them, see Profile Blocks and Tags.

The primary tag lists are configured in the SMS > Services > ACS Service > Configuration > Profile Tag Details and Profile Tag Mapping tabs (see ACS User's Guide, Profile Tag Details for more information).

This table lists the delimiters allowed between entries in the input string.

Note: Delimiter characters may be combined, for example, so that spaces and commas can be used between entries.

This node has one entry and three exits. The number of exits cannot be changed.

Follow these steps to configure the node.

1. From the drop down lists in the Source String area, select the profile tag field containing the string you want to use to create the prefix tree.

2. From the drop down lists in the Destination Profile area, select the profile tag field where the prefix tree will be stored.

3. To limit the allowable entries in the source string, tick the Use Limitations check box. Then, from the Limitation Primary Tag drop down list, select the profile tag field to use.

   Note: The Product Type profile will be used if available, otherwise the Service Provider profile will be used.

4. Click Save.

Note: The list of data types is fixed at installation time for each feature node or screen.

Further reference:

• For information about profile blocks (data type, location, and field) and how to use them, see Profile Blocks and Tags.

The primary tag lists are configured in the SMS > Services > ACS Service > Configuration > Profile Tag Details and Profile Tag Mapping tabs (see ACS User's Guide, Profile Tag Details for more information).

The shortcut keys to add a Day of Week node are Alt+W.

The Day of Week node has one entry and may have 2 through 7 exits. Each exit is mapped to a day of week range, and must be connected to an appropriate node. You can configure the number of exits within this range as required, using the Edit Node Exits option on the shortcut menu. See Editing Feature Node Exits.

Follow these steps to configure the day of week node.

1. Edit the node exits to add up to another five exits as required to accommodate the dates you are planning to configure. See Editing node exits for details.

2. From the Timezone Type field, select the timezone to use.

   If you select Explicit Unix TZ, you must select a specific region from the Unix Timezone field.

   Note: The GMT+ and GMT- time zone names adhere to POSIX Unix conventions, which use positive (+) signs for West of Greenwich and negative (-) signs for East of Greenwich. For example, GMT+4 corresponds to 4 hours behind GMT.

   For more time zone information, see Time Zones.

3. Select the Default branch in the box on the left of the screen. Any calls made on a day not specified in an allocated range route down the default branch.

4. Map the required day of week ranges to the appropriate exits, as detailed below.

5. Once all the data is correct, click Save.

   The Save button will not be available if a range has not been accepted, or if the ranges overlap.

Follow these steps to map a day of week range to an exit, using the Configure Day of Week screen.

1. Click Add Range.

   To the left of the Branch field, the drop-down lists will be populated.

2. Select the day required in each list, to show the first and last day in the range. A range of:

   • Wed – Wed affects only calls made on Wednesday of each week.

   • Mon – Thur affects calls made on any day from Monday to Thursday.

3. Note that the range may not overlap any existing range. The ranges specified do not need to include all possibilities. Any calls made on a day not specified in an allocated range routes down the default branch.

4. Select the branch that is to be mapped to the specified range. Calls made within that range are routed down the exit selected in the branch list.

   It is possible to have several ranges routing down the same branch or to have branches that no calls will ever take.

5. Click Change.

   Result: The branch/range mapping will appear in the display field.

   To delete a mapping, select the entry and click Delete Range.

The shortcut keys to add a Day of Year node are Alt+Y.

The Day of Year node has one entry and may have 2 through 20 exits. Although this node accepts up to 20 exits, it is recommended that this number is restricted to a maximum of 10, due to the width restraints of the node. The default number of exits is 2.

There are three types of exit:

• A specific date or date range (which can be mapped to any free branch)

• A default branch (if the current date is not specified in any of the dates or date ranges, this branch will be followed)

• Any holiday in set (if it matches any of the dates in the chosen set that have not been specifically assigned a branch, this branch will be followed)

You cannot map two dates or date ranges to the same branch. Ensure you do not specify the same day twice (either in a holiday set or on a specified branch), as your control plan data will not compile successfully.

If you do not want to use the Any Holidays branch, set it to the same exit as the default.

You can configure the number of exits within this range as required, using the Edit Node Exits option on the shortcut menu. See Editing Feature Node Exits.

Dates may be entered in this node in two forms, as one of the following:

• Holiday entries as entered in a specified holiday set

• Explicit date ranges

If a date is included as a holiday set, but is not specifically assigned a branch, the call is routed down the Any Holiday exit.

For calls where there is no match found to any specified date, the call is routed down the default exit.

Follow these steps to configure the day of year node.

1. Edit the node exits to add up to another eighteen exits as required to accommodate the dates you are planning to configure. See Editing node exits for details.

2. From the Timezone Type box, select the timezone you want to use.

   If you select the Explicit Unix TZ option, you must choose a specific region from the Unix Timezone box.

   For more Time zone information, see Time Zones.

3. Specify the exit for dates which match a date within the specified Holiday Set, but do not match a date entry with a specific branch assigned to it.

4. Enter the holiday details by either:

   • specifying each date or date range explicitly, or

   • mapping the entries from a holiday set to the appropriate branches.

5. More information about entering dates is provided on the next two pages.

6. Select the Default branch in the box on the left of the screen. Any calls made on a day not specified in an allocated range route down the default branch.

7. Once all the data is correct, click Save.

   Note: The Save button will not be available if a range has not been accepted, or if the ranges overlap.

Follow these steps to add holiday set entries, using the Configure Day of Year Node screen.

1. Select the holiday set required from the drop-down box.

2. If the selected holiday set has:

   • More than one entry in it, you can add them all by clicking Add Whole Set.

   • Only one entry or if you only want to add the first entry from the set, click Add Entry.

3. Result: The chosen entries will be added to the display list.

4. In the list box below the display area, select the holiday entry that is required.

5. In the Branch field, select the branch the specified days should route to.

6. Click Change.

   Result: The selected default entry in the display area will be changed to the holiday entry and branch selected.

7. Repeat steps 3 and 4 until all the holiday entries have been mapped to different branches. (They must be mapped to different branches or the control plan will not compile.)

8. Click Save.

Follow these steps to add explicit date ranges, using the Configure Day of Year Node screen.

1. Click Add Entry.

   Result: A default entry will be added to the display list, as a selected entry.

2. Select the (Explicit Date Range) option in the Holiday Entry selection box.

   Result: The Start and End Date fields will become available.

3. Select the date range required.

   Note: The date ranges are inclusive. For example, a date range of January 1 to January 12 will route calls made on 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11 and 12 January down the selected branch.

   To specify a single date, set both the Start and End Date fields to the same day.

4. Select the branch to be taken by calls within that range.

5. Click Change Entry.

   Result: The selected default entry in the display area will be changed to the explicit date range and branch selected.

6. Select a holiday data set. This information will not be used, but is required for the Control Plan data to compile correctly.

7. Click Save.

This node has one entry and two exits. The number of exits cannot be changed.

Follow these steps to edit the node configuration.

1. In the Profile Field area, using the drop down lists, select the profile field to delete.

2. Click Save.

Note: The list of data types is fixed at installation time for each feature node or screen.

Further reference:

• For information about profile blocks (data type, location, and field) and how to use them, see Profile Blocks and Tags.

The primary tag lists are configured in the SMS > Services > ACS Service > Configuration > Profile Tag Details and Profile Tag Mapping tabs (see ACS User's Guide, Profile Tag Details for more information).

This node has one entry and may have 2 through 20 exits. You can configure the number of exits within this range as required, using the Edit Node Exits option on the shortcut menu. See Editing Feature Node Exits.

Follow these steps to add a prefix to the node data, using the Configure Dialled Number screen.

1. Edit the node exits to add up to another eighteen exits as required to accommodate the numbers you are planning to configure. See Editing node exits for details.

2. Click Add Prefix.

   Result: You see an undefined prefix displayed in the list box to the left of the button.

3. Enter the prefix into the field to the left of the Branch field, as shown below.

   
   Description of the illustration cpeconfigurediallednumbernodeprefixfield_2-4-2.jpg

   To determine the routing, prefixes (or the entire number) must be entered into the node data. The routing will be based on the best match between the dialed number and the prefixes that are in the node data. The dialed number list takes up to 1500 characters in total, which limits the number of entries in the list. It is recommended that a maximum of 50 entries be made in the list.

   Example: If 0800447732 is dialed and the prefixes entered into the node data are 0800, 0900, 0800447 and 080044, the call will be routed down the branch associated with 0800447 because this is the best match found for the number dialed.

4. In the Branch field, select the branch down which calls whose dialed number best matches this prefix are to route. When the entry is correct, click Change.

5. Repeat steps 1-4 until you have specified the dialed number ranges required.

6. From the Default box, select the branch that dialed numbers that do not match any prefix entered into the node will route down.

7. Click Save.

The shortcut keys to add a Disconnect Call node are Alt+R.

This node has one entry and one exit. The number of exits cannot be changed.

To edit the Disconnect Call node, enter the value that is to be sent to the switch in the ReleaseCall operation. The value entered determines the tone or message played to the caller on disconnection of the call.

The cause value defaults to 31. Other values are listed in ITU-T recommendation Q850.

Some examples are:

This node has one entry and 2 through 20 exits. Although this node accepts up to 20 exits, it is recommended that this number is restricted to a maximum of 10. You can configure the number of exits within this range as required, using the Edit Node Exits option on the shortcut menu. See Editing Feature Node Exits.

Only one exit at a time may be used, and all calls will be routed to the active exit.

Follow these steps to change the exit to which the switch points.

1. Edit the node exits to add up to another eighteen exits as required to accommodate the branches you are planning to configure.. See Editing node exits for details.

2. Use the arrows to change the exit number displayed.

   Result: As the exit number is changed, the diagram to the right will graphically demonstrate the exit to which the switch is set.

3. Click Save.

The shortcut keys to add an End node are Alt+E.

This node has one entry and no exit. It is possible to attach several branches of the control plan to the entry of a single End node.

This node requires no configuration data. You may change the Node name, if required.

This node has one entry and two exits. The number of exits cannot be changed.

Follow these steps to configure the Event Branching node.

1. From the Counter list, select the counter that is to be monitored by the node.

2. Counters are configured through the Event Counters tab on the ACS Resources screen. For more information, see ACS User's Guide

3. From the Operation list, select the type of comparison that is to be made.

4. From the Counter or Constant list, select a statistics counter or (Compare with Constant Value). If comparing with a constant value, enter the value in the field above the list field.

5. Click Save.

This node has one entry and one exit. The number of exits cannot be changed.

Follow these steps to configure the Event Counting node.

1. Select the event counter from the drop-down list to which this Event Counting node is counting. Event counters are set up in the Event Counters tab on the ACS Resources screen.

2. In the Increment field, enter the number that the counter will increment each time a call is routed through the node.

   The increment value must be between -99999 and 999999.

3. Click Save.

This node has one entry and one exit. The number of exits cannot be changed.

Follow these steps to configure the Event Setting Node.

1. Select the event counter that is to be reset from the drop-down list.

   Event counters are set up in the Event Counters tab on the ACS Resources screen.

2. Enter the number to which the statistics counter is to be reset. A Statistics Counter may be reset to any value between -99999 and 999999.

3. Click Save.

The shortcut keys to add a Geographical Routing node are Alt+Shift+G.

This node has one entry and may have two through 20 exits. Although this node accepts up to 20 exits, it is recommended that this number is restricted to a maximum of 10. You can configure the number of exits within this range as required, using the Edit Node Exits option on the shortcut menu. See Editing Feature Node Exits.

A geography set is made up of multiple nested geography entries. Each entry is mapped to a unique prefix, and may also be connected to a (or several) region. A region is a group of geography entries. The entries contained in a single region may come from different branches and different nested levels, or may contain whole branches.

Routing may be based on either region or geography entry prefix. A geography entry may only appear once on a branch. That is, it may not appear on two branches.

The routing will be based on the best match between the calling party number (or other selected buffer) and the number prefix that has been set for the region in the Geography tab of the configuration screens.

Follow these steps to add a geographic entry or region to an exit branch.

1. Select the location of the number data from the Source Data Type, Location and Field drop down lists.

2. Select the required geography set from the list. The list will display all the Geography sets that the customer has access to. To the left of the screen is the full tree structure of the geography set. Branches of the tree may be condensed and expanded by:

   • Using the left and right arrow keys

   • Clicking on the and

3. Enter the branch number to which the geographic entry or region is to be routed in the Number field.

   Example:

   
   Description of the illustration cpeconfiguregeographicalbranchspinbox_2-4-2.jpg

4. Select the entry that is to be routed to that branch from the geography tree at the left.

   Notes:

   • You can select the root branch by pressing Alt+S, and navigate around the tree using the arrow keys. You can also select any of the first nine entries by pressing Ctrl and the corresponding number key.

   • To route based on geography regions select the 74 Regions tab.

   • When routing to exit branches using regions the entries that belong to the region will be assigned to the exit branch.

   • It is important to ensure that an entry is only routed to one exit branch.

5. Either press Ctrl+B or click Move to Branch >>. The entry will be added to the tree structure for the specified branch. If a condensed branch of the geography tree is added to the branch sub-tree, the entry selected and all levels below that will be added to the branch sub-tree. To add geography entries to another branch, select a new branch and use Move to Branch >> or << Replace in Set to add and remove geography tree entries.

6. Add entries and regions to all branch exits as required.

7. Select the Default Branch.

8. When you have finished all editing, click Save.

   Note: Save is not available until changes have been made.

Follow these steps to remove Geography Entries from a Branch sub-tree.

1. Select the geography set that is required from the list. The list will display all the geography sets that the customer has access to. To the left of the screen is the full tree structure of the geography set. Branches of the tree may be condensed by:

   • Using the left and right arrow keys

   • Clicking on the and expanded by clicking on the

2. Select the branch to which a geography tree branch is currently routed by entering a number into the Branch field.

3. From the Branch Geo Areas frame, select the entry that is to be removed.

   Note: You can select the root branch by pressing Alt+B, and navigate around the tree using the arrow keys. You can also select any of the first nine entries by pressing Ctrl and the corresponding number key.

4. Either press Ctrl+S or click << Replace in Set.

   Result: The geography entry is replaced in the full geography set tree. This entry may now be added to another branch sub-tree if required.

5. When finished all editing, click Save.

   Note: Save is not available until changes have been made.

Follow these steps to find where a specific telephone number or prefix is in the geography tree.

1. In the Configure Geographical Routing screen, press Ctrl+R to place your cursor into the field next to the Find button.

2. Type the number or prefix you want to search for and press Ctrl+F to activate the Find button.

   Result: The All Geo Areas tree will expand and highlight the best match for your query.

Here is an example control plan containing a Geographical Routing feature node.

This control plan will route calls to different service centers based on where the call originates from (for example, routes to the nearest Pizza shop).

This control plan is triggered when the caller dials a certain termination number (for example 0800 PIZZA).

Description of the illustration cpecontrolplaneditorexamplegeoroutecp_5-0-0.jpg

This node has one entry and two exits. The number of exits cannot be changed.

Follow these steps to configure the node.

1. In the Hunting list area set the hunting list to use from the Hunting List Data Type, Location and Field drop down lists.

2. Set the Timeout. To use:

   • a value from a profile tag, select the Read from profile option and set the Data Type, Location and Field holding the timer using the drop down lists, or

   • a node configured value, select the Use default value option and enter the value in the Default Timeout field.

   Note: If you selected Read from profile and the node cannot find the specified profile field, then the No Answer Timeout will not be overridden.

4. Click Save.

Note: The drop down lists display Limited Order Prefix Tree profiles.

For more information on profile blocks and tags, see ACS User's Guide.

This node has one entry and three exits. The number of exits cannot be changed.

This node requires no configuration data. You may change the Node name, if required.

As an example, assuming that the following hunting configuration data has been placed in a profile block:

0x030020 Hunting Config

SubTags (2):

0x000001 356 Hunting Lists (tag 1):

Hunting List ID 1 (name = 'Hunting List 1'):

Rank 1 termination number:

Digits: 04111222

On network ID: 5

Timeout: 10

Rank 2 termination number:

Digits: 1234

Off network number

Timeout: 20

Hunting List ID 2 (name = 'Hunting list 2'):

Rank 1 termination number:

Digits: 04333444

On network ID: 5

Timeout: 30

Rank 2 termination number:

Digits: 4321

Off network number

Timeout: 40

0x000002 380 Hunting Planner (tag 2):

Time Data 0:

Location pattern: ^7777

CLI pattern: ^77777

Time of Day

Start Time: 04:15

End Time: 08:17

Hunting List ID: 1

Time Data 1:

Location pattern: ^6666

CLI pattern: ^76666

Day of Week and Time of Day

Start Time: Sunday 05:00

End Time: Monday 06:00

Hunting List ID: 2

Time Data 2:

Location pattern: ^5555

CLI pattern: ^75555

Day of Year and Time of Day

Start Time: 28 December 01:12

End Time: 29 December 02:15

Hunting List ID: 1

Default Hunting List ID: 1

When the node is used for the first time in a call, it works out which hunting list to use from the hunting planner information, based on time of day, and other factors. The hunting list is an ordered list of termination numbers to try, and a no answer timeout. So, the first list in the example above says try private number 04111222 on network 5 for 10 seconds. The second list says try public number 1234 for 20 seconds.

Each time the get hunting number node is executed, it puts a new number from the list in the pending termination number buffer and the corresponding timeout value in the no answer timer variable in call context. If the end of the list is reached, the get hunting number node exits down branch 2.

The idea is that there is a loop back from the no answer branch of an attempt terminate to pending TN node to a Get Hunting Number node.

This feature node has one entry and one exit. The number of exits cannot be changed.

This node requires no configuration data. You may change the Node name, if required.

This node has one entry and three exits. The number of exits cannot be changed.

Follow these steps to configure the Load Profile node.

1. From the Main Announcement area, select the Announcement Set that contains the main announcement you want to play to the caller.

   Result: The Announcement Entry drop-down box will become available.

2. From the Announcement Entry drop-down list, select the main announcement you want to play to the caller.

   Note: The announcement set and announcement entry lists are populated with data that is specified using the Announcements tab of the ACS Configuration screen.

   For more information about configuring announcement sets and announcement entries, see Announcements.

3. Set the Repetition field to the number of times to repeat the main announcement while the system waits for the caller to take an action. If set to zero, the announcement will be repeated for the length of the duration set.

4. Set the Duration field to the length of time in seconds that the announcement is to be played. If set to zero, the announcement will be played for its full length.

5. The retry announcement contains the announcement you want to play to the caller if the number of digits collected is not within the range specified.

   In the Retry Announcement area, select one of the following as described in steps 1 - 4:

   • Announcement Set which contains the retry announcement

   • Announcement Entry for the retry announcement you want to play, and set the

   • Repetition to the number of times to repeat the retry announcement

   • Duration to the length of time, in seconds, that the retry announcement is to be played.

6. In the Number of Retries field, set the number of times that the node will attempt to collect data from the caller, before routing the call to the Not Updated branch. This value may be between 0 and 10.

7. Using the drop down lists in the Load From Data Type and Load From Location fields, select the Profile block from which information is to be loaded onto the node.

   Note: This lists only the profiles that can be updated. For more information about profile blocks, see Profile Blocks and Tags.

8. Click Save.

   Note: Save is not available until all the required information has been selected or entered.

Note: The list of data types is fixed at installation time for each feature node or screen.

Further reference:

• For information about profile blocks (data type, location, and field) and how to use them, see Profile Blocks and Tags.

The primary tag lists are configured in the SMS > Services > ACS Service > Configuration > Profile Tag Details and Profile Tag Mapping tabs (see ACS User's Guide, Profile Tag Details for more information).

Here is an example of using the Load Profile node to load the customer profile, in order to access the dial-up self management options.

For detailed information on the ACS Management control plan, see the chapter - Dial-up Control Plan Management in ACS.

1. A customer is set up with an 0800 number and the self management screens.

2. The customer phones a number attached to the ACS management control plan.

Here is an example of a Configure Load Profile screen in ACS Management control plan that prompts the caller for a Customer Profile. See the ACS Management Control Plan example in ACS User's Guide to see the entire control plan.

Description of the illustration cpeconfigureloadprofile-customerprofile_2-4-3.jpg

In this example, the caller is prompted to enter their management ID.

This node has one entry and two exits. The number of exits cannot be changed.

Follow these steps to configure the node.

1. In the Value field type the number of iterations for the loop. The value must be between 1 and 1000.

2. Click Save.

This node has one entry and two exits. The number of exits cannot be changed.

Follow these steps to edit the node.

1. In the Modify area, using the drop down lists, select the field to modify.

   Note: ACS normalisation will have already been applied to this number.

2. Type the number of digits that are to be stripped from the front of the number.

   Example: If a value of 2 is entered, 2 digits are removed from the start of the number.

3. Type the number of digits that are to be stripped from the end of the number.

4. Type the characters to prepend to the start of the number.

5. Type the characters to append to the end of the number.

6. Click Save.

Note: The list of data types is fixed at installation time for each feature node or screen.

Further reference:

• For information about profile blocks (data type, location, and field) and how to use them, see Profile Blocks and Tags.

The primary tag lists are configured in the SMS > Services > ACS Service > Configuration > Profile Tag Details and Profile Tag Mapping tabs (see ACS User's Guide, Profile Tag Details for more information).

This node has one entry and 11 exits. The number of exits cannot be changed.

This table describes the function of each field.

Follow these steps to configure the node.

1. Select the required Internal option.

2. Select the required External option.

3. Select the Append URI check box if required.

4. Click Save.

This node has one entry and four exits. The number of exits cannot be changed.

This node requires no configuration data. You may change the node name, if required.

This node has one entry and four exits. The number of exits cannot be changed.

This table describes the function of the field on this screen.

Follow these steps to configure the node.

1. Select the Rule Set from the drop down list of carriers to use for least cost routing.

2. Click Save.

This node has one entry and two exits. The number of exits cannot be changed.

This table describes the function of each field.

Note: The DRA is the destinationRoutingAddress field in the INAP CONNECT and is derived from the pendingTN buffer.

Follow these steps to configure the node.

1. Select the required option.

2. If you selected one of the following options, then in the NOA field, set the NOA:

   • Map with DRA

   • SCCP with GTT

   • SCCP no GTT, or

   • SCCP with GT digits

3. If you selected the MAP Error option then select the map error message to use from the Map Error drop down list.

4. If you selected the TCAP Abort option then in the TCAP Error field, type the cause value.

5. Click Save.

This node has one entry and four exits. The number of exits cannot be changed.

Follow these steps to configure the node.

1. In the Read number translation list from field, select the location in which the number translations are stored. The Control Plan designer must verify that this field contains the correct selection.

   Note: If this number translation has been established by using the ACS > Resource > Number Translations screen, the information will always be in Customer Profile, Sub-field 1.

2. In the Sub-field field, enter the sub-tag that selects a group of number translations. This field entry does not have a default value. See Sub-tags for a definition of sub-tags.

   The list that is stored under the sub-field is a prefix tree data structure, which allows the input number to be quickly looked up and verified.

   Example:

   • Sub-field 1 could be Marketing translations between account codes and phone numbers.

   • Sub-field 2 could be Sales Department quick dial numbers.

3. Select the method of obtaining the number:

   • Retrieve stored number

     Result: The Retrieve number from location and Retrieve number from field fields are activated. Go to Step 4.

   • Prompt and collect number

     Result: The Announcement areas are activated. Go to Step 6.

4. If you selected the Retrieve stored number option, in the Retrieve number from location and Retrieve number from field drop down lists, select the location of the data to retrieve.

5. Go to Step 12.

6. If you selected the Prompt and collect number option, from the Main Announcement area, select the Announcement Set that contains the main announcement you want to play to the caller.

   Result: The Announcement Entry drop-down box will become available.

7. From the Announcement Entry drop-down list, select the main announcement you want to play to the caller.

   Note: All announcements are established in the ACS > Configuration > Announcements screens.

8. Set the Repetition field to the number of times to repeat the main announcement while the system waits for the caller to take an action. If set to zero, the announcement will be repeated for the length of the duration set.

9. Set the Duration field to the length of time in seconds that the announcement is to be played. If set to zero, the announcement will be played for its full length.

10. The retry announcement contains the announcement you want to play to the caller if the digits they enter are not recognised.

    In the Retry Announcement area, select one of the following as described in steps 5 - 9:

    • Announcement Set which contains the retry announcement

    • Announcement Entry for the retry announcement you want to play, and set the

    • Repetition to the number of times to repeat the retry announcement

    • Duration to the length of time, in seconds, that the retry announcement is to be played.

11. In the Number of Retries field, set the number of times that the node will attempt to collect data from the caller, before routing the call to the Not Translated branch. This value may be between 0 and 10.

12. From the Store translated number to Location and Store translated number to Field drop down lists, select where to store the translated number.

13. Click Save.

    Note: Save is not available until all the required information has been selected or entered.

Note: The announcement set and announcement entry lists are populated with data that is specified using the Announcements tab of the ACS Configuration screen.

For more information about configuring announcement sets and announcement entries, see the Announcements tab of the ACS Configuration screen.

The following have been set up in the ACS > Resource > Number Translation screens (list of Sub-field 1 numbers):

The number to translate is compared to the Input Number list.

When a match is found, the matching termination number is stored in the configured location.

This node has one entry and three exits. The number of exits cannot be changed.

The Number Matching feature node allows you to enter one or more search patterns in the Static Pattern List field.

The search patterns are entered using regular expressions. Some characters have special meaning when used in a regular expression; other characters stand for themselves. Under ACS, telephone number matching is customized for patterns of telephone numbers. The "number" character set is represented by digits zero through nine, asterisk, pound sign (hash mark), and the letters A through F.

The control plan compiler notifies you if the pattern entered is invalid.

Special characters

Here are the definitions of special characters used in search patterns.

Examples:

Here are some examples of search patterns.

Follow these steps to configure the node.

1. In the Number to Match frame, using the drop down lists, specify the number to match.

2. Select the pattern list location. If you select:

   • Node dialog, the Static Pattern List field is active.

   • Profile, specify the data type, location, and field.

3. If you selected Node dialog, fill in the Number Match Pattern List field. See Search patterns – Number Matching for a list of example patterns.

   Warning: Do not leave this field empty. If you leave this field empty, exit 2 will be taken, as there is nothing to match against.

   If you selected Profile, select from the drop-down lists:

   • Pattern List Data Type

     Note: Only String data types are accepted. To be able to find a profile with an Integer data type, you must add a Copy node to your control plan just before the Number Matching Node. Configure the Copy node to temporarily change the profile data type from Number to String.

   • Pattern List Location

   • Pattern List Field containing the pattern to match against

4. Click Save.

Note: If any control plan containing Number Matching nodes were exported prior to the profile block functionality being introduced and you import them again, you will need to re-save to allow the control plan to recompile.

Note: The list of data types is fixed at installation time for each feature node or screen.

Further reference:

• For information about profile blocks (data type, location, and field) and how to use them, see Profile Blocks and Tags.

• The primary tag lists are configured in the SMS > Services > ACS Service > Configuration >Profile Tag Details and Profile Tag Mapping tabs (see ACS User's Guide, Profile Tag Details for more information).

This example is based on the configuration screen shown for this node:

• The number to match against is held in the Calling Logical Number field in the call context.

• The search pattern looks for the digits 123, starting in position 3, in an eight digit number.

The exit taken is shown in this table for the various Calling Logical Number examples:

This node has one entry and two exits. The number of exits cannot be changed.

Follow these steps to edit the node configuration.

See the ACS technical Guide, topic acsChassis Normalisation Parameters (SCP) for information on number normalisation.

1. Using the drop down lists in the Number Buffer area, specify the buffer containing the number to normalise.

2. Type the Source NOA value.

3. Click Save.

Note: The list of data types is fixed at installation time for each feature node or screen.

Further reference:

• For information about profile blocks (data type, location, and field) and how to use them, see Profile Blocks and Tags.

The primary tag lists are configured in the SMS > Services > ACS Service > Configuration > Profile Tag Details and Profile Tag Mapping tabs (see ACS User's Guide, Profile Tag Details for more information).

This node has one entry and three exits. The number of exits cannot be changed.

Follow these steps to edit the PIN Authorisation node.

1. From the Main Announcement area, select the Announcement Set that contains the main announcement you want to play.

   Result: The Announcement Entry drop-down box will become available.

2. From the Announcement Entry drop-down list, select the main announcement you want to play to the caller to request a PIN.

3. Set the Repetition field to the number of times to repeat the main announcement while the system waits for the caller to take an action. If set to zero, the announcement will be repeated for the length of the duration set.

4. Set the Duration field to the length of time in seconds that the announcement is to be played. If set to zero, the announcement will be played for its full length.

5. The retry announcement contains the announcement you want to play to the caller if an incorrect PIN is entered.

   In the Retry Announcement area, select one of the following as described in steps 1 - 4:

   • Announcement Set which contains the retry announcement

   • Announcement Entry for the retry announcement you want to play, and set the

   • Repetition to the number of times to repeat the retry announcement

   • Duration to the length of time, in seconds, that the retry announcement is to be played.

6. In the Number of Retries field, set the number of times that the node will attempt to collect the correct PIN from the caller, before routing the call to the Not Allowed branch. This value may be between 0 and 10.

7. Tick the Access Rights Required check boxes that you wish to give right of access to the information that the node requires. These relate directly to the application in which the PIN was stored.

8. Select the profile blocks in which the information that the node requires is located. A profile block must be selected for each of the PIN, the Access Rights, and the default Access.

   Note: For information about profile blocks, see Profile Blocks and Tags.

9. Click Save.

   Note: Save is not available until all the required information has been selected or entered.

Note: The announcement set and announcement entry lists are populated with data that is specified using the Announcements tab of the ACS Configuration screen.

For more information about configuring announcement sets and announcement entries, see the Announcements tab of the ACS Configuration screen.

The shortcut keys to add a Play Announcement node are Alt+P.

This feature node has one entry and two exits. The number of exits cannot be changed.

Follow these steps to edit the Play Announcement node.

1. In the Main Announcement frame, select the Announcement Set which contains the main announcement to play to the caller.

   Result: The Announcement Entry field becomes available.

2. From the Announcement Entry drop-down list, select the main announcement to play to the caller.

3. Set the Repetition field to the number of times to repeat the main announcement while the system waits for the caller to take an action. If set to zero, the announcement is played for the duration set.

4. Set the Duration field to the length of time, in seconds, that the announcement is to be played. When set to zero, the announcement will be played for its full length.

5. Click Save.

Note: The announcement set and announcement entry lists are populated with data that is specified using the Announcements tab of the ACS Configuration screen.

For more information about configuring announcement sets and announcement entries, see the Announcements tab of the ACS Configuration screen.

Selection keys (digits 0 to 9) to cater for “Forward”, “Backward”, “Select”, and “Exit” operations can be optionally configured to enable scrolling through a prefix tree.

When configured, the announcement is played as a prompt and collect operation. If an incorrect digit is collected, the Invalid Key error branch is taken.

When not configured, the announcement is played as a variable announcement with two parts in the following order:

1. Entry Number

2. Prefix Tree Entry

This node has one entry and nine exits. The number of exits cannot be changed.

Exits 1 through 5 are optional and therefore available only when configured.

This table describes the function of each field.

Follow these steps to edit the node configuration.

1. Tick the Check limitations check box to restrict the maximum number of entries to play to the source prefix tree maximum number of entries.

   Non-selection will allow all the available entries to be played.

2. In the Play Entry area, using the drop down boxes, select the Announcement Set and Announcement Entry for the prefix tree entry announcement to play.

3. In the source Prefix Tree area, using the drop down boxes, select the prefix tree.

4. In the Entry Number to be Played area, using the drop down boxes, select the prefix tree number to play.

5. In the Forward field, enter the unique digit (0 to 9) the caller must enter to use the forward function. This is optional.

6. In the Backward field, enter the unique digit (0 to 9) the caller must enter to use the backward function. This is optional.

7. In the Exit field, enter the unique digit (0 to 9) the caller must enter to use the exit function. This is optional.

8. In the Select field, enter the unique digit (0 to 9) the caller must enter to use the select function. This is optional.

9. In the Menu Timeout field, optionally enter a number of seconds (0 to 99). This is the amount of time to wait for a response from the caller before taking the Timed out exit.

   Note: The lower this value is, the more likely a timeout is going to occur. 0 results in 100% certain timeout.

10. Click Save.

Note: In steps 5 to 8, the digit must be unique for this configuration. Any conflicts will be reported and must be resolved before saving.

Note: The list of data types is fixed at installation time for each feature node or screen.

Further reference:

• For information about profile blocks (data type, location, and field) and how to use them, see Profile Blocks and Tags.

The primary tag lists are configured in the SMS > Services > ACS Service > Configuration > Profile Tag Details and Profile Tag Mapping tabs (see ACS User's Guide, Profile Tag Details for more information).

This feature node has one entry and two exits. The number of exits cannot be changed.

Note: These exit descriptions are specific to the responses received from an Oracle VWSbilling engine. For specific information about how responses from other billing engines map to these exits, see the technical guide for the interface for billing engine being used.

Follow these steps to edit the Play Variable Part Announcement node.

1. From the Main Announcement frame, select the Announcement Set which contains the main announcement you want to play to the caller.

   Result: The Announcement Entry list becomes available.

   Select the main announcement you want to play to the caller from the Announcement Entry drop down list.

2. For each of the variable parts:

   • In the Data Type field, select the profile data type.

   • In the Location field, select the location where the field is stored.

   • In the Field field, select the field to be played.

   • Select the Denormalisation check box, if you wish the number in this field to be denormalized. See ACS Technical Guide, Play Variable Part Announcement Configuration topic , for this node's denormalization rules.

3. Click Save.

   Note: Save is not available until all the required information has been selected or entered.

Note: The announcement set and announcement entry lists are populated with data that is specified using the Announcements tab of the ACS Configuration screen.

For more information about configuring announcement sets and announcement entries, see the Announcements tab of the ACS Configuration screen.

Note: The list of data types is fixed at installation time for each feature node or screen.

Further reference:

• For information about profile blocks (data type, location, and field) and how to use them, see Profile Blocks and Tags.

• The primary tag lists are configured in the SMS > Services > ACS Service > Configuration >Profile Tag Details and Profile Tag Mapping tabs (see ACS User's Guide, Profile Tag Details for more information).

This node has one entry and two exits. The number of exits cannot be changed.

Follow these steps to edit the node configuration.

1. Using the drop down lists in the Number String area, select the source prefix tree.

2. Using the drop down lists in the Number Source area, select the ACS number buffer containing the number to compare with the prefix tree.

3. Click Save.

Note: The list of data types is fixed at installation time for each feature node or screen.

Further reference:

• For information about profile blocks (data type, location, and field) and how to use them, see Profile Blocks and Tags.

The primary tag lists are configured in the SMS > Services > ACS Service > Configuration > Profile Tag Details and Profile Tag Mapping tabs (see ACS User's Guide, Profile Tag Details for more information).

This node has one entry and three exits. The number of exits cannot be changed.

Follow these steps to edit the node configuration.

1. In the Prefix Tree area, using the drop down boxes, select from the list of prefix trees.

2. In the Number Source area, using the drop down boxes, select the source for the number to match.

3. If you want to temporarily store a matched number in a specified field so that the node doesn't change the prefix tree:

   1. Tick the Enabled check box in the Use Selected Entry area.

   2. Then use the drop-down lists in the Selected Entry area to specify where to store the number.

4. Click Save.

Note: The list of data types is fixed at installation time for each feature node or screen.

Further reference:

• For information about profile blocks (data type, location, and field) and how to use them, see Profile Blocks and Tags.

The primary tag lists are configured in the SMS > Services > ACS Service > Configuration > Profile Tag Details and Profile Tag Mapping tabs (see ACS User's Guide, Profile Tag Details for more information).

If there is more than one entry in the prefix tree that requires processing then the Prefix Tree Entry Extraction node should be set up in a loop in the control plan. If no external data will be supplied to the Prefix Tree Entry Extraction node, then the following additional nodes will be required in the control plan:

• Set feature node

• Loop Limit feature node

• Profile Counting feature node

This process describes how a loop can be used to process multiple entries from the prefix tree specified in the Prefix Tree Entry Extraction (PTEE) node in the control plan.

1. The Set node is used to initialize the first entry position for the PTEE node. This means it must be placed in the control plan before the PTEE node.

2. The PTEE node will extract the initial entry and follow the More Entries path (if more entries exist).

3. Following any required processing, the Loop Limit node will be checked to ensure the maximum number of iterations has not been reached and its counter will be incremented.

4. The Profile Counting node must be placed after the Loop Limit node in the control plan. It will increment the entry position to be used by the PTEE node.

5. The PTEE node will extract the entry indicated by the Profile Counting node and if more entries exist it will exit through the More Entries path.

6. This processing will continue until there are no more entries in the prefix tree or the loop limit is reached. The loop will then be exited following any required processing.

This node has one entry and four exits. The number of exits cannot be changed.

This table describes the function of each field.

Follow these steps to configure the node.

1. From the Source Prefix Tree area, using the drop down boxes, select the prefix tree.

2. From the Entry Position to be Extracted area, using the drop down boxes, select the prefix tree number to extract.

3. From the Destination Profile Field area, using the drop down boxes, select the destination profile field for the extracted data.

4. Click Save.

For more information about profile blocks (data type, location, and field) and how to use them, see Profile Blocks and Fields.

For more information about profile field configuration, see the discussion on profile tag configuration in NCC Advanced Control Services User's Guide.

This node has one entry and up to eight exits depending on which availabilities the user configures for the selected query location.

Exits 1 through 4 are determined by the system and cannot be changed.

Note: Exits 5 through 8 will be in the order configured, and therefore not necessarily in the order shown here.

Follow these steps to edit the node configuration.

1. From the drop down lists in the Presence Entity panel, select the Data Type, Location and Field where the presence entity name or number is held.

   Note: The selected Field must be of type STRING.

2. If required, set the Domain Name field to the name of the domain to append to the presence entity name or number.

   Note: The domain will not be appended to the presence entity if it is already present in the Field selected in the Presence Entity panel.

3. From the drop down lists in the Presence Domain panel, select the Data Type, Location and Field that identifies the presence query chassis action protocol. The selected Field must be of type INTEGER.

   Note: Currently only the SIP protocol is supported.

4. Set the action to be taken if the presence domain cannot be found. Select:

   • Error - to report an error, or

   • Use default below - to use the default presence domain. Select the default presence domain from the drop down list.

5. Set the Location to query for the presence entity.

6. Set the Availabilities to query for the selected location.

   • To add an availability to the location query, select it in the drop down list and click Add branch.

   • To remove an availability from the location query, select it in the drop down list and click Remove branch.

7. Note: Each time you add or remove an availability, an exit is either added or removed from the node.

8. Click Save.

This node has one entry and three exits. The number of exits cannot be changed.

Note: These exit descriptions are specific to the responses received from an Oracle VWS billing engine. For specific information about how responses from other billing engines map to these exits, see the technical guide for the interface for billing engine being used.

Follow these steps to configure the Profile Branching node.

1. In the Source Data Type field, select the data type of the source profile block.

2. In the Source Location field, select the profile block in which relevant information is stored.

3. In the Source Field field, select the profile tag that identifies the information required by the node.

4. Select either to compare the Value, or the Length of the source.

5. From the Comparison Operator list, select the type of comparison that is to be made.

   This field describes the relationship between the value in the specified profile field and the value set as the Constant.

   Example: In the screen shown above, the value in the specified profile field is required to be greater than 0. Therefore, the Comparison Operator is set to “Greater than” and the Comparison Constant is set to “0”.

6. Type the Comparison Constant that is required.

   Result: The specified Profile field will be compared with the set constant value.

7. Click Save.

   Note: The Save button becomes available when the Primary Tag field is populated with a value other than 0.

This node has one entry and two exits. The number of exits cannot be changed.

Follow these steps to edit the node configuration.

1. In the Profile Counter Field area, using the drop down boxes, select the target profile counter field.

2. Type the number to set to or increment the profile counter by in the Value field.

3. To set the profile counter to the value, tick the Set Absolute check box.

   To increment the profile counter by the value, clear the Set Absolute check box.

4. Click Save.

Note: The list of data types is fixed at installation time for each feature node or screen.

Further reference:

• For information about profile blocks (data type, location, and field) and how to use them, see Profile Blocks and Tags.

The primary tag lists are configured in the SMS > Services > ACS Service > Configuration > Profile Tag Details and Profile Tag Mapping tabs (see ACS User's Guide, Profile Tag Details for more information).

This node has one entry and five exits. The number of exits cannot be changed.

Follow these steps to edit the Profile Date Compare node.

1. From the drop down lists in the Location of Date area, select the profile Data Type, Location and Field that holds the stored Profile Date you want to be compared against the current system date.

2. Click Save.

Note: The list of data types is fixed at installation time for each feature node or screen.

Further reference:

• For information about profile blocks (data type, location, and field) and how to use them, see Profile Blocks and Tags.

The primary tag lists are configured in the SMS > Services > ACS Service > Configuration > Profile Tag Details and Profile Tag Mapping tabs (see ACS User's Guide, Profile Tag Details for more information).

The Profile Date Store feature node has one entry and two exits. The number of exits cannot be changed.

Follow these steps to edit the Profile Date Store feature node.

1. From the drop down lists in the Store Date To area, select the Data Type, Location and Field where you want to retrieve and/or store the Profile Date.

   Note: The available profile data is the same for all service providers on the system.

2. In the Units area select whether to add Days, Months or Years to the stored date.

3. In the Number to add area, configure the number of units of the selected type to add to the stored date. Do one of the following:

   • In the Time to add field enter the number of units to add.

   • Tick the Use Profile check box and select the profile Data Type, Location and Field where the number you want to add is stored.

   The feature node checks the extended date to ensure that it is not greater than the maximum Unix time defined for the system.

   Note: If you do not specify a value here, then a value of zero is assumed.

4. If you chose Months in the Units area, then in the End month algorithm area select the required option for adjusting end of month dates.

   • Adjust up – Adding a month to the end of the current month sets the date to the last day in the following month. Also sets the date to the last day in the following month if the current date is the day before the last day in the month and the following month has fewer days.

   • Adjust down – Adding a month to the end of the current month sets the date to the last day in the following month for months which have the same or fewer days than the current month. Where the following month has more days than the current month, it sets the date to the same day number in the month.

   • Add # days in month – Adds the number of days in the current month to the selected Extend From date.

5. For further clarification, see Adding months example.

6. Select the type of extension required from the Extend From options.

   • Today – To add the specified number of units to the current system time.

   • Profile – To add the specified number of units to the date currently stored.

   • Later of the two – To store the later date out of the Today and Profile options.

7. In the Timezone area select the required time zone from the drop down lists.

8. Click Save.

Note: The list of data types is fixed at installation time for each feature node or screen.

Further reference:

• For information about profile blocks (data type, location, and field) and how to use them, see Profile Blocks and Tags.

The primary tag lists are configured in the SMS > Services > ACS Service > Configuration > Profile Tag Details and Profile Tag Mapping tabs (see ACS User's Guide, Profile Tag Details for more information).

This table shows some example month end adjustment results after adding one month to the current date.

The shortcut keys to add a Proportional Distribution node are Alt+D.

This node has one entry and may have 2 through 20 exits. You can configure the number of exits within this range as required, using the Edit Node Exits option on the shortcut menu. See Editing Feature Node Exits.

Follow these steps to configure the node.

1. Ensure that you have enough exits specified to accommodate the proportions you are planning to configure.

2. Using the spin box for each exit, change the number displayed to show the proportion of calls that are routed down that exit.

   Note: The proportion is calculated per total across all exits. To configure the node on a percentage basis, the total must equal 100. If there are two exits, configured with the digits 1 and 4, 1 out of 5 calls will route down exit 1 and the remaining 4 calls will route down exit 2.

3. When all proportions are as required, click Save.

The shortcut keys to add a Selection Dependent Routing node are Alt+M.

This node has one entry and may have 2 through 20 exits. You can configure the number of exits within this range as required, using the Edit Node Exits option on the shortcut menu. See Editing Feature Node Exits.

There are two cases in which a caller will be sent to a branch other than the branch corresponding to a digit selected by the caller. These are:

Follow these steps to configure the Selection Dependent Routing node.

1. From the Main Announcement area, select the Main Announcement Set that contains the main announcement to play to the caller.

   Note: It is not necessary to have all the announcements that are to be played by this node in the same announcement set.

   Result: The Main Announcement Entry drop-down box will become available.

2. From the Main Announcement Entry drop-down list, select the main announcement to play to the caller.

3. Set the Repetition field to the number of times to repeat the main announcement while the system waits for the caller to take an action. If set to zero, the announcement will be repeated for the length of the duration set.

4. The timeout announcement contains the announcement you want to play to the caller when the caller has waited too long before entering a digit.

   In the Timeout Announcement frame, select the following, as described in steps 2 - 5:

   • Timeout Announcement Set which contains the timeout announcement

   • Timeout Announcement Entry for the announcement to play

   • Repetition to the number of times to repeat the announcement

   • Duration to the length of time, in seconds, that the announcement is to be played.

5. The invalid digit announcement contains the announcement you want to play to the caller when the caller has entered a disallowed digit.

   In the Invalid Digit Announcement frame, select the following, as described in steps 2 - 5:

   • Invalid Digit Announcement Set which contains the announcement

   • Invalid Digit Announcement Entry for the announcement to play

   • Repetition to the number of times to repeat the retry announcement

   • Duration to the length of time, in seconds, that the retry announcement is to be played.

6. In the Number of Retries field, set the number of times that the node will attempt to collect a number from the caller, before routing the call to the Not Collected branch. This value may be between 0 and 10.

7. In the standard range entry field in the lower half of the screen, map the digits that a caller may enter to an exit branch.

   To add a digit:

   • Click Add Digit

     Result: A new default entry appears.

   • In the Digit drop-down box, select the required digit.

   • In the Branch drop-down box, select the exit to which calls receiving the entry of that digit are to be routed.

   • Click Change.

8. Repeat for the required number of mappings.

9. Click Save.

   Note: Save is not available until all the required information has been selected or entered.

Note: The announcement set and announcement entry lists are populated with data that is specified using the Announcements tab of the ACS Configuration screen.

For more information about configuring announcement sets and announcement entries, see the Announcements tab of the ACS Configuration screen.

To configure the Selection Dependent Routing feature node to exit directly after timing out:

1. Open the configuration window for the Selection Dependent Routing feature node.

2. Specify the branch that you want to use for the fast timeout exit by changing the current configuration for a branch to T or by adding T to a branch.

   To change the current configuration for a branch to T.

   1. Select the digit and branch combination you want to change from the list in the digit table.

   2. Select T from the Digit list and click Change.

   To add T to a branch.

   1. Use the Branch arrow keys to select the branch you want.

   2. Select T from the Digit list and click Add.

   The Fast Timeout Period field is enabled and set to the preconfigured default value of 10.

   Note: If set, the value for the SDRfastTimeoutDefault parameter in the sms.jnlp file overrides the fast timeout period default value. For more information on configuring ACS sms.jnlp parameters, see Advanced Control Services Technical Guide.

3. (Optional) Change the timeout period by performing the following steps:

   1. In the digit table, select T.

   2. In the Fast Timeout Period field, enter the timeout value in seconds and click Change.

4. Click Save.

   The feature node configuration is saved.

This node has one entry and eleven exits. The number of exits cannot be changed.

Note: The temporary, permanent and abort errors are all configured in the Messaging Manager Action and Error Codes screens. From the main SMS screen, see Services > Messaging Manager > Action and Error Codes and the Error Type column.

Follow these steps to configure the node.

1. In the Template section, do one of:

   • Provide the location of the template by selecting a profile location from the Data Type, Location and Field lists

   • Select the template to use from the Fixed lists

   • Select the location where notification template name for a specific Application type can be found from the Data Type, Location and Field lists

2. In the Language section, do one of:

   • Select Automatically determined to have the system determine the language

   • Select the location where the language can be found from the Data Type, Location and Field lists

   • Select the language to use from the Fixed list

3. If a response is expected, to avoid missing the response, select the Wait for Response check box and then enter the number of seconds to wait for the response in the Timeout field in the Options section.

   Tip: If the check box is deselected, then the node will exit the Success exit immediately.

4. Click Save.

This node has one entry and two exits. The number of exits cannot be changed.

Follow these steps to configure the Send Short Message node.

1. From the Application drop down list, select application that will trigger the short message to be sent.

2. From the Message drop down list, select the message that will be sent.

   Note: Messages are created and maintained through the ACS > Configuration > Notification tab.

3. From the Language drop down list, select the language the message will be sent in.

   Note: Available languages are maintained through the ACS > Tools > Language tab.

4. Click Save.

Notes:

• The calling number is normalized before it is sent to the notificationIF.

• This node sends a SLEE notification event to the notificationIF.

• The notificationIF will then forward the message to either Messaging Manager or the SMSC interface depending on configuration.

• See SMSC Technical Guide for details on how to install and configure the notificationIF.

This node has one entry and two exits. The number of exits cannot be changed. Since this node passes the call to another control plan, a Success exit is not required.

Follow these steps to configure the Service Handover node.

1. In the Handover to list, select a service. Calls passing through this node will be transferred to this service.

2. Click Save.

This node has one entry and two exits. The number of exits cannot be changed.

Follow these steps to configure the Set node.

1. In the Value field type the number (in digits) to save in the selected target profile field.

2. In the Target Profile area, using the drop down boxes, select the target profile.

3. Click Save.

Note: The list of data types is fixed at installation time for each feature node or screen.

Further reference:

• For information about profile blocks (data type, location, and field) and how to use them, see Profile Blocks and Tags.

The primary tag lists are configured in the SMS > Services > ACS Service > Configuration > Profile Tag Details and Profile Tag Mapping tabs (see ACS User's Guide, Profile Tag Details for more information).

This node has one entry and two exits. The number of exits cannot be changed.

Follow these steps to configure the Set Carrier Code node.

1. Select the option of:

   • using the carrier number entered into this screen, or

   • reading the carrier number from a profile block.

   The fields relating to the non-selected option are disabled and cannot be edited.

2. Where the following option is selected:

   • Use This Carrier Number

     Type the carrier code in the Use This Carrier Number field.

     Carrier codes may include any hexadecimal character (0-9, a-f, A-F, and # and *). You can enter up to 20 characters.

     Note: If this option is selected and the text field is empty, then the carrier code field will be cleared when this node is triggered. Use to clear a carrier code set by an earlier Set Carrier Code node.

   • Read from Profile Block

     Select the profile field to read the carrier code from using the Read From Data Type, Read from Location and Read From Field drop down lists.

     Note: If the length of the number string in the profile field specified for the carrier code is greater than the allowable length of the carrier code, an alarm is raised and the “CC Not Set Branch” is taken.

3. Click Save.

   Note: Save is not available until all the required information has been selected or entered.

Note: If you import a previously exported control plan which contains Set Carrier Code nodes prior to the profile block functionality being introduced, then you will need to re-save in order to allow the control plan to recompile.

Note: The list of data types is fixed at installation time for each feature node or screen.

Further reference:

• For information about profile blocks (data type, location, and field) and how to use them, see Profile Blocks and Tags.

The primary tag lists are configured in the SMS > Services > ACS Service > Configuration > Profile Tag Details and Profile Tag Mapping tabs (see ACS User's Guide, Profile Tag Details for more information).

This node has one entry and one exit. The number of exits cannot be changed.

Follow these steps to configure the Set Cut and Paste node.

1. In the Cut Value field, enter the value to set the cutAndPaste parameter to in INAP Connect operations sent to the switch from here on.

   Note: If you set Cut Value to 23 or more, ACS will stop setting the cutAndPaste parameter in INAP Connect operations.

2. Click Save.

This node has one entry and two exits. The number of exits cannot be changed.

Follow these steps to configure the node.

1. From the Select Indicator options, select the indicator to set:

   • Presentation Restricted

   • Screening

   • Number Incomplete.

2. From Select Number drop down list, select the phone number to apply the indicator to.

   • CallingPartyNumber

   • AdditionalCallingPartyNumber

   • OriginalCalledPartyID

   • RedirectingPartyID

   • LocationNumber

   • LocationInformationLocationNumber

3. Note: This list contains all the valid phone number options.

4. From the Set Indicator options, select the value to apply to the selected phone number indicator.

   Refer to the interpretation of values table below.

5. Click Save.

This table describes the meaning of each value, depending on the indicator selected.

This node has one entry and two exits. The number of exits cannot be changed.

Follow these steps to configure the Set Pending TN from Profile node.

1. Using the drop down lists in the Location of TN Data Type, Location and Field boxes, select where the number is to be read from.

   Notes:

   • If you set a customer-specific profile, the profile set in this field must belong to the customer who will be running the control plan.

   • If the control plan is owned by the Boss user then the profile must be set to control plan, or a customer ID must be specified at an earlier point in the control plan.

2. Using the drop down lists in the Location of Timeout Data Type, Location and Field fields, select where the timeout period is to be read from.

3. Click Save.

   Note: Save is not available until all the required information has been selected or entered.

Note: The list of data types is fixed at installation time for each feature node or screen.

Further reference:

• For information about profile blocks (data type, location, and field) and how to use them, see Profile Blocks and Tags.

• The primary tag lists are configured in the SMS > Services > ACS Service > Configuration >Profile Tag Details and Profile Tag Mapping tabs (see ACS User's Guide, Profile Tag Details for more information).

This node has one entry and four exits. The number of exits cannot be changed.

Follow these steps to edit the node configuration.

1. From the drop down lists in the Presence Entity panel, select the Data Type. Location and Field where the presence entity name or number is held.

2. If required, set the Domain Name field to the name of the domain to append to the presence entity name or number.

   Note: The domain will not be appended to the presence entity if it is already present in the Field selected in the Presence Entity panel.

3. From the drop down lists in the Presence domain panel, select the Data Type, Location and Field where the presence setting chassis action information is held.

   Note: Currently only SIP presence setting is supported.

4. Set the action to be taken if the presence domain cannot be found. Select:

   • Error – to report an error, or

   • Use default below – to use the default presence domain. Select the default presence domain from the drop down list.

5. Set the Location for the presence entity.

6. Select the Availability that will be set by the node for the selected location.

7. Click Save.

This node has one entry and two exits. The number of exits cannot be changed.

Follow these steps to set the tariff code.

1. Use the drop-down list to select the type tariff applied to the current call. The tariff code names available in the list are set on the Tariff Codes tab of the ACS Resources screen.

2. Click Save.

   Note: Save is not available until all the required information has been selected or entered.

This node has one entry and two exits. The number of exits cannot be changed.

Follow these steps to configure the node.

1. Enter the Sleep Time Value in milliseconds the node is to wait before branching down the Success branch.

   Note: There is a maximum sleep time allowed of 600000ms (ten minutes)

2. Click Save.

The shortcut keys to add a Start node are Alt+S.

Note: If there is already a Start node in the Control Plan, pressing this key combination will select the Start node.

This node has no entry and one exit. The number of exits is fixed and cannot be changed.

The Start node does not need to have any control plan data attached to it when operating in standard mode, although the user must accept the default settings by opening the node edit screen and clicking Save.

Follow these steps to configure the Start node.

1. In the Standard Mode of operation, the control plan may not contain loops. For some advanced control plans, loops may be required. to allow loops in the control plan, select the Loops Allowed check box.

   Note: The control plan compiler will permit loops within the control plan, as long as those loops contain at least one feature node that performs a telephony action. For example, an attempt termination node or node that plays an announcement.

2. Click Save.

This node has one entry and three exits. The number of exits cannot be changed.

Follow these steps to configure the Statistic Increment node.

1. Select the Statistic Action, either:

   • Reset - reset the statistic value to zero.

   • Increment - increments the statistic by one.

2. Select the Statistic Name to action location, either:

   • From a profile field - check the Derive From Profile check box.

   • A named statistic - uncheck the Derive From Profile check box.

3. Select the Statistic Name to action, either:

   • From a profile field - select location from the Data Type, Location and Field drop down lists.

   • Named statistic - select from the Application Id and Statistic ID drop down lists.

   Note: This list is populated from entries made in the Statistic Management screens. Refer to the SMS User's Guide for more information.

4. Optionally set the Statistic Storage location. Check the Store check box and then selection the storage location from the Data Type, Location and Field drop down lists.

5. Click Save.

This node has one entry and two exits. The number of exits cannot be changed.

Follow these steps to configure the Statistic Increment node.

1. (Required) Select the Application ID using the Application ID field drop down list.

2. (Required) Select the Statistic ID using the Statistic ID field drop down list.

   Note: This list is populated from entries made in the Statistic Management screens. See SMS User's Guide for more information.

You can produce reports on the statistic from the Service Management System Operator Functions, Report Functions menu option. See SMS User's Guide for more information.

This node has one entry and a varying number of exits that are set as a result of the sub control plan. A user cannot change the number of exits.

Follow these steps to edit the node configuration.

1. (Optional) In the Search By field enter the control plan name prefix to use to filter the list of available control plans. You can enter the following wildcards in the search string:

   • % (percent) to match any string of any length

   • _ (underscore) to match a single character

     Tip: You can limit the number of control plans found by entering a value in Max Rows.

2. From the Control Plans list, select the control plan to load into the main control plan as a sub-control plan.

3. (Optional) To view the selected control plan, click View.

   The selected control plan opens in a new Control Plan Editor window. The control plan structure will be read-only, but you will be able to edit the control plan data, and save it to a new version of the control plan, if required.

   • To save any changes to the control plan data, select Save from the File menu. In the Save Data/Structure dialog box, enter a new name in the Control Plan Data field, and click Save.

   • To close the control plan, click the close window button in the top right corner of the Control Plan Editor window.

4. Click Save.

A table lookup dataset contains a group of related codes, for example, for a specific geographic area or suburb.

A table lookup dataset can be public or private. A private table lookup dataset belongs to a specific customer. It is only available to that customer and the parent customers linked to that customer in the customer hierarchy. A public table lookup dataset is available to all customers.

This node has one entry and three exits. The number of exits cannot be changed.

To configure the Table Lookup feature node:

1. Open the configuration window for the Table Lookup feature node.

2. In the Lookup Input source area select the location of the prefix or CLI that you want the feature node to look up from the Source Data Type, Source Location and Source Field lists.

3. In the Lookup Result target area select the location to store the resulting code from the Target Data Type, Target Location and Target Field lists.

4. From the Dataset list, select the dataset that corresponds to the type of code you want. You can select a publicly owned dataset or a dataset that belongs to the customer. For more information about table lookup datasets, see About table lookup datasets.

5. Click Save.

This node has one entry and three exits. The number of exits cannot be changed.