Oracle Communications Network Charging and Control Control … · feature node. For example, a day-of-week feature node has multiple output paths. The current day-of-week determines

Oracle® Communications Network Charging and Control

Control Plan Editor User's Guide

Release: 4.4

June 2011

Commercial In Confidence

Page ii Control Plan Editor User's Guide

Copyright

Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.


Control Plan Editor Page iii User's Guide

Contents

Copyright ............................................................................................................................. ii About this Document ........................................................................................................... v Document Conventions ...................................................................................................... vi

Chapter 1

System Overview

Overview .............................................................................................................................. 1 What is the Control Plan Editor? ......................................................................................... 2 What is a Control Plan? ....................................................................................................... 4 What is a Feature Node? ..................................................................................................... 7 What is a Global Control Plan? ......................................................................................... 10 Accessing the Control Plan Editor ..................................................................................... 12 Viewing the Main Screen ................................................................................................... 13 File Menu ........................................................................................................................... 15 Edit Menu ........................................................................................................................... 20 Tools Menu ........................................................................................................................ 21 Printing Control Plans ........................................................................................................ 24

Chapter 2

Getting Started

Overview ............................................................................................................................ 27 Using the Mouse ................................................................................................................ 28 Using the Toolbar .............................................................................................................. 29 Using the Feature Palette .................................................................................................. 31 Keyboard Navigation ......................................................................................................... 35 Keyboard Navigation ......................................................................................................... 38

Chapter 3

Configuring the Control Plan Editor

Overview ............................................................................................................................ 41 Establishing Sets and Structures....................................................................................... 42 Establishing New Customer or Service Provider ............................................................... 44

Chapter 4

Using Feature Nodes

Overview ............................................................................................................................ 47 Feature Node Behaviour ................................................................................................... 48 Finding Feature Nodes ...................................................................................................... 51 Configuring Feature Nodes ............................................................................................... 52 Adding Node Comments ................................................................................................... 55 Moving Feature Nodes ...................................................................................................... 56 Copying Feature Nodes ..................................................................................................... 57 Deleting Feature Nodes ..................................................................................................... 58 Using the Control Plan Editor ............................................................................................ 59 How Feature Nodes are Joined ......................................................................................... 60

Continued on next page


Page iv Control Plan Editor User's Guide

Chapter 5

Creating Control Plans

Overview ............................................................................................................................ 63 Opening a Control Plan ..................................................................................................... 64 Creating a New Control Plan Structure ............................................................................. 65 Using an Existing Control Plan Structure .......................................................................... 66 Adding Control Plan Data .................................................................................................. 69 Saving a Control Plan ........................................................................................................ 70 Creating Public Control Plans ............................................................................................ 75 Editing Control Plans ......................................................................................................... 76 Deleting Control Plans and Structures .............................................................................. 77

Chapter 6

User Messages

Overview ............................................................................................................................ 79 CPE Compiler Errors ......................................................................................................... 80

Appendix Overview ............................................................................................................................ 83 Glossary of Terms ............................................................................................................. 85 Index .................................................................................................................................. 87


Control Plan Editor Page v User's Guide

About this Document

The scope of this document includes all functionality a user must know in order to effectively operate the CPE application. It does not include detailed design of the service or Feature Nodes specific to other applications.

This guide is written primarily for CPE administrators. However, the overview sections of the document are useful to anyone requiring an introduction.

Although there are no pre-requisites for using this guide, familiarity with the target platform would be an advantage.

A solid understanding of Unix and a familiarity with IN concepts are an essential pre-requisite for safely using the information contained in this technical guide. Attempting to install, remove, configure or otherwise alter the described system without the appropriate background skills, could cause damage to the system; including temporary or permanent incorrect operation, loss of service, and may render your system beyond recovery.

This manual describes system tasks that should only be carried out by suitably trained operators.

The following documents are related to this document:

SMSC Technical Guide

ACS Technical Guide

ACS Feature Nodes User’s Guide

ACS User Guide

Here are the changes to the document since the last release.

Version no.

Revision Date Description

01.00 2010-06-09 Initial release, based on CPE 2.4.2-06.00.

All feature node documentation is now in ACS Feature Nodes Guide.

02.00 2010-10-11 Re-branded.

Scope

Audience

Prerequisites

Related documents

Changes in this document


Page vi Control Plan Editor User's Guide

Document Conventions

Before you start using this guide, it is important to understand the terms and typographical conventions used in the documentation.

Specialized terms and acronyms are defined in the Glossary at the end of this guide.

Formatting convention Type of information

Special Bold Items you must select, such as names of tabs.

Names of database tables and fields.

Italics Name of a document, chapter, topic or other publication.

Emphasis within text.

Button The name of a button to click or a key to press.

Example: To close the window, either click Close, or press Esc.

Key+Key Key combinations for which the user must press and hold down one key and then press another.

Example: Ctrl+P, or Alt+F4.

Monospace Text that you must type and examples of code or standard output.

variable Used to indicate variables or text that should be replaced.

menu option > menu option > Used to indicate the cascading menu option to be selected, or the location path of a file.

Example: Operator Functions > Report Functions

Example: /IN/html/SMS/Helptext/

hypertext link Used to indicate a hypertext link on an HTML page.

The following icons are used as visual cues to draw attention to important information.

Note: Indicates useful and complementary information. Explanation, comment, or short expansion of the text object that is intended to catch your attention.

Tip: Indicates practical but non-essential information that makes the solution easier to use or operate (for example, keyboard shortcut, alternative way to perform a step in a procedure).

Warning: Indicates a caution. If this information is ignored, it could cause possible and irreversible damage to the equipment, data or software.

Typographical conventions

Icons


Control Plan Editor Page 1 User's Guide

System Overview

Overview

This chapter describes what the Control Plan Editor is and the basic functionality of the application.

This chapter contains the following topics.

What is the Control Plan Editor? ..................................................................... 2 What is a Control Plan? ................................................................................... 4 What is a Feature Node? ................................................................................ 7 What is a Global Control Plan? ..................................................................... 10 Accessing the Control Plan Editor ................................................................. 12 Viewing the Main Screen............................................................................... 13 File Menu ....................................................................................................... 15 Edit Menu ...................................................................................................... 20 Tools Menu .................................................................................................... 21 Printing Control Plans .................................................................................... 24

Chapter 1

Introduction

In this chapter

Chapter 1 Commercial In Confidence

Page 2 Control Plan Editor User's Guide

What is the Control Plan Editor?

The Control Plan Editor (CPE) is a graphical interface that allows the user to build Control Plans. This allows the Telco to route calls according to such factors as geographic location or time of day. Other services, such as freephone, PIN authorisation, call diversion, or announcements, are also made possible using the feature nodes available in the Control Plan Editor.

Using a drag and drop operation or keyboard commands, the user positions icons on the screen to represent the route taken by a call made through the Control Plan. Each icon represents a feature node and its associated functionality. Calls passing through the node are routed or logged, according to the functionality of the node. Where specific data is required to customise a feature node, an editable screen is provided.

In addition to allowing the flexible routing of calls, data may also be collected based on the operations performed by the processing of the service.

Example: An ACS Customer can use the “Event Counting” Feature Node to record the number of calls that were routed to a free phone service number. This may help the Customer decide the number of telephone lines and customer service operators needed to manage the volume of calls coming in.


Description

User interface and functionality

Data collection

Commercial In Confidence Chapter 1

What is the Control Plan Editor?, Continued


Here is an example of a control plan, as displayed on the ACS Control Plan Editor screen.

Example control plan



What is a Control Plan?

A Control Plan is similar to a flow chart. It defines the decisions and actions made to determine the routing of a call.

A Control Plan may consist of multiple different decision points or actions called “Feature Nodes”. Each feature node has one input and a number of outputs. The exceptions to this are the Start and End feature nodes, which have only one output or one input respectively.

Each output from a feature node can lead to another feature node. The output path used when exiting a feature node is determined by the functionality of that feature node. For example, a day-of-week feature node has multiple output paths. The current day-of-week determines the call’s output path. The user associates each day-of-week to an output path.

The Control Plan is made up of two parts: the Control Plan structure and the Control Plan data. The Control Plan structure is the flowchart (that is, the Feature Nodes that can be used during a call and the various paths through those Feature Nodes along which the call can progress). The Control Plan data is the decisions (that is, the values held at each Feature Node) that determine which path the call will progress along.

Some Control Plans are designed specifically for an application, to provide features that are appropriate to that application. The following Control Plan is specific to ACS and is explained in more detail in the ACS User's Guide.

This Control Plan is unavailable when ACS is run on MVAM 2.2.0c0

ACS2Management

ACS2 has a Control Plan for the ACS management service called ACS2Management. The Management Control Plan may be accessed as a dial-up feature, to allow the Telco to route a call through a series of prompts, in order for callers to change features of their own Control Plans.

You can run one control plan from within another. A control plan that is run from within another is known as a sub control plan.

A control plan that runs a sub control plan does so from a Load Sub Control Plan node.

For information about the Load Sub Control Plan node, refer to Sub Control Plan.


Description

Structure and data

ACS Control Plans

Sub control plans


What is a Control Plan?, Continued


Sub control plans (continued)

Viewing instance

When you set up a Load Sub Control Plan node, you view a list of control plans. From the list you select a candidate sub control plan. At this stage and from within the Load Sub Control Plan node, you can chose to view the candidate plan. When you view the plan in this way, you are using what is called a viewing instance of the control plan editor's screen.

The viewing instance allows you only to see the candidate sub control plan; you cannot edit it. In addition, not all types of node interaction are available. You can see help balloons but you cannot see input summary bubbles. See Bubble help (on page 48) and Input summary bubble (on page 48).



What is a Control Plan?, Continued


Sub control plans (continued)

Restrictions

There are some restrictions on the use of sub-control plans.

A control plan can include up to 127 Load Sub Control Plan nodes.

A control plan to be used as a sub control plan must have less than 21 exit nodes.

A control plan to be used as a sub control plan must itself not contain sub control plans.

A control plan that did not compile successfully will not be selectable from within a Load Sub Control Plan node.

The maximum number of nodes allocated to any customer's control plan is calculated across all control plans. You cannot exceed the allocation by the use of sub control plans. The maximum number of nodes is set in the ACS Customer screen, the absolute maximum is 2000 nodes. Refer to the Customer Resource Limits section of ACS User Guide.



What is a Feature Node?

In order to build a Control Plan, you will need to add feature nodes. The feature nodes will be assigned node numbers in the order you add them to the Control Plan. The order in which the nodes will operate is defined by the connecting lines between them. All nodes will have at least 1 entry path and 1 exit (except for the Start and End Node).

You can add feature nodes using either the mouse or keyboard commands.

Each feature node will have a set of default configuration data when you add it to a Control Plan. You can configure the default data in the ACS.

Each feature node has a different symbol on it, making it easier to see what functionality is in a Control Plan. Feature nodes in the work area have several things in common, shown in this diagram.

Feature Description

Colour If the node requires the addition of data to complete the Control Plan, the node will be shown in red. Once valid data has been provided and saved, the red colouring will disappear.

Note: If the node has been populated with adequate default data, it will appear as grey. You may still need to edit the data to create the desired result.

Exits Exit points are shown at the bottom of the node as diamonds. The exit points are shown in red if they are unconnected to another node and, once connected, will change to black.

Tip: In some circumstances, a node will link to itself. This will show as a black exit point, but with no line.

Name Each node has a node name. This is either assigned automatically, or can be specified in the node configuration screen in the Node name field.

The nodes will either be displaying the nodes’ numbers or the nodes’ names in the top left hand corner or the node. You can toggle between the two modes by pressing N.


Introduction

Default data

Node features


What is a Feature Node?, Continued


Node features (continued)

Feature Description

Number For each node added to the work area, the system will assign a node number. These are assigned sequentially based on the order the nodes were added. The node number is very useful when saving your Control Plan and trying to remove any errors in it. When saving a Control Plan, a report is given that will highlight any errors that may be present in the Control Plan and the number of the node in which the error occurred.

If the node number is not displayed in the left-top corner of the nodes, press N to change the display. Pressing N again will restore the node name display.

