::RESORSYS::Business application for Telecom Billing Solution, Bespoke Development, Business Consulting, Outsourcing Solutions

Page 1

BillNet Telecom Billing System User Guide

Optivity Telephony Manager

Telecom Billing System

User Guide

Document Number: P0910103

Document Release: Standard 1.0

Date: July 2000

Year Publish FCC TM

� 2000 Nortel Networks

Printed in the United States of America

Information is subject to change without notice. Nortel Networks reserves the right to make changes in design

or components as progress in engineering and manufacturing may warrant. This equipment has been tested

and found to comply with the limits for a Class A digital device pursuant to Part 15 of the FCC rules, and the

radio interference regulations of Industry Canada. These limits are designed to provide reasonable protection

against harmful interference when the equipment is operated in a commercial environment. This equipment

generates, uses and can radiate radio frequency energy, and if not installed and used in accordance with the

instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a

residential area is likely to cause harmful interference in which case the user will be required to correct the

interference at their own expense.

SL-1 and Meridian 1 are trademarks of Nortel Networks. Microsoft, MS, MS-DOS, Windows, and Windows NT

are registered trademarks of Microsoft Corporation. All other trademarks and registered trademarks are the

property of their respective owners.

Page 2

Page 3

iii

BillNet Telecom Billing System User Guide

Revision history

Release Date

Document Version

Product Release

July 2000

Standard 1.0

1.0

Page 4

P0910103 Standard 1.0 July 2000

Page 5

BillNet Telecom Billing System User Guide

Contents

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CDR data collection options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

About this user guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Conventions used in this user guide . . . . . . . . . . . . . . . . . . . . . . . .

Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Anatomy of a call record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Meridian 1 outputs call records . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The Telecom Billing System collects call records . . . . . . . . . . . . .

The Telecom Billing System costs call records . . . . . . . . . . . . . . .

Setting up the Telecom Billing System: Example scenario . . . . . . . . .

Setting up the Telecom Billing System: Summary . . . . . . . . . . . . . . .

Step 1: Ensure that Meridian 1 is set up properly . . . . . . . . . . . . . . . .

Select CDR output format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Auxiliary Identification output in CDR record . . . . . . . . . . . . . . . .

Configure routes for CDR output . . . . . . . . . . . . . . . . . . . . . . . . . .

Step 2: Install and set up buffer unit . . . . . . . . . . . . . . . . . . . . . . . . . .

Security precautions for MDR-2000 ISD . . . . . . . . . . . . . . . . . . . .

Connect MDR-2000 ISD to Meridian 1 and PC . . . . . . . . . . . . . . .

Changing communications parameters . . . . . . . . . . . . . . . . . . . . . .

Step 3: Install rate tables and location books . . . . . . . . . . . . . . . . . . . .

Step 4: Run Telecom Billing System so it can be configured . . . . . . .

Step 5: Set up and test data collection . . . . . . . . . . . . . . . . . . . . . . . . .

Page 6

BillNet Telecom Billing System User Guide

Enter data collection parameters . . . . . . . . . . . . . . . . . . . . . . . . . . .

Test data collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Step 6: Obtain LTM from Meridian 1 . . . . . . . . . . . . . . . . . . . . . . . . .

Step 7: Set up Telephone Configuration . . . . . . . . . . . . . . . . . . . . . . .

Summary of steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Access Telephone Configuration Database editor . . . . . . . . . . . . .

Update Call Type Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Define Carrier Pricing Templates . . . . . . . . . . . . . . . . . . . . . . . . . .

Define Call Digit Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Enter Telephone Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Step 8: Test telephone configuration . . . . . . . . . . . . . . . . . . . . . . . . . .

Apply costs to call records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Generate reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Update databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Operating Procedures . . . . . . . . . . . . . . . . . . . . . . . 45

Schedule of activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Data collection (daily) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Data collection troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Costing of call records (daily) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Report generation (monthly) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Step 1: Select report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Step 2: Select output device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Step 3: Select report filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Step 3: Generate report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Database updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Employee Database (weekly) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Page 7

vii

BillNet Telecom Billing System User Guide

External Parties and Roles/Projects Databases (weekly) . . . . . . . .

Telephone Configuration Database (monthly) . . . . . . . . . . . . . . . .

Location Books (quarterly) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Rate Tables (quarterly) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Database management (weekly) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Backup Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Restore Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Call Database maintenance (monthly) . . . . . . . . . . . . . . . . . . . . . . . . .

Archive Call Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Purge Call Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Restore Call Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Summary of tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Daily tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Ongoing tasks (recommended weekly) . . . . . . . . . . . . . . . . . . . . . .

Monthly tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Quarterly tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

User�s Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Panes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

File menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Edit menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Organizational Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Employees . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

External Parties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Page 8

viii

BillNet Telecom Billing System User Guide

Roles/Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Asset Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Telephone Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Location Books . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Rate Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Taxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Call Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

View menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Tools menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Costing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Options menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

List of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Page 9

BillNet Telecom Billing System User Guide

List of figures

Figure 1

System block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2

Sample System setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3

Sample call record allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4

Meridian 1 to MDR-2000 ISD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 5

MDR-2000 ISD to modems to PC . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 6

MDR-2000 ISD status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 7

BillNet Navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 8

Telecom Billing System main window . . . . . . . . . . . . . . . . . . . . . . . .

Figure 9

Call Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 10

Telephone Configuration Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 11

Call Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 12

Carrier Pricing Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Page 10

List of figures

P0910103 Standard 1.0 July 2000

Figure 13

Carrier Pricing Template: International Calls . . . . . . . . . . . . . . . . . . .

Figure 14

Carrier Pricing Template: Long Distance (National) Calls . . . . . . . . .

Figure 15

Telephone Configuration editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 16

Telephone Configuration - Node editor . . . . . . . . . . . . . . . . . . . . . . . .

Figure 17

Telephone Configuration - Service Definition . . . . . . . . . . . . . . . . . .

Figure 18

Telecom Billing System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 19

System Tasks pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 20

System Monitor pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 21

System Alarm pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 22

Reporting dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 23

Telephone Configuration Database editor . . . . . . . . . . . . . . . . . . . . . .

Page 11

Page 1 of 78

BillNet Telecom Billing System User Guide

Introduction

Welcome to the Telecom Billing System, the Optivity Telephony Manager's

costing and billing application. The Telecom Billing System helps monitor

and control telecom costs for your telephone system. It collects call records

from your Meridian 1, allocates costs to the appropriate users and generates

detail and summary reports outlining these costs. The reports provide details

on the actual usage of your telephone system and allow you to assess the

effectiveness of your telephone services.

The Telecom Billing System collects data from your Meridian 1 either

through a buffer device or through a direct connection. Using defined

communications and collection parameters, the Telecom Billing System

communicates with the Meridian 1 to collect the necessary telephone usage