Tip: The node number may not necessarily be used to determine how many nodes have been used in the Control Plan, as when nodes are deleted from the middle of a Control Plan, the node number they were given is not reassigned. Deleting a node with the highest node number will result in that node number being reassigned to the next added node.

When a new feature node is added to the work area, it is given a sequential number. This is the node’s node number. This number (n) shows that this node was placed nth on the work area. This number will not change, even if nodes with a lower number are deleted. If a node with the highest node number is deleted, the node number will be reassigned to the next node to be added.

You can find a node by its number by either:

pressing the number key(s) which correspond to the node number

using the Find Node screen, or

entering the Node Number field in the toolbar.

You can add nodes using shortcut keys. The new node will be:

connected to the first available exit from the previously selected node, and

added to the work area below the previously selected node.

When a new node is added it will become the currently selected node.

The full list of shortcut keys for adding feature nodes is in Adding feature nodes using keyboard (on page 36).

The shortcut keys to add a feature node is also noted in each feature node description in the chapter Nodes in Depth.


Node numbers

Shortcut keys


What is a Feature Node?, Continued


Here are the generic steps for adding a feature node using the graphical interface.

Step Action

1 Open a new, or existing, Control Plan.

2 There are three ways of adding a feature node to a Control Plan using the GUI:

Clicking on a feature node button on the left of the Main Screen and dragging it to the desired location in the Control Plan.

Clicking on a feature node button on the left of the Main Screen, then double-clicking in the desired location in the Control Plan.

Result: A new feature node of the type you chose will appear on the Control Plan.

3 If required, add configuration details to the node as outlined in Editing node data (see "Configuring node data" on page 53).

Tip: The node may have default data already configured.

4 Connect the feature node to the other feature nodes by clicking on one of the red diamonds at the bottom of:

another feature node and dragging the cursor to the top of the new node, or

the node and dragging the cursor to the top of another feature node.

Result: This will connect the two feature nodes in the Control Plan structure. For more information, see How Feature Nodes are Joined (on page 60).

Graphical interface



What is a Global Control Plan?

Global Control Plans are an optional feature, allowing global call-screening at Telco level. Global Control Plans are always owned by the Telco, through the default Customer "Boss". This Customer can be renamed, but will be the only level 7 Customer in the system.

Global Control Plans are associated with a specific service entry, so that they apply only to Control Plans of a selected type. Service entries are defined in the configuration file for the appropriate application.

For example, the Control Plan saved under the name “Global Screening ACS” is associated with the service entry:

ServiceEntry (ACS,libacsService.sl)

This saved Control Plan is then recognised by the system as a global Control Plan, which is applied to all Control Plans associated with that particular service. The system will apply the Global Control Plan to all calls for all Customers before the Customer's Control Plans are applied. If the call is not connected through the Global Control Plan, the Customer's Control Plan will be applied.

As an example, the Telco may have been commissioned by Customer "Garden Centre" to advertise the special offers available throughout the year. The Telco creates a global Control Plan, which includes an announcement advertising Garden Centre. This is the Control Plan called Global Screening VPN. Every Control Plan associated with ServiceEntry (202,111,SIB_POI_ADDRESS_COLLECTED,VPN_Originating,libvpnService.sl) will be played the announcement before being routed according to Customer "Garden Centre’s" Control Plan for 0800 numbers.

Because the global Control Plan is enabled at Telco level and is invisible to the Customer, it is not possible for the Customer to choose whether or not the advertisement is heard by its callers. This gives the Telco superior control over any selected call processing.

Another possible application of this feature may be to exclude invalid calls at Telco level. For example, it may be necessary to exclude all calls originating in prisons from attaining 0900 numbers. This could be achieved using a global Control Plan incorporating the Calling Party Category feature node, to identify the category of the originating call. Global Control Plans have the flexibility to adapt to the needs of the Telco.

Only the system administrator is able to create a global Control Plan. Once logged in, the system administrator creates a new Control Plan in the usual way, in the Control Plan Editor.

The Control Plan may contain all the features of ordinary Control Plans, following the guidelines in this user guide. However, note that the global Control Plan takes precedence over any Control Plan associated with it. Any nodes in the global Control Plan that require telephony action (unconditional terminate, attempt terminate, disconnect, terminate unchanged) will result in the main Control Plan being abandoned.

For example, if the Global Screening VPN_Originating Control Plan included a disconnect node, the caller would hear the announcement advertising Customer "Garden Centre" and then the call would be disconnected. The Control Plan created by Customer "Garden Centre" is never enacted.


Introduction

Example 1

Example 2


What is a Global Control Plan?, Continued


Once the Control Plan is completed, follow these steps.

Step Action

1 Go to the appropriate configuration file (for example, acs.conf) to find the name of the required service entry, as explained above.

2 Save the Control Plan under the name Global Screening <service name>, where <service name> is the name of the service entry, as defined in the acs.conf file. Possible names are:

"Global Screening ACS_Outgoing"

"Global Screening ACS"

The Global Screening part of the name triggers the system to use this Control Plan as a global Control Plan, rather than an ordinary Control Plan.

The saved global Control Plan is then activated for all calls associated with the selected service entry.

Tip: Control Plan names are case sensitive.

The saved Control Plans are cached and are refreshed at 5 minute intervals. This means that changes to global screening plans are not updated immediately.

Saving the global Control Plan

Naming conventions and activating plan

Update interval



Accessing the Control Plan Editor

This topic explains how to access the CPE and the contents of the CPE Main Screen.

The Control Plan Editor is accessible through more than one application. Access to the Control Plan Editor is dependent on and specific to the application from which it is located. For example, to access the Control Plan Editor in ACS, select Control Plans on the main screen.

You can access the CPE through the ACS Numbers screen. This method is useful if you intend to use templates.

For more information on opening templates and the CPE from the ACS Numbers Screen, see the ACS User's Guide.

You can access the CPE through the ACS Numbers screen. This method is useful if you intend to use templates.

For more information on opening templates and the CPE from the ACS Numbers Screen, see ACS Numbers Screen.

Introduction

Signing on

ACS Numbers Screen

ACS Numbers Screen



Viewing the Main Screen

The Control Plan Editor is a graphical interface that uses a drag and drop operation or keyboard commands to allow the user to build Control Plans.

Here is an example of a typical Control Plan Editor screen.


Main screen

CPE Screen


Viewing the Main Screen, Continued


There are several visual features of the CPE:

Feature Description

Menu bar The Control Plan Editor has a menu bar at the top of the screen. Under each menu is a drop-down list of options. These will be described in detail in the following sections.

Toolbar The Toolbar is just below the menu bar and contains several buttons that allow actions to be performed directly. Choosing an option on a menu may also perform the same action. The Toolbar provides a shortcut method of performing frequently required actions.

To the right of the buttons there are two areas which display the MF Identifier and Control Plan Name of the current Control Plan.

If the relevant details are not yet available, these will display <Undefined>.

To the right of the Control Plan Name is the Node Number field.

To the right of the Node Number is a field displaying the name of the customer who logged on to the application. This is only available to the System Administrator.

For more information about the Toolbar and its functionality, see Using the Toolbar (on page 29).

Feature Palette The feature palette displays all the feature nodes that the customer can access. These nodes may be selected (clicked), dragged and dropped onto the work area to create a Control Plan. If a node on the palette is clicked "on", you may double click on the page to insert another node of that type on the work area.

Status Bar At the bottom of the screen, there is an information bar. This bar will display information relevant to the action that is being undertaken.

Work Area The work area is the white area in the Control Plan Editor, onto which feature nodes may be added. This is simply a blank area in which the user may build their Control Plans.

Screen features



File Menu

The Control Plan Editor File menu contains many of the file management commands that you require to create, save, load and remove Control Plans.

The File menu also displays a list of shortcut key combinations that you can use to select the options directly from the keyboard.

Here is the File menu of the CPE screen.

In the File menu, there are several options that display screens which require the user to make a selection from a displayed list of Control Plan or Control Plan Structures. The features that these screens have in common and their use will be described here. Those things that are specific to each screen will be covered under the specific option description.

On the left side of the screens there is usually a list of Control Plans or Control Plan Structures. These are displayed in alphabetical order.

After the Name of the Control Plan (Structure) in brackets is the version number of the Control Plan followed by the compile status and the Public status.

That is: Control Plan Name (version number, compile status, public status)

Detail Description

Version Number

This is displayed as Vn where n is the version number of the Control Plan.

Compile Status This informs the user of whether the Control Plan or Control Plan structure compiled successfully or not. Compile status are:

S = Successfully Saved without Errors

E = Saved with errors

B = Saved. But has not been checked for errors (this is the status that is given to a Control Plan before it has been checked by the system for errors). This Status should only be seen in the Delete Data and Delete Structure Screens.

Control Plans with a Compile Status of E or B will not be available for use. That is, they may not be used by the Service Logic to route calls.


Introduction

CPE File menu

Screen selections

Control Plans and Structures

Naming Conventions and Control Plan information


File Menu, Continued


Naming Conventions and Control Plan information (continued)

Detail Description

Public Status The Public Status is shown by the absence or presence of the word Public. If a Control Plan Structure is Public, or is based on a Public structure, a status of Public will be displayed. If the Control Plan Structure is not public, the status will be indicated by the lack of 'Public' being displayed.

Structure Status / Availability Status

To the right of the selection list, there are check boxes that allow filtering of Control Plans. Control Plans may be filtered according to who owns the Control Plan structure, or according to the compile status of the Control Plan or Structure. To use either of these filtering options, tick the appropriate check box and only those Control Plans that meet the filtering criteria will be shown in the list of available Control Plans.

Example: Ticking the Private Owner box and the compiled OK box will refresh the list of available Control Plan structures to display only those structures that are privately owned by the customer (that is, no other User may see them) AND have compiled OK, without any errors.

The required option may be selected and the action of the default button on the screen activated by double clicking on the required option in the selection list (for example, in an Open screen, double clicking on an entry in the selection list will open that Control Plan).

Here are the options available from the File menu.

Menu option Description

Open This option allows you to open and modify existing Control Plans.

The shortcut keys for this option are Ctrl+O.

The Toolbar button for this option is .

Selecting Open will display the Open Existing Control Plan screen.

For more information, refer to Opening a Control Plan (on page 64).

New This option clears the screen, to allow a completely new Control Plan to be built using the Feature Nodes on the Feature Palette.

The shortcut keys for this option are Ctrl+N.


The Control Plan that is currently on the work area must be saved before a new work area is opened, otherwise it will be lost.

For more information, refer to Creating a New Control Plan Structure (on page 65).


File Menu options




File Menu options (continued)


New plan from Existing Structure

Selecting this option will display the New Plan from Existing Structure screen.

Tip: You can also open a Control Plan from a template through the Numbers screen of the ACS.

For more information, refer to Using an Existing Control Plan Structure (on page 66).

Save This option allows you to save Control Plans to the database.

The shortcut keys for this option are Ctrl+S.


The Control Plan structure and the Control Plan data may be saved with separate names in the Save Data/Structure screen. Both the Structure Name and Data Name may be up to 30 characters in length, but must be unique for the Customer.

For more information, refer to Saving a Control Plan (on page 70).

Import from file

This option allows you to import back into the Control Plan Editor a Control Plan that has been exported to a file to be and saved so it may be used. When a Control Plan is imported, it must then be saved. This will call the Control Plan compiler and thus ensure that the Control Plan is valid for the Customer for whom it has been imported.

Where a Control Plan is imported for a Customer that does not have all the nodes in the Control Plan, a warning will be displayed for each node that the Customer does not have, informing the user that a specific node is not available and so the Control Plan may not be saved with that node in it.

Export to file Selecting this option will display the Export To File screen, which allows you to specify a location on any local or mapped drive on their machine to save the current Control Plan to.

The Control Plan will be saved as a file in the location and with the name specified by the user. A text-based summary of the call will be added to the beginning of the file.

Print This option allows you to print the Control Plan that is currently open in the Control Plan Editor. The entire Control Plan is scaled to fit a single printed page, as configured in the print dialogue.

The Print menu option reveals a sub-menu for Sun or Postscript printing dialogs.

For more information, refer to Printing Control Plans (on page 24).





File Menu options (continued)


Delete Data This option allows you to delete Control Plans. The screen displays only Control Plans that are not active (that is, Control Plans that are not attached to a Service Number or CLI).

For more information, refer to Deleting Control Plans and Structures (on page 77).

Delete Structure

This option allows you to delete Control Plan Structures.

For more information, refer to Deleting Control Plans and Structures (on page 77).

Exit Use this option to Exit the Control Plan Editor.

The shortcut keys are Alt+F4.

You can import and export Control Plans from the File menu. When you export a file, you create a .cpl file in text format. You can open and edit a .cpl file using Notepad (or any other text editor). A summary of the Control Plan is provided at the beginning of the file. To add a comment to the text, start the line with a “#” character.

Exporting a Control Plan to a file allows Control Plans to be saved and imported into another database, or to the same database but for another customer.

Here is an example of the Import Control Plan screen.


Importing and exporting Control Plans

Import Control Plan screen




Here is an example of the Export Control Plan screen.

Export Control Plan screen



Edit Menu

The Control Plan Editor Edit menu contains the editing commands that you require to cut, copy, paste and find Feature Nodes within the currently selected Control Plan.

The Edit menu also displays a list of shortcut key combinations that you can use to select the options directly from the keyboard.

Here is the Edit menu of the CPE screen.

Here are the options available from the Edit menu.


Cut This option allows you to cut a selected node to the clipboard.

The shortcut keys for this option are Ctrl+X.

Copy This option allows you to copy a selected node to the clipboard.

The shortcut keys for this option are Ctrl+C.

For more information, see Copying Feature Nodes (on page 57).

Paste This option allows you to paste a node from the clipboard.

The shortcut keys for this option are Ctrl+V.

For more information, see Copying Feature Nodes (on page 57).

Find This option allows you to find a node on the open Control Plan.

The shortcut keys for this option are Ctrl+F.

For more information, see Finding Feature Nodes (on page 51).

Introduction

CPE Edit menu

Edit Menu options



Tools Menu

The Control Plan Editor Tools menu contains a number of features which allow you to customise and enhance the CPE environment to suit your own working requirements.

Here is an example of the Tools menu in the CPE screen.


Introduction

CPE Tools menu


Tools Menu, Continued


Here are the options available from the Tools menu.


Reload Customer Data

This option tells the Control Plan Editor to look at the database again and refresh the information it holds. This must be used if data has been changed in the management screens while the Control Plan Editor is being used. This will allow the Control Plan Editor to see any changes that may have been made to the data since it was opened.

Example: If a change has been made to an Announcement Set, the Reload Customer Data option must be activated before the changes will be available in the CPE.

Properties This will display the name of the user and the customer who is logged on, their permission level and their session ID. The session ID and the numbers in brackets next to the names are used by the system and, in case of system failure, your technical support person may ask you for these.

The Control Plan information is also included. This tells you the Control Plan structure name, the Control Plan data name, the number of nodes that have been used in the Control Plan and whether it has been modified.

The Properties option will display an information box similar to this one:

Display Control Plan Bubble Help

If you select this option, you are able to view a node icon's:

name in full,

comments, and

exit point details.

See also Bubble help (on page 48).

Display Node Input Summary Bubble

If you select this option, you are able to view details of a node's inputs. See also Input summary bubble (on page 48).


Menu options


Tools Menu, Continued


Menu options (continued)


Display node parameters

This option allows you to display the parameters of all the nodes in the work area. The parameters will appear in a pink bubble to the left of the node. You can turn the display off by choosing the option again.

You can also turn this option on or off by pressing the shortcut keys Ctrl+D.

Grid granularity

This option displays the Snap to Grid control. The Snap to Grid option will align nodes on the screen as they are placed or moved to a non-visible grid. The control allows you to make the grid larger or smaller by moving the pointer along the scale.



Printing Control Plans

There are two Print options in the Control Plan Editor:

Sun Dialog

Postscript Dialog

Follow these steps to print a Control Plan, using the Sun dialog.

Step Action

1 Open the Control Plan you want to print.

2 Select the Print > Sun Dialog option from the File menu.

Result: You see the Print Dialog screen.

3 Configure the printing options as detailed below.

4 Click Print.

The Sun print dialog defaults to the standard dialog for the current operating system. The appearance of the dialog is therefore dependent on the current operating system.


Introduction

Printing a Control Plan

Configuring the Sun print options


Printing Control Plans, Continued


Follow these steps to print a Control Plan, using the Postscript dialog.

Step Action

1 Open the Control Plan to be printed.

2 Select the Print > Postscript Dialog option from the File menu.

Result: You see the Print Control Plan screen.

3 Configure the printing options as detailed below.

4 Click Print.

Here are the print options available in a Postscript print dialog.

Option Description

Title Displays the name of the open Control Plan.

Copies Enter the number of copies required.

Print command Enter the print command. Under Windows, this is “print”, where a print command exists. In case of difficulty, see the system administrator.

Print command options

Enter the port of the target printer. lpt1 is the default option. If lpt1 is not mapped to the appropriate printer, see the system administrator to set the correct mappings.

Top margin Enter the width of the top margin. This is measured in printer’s pts, which is approximately 1/72 inch.

Left margin Enter the width of the left margin. This is measured in printer’s pts, which is approximately 1/72 inch.

Bottom margin Enter the width of the bottom margin. This is measured in printer’s pts, which is approximately 1/72 inch.

Right margin Enter the width of the right margin. This is measured in printer’s pts, which is approximately 1/72 inch.


Printing a Control Plan - Postscript

Configuring the Postscript print options


Printing Control Plans, Continued


Configuring the Postscript print options (continued)

Option Description

Scale This option is currently unused.

Fit to Page Check this box to automatically scale the Control Plan to the page. If this option is not checked, the Control Plan is printed in proportion to its appearance on the screen.

Page Size Select the page size from the pull down list.

Orientation Select the page orientation, or select “automatic” to match the page orientation to the proportions of the Control Plan.

Print Activates the print job, following the specified configuration.

Set Defaults This button resets all fields with their default settings.

Close Closes the dialogue without printing the Control Plan.

Once printing is launched from a dialog, a modal progress bar prompt is displayed. Clicking Cancel will abort the print job.

Printing progress



Getting Started

Overview

This chapter describes how to access the Control Plan Editor (CPE) application and the interactive functions common to many of the Control Plan Editor screens.

Not all screens will have all the features listed in this section; some screens operate slightly differently to others.

There are several methods for performing user actions.

Point and click using the mouse

Toolbar

On-screen buttons

Shortcut keys

These are described in detail in the following topics


Using the Mouse ........................................................................................... 28 Using the Toolbar .......................................................................................... 29 Using the Feature Palette.............................................................................. 31 Keyboard Navigation ..................................................................................... 38

Chapter 2

Introduction

Methods

In this chapter



Using the Mouse

Use your mouse to navigate between screens and initiate system actions.

The Control Plan Editor enables you to use the point and click method for many of the actions required.

Follow these steps to add nodes to the page, or to move nodes around the page.

Step Action

1 Place the cursor over the node.

2 Press (“click”) the left mouse button and hold it down.

3 Drag the node to the desired location.

4 Release the mouse button to drop the node in place.

Follow these steps to edit nodes in the Control Plan Editor.

Step Action

1 Place the cursor over the node.

2 Either:

Click the right mouse button to display the shortcut menu, or

Double click the left mouse button to open the screen.

Introduction

Moving nodes

Editing nodes



Using the Toolbar

The Control Plan Editor Toolbar:

contains a number of buttons that provide a one step shortcut method of performing commonly used actions such as saving information, opening documents and selecting customers, and

displays information about the current Control Plan including:

the ACS Management Feature (MF) Identifier the Control Plan name the currently selected feature node, and the Customer.

Here is an example Control Plan Editor toolbar.

Here are the buttons on the Control Plan Editor toolbar.

Button Name Function

Open This will display the Open Existing Control Plan screen.

This action is also available from the Open option on the File menu.

New Structure This will clear the screen to allow a new Control Plan to

be built.

This action is also available from the New option on the File menu.

Save This will display the Save Data/Structure screen.

This action is also available from the Save option on the File menu.

Delete Node This will delete the selected Feature Nodes from the

Control Plan. Nodes may also be deleted using the shortcut menu. Alternatively the selected nodes may be deleted by using the Delete key on the keyboard.

Properties This displays the information screen.

This action is also available form the Properties option on the Tools menu.

Check Generate a Check Report on the current Control Plan.

The Check Report will detail any errors and inconsistencies that may exist in the Control Plan.


Description

Toolbar

Toolbar buttons


Using the Toolbar, Continued


Here is the information displayed on the toolbar about the Control Plan.

Display Description

MF Identifier This is a unique identifier that allows the application to determine which Control Plan is to be changed when dialling up the ACS Management Control Plan. The MF Identifier is allocated when the Control Plan is saved.

If this is a new Control Plan that has not yet been saved, or the loaded Control Plan does not have an MF Identifier, this will be displayed as <Undefined>.

Control Plan Name

The name of the current Control Plan is displayed in this section of the CPE Toolbar.

If this is a new Control Plan that has not yet been saved, <Undefined> will be displayed. The Control Plan name is the name of the Control Plan data.

Node Number To the right of the Control Plan Name is the Node Number field. This field will display the number of the currently selected node. If you type a number into this field and press Enter, the selected node will change to the node number entered.

Customer This field is only available to system administrators.

You use the Customer box to browse and select from a list of customers.

Control Plans that are created will belong to the customer that is displayed in this field.

If the user who logged into ACS has privilege level 6 or 7 (or ACS is being accessed through the SMS), then all customers in the system will be available for selection through this combo box. Where the user who logged on has a privilege level of 5 or below, then this is not available.

Toolbar Control Plan display information



Using the Feature Palette

The feature palette appears to the left of the work area when the Control Plan Editor is opened.

The feature palette contains all the feature nodes that the logged in Customer may use in their Control Plans. These are the icons that are used to build up Control Plans.

Here is an example of the ACS feature node palettes.

Note: The appearance of the feature palette may differ from user to user, according to the application installed and the selection of nodes available to the current user.

Base nodes

Here is an example feature palette for the base nodes.

See CPE User's Guide for details about the nodes in this feature set.

Data Operations nodes

Here is an example feature palette for the Data Operations nodes.

See ACS Feature Nodes User Guide for details about the nodes in this feature set.

Events nodes

Here is an example feature palette for the Events nodes.



Description

Example feature palette


Using the Feature Palette, Continued


Example feature palette (continued)

Interaction nodes

Here is an example feature palette for the Interaction nodes.

See Interaction nodes for details about the nodes in this feature set.

Network nodes

Here is an example feature palette for the Network nodes.


NTS nodes

Here is an example feature palette for the NTS nodes.


Number nodes

Here is an example feature palette for the Number nodes.






Example feature palette (continued)

Others nodes

Here is an example feature palette for the Others nodes.


Pending TN nodes

Here is an example feature palette for the Pending TN nodes.


Prefix Trees nodes

Here is an example feature palette for the Prefix Trees nodes.


Time nodes

Here is an example feature palette for the Time nodes.


The feature palette displays all the feature nodes which are available for use in the selected Customer's Control Plans. If the user with level 7 privileges (usually Boss) is selected, the full range of feature nodes will be displayed.

You can add feature nodes to the Control Plan by clicking on the node icon in the feature palette and dragging it onto the work area. You can also use the assigned keyboard Quick Keys to add the node. The node will appear below, and connected to, the previously selected node. You can find out what the assigned Quick Key combination is for a node (and its name) by hovering the mouse over the node icon in the feature palette.

For more information about adding nodes using keyboard commands, see Keyboard shortcut keys (on page 35).


Adding feature nodes




Follow these steps to add feature nodes on the work area using the mouse.

Step Action

1 Click on the required node icon in the feature palette.

2 Either:

hold down the mouse button and drag the node from the feature palette onto the work area, and release it into position, or

move the mouse to the work area and double click. This will place a node of the type selected on the work area, with the top left corner of the node at the point you double clicked.

Adding nodes using the mouse