data. In order for the Telecom Billing System to communicate with the

Meridian 1 and collect data, the Meridian 1 must be equipped with a suitable

CDR port.

This user guide provides basic information on setting up and running the

Telecom Billing System. Along with a brief outline of its main functions, this

user guide also contains examples and procedures to assist you in setting up

the Telecom Billing System. This user guide assumes that you have user-level

knowledge of the Windows� 95 and Windows� NT V4.0 operating

systems. In order to ensure optimum operation of this application, read the

material in this user guide before attempting to run it.

Overview

The Telecom Billing System supports the Meridian line of telephone

switches. The Meridian 1 must be equipped with a suitable CDR port for

proper connection to the PC or CDR buffer unit.

Page 12

Page 2 of 78

Introduction

P0910103 Standard 1.0 July 2000

Once you collect the call records either directly from the Meridian 1 or from

the CDR buffer unit, the records must be costed, collated, sorted and printed

on a report. This call detail information will help you achieve the following

goals.

� The system provides details on the actual telephone usage. Management

can isolate individual users and departments who are not properly

utilizing the telephone system through misuse or neglect.

� It provides usage details for cost allocation within the organization or for

client billing purposes.

� Management can use the information to determine which telephone

company services are not being utilized. This analysis will allow you to

adjust your telephone services to suit your needs resulting in a savings to

your organization.

CDR data collection options

The Telecom Billing System can collect CDR data from the Meridian 1 in

several ways:

� It can collect CDR data directly from the Meridian 1 to its databases,

� It can collect CDR data through the BillNet Data Buffering and Access

(DBA) application or

� It can collect CDR data through a buffer unit.

The DBA application and the optional buffer units can be used to

continuously collect CDR data from the Meridian 1 and store the data for later

collection and processing by the Telecom Billing System. CDR data is saved

to system-specific files so that multiple DBA�s or buffer units (multiple

Meridian 1 switches) can be supported concurrently by the Telecom Billing

System. For a complete list of script files used for communications and data

collection, refer to Appendix A: Script File Summary of the Common Services

User Guide. For more information about the DBA application, refer to the

Data Buffering and Access section of the Common Services User Guide.

Where required, buffer units can connect to each Meridian 1 via its RS-232

port and connect to the PC using a supported modem. It is recommended that

the buffer unit contains battery backup power in the event of a power failure.

Refer to the buffer unit�s reference documentation for more information.

Page 13

Introduction

Page 3 of 78

BillNet Telecom Billing System User Guide

Note: It is recommended that you use either the DBA application or a

buffer unit for CDR data collection. If you use one of these devices, the

CDR data will be collected and securely stored for later retrieval by the

Telecom Billing System. Although the DBA or buffer units are not

required to properly use the Telecom Billing System, these options are

recommended in order to securely store the CDR data. If you choose to

collect the CDR data directly to the PC without the use of the DBA or

buffer unit, then you may lose data if the PC is accidentally rebooted or

shut down.

About this user guide

This user guide is intended to provide you with an introduction to the Optivity

Telephony Manager (BillNet) Telecom Billing System application as wellas an

overview of its major functions. It discusses how you can best use it to easily

manage CDR data, update its databases and generate meaningful reports. It

includes a schedule of routine operations and a sample setup to assist you in

configuring your version of the Telecom Billing System.

Conventions used in this user guide

This user guide uses the following terms:

� Computer system refers to the hardware and software of an IBM-PC� or

100% compatible PC.

� Windows refers to Microsoft

�

Windows

�

95 and Windows NT

�

V4.0.

� Mouse refers to any standard PC pointing device. Common mouse

actions include point, click, right-click and double-click.

� Standard Windows terminology includes: icon, window, dialog box (or

dialog) and menu.

� Angle brackets denote a single keyboard key. For example, <Esc>

denotes the Escape key, labeled Esc on PC keyboards. Angle brackets

with multiple keys denote keyboard keys to use simultaneously. For

example, <Ctrl-Alt-Del> denotes the key sequence for rebooting a PC.

�

This font

is used to designate buttons, menu choices and information you

are to enter.

Page 14

Page 4 of 78

Introduction

P0910103 Standard 1.0 July 2000

Help

This user guide does not discuss each Telecom Billing System function and

command in detail. It only discusses the major functions and how they are

accessed. For detailed information on each Telecom Billing System function,

use the on-line Help function. You can use the Help function to obtain help

for topics either directly or via its index and word-search functions. While

running the Telecom Billing System, you can obtain context-sensitive help on

any topic you require by simply clicking

Help

from a specific dialog or

window.

To obtain help for a topic, click

Help

from the currently-selected dialog or

window. This will access the Windows Help function and display

context-sensitive help information on the current topic.

Once you have accessed Help, use it to scroll through the other Telecom

Billing System help topics, search for a specific topic or print the help

information.

To view a list of Help topics for the Telecom Billing System, click

Contents

from the Help drop-down menu. Choose from one of the items in this list to

load the Help file and display its information.

Page 15

Page 5 of 78

BillNet Telecom Billing System User Guide

Getting Started

This chapter describes how to access the Telecom Billing System and set it

up for initial use. Using the instructions and examples in this chapter, you will

be able to configure the Telecom Billing System to collect and process the

call detail recording (CDR) records which are output from your Meridian 1.

This chapter includes:

� An overview of a call record and how the Telecom Billing System

applies costs to it,

� The options which you must activate in the Meridian 1 switch to allow

for CDR data collection,

� How to connect and set up a CDR buffer unit, specifically the

MDR-2000 Intelligent Storage Device (ISD),

� How to run the Telecom Billing System for a system,

� How to set up and start data collection for the Telecom Billing System

and

� How to set up the Telecom Billing System Telephone Configuration

Database (including entering node information, rate tables and location

books).

The instructions and examples in this chapter are intended to assist you in

setting up the Telecom Billing System for your own configuration. Since each

telephone system is configured differently and each BillNet installation is

different, these examples cannot predict every scenario. You should therefore

use these examples to teach yourself how to set up your hardware, and

configure the Telecom Billing System software to work with this hardware.

These examples were designed to account for the majority of cases and will

provide you with valuable assistance in getting started.

Page 16

Page 6 of 78

Getting Started

P0910103 Standard 1.0 July 2000

Before using the Telecom Billing System, you must install and configure it as

part of the Optivity Telephony Manager (BillNet) system. Refer to Getting

Started in the BillNet Common Services User Guide for complete details on

installing the Telecom Billing System as part of BillNet and assigning it to a

site and a system.

Anatomy of a call record

Before you enter your system configuration and update your Telecom Billing

System databases, you should first understand the nature of the data which is

output from the Meridian 1. This will help you to construct your system

configuration databases to match your system. This section describes the

components of a call record as well as how it is processed and costed by the

Telecom Billing System.