Keyboard Navigation

You can navigate around the screens using keyboard commands or the shortcut keys. Keystrokes that will activate a specific menu option are displayed in the menu next to the option.

Many Feature Nodes can be added to a Control Plan using keyboard commands also. The new node will be added below and connected to the previously selected node.

Within the node configuration screens, there are a number of available keyboard commands. For more information about which key commands are available within each screen, see Navigating around node configuration screens (on page 35) and the node summary in Nodes in Depth.

Within the node configuration screens, you can navigate around the buttons and fields using the following commands:

Key Combination Action

Tab Move to the next field or button.

Shift+Tab Move to the previous field or button.

Ctrl+Tab Move to the next group of fields and/or buttons.

Ctrl+Shift+Tab Move to the previous group of fields and/or buttons.

Space or Enter Activate the selected button or save data entered in a field.

Alt Displays any keys that have been assigned to the buttons on a screen. To activate the button, press Alt and the underlined character.

Here are the shortcut keys for using the CPE.

Keys Action

Alt+F4 Quits from the CPE.

Warning: You will not be prompted to save the existing Control Plan when you exit.

arrow keys Enables you to scroll around the work area.

Alt+arrow keys Enables you to change the selected node.

Alt+drag node exit

Enables you to select all the unconnected node exits on a node and connect them to another node.

Ctrl + arrow keys This key combination enables you to select a series of nodes.

number keys The selected node will change to the number pressed.

Tip: To change to a node number with more than one digit, press the number keys in close succession.

Enter Opens the configuration editing screen for the selected node.

Alt+Enter If it is possible to change the number of exists a node has, this key combination will open the edit node exits screen for the selected node.

Ctrl+C Copies the selected Feature Node(s).


Introduction

Navigating around node configuration screens

Keyboard shortcut keys


Keyboard Navigation, Continued


Keyboard shortcut keys (continued)

Keys Action

Ctrl+D Turns the display of Feature Node parameters on and off.

N Turns the display of Feature Node names on and off.

Ctrl+E Displays the Save screen for exporting Control Plans to file.

Ctrl+F Displays the Search for Feature Nodes screen.

Ctrl+M Displays the Open screen for importing files.

Ctrl+N Clears the existing Control Plan from the work area and displays a blank Control Plan.

Ctrl+O Displays the Open Existing Control Plan screen.

Ctrl+P Displays the Postscript Printing Dialog.

Ctrl+S Saves the current Control Plan.

Ctrl+U Displays the Sun Printing Dialog.

Ctrl+V Adds a Feature Node or Nodes to the Control Plan at the bottom right of the selected Feature Node. The node added will be the same type and have the same configuration as the node(s) most recently copied or cut. The node(s) added will have new node numbers.

Ctrl+X Removes the selected Feature Node(s).

These shortcut keys add the following feature nodes to a Control Plan.

Keys Feature Node

Alt+A Attempt Termination

Alt+Shift+A Attempt Terminate to Pending TN

Alt+C Calling Party

Alt+Shift+C Calling Party Category

Alt+D Proportional Distribution

Alt+E End

Alt+Shift+G Geographical Routing

Alt+M Selection Dependant Routing

Alt+P Play Announcement

Alt+R Disconnect Call

Alt+S Start

Tip: If there is already a Start node in the Control Plan, pressing this key combination will select the Start node.

Alt+T Time of Day

Alt+U Unconditional Termination

Alt+Shift+U Unconditional Terminate to Pending TN


Adding feature nodes using keyboard




Adding feature nodes using keyboard (continued)

Keys Feature Node

Alt+W Day of Week

Alt+Y Day of Year



Keyboard Navigation

You can navigate around the screens using keyboard commands or the shortcut keys. Keystrokes that will activate a specific menu option are displayed in the menu next to the option.

Many Feature Nodes can be added to a Control Plan using keyboard commands also. The new node will be added below and connected to the previously selected node.

Within the node configuration screens, there are a number of available keyboard commands. For more information about which key commands are available within each screen, see Navigating around node configuration screens (on page 35) and the node summary in Nodes in Depth.

Within the node configuration screens, you can navigate around the buttons and fields using the following commands:

Key Combination Action

Tab Move to the next field or button.

Shift+Tab Move to the previous field or button.

Ctrl+Tab Move to the next group of fields and/or buttons.

Ctrl+Shift+Tab Move to the previous group of fields and/or buttons.

Space or Enter Activate the selected button or save data entered in a field.

Alt Displays any keys that have been assigned to the buttons on a screen. To activate the button, press Alt and the underlined character.

Here are the shortcut keys for using the CPE.

Keys Action

Alt+F4 Quits from the CPE.

Warning: You will not be prompted to save the existing Control Plan when you exit.

arrow keys Enables you to scroll around the work area.

Alt+arrow keys Enables you to change the selected node.

Alt+drag node exit

Enables you to select all the unconnected node exits on a node and connect them to another node.

Ctrl + arrow keys This key combination enables you to select a series of nodes.

number keys The selected node will change to the number pressed.

Tip: To change to a node number with more than one digit, press the number keys in close succession.

Enter Opens the configuration editing screen for the selected node.

Alt+Enter If it is possible to change the number of exists a node has, this key combination will open the edit node exits screen for the selected node.

Ctrl+C Copies the selected Feature Node(s).


Introduction

Navigating around node configuration screens

Keyboard shortcut keys




Keyboard shortcut keys (continued)

Keys Action

Ctrl+D Turns the display of Feature Node parameters on and off.

N Turns the display of Feature Node names on and off.

Ctrl+E Displays the Save screen for exporting Control Plans to file.

Ctrl+F Displays the Search for Feature Nodes screen.

Ctrl+M Displays the Open screen for importing files.

Ctrl+N Clears the existing Control Plan from the work area and displays a blank Control Plan.

Ctrl+O Displays the Open Existing Control Plan screen.

Ctrl+P Displays the Postscript Printing Dialog.

Ctrl+S Saves the current Control Plan.

Ctrl+U Displays the Sun Printing Dialog.

Ctrl+V Adds a Feature Node or Nodes to the Control Plan at the bottom right of the selected Feature Node. The node added will be the same type and have the same configuration as the node(s) most recently copied or cut. The node(s) added will have new node numbers.

Ctrl+X Removes the selected Feature Node(s).

These shortcut keys add the following feature nodes to a Control Plan.

Keys Feature Node

Alt+A Attempt Termination

Alt+Shift+A Attempt Terminate to Pending TN

Alt+C Calling Party

Alt+Shift+C Calling Party Category

Alt+D Proportional Distribution

Alt+E End

Alt+Shift+G Geographical Routing

Alt+M Selection Dependant Routing

Alt+P Play Announcement

Alt+R Disconnect Call

Alt+S Start

Tip: If there is already a Start node in the Control Plan, pressing this key combination will select the Start node.

Alt+T Time of Day

Alt+U Unconditional Termination

Alt+Shift+U Unconditional Terminate to Pending TN


Adding feature nodes using keyboard




Adding feature nodes using keyboard (continued)

Keys Feature Node

Alt+W Day of Week

Alt+Y Day of Year



Configuring the Control Plan Editor

Overview

This chapter explains how to set up and use the Control Plan Editor. You must complete all the stages of this process before you can use the Control Plan Editor.


Establishing Sets and Structures .................................................................. 42 Establishing New Customer or Service Provider .......................................... 44

Chapter 3

Introduction

In this chapter



Establishing Sets and Structures

To make public Control Plan structures in the Control Plan Editor, you must open the ACS and log on as the level 7 user (usually Boss, unless this Customer has been renamed).

Follow the directions in the ACS User Guide, to set up ACS for initial use.

Feature Node Sets must be set up to allow Customers to use Feature Nodes in their Call Plans. Feature Node sets are set up in the Feature Sets tab on the ACS Configuration screen. It is not possible to add or to edit sets through CPE, you must do this through the ACS application.

Set up the required Feature Node Sets and enter Feature Nodes into them.

For more information on setting these elements up, see the ACS User Guide.

Once the relevant feature set has been set up, it must be assigned to a Customer before they can use it in the CPE. This is done in the Resource Limits tab of the ACS Customer screen. Several Customers may use the same set.

Note: The Customer will not have access to a newly assigned Feature Node set until they open the CPE again, or the choose Refresh Customer Data from the Tools Menu in the CPE.


Public Holiday Sets are Holiday Sets that all Customers will be able to use in their Control Plans, but will not be able to change them. This is not essential, but may prevent unnecessary duplication of Holiday Sets.

For example, it may be useful for the telecommunications provider to set up a Public Holiday Set containing all the public holidays for the year. This will enable all Customers to use the set of public holidays where their business may be closed, rather than each Customer setting up their own set of public holiday days.

Public Holiday Sets may only be set up by the System Administrator and only New Sets may be saved as public sets. It is not possible to edit a set to become public, or to edit a public set to become non-public. It is important to tick the Public check box on the New Holiday Set screen, to save the Holiday Set as a public Holiday Set.

Holiday Sets are set up in the Holidays tab on the ACS Configuration screen.

Public Announcement Sets are sets of announcements that are grouped together for convenience and may be used by all Customers. Customers may use public announcements in their Control Plans, but may not change the set. As for public Holidays, the telecommunications provider may wish to make certain announcement sets public, to prevent duplication.

Public Announcement Sets (in fact all announcements) may only be set up and edited by the System Administrator. Only New Sets may be saved as public sets. It is not possible to edit a set to become public, or to edit a public set to become non-public. It is important to tick the Public check box on the New Announcement Set screen, to save the Announcement Set as a public Announcement Set.

Announcement Sets are set up in the Announcements tab on the ACS Configuration screen.


Before making public call plan structures

Additional set up info

Set up feature node sets

Additional info

Assigning sets to customers

Additional info

Making public holiday sets

Making public announcement sets


Establishing Sets and Structures, Continued


Public Geography Sets are sets of Geographical Entries that are grouped together for convenience and may be used by all Customers. Customers may use public Geography Entries in their Control Plans, but may not change the set. As for public Holidays, the telecommunications provider may wish to make certain announcement sets public, to prevent duplication.

Public Geography Sets may only be set up and edited by the System Administrator. Only New Sets may be saved as public sets. It is not possible to edit a set to become public, or to edit a public set to become non-public. It is important to tick the Public check box on the New Geography Set screen, to save the Geography Set as a public Geography Set.

Geography Sets are set up in the Geography tab on the ACS Configuration screen.


Open the Control Plan Editor and build the Control Plans that are to be public. Save the Control Plan Structure as a public Control Plan Structure. This will allow all Customers to make their own Control Plans based on these structures.

Any Control Plans that the System Administrator saves will be available on the override Control Plan field, in the Customer Details screen.

Public Control Plans are identifiable in the New Control Plan on Existing Structure screen list of Control Plan Structure, by the word (Public) being placed in brackets after the Structure Name.

Making public geography sets

Additional info

Making public Control Plan structures



Establishing New Customer or Service Provider

To set up a new Customer or service provider so they can use the CPE, the telecommunications provider will need to follow this process, using the ACS screens.

Stage Action

1 Set up the Customer or service provider, according to the application user guide.

2 Add CLIs and Service Numbers.

3 Add Termination Number ranges, Event Counters, Tariff Codes and Number Restrictions, as required.

4 Make private Geography, Holiday, and Announcement sets, as required.

5 Allocate a feature node set to the customer, using the Resource Limits tab on the Customer screen.

6 If required, make private Control Plan structures.


For Customers who wish to access ACS themselves, users must be set up.

Each Customer must have at least one User of privilege level 5 to enable them to effectively use the ACS service themselves. When a new Customer is added to ACS, there is an tick box which can be selected to assigns a level 5 user with a user name and password of Administrator. Using this User, the Customer may then provision other Users of privilege level 5 or below as they wish.

Additional Users are set up on the Users tab of the ACS Customer screen.

Important: For security reasons, the first time the Customer uses an application, they should change the default user name and password of the Administrator user. It is important to inform the customer of this.

For Customers who are to be completely managed by the telecommunications provider, the Managed Customer check box should be ticked on the Edit Customer screen. This will allow the Telco to skip the following set-up steps:

1 Set up a privilege level 5 User.

2 Add Termination Ranges for the Customer.

3 Allocate the resources that the Customer may use.

In addition, the Customer will not be able to log onto ACS.

Service Numbers must be assigned to the Customer by the ACS System Administrator. A Customer cannot change their Service Numbers.

Service Numbers are set up in the Service Numbers tab on the ACS Numbers screen.

CLIs must be assigned by the System Administrator. A Customer may not change their CLIs.

CLIs are set up in the CLI Nos. tab on the ACS Numbers screen.


Process overview

Additional info

ACS Customers

Managed users

Add Service Numbers

Add CLIs


Establishing New Customer or Service Provider, Continued


Resources and Sets must be set up to allow Customers to configure some of the Feature Nodes in the CPE. This is done through the ACS screens. Things which are likely to be required include:

Resources (accessed through the Resources Screen of the ACS):

Termination and Default Termination Ranges Number Translation Event Counters Tariff Codes Incoming and Outgoing Number Restrictions

Sets (accessed through the Configuration Screen of the ACS):

Geography Sets Holiday Sets Announcement Sets and Variable Part Announcement Rules


Before ACS Customers may use the system, they must be allocated access to system resources. When a Customer or service provider is created, they are allocated the default number of system resources. This may be changed in the Edit Customer Resource Limits screen, as required. To allow a Customer access to any public sets and Feature Node sets, the appropriate check boxes on this screen must be ticked.

Resources and Sets

Additional info

Allocate resources



Using Feature Nodes

Overview

This chapter explains what a Feature Node is, and how to use them within a control plan.


Feature Node Behaviour ............................................................................... 48 Finding Feature Nodes .................................................................................. 51 Configuring Feature Nodes ........................................................................... 52 Adding Node Comments ............................................................................... 55 Moving Feature Nodes .................................................................................. 56 Copying Feature Nodes ................................................................................ 57 Deleting Feature Nodes ................................................................................ 58 Using the Control Plan Editor ........................................................................ 59 How Feature Nodes are Joined .................................................................... 60

Chapter 4

Introduction

In this chapter



Feature Node Behaviour

When clicking on a feature node, the mouse must not be moving at the time of the click. For best results, hold the mouse still at the place required, then click.

Once a feature node has been placed on the work area, you can quickly find out information about some of its properties. The node's icon incorporates bubble help areas. If you move the mouse pointer over one of these areas an information bubble appears.

Information bubbles reveal:

the node's name,

any comments contained in its properties, and

details of nodes connected to its exit ports.

The name and comment bubble areas are located respectively on the top left and top right corners of the icon.

If a node contains a comment, a yellow box is shown in the icon's top right corner. If the yellow box is not there, the comment information bubble will not appear.

Exit port bubble areas are the dots symbolising exit ports shown at the bottom of the icon. As you pass the mouse pointer over an exit port, the port symbol's colour changes to yellow.

For the icon shown above, information bubbles might appear as shown below.

Tip: For information bubbles to display, you must have enabled the Display Control Plan Bubble Help option under Tools. Refer to Menu options (on page 22).

Once a feature node has been placed on the work area, you can quickly find out information about its inputs. If you click on the icon, an information bubble appears.


Interacting with feature nodes

Bubble help

Input summary bubble


Feature Node Behaviour, Continued


Input summary bubble (continued)

Note: For the information bubble to display:

The node must have inputs.

You must have enabled the Display Node Input Summary Bubble option under Tools. See also Menu options (on page 22).

Note: The input summary bubble will not display for icons shown on a viewing instance of the CPE. You use a viewing instance of the CPE when you inspect a control plan from within a Load Sub Control Plan node's icon. See also Sub control plans (on page 4).

The label at the top left of a node icon can display either the node's name or its number.

Press the N key on the keyboard to change the label from name to number. Press N again to change from number to name.

See also Node numbers (on page 8).

To access the shortcut menu for the node, right-click on the node with the mouse. The shortcut menu is shown below:


Displaying the node number

Node shortcut menu


Feature Node Behaviour, Continued


Here are the options on the shortcut menu.


Node Properties This option will display information about the node in the information bar at the bottom of the screen. This will include:

the node type

the node number (each node in the Control Plan will be assigned a sequential number), and

the validity status of the node (this will be true, if the node has all the data that is required to compile successfully, and false, if the node data is incomplete and so will cause the Control Plan to fail to compile).

The node number is given in any compiler errors, to make corrections of Control Plan errors simple.

Edit Node Data This option will only be available for those nodes that may have a variable number of exits. Those nodes that have a set number of exits will have this option greyed out. If available, this option will display a screen that allows the data to be added to the node. There is a different Edit Node Data screen for each node that requires data.

You can also access this screen by selecting a node and pressing Enter.

For more information, see Configuring Feature Nodes (on page 52).

Edit Node Exits This option allows the number of exits on those nodes that have a configurable number of exits to be modified.

You can also access this screen by selecting a node and pressing Shift+Enter.

For more information, see Configuring Feature Nodes (on page 52).

Delete Node This option will remove the node from the work area.

You can also delete nodes by selecting them and pressing Delete.

For more information, see Deleting Feature Nodes (on page 58).

Node shortcut menu options



Finding Feature Nodes

Follow these steps to find feature nodes in the currently selected Control Plan.

Step Action

1 Either:

select Edit > Find from the menu, or

press Ctrl+F

Result: You see the Search for Feature Nodes screen.

2 Type search criteria in a search field, or select a node name from the Node Type list and click Find.

Result: All nodes matching the search criteria are displayed in the Search Results grid.

3 To select the node, either:

Click on the node record in the grid and click Select, or

Double-click on the node record in the grid.

Result: You are returned to the Control Plan Editor screen and the node is selected.

Example:

Searching for feature nodes



Configuring Feature Nodes

Node data is edited in the node configuration screens. These are specific to each node and are detailed in full in ACS Feature Nodes User Guide, chapter, Nodes in Depth.

Here are the generic features of all node configuration screens.

Feature Description

Node Name All Configure Node screens have a node name that allows the user to give the node an identifying name. These names are for the convenience of the user. They may be up to 50 characters in length, are not required and do not have to be unique. When a node is created, it has a default node name. You may change this as required.

Help Opens the context sensitive help system.

Comments Opens a Comments screen. For more information, see Adding Node Comments (on page 55).

Save Saves changes to the node.

Cancel Closes the window without saving data.


Introduction

Node configuration screen features


Configuring Feature Nodes, Continued


Follow these steps to configure node data.

Step Action

1 Open the node configuration screen for the specific node. An example of the Configure PIN Authorisation screen is shown below.

2 Enter any data that is required by the Control Plan in which the node appears, and/or accept any pre-configured defaults.

3 Click Save.

Result: The edit screen closes and the Feature Node is displayed as a grey icon on the work area.


Configuring node data


Configuring Feature Nodes, Continued


Follow these steps to edit the number of exit branches of a node.

Note: Many feature nodes have a fixed number of exits. This option is unavailable for those nodes.

Step Action

1 Select the node you want to change the number of exits for.

2 Open the Edit Node Structure screen by either:

Pressing Alt+Enter, or

Right-click on node you want to change the number exits for and select Edit Node Exits (if available) from the shortcut menu displayed.

Result: You see the Edit Node Structure screen.

3 In the Branch field, type the number of exits the node should have.

Tip: You can also use the arrows to change the number displayed. The up arrow will increase the displayed number and the down arrow will decrease the displayed number.

4 Click Save.

Result: The Edit Node Structure screen will close. The number of exits on the node will now reflect the number that was entered into the Edit Node Structure screen.

Editing node exits



Adding Node Comments

The Node Comments & Notes screen allows you to enter comments about the node and the data it contains. The comment for each node may be up to 2000 characters in length, but is not required.

There is a Comments button on each Configure Node screen.

Follow these steps to add a comment to a feature node.

Step Action

1 Open the node configuration screen.

2 Click Comments at the bottom of the screen. This opens the following screen.

3 Type the comment, as it should appear in the node bubble help.

4 Click Save.

Introduction

Adding comments



Moving Feature Nodes

Nodes may be moved individually on the work area by clicking on them and dragging to the new location, or may be moved as a group.

When clicking on a feature node, the mouse must not be moving at the time of the click. For best results, hold the mouse still at the place required, then click.

Follow these steps to move nodes.

Step Action

1 Select the node(s) to be moved.

To select a group of nodes:

click on each node to be included in the group while holding down Ctrl on the keyboard

use rubber band selection, or

hold down Ctrl and use the arrow keys to add nodes to the selection.

All nodes that are moved as a group will be moved in relation to the other nodes in the group.

2 With the cursor over one of the selected nodes, drag the node(s) to the new location, by holding down the left mouse button and moving the cursor across the screen.

3 Drop the node(s) in place, by releasing the mouse button.

Introduction

Moving nodes



Copying Feature Nodes

Nodes may be copied and pasted within the work area, either in the same Control Plan or to another Control Plan.

The copy and paste function will copy a selected node or object and paste it in the work area as required. A single node or group of nodes may be copied and pasted, as required.

Follow these steps to copy and paste nodes.

Step Action

1 Select the node(s) to be copied.


click on each node to be included in the group while holding down Ctrl on the keyboard

use rubber band selection, or

hold down Ctrl and use the arrow keys to add nodes to the selection.

2 Either:

select Edit > Copy from the menu,

or press Ctrl+C

to copy the selection.

3 Click on a new location, to select the area where the copied data is required.

4 Either:

select Edit > Paste from the menu,

or press Ctrl+V

to paste the copied node(s) onto the selected area.

Introduction

Copying nodes



Deleting Feature Nodes

Nodes may only be deleted in Graphical mode. Nodes may be deleted from a Control Plan in two ways:

Method 1: Using the right mouse button menu.

Method 2: Deleting selected nodes.

These steps describe one method of deleting a feature node.

Step Action

1 Right-click on the node using the mouse.

Result: You see the shortcut menu.

2 Select Delete Node.

Result: The node is removed from the work area.

Warning: You will not be asked to confirm the deletion.

These steps describe a method of deleting feature nodes.

Step Action

1 Select the node(s) to be deleted.


click on each node to be included in the group while holding down the Ctrl key on the keyboard

use rubber band selection with the mouse, or

hold down Ctrl and use the arrows keys to add nodes to the selection.

2 Delete the node using one of:

the button on the toolbar

the Delete key on the keyboard

the shortcut keys Ctrl+X

Introduction

Method 1

Method 2



Using the Control Plan Editor

To use the Control Plan Editor, the Customer (or the telecommunications provider) must follow the steps below.

Step Action

1 Open the Control Plan Editor.

2 Enter Control Plan data into required Control Plan structures.

3 Compile Control Plans.

4 Assign an ACS Service Number or ACS CLI to each Control Plan.

Once all the Customer-specific data has been set up by the Customer, Control Plans may be built. Control Plans are the flow charts of what happens when a call is made by a caller to the ACS Customer’s Service Number. The nodes that are in the Control Plans and the Control Plan data attached to the nodes make decisions that affect what happens to the call.

Control Plans are built in the Control Plan Editor, which is available as an option on the ACS Main menu.

Once Control Plans have been built, saved and compiled, then they are available within the service. To activate a Control Plan, it must be attached to an ACS Service Number or CLI.

Attaching a Control Plan to an ACS Service Number or CLI puts it into action. A Control Plan may be built, saved and compiled, but unless attached to a Service Number or CLI, will not be used in ACS.

Control Plans are attached to Service Numbers in the Service Numbers tab, and to CLIs in the CLI Nos tab, both of which are on the ACS Numbers screen.

An ACS Customer may not add a new Service Number or CLI, or change their Service Number or CLI, but they may change the Control Plan that is used when the Service Number or CLI is called. A Customer may also change the effective date that is set for the Service Number or CLI to use that Control Plan. This allows a Customer to schedule Control Plans for their Service Numbers or CLIs that will become effective on the specified date.

Procedure

Build Control Plans

Assign ACS Service Number or CLI



How Feature Nodes are Joined

Once placed in the work area feature nodes need to be joined to create the Control Plan flow.