CDR call records which are output from the Meridian 1 and are collected by

the Telecom Billing System contain the key information to producing costing

reports. The following is a summary of what happens to a call record.

Meridian 1 outputs call records

When a user places or receives a telephone call, the Meridian 1 records its

information as a CDR record (call record). This record contains such

information as the call�s start date and time, its duration, the trunk it went out

on, its associated line and the digits dialed. This data is sent to the Meridian 1

CDR port. From here, an application or hardware device must record it so it

can be processed. This could be a buffer unit which is connected to the

Meridian 1�s CDR port (recommended) or even a PC running the Telecom

Billing System for a direct connection.

As call records are output from the Meridian 1, the Telecom Billing System

collects this data either through a buffer unit such as the MDR-2000 ISD or

directly to the PC. Buffer units are recommended for collecting CDR data

since they can continuously collect and safely store these call records. A

buffer unit is portable enough to be located close to the Meridian 1. Some

may also have security features to allow for safe data storage (e.g., battery

backups). Whichever way you decide to collect the call records, remember

that unless something is collecting the call records output from the

Meridian 1, they will be lost.

Page 17

Getting Started

Page 7 of 78

BillNet Telecom Billing System User Guide

The following schematic displays the movement of a call record from the

Meridian 1 through a buffer unit to the Telecom Billing System software

program on a PC. Notice that modems can be used to communicate with the

Meridian 1 and buffer units from distant locations.

The example in the above schematic represents a single �System�. This

system usually represents a Meridian 1 or physical location in the Telecom

Billing System software, and contains the actual database files for it. Before

attempting to use the Telecom Billing System, you must add it as an

application to the appropriate system.

The following is an example of how the System would be set up.

Figure 1

System block diagram

Page 18

Page 8 of 78

Getting Started

P0910103 Standard 1.0 July 2000

The Telecom Billing System collects call records

The Telecom Billing System collects call records from your Meridian 1

through the buffer unit and formats and appends them to the end of the Call

Database. The Call Database is an indexed collection of call records which

reflects the calling activity of the Meridian 1.

The following is a breakdown of the information found in each call record.

Notice how the Telecom Billing System databases uses each component of

the call record.

Figure 2

Sample System setup

Page 19

Getting Started

Page 9 of 78

BillNet Telecom Billing System User Guide

The Telecom Billing System costs call records

Once the Telecom Billing System collects the call records, it runs them

through a series of calculations to apply costs to them. It then stores these

costed call records in the Call Database. Each process uses the parameters

stored in the Telephone Configuration Database (you will see how to

configure these later in this chapter).

The following is a summary of how the call records are processed.

The Call Digit Translation table of the Telephone Configuration

Database translates the digits dialed to remove or edit any access codes.

The Telecom Billing System looks up the trunk the call went out on to

see which service definition to check. It looks this up in the Telephone

Configuration Database's Service Definition table.

The Telecom Billing System applies any minimum call duration and

network connect time adjustment values to the call.

Figure 3

Sample call record allocation

Page 20

Page 10 of 78

Getting Started

P0910103 Standard 1.0 July 2000

The Telecom Billing System identifies the Carrier Pricing Template

assigned to the trunk. This indicates: the type of call it is; how the number

should be formatted on the report; and which rate structure should be

used to cost it.

The Telecom Billing System applies any fixed costs to the call.

This completes the overview of how the Telecom Billing System processes a

call record.

Setting up the Telecom Billing System: Example scenario

The example setup in this chapter are based on the following scenario.

� The company Acme Company has its head office located in Dallas,

Texas. The telephone number for its head office is (214) 555-1111.

� The telephone system requires that users enter the access code �9� before

making any outgoing calls.

� There are 5 trunks on the Meridian 1. These are configured as trunks 1 to

� The Meridian 1 located in the switch room of the Acme Company head

office building requires an MDR-2000 ISD to collect CDR data. A

modem is attached to it to allow for communications between it and a PC

in another room. It has a dedicated extension number 222.

� The PC on which the Telecom Billing System is installed is located in

another room of the same building. A modem is attached to this PC's

COM1 port and will be used to connect to the MDR-2000 ISD.

Setting up the Telecom Billing System: Summary

The following is a summary of the steps required to set up and configure the

Telecom Billing System to process call records. You will only need to

perform these steps when you first install and use the Telecom Billing System

or if your configuration or hardware changes.

Ensure that the Meridian 1 is set up to properly output CDR data.

Install and set up the buffer unit.

Install any rate tables purchased for your dialing plan.

Run the Telecom Billing System so it can be configured.

Page 21

Getting Started

Page 11 of 78

BillNet Telecom Billing System User Guide

Set up and test the data collection process before running it in a real-time

situation.

Obtain the List Trunk and Member (LTM) values from the Meridian 1.

Set up the telephone configuration.

Test the telephone configuration.

For more details on each of the Telecom Billing System functions and

features described in the following sections, refer to the on-line Help included

with Telecom Billing System. For more details on the hardware components

included with the BillNet Telecom Billing System (e.g., buffer units, modems),

refer to their associated documentation.

Step 1: Ensure that Meridian 1 is set up properly

In order for the Telecom Billing System to collect and process CDR data, the

Meridian 1 must output the data in the proper format. You must therefore

enable the required features and options in the Meridian 1 overlays. This

section describes the options which are required for the Telecom Billing

System to process the CDR data.

Note: This document is not intended to describe all options related to

CDR data. For complete details on the available CDR options and

information on configuring CDR, refer to the appropriate documentation

(e.g., Call Detail Recording Description and Formats).

Select CDR output format