Follow these steps to join together the nodes in the Control Plan.

Step Action

1 Click on a node exit in a node in the call flow.

Result: The node exit will change colour to yellow.

2 Keeping the mouse button down, drag the cursor to the next node in the Control Plan flow and release the mouse button at the node.

Result: The two nodes will be joined by a line.

Tip: To connect all unconnected node exits in the node to a single next node:

press Alt

click on an unconnected exit,

then drag the mouse to the next node in the Control Plan flow,

release the mouse button at the node.

3 Repeat steps 1 and 2 until all nodes in the Control Plan are connected as required.

4 To disconnect two nodes click on the exit that is to be disconnected.

Result: The line connecting the exit to the next node in the Control Plan flow will be removed.

There are two types of connector types:

Bendy Connectors

Straight Connectors

Each of these connectors have advantages and disadvantages, and it is up to the user to determine which connector type suits them best.

The default connector type is Bendy Connectors; to change the display to use Straight connectors do the following:

File Action

sms.html Add the following line to the file: <param name=cpeLineDrawingMechanism

value="ColouredNodeConnectionDrawer">

Result: All users that log on to the system through the SMS application will have Control Plan Editor connectors displayed as Straight connectors.

acs.html Add the following line to the file: <param name=cpeLineDrawingMechanism

value="ColouredNodeConnectionDrawer">

Result: All users that log on directly to the ACS application will have Control Plan Editor connectors displayed as Straight connectors.


Introduction

Joining nodes together

Connector Types


How Feature Nodes are Joined, Continued


Connector Types (continued)

File Action

SMS User Config

Add the following configuration option to the User in the SMS User Management screen. cpeLineDrawingMechanism=ColouredNodeConnectionDra

wer

Result: The user will have Control Plan Editor connectors displayed as Straight Connectors.

By default the system is installed with connectors that will route so that the minimum number of nodes have connectors drawn over top of them. See the example below:


Bendy Connectors


How Feature Nodes are Joined, Continued


The other type of connector are the straight line connectors. Here is the same Control Plan as shown in the Bendy Connectors section, but with straight line connectors:

This type of connector will show the user the input and exit connectors to a node. When a node is selected, all connectors that are inputs to the node are coloured red, and all connectors that are exits from the node are coloured blue. This feature is useful when looking at Control Plans that are larger than a single screen, and allows the user to identify where a connector goes.

Straight Connectors



Creating Control Plans

Overview

This chapter explains how to create Control Plans.

A Control Plan is similar to a flow chart. It defines the decisions and actions made to determine the routing of a call. A Control Plan may consist of multiple different decision points or actions called “feature nodes”. Control Plans are constructed using the Control Plan Editor.


Opening a Control Plan ................................................................................. 64 Creating a New Control Plan Structure ......................................................... 65 Using an Existing Control Plan Structure ...................................................... 66 Adding Control Plan Data .............................................................................. 69 Saving a Control Plan .................................................................................... 70 Creating Public Control Plans ....................................................................... 75 Editing Control Plans ..................................................................................... 76 Deleting Control Plans and Structures .......................................................... 77

Chapter 5

Introduction

In this chapter



Opening a Control Plan

Follow these steps to open an existing Control Plan using the Control Plan Editor.

Step Action

1 From the File menu, select Open.

Result: You see the Open Existing Control Plan screen.

2 Sort the list to display the required selection of available public or private Control Plans.

3 Select the Control Plan name from the list on the left side of the screen.

4 Click Open.

On the left side of the Open Existing Control Plan screen is a list of all Control Plans that are available to the customer. To the right of this list, there are check boxes that allow sorting of Control Plans.

Towards the bottom of the screen, there are two check box options:

Sorting option Description

Open Structure as Read-Only

Where this option is ticked, the Control Plan will open, but you will:

only be able to edit the data of the Control Plan and

not be able to change the structure of the Control Plan.

Open Data as Read-Only

Where this option is ticked, the Control Plan will open, but you will not be able to edit the data of the Control Plan.

The sorting level boxes you can select depend on the permission level of ACS users.

Permission levels Check box access

1 and 2 Both the check boxes are ticked and may not be cleared.

3 Only Open Structure as Read-Only is ticked and may not be cleared.

4, 5 and 6 May clear both boxes.

Opening an existing Control Plan

Sorting Control Plans

Using the sorting option boxes



Creating a New Control Plan Structure

A Control Plan consists of the Control Plan structure and the Control Plan data. The Control Plan structure is a flow chart of Feature Nodes, giving action types that are to be carried out. The Control Plan data is the specific instruction for action at each node decision point.

To make a Control Plan, you must build a Control Plan structure, and then add Control Plan data.

When making a Control Plan, you may build a completely new Control Plan structure or base the Control Plan on an existing structure.

Follow these steps to create a new Control Plan structure.

Step Action

1 On the Control Plan Editor main screen, either:

click the button on the toolbar,

from the File menu, select New, or

press Ctrl+N.

Result: An empty Control Plan appears in the work area.

2 Add the required Feature Nodes to the work area.

For more information on adding nodes, see Adding Feature Nodes.

3 Move the Feature Nodes to the required positions. All nodes must follow in a tree structure from the start node.

4 Join the Feature Nodes together by lines, to form a flow chart.

To create the joining lines: 1 Click on an exit node and, keeping the mouse button pressed,

2 draw a line from one node to another.

3 Release the mouse button.

To delete a join line, click on the exit node it starts from.

All node exits must be connected before the Control Plan is valid.

5 Click the button on the Toolbar, to verify that the Control Plan is complete.

Introduction

Procedure



Using an Existing Control Plan Structure

A Control Plan (or several Control Plans) may be based on an existing structure. This allows a Telco to create a single structure, which may be customised and used by several Customers.

There are two methods for opening a Control Plan from an existing structure:

using the New Plan from Existing Structure option, and

using the Numbers screen in the ACS.

Follow these steps to use an existing Control Plan structure in the Control Plan Editor.

Step Action

1 From the File menu, select New Plan from Existing Structure.

Result: You see the New Control Plan From Existing Structure screen.

2 Sort the list to display the required selection of available public or private Control Plan structures.

3 Select the required Control Plan Structure. If the structure will not require editing, tick the Open Structure as Read-Only check box.

Note: If the Open Structure as Read-Only field is ticked, then the structure of the Control Plan (or Control Plan Template) may not be changed.

4 Click Open.


Introduction

Using a new plan from an existing structure


Using an Existing Control Plan Structure, Continued


The New Control Plan From Existing Structure screen is similar to the Open Existing Control Plan screen. To the left of the screen is a list of all Control Plan Structures on which the Customer may base a new Control Plan. To the right of the list of Control Plan structures are sorting options.

Toward the bottom of the screen is an option to open the structure as read-only.

Sorting Option Description

Open Structure as Read-Only

Ticking this check box will allow a Control Plan to be created based on the selected structure, but the structure may not be changed in any way.

To open the structure and base a new Control Plan on it, sort the list of available Control Plan structures as required, select the Control Plan structure from the list shown and click Open.

You can use the sorting option depending on your Permission level.

Permission levels Check box access

1, 2 and 3 For ACS Users of permission level 3 and below, this check box will be ticked by the system and may not be cleared.

Follow these steps to use an existing Control Plan structure using the ACS Numbers screen.

Step Action

1 Open the ACS application.

2 Click Numbers.

Result: You see the Numbers screen.

3 In either the Service Numbers tab or the CLI Numbers tab, from the Templates grid, choose the Control Plan structure you want to use.

4 If you want to open a new Control Plan and Template, or a just a new Template, click New Template. Go to Step 5.

If you want to open a new Control Plan from a Template (to edit the content or edit the content and structure), click New Control Plan. Go to step 6.

5 A prompt will appear.

If you want a new Control Plan, click Control Plan and Template.

Result: The CPE will start up with a standard Control Plan.

If you want a new Control Plan Template, click Template Only.

Result: The CPE will start up with a Control Plan. You will only be able to save the structure of this Control Plan, not the data.


Sorting Control Plans

Using the sorting option box

Using the ACS Numbers screen


Using an Existing Control Plan Structure, Continued


Using the ACS Numbers screen (continued)

Step Action

6 A prompt will appear.

If you want a new Control Plan, based on the Template where the structure of the Control Plan cannot be changed, click Read Only.

Result: The CPE will start up with a pre-populated Control Plan. You will only be able to save the Call Data, as the Call Structure is being defined in the Template.

If you want a new Control Plan, based on and pre-populated by the Template which you can edit and save as a separate Control Plan, click Writable.

Result: The CPE will start up with a pre-populated Control Plan. You will be able to edit and save both the Call Data and the Call Structure.

For more information about the Numbers screen, see the ACS User Guide.



Adding Control Plan Data

Once the nodes have been placed on the work area, you may add Control Plan data to them, but often it is more convenient to leave this until the structure has been completed.

You can tell at a glance which nodes in the Control Plan need data, because they will be shown with the node background in red. Those nodes that do not require Control Plan Data are shown with the node background coloured grey. In the Edit Node Data screen that is displayed, enter the required data for the node.

Follow these steps to add data to the open Control Plan structure.

Step Action

1 Open the required Control Plan structure, or create a new structure.

2 Following the instructions detailed in the Editing Feature Nodes section, display the configure node screen of each red node in the Control Plan structure.

3 Enter the data required by the specific node, as detailed in the Node Descriptions chapter.

4 Repeat steps 1 and 2, for each red node in the Control Plan structure.

Introduction

Procedure



Saving a Control Plan

When you have finished constructing a Control Plan, you will need to save it. When you save the Control Plan, it is compiled. Consequently, you must have a Control Plan that can be compiled before you can save it.

Only compiled Control Plans may be attached to Service Numbers or CLIs, and so be used by calls.

Note: If the call-plan has red (unconfigured) nodes (e.g. UT that has never been opened), then an error message will display for one of the red nodes:

Information, Node <Node Number> is not configured. Configure

or delete it.

Correct the problem and try saving again.

It is possible to name the Control Plan data and the Control Plan structure differently. Separating the structure and the data in this way will allow the Control Plan structure to be reused for another Control Plan. The Control Plan itself will be referred to by the Control Plan data name.

If a Control Plan is saved with a different Control Plan Structure name, the new Control Plan Structure will be saved and the old Control Plan Structure will still exist. Saving it with the same name will overwrite the old one. The same rule applies to Control Plan Data.

If the Control Plan has been based on an existing structure, the Plan Structure field will be greyed out and will display the name of the structure on which the Control Plan was based.

Both the Control Plan structure and the Control Plan data are saved, and the compiler is then called. The compiler attempts to compile the Control Plan to allow it to be used by a Service Number.

Note: If the Control Plan structure (or Control Plan data) has been opened as read only, the structure (or data) is not saved (it cannot be changed, therefore there is no need to resave it). ACS Users of permission level 3 and above are able to save their Control Plans.

The Control Plan may also be allocated an MF Identifier on the Save Data/Structure screen. This is used in the Activate Control Plan node in dial-up management Control Plans such as the ACS Management Control Plan.

The MF Identifier is not required. It may be up to 8 digits in length and if used, must be unique.


Introduction

Saving with different names

Saving Control Plans

MF Identifier


Saving a Control Plan, Continued


Follow these steps to save a Control Plan.

Step Action

1 On the CPE Main screen, either:

from the File menu, select Save, or

on the toolbar, click the save button .

Result: You see the Save Data/Structure screen.

2 In the Plan Structure field, enter the name for the structure part of the Control Plan. This will also be the default name of any template built from this Control Plan.

Result: The Control Plan Data field will automatically be populated with the name entered in the Plan Structure field.

3 If you want to change the name of the data part of the Control Plan, enter the new name in the Control Plan Data field.

4 If required, enter the MF Identifier for the Control Plan.

5 If you are saving this Control Plan as a public structure, tick the Public Structure check box. For more information, see Creating Public Control Plans (on page 75) for details.

6 If you are making this template available on the ACS Numbers screen, tick the Show in Template Grid check box.

7 If this Control Plan is to be invoked by a third party via WSDL, select the WSDL operation from the Generate WSDL for operation drop down list.

Notes:

This list contains all the known operations for the current customer, as selected in the customer combo box.

After a successful compile, this Control Plan WSDL file can be viewed in the OSD Operations tab. See OSD User and Technical Guide.

This list only appears for SMS users who have been given this capability in a template, and when the OSD package has been installed.


Procedure




Procedure (continued)

Step Action

8 Click Save to save the Control Plan, or Cancel to close the screen without saving the Control Plan.

Tip: Save will not become available until the Control Plan Structure and the Control Plan Data fields have been completed.

Result: The compiler will attempt to compile the Control Plan. For more information about the acsCompilerDaemon, see the ACS Technical Guide.

Once the compiler has attempted to compile the Control Plan, it produces a report. The compiler will first attempt to compile the Control Plan's structure and then will attempt to compile the Control Plan's data. It will display:

1 Beginning Compile messages

2 any errors that are found

3 the status of the compile (that is, Successful or Failed) and,

4 “Finished”.

Note: If, when the Control Plan was saved, the Control Plan Data or Control Plan Structure name entry fields were greyed out, then the compiler will not attempt to compile the part that was greyed out. To have either the Control Plan Data or the Plan Structure name entry fields greyed out, the Control Plan must have been opened with the Structure (or the Data) Read-Only. Because the Structure (or Data) cannot have been changed, it does not need to be compiled.

If there are any errors found in the Control Plan's structure, then the Control Plan's data will also not compile. Any error messages given will include the number of the node that has caused the error to be given. This makes it simple to find the error in the Control Plan and alter it as required.


Compiler report

Compiler report errors




This example shows a compilation report, where both the Control Plan's structure and the Control Plan's data are being compiled and both compiled successfully.

The compiler report may display any of the following notices.

Report Notices Explanations

Waiting for compilation Report The compiler is compiling the Control Plan.

Control Plan Structure Beginning Compile

The compiler is beginning the attempt to compile the Control Plan structure.

Control Plan Structure Compile Successful

The Control Plan structure compiled with no errors.

Control Plan Structure Compile Failed

Errors were found in the Control Plan structure and it could not be compiled.

Error messages will be displayed in the compiler report.

Structure Compilation Complete The attempt to compile the Control Plan structure has been completed.

Control Plan Data Beginning Compile

The compiler is beginning to compile the Control Plan data.

Control Plan Data Compile Successful

The Control Plan data has been compiled with no errors.

Control Plan Data Compile Failed Errors were found in the Control Plan data and it could not be compiled.


Example compiler report

Understanding the compiler report




Understanding the compiler report (continued)

Report Notices Explanations

Data Compilation Complete The attempt to compile the Control Plan data has been completed.

Finished The Control Plan has been compiled successfully.

Click on the Close button The label on this button is Cancel during compilation; once the Control Plan is compiled, it changes to Close.

Once you have compiled the new Control Plan, you will be prompted to see which numbers you want to change to the new Control Plan.

Step Action

1 Specify the numbers you want to have the new Control Plan by ticking the check box next to the required number.

2 Click Apply.

Implementing Control Plan changes



Creating Public Control Plans

Any Control Plans that the System Administrator saves will be available on the Override Control Plan field, in the ACS New Customer screen and the ACS Edit Customer screen.

Public Control Plans are identifiable in the New Control Plan on Existing Structure screen list of Control Plan Structure, by the word (Public) being placed in brackets after the Structure Name.

If the logged on User is the ACS System Administrator (has a privilege level of 6 or 7), they may save the Control Plan structure as a public structure. Any User may use a public Control Plan structure, as a base for their own Control Plans.

The Control Plan Data field is greyed out, as only structures may be saved as public. Control Plan Data may not be public.

Follow these steps to create a public Control Plan.

Step Action

1 Open the Control Plan Editor.

2 Build the Control Plan that is to be public.

3 Open the Save Data/Structure screen.

4 Enter details of the new Control Plan structure, and tick the Public Structure check box.

5 Click Save. The Control Plan structure is now saved as a public Control Plan Structure.

Result: This allows all Customers to make their own Control Plans based on this structure.

Introduction

Saving public Control Plan structures

Creating a public Control Plan



Editing Control Plans

Follow these steps to edit a Control Plan.

Step Action Notes

1 Open Control Plan. For more information, see Opening a Control Plan (on page 64).

2 Select a node to edit. -

3 Either:

Right click on the node and select option Edit Node Data,

Press Enter, or

Double click on node.

The configuration screen will appear.

4 Make changes as required. For more information, see Configuring node data (on page 53).

5 If required, add new nodes. For more information, see Adding Feature Nodes (on page 33).

6 Join any nodes that have unconnected exit points.

For more information, see Graphical interface (on page 9).

7 Save Control Plan. For more information, see Saving a Control Plan (on page 70).

Procedure



Deleting Control Plans and Structures

Follow these steps to delete a Control Plan.

Step Action

1 In the CPE Main screen, from the File Menu, select Delete Data.

Result: You see the Delete Non-Active Control Plan screen.

2 Use sort options to display Control Plan Data as required.

3 Select the Control Plan name from the list on the left side of the screen. You may select Multiple Control Plans to delete at once by using the Shift or Ctrl key when selecting Control Plans.

4 Click Delete.

Result: The following confirmation message is displayed:

5 Click OK.

Result: The screen will close and the Control Plan will be deleted.

Note: Deleting the Control Plan will delete the Control Plan data and, unless specified otherwise, will not attempt to delete the Control Plan Structure.


Deleting Control Plan


Deleting Control Plans and Structures, Continued


Follow these steps to delete a Control Plan structure.

Step Action

1 Ensure Control Plan Editor is in Graphical mode.

2 In the File menu, select Delete Structure.

Result: You see the Delete Unused Structure screen.

3 Use sort options to display Control Plan structures as required.

4 Select the structure to delete.

4 Click Delete.

Result: You see a warning prompt indicating the number of nodes in the Control Plan.

5 Click OK.

Result: The screen will close and the Control Plan structure will be deleted.

Note: A Control Plan structure may only be deleted if it has no Control Plans attached to it.

Deleting Control Plan Structure



User Messages

Overview

This chapter describes possible warning messages generated by the system and displayed to the user. These user messages are informative only and are not entered into the system alarm log.


CPE Compiler Errors ..................................................................................... 80

Chapter 6

Introduction

In this chapter



CPE Compiler Errors

This table defines the compiler error messages for the Control Plan Editor. These messages are listed in alphabetic order.

Error Text Function Reason Advice

Data in

ACS_COMPILE_L

IST is

invalid

compileCallPlans The compiler found an invalid row in the compile list.

This is a non-fatal error. However, it may signal a deeper problem.

Contact Technical Support.

Data selected

from Oracle

was shortened

getFNMapping, getRegion, getHoliday, getCallPlanStructureNode, getCompiledCallPlanStructure, getCallPlanDataNode, getCompiledCallPlanData, getAnnouncementInformationString, findStructure, findCPDID,

The compiler has had difficulty retrieving information from the database.


Compiled

Structure too

large, Max

65535 bytes

updateCompiledCallPlanStructure, updateCompiledCallPlanData

The compiler has reached the internal limit on the compiled size of a Control Plan.


connect_flag:

Cannot read

config file.

connect_flag The compiler was unable to read the configuration file during a connection attempt.

The permissions on the configuration file or the ACS tree may be incorrect. Verify that it is readable by the ACS compiler account.


Failed to

connect to

ORACLE as

user: X.

connect_flag The compiler was unable to connect to the database as the specified user.

Either the Oracle Username/Password is incorrect, the Oracle environment variables are incorrect or the database isn’t running. Verify these using SQL*Plus and fix, or contact Technical Support.

Invalid data

was selected

from the

database

compileCallPlans The compiler has had difficulty selecting information from the database.



Message list


CPE Compiler Errors, Continued


Message list (continued)


Startup

Successful main The compiler

daemon process started successfully and is ready to process compilation requests.

This a notification message only.

Unable to

catch SIGABRT set_catch The process was not

allowed to setup a signal handler for SIGABRT signals.

This is not a fatal error. However, it will result in the compiler being unable to shutdown cleanly upon receiving a SIGABRT.


Unable to

catch SIGHUP set_catch The process was not

allowed to setup a signal handler for SIGHUP signals.

This is not a fatal error. However, it will result in the compiler being unable to re-read its configuration file upon receiving a SIGHUP.


Unable to

catch SIGTERM set_catch The process was not

allowed to setup a signal handler for SIGTERM signals.

This is not a fatal error. However, it will result in the compiler being unable to shutdown cleanly upon receiving a SIGTERM.


Unable to

Connect to

Oracle

main The compiler was unable to login to Oracle using the supplied username/password.




CPE Compiler Errors, Continued


Message list (continued)


Unable to

connect to

Oracle

acsCompilerDBConnection The compiler was unable to login to Oracle using the supplied username/password.


Unable to

fork child

process

main The compiler was unable to startup in Daemon mode. The fork attempt failed.


Unable to

handle Signal cleanup, restart The process

attempted to handle a signal it does not expect to handle.


Unable to

mask Signals maskSignals The compiler was

unable to mask signals before executing Oracle commands.

This is not a fatal error, however it may result in failed compiles because of signals.


Unable to

unmask

Signals

unmaskSignals The compiler was unable to unmask signals after executing Oracle commands.

This is not a fatal error, however it may result in the compiler ignoring signals (i.e. unable to shutdown cleanly, or re-read its configuration file).




Appendix

Overview

This appendix contains the following topics.

Glossary of Terms ......................................................................................... 85 Index .............................................................................................................. 87

In this appendix



Glossary of Terms

Advanced Control Services configuration platform.

Automatic Number Identification - Term used in the USA by long distance carriers for CLI.

Calling Line Identification - the telephone number of the caller. Also referred to as ANI.

Control Plan Editor (previously Call Plan Editor) - software used to define the logic and data associated with a call - e.g. "if the subscriber calls 0800 nnnnnn from a phone at location xxx then put the call through to bb bbb bbbb".

Graphical User Interface

HyperText Markup Language, a small application of SGML used on the World Wide Web.

It defines a very simple class of report-style documents, with section headings, paragraphs, lists, tables, and illustrations, with a few informational and presentational items, and some hypertext and multimedia.

Intelligent Network

Oracle Corporation

Personal Identification Number

Standard Generalized Markup Language. The international standard for defining descriptions of the structure of different types of electronic document.

Service Independent Building Block

Depending on context, either:

Short Message Service, or

Service Management Server.

Short Message Service Centre - stores and forwards a short message to the indicated destination subscriber number.

Structured Query Language - a database query language.

The person(s) responsible for the overall set-up and maintenance of the IN.

Telecommunications Provider. This is the company that provides the telephone service to customers.

See Telco.

The final number that a call terminates to. Can be set in control plan nodes such as Attempt Termination and Unconditional Termination for re-routing numbers such as Toll Free or Follow Me numbers.

ACS

ANI

CLI

CPE

GUI

HTML

IN

Oracle

PIN

SGML

SIB

SMS

SMSC

SQL

System Administrator

Telco

Telecommunications Provider

Termination Number



The Virtual Private Network product is an enhanced services capability enabling private network facilities across a public telephony network.

Web Services Description Language.

VPN

WSDL



A

About this Document Audience • v Changes in this document • v Prerequisites • v Related documents • v Scope • v

Accessing the Control Plan Editor ACS Numbers Screen • 12 Introduction • 12 Signing on • 12

ACS • v ACS Control Plans

What is a Control Plan? • 4 ACS Customers

Establishing New Customer or Service Provider • 44

ACS Numbers Screen Accessing the Control Plan Editor • 12

Add CLIs Establishing New Customer or Service

Provider • 44 Add Service Numbers

Establishing New Customer or Service Provider • 44

Adding comments Adding Node Comments • 55

Adding Control Plan Data Introduction • 69 Procedure • 69

Adding feature nodes • 76 Using the Feature Palette • 33

Adding feature nodes using keyboard • 8 Keyboard Navigation • 36, 39

Adding Node Comments • 52 Adding comments • 55 Introduction • 55

Adding nodes using the mouse Using the Feature Palette • 34

Additional info Establishing New Customer or Service