In Overlay 17, select either NEW or OLD format CDR output (

FCDR=NEW

The Telecom Billing System contains script files for supported buffer units,

including the MDR-2000 ISD. As well, it can be configured to support both

NEW and OLD CDR formats.

Auxiliary Identification output in CDR record

In Overlay 15 configure the Auxiliary Identification to be output in CDR

(

AXID=Yes

). The AXID field is not captured by the Telecom Billing System

but is required to ensure that data fields output in the CDR record appear in

the expected positions.

Page 22

Page 12 of 78

Getting Started

P0910103 Standard 1.0 July 2000

Configure routes for CDR output

In Overlay 16, configure the routes that will output CDR data (

CDR=Yes

) and

determine the type of CDR data to output. For example, you may wish to

record all incoming calls and only outgoing toll calls.

Ensure that the SDI port for your system is configured to match the settings

on the buffer unit. If you plan to collect data at a higher baud rate, you may

need to change both the SDI port and the buffer unit settings.

The default settings for the MDR-2000 ISD are:

� Baud =

1200

� Data Bits =

� Parity =

� Stop Bits =

If you plan to use the default values for the MDR-2000 ISD, you must use the

same values for the SDI port.

Step 2: Install and set up buffer unit

The Telecom Billing System collects CDR data from the Meridian 1 either

directly or through one of several types of buffer units. Depending on your

configuration, you may need to collect the CDR data from a buffer unit in a

specific format and share it between different applications.

For this setup, assume that the Telecom Billing System is collecting CDR

data from the MDR-2000 ISD. This section describes how to connect the

MDR-2000 ISD to the Meridian 1 and the PC via a modem connection. This

will provide you with an example by which you can learn how to set up the

other BillNet-supported buffer units. Since other buffer units have different

connection and communications requirements, you should refer to their

documentation for more details on setting them up.

Page 23

Getting Started

Page 13 of 78

BillNet Telecom Billing System User Guide

Security precautions for MDR-2000 ISD

The MDR-2000 ISD is a precision electronic product. Remember to review

all of the documentation included with the MDR-2000 ISD before attempting

to install and use it. Failure to observe the precautions and guidelines outlined

in the documentation may lead to product failure, damage and invalidation of

all warranties.

Before handling the MDR-2000 ISD, take all proper electrostatic discharge

(ESD) precautions, including personnel and equipment grounding.

� Do not rest the MDR-2000 ISD on the power cord. A damaged power

cord can cause fires or electrical shocks.

� Do not use the MDR-2000 ISD in damp, dusty or dirty places.

� Store spare components in proper anti-static material.

� Make sure equipment is turned off before handling or changing

components.

Connect MDR-2000 ISD to Meridian 1 and PC

The first step is to connect and install the MDR-2000 ISD onto the

Meridian 1. It can then collect and store call records as they are output from

the Meridian 1. You must then connect the PC to the MDR-2000 ISD so the

Telecom Billing System can collect the call records from its database files.

For this example, you would configure and connect modems to the

MDR-2000 ISD and to the PC.

WARNING

ESD damage is not always immediate and can result in failures after

months of operation.

Page 24

Page 14 of 78

Getting Started

P0910103 Standard 1.0 July 2000

Perform the following steps to connect the MDR-2000 ISD to the Meridian 1

and then to the PC via a modem connection.

Locate the CDR port on the Meridian 1.

Connect the MDR-2000 ISD to the Meridian 1 CDR port using an

RS232C cable:

Connect one end of the RS232C cable to the PBX port on the

MDR-2000 ISD and the other end to the CDR output port on the

Meridian 1.

Use a male DB-25 connector when connecting to the PBX port of

the MDR-2000 ISD.

Connect the MDR-2000 ISD to the first modem:

Connect the null modem cable which is provided with the

MDR-2000 ISD from the Modem port of the MDR-2000 ISD to the

serial port of the modem.

Connect a telephone line cord from the �To Line� output jack of

the first modem to the telephone jack.

Figure 4

Meridian 1 to MDR-2000 ISD

Page 25

Getting Started

Page 15 of 78

BillNet Telecom Billing System User Guide

Connect the PC to the second modem:

Connect a modem cable from an available communications port

(e.g., COM 1) on the PC to the serial port of the second modem. If

you have an internal modem attached to your PC, ignore this step.

Connect a telephone line cord from the �To Line� output jack of

the second modem to the telephone jack.

Plug in and turn on the MDR-2000 ISD:

Plug in the MDR-2000 ISD�s AC adapter into the electrical outlet.

Insert the AC power supply connector into the 9 VDC jack of the

MDR-2000 ISD.

Figure 5

MDR-2000 ISD to modems to PC

Page 26

Page 16 of 78

Getting Started

P0910103 Standard 1.0 July 2000

Plug in and turn on the modems:

Plug in the modems� AC adapters into the electrical outlets.

Insert the AC power supply connector into the Power jack of the

modem.

Test the MDR-2000 ISD to ensure that it is collecting data. Once you

have turned on the MDR-2000 ISD, all the lights will flash briefly and

the RUN and BMT indicators will remain on. After the second valid call

record is obtained, only the RUN indicator will remain on. The first valid

call is used to populate the buffer registries when the MDR-2000 ISD has

been turned off and on.

The PBX indicator will flash as the MDR-2000 ISD receives data. This

indicates that the data stream is being received. If the PBX light does not

flash and you are sure that a call has been made, check the following.

�

If you require a null modem adapter between the Meridian 1 and the

MDR-2000 ISD, then ensure that it is connected between the CDR

port of the Meridian 1 and the PBX port of the MDR-2000 ISD.

�

Ensure that CDR is turned on for the trunk route you are using.

Verify that the MDR-2000 ISD is collecting data

Access the MDR-2000 ISD to view and verify that the incoming data stream

is valid. To access the MDR-2000 ISD, perform the following steps.

Run a terminal program such as Windows HyperTerminal.

Dial up the telephone number of the MDR-2000 ISD. This is the number

where the MDR-2000 ISD was connected via its modem. If the PC is

connected directly to the MDR-2000 ISD, then you can simply start

typing the commands to edit the parameters. For this example, enter:

222

Type:

<Ctrl-V> I D <Enter>

. This will verify that you are communicating

with the MDR-2000 ISD. The response will be the serial number of the

MDR-2000 ISD.

To view the data, type:

<Ctrl-V> D U <Enter>

(you may need to type this

twice). If the data appears incorrect (e.g., it contains random characters),

then there is probably a communications problem.

Page 27

Getting Started

Page 17 of 78

BillNet Telecom Billing System User Guide

Changing communications parameters

The MDR-2000 ISD default communications parameters may be different

from the Meridian 1. For example, the MDR-2000 ISD baud rate defaults to

1200 and the Meridian 1 may be 9600. If they are different, you must change

the communications parameters of one or the other.

The following example demonstrates how to change the communications

parameters of the MDR-2000 ISD and also set it for

NEW

CDR format. If you

wish to change the communications parameters on the Meridian 1, refer to the

documentation provided with it.

To change the MDR-2000 ISD�s communications parameters, access the

MDR-2000 ISD interface using any terminal program running directly from

your PC. The following example demonstrates this process.

Run a terminal program such as Windows HyperTerminal.

Dial up the telephone number of the MDR-2000 ISD (e.g.,

222

). This is

the number where the MDR-2000 ISD was connected via its modem. If

the PC is connected directly to the MDR-2000 ISD, then you can simply

start typing the commands to edit the parameters.

Access the MDR-2000 ISD interface by typing:

<Ctrl-V> I M <Enter>

The M2K> prompt will appear.

Check the status of the MDR-2000 ISD by typing:

ST <Enter>

. The

status will appear similar to the following.

Page 28

Page 18 of 78

Getting Started

P0910103 Standard 1.0 July 2000

To change the baud rate for the modem port on the MDR-2000 ISD to

9600, type:

SE BA <Enter> 9600 <Enter>

. This will respond as: SE (Set

Options) BA (Baud) PBX (PBX default) 9600. The first

<Enter>

in this

line selects the default baud rate for the PBX port on the MDR-2000 ISD.

To quit and exit from this interface, enter:

(quit).

Note 1: If you are changing the baud rate for the modem, ensure that the

modem answers at the desired speed first. For example, if you are using

the Windows HyperTerminal program to access the modem, it will

prompt:

Connect 9600

when you are connected.

Note 2: Once you have completed accessing the MDR-2000 ISD,

remember to exit from it by entering:

(quit). If your communications

session is interrupted (e.g., by a disconnected line or a power failure),

then you will lose your edits.

Figure 6

MDR-2000 ISD status

Page 29

Getting Started

Page 19 of 78

BillNet Telecom Billing System User Guide

Notes for customization strings

In certain cases, you may need to change the customization strings of the

MDR-2000 ISD to match the output of the Meridian 1. If you need to change

the customization strings, use the CU (Customize) command in the

MDR-2000 ISD interface and change the strings as necessary. Refer to the

documentation provided with the MDR-2000 ISD for more details on what

the customization strings represent.

Step 3: Install rate tables and location books

Before you configure the Telecom Billing System, you must install the rate

tables which reflect your telecom provider�s rates. These provide such rates

as long distance charges for direct dialed calls to North America as well as

international long distance charges. The Telecom Billing System requires

these rate tables in order to accurately apply costs to your long distance calls.

As well as rate tables, you must install a set of location books for your

software. Location books contain codes for the actual locations which are

used by the rate tables to determine the charges incurred when calling these

locations.

You can obtain rate tables from a rate service or from your dealer. Remember

that the rate table files must be compatible with the Telecom Billing System

software. If in doubt, check with your supplier before purchasing any rate

tables.

To install the rate tables and location books, simply follow the instructions

included with them. Remember to install the rate table files onto your BillNet

Telecom Billing System directory so you can select the appropriate rate table

files when you are defining your carrier pricing templates.

Step 4: Run Telecom Billing System so it can be configured

If BillNet is not already running, click BillNet from the StartUp program group.

In the BillNet Navigator, open a predefined site and system (e.g., Site=Acme

Company, System=Head Office).

Once you opened the site and system, the following windows will appear.

Page 30

Page 20 of 78

Getting Started

P0910103 Standard 1.0 July 2000

From the selected site and system in the BillNet Navigator, click

Telemanagement

and click

Telecom Billing System

. This will access the

Telecom Billing System application main window from which you can set up

the communications parameters, telephone configuration and rate tables for

initial use. You will also need to test the data collection and run reports to see

if the data was collected and costed properly.

Figure 7

BillNet Navigator

Page 31

Getting Started

Page 21 of 78

BillNet Telecom Billing System User Guide

Step 5: Set up and test data collection

Before you enter your telephone configuration, you should verify that the

Telecom Billing System is collecting data from the Meridian 1 in the correct

format. This way, you can test the configuration against actual calls. To test

the data collection, simply enter the data collection parameters, collect the

call records from the Meridian 1 and view them in the Call Database.

Enter data collection parameters

In order for the Telecom Billing System to collect data from the Meridian 1,

you must enter the data collection parameters for the site and system. You

should have already connected and configured your hardware (previous

sections entitled: Step 1: Ensure that Meridian 1 is set up properly and Step

2: Install and set up buffer unit). You would just need to access the System

Configuration function�s Communications tab to select the communications

and data collection parameters.

Figure 8

Telecom Billing System main window

Page 32

Page 22 of 78

Getting Started

P0910103 Standard 1.0 July 2000

To enter the data collection parameters for the Telecom Billing System,

perform the following steps.

From the Telecom Billing System main window, click

Options | System

Configuration

. The System Configuration dialog will appear.

Click the

Collection

tab and enter your communications and collection

parameters. For example, enter the following values:

�

Type:

Dial-Up

�

Phone No:

222

�

Redials:

�

Port:

COM1

�

Baud Rate:

9600

�

Data Bits:

�

Parity:

None

�

Stop Bits:

In the Collection Script field, enter name of the script file which will be

used for this data collection. This file contains the instructions used to

communicate with the buffer unit and collect data from it. The script

filename you select depends on the type of buffer unit and the format of

the data being collected. For example, if you are collecting data from the

MDR-2000 ISD, then you would select

COLLECT.COL

. Refer to the

BillNet Common Services User Guide for a list of supported buffer units

and their corresponding script filenames.

Click

to select these options and return to the Telecom Billing

System main window.

Test data collection

Now that you have configured your hardware and entered the required

communications parameters, you are now ready to test the data collection. At

this stage, you should just run a data collection as a test. Later, you can set up

and invoke data collection once you have entered all of your system

information and you are ready to run it live.

Page 33

Getting Started

Page 23 of 78

BillNet Telecom Billing System User Guide

The following is an example to demonstrate how to test the data collection

process. This example assumes the following:

� The Meridian 1 is outputting CDR data to the CDR port.

� The MDR-2000 ISD is directly connected to the Meridian 1 and is

continuously collecting and storing the raw CDR data (call records) as

they are output from the Meridian 1.

� The Telecom Billing System will collect this CDR data from the

MDR-2000 ISD and store them in the Call Database.

To test the data collection for this scenario, perform the following steps.

Wait for some calls to be recorded by the Meridian 1. Either wait for

some calling activity on the Meridian 1 or make a few telephone calls. If

the MDR-2000 ISD is properly connected to the Meridian 1, it will

collect and store these call records as they are recorded by the Meridian 1

(note that the BMT light will be out).

Start the data collection process by clicking

Tools | Collection | Start

from the Telecom Billing System main window.

From the Start Collection dialog, select the

Batch

option and click

Start

The Telecom Billing System will start collecting the call records from

the MDR-2000 ISD and place them in the Call Database.

During the data collection process, the Telecom Billing System will

display both the collection activities as well as the call records as they are

collected. To view this information, click the

Collection

tab in the

System Tasks pane. Click

Status

to view the status of the collection.

Click

Data

from this tab to view the call records and verify that they are

in the correct format.

Review the call records for any invalid fields. For example, check the

trunk numbers and digits dialed for invalid values. The trunk numbers

appear in the Orig ID or Term ID fields depending on the �Orig� or

�Term� values. Check the first digits in the Digits Dialed fields to

confirm the access codes. As well, check the call records� dates and times

to ensure that they match the date and time on the Meridian 1.

Page 34

Page 24 of 78

Getting Started

P0910103 Standard 1.0 July 2000

If the data appears invalid, then repeat the previous steps checking to

ensure that your hardware is connected properly and that you have the

correct settings. Check the parameters on your Meridian 1 and the

MDR-2000 ISD.

This completes the steps required to initiate a data collection and verify the

call records.

Step 6: Obtain LTM from Meridian 1

Before you start entering the telephone configuration, you must first obtain

the List Trunk and Member (LTM) report from the Meridian 1. This will

provide you with invaluable information on how to set up your configuration.

Note: If you have ISA, the LTM will not show any members for the

service routes. You should print the Route Data Block (RDB) to

determine the service routes associated with the ISA routes. All members

indicated in the ISA route must be added to the associated service routes.

To obtain the LTM and RDB information for your configuration, access the

Meridian 1 and print the associated LTM and RDB reports.

Figure 9

Call Database

Page 35

Getting Started

Page 25 of 78

BillNet Telecom Billing System User Guide

Step 7: Set up Telephone Configuration

The next step in setting up the Telecom Billing System is to define the

telephone configuration. This identifies how the Telecom Billing System

processes the call records. It involves: assigning the appropriate rate tables

and carrier pricing templates to your system�s trunk groups; entering any call

digit translations; and setting any reporting options.

Since defining the telephone configuration is a complex task, it will be helpful

to demonstrate how to define one using an example configuration. This

example represents a typical configuration and will help you to set up your

own configuration.

Note: This telephone configuration is only an example. When setting up

your own configuration, you must enter your own company�s system and

rate information. You should review all of the documentation provided

with your Meridian 1 and by your service provider. This includes trunk

route and member numbers, output format, and rate table names.

Summary of steps

The following summary outlines the steps which you must perform to define

the telephone configuration for this example.

Access Telephone Configuration Database editor

Update Call Type Definitions table

Define Carrier Pricing Template

Define Call Digit Translation

Enter Telephone Configuration

Create Telephone Configuration

Add Main Node

Add Long Distance Service Definition to Main Node

Access Telephone Configuration Database editor

To access the Telephone Configuration Database tables, click

Edit |

Telephone Configuration

from the Telecom Billing System main window.

Page 36

Page 26 of 78

Getting Started

P0910103 Standard 1.0 July 2000

The following is a sample Telephone Configuration editor. When you access

this function for the first time, it will appear with blank menu items in the

Telephone Configuration menu tree.

Review the LTM report from the Meridian 1 to identify the call types for

reporting. For example, you can set up the call types: CO, DID, 800 and TIE.

With this information, you can set up columns of costing details or cost

summaries for these call types.

Update Call Type Definitions

The Call Type Definition function contains a list of the types of calls that may

be used by your organization (e.g., International, Local, etc.). You will select

these call types when you define the dialing patterns of your organization in

the Carrier Pricing Template. Select these predefined call types when

entering your costing and reporting options.

Figure 10

Telephone Configuration Editor

Page 37

Getting Started

Page 27 of 78

BillNet Telecom Billing System User Guide

The Call Type Definition function lists a set of default call types which you

can select when entering your costing and reporting options. In this step, add

any additional call types which you may require for your configuration (e.g.,

emergency calls). If you do not require any additional call types, then skip this

step.

The following steps demonstrate how to enter a call type. For this example,

you will enter the call type: Emergency for Emergency 911 calls (these are

sometimes costed differently).

From the Telephone Configuration menu tree, click

Call Type

. The Call

Type Definition grid will appear in the right pane with a list of default

definitions.

Click a blank line at the bottom of this grid and type:

Emergency

. This

will add this call type to this list.

The following diagram lists the default call types plus the new one you just

entered.

Figure 11

Call Type Definition

Page 38

Page 28 of 78

Getting Started

P0910103 Standard 1.0 July 2000

You have now told the Telecom Billing System that calls from this trunk

should be costed according to the template you created.

Define Carrier Pricing Templates

Carrier Pricing Templates help determine the type and cost of a call. The

Telephone Configuration Database uses these templates to assign costs to the

calls based on the trunks used and the digits dialed. For this example, you will

define a template for regular long distance service with multiple pricing

definitions.

For each digit pattern that represents a billable call, assign either the rate file

and table from your telephone company or a flat per-minute or per-call

charge. Add the flat per-call charges to the cost assigned by the rate file of

your telephone company.

Carrier Pricing Template�Sample Rates

To enter the sample carrier pricing template, perform the following steps.

From the Telephone Configuration menu tree, click

Carrier Pricing

Template

and click

File | New Carrier Pricing Template

. This will

display the Carrier Pricing Template grid in the right pane.

In the Name field, enter:

Sample Rates

Click the

Use Default Template

button to create a set of default values

for North America. Update these values with your own system

requirements.

Page 39

Getting Started

Page 29 of 78

BillNet Telecom Billing System User Guide

Edit pricing definitions in Carrier Pricing Template

The following steps describe how to edit the pricing definitions for this

default table. These pricing definitions allow the Telecom Billing System to

interpret any type of call containing identifiable digit patterns and then cost

them accordingly. They appear as a line-by-line listing in the grid.

For this example, you will only edit the pricing definitions for international

and North American long distance calls to specify the appropriate rate tables

for your carrier. These default pricing definitions have already been created

to provide you with standard North American dialing patterns. You only need

to select the appropriate rate tables for them. The following examples

demonstrate the use of the rate tables.

National Calls: These types of calls will use the location book

VHDATA

Location Book

International Calls: These types of calls would use the location book

Teleglobe International Location Book

Figure 12

Carrier Pricing Template

Page 40

Page 30 of 78

Getting Started

P0910103 Standard 1.0 July 2000

In certain cases, you may need to add new pricing definitions to match your

own configuration and dialing patterns.

Note: The order in which you enter these pricing definitions is

important. During costing, calls are compared to the digit pattern of the

first definition at the top of the list. The Telecom Billing System then

proceeds down the list until it matches the Digit Pattern field and, if used,

the rate table. The Telecom Billing System will then proceed to the next

definition if the rate table cannot cost the call (even if the digit patterns

are matched).

When you enter digit patterns for the pricing definitions, you can use certain

wild card and format characters as digit place holders. Use the asterisk

(multiple place holder) or question mark

(single place holder) as wildcards

for selecting common digit patterns. Use the optional flags

{}

(curled

brackets) to select optional digits to be included in the digits dialed. Use the

delete flags

[ ]

(square brackets) to select any digits which need to be

suppressed during rate table lookups but displayed on reports. Use the hide

flag

(period) to hide all of the digits which follow it in formatted reports.

Refer to the on-line Help under Pricing Definition for more details on using

wild card characters.

You can modify each pricing definition in this Carrier Pricing Template by

clicking the record line in the list and typing over the available fields. To view

each record in a dialog, click the record line and click

Edit

For example, to edit the International pricing definition, click the record line

for International (you may need to scroll across the grid to locate

International

under the Comments field) and click

Edit

. In the dialog which

appears, simply enter the desired information for it. Once you have entered

the rate information for each type of call, click

to save it and return to the

Carrier Pricing Template grid.

Perform the following steps to modify these pricing definitions.

International Calls

Click the record line in the Carrier Pricing Template grid which contains

International

in the Comments field and click

Edit

Enter the information as listed in the following dialog for International

calls and click

Page 41

Getting Started

Page 31 of 78

BillNet Telecom Billing System User Guide

Long Distance (National) Calls

Click the record line in the Carrier Pricing Template grid which contains

National

in the Comments field and click

Edit

Enter the information as listed in the following dialog for national calls

and click

Figure 13

Carrier Pricing Template: International Calls

Page 42

Page 32 of 78

Getting Started

P0910103 Standard 1.0 July 2000

Repeat the above steps for other dialed digit patterns where other charges may

apply. This completes the entries for this template's pricing definitions.

Define Call Digit Translation

The Call Digit Translation function translates the digits dialed on call records.

This translation can be applied to all outgoing calls in the system or to calls

on specific trunk groups in the system. This allows the Telecom Billing

System to process and print a different digit pattern from the one that is

actually dialed (e.g., suppressing access codes).

Note: Call Digit Translation does not affect Calling Line ID or

Automatic Number Identification (CLID/ANI) digit patterns on

incoming calls.

Figure 14

Carrier Pricing Template: Long Distance (National) Calls

Page 43

Getting Started

Page 33 of 78

BillNet Telecom Billing System User Guide

For this example, you will build a System Call Digit Translation table to

remove the access code �9� from the digits dialed of the call records. This

way, each call record will appear without the access code on reports. The digit

is the access code used to access a trunk on the Meridian 1 to initiate a call.

For example, your Meridian 1 may require that you enter �9� to select a trunk

to make an outgoing call. Each call record contains the access code digits

which are entered as part of the digit stream.

To translate the digit patterns for all calls, perform the following steps.

Click

Call Digit Translation

from the Telephone Configuration menu

tree.

Click

File | New Digit Translation Table

to add a new definition for this

table. This will create another menu item entitled:

New Digit Translation

Table 1

under this menu item. For this new call digit translation, a blank

table will appear in the right pane.

Rename this table by typing:

Sample CDT

in the Name field.

Enter the following information in the first line of this grid:

�

Match Digits:

�

Replace Digits:

Leave the remaining fields blank.

If you are not sure of what your access codes are, review the collected call

records in the Collection tab (Data) of the System Task pane. Access the

Telecom Billing System main window, click the

Collection

tab of the System

Task pane, and click

Data

. Check the Digits field for any of the outgoing call

records. If the system inserts an access code in the digit stream, it will appear

here.

This completes the steps for entering the Call Digit Translation.

Page 44

Page 34 of 78

Getting Started

P0910103 Standard 1.0 July 2000

Enter Telephone Configuration

The Telephone Configuration Database is the key to pricing calls and tracing

them to their destinations. This database defines the type of costing used

through each defined service and includes any additional costs defined for

your system and location. Each defined service uses predefined location

books and rate tables based your telecom carrier�s offerings. The Telecom

Billing System uses this configuration information to cost the call records and

report on them.

Now that you have all of the elements required to construct your telephone

configuration, you must add them to this table. The Telephone Configuration

table (in the Telephone Configuration Database editor) is sorted into the

following three components:

� General information (includes internal call definitions)

� Node information

� Service definitions (trunks)

You can define multiple nodes for each telephone configuration. As well, you

can define multiple service definitions for each node.

The following sections will describe how to create each of these components.

Create Telephone Configuration (General Information)

The first part of the Telephone Configuration table contains its general

information and optional costing for internal calls.

To create a new telephone configuration table and enter its general

information, perform the following steps.

Click the

Telephone Configuration

menu item and click

File | New

Configuration

. A data entry form will appear in the right pane allowing

you to enter this telephone configuration's general information.

Enter a descriptive name for this configuration by typing:

Telephone

Configuration Head Office

in the Telephone Configuration field.

Page 45

Getting Started

Page 35 of 78

BillNet Telecom Billing System User Guide

Specify the Call Digit Translation table which will be used for this

Telephone Configuration by selecting

Sample CDT

from the Call Digit

Translation drop-down list box. You previously defined this table in the

Call Digit Translation function.

If your Meridian 1 outputs CDR for internal calls (i.e., calls made

between extensions within the Meridian 1 system), then enter these costs

in the Internal Calls fields of this table. For this example, leave the

default values in these fields.

This completes the steps for creating a new Telephone Configuration table

and entering its general information.

Figure 15

Telephone Configuration editor

Page 46

Page 36 of 78

Getting Started

P0910103 Standard 1.0 July 2000

Add Main Node (Node Information Editor)

The next step in entering this telephone configuration is to define the general

information for the main node. Since a telephone configuration can contain

multiple nodes, you must define each node separately. For example, your

company�s telephone system may span different offices (nodes). For this

example, you are creating the minimum required node�the Main Node.

To add a node to this defined configuration, click the menu item

Telephone

Configuration Head Office

(which you just created in the previous steps) and

click

File | New Node

Perform the following steps to edit this node.

In the Company/Node Name field, enter the name for this node. For

example, enter:

Main Node

. The title in the menu tree will change to

Main Node

In the Company Location field, enter the city and province/state for your

company. For example, enter:

Dallas, Texas

In the Main Phone Number field, enter the telephone number for this

location. For example, enter:

214-555-1111

From the Location Book drop-down list box, select:

VHDATA Location

Book

Since this is the main node, leave the Time Zone field at

Since this is the main node, leave the Currency Exchange field at its

default value:

Leave the Main Node check box turned on. Only one node can have this

checked.

If the rates defined for this node require additional taxes, then select them

from the Tax Information drop-down list boxes. You must have defined

these taxes in the Taxes editor.

Page 47

Getting Started

Page 37 of 78

BillNet Telecom Billing System User Guide

This completes the steps for defining the Main Node. The next step is to

create the service definitions for this node. That is, you must enter the costing

parameters for the different trunk groups in this node.

Add Long Distance Service Definition to Main Node

Now that you have selected a node, you must enter its pricing definitions.

These pricing definitions apply to different trunk groups. For example, trunks

1 to 5 may be used for regular long distance calling and trunks 7 and 8 may

be used exclusively for toll free calls.

To add a long distance service definition to the main node, click the

Main

Node

menu item and click

File | New Service/Trunk Group

. This will create

another menu item under it entitled:

New Service 1

and will display the tabs

in which you can enter the service definition, fixed and variable costs, and

reporting options. Click on the following tabs to enter the information for this

service.

Figure 16

Telephone Configuration - Node editor

Page 48

Page 38 of 78

Getting Started

P0910103 Standard 1.0 July 2000

Service Definition Tab

In this tab, enter the general information for this service definition. This

includes the range of trunks using this service as well as its billing parameters.

Perform the following steps to enter this service definition.

In the Name field, enter:

Main Trunk Group

over the �New Service 1�

text. Notice that the tree menu item will change to reflect what you just

typed.

Leave the Termination option (Public Switch Network) and the Billing

Parameters fields in their defaults.

In the Trunk Numbers table, enter the trunk range for this trunk group in

your Meridian 1. For this example, enter the following:

�

Total Number of Equipped Trunks:

�

Line/Description:

CO Trunks

�

Low Range:

�

High Range

Note on Billing Parameters

For certain types of calls (e.g., international calls), you may need to enter a

connect time adjustment or a minimum call duration to allow for a delayed

connection. Enter this information in the Billing Parameters table of the

Service Definition tab.

Click the first record line of the Billing Parameters table, and perform the

following steps to enter a minimum call duration and a connect time

adjustment for international calls.

In the Match Digits field, enter:

011

. The system will interpret all calls

starting with the digits 011 (international calls) and apply the minimum

call duration and connect time adjustment from the following fields.

In the Comments field, enter:

International Calls

Page 49

Getting Started

Page 39 of 78

BillNet Telecom Billing System User Guide

In the Min. Duration field, enter:

. This is the minimum call duration

in seconds, which a call must exceed for it to be costed.

In the Connect Time field, enter:

. This is the time in seconds which the

system allows for a connection. This will be subtracted from the call

duration before costing.

Note: If these trunks have answer supervision, then you do not need to

enter a connect time adjustment value. You can therefore ignore these

steps.

Fixed Costs Tab

If your system requires fixed costs for these trunk groups, then enter them in

the Fixed Costs tab. You can enter fixed costs per minute, per call, per meter

pulse or per month. As well, you can define these costs for outgoing or

incoming calls.

Figure 17

Telephone Configuration - Service Definition

Page 50

Page 40 of 78

Getting Started

P0910103 Standard 1.0 July 2000

Variable and Carrier Costing Tab

In this tab, enter the costs which will be applied to calls made on this service.

You can enter costs for both outgoing and incoming calls. For outgoing calls,

you can enter variable costs based solely on the digit patterns or you can enter

the carrier costs which are based on these digit patterns. The carrier costs will

vary depending on the destinations of the outgoing calls.

For this example, you will select the predefined Carrier Pricing Template for

all calls using this service. The Carrier Pricing Template can then distinguish

between different types of calls for its costing.

Perform the following steps to select the carrier costing for this service.

In the Carrier Costing by Digits Comments field, enter:

Outgoing Calls

Leave the VPN Location Book field blank.

From the Carrier Pricing Template drop-down list box, select

Sample

Rates

Leave the % Cost Adjust field blank.

Report Options Tab

In this tab, enter the call reporting options for this trunk service. This allows

you to define how calls which use this service will appear on reports. For

example, you can suppress all incoming calls.

To enter the call reporting options for all calls using this service, perform the

following steps.

Click the first record in this grid.

From the Call Type drop-down list box, select:

All Calls

In the Print Option field, enter:

Detail

(this indicates that these calls

should be displayed in the main report body of the detail reports).

Leave the Cost Field blank. This determines the report grouping and

summary field on reports. Cost fields are defined in the Cost Field table.

In the Route DES field, enter:

DDD

(this is the route used on detail

reports for this call).

Page 51

Getting Started

Page 41 of 78

BillNet Telecom Billing System User Guide

This completes the defined service for the main node. You have now defined

how calls from this trunk should be costed according to the template you

created. Click

File | Close

to save this information and return to the Telecom

Billing System main window.

Step 8: Test telephone configuration

Now that you have entered your system's costing model and configuration,

you should test the accuracy of the configuration. To do so, you must apply

these costs to the collected call records and print some reports to review the

generated costs.

Apply costs to call records

The Telecom Billing System applies the costs based on your Telephone

Configuration Database and Rate Tables as a separate step to data collection.

That is, once you have collected the call records from the Meridian 1, you

must apply costs to them as a separate step.

To apply these costs to the collected call records, perform the following steps.

Click

Tools | Costing | Start

from the Telecom Billing System window.

From the Start Costing dialog which appears, select the

Batch

Costing

Mode option. This will perform a one-time costing of all non-costed call

records.

In the Available Telephone Configurations list, turn on the

Telephone

Configuration Head Office

check box. This will apply this specific

telephone configuration to these call records.

Click

Start

to cost the call records. The Telecom Billing System will then

start the costing procedure.

Click the Costing tab

Status

view of the System Tasks pane to check this

process. Once it displays the message:

The Costing task has

completed

, you are ready to generate reports based on the costed call

records.

This completes the steps involved in costing the call records.

Generate reports

Generate the following reports to test the accuracy of the telephone

configuration which you just entered.

Page 52

Page 42 of 78

Getting Started

P0910103 Standard 1.0 July 2000

Telephone Configuration Report

The Telephone Configuration Report displays your telephone configuration

information.

To print this report, perform the following steps.

Click

File | Reports

from the Telecom Billing System main window.

The Reporting dialog will appear.

From the Telecom Billing System Reports menu folder in the Reporting

menu tree (left pane), double-click the

Utility Tools

folder.

From the list of reports which appears, click

Telephone Configuration

From the Output Type drop-down list box, select

Printer

From the Configuration drop-down list box, select

Telephone

Configuration Head Office

. This represents the telephone configuration

you just defined.

Click

to print the report.

Exception Chronological Report

The Exception Chronological Report lists in chronological order all of the

calls that were made, and then collected by the Telecom Billing System.

Review this report to verify that the calls were processed and costed

accurately. Look for calls that have no location (except toll free calls). Check

that the long distance calls have costs assigned to them and that local calls do

not. Some common errors in the Telephone Configuration Database include

incorrect access codes and missing trunks.

To print this report, perform the following steps.

Click

File | Reports

from the Telecom Billing System main window.

The Reporting dialog will appear.

From the Telecom Billing System Reports menu folder in the Reporting

menu tree (left pane), double-click the

Cost Analysis

folder.

From the list of reports which appears, click

Exception Chronological

From the Output Type drop-down list box, select

Printer

Page 53

Getting Started

Page 43 of 78

BillNet Telecom Billing System User Guide

From the Configuration drop-down list box, select

Telephone

Configuration Head Office

. This represents the telephone configuration

you just defined.

Click

to print the report.

If either of these reports appears inaccurate, then review your input and make

any necessary adjustments to your telephone configuration.

Update databases

In order for your call records to accurately link to the proper employees and

their extensions as well as to your company�s customers and projects, you

should update the following databases with the latest employee and customer

information.

Employee Database: This database contains a list of employees linked to

specific extensions on the Meridian 1. When a call record is generated, it

needs to be associated with a specific extension. The Employee Database

contains this information as well as the organizational hierarchy level to

which this extension belongs. If you have installed the BillNet Station

Administration application, then this is populated from the Set Database.