Provider • 44, 45 Establishing Sets and Structures • 42, 43

Additional set up info Establishing Sets and Structures • 42

Allocate resources Establishing New Customer or Service

Provider • 45 ANI • 85 Assign ACS Service Number or CLI

Using the Control Plan Editor • 59

A,(continued)

Assigning sets to customers Establishing Sets and Structures • 42

Audience About this Document • v

B

Base nodes • 31 Before making public call plan structures

Establishing Sets and Structures • 42 Bendy Connectors

How Feature Nodes are Joined • 61 Bubble help • 5, 22

Feature Node Behaviour • 48 Build Control Plans

Using the Control Plan Editor • 59

C

Changes in this document About this Document • v

CLI • 18 Compiler report

Saving a Control Plan • 72 Compiler report errors

Saving a Control Plan • 72 Configuring Feature Nodes • 50

Configuring node data • 53 Editing node exits • 54 Introduction • 52 Node configuration screen features • 52

Configuring node data • 9, 76 Configuring Feature Nodes • 53

Configuring the Postscript print options Printing Control Plans • 25

Configuring the Sun print options Printing Control Plans • 24

Connector Types How Feature Nodes are Joined • 60

Control Plans and Structures File Menu • 15

Copying Feature Nodes • 20 Copying nodes • 57 Introduction • 57

Copying nodes Copying Feature Nodes • 57

CPE • v CPE Compiler Errors

Message list • 80 CPE Edit menu

Edit Menu • 20 CPE File menu

File Menu • 15

Index



C,(continued)

CPE Screen Viewing the Main Screen • 13

CPE Tools menu Tools Menu • 21

Creating a New Control Plan Structure • 16 Introduction • 65 Procedure • 65

Creating a public Control Plan Creating Public Control Plans • 75

Creating Public Control Plans • 71 Creating a public Control Plan • 75 Introduction • 75 Saving public Control Plan structures • 75

D

Data collection What is the Control Plan Editor? • 2

Data Operations nodes • 31 Default data

What is a Feature Node? • 7 Deleting Control Plan

Deleting Control Plans and Structures • 77 Deleting Control Plan Structure

Deleting Control Plans and Structures • 78 Deleting Control Plans and Structures • 18

Deleting Control Plan • 77 Deleting Control Plan Structure • 78

Deleting Feature Nodes • 50 Introduction • 58 Method 1 • 58 Method 2 • 58

Description Using the Feature Palette • 31 Using the Toolbar • 29 What is a Control Plan? • 4 What is the Control Plan Editor? • 2

Displaying the node number Feature Node Behaviour • 49

Document Conventions Icons • vi Typographical conventions • vi

E

Edit Menu CPE Edit menu • 20 Edit Menu options • 20 Introduction • 20

Edit Menu options Edit Menu • 20

Editing Control Plans Procedure • 76

Editing node exits Configuring Feature Nodes • 54

E,(continued)

Editing nodes Using the Mouse • 28

Establishing New Customer or Service Provider ACS Customers • 44 Add CLIs • 44 Add Service Numbers • 44 Additional info • 44, 45 Allocate resources • 45 Managed users • 44 Process overview • 44 Resources and Sets • 45

Establishing Sets and Structures Additional info • 42, 43 Additional set up info • 42 Assigning sets to customers • 42 Before making public call plan structures •

42 Making public announcement sets • 42 Making public Control Plan structures • 43 Making public geography sets • 43 Making public holiday sets • 42 Set up feature node sets • 42

Events nodes • 31 Example 1

What is a Global Control Plan? • 10 Example 2

What is a Global Control Plan? • 10 Example compiler report

Saving a Control Plan • 73 Example control plan

What is the Control Plan Editor? • 3 Example feature palette

Using the Feature Palette • 31 Export Control Plan screen

File Menu • 19 eyboard shortcut keys

Keyboard Navigation • 35

F

Feature Node Behaviour Bubble help • 48 Displaying the node number • 49 Input summary bubble • 48 Interacting with feature nodes • 48 Node shortcut menu • 49 Node shortcut menu options • 50

File Menu Control Plans and Structures • 15 CPE File menu • 15 Export Control Plan screen • 19 File Menu options • 16 Import Control Plan screen • 18 Importing and exporting Control Plans • 18 Introduction • 15



F,(continued)

Naming Conventions and Control Plan information • 15

Screen selections • 15 File Menu options

File Menu • 16 Finding Feature Nodes • 20

Searching for feature nodes • 51

G

Graphical interface • 76 What is a Feature Node? • 9

GUI • 9

H

How Feature Nodes are Joined • 9 Bendy Connectors • 61 Connector Types • 60 Introduction • 60 Joining nodes together • 60 Straight Connectors • 62

HTML • vi

I

Icons Document Conventions • vi

Implementing Control Plan changes Saving a Control Plan • 74

Import Control Plan screen File Menu • 18

Importing and exporting Control Plans File Menu • 18

IN • v Input summary bubble • 5, 22

Feature Node Behaviour • 48 Interacting with feature nodes

Feature Node Behaviour • 48 Interaction nodes • 32 Introduction

Accessing the Control Plan Editor • 12 Adding Control Plan Data • 69 Adding Node Comments • 55 Configuring Feature Nodes • 52 Copying Feature Nodes • 57 Creating a New Control Plan Structure • 65 Creating Public Control Plans • 75 Deleting Feature Nodes • 58 Edit Menu • 20 File Menu • 15 How Feature Nodes are Joined • 60 Keyboard Navigation • 35, 38 Moving Feature Nodes • 56 Printing Control Plans • 24 Saving a Control Plan • 70 Tools Menu • 21

I,(continued)

Using an Existing Control Plan Structure • 66

Using the Mouse • 28 What is a Feature Node? • 7 What is a Global Control Plan? • 10

J

Joining nodes together How Feature Nodes are Joined • 60

K

Keyboard Navigation Adding feature nodes using keyboard • 36,

39 Introduction • 35, 38 Keyboard shortcut keys • 35, 38 Navigating around node configuration

screens • 35, 38 Keyboard shortcut keys • 33

Keyboard Navigation • 38

M

Main screen Viewing the Main Screen • 13

Making public announcement sets Establishing Sets and Structures • 42

Making public Control Plan structures Establishing Sets and Structures • 43

Making public geography sets Establishing Sets and Structures • 43

Making public holiday sets Establishing Sets and Structures • 42

Managed users Establishing New Customer or Service

Provider • 44 Menu options • 48, 49

Tools Menu • 22 Message list

CPE Compiler Errors • 80 Method 1

Deleting Feature Nodes • 58 Method 2

Deleting Feature Nodes • 58 MF Identifier

Saving a Control Plan • 70 Moving Feature Nodes

Introduction • 56 Moving nodes • 56

Moving nodes Moving Feature Nodes • 56 Using the Mouse • 28



N

Naming conventions and activating plan What is a Global Control Plan? • 11

Naming Conventions and Control Plan information File Menu • 15

Navigating around node configuration screens • 35, 38 Keyboard Navigation • 35, 38

Network nodes • 32 Node

name • 7, 35 number • 7, 8, 35 select all exits • 35, 60

Node configuration screen features Configuring Feature Nodes • 52

Node features What is a Feature Node? • 7

Node numbers • 49 What is a Feature Node? • 8

Node shortcut menu Feature Node Behaviour • 49

Node shortcut menu options Feature Node Behaviour • 50

NTS nodes • 32 Number nodes • 32

O

Opening a Control Plan • 16, 76 Opening an existing Control Plan • 64 Sorting Control Plans • 64 Using the sorting option boxes • 64

Opening an existing Control Plan Opening a Control Plan • 64

Oracle • ii Others nodes • 33

P

Pending TN nodes • 33 PIN • 2 Prefix Trees nodes • 33 Prerequisites

About this Document • v Printing a Control Plan

Printing Control Plans • 24 Printing a Control Plan - Postscript

Printing Control Plans • 25 Printing Control Plans • 17

Configuring the Postscript print options • 25 Configuring the Sun print options • 24 Introduction • 24 Printing a Control Plan • 24 Printing a Control Plan - Postscript • 25 Printing progress • 26

P,(continued)

Printing progress Printing Control Plans • 26

Procedure Adding Control Plan Data • 69 Creating a New Control Plan Structure • 65 Editing Control Plans • 76 Saving a Control Plan • 71 Using the Control Plan Editor • 59

Process overview Establishing New Customer or Service

Provider • 44

R

Related documents About this Document • v

Resources and Sets Establishing New Customer or Service

Provider • 45 Restrictions • 6

S

Saving a Control Plan • 17, 76 Compiler report • 72 Compiler report errors • 72 Example compiler report • 73 Implementing Control Plan changes • 74 Introduction • 70 MF Identifier • 70 Procedure • 71 Saving Control Plans • 70 Saving with different names • 70 Understanding the compiler report • 73

Saving Control Plans Saving a Control Plan • 70

Saving public Control Plan structures Creating Public Control Plans • 75

Saving the global Control Plan What is a Global Control Plan? • 11

Saving with different names Saving a Control Plan • 70

Scope About this Document • v

Screen features Viewing the Main Screen • 14

Screen selections File Menu • 15

Searching for feature nodes Finding Feature Nodes • 51

Set up feature node sets Establishing Sets and Structures • 42

SGML • 85 Shortcut keys

What is a Feature Node? • 8 SIB • 10



S,(continued)

Signing on Accessing the Control Plan Editor • 12

SMS • vi SMSC • v Sorting Control Plans

Opening a Control Plan • 64 Using an Existing Control Plan Structure •

67 SQL • 80 Straight Connectors

How Feature Nodes are Joined • 62 Structure and data

What is a Control Plan? • 4 Sub control plans • 49

What is a Control Plan? • 4 System Administrator • 14

T

Telco • 2 Telecommunications Provider • 85 Termination Number • 44 Time nodes • 33 Toolbar

Using the Toolbar • 29 Toolbar buttons

Using the Toolbar • 29 Toolbar Control Plan display information

Using the Toolbar • 30 Tools Menu

CPE Tools menu • 21 Introduction • 21 Menu options • 22

Typographical conventions Document Conventions • vi

U

Understanding the compiler report Saving a Control Plan • 73

Update interval What is a Global Control Plan? • 11

User interface and functionality What is the Control Plan Editor? • 2

Using a new plan from an existing structure Using an Existing Control Plan Structure •

66 Using an Existing Control Plan Structure • 17

Introduction • 66 Sorting Control Plans • 67 Using a new plan from an existing structure

• 66 Using the ACS Numbers screen • 67 Using the sorting option box • 67

U,(continued)

Using the ACS Numbers screen Using an Existing Control Plan Structure •

67 Using the Control Plan Editor

Assign ACS Service Number or CLI • 59 Build Control Plans • 59 Procedure • 59

Using the Feature Palette Adding feature nodes • 33 Adding nodes using the mouse • 34 Description • 31 Example feature palette • 31

Using the Mouse Editing nodes • 28 Introduction • 28 Moving nodes • 28

Using the sorting option box Using an Existing Control Plan Structure •

67 Using the sorting option boxes

Opening a Control Plan • 64 Using the Toolbar • 14

Description • 29 Toolbar • 29 Toolbar buttons • 29 Toolbar Control Plan display information •

30

V

Viewing instance • 5 Viewing the Main Screen

CPE Screen • 13 Main screen • 13 Screen features • 14

VPN • 10

W

What is a Control Plan? ACS Control Plans • 4 Description • 4 Structure and data • 4 Sub control plans • 4

What is a Feature Node? Default data • 7 Graphical interface • 9 Introduction • 7 Node features • 7 Node numbers • 8 Shortcut keys • 8



W,(continued)

What is a Global Control Plan? Example 1 • 10 Example 2 • 10 Introduction • 10 Naming conventions and activating plan •

11 Saving the global Control Plan • 11 Update interval • 11

What is the Control Plan Editor? Data collection • 2 Description • 2 Example control plan • 3 User interface and functionality • 2

WSDL • 71

Documents

Oracle Communications Network Charging and Control Control … · feature node. For example, a day-of-week feature node has multiple output paths. The current day-of-week determines