Telephony Manager-Full 100102894

Nortel Communication Server 1000

Telephony Manager 4.0Telemanagement ApplicationsFundamentalsRelease: 6.0Document Revision: 03.04

www.nortel.com

NN43050-602.

Nortel Communication Server 1000Release: 6.0Publication: NN43050-602Document release date: 28 May 2009

Copyright © 2003-2009 Nortel Networks. All Rights Reserved.

While the information in this document is believed to be accurate and reliable, except as otherwise expresslyagreed to in writing NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OFANY KIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document aresubject to change without notice.

Nortel, Nortel Networks, the Nortel logo, and the Globemark are trademarks of Nortel Networks.

All other trademarks are the property of their respective owners.

.

3.

ContentsNew in this release 9Navigation 9Feature changes 9Other changes 9

Revision History 9

How to get help 11Getting help from the Nortel Web site 11Getting help over the telephone from a Nortel Solutions Center 11Getting help from a specialist by using an Express Routing Code 12Getting help through a Nortel distributor or reseller 12

Overview 13Contents 13Introduction 13Telemanagement applications 14Purpose of this guide 15

Telecom Billing System 17Contents 17Introduction 17Call records 19Telephony Manager Directory Services 24TBS interface 35Configuring TBS 58

Configuring a USB modem for use with Telephony Manager 67Changing the virtual COM port to USB modem association 69

Data collection and transmission 105Maintenance tasks 106Using TBS for hospitality billing 117Collecting data from Telephony Manager DBA Application 120Importing and exporting TBS data 122E-mail reporting feature 132Collecting Dialed Number Information Service data 136

Nortel Communication Server 1000Telephony Manager 4.0 Telemanagement Applications Fundamentals

NN43050-602 03.04 28 May 2009


.

4

Consolidated Call Cost Reports 139Contents 139Introduction 139CCCR interface 140Configuring CCCR 146Generating reports 153

TBS Web Reporting 157Contents 157Introduction 157TBS Web Reporting interface 158Configuring TBS Web Reporting 160

Configuring TBS Web Reporting 162Using TBS Web Reporting 166

General Cost Allocation System 167Contents 167Introduction 167GCAS interface 168Configuring GCAS 170Using GCAS 179

Consolidated Reporting System 187Contents 187Introduction 187CRS Interface 188Configuring CRS 189Using CRS 190

TBS scripts 195Contents 195Introduction 195Real-time CDR data collection 195CDR data collection from MDR 2000 195CDR data collection from PollCat III and PollNet Netlink 196CDR data collection from SEB II 197Sample data collection 197

TBS reports 199Contents 199Introduction 199Windows reports 199Web Navigator reports 222

Field Data Type Formatting for Export and Transmission 231Contents 231


NN43050-602 03.04 28 May 2009


.

5

Introduction 231Data type 231Data format 232

DATE data type 232TIME data type 234DURATION data type 236CURRENCY data type 237

List of terms 241

Index 247

ProceduresProcedure 1 Defining organization levels 26Procedure 2 Adding an organization node 27Procedure 3 Deleting an organization node 28Procedure 4 Adding an employee to an organization node 29Procedure 5 Editing employee data 30Procedure 6 Deleting an employee from an organization node 30Procedure 7 Searching for a specific employee 30Procedure 8 Sorting the employee list 32Procedure 9 Adding a new employee 33Procedure 10 Editing employee data 34Procedure 11 Deleting property assigned to an employee 35Procedure 12 Creating a custom graphic or logo for TBS reports 42Procedure 13 Disabling the TBS Display option 55Procedure 14 Preparing and configuring TBS to process call records 59Procedure 15 Ensuring that the system is configured properly 60Procedure 16 Connecting the MDR 2000 ISD to the system and to the PC 62Procedure 17 Verifying that the MDR 2000 ISD is collecting data 65Procedure 18 Changing the communication parameters of the MDR 2000 ISD 65Procedure 19 Checking for a virtual COM port 67Procedure 20 Changing the USB modem association with a COM port 69Procedure 21 Entering data collection parameters 74Procedure 22 Testing the data collection 76Procedure 23 Defining the telephone configuration 78Procedure 24 Entering a call type 80Procedure 25 Defining a cost field 81Procedure 26 Defining the Carrier Pricing Template 81Procedure 27 Modifying pricing definitions: international calls 83Procedure 28 Modifying pricing definitions: long distance (national) calls 84Procedure 29 Defining call digit translation 86Procedure 30 Determining your access codes 86Procedure 31 Creating the surcharge profile or groups and configuring surcharges

based on calling pattern 87Procedure 32 Configuring surcharges based on account codes 89Procedure 33 Creating a new telephone configuration table and entering general

information 93Procedure 34 Adding a node to a defined configuration 94Procedure 35 Adding long-distance services definitions to a node 95


NN43050-602 03.04 28 May 2009


.

6

Procedure 36 Applying costs to call records 98Procedure 37 Reapplying costs to call records 99Procedure 38 Generating the Telephone Configuration report 100Procedure 39 Generating the Trunk Diagnostic Report 101Procedure 40 Generating the Extension Diagnostic Report 101Procedure 41 Generating the Exception Chronological Report 102Procedure 42 Preparing for data transmission 103Procedure 43 Collecting data 105Procedure 44 Costing call records 105Procedure 45 Transmitting call records 106Procedure 46 Troubleshooting data collection 108Procedure 47 Costing call records 109Procedure 48 Generating reports 110Procedure 49 Updating the Employee database 112Procedure 50 Updating the Telephone Configuration database 113Procedure 51 Archiving the Call database 114Procedure 52 Purging the Call database 115Procedure 53 Restoring the Call database 115Procedure 54 Configuring TBS to process call records in a hospitality

environment 118Procedure 55 Collecting data from DBA 120Procedure 56 Importing data using a predefined configuration 123Procedure 57 Importing data using a custom configuration 123Procedure 58 Selecting a predefined import configuration 124Procedure 59 Creating a new configuration 124Procedure 60 Defining the import configuration and importing the data 125Procedure 61 Restoring the Call Database 126Procedure 62 Exporting data using a predefined configuration 128Procedure 63 Exporting data using a custom configuration 128Procedure 64 Selecting a predefined export configuration 129Procedure 65 Creating a new configuration 130Procedure 66 Defining the export configuration and exporting the data 130Procedure 67 Archiving the Call Database 131Procedure 68 Using the e-mail reporting feature 132Procedure 69 Configuring TBS and the MDR 2000 or MDR 2000e to collect DNIS

data 137Procedure 70 Configuring CCCR 147Procedure 71 Running CCCR 147Procedure 72 Assigning your systems to the consolidated server database 148Procedure 73 Editing the levels in the consolidated organizational hierarchy 150Procedure 74 Selecting local and alternate currencies for reports 151Procedure 75 Generating consolidated reports 153Procedure 76 Creating a custom graphic or logo for your reports. 154Procedure 77 Configuring and installing your server 161Procedure 78 Configuring TBS Web Reporting 162Procedure 79 Logging in to Telephony Manager Web and running TBS Web

Reporting 166Procedure 80 Defining the organizational hierarchy 172Procedure 81 Entering employee information 173Procedure 82 Entering external party information in the External Party

Database 174


NN43050-602 03.04 28 May 2009


.

7

Procedure 83 Entering role or project information in the Roles/ProjectsDatabase 175

Procedure 84 Entering a quantity-based bill type 176Procedure 85 Deleting a bill type 178Procedure 86 Defining taxes for a bill type 179Procedure 87 Entering billing records 179Procedure 88 Generating a report 182Procedure 89 Defining a report filter 184Procedure 90 Defining a sort definition 185Procedure 91 Generating an Entity Detail Report 191


NN43050-602 03.04 28 May 2009


.

8


NN43050-602 03.04 28 May 2009


.

9.

New in this releaseThe following sections details what’s new in Telephony Manager 4.0Telemanagement Application Fundamentals Guide (NN43050-602) forNortel Communication Server 1000 Release 6.0.

Navigation• “Feature changes” (page 9)

• “Other changes” (page 9)

Feature changesThe following product enhancement features have been added toTelephony Manager 4.0:

• Branding Changes to display Telephony Manager 4.0 release on allapplicable dialogs

• Web Report Scheduling

• TM-CND Enhancements

For information about TM-CND Enhancements, see TelephonyManager 4.0 System Administration Guide (NN43050-601).

Other changesRevision History

May 2009 Standard 03.04. This document is up-issued to support Nortel CommunicationServer 1000 Release 6.0.



July 2007 Standard 01.02. This document is up-issued to reflect changes in technicalcontent.


NN43050-602 03.04 28 May 2009


.

10 New in this release


July 2006 Standard 5.00. This document is up-issued to support the June 2006 review ofTelephony Manager 3.0.

March 2006 Standard 4.00. This document is up-issued to support Telephony Manager 3.0.

August 2005 Standard 3.00. This document is up-issued to support Nortel CommunicationServer 1000 Release 4.5.

September2004

Standard 2.00. This document is up-issued to support Nortel CommunicationServer 1000 Release 4.0.

October 2003 Standard 1.00 This document is issued to support the introduction ofTM Release 2.1.


NN43050-602 03.04 28 May 2009


.

11.

How to get helpThis chapter explains how to get help for Nortel products and services.

Getting help from the Nortel Web siteThe best way to get technical support for Nortel products is from the NortelTechnical Support Web site:

www.nortel.com/support

This site provides quick access to software, documentation, bulletins, andtools to address issues with Nortel products. From this site, you can:

• download software, documentation, and product bulletins

• search the Technical Support Web site and the Nortel Knowledge Basefor answers to technical issues

• sign up for automatic notification of new software and documentationfor Nortel equipment

• open and manage technical support cases

Getting help over the telephone from a Nortel Solutions CenterIf you do not find the information you require on the Nortel TechnicalSupport Web site, and you have a Nortel support contract, you can alsoget help over the telephone from a Nortel Solutions Center.

In North America, call 1-800-4NORTEL (1-800-466-7835).

Outside North America, go to the following Web site to obtain thetelephone number for your region:

www.nortel.com/callus


NN43050-602 03.04 28 May 2009


.

http://support.avaya.com

http://www.avaya.com/gcm/master-usa/en-us/tasks/connect/contacts/sales/salescontact.htm

12 How to get help

Getting help from a specialist by using an Express Routing CodeTo access some Nortel Technical Solutions Centers, you can use anExpress Routing Code (ERC) to quickly route your call to a specialist inyour Nortel product or service. To locate the ERC for your product orservice, go to:

www.nortel.com/erc

Getting help through a Nortel distributor or resellerIf you purchased a service contract for your Nortel product from adistributor or authorized reseller, contact the technical support staff for thatdistributor or reseller.


NN43050-602 03.04 28 May 2009


.

http://www.avaya.com/gcm/master-usa/en-us/tasks/connect/contacts/sales/salescontact.htm

13.

Overview

ContentsThis section contains the following topics:

• “Introduction” (page 13)

• “Telemanagement applications” (page 14)

• “Purpose of this guide” (page 15)

IntroductionTelephony Manager’s telemanagement applications offer you a range oftelecommunications and network management services, including billingand management, Web-based reporting, consolidated reporting, and callmonitoring. Each application contains unique functions that allow you tocollect, cost, track, and report on your telecommunications data. Together,they provide you with a complete call management and billing solution foryour telecommunications network.

The following is a list of the telemanagement applications available inTelephony Manager:

• Telecom Billing System (TBS)

• Consolidated Call Cost Reports (CCCR)

• TBS Web Reporting

• General Cost Allocation System (GCAS)

• Consolidated Reporting System (CRS)

Each application is installed separately onto Telephony Manager andruns independently of the other applications while still sharing commondata, such as employee and configuration information. As well, someapplications use data from the other applications during their operation.For example, TBS Web Reporting reports on data from CRS and TBS; andthe CRS generates reports for TBS and GCAS applications.


NN43050-602 03.04 28 May 2009


.

14 Overview

Based on your Telephony Manager license, you may have some or all ofthese applications included with your Telephony Manager system. Contactyour vendor for information on ordering additional telemanagementapplications for Telephony Manager.

Telemanagement applicationsThe following is a brief description of the telemanagement applicationsavailable for Telephony Manager. Refer to the remaining chapters in thisuser guide for more information about these applications.

Telecom Billing SystemTelecom Billing System (TBS) is the Telephony Manager advanced costallocation and billing application. TBS collects call records from yoursystems. It uses multiple costing models over multilevel organizationalhierarchies to allocate costs to the appropriate users, and to generatedetail and summary reports outlining these costs. These reports detail theactual usage of your telephone system, thus enabling you to assess theeffectiveness of your telephone services. As well, network utilization andsystem administration reports generated by TBS help you to manage yourtelecommunications network more effectively.

Consolidated Call Cost ReportsConsolidated Call Cost Reports (CCCR) is the Telephony Manager systemintegration and reporting application. CCCR combines data from theCorporate Directories in each of your Telephony Manager systems andgenerates billing reports based on this consolidated data. Specifically usedfor the Telephony Manager TBS, the CCCR application reports on yourcalling activity across multiple systems on a single Telephony Managerserver.

TBS Web ReportingTBS Web Reporting is the Telephony Manager Web-based reportingapplication for your telecommunications network. With TBS WebReporting, you can generate reports containing data from TBS throughyour intranet or Internet server. These reports provide you with valuableinformation about your organization’s calling activities. Its intuitiveWeb-based interface lets you view this information from any PC withintranet or Internet access to your server. Because these reportsare based on data from TBS, you must have previously installed andconfigured the TBS application as part of Telephony Manager.

General Cost Allocation SystemThe General Cost Allocation System (GCAS) is the Telephony Managergeneric billing application. It assigns usage charges to appropriateindividuals or departments within an organization. It can import billinformation, identify and log departmental or user-specific spendingcharacteristics, and generate meaningful reports summarizing these


NN43050-602 03.04 28 May 2009


.

Purpose of this guide 15

costs. With the GCAS, you can enter billing information, either throughan imported file or manually from the printed vendor statement. Thedata can then be used to allocate charges, such as those obtained fromcellular calls or pagers, to relevant individuals or departments within yourorganization. The GCAS generates detail and summary reports, includingthe billed products or services, associated costs, and departments orpersons to be billed.

Consolidated Reporting SystemThe Consolidated Reporting System (CRS) is the Telephony Managertelemanagement reporting application. It generates reports for both TBSand GCAS from a single interface. By defining filtering and sorting criteria,you can generate custom reports that detail organizational and employeespending characteristics for these applications. Each report is brokendown into sub-reports, which detail usage costs for TBS and GCAS.

Purpose of this guideThis document is designed to provide you with basic informationfor configuring and using the Telephony Manager telemanagementapplications. Where applicable, it includes any additional systemrequirements or installation procedures for specific applications. Beforeusing these applications, you must install and configure them as part of theTelephony Manager system. Refer to Telephony Manager 4.0 Installationand Commissioning (NN43050-300) for complete details about installingthese applications and assigning them to a site and a system.

Online and Web-based HelpThis user guide only briefly discusses the functions and commands of theTelephony Manager telemanagement applications. It provides you with abasic understanding of each of these applications and helps you to startusing the applications. For detailed information about each function andcommand for these applications, refer to the online Help function includedwith them.

You can use the Help functions to obtain help for topics either directly orthrough their indexes and word-search functions. While running theseapplications, you can obtain context-sensitive Help on any topic yourequire by clicking Help in a specific window or dialog box. This accessesthe Windows Help function and displays context-sensitive Help informationon the current topic.

To obtain help for a topic in TBS Web Reporting, click Help in the currentlyselected Web page. This accesses the Help function and displayscontext-sensitive Help information on the current topic.


NN43050-602 03.04 28 May 2009


.

16 Overview

If you click Help in a Web page other than that belonging to TBS WebReporting (for example, the Telephony Manager Administrator Logonpage), then the other Web application’s Help appears.


NN43050-602 03.04 28 May 2009


.

17.

Telecom Billing System



• “Call records” (page 19)

• “Telephony Manager Directory Services” (page 24)

• “TBS interface” (page 35)

• “Configuring TBS” (page 58)

• “Data collection and transmission” (page 105)

• “Maintenance tasks” (page 106)

• “Using TBS for hospitality billing” (page 117)

• “Collecting data from Telephony Manager DBA Application” (page 120)

• “Importing and exporting TBS data” (page 122)

• “E-mail reporting feature” (page 132)

• “Collecting Dialed Number Information Service data” (page 136)

IntroductionThis chapter provides basic information about configuring and running theTelecom Billing System (TBS). It also includes example procedures andreference information to assist you in configuring TBS.

As the Telephony Manager advanced costing and billing application, TBShelps monitor and control telecommunications costs for your telephonesystem. It collects call records from your system, allocates costs to theappropriate users, and generates detail and summary reports outliningthese costs. The reports provide details about the actual usage of yourtelephone system, and enables you to assess the effectiveness of yourtelephone services.


NN43050-602 03.04 28 May 2009


.

18 Telecom Billing System

TBS collects data from your system through a buffer device, adirect connection, or through a network connection. It uses definedcommunications and collection parameters to communicate with thesystem and collect the necessary telephone usage data.

TBS supports the CS 1000 and Meridian 1 lines of telephony equipment.After you collect the call records either directly from the system or fromthe Call Detail Recording (CDR) buffer unit, the records must be costed,collated, sorted, and printed on a report. This call detail information helpsyou achieve the following goals:

• The system provides details on the actual telephone usage.Management can isolate individual users and departments who are notproperly utilizing the telephone system through misuse or neglect.

• It provides usage details for cost allocation within the organization orfor client billing purposes.

• Management can use the information to determine which telephonecompany services are not being utilized. This analysis lets you adjustyour telephone services to suit your needs, resulting in savings to yourorganization.

CDR data collection optionsTBS collects CDR data from the system in several ways:

• directly from the system to its databases

• through the Telephony Manager Data Buffering and Access (DBA)application (network or serial connection)

• through a buffer unit

The DBA application and the optional buffer units can be used tocontinuously collect CDR data from the system and store the data for latercollection and processing by TBS. CDR data is saved to system-specificfiles so that multiple sessions of the DBA or buffer units can be supportedconcurrently by TBS. Only one instance of the DBA runs but multiplesessions can be created for different systems using the single instance ofthe DBA application.

For a complete list of script files used for communications and datacollection, refer to “TBS scripts” (page 195). For more information aboutthe DBA application, refer to Telephony Manager 4.0 Installation andCommissioning (NN43050-300).


NN43050-602 03.04 28 May 2009


.

Call records 19

Where required, buffer units can connect to each system through itsRS-232 port and connect to the PC using a supported modem. Nortelrecommends that the buffer unit contain battery backup power in the eventof a power failure. Refer to the buffer unit’s reference documentation formore information.

ATTENTIONNortel recommends that you use either the DBA application or a buffer unit forCDR data collection. If you use one of these devices, the CDR data is collectedand securely stored for later retrieval by TBS. Although the DBA or bufferunits are not required to properly use TBS, these options are recommended tosecurely store the CDR data. If you choose to collect the CDR data directly tothe PC without the use of the DBA or buffer unit, then you can lose data if thePC is accidentally rebooted or shut down.

With TBS, you can collect data from multiple buffer units into one system.This way, you can integrate data from multiple sites into a single system.

Call recordsBefore you enter your system configuration and update your TBSdatabases, you should first understand the nature of the data that isoutput from the system. This assists you in constructing your systemconfiguration databases to match your system. This section describes thecomponents of a call record as well as how it is processed and costed byTBS.

CDR call records, which are output from the system and are collectedby TBS, contain the key information to producing costing reports. Thefollowing is a summary of what happens to a call record:

System outputs call recordsWhen you place or receive a telephone call, the system records itsinformation as a CDR record (call record). This record contains suchinformation as the call’s start date and time, its duration, the trunk it wentout on, its associated line, and the digits dialed. This data is sent to thesystem’s Serial Data Interface (SDI) port. From here, an application orhardware device must record it so it can be processed. This can be abuffer unit that is connected to the system’s SDI port (recommended), oreven a PC running TBS for a direct connection.

As call records are output from the system, TBS collects this data eitherthrough a buffer unit, such as the MDR 2000 ISD, or directly to the PC.Buffer units are recommended for collecting CDR data because they cancontinuously collect and safely store these call records. A buffer unit isportable enough to be located close to the system. Some may also havesecurity features to allow for safe data storage (for example, batterybackups). Remember that CDR records are lost unless there is a devicecollecting the data from the SDI port, because although the call server can


NN43050-602 03.04 28 May 2009


.


also perform a backup and store it, the storage size has limitation (basedon the type of system), beyond which data might get lost. This is becausethe customer may not have a buffer box and may use the DBA applicationto collect CDR data from the system. For every network disconnection, thesystem performs a backup and stores the data in a file, which the DBAretrieves when the connection is restored.

Figure 1 "System block diagram" (page 20) displays the movement of acall record from the system through a buffer unit to TBS software on a PC.Notice that modems can be used to communicate with the system andbuffer units from distant locations.

Figure 1System block diagram

Figure 1 "System block diagram" (page 20) represents a single system.This system is usually a CS 1000 or Meridian 1 system or a physicallocation in TBS software and contains the actual database files for it.Before attempting to use TBS, you must add it as an application to theappropriate system.

Figure 2 "Sample system setup" (page 21) shows how a sample system isconfigured.


NN43050-602 03.04 28 May 2009


.

Call records 21

Figure 2Sample system setup

Collecting call recordsTBS collects call records from the system through the buffer unit, andformats and appends them to the end of the Call Database. The CallDatabase is an indexed collection of call records that reflects the callingactivity of the system.

Figure 3 "Sample call record allocation" (page 22) shows the informationfound in each call record.

ATTENTION


NN43050-602 03.04 28 May 2009


.


TBS databases use each component of the call record.

Figure 3Sample call record allocation

Processing X (transferred) recordsYou can program your CS 1000 or Meridian 1 system to output transferredcall records (also known as X records) as individual call records. Whererequired, you can configure TBS to process and report on these X records.

ATTENTIONThis option affects call volumes and, therefore, makes any costing based onvolume plans inaccurate.

To configure TBS to process X records, you must edit the ScriptConfiguration initialization file (ScriptConfig.ini). This text file, locatedin your site and system directory (for example, <TM Root>\CommonData\Sample Site\Sample System), identifies how the X records areprocessed. By default, TBS does not process X records.

The following is an example of a Script Configuration initialization file (withthe ProcessXRecords option set to NO):

[SL1NEW]ProcessXRecords=NoTo change its settings so TBS can process X records, open the file using atext editor such as MS Notepad, and change the text to read as follows:

[SL1NEW]ProcessXRecords=Yes


NN43050-602 03.04 28 May 2009


.

Call records 23

Save this file and run TBS to process these records. You are promptedwith a warning message stating that X records are being processed.

For real-time CDR collection of X type records, select the scriptSL1NEW.COL. To collect these records from an MDR 2000 ISD, select thescript M2KIMG_SL1NEW.COL. For more information about these scripts,refer to “TBS scripts” (page 195).

Processing B (Abandoned call) recordsWith International Release 18 Group H and North American Release 20,B (Abandoned call) records are output when the Time to Answer featureis active and New format CDR is selected for CDR TTY output (FCDR =NEW in LD 17). B records are output only to CDR – Teletype devices.

B records are output when:

• an unanswered incoming trunk disconnects and ABAN = YES in LD 16

• internal CDR is equipped and an unanswered internal stationdisconnects from another internal station that has ABDA class ofservice

Prior to Release 23, the CDR B record provided information only forabandoned calls on ringing. With the Release 23 feature CDR on BusyTone, a B record is produced when the originator of an incoming orinternal call disconnects after receiving a busy tone. The CDR on BusyTone B record information is displayed on the third line of the CDR Brecord for customers with the New CDR format (FCDR) configured.

For real-time CDR collection of B type records, select the scriptSL1NEW.COL. To collect these records from an MDR 2000 ISD, select thescript M2KIMG_SL1NEW.COL. For more information about these scripts,refer to “TBS scripts” (page 195).

Costing call recordsAfter TBS collects the call records, it runs them through a series ofcalculations to apply costs to them. It then stores these costed call recordsin the Call Database. Each process uses the parameters stored in theTelephone Configuration Database (you will see how to configure theselater in this chapter).


NN43050-602 03.04 28 May 2009


.


The following is a summary of how call records are processed:

1. The Call Digit Translation table of the Telephone ConfigurationDatabase translates the digits dialed to remove or edit any accesscodes.

2. TBS looks up the trunk on which the call went out to see which servicedefinition to check. It looks the trunk up in the table of the TelephoneConfiguration Database Service Definition.

3. TBS applies any minimum call duration and network connect timeadjustment values to the call.

4. TBS identifies the Carrier Pricing Template assigned to the trunk. Thisindicates the type of call, how the number is formatted on the report,and which rate structure is used to cost the call.

5. TBS applies any fixed costs to the call.

Telephony Manager Directory ServicesYou can input end user data directly into the customer’s server throughTBS by using Telephony Manager Directory Services. Telephony ManagerDirectory contains employee and organization details, with a number offields that are common to both Directory and Telephony Manager.

Telephony Manager Directory provides a number of tools to configure yourcompany structure and create an employee database:

• an Organizational Hierarchy Editor to define your business organization

• an Employee Editor to manage user data

• an External Party Editor to configure external party records

• a Roles/Project Editor to create role and project groups within theorganization

Organizational Hierarchy EditorThe Organizational Hierarchy Database contains the different structurallevels within your organization (for example, departments, divisions, andso on). You can create up to 20 different levels in this hierarchy. TheOrganizational Hierarchy Editor is used to create, name, and arrangethese different organizational levels. The company’s organizationalunits are assigned to these levels. The cost summary reports can thensummarize the calling activity and associated usage costs by these levels.

With the Organizational Hierarchy Editor, you create and edit the structureof your company. You build an organization tree representing the differentorganization nodes in your corporation, such as divisions, departments,


NN43050-602 03.04 28 May 2009


.

Telephony Manager Directory Services 25

projects, and project teams. You can place each organization node at itslevel in the hierarchy. After defining an organization node in the structure,you can assign employees to the node using the Org. Path field in theEmployee Editor.

ATTENTIONNone of the information entered into the Organizational Hierarchy Database fromthe Telecom Billing System is automatically entered into the Common NetworkDirectory. The information has to be manually input into the Common NetworkDirectory database as well as into the Organizational Hierarchy Database.

Access the Organizational Hierarchy EditorTo access the Organizational Hierarchy Editor, select Edit >Organizational Hierarchy.

The Organizational Hierarchy window, shown in Figure 4 "OrganizationalHierarchy Editor: Levels tab" (page 25), is where you define the structureof your organization. The left side of the window shows the organizationalhierarchy tree. The right side of the window is the Employee Selector,providing a list of employees related to the selected organization node.

Figure 4Organizational Hierarchy Editor: Levels tab


NN43050-602 03.04 28 May 2009


.


Define organization levelsBefore you begin adding organization nodes to the tree, define thelevels of the organizations in your company. The levels represent thestructure of your company. For example, the company can have divisions,departments within divisions, and projects within departments. You candefine a maximum of 20 different levels.

Procedure 1Defining organization levels

Step Action

1 Select the Levels tab.

The tree displays the levels defined for the structure. If you havenot yet entered the structure for your organization, the windowcontains a default menu tree with the Organization, Division, andDepartment levels.

2 Click the lowest level to define a new level.

3 Right-click to open the Add New Level window.

4 Type the name of the new level.

5 Click Enter.

6 To delete a level, right-click on the lowest entry and selectDelete.

--End--

As shown in the example in Figure 4 "Organizational Hierarchy Editor:Levels tab" (page 25), the levels are defined as:

• Corporation

• Divisions within the corporation

• Departments within the division

• Projects within the department

• Employee teams within the project

Add an organization nodeYou must define an organization level before you can add an organizationnode at that level. See “Define organization levels” (page 26).


NN43050-602 03.04 28 May 2009


.


Procedure 2Adding an organization node

Step Action

1 Select the Organizations tab.

The Organizations tab opens, as shown in Figure 5"Organizational Hierarchy Editor: Organizations tab" (page 27).

2 Select the name of the organization in the tree where you wantto add a new organization node.

For example, if adding a new department to a division, select thename of the division.

3 Right-click and select Add New Division.

The new node appears in the tree. For example, if adding a newdivision, Division appears in the tree.

4 Type the name of the new node and click Enter.

To rename the node, click the right mouse-button and selectRename to give the node a new name.Figure 5Organizational Hierarchy Editor: Organizations tab

--End--


NN43050-602 03.04 28 May 2009


.


Delete an organization nodeUse Procedure 3 “Deleting an organization node” (page 28) to delete anorganization node.

Procedure 3Deleting an organization node

Step Action

1 Select the organization node in the tree.

2 Right-click and select Delete.

A dialog box opens confirming that you want to delete the node.

3 Click Yes.

The node disappears from the tree.

--End--

Employee Selector windowThe right section of the Organizational Hierarchy window consists of theEmployee Selector window.

The Employee Selector window also appears as an individual window byclicking Directory in the Station Set window.

This window displays the list of current Employee entities in the Directorydatabase, and enables you to create a new employee entity, add it to yourorganization node, and edit the details of an existing entity.

Use the icons in the Organization Hierarchy toolbar to edit the Employeerecords listed or create new Employee, Roles/Projects, or External Partiesrecords to be added to your organization node. As they appear from leftto right, the icons are:

• Add new record—Select a record type (Employee, External Party,Role/Project) from the Entity Selector. You can then add a newEmployee record to the database (which opens the Employee Editor),or add a new Roles/Projects record (which opens the Roles/ProjectsEditor) or a new External Party record (which opens the External PartyEditor). Use Procedure 4 “Adding an employee to an organizationnode” (page 29).


NN43050-602 03.04 28 May 2009


.


ATTENTIONDo not use spaces in the names of Roles and Projects.

• Delete record—Delete the selected record from the database. UseProcedure 6 “Deleting an employee from an organization node” (page30)

• Edit record—Edit the selected record. This opens the correspondingEditor window (for example, Employee Editor, External Party Editor, orRoles and Projects Editor), in which you can edit the record details.See Procedure 5 “Editing employee data” (page 30).

• Find—Search for a specific record. Enter a text string and select a fieldfrom ID, Entity Type or Name by which to search the database. UseProcedure 7 “Searching for a specific employee” (page 30).

• Sort—Sort the employee records in ascending or descending order.Use Procedure 8 “Sorting the employee list” (page 32).

• Refresh view—Refresh the list after making changes.

• Move First/Previous/Next/Last—Move the cursor to the top of the list,to the previous entity to the one selected, to the next entity to the oneselected, or to the end of the list.

• Help—Consult the online Help system.

The following procedures describe how to maintain employees assignedto an organization node. The procedures to maintain External Parties andRoles/Projects are similar.

Procedure 4Adding an employee to an organization node

Step Action


2 Click Add (the toolbar button with the plus sign).

The Entity Type Selector window opens.

3 Select Employee.

The Employee Selector window opens.

4 Select the Employee name to assign to the organization node.

--End--


NN43050-602 03.04 28 May 2009


.


Procedure 5Editing employee data

Step Action


The names of the employees appear in the Employee Selectorwindow.

2 Select the name of the employee you want to edit.

3 Click Edit (the Toolbar button with the pencil).

The Employee Editor opens.

4 UseProcedure 10 “Editing employee data” (page 34) to edit theemployee information.

--End--

Procedure 6Deleting an employee from an organization node

Step Action


The names of the employees appear in the Employee Selectorwindow.

2 Select the employee you want to delete.

3 Click Delete (the toolbar button with the X).

The employee disappears from the list, and is removed only fromthe organization node. The employee still exists in the TelephonyManager Directory.

--End--

Procedure 7Searching for a specific employee

Step Action


2 Click Search (the toolbar button with the flashlight).

The Find and Replace window opens, as shown in Figure 6 "Findand Replace window" (page 31).


NN43050-602 03.04 28 May 2009


.


Figure 6Find and Replace window

3 Select the field you want to search from the Search Field list.

4 Enter the character string to search for in the Find What textbox.

If you enter a blank value in the Find What text box, allemployees will be searched. For example, if "Last Name" isselected from the list in the Search Field field, and nothing isentered in the Find What text box, the system will search allemployees having a last name.

5 Click one of the following:

• Find First—Finds the first occurrence of the character string

• Find Next—Finds the next occurrence of the character string

• Close—Ends the search

If the search finds a match, the employee’s name appearshighlighted in the Entity Selector window, as shown in Figure 7"Entity Selector window" (page 32).


NN43050-602 03.04 28 May 2009


.


Figure 7Entity Selector window

--End--

Sort the employee listProcedure 8Sorting the employee list

Step Action


2 Select the column header of the column you want to sort in theEmployee Selector window.

3 Click Sort Ascending or Sort Descending (the toolbar buttonswith AZ Up or AZ Down).

--End--


NN43050-602 03.04 28 May 2009


.


Employee EditorThe Employee database contains information about your organization’semployees that is relevant to TBS. It includes such information as youremployees’ names, telephone extensions, authorization codes, and theirlocations within the organizational hierarchy. This information is required tocost and allocate telephone calls to the proper extensions and cost centerswithin your organization.

ATTENTIONNone of the information entered into the Organizational Hierarchy Database fromthe Telecom Billing System is automatically entered into the Common NetworkDirectory. The information has to be manually input into the Common NetworkDirectory database as well as into the Organizational Hierarchy Database.

The Employee Editor window enables you to add new employees andupdate employee personal and job-related data. The tabs on the right sideof the window enable you to define the assets assigned to the employee.You can also define the property assigned to the employee, such astelephone and terminal numbers.

Access the Employee EditorYou can access the Employee Editor in one of two ways:

• Click Add or Edit in the Organizational Hierarchy Editor window.

• Double-click an employee’s name in the Employee Selector window.

Procedure 9Adding a new employee

Step Action

1 Enter the employee data as follows:

a Enter the employee information in the appropriate fields.

b Select the organization node to which the employee is tobe added by selecting the node from the Org Path list, orentering the path to the node in the Org Path text box.

c From the Manager list, select the employee’s manager.

The Manager name is defined in the Web Directory section.After the CND synchronization, the name propagates to theEmployee Editor.

d Click the envelope icon next to E-mail to enter theemployee’s default e-mail address or type the e-mail address.

Ensure that you type a valid e-mail address as this field is notvalidated.

2 Enter the asset information as follows:


NN43050-602 03.04 28 May 2009


.


a Select New Asset in the Type column.

The edit boxes below the grid become active.

b Select the type of asset from the Type list.

The asset types available identify the employee in thedifferent Telephony Manager applications. Based on the typeselected, a corresponding field entry appears, into which youenter a value.

c If the employee is the prime user of this asset, select Prime.

This allows several employees to use the same asset, whileone employee in particular is the main owner of the asset andis assigned the cost.

d Click Apply.

3 Click one of the following:

• OK—Saves the employee information and closes the window.

• Apply—Applies the information configured.

• Apply/New—Saves the employee information and leaves thewindow open. The window is blank so you can add anothernew employee.

• Cancel—Closes the window without saving the employeeinformation.

--End--

Procedure 10Editing employee data

Step Action

1 Select the Employee tab in the Employee Editor window.

The selected employee data appears.

2 Edit the employee data as follows:

a Edit the employee information in the appropriate fields.

b Select the organization node with which the employee isassociated by selecting the node from organization structuretree, or entering the path to the node in the Org Path textbox.

c From the Manager list, select the employee’s manager.

d Click the envelope icon next to E-mail to enter theemployee’s default e-mail address or type the e-mail address.

e Click one of the following:


NN43050-602 03.04 28 May 2009


.

TBS interface 35

• OK—Saves the employee information and closes thewindow.

• Apply/New—Saves the employee information and leavesthe window open. The Up and Down arrows appear onthe right side of the window. Use these arrows to scroll toanother employee record for updating.

• Cancel—Closes the window without saving the employeeinformation.

3 Edit the property information:

a Select the property you want to edit from the list of property inthe grid at the right of the window.

The edit boxes below the grid display the current values.

b Change the information in the edit boxes.

If the property is new, the system automatically selects thePrime field.

c Click Apply.

--End--

Procedure 11Deleting property assigned to an employee

Step Action

1 Select the property you want to delete from the list of property inthe grid at the right of the Employee Editor window.

2 Click Delete located below the grid.

--End--

TBS interfaceThis section contains an overview of TBS functions and databases. Itbriefly describes their function and purpose. For complete details abouteach of these functions and their operation, refer to the online Helpincluded with the software.

Interface elementsThe TBS main window is the main interface for editing the databases,collecting data, and generating reports. See Figure 8 "TBS main window"(page 36).


NN43050-602 03.04 28 May 2009


.


Figure 8TBS main window

The following sections provide a brief outline of TBS commands,databases, and panes.

PanesTBS displays its activities in the following panes:

System Tasks section The System Tasks section, shown in Figure9 "System Tasks section" (page 37), displays information about thedata collection, costing, and data transmission functions. Each tab inthis section displays the data being processed, as well as the status ofeach process. Use this section to view the status of your data and of thesystem’s functions.


NN43050-602 03.04 28 May 2009


.

TBS interface 37

Figure 9System Tasks section

System Monitor section The System Monitor section, shown inFigure 10 "System Monitor section" (page 37), displays another view ofCollection, Costing, and Transmission activities. You can view the statusof a particular process and determine at a glance if the system is runningproperly.

Figure 10System Monitor section

System Alarm section The System Alarm section, shown in Figure 11"System Alarm section" (page 38), displays alarm messages to indicateany abnormal activity during the TBS session. It displays the alarmmessages for alarms that were defined in the System Configurationfunction. When the system encounters an activity that surpasses a definedalarm threshold, it displays the corresponding alarm in this section. Aswell, this section displays all status messages for any running tasks with aseverity level of Warning or higher.


NN43050-602 03.04 28 May 2009


.


Figure 11System Alarm section

File menuThe File menu accesses functions used to archive, purge, and restore theCall Database; import and export data; generate reports; and exit fromTBS.

To access these functions, click File in the main window, and then selectfrom the following menu options:

• Call Database

— Archive

— Restore

— Purge

• Import

• Export

• Reports

• Exit

Call DatabaseThe Call Database menu option accesses another cascading menucontaining the Archive, Restore, and Purge menu options. These menuoptions access the Archive, Restore, and Purge functions, which help youto manage your Call Database records.

Archive The Archive function is used to copy—or archive—a rangeof call records from the Call Database to an external device, such as anetwork drive or a disk.

Restore The Restore function is used to copy—or restore—the archivedcall records from an external device, such as a network drive, back to theCall Database.


NN43050-602 03.04 28 May 2009


.

TBS interface 39

Purge The Purge function is used to delete—or purge—a range of callrecords from the Call Database. This frees more disk space on your PCfor new call records and improves overall system performance.

ImportThe Import function is used to import data records from an externalsource to this system and convert them to a format compatible with TBSdatabases. This function is useful for quickly updating TBS databases withdata from another application.

ExportThe Export function is used to export data from TBS databases to anexternal source.

ReportsTBS reports provide you with thorough and detailed information about yourtelephone system. These reports detail and summarize your telephonesystem usage, assign costs to the appropriate cost centers, and displayinformation about your system organizational databases. As well, theyprovide statistics about your system to help assess the effectiveness ofyour telephone services.

Figure 12TBS Reporting window

Reporting options The following options are used to select the outputdevice for the report, as well as its filters and sorting definitions. These


NN43050-602 03.04 28 May 2009


.


options appear in the Profile section (right side) of the TBS Reportingwindow, shown in Figure 12 "TBS Reporting window" (page 39).

• Output Type

The Output Type list contains a list of output formats for the selectedreport. You can select from the following options:

— Screen—This option displays the report on the screen.

— Printer—This option prints the report to the Windows-configuredprinter.

— Rich Text Format—This option exports the report to a file in richtext format (RTF). Its filename is the name you entered in the FileName box as extension.RTF.

Reports exported in RTF do not contain logos or graphs.

— HTML Format—This option exports the report to a file in hypertextmarkup language format (HTML). Its filename is the name youentered in the File Name box as extension.HTM.

Reports exported in HTML do not contain graphs.

— Snapshot Format—This option exports the report to a file inMicrosoft Snapshot format. Its filename is the name you entered inthe File Name box as extension.SNP. To open the file in Snapshotformat, you must have the Snapshot Viewer installed on your PC.

• File Name

When outputting a report to a format other than a printer or screen, theReport Generator requires that you specify its filename and destination.This way, it can save the report to a file in that selected format. In theFile Name box, enter the name of the file to which the report is to beexported. Also select the destination drive and directory for this file.This filename has an extension that corresponds to the format of thefile. This field is activated only if you are exporting the report to a file inone of the supported formats (RTF, HTML, or Snapshot).

ATTENTIONYou can enter specific variable tags in your filenames to create uniquefilenames during report generation. This provides you with added flexibilitywhen you are generating reports at scheduled intervals and you do not wantto rename the files for each interval.

• Send File Using E-mail

When generating a report to a file, you can also send copies of thatfile to definable e-mail addresses. The Send File Using E-mail optionallows you to e-mail a copy of the report to selected e-mail addresses.When you generate the report, this option inserts the report file as anattachment to an e-mail message. This option e-mails the outputted filethat you entered in the File Name box. Because this function inserts


NN43050-602 03.04 28 May 2009


.

TBS interface 41

the report file as an attachment to an e-mail message, it is availableonly if you are outputting a file to RTF or Snapshot format.

• Filter

The Filter function is used to select the reporting criteria for yourreports. This allows you to generate reports based on very specificrequirements. For example, you may want to view a report for only thecurrent day. Use the Filter function to select the most recent day forthis report, then select this filter name from the Filter list in the mainReport Generation dialog box when you print the report.

• Sort

The Sort function is used to sort the data in the reports in differentformats. For example, you may want to display a report by date andtime. Use the Sort function to sort the report by the selected dateand time. then select this sort definition name from the Sort list in theReporting dialog box when you print the report.

• Configuration

The telephone configuration to which these reports apply. Thetelephone configuration is initially defined as described in “Preparetelephone configuration” (page 78).

Reporting commands The following is a list of the Report Generatorcommands:

• Go—This command generates the selected report.

• Schedule—This command schedules the report to be run at a laterdate and time. This accesses the Scheduler application in which youenter the scheduling criteria for the report.

• Cancel—This command exits this function.

• Help—This command allows you to obtain help for the ReportGenerator function.

Creating custom logos on reports Each TBS report contains acommon header graphic, which is located at the top left corner of thereport. This graphic helps you to easily identify the reports as part of TBS.

Use TBS to edit this graphic, or even replace it with another graphic, byediting a bitmap (BMP) file. You can replace this graphic with anothermore descriptive design, such as your company logo, to suit yourown needs. For example, you can include your company logo on yourTBS reports to provide you with professional-looking reports that arecustomized for your organization.


NN43050-602 03.04 28 May 2009


.


CAUTIONBe careful when editing the graphic file. If the file is too large,it may cause errors in the generated reports. To ensure thatthe original graphic file is secure, make a backup copy of it.To do so, copy the file Logo.bmp from the site and systemdirectory to another directory, or rename it (for example,Backup_Logo.bmp).

Perform the following steps to create a custom graphic or logo for yourTBS reports.

Procedure 12Creating a custom graphic or logo for TBS reports

Step Action

1 Use a graphics program such as MS Paint to create a bitmapwith the following dimensions: 3.73" (W) by 0.86" (H).

2 Insert or create the new graphic (for example, your companylogo) in the bitmap file.

3 Save this file as Logo.bmp to the drive and directory for yoursite and system (for example, C:\Nortel\Common Data\SampleSite\Sample System\Logo.bmp).

--End--

To help you to use the correct dimensions for your logo, you can make acopy of the original graphic file Logo.bmp and use it as a template for yourown graphic. Open the file Logo.bmp and insert the new graphic in the file.

The TBS reporting function automatically uses this logo on your reports.

List of reports The following is a list of the reports that are available forTBS.

• Cost Analysis Reports

The Cost Analysis Reports display costing information for calls madeby your employees, either by their extensions or authorization codes.The tabulated costs are then rolled up to their respective organizationallevel summaries. Costs can also be identified by account codes andthen charged back to your clients.

ATTENTIONThe requested TBS report could be empty as there might be no dataavailable for the report or there is no data collected from the telephonesystem.

The following is a list of the available Cost Analysis Reports:


NN43050-602 03.04 28 May 2009


.

TBS interface 43

— Extension Detail Report

— Extension Detail Report with Account Codes

— Exception Chronological Report

— Entity Detail Report

— Dialed Number Info Service (DNIS) Summary Report

— DNIS Detail Report

— Auxiliary ID Detail Report

— Authorization Code Detail Report

— Account Code Summary Report

— Account Code Detail Report with Employees

— Account Code Detail Report

— Entity Summary Graphs

— Organization Roll-up Summary Graphs

— Account Code Roll-up Summary Reports

— Authorization Code Roll-up Summary Reports

— Entity Roll-up Summary Reports

— Extension Roll-up Summary Reports

• Directory Information Reports

The Directory Information Reports provide you with details aboutyour system’s corporate databases. Such reports as the role/project,external party, and employee directory reports are useful in maintainingan up-to-date listing of your projects, customers, and employees.

The following is a list of the available Directory Information Reports:

— Role/Project Directory Report

— External Party Directory Report

— Employee Directory Report (ordered by Organizational Unit)

— Employee Directory Report


• Frequency Reports

The Frequency Reports provide details about actual telephone usage.Management can isolate individual users and departments that are notproperly using the telephone system through misuse or neglect. Aswell, system administrators can use this information to determine which


NN43050-602 03.04 28 May 2009


.


services are not being utilized. This analysis enables you to adjustyour telephone services to suit your needs.

The following is a list of the available Frequency Reports:

— Undisbursed Verification Report

— Unanswered Calls Summary Report

— Unanswered Call Detail Report

— Ring Time Report

— Ring Time Analysis Report

— Location Summary Report

— Hold Time Summary Graph

— Hold Time Detail Report

— Frequently Called Numbers Report

— External Party Summary Report

— Duration Summary Graph by Call Type

— Duration Summary Graph

— Digits Detail Report

— Call Area Summary Report

— Area Code Summary Report

— Area Code Location Summary Report

— Area Code Summary Graphs

— Location Summary Graphs


• Surcharge Reports

The Surcharge Reports display costing information for calls madethrough your system. They itemize the total usage charges by cost,surcharge (profit), and total cost (billed amount). The tabulated costsare then rolled up to their respective organizational level summaries.These costs are identified by the associated authorization codes andextensions on the entity reports. The costs can also be identified byaccount codes and then charged back to your clients.

The following is a list of the available Surcharge Reports:

— Exception/Chronological Surcharge Report

— Entity Surcharge Summary Report

— Entity Surcharge Detail Report


NN43050-602 03.04 28 May 2009


.

TBS interface 45

— Account Code Surcharge Summary Report

— Account Code Surcharge Detail Report

— Account Code Surcharge Roll-up Summary Reports

— Entity Surcharge Roll-up Summary Reports


• Utility Tools Reports

The Utility Tools Reports provide assistance in managing the telephoneconfiguration databases. These reports highlight features of yourtelephone configuration that must be updated regularly to keep yournetwork management and fiscal reports accurate.

The following is a list of the available Utility Tools Reports:

— Trunk Diagnostic Report

— Telephone Configuration Report

— System Configuration Report

— Extension Diagnostic Report

— Authorization Code Diagnostic Report

— Account Code Diagnostic Report


• Traffic Reports

The Traffic Reports help to determine cost effective networkingsolutions by critically examining the telephone system’s trunks andservices.

The following is a list of the available Traffic Reports:

— Trunk Group Utilization Graphs

— Trunk Usage Reports

– Trunk Utilization Report

– Trunk Graph

– Trunk Detail Report

– Tandem Tie Summary Report


NN43050-602 03.04 28 May 2009


.



• Custom Reports

The Custom Reports folder contains any custom reports created usingthe Custom Reports utility. This utility is used to create and buildreports using the tables and data from TBS databases.

Edit menuThe Edit menu accesses the TBS main databases. These databasescontain all of the information you need to run TBS effectively for yourorganization.

To access these databases, click Edit in the main window, and then selectfrom the following:

• Organizational Hierarchy

• Employees

• External Parties

• Roles/Projects

• Asset Assignments

• Telephone Configuration

• Location Books

• Rate Tables

• Taxes

• Call Database

External PartiesThe External Parties Database contains information about individualsor companies with whom you have regular contact. It includes suchinformation as the external party’s name, address, telephone number,and account code. Use this database to define the telephone numbersand optional account codes for your customers and contacts so youcan identify commonly called telephone numbers on your detail andsummary reports. This database can also be used to maintain a list of yourfrequently called customers or clients.


NN43050-602 03.04 28 May 2009


.

TBS interface 47

Roles/ProjectsThe Roles/Projects Database contains information about the differentroles or projects that require reporting in TBS. It is used to assignextensions, authorization codes, account codes, or dedicated trunk groupsto projects or personnel for reporting purposes. For example, it can containinformation about individuals or companies who use dedicated extensionsbut are not included in the Employee Database (for example, contractworkers). It can also contain information on projects that require dedicatedextensions and, therefore, require a name and organizational position forreporting.

Asset AssignmentsThis database defines how the different assets are assigned to thecorporate entities in the Employee, External Parties, and Roles/ProjectsDatabases.

Telephone ConfigurationThe Telephone Configuration Database is the main costing database.It combines rate tables, location books, and carrier pricing templates tocalculate usage costs for the various trunk groups that are defined for thesites in your organization. It also calculates additional fixed costs, whichcan be added to the basic usage costs of these trunk groups. As well,it enables you to assign various reporting groups to calls for the systemdetail and summary reports.

When calls are made through the trunks in these trunk groups, TBS usesthe Telephone Configuration Database to calculate their total costs. It canthen assign these costs to the appropriate extensions (and, therefore,personnel), as well as any defined organizational hierarchy levels withinyour company.

The following is a summary of some of the features of the TelephoneConfiguration Database:

• You can define multiple telephone configurations, call digit translations,and carrier pricing templates. This allows you to configure multiplecosting scenarios for a specific location, and then compare rates fromdifferent carriers based on your telephone usage patterns. This way,you can find out the true savings of using different carriers.

• This single editor enables you to define multiple telephoneconfigurations, and assign any predefined call digit translations andcarrier pricing templates to them.


NN43050-602 03.04 28 May 2009


.


• The Telephone Configuration navigation tree enables you to view yourconfiguration information for each system. Therefore, you can easilymake any corrections to your configuration for all of your systems.

• The Bill Party Surcharge function is used to define and apply additionalcharges to calls over and above the standard charges calculatedusing the Telephone Configuration Database. These surcharges areassigned to bill (or call) parties—typically, the extension from whichthe call was placed, rather than the trunk line over which the call wastransmitted. This feature is used primarily in the hospitality and campusbilling market where TBS can be used to bill guests and other users.

Figure 13 "Telephone Configuration Database editor" (page 48) shows anexample of the Telephone Configuration Database editor.

Figure 13Telephone Configuration Database editor

Location BooksThe Location Books function is used to define the location books(distance-based, latitude and longitude, and non-distance-based),and virtual private network books, which are used by TBS. Locationbooks serve two purposes in calculating costs for TBS. Their first andprimary purpose is to find a meaningful location name for the source anddestination of a phone call. The second purpose is to obtain additionalrating information, which is used to determine the cost of a call. That is,


NN43050-602 03.04 28 May 2009


.

TBS interface 49

Location books identify the physical or virtual locations of calls so that TBScan apply the appropriate usage costs to them based on their distanceor codes.

Rate tablesRate tables provides TBS with the required rates and coverage areas.These are used to identify how the calls to different locations are costed.Using the rate tables, TBS can cost calls with the appropriate rates.Telephony Manager rate tables are ordered directly from the rate tablesvendor (For example, Avotus) and Telephony Manager Billing packagemust be ordered first. Customer also has web access for downloading ofthe rates and tariffs from the rate table vendor’s web site. Consult ’CS1000TM4.0 Order Management Knowledge Transfer Kit’ on Nortel PartnerInformation Center website: https://app12.nortelnetworks.com/cgi-bin/mynn/home/NN_prodDoc.jsp?BkMg=0&=25540&=-8026&=23&=12460 forrate tables ordering details.

For information about obtaining updated rate tables, contact your Norteldistributor.

TaxesThe Tax Definition Editor is used to define the taxes that are applied tothe telephone usage costs for your system. For example, if you want toadd a sales tax to all usage costs calculated for the main node, then enterthis tax value in this editor. You can then select it from the Tax Informationfields of the Node Information Editor. If your system requires compoundtaxes, then you must calculate them first, and then enter the resultingvalue in these fields.

Call DatabaseThe Call Database Editor is used to display and edit the call recordsstored in the Call Database. The Call Database contains all of the callrecords that have been collected from the switch. In some cases, it maybe necessary to edit or delete some call records (due to invalid fields, suchas corrupted dates or IDs). Use it to remove bad or unwanted sections ofthe database or replace invalid dates with valid dates.

ATTENTIONEach of the main database editors described previously record messages in theTelephony Manager Event Log Viewer for diagnostics and troubleshooting. Themessages typically indicate when the editor is launched; however, messagesonly appear after the editor is closed.


NN43050-602 03.04 28 May 2009


.


View menuThe View menu contains commands that are used to display or hide thegraphical toolbar and status bar. As well, you can clear the contents of theAlarms section and select the data to be displayed in the System Taskssection.

To access these functions, click View in the main window, and then selectfrom the following menu options:

• Toolbar

• Status Bar

• Clear Alarms section

• Settings

Tools menuThe Tools menu accesses the commands that manage the mainprocesses in TBS. Use these commands to start, stop, schedule,and configure the data collection, call costing, and data transmissionprocesses.

To access these commands, click Tools in the main window, and thenclick the following menu options.

ATTENTIONYou can also click the corresponding icons in the toolbar.

CollectionThe Collection menu accesses the functions that manage thedata-collection process.

• Start—Starts the data collection in either batch or real-time mode.

• Stop—Stops the data collection process.

• Schedule—Accesses the Scheduler to schedule data collection at alater date and time.

• Configuration—Defines the parameters used by TBS to communicatewith, and collect data from, the CS 1000 or Meridian 1 system.

CostingThe Costing menu accesses the functions that manage the call costingprocess.

• Start—Starts the call costing process.

• Stop—Stops the call costing process.


NN43050-602 03.04 28 May 2009


.

TBS interface 51

• Schedule—Accesses the Scheduler to schedule call costing at a laterdate and time.

• Configuration—Defines the costing parameters in the TelephoneConfiguration Database.

TransmissionThe Transmission menu accesses the functions that manage the datatransmission process.

• Start—Starts data transmission in real-time or batch mode.

• Stop: Stops the data transmission process.

• Schedule—Accesses the Scheduler to schedule data transmission at alater date and time.

• Configuration—Defines the parameters used by TBS to communicatewith and transmit data to an external source, such as a PropertyManagement System (PMS).

Options menuThe Options menu accesses the System Configuration function. To accessthis function, click Options > System Configuration in the main window.

System ConfigurationThe System Configuration function allows you to configure system options,data collection and transmission parameters, and alarm thresholds.

• System Tab—This tab contains processing parameters for the callrecords.

• Collection Tab—This tab contains the connection and communicationsparameters for data collection.

• Transmission Tab—This tab contains the connection andcommunications parameters for data transmission, as well as thetransmission setup configuration.

• Alarms Tab—This tab contains any alarm thresholds and theircorresponding alarm messages. These messages appear in theSystem Alarms section of the main window.

Setup Transmission Record Format Fields The Available Fields listbox in the Transmission tab contains all of the fields you can select foryour record format. The Selected Fields list box contains all the fieldsyou selected from the Available Fields list box (see Figure 14 "SetupTransmission Record" (page 52)). These fields are included in the outputstream during data transmission.


NN43050-602 03.04 28 May 2009


.


Figure 14Setup Transmission Record

The following is a list of the field names that you can select.

• Unique Record ID—Unique identifier for the call.

• Billing Extension—Extension that is billed for the call. On an outgoingcall, this is the extension that placed the call. On an incoming call, it isthe extension that received the call.

• Call Trunk—Trunk that carried the call.

• Billing Trunk (Tandem Only)—On a tandem call, two trunks areinvolved in the call. TBS creates two charge records, one for theincoming call on the originating trunk and the other for the outgoing callon the terminating trunk. When rating the incoming call, the originatingtrunk is considered to be the Call Trunk because it is the one carryingthe inbound traffic. The terminating trunk is the Billing Trunk becauseit can be used through the Corporate Directory trunk assets for billingback to a corporate entity. Conversely, when rating the outgoing call,the terminating trunk is considered to be the Call Trunk because it isthe one carrying the outbound traffic. The originating trunk is the BillingTrunk because it can be used by the Corporate Directory trunk assetsfor billing back to a corporate entity.

• Call Type (N=Normal, I=Internal, T=Tandem)—A Normal calldesignation is given to an outbound or inbound call involving an on-netparty and an off-net party (for example, either the originating ID orthe terminating ID is an extension, and the other ID is a trunk). An


NN43050-602 03.04 28 May 2009


.

TBS interface 53

Internal call designation is given to calls involving two on-net parties(for example, both originating and terminating IDs are extensions). Atandem call involves two off-net parties (for example, both originatingand terminating IDs are trunks).

• Calling Direction (O=Outbound, I=Inbound)—An outbound call isone placed by an on-net party (an extension) to an off-net party (forexample, a trunk is used to reach the off-net party). An inbound call isa call coming from an off-net party (for example, a trunk carries the callinto the switch) that terminates at an extension.

• Originating ID Type (D=Extension, T=Trunk)—Designates whether theoriginating party of the call is a trunk or an extension.

• Originating Extension/Trunk—Identifier of the originating party (forexample, the specific extension or trunk number of the originatingparty).

• Terminating ID Type (D=Extension, T=Trunk)—Designates whether theterminating party is a trunk or an extension.

• Terminating Extension/Trunk—Identifier of the terminating party (forexample, the specific extension or trunk number of the originatingparty).

• Date—Date on which the call was made.

• Time—Time of day at which the call was made.

• Billed Duration—Duration of the call used for billing. This is the actualduration of the call rounded according to the specified roundingparameters determined by the carrier.

• Duration—Actual duration of the call in seconds.

• Digits Dialed—Digits dialed that were recorded and output by theswitch in the CDR stream.

• Formatted Digits Dialed—Digits formatted after processing by thecosting function according to its call digit translation, access codes,and carrier pricing templates.

• Digits as Costed—Digits used by the costing function to determine thecall location and carrier pricing. These are the original digits dialedafter call digit processing and access code removal by the costingfunction.

• Account Code—Additional code dialed on a call for charge-backpurposes, often used by legal, accounting, and consulting firms toidentify a specific client for charge back.

• Authorization Code—Additional code dialed on a call to authorize andidentify the individual placing the call. This is often used in campus


NN43050-602 03.04 28 May 2009


.


environments when calls need to be placed from anywhere within thecampus.

• Calling Line ID (CLID)—Telephone number of the calling party on aninbound call.

• Dialed Number Info Service (DNIS)—Number dialed by the callingparty to reach the company.

• Area Code & Exchange (NPANXX)—North American numbering planarea code and exchange dialed on the call. On non-North Americancalls, this field contains the dial code of the location that matchedthe digits or CLID on the call. This is used when looking up the calllocation in the location book specified in the Telephone ConfigurationDatabase.

• Location—City name of the called or calling location, which is lookedup in the specified location book using digits or CLID on the call.

• Province/State—Province or state name of the called or callinglocation, which is looked up in the specified location book using digitsor CLID on the call.

• Country—Country name of the called or calling location, which islooked up in the specified location book using digits or CLID on thecall.

• Route—Route designation for the call specified by the TelephoneConfiguration Database.

• Call Cost—Basic cost of the call as determined by the TelephoneConfiguration Database before surcharging.

• Tax on Call Cost—Total tax charged on the above-listed Call Costaccording to the taxes specified in the Telephone ConfigurationDatabase.

• Call Cost + Taxes—Sum of the Call Cost and Tax on Call Cost.

• Surcharge—Surcharge applied to the call according to the Surchargingparameters specified in the Telephone Configuration Database.

• Tax on Surcharge—Tax amount on the surcharge calculated accordingto the taxes specified in the Telephone Configuration Database.

• Call Cost + Surcharge—Call Cost plus the Surcharge without taxes.

• Tax on (Call Cost + Surcharge)—Total tax on the Call Cost andSurcharge.

• Call Cost + Surcharge + Taxes—Total of the Call Cost and theSurcharge values and the taxes on those values.

• Tax 1, Tax 2, Tax 3 & Tax 4—Up to four different taxes can bespecified in the Telephone Configuration Database. These fields


NN43050-602 03.04 28 May 2009


.

TBS interface 55

contain the tax amount calculated on the above-listed Call Cost valueplus the Surcharge value for the four specified taxes.

• Off End Taxes—Tax applied to any charges that have gone off endfrom a TIE-line node programmed in the Telephone ConfigurationDatabase.

• User Defined—Any constant value that you wish to include in a specificlocation of the output data stream during data transmission. Forexample, the standard HOBIC record format for hotels may require a3-letter hotel ID column, which you can enter in the User Defined fieldas a constant value (for example, HB1). This value is included in therecord that is sent to a downstream property management system.When you select User Defined, it uses the constant value that youentered in the Sample Value field (located next to the selected fieldslist). As with the other fields defined in the data transmission, you canselect multiple User Defined fields and position them at any location inthe record.

TBS Display optionThe TBS Display option for collecting, costing, and transmitting call recordsnegatively impacts system performance by consuming system resources.To improve system performance, disable the TBS Display option.

Procedure 13Disabling the TBS Display option

Step Action

1 Select View > Settings in the TBS main window, as shown inFigure 8 "TBS main window" (page 36).

The Settings dialog box opens with the Collection tab selected.See Figure 15 "Settings dialog box: Collection tab" (page 56).


NN43050-602 03.04 28 May 2009


.


Figure 15Settings dialog box: Collection tab

2 Clear the Display CDR records as they are collected checkbox.

3 Select the Costing tab.

The Settings dialog box—Costing tab appears, as shown inFigure 16 "Settings dialog box: Costing tab" (page 57).


NN43050-602 03.04 28 May 2009


.

TBS interface 57

Figure 16Settings dialog box: Costing tab

4 Clear Display Call Records as they are costed.

5 Select the Transmission tab.

The Settings dialog box—Transmission tab appears, as shown inFigure 17 "Settings dialog box: Transmission tab" (page 58).


NN43050-602 03.04 28 May 2009


.


Figure 17Settings dialog box: Transmission tab

6 Ensure that the Display Call Records as they are transmittedcheck box is cleared.

7 Click OK.

--End--

Configuring TBSBefore using TBS, you must install and configure it as part of theTelephony Manager system. Refer to Telephony Manager 4.0 Installationand Commissioning (NN43050-300) for complete details of installing TBSas part of Telephony Manager and assigning it to a site and a system.

The following instructions and examples are intended to assist you inpreparing TBS for your own configuration. Because each telephonesystem is configured differently and each Telephony Manager installation


NN43050-602 03.04 28 May 2009


.

Configuring TBS 59

is different, these examples cannot predict every scenario. Use theseexamples to teach yourself how to configure your hardware and how toconfigure TBS software to work with this hardware.

These examples are designed to account for the majority of cases andprovide you with assistance in getting started.

This section describes how to configure TBS, using as an example ascenario with the following characteristics:

• The Acme Company has its head office located in Dallas, Texas. Thetelephone number for its head office is (214) 555-1111.

• The telephone system requires that users enter the access code 9before making any outgoing calls.

• There is one trunk route with 46 members on the Meridian 1. Theseare configured as trunks 2001 to 2046.

• The Meridian 1that is located in the switch room of the Acme Companyhead office building requires an MDR 2000 ISD to collect CDR data. Amodem is attached to it to allow for communications between it and aPC in another room. It has a dedicated extension number of 222.

• The PC on which TBS is installed is located in another room of thesame building. A modem is attached to the PC’s COM1 port and isused to connect to the MDR 2000 ISD.

SummaryThe following is a summary of the steps required to prepare and configureTBS to process call records. You need to perform these steps only whenyou first install and use TBS or if your configuration or hardware changes:

Procedure 14Preparing and configuring TBS to process call records

Step Action

1 Ensure that the system is configured to properly output CDRdata. See “Ensure that the system is configured properly” (page60).

2 Install and configure the buffer unit. See “Install and configurebuffer unit” (page 61).

3 Install any rate tables purchased for your dialing plan. See“Install rate tables and location books” (page 71).

4 Run TBS so it can be configured. See “Run TBS so it can beconfigured” (page 72).


NN43050-602 03.04 28 May 2009


.


5 Configure and test the data collection process before running itin a real-time situation. See “Configure and test data collection”(page 74).

6 Obtain the List Trunk and Member (LTM) values from theMeridian 1. See “Obtain LTM from the system” (page 78).

7 Configure the telephone. See “Prepare telephone configuration”(page 78).

8 Test the telephone configuration. See “Test telephoneconfiguration” (page 98).

9 Configure data transmission. See “Configuring datatransmission” (page 102).

--End--

For more details about each of the TBS functions and features describedin the following sections, refer to the online Help included with TBS.For more details about the hardware components included withTBS (for example, buffer units and modems), refer to the associateddocumentation.

Ensure that the system is configured properlyFor TBS to collect and process CDR data, the system must output the datain the proper format. You must, therefore, enable the required features andoptions in the system overlays. This section describes the options that arerequired for TBS to process the CDR data.

ATTENTIONThis document is not intended to describe all options related to CDR data.For complete details about the available CDR options and information aboutconfiguring CDR, see Call Detail Recording Fundamentals (NN43001-550).

Procedure 15Ensuring that the system is configured properly

Step Action

1 Select CDR output format.

In LD 17, at the TYPE prompt, respond with PARAM, select eitherNEW or OLD format CDR output (FCDR=NEW). TBS containsscript files for supported buffer units, including the MDR 2000ISD. As well, it can be configured to support both NEW and OLDCDR formats.

2 Configure Auxiliary Identification output in CDR record.

In LD 15, at the TYPE prompt, respond with CDR_DATA,configure the Auxiliary Identification to be output in CDR(AXID=Yes). The AXID field is not captured by TBS, but is


NN43050-602 03.04 28 May 2009


.

Configuring TBS 61

required to ensure that data fields output in the CDR recordappear in the expected positions.

3 Configure routes for CDR output.

In LD 16, configure the routes that output CDR data (CDR=Yes),and determine the type of CDR data to output. For example, youmay want to record all incoming calls and only outgoing toll calls.

4 Ensure that the SDI port for your system is configured to matchthe settings on the buffer unit. If you plan to collect data at ahigher baud rate, you may need to change both the SDI port andthe buffer unit settings.

--End--

The default settings for the MDR 2000 ISD are:

• Baud = 1200

• Data Bits = 8

• Parity = None

• Stop Bits = 1

If you plan to use the default values for the MDR 2000 ISD, you must usethe same values for the SDI port.

Install and configure buffer unitTBS collects CDR data from the system either directly or through one ofseveral types of buffer units. Based on your configuration, you may needto collect the CDR data from a buffer unit in a specific format and share itbetween different applications.

For this setup, assume that TBS is collecting CDR data from the MDR2000 Intelligent Storage Device (ISD). This section describes how toconnect the MDR 2000 ISD to the system and the PC using a modemconnection. This provides you with an example by which you can learnhow to configure the other Telephony Manager-supported buffer units.

If the system uses Ethernet connections, the MDR 2000e ISD is used.

Because other buffer units have different connection and communicationsrequirements, refer to their documentation for more details of configuringthem.

To collect Dialed Number Information Service (DNIS) data using an MDR2000 or MDR 2000e buffer box, see “Collecting Dialed Number InformationService data” (page 136).


NN43050-602 03.04 28 May 2009


.


Security precautions for MDR 2000 ISDThe MDR 2000 ISD is a precision electronic product. Remember toreview all of the documentation included with the MDR 2000 ISD beforeattempting to install and use it. Failure to observe the precautions andguidelines outlined in the documentation may lead to product failure,damage, and invalidation of all warranties.

CAUTIONCAUTION WITH ESDS DEVICESBefore handling the MDR 2000 ISD, take all proper electrostaticdischarge (ESD) precautions, including personnel andequipment grounding:

• Do not rest the MDR 2000 ISD on the power cord. Adamaged power cord can cause fires or electrical shocks.

• Do not use the MDR 2000 ISD in damp, dusty, or dirtyplaces.

• Store spare components in proper antistatic material.

• Make sure equipment is turned off before handling orchanging components.

ESD damage is not always immediate and can result in failuresafter months of operation.

Connect MDR 2000 ISD to system and PCThe first step is to connect and install the MDR 2000 ISD onto the system.It can then collect and store call records as they are output from thesystem. You must then connect the PC to the MDR 2000 ISD so TBScan collect the call records from its database files. In this example, youconfigure and connect modems to the MDR 2000 ISD and to the PC.

Use Procedure 16 “Connecting the MDR 2000 ISD to the system and tothe PC” (page 62) to connect the MDR 2000 ISD to the system, and thento the PC with a modem connection.

Procedure 16Connecting the MDR 2000 ISD to the system and to the PC

Step Action

1 Locate the system SDI port.

2 Connect the MDR 2000 ISD to the system SDI port using anRS-232C cable, as shown in Figure 18 "Meridian 1to MDR 2000ISD" (page 63).

Connect one end of the RS-232C cable to the PBX port on theMDR 2000 ISD using a male DB-25 connector, and the otherend to the SDI output port on the system.


NN43050-602 03.04 28 May 2009


.

Configuring TBS 63

Figure 18Meridian 1to MDR 2000 ISD

3 Connect the MDR 2000 ISD to the first modem:

a Connect the null modem cable, which is provided with theMDR 2000 ISD, from the Modem port of the MDR 2000 ISDto the serial port of the modem.

b Connect a telephone line cord from the To Line output jackof the first modem to the telephone jack.

4 Connect the PC to the second modem, as shown in Figure 19"MDR 2000 ISD to modems to PC" (page 64).

a Connect a modem cable from an available communicationsport (for example, COM 1) on the PC to the serial port of thesecond modem. If you have an internal modem attached toyour PC, ignore this step.

b Connect a telephone line cord from the To Line output jack ofthe second modem to the telephone jack.


NN43050-602 03.04 28 May 2009


.


Figure 19MDR 2000 ISD to modems to PC

5 Plug in and turn on the MDR 2000 ISD:

a Plug the MDR 2000 ISD AC adapter into the electrical outlet.

b Insert the AC power supply connector into the 9 VDC jack ofthe MDR 2000 ISD.

6 Plug in and turn on the modems:

a Plug the modem AC adapters into the electrical outlets.

b Insert the AC power supply connector into the power jack ofthe modem.

7 Test the MDR 2000 ISD to ensure that it is collecting data.

After you have turned on the MDR 2000 ISD, all the lights flashbriefly and the RUN and BMT indicators remain on. After thesecond valid call record is obtained, only the RUN indicatorremains on. The first valid call is used to populate the bufferregistries when the MDR 2000 ISD has been turned off and on.

--End--

The PBX indicator flashes as the MDR 2000 ISD receives data. Thisindicates that the data stream is being received. If the PBX light does notflash and you are sure that a call has been made, check the following:

• If you require a null modem adapter between the system and the MDR2000 ISD, then ensure that it is connected between the system’s SDIport and the PBX port of the MDR 2000 ISD.

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


NN43050-602 03.04 28 May 2009


.

Configuring TBS 65

Verify that the MDR 2000 ISD is collecting dataUse Procedure 17 “Verifying that the MDR 2000 ISD is collecting data”(page 65) to access the MDR 2000 ISD to view and verify that theincoming data stream is valid.

Procedure 17Verifying that the MDR 2000 ISD is collecting data

Step Action

1 Run a terminal program such as Windows HyperTerminal.

2 Dial the telephone number of the MDR 2000 ISD.

This is the number to which the MDR 2000 ISD was connectedby its modem. If the PC is connected directly to the MDR 2000ISD, then start typing the commands to edit the parameters. Forexample, enter 222.

3 Type <Ctrl-V> I D <cr>.

This verifies that you are communicating with the MDR 2000ISD. The response is the serial number of the MDR 2000 ISD.

4 To view the data, type <Ctrl-V> D U <cr> (you may need totype this twice).

If the data appears incorrect (for example, it contains randomcharacters), then there is probably a communications problem.

--End--

Changing communications parametersThe MDR 2000 ISD default communications parameters can be differentfrom the CS 1000 or Meridian 1 system. For example, the MDR 2000ISD baud rate defaults to 1200, and the system may be 9600. If they aredifferent, you must change the communications parameters of one or theother.

Procedure 18 “Changing the communication parameters of the MDR 2000ISD” (page 65) describes how to change the communications parametersof the MDR 2000 ISD and also configure it for NEW CDR format. If youwant to change the communications parameters on the system, refer tothe documentation provided with it.

Procedure 18Changing the communication parameters of the MDR 2000 ISD

Step Action

1 Run a terminal program such as Windows HyperTerminal.


NN43050-602 03.04 28 May 2009


.


2 Dial the telephone number of the MDR 2000 ISD (for example,222).

This is the number at which the MDR 2000 ISD was connectedthrough its modem. If the PC is connected directly to the MDR2000 ISD, then you can start typing the commands to edit theparameters.

3 Access the MDR 2000 ISD interface by typing<Ctrl-V> I M

The prompt M2K> appears.

4 Check the status of the MDR 2000 ISD by typingST <cr>.

The status appears, similar to that shown in Figure 20 "MDR2000 ISD status" (page 66).Figure 20MDR 2000 ISD status

5 To change the baud rate for the modem port on the MDR 2000ISD to 9600, typeSE (Option) BA (PBX) (enter) (Modem) 9600 (enter)

This responds as SE (Set Options) BA (Baud) PBX (PBX default)9600. The first command in this line selects the default baud ratefor the PBX port on the MDR 2000 ISD.

ATTENTIONIf you are changing the baud rate for the modem, ensure that themodem answers at the desired speed first. For example, if you areusing the Windows HyperTerminal program to access the modem, itprompts Connect 9600 when you are connected.


NN43050-602 03.04 28 May 2009


.

Configuring TBS 67

6 To quit and exit from this interface, type<cr>Q

After you have accessed the MDR 2000 ISD, remember toexit from it by typing Q (quit). If your communications sessionis interrupted (for example, by a disconnected line or a powerfailure), then you lose your edits.

--End--

Notes for customization stringsIn certain cases, you may need to change the customization strings ofthe MDR 2000 ISD to match the output of the system. To change thecustomization strings, use the CU (Customize) command in the MDR2000 ISD interface and change the strings as necessary. Refer to thedocumentation provided with the MDR 2000 ISD for more details about thecustomization strings.

Configuring a USB modem for use with Telephony ManagerThe installation program for the USB modem creates a virtual COMport. The virtual COM port allows various communications programsto seamlessly operate with USB modems. This section shows how todetermine if a virtual COM port has been created, and how to changewhich virtual COM port is associated with your USB modem.

To ensure your USB modem is associated with a virtual COM port, followthe subsequent procedure.

Procedure 19Checking for a virtual COM port

Step Action

1 To open the modem options dialog from your operating system,perform the following steps:

a For Windows 2000 and Windows Server 2003: Go to Start >Settings > Control Panel > Phone and Modem Options

b For Windows XP: Go to Start > Control Panel > Printersand Other Hardware > Phone and Modem Options

2 Click the Modems tab.

Your modem should be displayed in the list. Figure 21 "List ofinstalled modems" (page 68) shows one installed U.S.RoboticsUSB modem associated with COM3.


NN43050-602 03.04 28 May 2009


.


Figure 21List of installed modems

If the modem is not connected to the computer, it does notappear in the installed modems list. Connect your modem andreopen this dialog. If your modem is connected to your server,and has been properly installed, but still does not appear in thislist, Telephony Manager 4.0 does not support your modem. Ifyou see your modem, it has properly created a virtual COM portand is supported by Telephony Manager 4.0.

3 Take note of the COM port your modem is associated with, asindicated in the Attached To column. This is the COM port youneed to select when configuring the dialup parameters for acollection task in the Telecom Billing System.

--End--


NN43050-602 03.04 28 May 2009


.

Configuring TBS 69

Changing the virtual COM port to USB modem associationTelephony Manager 4.0 requires your USB modem to be associated witha COM port in the range between COM1 and COM10. Use Procedure 19“Checking for a virtual COM port” (page 67) to identify the COM port. Ifthe virtual COM port is not within the supported range; use Procedure 20“Changing the USB modem association with a COM port” (page 69) tochange the association.

Procedure 20Changing the USB modem association with a COM port

Step Action

1 Close all applications that may be using a COM port on theTelephony Manager server.

2 Open the System Properties dialog.

a For Windows 2000 and Windows Server 2003: Go to Start >Settings > Control Panel > System.

b For Windows XP: Go to Start > Control Panel >Performance and Maintenance > System.

3 Click the Hardware tab.

4 Click the Device Manager button.

5 Expand the Modems node of the tree and select your USBmodem.

6 Right-click and select Properties from the popup menu.

7 Click the Advanced tab. The figure Figure 22 "Advanced tab ofmodem properties dialog" (page 70) shows one properties dialogscreen for the U.S.Robotics USB modem.


NN43050-602 03.04 28 May 2009


.


Figure 22Advanced tab of modem properties dialog

8 Select the Advanced Port Settings button. A dialog similar toFigure 23 "Advanced port settings" (page 70) appears.Figure 23Advanced port settings


NN43050-602 03.04 28 May 2009


.

Configuring TBS 71

The COM Port Number select list allows you to change theCOM port to that with which the USB modem is associated, andcorrespondingly change the virtual COM port.

9 From the list, select a COM port not in use and which is withinthe range of COM1 to COM 8.

Many servers today do not have a COM port. You may chooseany port in the supported range. If a COM port is in use, theentry in the list states it as such. For example, if your serverhas a COM1, the list shows COM1 (in use) because this is aphysically present COM port that cannot also be a virtual COM.If you have installed a multi-modem or multiple-serial port cards,these cards also create virtual COM ports. Typically, they create2, 4, or 8 virtual COM ports numbered beginning at 3, 4, or 5.You may need to change their first virtual COM port, so yourUSB modem is mapped to a virtual COM port in the range ofCOM1 to COM10.

10 Click OK once the selection has been made.

If you have changed the COM port, the old virtual COM port isremoved, and the new one created. You can now use this virtualCOM port in the Telecom Billing System.

11 Close all open Device Manager and property dialogs.

--End--

Install rate tables and location booksBefore you configure TBS, you must install the rate tables that reflectyour telecommunications provider’s rates. These provide such rates aslong-distance call charges for direct dialed calls to North America, as wellas international long-distance charges. TBS requires these rate tables toaccurately apply costs to your long-distance calls.

ATTENTIONFor information on obtaining rate tables, contact your Nortel distributor.Remember that the rate table files must be compatible with the TBS software. Ifin doubt, check with your distributor before purchasing any rate tables.

As well as rate tables, you must install a set of location books for yoursoftware. Location books contain codes for the actual locations that areused by the rate tables to determine the charges incurred when callingthese locations.

To install the rate tables and location books, follow the instructionsincluded with them. Remember to install the rate table files onto yourTelephony Manager TBS directory so you can select the appropriate ratetable files when you are defining your carrier pricing templates.


NN43050-602 03.04 28 May 2009


.


Run TBS so it can be configuredIf Telephony Manager is not already running, click TM Navigator fromthe Start Up program group. In the Telephony Manager Navigator,open a predefined site and system (for example, Site=Acme Company,System=Head Office).

After you open the site and system, the window shown in Figure 24"Telephony Manager Navigator" (page 72) appears.

Figure 24Telephony Manager Navigator

From the selected site and system in the Telephony Manager Navigator,click Telemanagement, and then click Telecom Billing System.

This accesses the TBS application main window, shown in Figure8 "TBS main window" (page 36), from which you can configure thecommunications parameters, telephone configuration, and rate tables forinitial use. You must also test the data collection and run reports to see ifthe data was collected and costed properly.

When you first run TBS for a specific site and system, the TelephoneConfiguration Wizard appears.


NN43050-602 03.04 28 May 2009


.

Configuring TBS 73

ATTENTIONThe wizard that permits basic telephone configuration appears only when asystem is created or after certain restores from backup. If the information is notprovided to the window presented, then costing of local calls dialed using 7digits does not provide a location name for those calls. If the wizard is run aftera restore from backup, parts of the costing configuration are deleted and youmust run the configuration again. See Figure 25 "Basic telephone configuration"(page 73).

Figure 25Basic telephone configuration


NN43050-602 03.04 28 May 2009


.


This allows you to optionally enter a basic telephone configuration for thissite and system. Because you are not using the Telephone ConfigurationWizard to enter your configuration, leave these fields blank and click OKto access TBS.

Configure and test data collectionBefore you enter your telephone configuration, verify that TBS is collectingdata from the system in the correct format. This way, you can test theconfiguration against actual calls. To test the data collection, enter thedata collection parameters, collect the call records from the system, andview them in the Call Database.

Enter data collection parametersFor TBS to collect data from the system, you must enter the data collectionparameters for the site and system. Make sure that you have alreadyconnected and configured your hardware (see “Ensure that the systemis configured properly” (page 60) and “Install and configure buffer unit”(page 61)).You need to access the Communications tab only to select thecommunications and data collection parameters.

In this example, you are collecting data from the Meridian 1or CS 1000Ssystem through the MDR 2000 ISD buffer unit.

ATTENTIONYou can also collect data from other buffer units. You can also collect datadirectly from the system using a direct connection or from the DBA application(network connection).

For more information about configuring TBS to collect data from theTelephony Manager DBA application, see “Collecting data from TelephonyManager DBA Application” (page 120).

Procedure 21Entering data collection parameters

Step Action

1 In the TBS main window, select Options > SystemConfiguration.

The System Configuration dialog box appears.

2 Select the Collection tab.

3 Enter your communications and collection parameters.

For example, enter the following values:

• Type: Dial-Up

• Phone No: 222


NN43050-602 03.04 28 May 2009


.

Configuring TBS 75

• Re-dials: 3

• Port: COM1

• Baud Rate: 9600

• Data Bits: 8

• Parity: None

• Stop Bits: 1

4 In the Collection Script box, enter the name of the script filethat is used for this data collection.

This file contains the instructions used to communicate withthe buffer unit and collect data from it. The script filename youselect depends on the type of buffer unit and the format of thedata being collected. For example, if you are collecting datafrom the MDR 2000 ISD, then select MDR2000.COL. See “TBSscripts” (page 195) for a list of supported buffer units and theircorresponding script filenames.

In certain cases, you may want to report on transferred callrecords (also known as X records) and on Abandoned calls(also known as B records). With the X record option, callrecords representing calls that have been transferred are brokendown into individual call records based on the call transfer.For more information about reporting on X and B records, see“Processing X (transferred) records” (page 22) and “ProcessingB (Abandoned call) records” (page 23).

ATTENTIONX records cannot be processed if you are collecting data from theMDR 2000 ISD.

5 Click OK.

--End--

Test data collectionNow that you have configured your hardware and entered the requiredcommunications parameters, you are ready to test the data collection. Atthis stage, run a data collection only as a test. Later, you can invoke datacollection after you enter all of your system information and are ready torun it live.


NN43050-602 03.04 28 May 2009


.


Procedure 22 “Testing the data collection” (page 76) describes how to testthe data collection process, assuming the following scenario.

• The system is outputting CDR data to the SDI port.

• The MDR 2000 ISD is directly connected to the system and iscontinuously collecting and storing the raw CDR data (call records) asthey are output from the system.

• TBS collects this CDR data from the MDR 2000 ISD and stores it inthe Call Database.

Procedure 22Testing the data collection

Step Action

1 Wait for some calls to be recorded by the system.

Either wait for some calling activity on the system or make a fewtelephone calls. If the MDR 2000 ISD is properly connected tothe system, it collects and stores these call records as they arerecorded by the system (note that the BMT light is out).

2 Start the data collection process by selecting Tools > Collection> Start in the TBS main window.

3 In the Start Collection dialog box, select the Batch option.

4 Click Start.

TBS starts collecting the call records from the MDR 2000 ISDand places them in the Call Database. During the data collectionprocess, TBS displays both the collection activities as well asthe call records as they are collected in a window similar to thatshown in Figure 26 "Call Database" (page 77).


NN43050-602 03.04 28 May 2009


.

Configuring TBS 77

Figure 26Call Database

5 To view the status of the collection:

a Select the Collection tab.

b Click Status.

6 To view the call records:

a Select the Collection tab.

b Click Data.

7 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 fieldsdepending on the Orig or Term values.

• Check the first digits in the Digits Dialed fields to confirm theaccess codes.

• Check the call records’ dates and times to ensure that theymatch the date and time on the system.

8 If the data appears invalid, repeat the collection process.

Check to ensure that your hardware is connected properly andthat you have the correct settings. Check the parameters on yoursystem and the MDR 2000 ISD.

--End--


NN43050-602 03.04 28 May 2009


.


Obtain LTM from the systemBefore you start entering the telephone configuration, you must first obtainthe List Trunk and Member (LTM) report from the system. This providesyou with valuable information about how to prepare your configuration.

ATTENTIONIf you have Internet Security and Acceleration (ISA), the LTM does not show anymembers for the service routes. Print the Route Data Block (RDB) to determinethe service routes associated with the ISA routes. All members indicated in theISA route must be added to the associated service routes.

To obtain the LTM and RDB information for your configuration, access thesystem and print the associated LTM and RDB reports from LD 21.

Prepare telephone configurationThe next step in preparing TBS is to define the telephone configuration.This identifies how TBS processes the call records. It involves assigningthe appropriate rate tables and carrier pricing templates to your system’strunk groups, entering any call digit translations, and setting any reportingoptions.

Because defining the telephone configuration is a complex task, it ishelpful to demonstrate how to define one using an example configuration.This example represents a typical configuration and helps you to prepareyour own configuration.

ATTENTIONThis telephone configuration is only an example. When preparing your ownconfiguration, you must enter your own company’s system and rate information.Review all of the documentation provided with your system and by your serviceprovider. This includes trunk route and member numbers, output format, andrate table names.

Defining the telephone configurationPerform the following steps to define the telephone configuration:

Procedure 23Defining the telephone configuration

Step Action

1 Access Telephone Configuration Database editor.

2 Update Call Type Definitions table. See “Update Call TypeDefinitions” (page 80).

3 Define the Cost Field. See “Define Cost Field” (page 80).

4 Define Carrier Pricing Template. See “Define Carrier PricingTemplates” (page 81).


NN43050-602 03.04 28 May 2009


.

Configuring TBS 79

5 Define Call Digit Translation. See “Define Call Digit Translation”(page 85).

6 Define surcharges. See “Define surcharges” (page 86).

7 Enter telephone configuration:

a Create telephone configuration. See “Create TelephoneConfiguration (General Information)” (page 93) .

b Add Main Node. See “Add Main Node (Node InformationEditor)” (page 94) .

c Add Long Distance Service Definition to Main Node. See“Adding Long-Distance Service Definition to Main Node”(page 95) .

--End--

Access Telephone Configuration Database EditorTo access the Telephone Configuration Database tables, select Edit >Telephone Configuration in the TBS main window.

Figure 27 "Telephone Configuration Editor" (page 79) shows a sampleTelephone Configuration Editor. When you access this function for the firsttime, it appears with blank menu options in the Telephone Configurationnavigation tree.

Figure 27Telephone Configuration Editor


NN43050-602 03.04 28 May 2009


.


Review the LTM report from the system to identify the call types forreporting. For example, you can configure the call types CO, DID, 800,and TIE. With this information, you can create columns of costing details orcost summaries for these call types.

Update Call Type DefinitionsThe Call Type Definition function contains a list of the types of calls thatmay be used by your organization (for example, international, local, and soon). You select these call types when you define the dialing patterns ofyour organization in the Carrier Pricing Template. Select these predefinedcall types when entering your costing and reporting options.

The Call Type Definition function displays a list of default call types,which you can select when entering your costing and reporting options.In this step, add any additional call types that you may require for yourconfiguration (for example, emergency calls). If you do not require anyadditional call types, skip this step.

The following procedure shows how to enter the call type Emergency forEmergency 911 calls.

Procedure 24Entering a call type

Step Action

1 From the Telephone Configuration navigation tree, click CallType.

The Call Type Definition grid appears in the right section with alist of default definitions.

2 Click a blank line at the bottom of this grid.

3 Click Emergency.

This adds this call type to this list. The display shows the defaultcall types plus the new one that you just entered. Calls from thistrunk are now costed according to the template you created.

--End--

Define Cost FieldYou must also define the cost field. The cost field determines the reportgrouping and summary field on reports.


NN43050-602 03.04 28 May 2009


.

Configuring TBS 81

Procedure 25Defining a cost field

Step Action

1 From the Telephone Configuration navigation tree, click CallField.

The Call Type Definition table appears.

2 Enter the cost field.

For example, enter DDD.

--End--

Define Carrier Pricing TemplatesCarrier Pricing Templates help determine the type and cost of a call. TheTelephone Configuration Database uses these templates to assign coststo the calls based on the trunks used and the digits dialed. For example,you define a template for regular long-distance service with multiple pricingdefinitions.

For each digit pattern that represents a billable call, assign either the ratefile and table from your telephone company or a flat per-minute or per-callcharge.

Procedure 26Defining the Carrier Pricing Template

Step Action

1 From the Telephone Configuration navigation tree, clickCarrier Pricing Template.

2 Select File > New Carrier Pricing Template.

The Carrier Pricing Template section appears, as shown inFigure 28 "Carrier Pricing Template" (page 82).


NN43050-602 03.04 28 May 2009


.


Figure 28Carrier Pricing Template

3 In the Name field, enter Sample Rates.

4 Click Use Default Template to create a set of default values forNorth America.

Update these values with your own system requirements.

--End--

Modify pricing definitions in Carrier Pricing Template Pricingdefinitions allow TBS to interpret any type of call containing identifiabledigit patterns, and then cost them accordingly. They appear as aline-by-line listing in the grid.

For example, you edit only the pricing definitions for international andNorth American long-distance calls to specify the appropriate rate tablesfor your carrier. These default pricing definitions are already created toprovide you with standard North American dialing patterns. You only needto select the appropriate rate tables for them. The following examplesdemonstrate the use of the rate tables.

• International calls—These types of calls use the location bookTeleglobe International Location Book.

• National calls—These types of calls use the location book VHDATALocation Book.


NN43050-602 03.04 28 May 2009


.

Configuring TBS 83

In certain cases, you need to add new pricing definitions to match yourown configuration and dialing patterns.

ATTENTIONThe order in which you enter these pricing definitions is important. Duringcosting, calls are compared to the digit pattern of the first definition at the top ofthe list. TBS then proceeds down the list until it matches the Digit Pattern fieldand, if used, the rate table. TBS then proceeds to the next definition if the ratetable cannot cost the call (even if the digit patterns are matched).

When you enter digit patterns for the pricing definitions, you can usecertain wild card and format characters as digit placeholders. Use theasterisk (*) (multiple placeholder) or question mark ? (single placeholder)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 that need tobe suppressed during rate table lookups but displayed on reports. Usethe hide flag . (period) to hide all of the digits that follow it in formattedreports. Refer to the online Help under Pricing Definition for more detailsabout using wild card characters.

You can modify each pricing definition in this Carrier Pricing Template byclicking the record line in the list and typing over the available fields. Toview each record in a dialog box, click the record line and click Edit.

For example, to edit the International pricing definition, click the recordline for International (you may need to scroll across the grid to locateInternational in the Comments box), and then click Edit. In the dialogbox that appears, enter the desired information for it. After you enter therate information for each type of call, click OK to save it and return to theCarrier Pricing Template grid.

Procedure 27Modifying pricing definitions: international calls

Step Action

1 Click the line in the Carrier Pricing Template section thatcontains International in the Comments box.

2 Click Edit.

The Carrier Pricing Template appears, as shown in Figure 29"Carrier Pricing Template: international calls" (page 84).


NN43050-602 03.04 28 May 2009


.


Figure 29Carrier Pricing Template: international calls

3 Enter the required information.

4 Click OK.

--End--

Procedure 28Modifying pricing definitions: long distance (national) calls

Step Action

1 Click the line in the Carrier Pricing Template section thatcontains National in the Comments box.

2 Click Edit.

The Carrier Pricing Template window appears, as shown inFigure 30 "Carrier Pricing Template: long distance (national)calls" (page 85).


NN43050-602 03.04 28 May 2009


.

Configuring TBS 85

Figure 30Carrier Pricing Template: long distance (national) calls

3 Enter the required information.

4 Click OK.

--End--

Repeat this procedure for other dialed digit patterns where other chargesmay apply.

Define Call Digit TranslationThe Call Digit Translation function translates the digits dialed on callrecords. This translation can be applied to all outgoing calls in the systemor to calls on specific trunk groups in the system. This allows TBS toprocess and print a different digit pattern from the one that is actuallydialed (for example, suppressing access codes).

Call Digit Translation does not affect Calling Line ID or Automatic NumberIdentification (CLID/ANI) digit patterns on incoming calls.

For example, you build a System Call Digit Translation table to remove theaccess code 9 from the digits dialed of the call records. This way, eachcall record appears without the access code on reports. The digit is theaccess code used to access a trunk on the CS 1000 or Meridian 1 systemto initiate a call. For example, your system may require that you enter 9to select a trunk to make an outgoing call. Each call record contains theaccess code digits, which are entered as part of the digit stream.


NN43050-602 03.04 28 May 2009


.


Procedure 29Defining call digit translation

Step Action

1 Select Call Digit Translation in the Telephone Configurationnavigation tree.

2 Select File > New Digit Translation Table to add a newdefinition for this table.

This creates another menu option entitled New Digit TranslationTable 1 under this menu option. For this new call digittranslation, a blank table appears in the right section.

3 Rename this table by typing Sample CDT in the Name box.

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

• Match Digits: 9

• Replace Digits: -

5 Leave the remaining fields and boxes blank.

--End--

If you do not know your access codes, follow the steps in Procedure 30“Determining your access codes” (page 86).

Procedure 30Determining your access codes

Step Action

1 Go to the TBS main window.

2 Select the Collection tab of the System Task section.

3 Click Data.

4 Check the Digits field for any of the outgoing call records.

If the system inserts an access code in the digit stream, itappears here.

--End--

Define surchargesThe Bill Party Surcharge function of the Telephone Configuration Databaseis used to define any charges that are applied to calls in addition to yourtrunk-based charges. This function allows for additional telephone usage


NN43050-602 03.04 28 May 2009


.

Configuring TBS 87

charges to be assigned to users based on their extensions, authorizationcodes, or account codes. The filterable data transmission function canpost this usage data to an existing Property Management System.

If you are not applying surcharges, skip this step.

Create surcharge profile and surcharge groups You must createsurcharge profiles and surcharge groups. Surcharge profiles define twokey pieces of information: they define how to calculate the surcharges andto whom these surcharges are to be applied.

Define surcharges When you create the surcharge profile and thegroups for this profile, you are ready to apply the surcharges to the entitiesthat make up (or members of) the groups. Enter the organizational unitsin the Members tab for each group. You already defined these units inthe Organizational Hierarchy Database and assigned the appropriateextensions in the Employee Database. Enter the appropriate surchargesfor these members in the Surcharges tab.

The following procedure creates the surcharge profile and group andalso defines the surcharges for the group. This procedure is appropriatefor hotels, motels, hospitals, and possibly businesses that run the phonesystem as a profit center. Repeat the procedure as necessary to definesurcharges for various surcharge profiles and surcharge groups.

Procedure 31Creating the surcharge profile or groups and configuring surcharges basedon calling pattern

Step Action

1 Select Surcharging in the Telephone Configuration navigationtree.

2 Select File > New Surcharge Profile to add a new surchargeprofile to this table.

3 In the Name box, enter the name of the surcharge profile.

For example, enter Room Group Surcharge.

4 From the first Identify Bill Party list, select Extension.

5 For each surcharge group:

a Select the surcharge profile that you just created.

b Select File > New Surcharge Group.

c In the Name box, enter the name of the surcharge group.

For example, enterGuest Rooms.


NN43050-602 03.04 28 May 2009


.


6 From the surcharge profile select the name of the surchargegroup .

For example, select Guest Rooms from Room Group Surcharge.

7 Select the Members tab.

8 Select the path of the surcharge group from the OrganizationalUnit list.

For example, select Rooms International/DowntownProperty/Guest Rooms.

9 If there are no sub-units of this node that require additionalsurcharges, clear the Include Sub-units check box.

10 Select the Surcharges tab.

The Surcharge Group—Surcharges tab appears, as shown inFigure 31 "Surcharge Group: Surcharges tab" (page 88).Figure 31Surcharge Group: Surcharges tab

11 Enter the information for each category of surcharge.

a Click on an empty line.

b Enter the information for each surcharge category in theappropriate fields.

For example, to assign a surcharge of $1.00 to all local outgoingand incoming calls and $2.00 to all national outgoing and


NN43050-602 03.04 28 May 2009


.

Configuring TBS 89

incoming calls, enter the information shown in Table 1 "Entries:Surcharges tab" (page 89).

Table 1Entries: Surcharges tab

Line Rule Name Call Type Cost/Call TransmitCall

1 Local Calls Local 1.00 Enabled

2 National Calls National 2.00 Enabled

--End--

The following procedure configures surcharges based on account codesthat lawyers, accountants, engineers, and others who market their timeand expertise would use.

Procedure 32Configuring surcharges based on account codes

Step Action

1 Create an Org Path to hold a unique organization for theaccount codes.

a Typically the top level is the company name, and divisionsand departments are present to support report grouping.

b Chose the names for each department under Acct Codesfrom lists in subsequent steps.

c Create an entry for each surcharge amount required.

2 Create a Surcharge Profile, and assign an Account Code toidentify the bill party, as shown in Figure 32 "Assign Code toidentify bill party" (page 90).


NN43050-602 03.04 28 May 2009


.


Figure 32Assign Code to identify bill party

3 Create the number of Surcharge Groups required for varioussurcharge amounts.

4 Assign each group an Organization Unit from the Org Pathcreated in Step 1.

5 Configure the Surcharges tab as required.

You must provide a Rule Name.

You must provide either a Digit Pattern or Call Type.

Complete the other fields as appropriate to apply the surcharge.

6 Assign the Surcharge Profile in the Basic Configuration page.

See Figure 33 "Assign the Surcharge Profile" (page 91).


NN43050-602 03.04 28 May 2009


.

Configuring TBS 91

Figure 33Assign the Surcharge Profile

7 Create a Role/Project for each account code.

8 Assign the Org Path appropriate to the desired surcharge rate.

Add as many account codes as required, and keep in mind thateach one takes one RU license.

To change a surcharge applied to an account code, select adifferent Org Path in the Roles and Projects Editor. See Figure34 "Roles and Projects editor" (page 92).


NN43050-602 03.04 28 May 2009


.


Figure 34Roles and Projects editor

9 Cost or recost collected records.

10 Consult the Account Code Surcharge Detail report or AccountCode Surcharge Summary report.

Although the costs appear on other reports as well, these tworeports are the most useful to verify your configuration.

--End--

Enter Telephone ConfigurationThe Telephone Configuration Database is the key to pricing callsand tracing them to their destinations. This database defines thetype of costing used through each defined service and includes anyadditional costs defined for your system and location. Each definedservice uses predefined location books and rate tables based on yourtelecommunications carrier’s offerings. TBS uses this configurationinformation to cost the call records and report on them.


NN43050-602 03.04 28 May 2009


.

Configuring TBS 93

Now that you have all of the elements required to construct yourtelephone configuration, you must add them to this table. The TelephoneConfiguration table (in the Telephone Configuration Database editor) issorted 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.

Create Telephone Configuration (General Information) The first partof the Telephone Configuration table contains its general information andoptional costing for internal calls.

Procedure 33Creating a new telephone configuration table and entering generalinformation

Step Action

1 Select the Telephone Configuration menu option.

2 Select File > New Configuration.

A data entry form appears.

3 Enter a descriptive name for this configuration in the TelephoneConfiguration box.

For example, enter Telephone Configuration RoomsInternational.

4 Specify the Call Digit Translation table that is to be used for thisTelephone Configuration by selecting Sample CDT from the CallDigit Translation list.

You previously defined this table in the Call Digit Translationfunction.

5 If you want to assign bill party surcharging to this configuration(that is, you want to apply additional surcharges for telephoneusage based on extensions, authorization codes, or accountcodes), select the surcharge definition from the Call PartySurcharge Profile list.

This example does not require surcharges, so leave this fieldblank.

6 If your system outputs CDR for internal calls (that is, calls madebetween extensions within the system), then enter these costs inthe Internal Calls fields of this table.


NN43050-602 03.04 28 May 2009


.


For this example, leave the default values in these fields.

--End--

Add Main Node (Node Information Editor) The next step in enteringthis telephone configuration is to define the general information for theMain Node. Because a telephone configuration can contain multiplenodes, you must define each node separately. For example, yourcompany’s telephone system may span different offices (nodes), whichmay use multiple TIE trunks. For this example, you are creating theminimum required node—the Main Node.

Procedure 34Adding a node to a defined configuration

Step Action

1 Select the menu option Telephone Configuration RoomsInternational which you just created in Procedure 33 “Creatinga new telephone configuration table and entering generalinformation” (page 93).

2 Select File > New Node.

The Node editor window opens.

3 In the Node Name box, enter the name for this node.

For example, enter Main Node. The title in the menu changesto Main Node.

4 In the Node Location box, enter the city and province/state foryour company.

For example, enter Dallas, Texas.

5 In the Main Phone Number box, enter the telephone numberfor this location.

For example, enter 214-555-1111.

6 From the Location Book list, select VHDATA Location Book.

7 Because this is the Main Node, leave the Time ZoneAdjustment box at default value: 0.

8 Because this is the Main Node, leave the Currency Exchangebox at its default value: 1.

9 Leave the Main Node check box turned on.

Only one node can have this selected.

10 If the rates defined for this node require additional taxes, thenselect them from the Tax Information lists.


NN43050-602 03.04 28 May 2009


.

Configuring TBS 95

You must have defined these taxes in the Taxes editor.

--End--

Adding Long-Distance Service Definition to Main Node Now that youhave selected a node, you must enter its pricing definitions. These pricingdefinitions apply to different trunk groups. For example, trunks 1 to 5 maybe used for regular long-distance calling, and trunks 7 and 8 may be usedexclusively for toll-free calls.

Procedure 35Adding long-distance services definitions to a node

Step Action

1 Select the Main Node menu option.

2 Select File > New Service/Trunk Group.

This creates another menu option entitled New Service 1, anddisplays the tabs in which you can enter the service definition,fixed and variable and carrier costs, and reporting options.

3 Select the Service Definition tab.

The Service Definition tab appears, as shown Figure 35 "ServiceDefinition" (page 96).


NN43050-602 03.04 28 May 2009


.


Figure 35Service Definition

a In the Name box, enter the name of the Main Trunk Groupover the New Service 1 text.

For example, enter CO Trunks. The navigator tree menuoption changes to reflect what you just typed.

b Leave the Termination section at the default values.

c (Optional) Enter a minimum call duration and a connect timeadjustment to allow for a delayed connection in the BillingParameters table.

This may be required for certain types of calls, such asInternational calls. If the trunks have answer supervision,these adjustments are not required, regardless of the type ofcall.

1. Click the first record line of the Billing Parameters table.

2. In the Match Digits box, enter 011.The system interprets all calls starting with the digits 011(international calls) and applies the minimum call durationand connect time adjustment from the following fields.

3. In the Comments box, enter International Calls.


NN43050-602 03.04 28 May 2009


.

Configuring TBS 97

4. In the Min. Duration box, enter 10.This is the minimum call duration in seconds that a callmust exceed for it to be costed.

5. In the Connect Time box, enter 5.This is the time in seconds that the system allows fora connection. This is subtracted from the call durationbefore costing.

d In the Trunk Numbers section, enter the trunk range for thistrunk group in your CS 1000 or Meridian 1 system.

1. Enter the Total Number of Equipped Trunks.

2. Enter a Line Description.

3. In the Low Range and High Range fields, enter the trunkrange (up to seven digits) in the format [R][R]RMMM,where [R][R]R represents the trunk route number andMMM represents the trunk member number.The digits RMMM are required. The leading digits [R][R]are optional if they are 0.

For example, enter the following:

• Total Number of Equipped Trunks: 1

• Line/Description: CO Trunks

• Low Range: 2001

• High Range: 2046

4 Enter fixed costs for these trunk groups, if required by thesystem.

a Select the Fixed Costs tab.

b Enter the fixed costs per minute, per call, per meter pulse, orper month, as required.

c (Optional) Define these costs as applying to outgoing orincoming calls.

5 Enter variable and carrier costs that are applied to calls madeon this service.

a Select the Variable and Carrier Costing tab.

b Enter the costs.

The carrier costs vary depending on the destinations of theoutgoing calls.

For example, select the predefined Carrier Pricing Template forall calls using this service. The Carrier Pricing Template can thendistinguish between different types of calls for its costing.

6 Enter the call reporting options for this trunk service.


NN43050-602 03.04 28 May 2009


.


These options define how calls that use this service appear onreports. For example, you can suppress all incoming calls.

a Select the Report Options tab.

b Click the first record in the grid.

c From the Call Type list, select All Calls.

d From the Cost Field list, select the cost field defined inProcedure 25 “Defining a cost field” (page 81).

For example, select DDD.

e From the Print Option list, select Detail.

This indicates that these calls are displayed in the mainreport body of the detail reports.

f In the Route Description box, enter DDD.

This is the route used on detail reports for this call.

7 Select File > Close.

--End--

Test telephone configurationNow that you have entered your system costing model and configuration,test the accuracy of the configuration. To do so, you must apply thesecosts to the collected call records and print some reports to review thegenerated costs.

Apply costs to call recordsTBS applies the costs based on your Telephone Configuration Databaseand Rate Tables as a separate step to data collection. That is, after youcollect the call records from the CS 1000 or Meridian 1 system, you mustapply costs to them as a separate step.

Procedure 36Applying costs to call records

Step Action

1 Select Tools > Costing > Start in the TBS window.

The Start Costing window appears.

2 Select the Batch Costing Mode option.

This performs a onetime costing of all non-costed call records.

3 In the Available Telephone Configurations list, select theTelephone Configuration Head Office.


NN43050-602 03.04 28 May 2009


.

Configuring TBS 99

This applies this specific telephone configuration to these callrecords.

4 Click Start to cost the call records.

TBS starts the costing procedure.

5 Select the Costing tab Status view of the System Taskssection to check this process.

After it displays the message The Costing task hascompleted, you are ready to generate reports based on thecosted call records.

--End--

Reapply Costs to RecordsIn some cases, it may be necessary to reapply costs to records so thatthe software can generate valid reports. For example, a value changeor correction in the Telephone Configuration database may require newcosts. TBS does not cost records that have already been costed once.Therefore, the original costs from the records must be deleted first.

Procedure 37Reapplying costs to call records

Step Action

1 In the TBS main window, select Edit > Call Database.

The Call Database appears.

2 In the Collected Records view, select the records to whichcosts are to be reapplied by doing one of the following:

• Highlight the records that need to be reset.

• Click the box in the first column header to select all records.

CAUTIONUse the reset command with care. You arepermanently deleting the costs from the chosenrecords.

3 Select Records > Reset Status.

4 Close the Call Database.

5 in the TBS main window, select Tools > Costing > Start toreapply costs.

6 Observe the online status.


NN43050-602 03.04 28 May 2009


.


7 When the process is complete, select the Data tab and reviewthe information that appears on the screen.

--End--

Generate reportsGenerate the following reports to test the accuracy of the telephoneconfiguration that you just entered:

• Telephone Configuration Report—This report lists telephoneconfiguration information. Use Procedure 38 “Generating theTelephone Configuration report” (page 100) to generate the report.

• Trunk Diagnostic Report—This report compares trunk ranges youentered in the Telephone Configuration with the trunks that have actualcall activity. Use Procedure 39 “Generating the Trunk DiagnosticReport” (page 101) to generate the report.

• Extension Diagnostic Report—This report compares the extensionsassigned to users in the Corporate Directories (that is, employees,external parties, and roles and projects) with the extensions that haveactual call activity. Use Procedure 40 “Generating the ExtensionDiagnostic Report” (page 101) to generate the report.

• Exception Chronological Report—This reports lists in chronologicalorder all of the calls that were made, and then collected by TBS.Review this report to verify that the calls were processed and costedaccurately. Look for calls that have no location (except toll-free calls).Check that the long-distance calls have costs assigned to themand that local calls do not. Some common errors in the TelephoneConfiguration Database include incorrect access codes and missingtrunks. Use Procedure 41 “Generating the Exception ChronologicalReport” (page 102) to generate the report.

If any of these reports appears inaccurate, review your input and make anynecessary adjustments to your telephone configuration.

ATTENTIONYou must define a printer before you generate the Telephone Configurationreport, regardless of what output type you select for the report.

Procedure 38Generating the Telephone Configuration report

Step Action

1 Select File > Reports in the TBS main window.

The TBS Reporting window appears, as shown in Figure 12"TBS Reporting window" (page 39).


NN43050-602 03.04 28 May 2009


.

Configuring TBS 101

2 From the TBS Reports menu folder, double-click the UtilityTools folder.

3 Select Telephone Configuration.

4 From the Output Type list, select Printer.

5 From the Configuration list, select the telephone configuration.

This represents the telephone configuration you just defined.For example, select Telephone Configuration RoomsInternational.

6 Click Go to print the report.

--End--

Procedure 39Generating the Trunk Diagnostic Report

Step Action




3 Select Trunk Diagnostic Report.





--End--

Procedure 40Generating the Extension Diagnostic Report

Step Action





NN43050-602 03.04 28 May 2009


.


3 Select Extension Diagnostic Report.





--End--

Procedure 41Generating the Exception Chronological Report

Step Action



2 From the TBS Reports menu folder, double-click the CostAnalysis folder.

3 Select Exception Chronological Report.


5 From the Configuration list, select Telephone ConfigurationRooms International.

This represents the telephone configuration you just defined.


--End--

Configuring data transmissionThe Data Transmission function is used to transmit the call records toan external device or location, such as a Property Management System(PMS). For example, you can configure TBS to post the call usage recordsfor your hotel’s guests to a Property Management System using theACK/NAK interface protocol. After you configure the data transmission, runit in real time along with the data collection.


NN43050-602 03.04 28 May 2009


.

Configuring TBS 103

ATTENTIONThe transmission from TBS does not include the department name. If the PMSdoes require department names, use the export feature in TBS to export thedepartment names.

Procedure 42Preparing for data transmission

Step Action

1 Select Options > System Configuration in the TBS mainwindow.

2 Select the Transmission tab.

The Transmission tab appears, as shown in Figure 36"Transmission tab" (page 103).Figure 36Transmission tab

3 From the Connection Type list, select Direct.

4 In the Port Settings boxes, enter the communicationsparameters required to connect to your Property ManagementSystem.


NN43050-602 03.04 28 May 2009


.


For example, enter the following settings:

• Port: COM2

• Baud Rate: 9600

• Data Bits: 8

• Parity: None

• Stop Bits: 1

5 Click Record Format in the Transmission tab. For moreinformation, see “Field Data Type Formatting for Export andTransmission” (page 231).

6 Enter the fields you want to include in the call records that areposted.

7 Click the ellipsis (...) next to the Record Filter list to select thefilters for the call records being posted.

These extensions represent the guest rooms and suites inyour hotel. For example, you only post call records that haveextensions 100 to 999.

8 In the Filters dialog box that appears, click Add.

9 In the Filter dialog box, select the Extension/Trunk tab.

10 Enter the filters as required to post only the call records for givenextensions.

For example, enter the filters shown in Table 2 "Trunks andextensions filters" (page 104) to post only the call records forextensions 100 to 999. The first line represents outgoing callsfrom this range of extensions. The second line represents allincoming calls to this range of extensions:

Table 2Trunks and extensions filters

OriginatingID Type Low

High

TerminatingID Type Low

High

ShowCost

Extension 100 999 Both

Extension 100 999 Both

11 Select Include and Activate to include this filter range.

12 In the Filter Name box, enter the name for this filter.

For example, enter Guest Rooms and Suites.

13 Click OK to save this filter range and return to the previousdialog box.

14 Click OK again to save it and return to the Transmission tab.

15 Click the Record Filter list.


NN43050-602 03.04 28 May 2009


.

Data collection and transmission 105

16 Select the name of the filter you just created.

For example, select Guest Rooms and Suites.

17 From the Interface Protocol list box, select ACK/NAK.

18 In the Script box, enter Transmit.TRN.

19 Under the Record Posting Options (ACK/NAK only) options,enter 1 in the Retries field.

20 Click OK.

--End--

Data collection and transmissionNow that you have entered all of your collection, costing, and transmissionsettings, you are ready to start collecting and processing your call records.

Collect dataProcedure 43Collecting data

Step Action

1 Select Tools > Collection > Start in the TBS main window.

The Start Collection dialog box appears, prompting you to selectthe collection mode and start the data collection.

2 Select Real Time to have the system continuously collect CDRrecords from the MDR 2000 ISD.

3 Click Start.

--End--

The data collection starts. The status section displays a list of the callrecords as they are collected.

Cost call recordsProcedure 44Costing call records

Step Action

1 Select Tools > Costing > Start in the TBS main window.

The Start Costing dialog box appears, prompting you to selectthe costing mode and start the call costing process.

2 Select Real Time to have the system apply costs to the collectedcall records continuously.


NN43050-602 03.04 28 May 2009


.


3 From the Available Telephone Configurations list, select thetelephone configuration to be used.

This applies this specific telephone configuration to these callrecords. For example, select Telephone Configuration RoomsInternational.

4 Click Start to start costing the call records.

--End--

Transmit call recordsProcedure 45Transmitting call records

Step Action

1 In the TBS main window, select Tools > Transmission > Start.

The Start Transmission dialog box appears, prompting youto select the data transmission mode and start the datatransmission.

2 Select Real Time to have the system continuously transmit callsthat have not been transmitted.

3 Click Start to start transmitting the call records.

--End--

Maintenance tasksAfter you initially populate the main databases with your company’sinformation, you must collect data, apply costs to the call records, andgenerate reports regularly. Because TBS can perform these activitiesbased on a routine schedule, establish your own schedule of activities toallow for regular data collection and reporting. As well, routinely maintainand back up your databases to keep them accurate.

The following sections outline the standard procedures to incorporate intoyour regular operational routines. They provide a model for you to followduring the operation of TBS.

Schedule of activitiesTable 3 "Telephony Manager Scheduler" (page 107) contains arecommended schedule of activities to follow while using TBS. To simplifythese activities, use the Telephony Manager Scheduler to schedule themto run at regular intervals.


NN43050-602 03.04 28 May 2009


.

Maintenance tasks 107

Table 3Telephony Manager Scheduler

Task Frequency

Data collection Daily

Costing of call records Daily

Report generation Monthly

Employee Database Weekly

External Parties Database Weekly

Roles/Projects Database Weekly

Telephone Configuration Database Monthly

Location Books Quarterly

Rate Tables Quarterly

Archive Call Database Monthly

Purge Call Database Monthly

Restore Call Database When recovering lost data

Data collection: dailyThe collection of call records from the system (or optional CDR bufferunit) to the PC is a key task of your TBS operations. Without this detailedcalling information, TBS reports do not contain any call record data.Therefore, it is important to regularly collect call records from the system.

Run data collection on a daily basis. If there is a problem with the flow ofdata from the system, the system warns you of the malfunction within ashort time period. This early detection can provide for quick correctiveaction and minimal data loss.

To collect data for a system, access TBS for the selected system, andthen click Tools > Collection > Start from its main window. From the StartCollection dialog box, select either Batch or Real Time mode, and thenclick Start. Select the Batch option to perform a onetime data collectionfrom the system, or from the buffer unit. Select Real Time to continuouslycollect CDR records from the system or from the buffer unit.

During the data collection process, TBS collects data from the system (oroptional buffer unit), and builds that data into the Call Database. Basedon the size of the buffer unit, communications usually take place nightly.Less frequent data collection is possible, provided the buffer unit does notreach capacity.


NN43050-602 03.04 28 May 2009


.


ATTENTIONIf the buffer reaches capacity and data collection has not been initiated, thesystem can lose valuable call records. Remember to collect data regularly.

The status of each data collection procedure is tracked in the Collectiontab of the System Tasks section. As well, all activity completed by TBSis recorded in the Telephony Manager Event Log Viewer for diagnosticsand troubleshooting. You can access the Event Log Viewer from theTelephony Manager Navigator. Review this information while collectingdata to ensure that the system is collecting properly.

After CDR data collection is complete, you are ready to apply costs tothem and generate reports based on this information.

Data collection troubleshootingDuring data collection, TBS displays the call records it has collected. If thisnumber fails to increment or remains at zero, then either there is no datato collect or TBS is not communicating with the system.

Procedure 46Troubleshooting data collection

Step Action

1 Select the Collection tab from the System Tasks section in theTBS window.

2 Click Status to review the task’s status.

3 Check the System Alarms section in the TBS window to reviewany relevant information.

4 If communicating through a modem, ensure that the modem’s AA(auto-answer) light is on.

5 Make sure that the communications port you specified in theSystem Configuration Collection tab is the same as theconnection on the back of your PC (the port on which youconnected your cable).

--End--

The following is a list of common data collection problems:

• Data files are in use by another network workstation, or the CallDatabase Editor is open.

• The communications parameters are not configured properly for thesystem.


NN43050-602 03.04 28 May 2009


.


• The data collection parameters are not configured properly.

• The PC has insufficient disk space for the Call Database.

Costing of call records: dailyTBS applies the costs based on your Telephone Configuration Databaseand Rate Tables as a separate step to data collection. That is, after youcollected the call records from the CS 1000 or Meridian 1 system, youmust apply costs to them based on the telephone configuration. As withthe Data Collection procedure, run the costing procedure on a daily basis.This way, you can quickly identify any problems in the costing model ortelephone configuration.

To cost call records for a system, perform the following steps.

Procedure 47Costing call records

Step Action

1 Access TBS for the selected system.

2 Select Tools > Costing > Start in the TBS main window.

3 In the Start Costing window, select one of the following:

• Batch— to perform a onetime costing of all non-costed callrecords.

• Real Time—to continuously cost all non-costed call records.

4 Click Start.

--End--

During this process, TBS creates a costed Call Database containingthe calculated costs. The status of each costing procedure is trackedin the Costing tab of the System Tasks section. As well, all activitycompleted by TBS is recorded in the Event Log Viewer for diagnostics andtroubleshooting. Review this information while costing the call records toensure that the system is costing properly.

After you cost the call records, you are ready to generate reports based onthis information.


NN43050-602 03.04 28 May 2009


.


Report generation: monthlyTBS reports provide information on the details of the call records thatwere collected from the CS 1000 or Meridian 1 system. They also includeinformation on your system databases and configurations. After you collectthe call records from the system, generate your detail and summaryreports to display their information.

Procedure 48Generating reports

Step Action


The TBS Reporting window appears, as shown in Figure 12"TBS Reporting window" (page 39)

2 Select the report you want to generate from the Report menu.

For example, to select the Extension Detail Report, select TBSReports > Cost Analysis > Extension Detail Report.

3 Select the output device from the Output Type list.

4 (Optional) Select the report parameters (filters).

a Click the ellipsis (...) next to the Filters field.

The Filters dialog box appears.

b Click Add.

The Filter editor dialog box appears.

c Enter the report’s filters.

d Enter a unique name for the report parameters (filters) in theFilter Name box.

e Exit from this function.

f Select this predefined filter from the Filter list.

5 Click Go to generate the report.

6 (Optional) Click Schedule to schedule a report to run at aspecific date and time.

This invokes the Telephony Manager Scheduler. Use theScheduler to enter the date and time that you want to run thereport. It then generates it at the selected date and time.

--End--


NN43050-602 03.04 28 May 2009


.


Database updatesTBS contains a set of functions to assist you in managing your system’sdatabases. Proper management of data ensures that your reports containtimely and accurate information. If TBS databases contain outdatedinformation (for example, the Employee Database contains employeeswho are no longer with the company), then the reports are inaccurate.Therefore, update your databases regularly.

As well, it is important to make backup copies of the main TBS databasefiles for recovery purposes. This way, if your PC loses data (for example,in case of hardware or disk failure), you can recover the lost data.

ATTENTIONIMPORTANT!You must decide on the frequency of the backup and archive procedures. Basethis frequency on the size of your data records and your system capacity. As arule, back up your data once a month.

Nortel recommends that you update the following databases on a regularbasis:

• Employee Database—weekly

• External Parties Database—weekly

• Roles/Projects Database—weekly

• Telephone Configuration Database—monthly

• Location Books—quarterly

• Rate Tables—quarterly

Employee Database: weeklyThe Employee Database contains a list of employees linked to specifictelephones and their associated display names on the system. When a callrecord is generated, it must be associated with a specific telephone. TheEmployee Database contains this information, as well as the organizationalhierarchy level to which this telephone belongs. If you have installedthe Telephony Manager Station Administration application, then this ispopulated with data from the CND through the Billing Sync process. Referto Telephony Manager 4.0 System Administration (NN43050-601) for moreinformation about editing this database.

The Employee Database controls the distribution of costs to the differentcost centers within your company. Charges for each extension must beallocated to the appropriate organizational level. Update this directory asoften as necessary depending on the frequency of changes made to theemployee records. As a rule, update it weekly.


NN43050-602 03.04 28 May 2009


.


Procedure 49Updating the Employee database

Step Action

1 Print the Employee Directory Report.

a Select File > Reports in the TBS main window.


b Select TBS Reports > Directory Information > EmployeeDirectory.

c Select Printer as the Output Type.

d Click Go.

2 On the hard copy printout of this report, enter the changes thathave occurred over the past week (for example, new department,staff moving to another department, new extensions, and so on).

3 Update the database using the Employee Editor.

a Select Edit > Employees in the TBS main window.

The Employee Editor appears.

b Enter the changes.

c The Department changes must be manually entered into theCND record.

4 Print the Employee Database Report again and verify yourchanges.

5 (Optional) Save this hard copy printout to track changes over along time frame without having to repeatedly access the system.

--End--

External Parties and Roles/Projects Databases: weeklyThe External Parties Database contains information about individualsor companies with whom you have regular contact. The Roles/ProjectsDatabase contains information about the different roles or projects thatrequire reporting in TBS. To avoid errors or out-of-date records, printthe External Parties and the Roles/Projects reports, and check them.Remember to update these databases weekly.


NN43050-602 03.04 28 May 2009


.


Telephone Configuration Database: monthlyThe Telephone Configuration Database contains the information neededto cost your telephone carrier services. Periodically, you may be requiredto enter changes to ensure the accuracy of your rates. These changesmay involve edits to the rate tables, carrier pricing templates, or to thetrunk tables.

Procedure 50Updating the Telephone Configuration database

Step Action

1 Use Procedure 38 “Generating the Telephone Configurationreport” (page 100) to print the Telephone Configuration Report.

2 Check that the information on this report is complete.

3 Review the information for accuracy with the appropriatepersonnel.

4 Make any changes required to the Telephone ConfigurationDatabase.

a Select Edit > Telephone Configuration in the TBS mainwindow.

b Enter the changes in the database.

--End--

Location books: quarterlyLocation books serve two purposes in calculating costs for TBS. Their firstand primary purpose is to find a meaningful location name for the sourceand destination of a phone call. The second purpose is to obtain additionalrating information, which is used to determine the cost of a call. That is, itidentifies the physical or virtual locations of calls so that TBS can apply theappropriate usage costs to them based on their distance or codes.

Periodically, location designations change (for example, new areacodes are added to the North American V&H grid). You must, therefore,remember to update your defined location books on a regular basis. Youcan obtain the latest location books from your dealer.

Rate Tables: quarterlyThe Rate Tables provide TBS with the required rates and coverage areasused to identify how the calls to different locations are costed. This way,TBS can associate calls with their corresponding rates.


NN43050-602 03.04 28 May 2009


.


Similar to the Location Books, Rate Tables must be updated on a regularbasis due to changes in tariffs. You must, therefore, update your ratetables on a regular basis. Contact your Nortel distributor for information onobtaining updated rate tables.

Call Database maintenance: monthlyThe Call Database contains all of the call records (CDR) that you havecollected from your CS 1000 or Meridian 1 system and optionally costedusing the Telephone Configuration Database. As TBS collects call recordsfrom the system, the Call Database file continues to grow in size and takeup more space on your PC’s disk drive. Therefore, periodically removeany old or unwanted call records from the Call Database to make room forthe new call records. This prevents the Call Database from taking up toomuch disk space on your PC. Remove old data from the Call Database ona monthly basis. Based on the size of your Call Database, you may needto remove old data from it more frequently.

You remove old call records from the Call Database by either copying (orarchiving) them to an external source, or by deleting them. The followingsections briefly describe the functions used to archive, delete (purge), andrestore these call records.

Archive Call DatabaseThe Archive function is used to copy, or archive, a range of call recordsfrom the Call Database to an external device, such as a network drive ora disk. Use the Archive function’s Purge option to delete this same rangeof call records from the current Site/System directory on your PC after thearchive has completed. This frees more disk space on your PC for newcall records. You can archive an entire Call Database, or you can archivea range of call records within a Call Database based on their call dates.This way, you can archive any old call records that you no longer require.If you ever need this data again, you can copy it back to your source CallDatabase by using the Restore function.

Procedure 51Archiving the Call database

Step Action

1 Select File > Call Database > Archive in the TBS main window.

2 Enter your archive information.

3 Click Go to proceed with the archive.

--End--


NN43050-602 03.04 28 May 2009


.


Purge Call DatabaseThe Purge function is used to delete—or purge—a range of call recordsfrom the Call Database. This frees more disk space on your PC for newcall records and improves overall system performance. You can purge anentire Call Database, or you can purge a range of call records within a CallDatabase based on their call dates. This way, you can remove any old callrecords that you no longer require.

Procedure 52Purging the Call database

Step Action

1 Select File > Call Database > Purge in the TBS main window.

2 Enter your purge information.

3 Click Go to start purging the range of call records.

The Archive/Restore/Purge status dialog box appears with thefollowing message:

Purge is an irreversible action. Are you sure you wantto continue?

4 Click Yes.

--End--

Restore Call DatabaseThe Restore function is used to copy—or restore—the archived callrecords from an external device such as a network drive back to the CallDatabase.

Procedure 53Restoring the Call database

Step Action

1 Select File > Call Database > Restore in the TBS main window.

The Restore dialog box appears.

2 Enter your restore information.

3 Click Go to proceed with the restore operation.

--End--


NN43050-602 03.04 28 May 2009


.


Chronological summary of tasksThe section contains a chronological summary of the major maintenanceactivities.

Daily

• Collect CDR data from your buffer unit (Nortel recommends that youuse a buffer unit to store CDR data). Collections can be scheduledto occur automatically every day, or they can be manually invokedeach day. If you are not using a buffer unit, a dedicated PC COM portcontinuously collects the CDR data as they are output from the system.

• Review the data collection Status section daily to ensure that yourscheduled collection was successful. As TBS collects call records, itdisplays them in the data collection Data tab.

Ongoing (recommended weekly)

• Perform your Employee Database updates.

• Update External Parties and Roles/Projects Databases. Thesedatabases assign the names of external parties or roles and projectsto the digits dialed. The reports can then include both the dialednumber and these names. If you use these databases, update themperiodically.

• Perform database backups. It is important to maintain backup files ofyour databases on external devices or media for security purposes.

Monthly tasks

• Run your monthly reports. Select your reporting filters to ensure thatyou are reporting on the correct subset of the collected data. Typically,this includes configuring the date for your reporting period.

• Archive or purge your Call Database data. Remove any old orunwanted call records from the Call Database to make room for thenew call records. Based on the size of your Call Database, you mayneed to remove old data from it more frequently than once a month.

Quarterly tasks

• Update your system Location Books. Periodically, locationdesignations change (for example, new area codes are added to the


NN43050-602 03.04 28 May 2009


.

Using TBS for hospitality billing 117

North American V&H grid). You must, therefore, remember to updateyour defined location books on a regular basis.

• Similar to the Location Books, Rate Tables must be updated on aregular basis due to changes in tariffs.

Contact your Nortel distributor for information about obtaining updatedRate Tables.

Using TBS for hospitality billingIn addition to its standard general business functions (that is, thoserequired by most organizations to collect, cost, and report on calls), TBSalso includes functions and reports to allow for hospitality and campusbilling. The Bill Party Surcharge function applies charges to calls inaddition to the trunk-based usage charges. This allows for additionaltelephone usage charges to be assigned to users based on such criteriaas their extensions, authorization codes, and account codes. The filterabledata transmission function can post this usage data to an existing PropertyManagement System.

This section explains how to configure TBS to process call records forhospitality billing. Specifically, it describes how to configure the systemdatabases to assign surcharges to guests at a hotel and transmit this datato a Property Management System.

Example scenarioThe instructions in this section are based on the following scenario:

• A hotel chain, Rooms International, has a property located in Dallas,entitled Downtown Property. The telephone number for this hotel is(214) 555-1111. The telephone system requires that all users andguests enter the access code 9 before making any outgoing calls.

• There are five trunks on the Meridian 1. These are configured as trunk1 to 5.

• The Meridian 1located in the switch room of this property requires anMDR 2000 ISD to collect CDR data. A modem is attached to it to allowfor communications between it and a PC in another room. It has adedicated extension number of 222.

• The PC on which TBS is installed is located in another room of thesame building. A modem is attached to the PC COM1 port and is usedto connect to the MDR 2000 ISD. TBS collects the CDR data from theMDR 2000 in real-time mode.

• TBS must also post all calling activity for its rooms (Guest Roomsand Suites with extensions 100 to 999) to its Property ManagementSystem.


NN43050-602 03.04 28 May 2009


.


System schematicFigure 37 "System block diagram" (page 118) outlines the relationshipbetween TBS and its hardware components.

Figure 37System block diagram

Configuring and running TBS in a hospitality environmentThe steps required to configure TBS to process call records in a hospitalityenvironment are as follows:

Procedure 54Configuring TBS to process call records in a hospitality environment

Step Action

1 Ensure that the system is configured to properly output CDRdata. See “Ensure that the system is configured properly” (page60).

2 Install and configure the MDR 2000 ISD. See “Install andconfigure buffer unit” (page 61).

3 Install any rate tables and location books that were purchasedfor your dialing plan. See “Install rate tables and location books”(page 71).

4 Run TBS so it can be configured. See “Run TBS so it can beconfigured” (page 72).

5 Configure and test the data collection process before running itin a real-time situation. See “Configure and test data collection”(page 74).

6 Obtain the List Trunk and Member (LTM) values from thesystem. See “Obtain LTM from the system” (page 78).


NN43050-602 03.04 28 May 2009


.

Using TBS for hospitality billing 119

7 Configure the Organizational Hierarchy and EmployeeDatabases to include the extensions for the guest rooms andsuites, as well as for the hotel’s staff.

a Configure the Organizational Database. See “OrganizationalHierarchy Editor” (page 24).

For this example, the hotel property in Dallas (DowntownProperty is the organizational level in the OrganizationalHierarchy Database. Guest Rooms and Suites are sublevelsof the Downtown Property level. You can then enter thecorresponding room numbers and details in the EmployeeDatabase.

b Configure the Employee Databases.

For hospitality billing, this database can be used to storeinformation about the rooms within your property (forexample, the extensions in these rooms). This informationis required to cost and allocate telephone calls to the properextensions and cost centers within your hotel—for bothguests and staff.

Use Procedure 9 “Adding a new employee” (page 33) to addthe guest rooms to the Employee Database and assign themto the Rooms International node. You must repeat thesesteps for each guest room and suite that has a telephoneextension and that requires billing.

8 Configure the Telephone Configuration Database

a Access the Telephone Configuration Database editor. See“Access Telephone Configuration Database Editor” (page 79).

b Update the Call Type Definitions table. See “Update CallType Definitions” (page 80).

c Define the Cost Field. See “Define Cost Field” (page 80).

d Define carrier pricing templates. See “Define Carrier PricingTemplates” (page 81).

e Define the call digit translation. See “Define Call DigitTranslation” (page 85).

f Define the bill party surcharges. See “Define surcharges”(page 86).

1. Create the surcharge profile and surcharge groups.Create the surcharge profile Room Group Surcharge,containing the surcharge groups Guest Rooms andSuites. These surcharge groups allow you to applytelephone usage charges to the Guest Rooms and Suitesthat you defined in the Organizational Hierarchy andEmployee Databases.

2. Define surcharges for the surcharge groups.


NN43050-602 03.04 28 May 2009


.


Apply the surcharges to the rooms and suites. UseProcedure 31 “Creating the surcharge profile or groupsand configuring surcharges based on calling pattern”(page 87) to assign a surcharge of $1.00 to all localoutgoing and incoming calls, and $2.00 to all nationaloutgoing and incoming calls.

g Enter the telephone configuration. See “Enter TelephoneConfiguration” (page 92).

9 Test the telephone configuration. See “Test telephoneconfiguration” (page 98).

10 Configure data transmission to post call records to theProperty Management System (PMS). See “Configuring datatransmission” (page 102).

11 Start collecting and transmitting data. See “Data collection andtransmission” (page 105).

The transmission from TBS does not include the departmentname. If the PMS does require department names, use theexport feature in TBS to export those names.

--End--

Collecting data from Telephony Manager DBA ApplicationThe Telephony Manager Data Buffering and Access (DBA) applicationcollects CDR data from the Communication Server 1000 and Meridian 1systems and stores this data to a text file, detail1.img, in the TelephonyManager system. As the DBA collects data, it appends this data to this textfile. TBS (after it is configured) can then collect the CDR data from this filefor processing and reporting.

This section describes how to configure TBS to collect this data from theDBA application. This section assumes that you have already configuredthe DBA application in the CS 1000 and Meridian 1 systems, and inTelephony Manager. For more information about this application, seeTelephony Manager 4.0 System Administration (NN43050-601).

Procedure 55Collecting data from DBA

Step Action

1 Select Options > System Configuration in the TBS mainwindow.

2 Select the Collection tab.


NN43050-602 03.04 28 May 2009


.

Collecting data from Telephony Manager DBA Application 121

The Collection tab appears, as shown in Figure 38 "ConfiguringTBS to collect data from Telephony Manager DBA" (page 121).Figure 38Configuring TBS to collect data from Telephony Manager DBA

3 From the Connection Settings Type list, select File.

4 Select Delete File(s) After Collection.

If this option is disabled, duplicate records are collected.

5 In the File Name field, enter the directory and filename of theDBA text file, or click ... next to the File Name field and navigateto the file.

For example, enter or select C:\Nortel\Common Data\SampleSite\Sample Meridian 1\detail1.img.

6 In the Collection Script field, enter either sl1new.col orsl1old.col, depending on the type of CDR data produced by thesystem.

7 Click OK to save these settings.

8 Select Tools > Collection > Start to collect the data.

The Start Collection dialog box appears (see Figure 39 "StartCollection dialog box" (page 122)).


NN43050-602 03.04 28 May 2009


.


Figure 39Start Collection dialog box

9 Select either BATCH or REAL TIME for the Collection Mode.

--End--

Importing and exporting TBS dataThis section contains a general overview of the Import and Export utilities.It describes their basic function and purpose.

ImportThe Import utility is used to import data records from an external source toa specific site/system and convert them to a format compatible with theTelephony Manager databases. This function is useful for quickly updatingyour databases with data from another application.

When importing data, you can select from a predefined importconfiguration or you can define your own configuration. The followingparagraphs outline how to import data using a predefined and customconfiguration. Review the information later in this section for details aboutthe functions and windows used to perform these steps.

Import data using a predefined configurationTo import data using a predefined configuration, you must first select theconfiguration and its component values. This configuration outlines theparameters of the data being imported. This includes such information asthe format of the data, the types of records, and their field parameters(character length, position, and so on). Telephony Manager includes a setof predefined import configurations for common database types. You canthen select the source from where the data is to be imported (for example,disk drive, CD-ROM, and so on).

The following is a summary of the steps required to import data using apredefined configuration:


NN43050-602 03.04 28 May 2009


.

Importing and exporting TBS data 123

Procedure 56Importing data using a predefined configuration

Step Action

1 Access the import utility - see “Access the Import utility” (page123)

2 Select import configuration components - see “Select importconfiguration components” (page 124)

3 Define the import configuration and import the data - see “Definethe import configuration and import the data” (page 125)

--End--

Import data using a custom configurationTo import data using a custom configuration, you must first define theimport configuration. This configuration outlines the parameters of the databeing imported. This includes such information as the format of the data,the types of records, and their field parameters (character length, position,and so on). You can then select from where the data is to be imported (forexample, disk drive, CD-ROM, and so on).

The following is a summary of the steps required to import data using acustom configuration:

Procedure 57Importing data using a custom configuration

Step Action

1 Access the import utility - see “Access the Import utility” (page123)

2 Import configuration list - see “Import configuration list” (page124)

3 Define the import configuration and import the data - see “Definethe import configuration and import the data” (page 125)

--End--

Access the Import utility Use a predefined or custom configuration toimport data from the Import utility.

• In TBS, select File > Import in the TBS main window.


NN43050-602 03.04 28 May 2009


.


The Import window appears, which allows you to select from a list ofpredefined configurations or add your own custom configuration.

Select import configuration components The Import (Select an ImportConfiguration) function is used to select a predefined import configuration.

Procedure 58Selecting a predefined import configuration

Step Action

1 Select the import configuration name from the Select an ImportConfiguration list.

2 To define the components of the imported file, click the ellipsis(...).

The Import window appears where you select the tables ordatabases to be imported.

3 After you select the predefined configuration and the sourcedirectories, click Go to import the data.

--End--

Import configuration list If you are creating a new import configuration,click the ellipsis (...) to access the Import-System name window. TheImport-System name window contains a list of predefined importconfigurations.

Procedure 59Creating a new configuration

Step Action

1 Do one of the following:

• To add a new configuration, click Add.

• To edit an existing configuration, select the name of theconfiguration and click Edit.

The Import window.

2 Select the import configuration name.

3 Click OK.

--End--


NN43050-602 03.04 28 May 2009


.


Define the import configuration and import the data The ImportConfiguration Definition function is used to select and define the type ofdata being imported into the Telephony Manager databases.

Procedure 60Defining the import configuration and importing the data

Step Action

1 Select the import configuration name from the ImportConfiguration Definition list.

2 Enter the following information to define the import configuration:

a Configuration Name—Name of this configuration. The namehelps to identify this configuration from others in the ImportConfigurations List.

b Tables/Database—Type of tables into which the data isimported. For example, if you are importing data into theTelephony Manager Telecom Billing System, you can selectfrom Call Records and Organization Levels to import data intothese databases.

c File/Database Type—Type of data being imported. Selectone of the following options:

• Corporate Directory data.Importing or exporting Corporate Directory data inserts thefile type as Text File (comma separated values).

• CDR data.Importing or exporting CDR data inserts the file type asTBS, which results in writing an Access database (*.mdb).

• V4 Employee Directory sets.Importing or exporting V4 Employee Directory setsFile/Database Type to V4 Store.

d File/Database Location—To select the source of theimported database file (that is, the directory or drive fromwhich the file is imported), click the ellipsis (...) next to theFile/Database Location field. From the Open window thatappears, select the drive and directory of the database filebeing imported, and then click OK. Notice that this appears inthe File/Database Location field.

e Format—To select the format of the imported file, clickFormat. This accesses the Import Format window in whichyou can select the field properties for the imported file.

f File/Table Name—Filename of the database being imported.


NN43050-602 03.04 28 May 2009


.


g Update Activity—How this database is updated. Select fromthe options listed in Table 4 "Import update activity options"(page 126).

Table 4Import update activity options

Option Meaning

Append Non Matching Appends non-matching records

Update Matching Updates matching records

Update Matching or Append Either updates or appends asappropriate

h Description—Description of the contents of the tableselected from the Tables/Database Name navigation tree.

3 Click OK to save the settings.

4 Click Go to import the data.

--End--

Restore Call Database using Import utilityThis example demonstrates how to restore the Telecom Billing System’sCall Database from drive A.

ATTENTIONOpening CSV files in Microsoft Excel may reformat certain data such astelephone numbers, resulting in the loss of data that cannot be recovered if thefile is saved. Nortel recommends you backup your data before opening files withMicrosoft Excel.

ATTENTIONImport/Export works with MS Access 97 files. Archive and Restore at File > CallDatabase works with comma separated values files. The Import/Export functionmay have trouble with Access files created with newer versions of Access.

Procedure 61Restoring the Call Database

Step Action

1 Access the Import utility by selecting File > Import in theTelecom Billing System main window.

2 Select Merge CDR/Costed Data as the Import Configuration.

3 To define the parameters for this restore operation, click theellipsis (...) next to this list box.

The Import configuration window appears listing CDR/CostedData Merge as the destination (To Telecom Billing System).


NN43050-602 03.04 28 May 2009


.


4 In the File/Database Location field, enter the source of thisrestore operation. Click the ellipsis (...) to view a list of availabledrives.

5 (Optional) To restore a range of call records based on theirdates:

a Click the ellipsis (...) next to the Filter list.

The Filters window appears.

b Create a new filter definition and enter the range of call datesfor this filter.

c Select this new filter name from the Filter list.

6 Click Go to proceed with the restore operation.

--End--

Export

ATTENTIONRecords exported by Telephony Manager that have the UserID field modified byanother program (to any value other than no value) are not updated during animport by Telephony Manager. During Import, Telephony Manager does notupdate these modified records but creates new records

Exporting copies data from the Telephony Manager databases to anexternal source. This is useful for archiving a range of data for laterretrieval. For example, if you want to archive a range of CDR data toan external source, then you can select a range of data and specify theexternal source.

When exporting data, you can select from a predefined exportconfiguration, or you can define your own custom configuration.

Export data using a predefined configurationTo export data using a predefined configuration, you must first selectthe configuration and its component values. This configuration outlinesthe parameters of the data being exported, such as the format of thedata, the types of records, and their field parameters (character length,position and so on). Telephony Manager includes a set of predefinedexport configurations for common database types. You can then selectthe location where the data is to be exported (for example, disk drive,CD-ROM, and so on).

The following is a summary of the steps required to export data using apredefined configuration:


NN43050-602 03.04 28 May 2009


.


Procedure 62Exporting data using a predefined configuration

Step Action

1 Access the Export utility—see “Access the Export utility ” (page129)

2 Select export configuration—see “Select export configuration”(page 129)

3 Export configuration definition and export the data—see “Exportconfiguration definition and export the data” (page 130)

--End--

Export data using a custom configurationTo export data using a custom configuration, you must first define theexport configuration. This configuration outlines the parameters of thedata being exported. This includes such information as the format of thedata, the types of records, and their field parameters (character length,position, and so on). You can then select the location where the data is tobe imported (for example, disk drive, CD-ROM, and so on).

The following is a summary of the steps required to export data using acustom configuration:

Procedure 63Exporting data using a custom configuration

Step Action

1 Access the Export utility—see “Access the Export utility ” (page129)

2 Export configurations list—see “Export configurations list” (page129)

3 Export configuration definition and export the data—see “Exportconfiguration definition and export the data” (page 130)

--End--


NN43050-602 03.04 28 May 2009


.


Access the Export utility To export data using a predefined or customconfiguration, access the Export utility. Based on which application you areusing, the Export utility may be accessed from two locations.

• In TBS, select File > Export in the TBS main window, there are twopredefined configurations Corporate Directory Export and ArchiveCDR/ Costed Data.

• From the System Window, select Utilities > Export. The Exportwindow appears allowing you to select from a list of predefinedconfigurations including Corporate Directory Export or add your owncustom configuration.

Select export configuration The Export (Select an ExportConfiguration) window is used to select a predefined export configuration.Use Procedure 64 “Selecting a predefined export configuration” (page129) to select a predefined export configuration.

Procedure 64Selecting a predefined export configuration

Step Action

1 Select export configuration from the Select an ExportConfiguration list.

2 To define the components of the exported file, click the ellipsis(...).

The Export window appears, where you select the tables ordatabases to be exported. If you are creating a new exportconfiguration, click the ellipsis (...) to access the Export – Systemname window.

3 After you select the predefined configuration and the destinationdirectories, click Go to export the data.

--End--

Export configurations list The Export – System name dialog boxcontains a list of predefined export configurations. Use Procedure 65“Creating a new configuration” (page 130) to create a new configuration.


NN43050-602 03.04 28 May 2009


.


Procedure 65Creating a new configuration

Step Action

1 Select (None) from Select an Export Configuration and clickthe ellipsis (...).

2 Click Add to access the Export window.

3 Enter the name of the new export configuration and inputdefinitions on this export configuration.

--End--

Export configuration definition and export the data The ExportConfiguration Definition window is used to select and define the type ofdata being exported from the Telephony Manager databases.

Procedure 66Defining the export configuration and exporting the data

Step Action

1 Select the export configuration name from the ExportConfiguration Definition list.

2 Enter the following information to define the export configuration

a Configuration Name—Name of this configuration. This is forinformational purposes and helps to identify this configurationfrom others in the Export Configurations List.

b Tables/Database—Type of tables the data is exported from.

c File/Database Type—Type of data being exported.

d File/Database Location—To select the destination of theexported database file (for example, the directory or drivethe file is exported to), click the ellipsis (...) next to theFile/Database Location field. From the Directory LocationForm window that appears, select the destination drive anddirectory. Click OK. Notice that the destination you selectedappears in the File/Database Location field.

e Export Profile Format—To select the format of the exportedfile, click Format. This accesses the Export Format windowin which you can select the field properties for the exportedfile. For more information, see “Field Data Type Formattingfor Export and Transmission” (page 231).

f File/Table Name—Filename of the database being exported.


NN43050-602 03.04 28 May 2009


.


g Update Activity—How this database is updated. Select fromthe options in Table 5 "Export update activity table" (page131).

Table 5Export update activity table

Option Meaning

Append All Appends all records

Delete All Rows Then Append Deletes rows then appendsrecords

Recreate Table Then Append Recreates table then appendsrecords

h Purge records after writing—Select this check box todelete the records from the source file after they have beensuccessfully written to the destination file.

CAUTIONThe Purge action is NOT reversible. Use cautionif selecting this option.

i Description—This field describes the contents of the tableselected from the Tables/Database Name menu tree.

3 Click OK.

4 Click Go to export the data.

--End--

Archiving Call Database using Export utilityThis example demonstrates how to archive the TBS Call Database to driveA. Use Procedure 67 “Archiving the Call Database” (page 131) to archivethe Call Database.

Procedure 67Archiving the Call Database

Step Action

1 Access the Export utility by selecting File > Export in the TBSmain window.

2 Select Archive CDR/Costed Data as the Export Configuration.

3 To define the parameters for this archive operation, click theellipsis (...) next to this list box.


NN43050-602 03.04 28 May 2009


.


The Export configuration window appears, listing CDR/CostedData as the source (from Telecom Billing System).

4 In the File/Database Location field, enter the destination of thisarchive operation. Click the ellipsis (...) to view a list of availabledrives.

5 If you want to archive a range of call records based on theirdates, then click the ellipsis (...) next to the Filter list.

6 In the Filters window that appears, create a new filter definitionand enter the range of call dates for this filter.

7 Select this new filter name from the Filter list.

8 Select Purge Records After Writing option to delete the rangeof call records from the original Call Database after the callrecords have been copied to the external source. This clears updisk space on your PC.

9 Click Go to proceed with the archive operation.

--End--

E-mail reporting featureTBS, GCAS, CCCR, and CRS utilize the Telephony Manager e-mailreporting feature. To enable this feature you must have the following:

• Internet access

• Access rights to a Simple Mail Transfer Protocol (SMTP) (outgoing)mail server.

Procedure 68 “Using the e-mail reporting feature” (page 132) describeshow to use the e-mail feature, beginning with the Reporting dialog.

Procedure 68Using the e-mail reporting feature

Step Action

1 In TBS, GCAS, or CCCR, select File > Reports.

2 Select a report.

3 Complete the Filter, Sort, and Configuration fields as required.

4 To create a report file type, select either Rich Text Format orSnapshot Format from the Output Type list.

Only these two file types are supported by the e-mail feature.When sending a file by e-mail, the Reporting system saves acopy of the RTF or Snapshot Format file using a name and


NN43050-602 03.04 28 May 2009


.

E-mail reporting feature 133

location that you specify and the e-mail feature attaches a copyof this file to the e-mail created.

5 Name the file and select a location.

1. click the ellipsis (...) in the File Name text box.

2. Provide a file name and file location for the RTF or SnapshotFormat report file.

3. Click Open to complete this step and close this dialog.

6 Select the Send File Using E-mail check box.

7 To configure your system and the current report for e-mailcapabilities, provide mail server access information.

1. Click the ellipsis (...) next to the text box below the Send FileUsing e-mail check box.

2. Click Mail Server Configuration.The Mail Server Configuration window opens, as shown inFigure 40 "Mail Server Configuration" (page 134).

ATTENTIONMail Server Configuration information is shared across all reportsand across all applications. Enter this information only once, andonly return if the information changes. You may need to contactthe administrator of your e-mail servers in order to provide theinformation required by the Mail Server Configuration window.


NN43050-602 03.04 28 May 2009


.


Figure 40Mail Server Configuration

3. In the SMTP outgoing Mail Server text box, enter the nameor address of your SMTP Server (for example, the server thatis used for your outgoing e-mail).This can be provided as an IP address (for example, 123.45.678.9) or domain name (for example, mymailhost.com)format.

4. In the Sender Display Name text box, enter the name youwant to display as the From name in the In-boxes of youre-mail recipients.

5. In the Sender E-mail Address text box, enter your e-mailaddress.

6. In the SMTP Port text box, enter the SMTP port on theSMTP Mail Server you are using.


NN43050-602 03.04 28 May 2009


.

E-mail reporting feature 135

The SMTP standard port is 25. Change this parameter onlyif your SMTP Mail Server’s SMTP port was changed to anon-standard value.

7. Check SMTP Server Requires Authentication check boxif your SMTP mail server is configured to require logonauthentication.If your mail server does support authentication, provide yourAccount Name and Password in the text boxes provided.

ATTENTIONVery few SMTP mail servers are configured to require logonauthentication. If you select this option, and your SMTP Serverdoes not support authentication, the logon/authentication processmay time out and the mail may fail to send. (This failure is loggedin the Event Log.)

8. Click OK.The E-mail Recipients window appears, as shown in Figure41 "E-mail recipients" (page 135).Figure 41E-mail recipients

8 Add a new e-mail recipient.

1. Select the <New> <Add New Recipient> row under theName and E-mail Address list box.

2. Do one of the following to complete the Name andE-mail Address (for example, mailbox@computer, e.g.,[email protected]) text boxes:

— Type the Name and E-mail Address of the recipient.

— Click the ellipsis (...) next to the Name field to view a listof names in the databases, and select the recipient (anemployee, external party, role, or project) from the list


NN43050-602 03.04 28 May 2009


.


in the Entity Selector dialog box. If an e-mail addresshas been assigned to the Entity you selected in thedatabases, this e-mail address is auto-inserted into theE-mail Address text box.

3. Click OK.

9 Attach the report file to an e-mail message.

1. Enter a Subject: for the subject line of the e-mail.

2. Enter a Short Message for the body of the e-mail.

10 Click OK.


• Click Go to send the e-mail and the accompanying report.

• Click Schedule to schedule the e-mail to be sent at a latertime.

12 (Optional) View the Event Log to determine if the report wasproduced, and if the e-mailing was successful.

--End--

Collecting Dialed Number Information Service dataDNIS is frequently a feature of 1-800 and 1-900 lines. It provides to thecaller the number dialed to make the call. With DNIS, a single trunk groupcan be used to serve multiple applications. DNIS information can be usedby the PBX to route the call or to provide the caller with a specific prompt.

For reporting purposes, DNIS data should be collected only under thefollowing circumstances:

• The PBX is configured to produce CDR.

• DNIS data is provided by the carrier.

• There are multiple 1-800 and 1-900 calling numbers into theorganization that are to be tracked.

• The 1-800 and 1-900 numbers arrive in a single trunk group.

If calls to the organization are routed to a group of agents assignedto a particular organization node, TBS can be used to display the callinformation for those agents without using DNIS information. If the callsare generated on different trunk groups, TBS can report on calls to eachtrunk group separately without using DNIS information.


NN43050-602 03.04 28 May 2009


.

Collecting Dialed Number Information Service data 137

Procedure 69Configuring TBS and the MDR 2000 or MDR 2000e to collect DNIS data

Step Action

1 Configure the MDR 2000 or MDR 2000e buffer box to collect inImage mode.

This increases the amount of data that is stored in the buffer.Depending on the buffer utilization, more frequent datacollections may be required. See the MDR 2000 or MDR 2000edocumentation for more information on configuring the bufferbox.

2 In the TBS Collection Configuration window, select theappropriate image collection script for your CDR format.

For example, select M2KIMG-SL1NEW.col or M2KIMG-SL1OLD.col.

3 Start the data collection.

DNIS information is stored in TBS as part of the call record.

--End--


NN43050-602 03.04 28 May 2009


.



NN43050-602 03.04 28 May 2009


.

139.

Consolidated Call Cost Reports



• “CCCR interface” (page 140)

• “Configuring CCCR” (page 146)

• “Generating reports” (page 153)

IntroductionThis chapter provides basic information about configuring and runningConsolidated Call Cost Reports (CCCR). Along with a brief outline of itsmain features and functions, this chapter contains step-by-step instructionsthat assist you in configuring CCCR.

CCCR is the Telephony Manager system integration and reportingapplication. CCCR combines data from the corporate directories in eachof your Telephony Manager systems and generates billing reports basedon this consolidated data. Specifically used for the Telephony ManagerTBS, the CCCR application reports on your calling activity across multiplesystems on a single Telephony Manager server.

Used in conjunction with the TBS, CCCR synchronizes your organization’sinformation and calling activity from the individual Telephony Managersystems. You still use the TBS to collect and cost the CDR data for eachsystem. After this data is processed, you then use CCCR to consolidatethe corporate data from each enabled system into its read-only databasefor reporting. The resulting corporate database is for the use of CCCRonly, and cannot be viewed or edited by other applications.

The following is an overview of some CCCR features:

• The consolidated reports provide details about the actual telephoneusage of the different sites and systems across your entireorganization. Management can then isolate individual users or


NN43050-602 03.04 28 May 2009


.

140 Consolidated Call Cost Reports

departments who are not utilizing the telephone system properlythrough misuse or neglect.

• The intuitive corporate editor is used to merge the differentorganizational hierarchies from your Telephony Manager systems intoa single consolidated server.

• The Telephony Manager Scheduler application can be used toconfigure the database synchronization and report generation functionsto run at scheduled intervals. This way, after you have configured thedatabases in CCCR, you can use the Scheduler to generate yourconsolidated reports automatically.

• The alternate currency option lets you include two different currencieson your consolidated reports.

CCCR interfaceThis section contains a brief overview of the CCCR interface. For completedetails about each of its functions, refer to the online Help.

Main windowThe CCCR main window is the main interface from which you define theconsolidated server and systems, configure the corporate properties, andgenerate your reports. See Figure 42 "CCCR main window" (page 141).


NN43050-602 03.04 28 May 2009


.

CCCR interface 141

Figure 42CCCR main window

File menuThe following File menu commands are used to synchronize the corporatedatabase, generate reports, and exit from CCCR:

• Synchronize Corporate Data

• Reports

• Exit

Synchronize Corporate DataThe Synchronize Corporate Data commands are used to synchronizethe data from the different systems that you have added to the CCCRdatabase. These systems appear in the Consolidated Server list:

The Synchronize Corporate Data commands are:

• Start

• Schedule


NN43050-602 03.04 28 May 2009


.


ReportsCCCR includes a number of reports that provide you with details aboutyour organization’s calling activities. These reports are based on thecall records that you collected from the different Telephony Managersystems in your organization, and then saved to the CCCR database.This reporting function is used to generate the reports to selected outputdevices (for example, printers) based on definable filters.

Reporting options The following options are used to select the outputdevice for the report as well as its filters. These options appear in theProfile section (right side) of the Reporting dialog box:

• Output Type—Contains a list of output formats for the selected report.You can select from the following options: Screen, Printer, Rich TextFormat, HTML Format, and Snapshot Format.

• File Name—Enter the name of the file to which the report is exported.

• Send File Using E-mail—Allows you to e-mail a copy of the report toselected e-mail addresses.

• Filter—The Filter definitions are used to select the reporting criteria foryour reports.

Reporting commands The following is a list of the Report Generatorcommands:

• Go

• Schedule

• Cancel

• Help

List of reports The following is a list of the reports that are available forCCCR:

• Entity Detail Report

• Entity Summary Report

• Entity Rollup Summary Reports

• Account Code Summary Report

• Account Code Rollup Summary Reports

ExitThe Exit command ends the current CCCR session.


NN43050-602 03.04 28 May 2009


.

CCCR interface 143

Edit menuThe Edit menu accesses the Refresh Site List command.

The Refresh Site List command refreshes the list of sites and systemsfor a selected server in the Consolidated Server list. This ensures thatthe server is up to date with the most current site and system informationbefore data synchronization. For example, if you add sites and systemsto the server and you update its costing configuration, then you use theRefresh Site List command to update the server with this most recentinformation. When you invoke this command, CCCR re-queries theselected server to reconstruct the list of sites and systems.

Consolidated Server listThe Consolidated Server list (left section of the CCCR main window)displays (in a navigation tree format) the server that has been defined forCCCR. The server nodes display all of the Telephony Manager sites andsystems that have been assigned to it. The root node for this list (labeledConsolidated) lists the defined server along with its sites and systems. Thedefault server (labeled Local Host) contains the sites and systems thatyou have defined for Telephony Manager. To view the sites and systemswithin the server, double-click the server name from the navigation tree.After you open the navigation trees for these sites and systems, click thenavigation tree command buttons to expand the menus.

Each system in this list is identified by an icon. These icons allow you toview, at a glance, which systems are enabled in the CCCR configurationdatabase. Systems that are enabled for consolidation are identified by ayellow icon. Systems that are disabled are identified by a gray icon. Bydefault, systems are disabled. Use the System Properties fields to enablethese systems.

Use this list to view and edit the consolidated server and systems inCCCR. To edit the properties of a server or system, click the name ofthe server or system in this navigation tree. The corresponding server orsystem properties fields appear in the right section.

Server PropertiesThe Server Properties fields contain general information about the sitesand systems that are being consolidated into the server of the CCCRdatabase.

To edit the properties of the server, select the server name from theConsolidated Server list (left section of this window). In the ServerProperties fields that appear, enter the following information:

• Server Name—Contains the name of the server as it appears in thenavigation tree of the Consolidated Server list. By default, it is the


NN43050-602 03.04 28 May 2009


.


same name as the Server URL. Enter a new name by typing over theexisting name.

• Server URL—Displays the original name of this server.

• Description—Enter a description of this server for informationalpurposes only.

System PropertiesThe System Properties fields contain general information about eachsystem that has been assigned to the server.

To edit the properties of a system, select the system from theConsolidated Server list (left section of this window). In the SystemProperties fields that appear, enter the following information:

• Enabled—Activates this system as part of CCCR. This adds the TBS’sdata to the CCCR database. If this check box is selected (that is, thissystem is enabled), the icon next to the system in the ConsolidatedServer list turns yellow; otherwise, the icon is gray. With these icons,you can view, at a glance, which systems are enabled for the CCCRconfiguration database. If this check box is not selected (that is, thissystem is disabled), the TBS data from this system is not included inany reports. By default, each system is disabled.

• Name—Identifies this system. You previously named the system whenyou created it in the Telephony Manager Navigator.

• Costing Configuration—Contains a list of all of the telephoneconfigurations that are part of the systems included in the server.From this list, select the telephone configuration to be used to costthis system on your reports. This list box is auto-populated from theoriginating system. If this system contains only one configuration, thenthat configuration appears in this list by default; otherwise, it defaultsto (None). You must select a configuration from this list before thissystem can be enabled.

• Currency—Lists the currencies that have previously been defined inthe Currency Exchange Rates grid of the Currency Properties tab.From this list, select which currency you want to use for this system’sreports. By default, it displays Local Currency.

Corporate Properties tabThe Corporate Properties tab contains the basic information requiredto create a consolidated version of the Telephony Manager corporatedirectory. These properties determine how the different systems aremerged into the new consolidated root node of CCCR.


NN43050-602 03.04 28 May 2009


.

CCCR interface 145

The Corporate Properties fields are:

• Corporate Root Node Name—Contains the name of the consolidatedroot node. In this box, enter the name of your organization. Thisbecomes the root node of the newly consolidated corporate hierarchy.

• Merge Root Nodes—Determines how the organizational hierarchies inthe different systems are combined within the new root node. Enablethe Merge Root Nodes option to merge common nodes within yourhierarchy under a single node. For example, if you have two systems,each with a Sales and Support department, that you want to mergeunder a main node containing these departments, then enable thisoption.

• Levels Table—Contains the names of the different levels in theconsolidated corporate directory (for example, Corporate, Division, andDepartment). This prevents conflicts between databases if differentsystems have their levels defined differently. The default values inthis table are the same as those in the Telephony Manager corporatedirectories.

• Entity Identification—Determines how the corporate entities areidentified in the consolidated database. When the original corporatedirectories are consolidated into the new CCCR database, an entity’srecord is consolidated only if the chosen field is the same on bothrecords. Select the following values from this list: Identification, E-mail,or Logon Name.

• View Organization—Accesses the Consolidated Organizational Viewdialog box, which displays a navigation tree of the organizational levelsin the newly consolidated corporate directory. This displays ORG asthe root node until you first consolidate the systems.

Currency Properties tabCCCR allows you to define currency settings that are independent fromthe settings in the individual Telephony Manager systems. This way, youcan define the main (local) and alternate currencies used by the reports inCCCR. These currency settings do not necessarily need to match the localand alternate currencies from each of your Telephony Manager systems.Use the Currency Properties tab to configure the different currency valuesand exchange rates for CCCR.

The Currency Properties fields are:

• Currency Name—Displays the name of the currently selectedmain currency. This is the main currency that is used on all reportsgenerated by CCCR. To change this currency, click Configure. This


NN43050-602 03.04 28 May 2009


.


accesses the Telephony Manager Navigator’s Currency Configurationdialog box in which you can enter your local and alternate currencies.

• Alternate Currency—Displays the name of the currently selectedalternate currency. This is the alternate currency that is used on allreports generated by CCCR. If no alternate currency is selected, or thealternate currency has been disabled, then this field is blank.

• Configure—Defines the local and alternate currencies used forCCCR. This accesses the Telephony Manager Navigator’s CurrencyConfiguration dialog box in which you can enter your local andalternate currencies.

• Currency Exchange Rates—Contains the different currencies andexchange rates used across your consolidated systems. In this table,enter the names of the different currencies used in your systems, aswell as the current multiplier used to convert each currency from thelocal currency to that selected currency. By default, this table containsonly one Local Currency entry with an exchange rate of 1.

Configuring CCCRThis section describes how to access CCCR and configure it for initial use.Use the following instructions to configure this application to synchronizethe corporate databases from the Telephony Manager systems andgenerate your consolidated reports.

The CCCR application is accessible only from the Telephony ManagerServer and not from Telephony Manager Clients.

Before using CCCR, install and configure it as part of the TelephonyManager system. Refer to Telephony Manager 4.0 Installation andCommissioning (NN43050-300) for complete details on installing thisapplication as part of Telephony Manager.

Before you beginBefore you begin to configure CCCR, make sure you complete thefollowing steps. These steps assume that you have already input yourcompany information into the Telephony Manager databases.

• Configure your sites and systems.

• Assign the TBS application to each applicable system.

• Populate the Telephony Manager employee databases with therequired organizational hierarchy and entity information. Rememberto completely configure TBS for all of your sites and systems beforeproceeding with CCCR.


NN43050-602 03.04 28 May 2009


.

Configuring CCCR 147

Summary of steps to configure CCCRThe following is a summary of the steps to configure CCCR:

Procedure 70Configuring CCCR

Step Action

1 Run CCCR from the Telephony Manager Navigator.

2 Assign systems to the consolidated server.

3 Download and synchronize the corporate data to the CCCRdatabase.

4 Review and edit the levels in the consolidated organizationalhierarchy.

5 Select the local and alternate currencies to be used on thereports.

--End--

Run CCCRBefore you can configure CCCR, you must first run it from the TelephonyManager Navigator. Because CCCR is not assigned to a specific site orsystem, you can access it from the Telephony Manager Navigator.

Procedure 71Running CCCR

Step Action

1 Run Telephony Manager by selecting Telephony ManagerNavigator in the StartUp program group.

The Telephony Manager Navigator window appears, as shownin Figure 8 "TBS main window" (page 36).

2 Select Utilities > Consolidated Call Cost Recording.

The main CCCR window appears, as shown in Figure 42 "CCCRmain window" (page 141).

--End--


NN43050-602 03.04 28 May 2009


.


Assign systems to consolidated serverTo allow for the consolidation of data from the different systems in yourorganization, CCCR stores the directory structure of all of the TelephonyManager sites and systems in a consolidated database. This directorystructure represents the defined Telephony Manager sites and systemsthat have the TBS application assigned to them.

When you access the Consolidated Server list, CCCR displays the defaultconsolidated server along with all of the defined Telephony Manager sitesand systems. This site and system list is auto-populated when you expandthe server node (or when you select Edit > Refresh Site List). By default,the systems that appear in this list are not enabled for consolidation. Thatis, even though they appear in this list, they are not actually part of theconsolidated database. You must select each system and assign it to theconsolidated server database.

Procedure 72Assigning your systems to the consolidated server database

Step Action

1 Access the Consolidated Server list and expand the server nodelabeled Local Host, as shown in Figure 43 "Consolidated Serverlist" (page 149).

This displays all of the sites and systems that you have definedin Telephony Manager. Only the systems that contain the TBSapplication appear in this list. By default, each system is disabledfor consolidation.


NN43050-602 03.04 28 May 2009


.


Figure 43Consolidated Server list

2 Select the name of the system that you want to enable forconsolidation.

The System Properties fields for this system appear.

3 Select Enabled.

4 Select a costing configuration from the Costing Configurationlist.

If you have defined a single costing configuration for this system,then this list defaults to that defined configuration. If you havedefined multiple configurations, then this list defaults to <None>.You must, therefore, select from the list of defined configurations(for example, Sample Configuration).

5 Select a sample currency from the Currency list.

6 Click Apply to assign this system to the Consolidated serverdatabase.

This enabled system is identified by a yellow icon.

7 Repeat this procedure for each system that you want to enablefor the consolidated server database.


NN43050-602 03.04 28 May 2009


.


After you have assigned all the systems, the ConsolidatedServer list displays all of the systems that are assigned to theconsolidated server database.

--End--

Synchronize corporate dataThe next step is to synchronize the corporate data from your TelephonyManager systems with the CCCR database. This function downloadsthe corporate database records from the assigned Telephony Managersystems (that is, the Organizational Hierarchy, Employee, External Parties,and Roles/Projects Databases). It then synchronizes this data with theCCCR database to ensure that the consolidated corporate information isup to date with the most current information from your Telephony Managersystems.

To run the database synchronization, select File > SynchronizeCorporate Data > Start. After you start a synchronization process, astatus dialog box appears displaying its progress.

Review and edit levels in the consolidated organizational hierarchyThe following steps outline how to edit the levels in the consolidatedorganizational hierarchy. After you have synchronize the corporatedata from the Telephony Manager systems with the CCCR database,review the defined levels to ensure that they reflect your organizationalhierarchy. If you need to edit these levels, you can do so by accessing theCorporate Properties tab of the CCCR window. This tab contains the basicinformation required to create a consolidated version of the TelephonyManager corporate directory. These properties determine how the differentsystems are merged into the new consolidated root node of CCCR.

Procedure 73Editing the levels in the consolidated organizational hierarchy

Step Action

1 Select the Corporate tab in the CCCR window.

2 In the Corporate Root Node Name box, enter a name for theconsolidated hierarchy.

For example, enter Acme Incorporated.

3 Select the Merge Root Nodes option to merge common nodeswithin your hierarchy under a single node.

4 Leave the Levels table with the default values.


NN43050-602 03.04 28 May 2009


.


This table contains the names of the different levels in theconsolidated corporate directory (for example, Corporate,Division, and Department).

5 From the Entity Identification list, select the value thatdetermines how the corporate entities are identified in theconsolidated database.

For example, select Identification.

6 Click Apply to save these settings.

--End--

To review the consolidated organizational hierarchy, click ViewOrganization. This accesses the Consolidated Organizational Viewdialog box, which displays all of the different levels in the consolidateddatabase. Review these levels to ensure that they accurately represent theconsolidated organizational hierarchy for your company (that is, all of theorganizational levels are structured correctly). If you need to change thisstructure, then repeat Procedure 73 “Editing the levels in the consolidatedorganizational hierarchy” (page 150) and change your settings as required.

Select local and alternate currenciesYou can select the local and alternate currencies that are used on yourreports. This is an optional step, and is required only if you want to usetwo different currencies for the costs on your reports.

Procedure 74Selecting local and alternate currencies for reports

Step Action

1 Select the Currency tab in the CCCR window.

2 Click Configure to define the local and alternate currencies usedfor CCCR.

This accesses the Telephony Manager Navigator’s CurrencyConfiguration dialog box in which you can enter your local andalternate currencies. You can also access this dialog box directlyfrom the Telephony Manager Navigator.

3 Select the Local Currency tab, and enter the requiredinformation.


• Currency Name: US Dollars

• Currency Symbol: $

• Position of Currency Symbol: *1.1

• Negative Number Format: (*1.1)


NN43050-602 03.04 28 May 2009


.


• Decimal Symbol: .

• No. of Digits after Decimal: 2

• Digit Grouping Symbol: ,

• Number of Digits in Group: 3

4 Select the Alternate Currency tab, and enter the requiredinformation.


• Currency Name: Canadian Dollars

• Currency Symbol: $

• Position of Currency Symbol: *1.1

• Negative Number Format: (*1.1)

• Decimal Symbol: .

• No. of Digits after Decimal: 2

• Digit Grouping Symbol: ,

• Number of Digits in Group: 3

• Currency Exchange Rate: 1.54

5 Click Apply to save the settings.

6 Click OK to return to the CCCR window.

The Currency Name and Alternate Currency fields are updatedwith these new values. The Currency Exchange Rates tabledisplays only the Local Currency with the exchange rate of 1.00.

7 To add the exchange rate for the alternate currency:

a Right-click on the grid.

b Select Add from the pop-up menu.

c In the blank line (cell) that appears, enter the requiredinformation.


• Currency: Canadian Dollars

• Exchange Multiplier: 1.54

8 Click Apply.

After you have defined a currency, you must assign it to thedifferent systems that are collecting data in that currency. To doso, access the System Properties for the different systems and


NN43050-602 03.04 28 May 2009


.

Generating reports 153

assign the new currency to each system. See “Assign systemsto consolidated server” (page 148).

--End--

Generating reportsAfter you have configured CCCR to reflect your organizational data, youare ready to generate your consolidated reports.

ATTENTIONNot all filters apply to all reports.

Procedure 75Generating consolidated reports

Step Action

1 Select File > Reports from the CCCR main window.

The CCCR Reporting window appears, as shown in Figure 44"CCCR Reporting window" (page 153).Figure 44CCCR Reporting window

2 Select the desired report by clicking the corresponding reportname.

For example, select Entity Detail Report.


NN43050-602 03.04 28 May 2009


.


3 Select the type of output from the Output Type list.

For example, to print the report, select Printer.

4 (Optional) Select the filters from the Filter list.


5 Click Go to generate the consolidated report.

CCCR automatically downloads the Call Database informationfrom all of the enabled systems and generate the report.

--End--

Creating custom logos on reportsThe reports in CCCR each contain a common header graphic, which islocated at the top left corner of the report. This graphic helps you to easilyidentify the reports as part of CCCR.

CCCR allows you to edit this graphic, or replace it with another graphic,by editing a bitmap (BMP) file. You can replace this graphic with anotherdesign, such as your company logo, to suit your own needs. For example,you can include your company logo on your reports to provide you withprofessional-looking reports that are customized for your organization.

CAUTIONBe careful when editing this graphic file. If the file is too large, itcan cause errors in the generated reports. To ensure that theoriginal graphic file is secure, make a backup copy of it. To doso, copy the file Logo.bmp from the CCCR directory to anotherdirectory, or rename it (for example, Backup_Logo.bmp).

Procedure 76Creating a custom graphic or logo for your reports.

Step Action

1 Use a graphics program such as MS Paint to create a bitmapwith the following dimensions: 3.73 in (W) by 0.86 in (H).

Insert or create the new graphic (for example, your companylogo) in the bitmap file. To ensure you have the correctdimensions for your logo, you can make a copy of the originalgraphic file Logo.bmp and use it as a template for your owngraphic. Open the file Logo.bmp and insert the new graphic inthe file.

2 Save this file as Logo.bmp to the dedicated CCCR drive anddirectory.


NN43050-602 03.04 28 May 2009


.

Generating reports 155

For example, C:\Nortel\Millennium\RootData\CCCR\Logo.bmp.CCCR automatically uses this logo on your reports.

--End--


NN43050-602 03.04 28 May 2009


.



NN43050-602 03.04 28 May 2009


.

157.

TBS Web Reporting



• “TBS Web Reporting interface” (page 158)

• “Configuring TBS Web Reporting” (page 160)

• “Using TBS Web Reporting” (page 166)

IntroductionThis chapter provides basic information about configuring and runningTBS Web Reporting. Along with a brief outline of its main functions, thischapter also contains procedures and reference information to assist youin configuring TBS Web Reporting.

TBS Web Reporting is the Telephony Manager Web-based reportingapplication for your telecommunications network. With TBS WebReporting, you can generate reports containing data from the TBS throughyour intranet or Internet server. These reports provide you with valuableinformation about your organization’s calling activities.

TBS Web reports are only some of the TBS reports available in TelephonyManager. “TBS reports” (page 199) lists all of the TBS reports available inTelephony Manager, from both TBS Web and TBS Windows.

The TBS application is the Telephony Manager telephone cost accountingand billing application. It collects call records from your telephone system,calculates usage costs based on defined rates and configurations, andallocates these costs to the appropriate users in your organization. TBSWeb Reporting generates reports summarizing and detailing these costs. Itprovides you with an easy method of accessing the TBS information.


NN43050-602 03.04 28 May 2009


.

158 TBS Web Reporting

The following is an overview of some of the features of TBS WebReporting:

• TBS Web Reporting produces a variety of costing reports detailing yourorganization’s calling activities.

• Based on your access rights, you can view call detail information forany level in your organizational hierarchy (for example, departmentsand users), both from a summary level and a detail level.

• Its reports provide details on the actual telephone usage of yoursystem. Management can then isolate individual users or departmentswho are not utilizing the telephone system properly through misuseor neglect.

• The interface enables you to access this information through anyPC—run a Web browser, access the Telephony Manager Web server,and run TBS Web Reporting.

TBS Web Reporting interfaceThis section contains a brief overview of the TBS Web Reporting mainWeb interface. For complete details on each of its functions, refer to theonline Help.

TBS Web Reports main windowThe TBS reports provide you with thorough and detailed informationabout your telephone system. These reports detail and summarize yourtelephone system usage, assign costs to the appropriate cost centers, anddisplay information on your system’s organizational databases.

After you log on to Telephony Manager Web, you can view the TBS WebReports.

List of reportsThe following sections briefly describe the reports available for TBS WebReporting. Based on your access rights, some or all of these reportsappear in this list.

Cost reportsThe following reports provide summaries and details of your organization’stelephone usage costs. These are based on your extensions, authorizationcodes, or account codes:

• Extension Summary Report

• Authorization Code Summary Report

• Account Code Summary Report


NN43050-602 03.04 28 May 2009


.

TBS Web Reporting interface 159

Level reportsThe following reports provide roll-up summaries of telephone usage costsfor your organization based on extensions, authorization codes, or accountcodes. They access summary and detail reports displaying this data basedon the organizational level. For example, the Extension Roll-up Reportconsists of the Extension Roll-up Report for the current organizationallevel, the Extension Summary Report for its sublevel, and so on, until youhave reached the detail report for each user:

• Extension Roll-up Report

• Authorization Code Roll-up Report

• Account Code Roll-up Report

Frequency/Digits reportsThe following reports provide roll-up summaries of your calling activitybased on frequency of calls to specific numbers and locations:

• Frequently Called Numbers Report

• Frequently Called Location Report

• Area Code Summary Report

• Ring Time by Time of Day Report

• Ring Time by Extension Report

• Hold Time by Time of Day Report

• Hold Time by Extension Report

Trunk reportsThe following reports provide call usage details for each trunk or trunkgroup in your organization:

• Trunk Group Utilization Report

• Trunk Utilization Report

Diagnostic reportsThe following reports list all of the extensions and trunks that are enteredin the telephone configuration that have no call activity, as well as all of theextensions and trunks that have call activity but have not been entered inthe telephone configuration:

• Extension Diagnostic Report

• Trunk Diagnostic Report


NN43050-602 03.04 28 May 2009


.


Filters and configurationsThe Filters page is used to select the reporting criteria for your reports.This allows you to generate reports based on very specific requirements.Whenever you select a report from the TBS page, the Filters page appearsallowing you to select its filters.

Figure 45 "Filters page for Extension Summary Report" (page 160) showsthe Extension Summary Report. Based on the report you select, the Filterspage displays different filters.

Figure 45Filters page for Extension Summary Report

Configuring TBS Web ReportingThis section describes how to access and use TBS Web Reporting.

Before using TBS Web Reporting, you must install and configure it aspart of the Telephony Manager. You must then assign it to a site andsystem. Refer to Telephony Manager 4.0 Installation and Commissioning(NN43050-300) for complete details about installing this application andassigning it to a site and system.

Additional system requirementsThe server and client PCs that run TBS Web Reporting each have theirown hardware and software requirements. The server PC is used to storethe files for TBS Web Reporting. The client PC is used only to accessthis application’s reports through a browser, such as Microsoft InternetExplorer or Netscape Navigator. Because this client PC can be differentfrom the server PC, these system requirements may differ from thoseof Telephony Manager common services. Refer to Telephony Manager


NN43050-602 03.04 28 May 2009


.

Configuring TBS Web Reporting 161

4.0 Installation and Commissioning (NN43050-300) for a complete list ofhardware and software requirements for all of the Telephony Managerapplications.

Server configuration and installationBefore installing TBS Web Reporting, configure and install your server,as outlined in Procedure 77 “Configuring and installing your server” (page161).

Procedure 77Configuring and installing your server

Step Action

1 Configure your server and install the Internet Information Server(IIS) to allow other users to have remote Web access to theserver.

2 Install the Telephony Manager common services and TBS ontothe server on which you are installing TBS Web Reporting.

3 Install Telephony Manager Web services onto the Web serverbefore attempting to run it. Refer to the Web services chapter inTelephony Manager 4.0 System Administration (NN43050-601)for instructions on installing and configuring Telephony ManagerWeb Services.

--End--

Installing TBS Web ReportingThe TBS Web Reporting installation kit includes all of the componentsyou need to install, configure, and run the program as part of TelephonyManager Web. The Setup utility installs each of the required componentsfor TBS Web Reporting and prompts you for specific information pertainingto your system (for example, install drive, directory, program folder, andso on). During the installation procedure, enter your system informationas directed.

Ensure that you have configured the access rights for the TelephonyManager Web users, and selected TBS Web Reporting as a reportingapplication, as follows:

• To configure the access rights for TBS Web Reporting, refer toTelephony Manager 4.0 System Administration (NN43050-601).

• To install and configure TBS Web Reporting as part of TelephonyManager Web, refer to Telephony Manager 4.0 Installation andCommissioning (NN43050-300).


NN43050-602 03.04 28 May 2009


.


Configuring TBS Web ReportingProcedure 78Configuring TBS Web Reporting

Step Action

1 Perform CND synchronization after a station retrieval is done.

ATTENTIONOnly stations with CPND entry are automatically added to theDirectory during CND synchronization.

The default values for User Group is End User and WebReporting Access Rights is Personal as shown in Figure 46"Update employee details page" (page 162). These fields maybe changed as required.

Figure 46Update employee details page

2 Perform Billing Synchronization.

3 Open TBS and go to Edit > Employees.

Information from the Directory is populated in the EmployeeEditor after Billing Synchronization as shown in the Figure 47"Employee shown in Employee Editor" (page 163) figure.


NN43050-602 03.04 28 May 2009


.


Figure 47Employee shown in Employee Editor

4 Go to Telephony Manager Windows Navigator. Under Security-- User Authentication, ensure that Common Network Directoryhas an order selected.

In Figure 48 "Order selection on User Authentication screen"(page 164) the selected order number is 2.


NN43050-602 03.04 28 May 2009


.


Figure 48Order selection on User Authentication screen

5 Open the Telephony Manager end user Web page.

The logon name is displayed, as shown in Figure 49 "TelephonyManager end user Web page" (page 165), and the defaultpassword is prefix (found under the CND server setup) followedby the common name.


NN43050-602 03.04 28 May 2009


.


Figure 49Telephony Manager end user Web page

6 Click Login and the billing report for the selected user isdisplayed, as shown in Figure 50 "Billing report screen" (page165).Figure 50Billing report screen

--End--


NN43050-602 03.04 28 May 2009


.


Using TBS Web ReportingProcedure 79Logging in to Telephony Manager Web and running TBS Web Reporting

Step Action

1 Log on to Telephony Manager Web Desktop Services.

The My Profile page appears, containing your user informationand links to the Web Reporting applications to which you haveaccess.

2 From the Web Desktop Services navigation tree, select BillingReports.

The Billing Reports page appears, containing links to your TBSreports.

3 Access the TBS Reports page by clicking on a system link.

You can also access your reports through any defined personalassets. The TBS Reports page for the selected system or assetopens.

4 To view a report from the TBS, select the report name in theTBS Reports page.

5 Select a telephone configuration table and any filters for thereport.

6 Click Run Report to view the selected report.

--End--


NN43050-602 03.04 28 May 2009


.

167.

General Cost Allocation System



• “GCAS interface” (page 168)

• “Configuring GCAS” (page 170)

• “Using GCAS” (page 179)

IntroductionThis chapter provides basic information about configuring and runningthe General Cost Allocation System (GCAS). It also includes exampleprocedures and reference information to assist you in configuring theGCAS.

The GCAS is used to assign usage charges to appropriate individuals ordepartments within an organization. It can import bill information, identifyand log departmental or user-specific spending characteristics, andgenerate meaningful reports summarizing these costs.

With the GCAS, you can enter billing information either through animported file or manually from the printed vendor statement. The datacan then be used to allocate charges, such as those obtained fromcellular calls or pagers, to relevant individuals or departments within yourorganization. The GCAS generates detail and summary reports, includingthe billed products or services, associated costs and departments, orpersons to be billed.


NN43050-602 03.04 28 May 2009


.

168 General Cost Allocation System

The following are some of the features of GCAS:

• It allows for effective distribution, tracking, and monitoring of allchargeable costs to departments or persons within an organization.

• Its reports detail products or services purchased, and the appropriatechargeable entity. Management can then monitor and isolate specificcosts to various business lines within an organization.

• Billing charges can be imported directly from a vendor’s electronic bill,thus reducing data entry time.

• The user-friendly hierarchical organizational interface allows for controlof the chargeable groups within your organization.

• Intuitive database editors allow you to populate, update, and view yourdatabase records.

GCAS interfaceThis section contains an overview of the GCAS functions and databases.It briefly describes their function and purpose. For complete details abouteach of these functions and their operation, refer to the online Helpincluded with the software.

File menuThe File menu contains commands used to manage the bill type records,generate reports, import and export data, and exit from the system.

The following is a list of the functions and commands in this menu:

• New Bill Type

• Delete Bill Type

• Reports

• General Export

• Import Bill Type

• Export Bill Type

• Archive Bill Type

• Merge Bill Type

• Purge Bill Type

• Exit


NN43050-602 03.04 28 May 2009


.

GCAS interface 169

Edit menuThe Edit menu accesses the GCAS main databases. These databasescontain the corporate information you need to run the GCAS effectivelyfor your organization.

To access these databases, click Edit in the main window, and then selectthe following:

• Organizational Hierarchy—This database contains the differentstructural levels within your organization (for example, departments,divisions, and so on). You can create up to 20 different levels in thishierarchy. The Organizational Hierarchy and the Level editor are usedto create, name, and arrange these different organizational levels.The employees in your organization are assigned to these levels. Thecost summary reports can then summarize the calling activity andassociated usage costs by these levels.

• Employees—This database contains information about yourorganization’s employees, which is relevant to the GCAS. It includessuch information as your employees’ names, telephone extensions,authorization codes, and their locations within the organizationalhierarchy. This information is required to allocate charges to the properextensions and cost centers within your organization.

• External Parties—This database contains information about individualsor companies with whom you have regular contact. It includes suchinformation as the external party’s name, address, telephone number,and account code.

• Roles/Projects—This database contains information about the differentroles or projects that require reporting in the GCAS. It is used toassign extensions, authorization codes, or account codes to projects orpersonnel for reporting purposes.

• Asset Assignments—This database defines how the different assetsare assigned to the corporate entities in the Employee, ExternalParties, and Roles/Projects Databases.

• Taxes—This editor is used to define the taxes that are applied to theusage or equipment charges of the billing records.

View menuThe View menu contains commands and toggles to display variouscomponents of the GCAS database.

This menu contains the following commands and toggles:

• Bill Party

• Grid Lines


NN43050-602 03.04 28 May 2009


.


• Status Bar

• Refresh

• Find

• Replace

Help menuThe Help menu offers commands that provide you with assistance as youuse the GCAS.

This menu contains the following commands:

• Help Topics

• About the GCAS

Configuring GCASBefore using the GCAS, you must install and configure it as part ofTelephony Manager. You must then assign it to a site and system. Referto Telephony Manager 4.0 Installation and Commissioning (NN43050-300)for complete details about installing this application and assigning it to asite and system.

Accessing the GCAS from Telephony ManagerTo access GCAS from the Telephony Manager Navigator, select thedesired site and system, and click GCAS under Telemanagement. TheGCAS main window appears, as shown in Figure 51 "GCAS main window"(page 171).


NN43050-602 03.04 28 May 2009


.

Configuring GCAS 171

Figure 51GCAS main window

Create organizational hierarchyThe Organizational Hierarchy Database is a structured databasecontaining important information about your organization, includingthe different organizational levels and how these levels are related(for example, departments within divisions). After you configure yourorganizational levels in this database, enter your bill type information andgenerate reports.

Before any meaningful allocation of billing charges can take place, youshould define the logical hierarchical structure of your organization.In short, you are creating a framework that holds and links the billinginformation in the GCAS to the correct billed entity (that is, the employeeor department).

Procedure 80 “Defining the organizational hierarchy” (page 172) describeshow to configure an organizational hierarchy. The sample entries in thisprocedure create a hierarchy with the levels Acme Company (organizationor top level), Head Office (Division level), and Sales (Departmentlevel). The Division level is a sublevel of the Organization level, and theDepartment level is a sublevel of the Department level.


NN43050-602 03.04 28 May 2009


.


Procedure 80Defining the organizational hierarchy

Step Action

1 Select Edit > Organizational Hierarchy from the GCAS mainwindow.

2 Right-click the folder ORG.

3 Select Rename from the menu.

4 Change ORG to a name that represents the top of yourorganizational structure.

For example, enter Acme Company.

For this example, the following levels have been defined:Division and Department.

5 To add a level to the organization:

a Right-click the folder for the level in which the sublevel is tobe created.

b Click Add New Level.

The first menu option under the organization appears as NewLevel 1 in a form that can be edited.

c Type over this default name with a new name.

For example, type Head Office.

d Repeat this step to add additional levels.

For example, create a new level under Head Office calledSales.

--End--

Enter employee, external party, and role or project informationWith your organizational hierarchy now in place, the next step is to enteryour company’s employee, external party, and role or project information.These are entered in your corporate databases.

Enter employee informationEmployee information is necessary to cost and allocate billing data to theproper individuals and cost centers within your organization.


NN43050-602 03.04 28 May 2009


.


Procedure 81Entering employee information

Step Action

1 From the GCAS main window, select Edit > Employees.

The Employee Editor grid dialog box appears, as shown inFigure 52 "Employee Database Employee Editor" (page 173).Figure 52Employee Database Employee Editor

2 Click on Add New Record.

A blank Employee Editor window appears.

3 Enter the employee information in the following fields:

• Identification—Unique identifier for this employee. Forexample, enter 001.

• First, Middle, and Last Name fields—For example, enterJohn Adam Smith.

• Job Title—For example, enter Sales Manager.

• Org. Path—Employee’s location in the organizationalhierarchy. For example, enter \Acme Company\HeadOffice\Sales.


NN43050-602 03.04 28 May 2009


.


• Manager—Employee’s manager. This can be selected fromthe drop-down menu. For example, enter Bill President.

• E-mail—Employee’s e-mail address. For example, [email protected].

• Street No., City, Prov./State, Country, Postal/Zip—Employee’s address. For example, leave these fields blank.

• Description—Any additional comments about this employee.This is for informational purposes only. For example, leavethis field blank.

4 To add an asset to this employee, click Apply in the rightsection.

The Asset list appears. This allows you to add any assets thatyou want to assign to the employee for billing and reportingpurposes. This can include such assets as account codes,extensions, cellular phone, or pagers.

a From the Type list, select the desired asset. The asset typemust be the same as that selected in Procedure 84 “Enteringa quantity-based bill type” (page 176). For example, selectAccount Code.

b In the Account Code box that appears, enter the accountcode. For example, enter 1001.

c Click OK to accept these values and return to the previousdialog box.

5 Click Close to exit to the main window.

--End--

Enter external party informationExternal parties are those individuals or organizations that exist outside therealm of your organization (for example, customers, vendors, and so on).

Procedure 82Entering external party information in the External Party Database

Step Action

1 From the GCAS main window, select Edit > External Parties.

The External Party Editor grid dialog box appears.

2 Click Add New Record.

A blank External Party editor appears. This editor is very similarto the Employee Database editor.

3 Enter the external party information in the available fields.


NN43050-602 03.04 28 May 2009


.


See Procedure 81 “Entering employee information” (page173) for detailed information about the fields.

4 Click OK to accept these values and return to the previous dialogbox.


--End--

Entering roles or projects informationWithin the Roles/Projects Database, you can document informationrelevant to a particular organizational project. For example, within yourorganization, there can be a marketing project incurring costs. In turn, youcan define your billing entity to be the role project name.

This database editor is similar to the Employee Database editor. Forinstructions about editing this type of database, see the example onentering information in the Employee Database ( “Enter employeeinformation” (page 172)).

Procedure 83Entering role or project information in the Roles/Projects Database

Step Action

1 From the GCAS main window, select Edit > Roles/Projects.

The Roles and Projects Editor grid dialog box appears.

2 Click Add New Record.

A blank Roles and Projects Editor appears. This editor is similarto the Employee Database editor.

3 Enter the role or project information in the available boxes.

4 Click OK to accept these values and return to the previous dialogbox.


--End--

Defining bill typesBy default, bill types fall into one of three categories: quantity-based,time-based, and destination-based. Quantity-based bill types are definedas having quantitative amounts and unit charges (for example, officefurniture, computers, stationery, and so on). Time-based bill types aredefined as having start and finish times (for example, Internet usage).


NN43050-602 03.04 28 May 2009


.


Destination-based bill types are defined as having call attributes such aslocation, digits dialed and route, and source and destination (for example,cellular or pager calls).

Assign bill to a bill typeAfter establishing what kind of bill type is best suited to represent yourdata, the next step is to enter the information from your bill into theGCAS. There are two ways in which you can enter this information. Youcan import a file or manually enter the data from a printed statement(for example, from a vendor’s bill). Whichever method of input you use,your first task is to attach your bill to one of the three defined bill types:quantity-based, time-based, or destination-based.

A quantity-based bill type is used for example purposes. The methodsof data entry for both time-based and destination-based bill types arefundamentally the same as quantity-based bill types. However, wheredata entry formats are different, examples and illustrations provide extraguidance.

Procedure 84Entering a quantity-based bill type

Step Action

1 From the GCAS main window, select Quantity-Based Billing inthe navigation tree.

2 Select File > New Bill Type.

The Properties tab appears.

3 Under Bill Type Name, identify your bill with an appropriatename.

For example, enter Office Furniture.

4 In the Identify Bill Party by box, enter how the billinginformation for this bill type is associated to the correct billingparty in your organization.

For example, you can use an employee’s extension number toassign office furniture charges to the employee, or you can use acalling card to assign calling card charges to the employee.

5 To select an existing value or to add a new one, click the ellipsis(...).

The Billing Key Information dialog box appears. The left sectiondisplays the Lookup Keys that are used to allocate the bill typecharges to the appropriate bill party in your organization.

6 If a Lookup Key is not defined:

a Click <Define New Bill Party Lookup>.


NN43050-602 03.04 28 May 2009


.


b In the Identify Bill Party by box, enter your Lookup Keyname.

c Enter the display mask.

The display mask denotes the format used when enteringvalues relevant to a particular bill type. The display maskcharacters can be numeric identifying the format of theLookup Key. See Table 6 "Examples of mask properties"(page 177) and Table 7 "Mask characters" (page 177) forexamples of mask properties and definitions. You can enterup to 50 characters in this field:

Table 6Examples of mask properties

Mask Description

Null String(Default) No mask. Acts like a standard textbox.

### Example: 321 (extension number)

#### ### ######

Example: 1234 567 891 000 (phone cardnumber)

???? ### Example: ABCD 123 (license plate)

??.#####Example: AB.12345 (purchase ordernumber)

Table 7Mask characters

Mask Description

# Digit placeholder (Optional)

. Decimal placeholder

’ Thousands separator

: Time separator

/ Date separator

& Character placeholder

> Convert all the characters that follow to uppercase.

< Convert all the characters that follow to lowercase.

A Alphanumeric character placeholder (entry required)

a Alphanumeric character placeholder (entry optional)

9 Digit placeholder (entry optional)

C Character or space placeholder

? Letter placeholder

d Click Apply to save the new Lookup Key into the system.


NN43050-602 03.04 28 May 2009


.


For example, click Extension No, and then click OK toassign the office furniture to each employee using theirextension numbers.

7 Repeat this procedure for each for each bill type you aredefining.

--End--

Deleting bill typesTo delete a bill type, search the menu view and highlight the desiredbill type for deletion. Deletion of a bill type deletes any billing recordsassociated with it. The deleted bill type is then removed from thenavigation tree.

Procedure 85Deleting a bill type

Step Action

1 From the navigation tree view of the GCAS main window, selectthe bill type to be deleted.

2 Select File > Delete Bill Type.

--End--

Enter cost profilesHaving defined your bill party identification key within the Billing Key dialogbox, you can now enter your cost profiles (optional). Cost profiles allowyou to define additional fixed costs and applicable taxes to each billableitem within a bill type.

Surcharges or deductions can be applied to an item in any of the followingways:

• A fixed cost per item charge added to the existing item charge. Forexample, a $0.10 fixed surcharge can be made against each recordrelated to a calling card bill. If a calling card has a base cost of $2.00,the total cost of the record, not including tax, would be $2.10.

• A cost per minute charge applied to each minute of each item. Thissurcharge is only applicable to time-based and destination-based billtypes, and is calculated by multiplying the duration of each item (inminutes) by the value entered in this box.

• A percentage adjustment applied against the original charge of eachitem. To increase the charge for each item by 10 percent, enter 10.00in the Percent Adjust box.


NN43050-602 03.04 28 May 2009


.

Using GCAS 179

Define taxesYou have the option of selecting up to four applicable taxes for each billtype. For this example, you enter one applicable tax: the Sample StateTax (SST) of 5 percent.

Procedure 86Defining taxes for a bill type

Step Action

1 From the Properties/Cost Profile dialog box, select Edit >Taxes to launch the Tax Editor dialog box.

2 Click Add graphical.

3 In the Name box, enter the tax name.

For example, enter Sample State Tax.

4 In the Short Name box, enter an abbreviation of the tax name.

For example, enter SST.

5 In the Percentage box, enter the percentile tax amount.

For example, enter 5.

6 Click OK to accept the values and return to the previous dialogbox.

7 After you define all of the required taxes, click Close to savethem and return to the main window.

8 In the Cost Profile group box, select the appropriate taxes foryour bill type from the Tax lists.

9 After all of the information for your bill type is entered, click Saveto add the new bill type to the GCAS.

--End--

Using GCASCreate billing records

After you define your bill types, enter individual billing records or items thatbelong to them.

Procedure 87Entering billing records

Step Action

1 From the navigation tree view of the GCAS main window, selecta defined bill type.

2 Select the Records tab.


NN43050-602 03.04 28 May 2009


.


3 Click Insert New Record.

The Record Editor dialog box appears, as shown in Figure 53"Record Editor dialog box" (page 180).Figure 53Record Editor dialog box

4 Enter the value that identifies the bill party for this record.

In this example, the employee extension is required. Therefore,in the Extension No. box, enter 191.

5 (Optional) In the Description box, enter a description of the billrecord.

For example, enter Main Extension Line.

6 (Optional) From the Report Group list, select a Report Groupvalue.

If an appropriate value is not found in the list, you can typethe required value in the Report Group list. This value furtherorganizes billed items into smaller subgroups. For example,enter Lines.

7 In the Quantity box, enter the quantity of products or servicesthat are to be billed.


NN43050-602 03.04 28 May 2009


.

Using GCAS 181

For example, enter 10.

8 In the Total Cost box, enter the pretax total cost for the specifiedquantity of items.

For example, enter 5.00.

9 In the Item Date box, enter the date assigned to this item (forexample, the original purchase date).

For example, enter 10/19/99.

10 In the Item Time box, enter the time assigned to this item (forexample, the original purchase time).

For example, enter 14:30:00.

11 In the Bill Date list, enter the bill date (that is, the date of the billor bill period on which this record appears).

For example, enter 10/19/99.

12 Click OK to accept the values, save the records, and return tothe main window.

--End--

Summary of fields (Record Editor dialog boxes)You do not necessarily need to enter data into every available data fieldwithin the Record Editor. In many instances, you can choose what datayou want to enter. However, depending upon what type of bill you areentering, there are specific fields that must be entered with a value.

Table 8 "Summary of record fields" (page 181) displays a completesummary of all field headings. Each field is designated as a Required orOptional entry.

Table 8Summary of record fields

Field

(R)equiredor(O)ptional Description

Billing Key R The Bill Party Lookup Key value that associatesthe charge record to the appropriate bill party in yourorganization.

Report Group O Provides the ability to organize the records within a billtype into smaller subgroups for reporting purposes.

Description O Description of the record.

Item Date R Date that the record was created. Dates appear in theformat specified by the short date format entered in theregional settings of your PC’s control panel.


NN43050-602 03.04 28 May 2009


.


Table 8Summary of record fields (cont’d.)

Field

(R)equiredor(O)ptional Description

Item Time O Time that the record was created. Time appears in theformat hh:mm:ss.

Bill Date R Default is the current date.

Quantity O The quantity of product or service items billed by thisrecord. Default is 1.

Duration O Applicable for Time and Destination-Based bill types. Thedefault value is 0:00:00, and the format is hhhhh:mm:ss.

Total Cost O Default is 0.00.

Destination ID O For Destination-Based bill types. Digits dialed.

Destination Location O For Destination-Based bill types. Called location.

Source ID O For Destination-Based bill types. ID of the record source(for example, the source telephone number of a callingcard call).

Source Location O For Destination-Based bill types. Location of where therecord was made.

Direction O For Destination-Based bill types. Incoming or Outgoing.

Route Used O For Destination-Based bill types.

Generate reportsAfter you enter your billing information, you can generate detail andsummary reports listing this information. The reports can appear on thescreen, be saved to a file, be sent to a printer, or be sent to an e-mailaddress. You can also filter and sort information within your bill and,therefore, create reports based on specific information.

Procedure 88Generating a report

Step Action

1 From the GCAS main window, select File > Reports.

The GCAS Reporting window appears, as shown in Figure 54"GCAS Reporting window" (page 183). This window lists thetypes of billing reports that can be generated.


NN43050-602 03.04 28 May 2009


.

Using GCAS 183

Figure 54GCAS Reporting window

2 Click on the report that you want to generate.

When you select the report, a brief description of it is visible inthe description field at the bottom of this dialog box.

3 Select the desired output device from the Output Type list in theProfile group box.

You can output your report to a printer, to the PC screen, to afile, or to an e-mail address.

4 (Optional) To filter the data, select on a filter name in the Filterlist.

If an appropriate filter does not appear in the list, define your ownusing Procedure 89 “Defining a report filter” (page 184).

5 (Optional) To sort the data, select the sorting definition in theSort drop-down menu of the Reporting dialog box.

If an appropriate sorting definition does not appear in the list,define your own using Procedure 90 “Defining a sort definition”(page 185).



NN43050-602 03.04 28 May 2009


.


• Click Go to generate the report immediately.

• Click Schedule and use the Scheduler to generate thereport at a later date and time.

--End--

Procedure 89Defining a report filter

Step Action

1 Click the ellipsis (...) next to the Filter list.

The Filters grid dialog box appears.

2 Click Add.

The Filter definition dialog box appears.

3 Enter the following filter values:

• Filter Name—Name of the filter. This appears in the Filtersgrid dialog box list and in the Filter list of the Reporting dialogbox. You can select this filter by clicking this name in theFilter list of the Reporting dialog box.

• Name in Report—Name of the filter that appears on theapplicable reports.

• Description—Any additional descriptive information aboutthis filter. This is for informational purposes and also appearsin the Filters grid dialog box.

4 Define the report parameters using the filter tabs in this dialogbox.


Each tab allows you to define specific information based onyour filter requirements. Several of the values entered on eachtab are ranges of time or cost (that is, From a certain date Toa certain date, and a Minimum cash amount to a Maximumcash amount). For example, you can print all reports betweentwo dates and include all records that fall between two costamounts. However, the following tab fields do have differentcharacteristics: Bill Type, Direction, and Organization. In each ofthese cases, you can select choices from a list by clicking thedown arrow button located to the right of each option line.

5 Once you have entered the filter’s parameters, click OK to savethem and return to the Filters grid dialog box.


NN43050-602 03.04 28 May 2009


.

Using GCAS 185

The name you entered in the Filter Name box appears in thegrid. After the filter is defined, you can select it any time from theFilter list in the Reporting dialog box.

--End--

Procedure 90Defining a sort definition

Step Action

1 Click the ellipsis button (...) next to the Sort list.

The Sort grid dialog box appears.

2 Click Add.

The Sort definition dialog box appears.

3 Enter the following values:

• Sort Name—Name of the sorting definition. This appearsin the Sorts grid dialog box list and in the Sort list of theReporting dialog box. You can select this sort definition byclicking this name in the Sort list of the Reporting dialog box.

• Description—Any additional descriptive information aboutthis sort definition. This is for informational purposes and alsoappears in the Sort grid dialog box.

4 In the Sort by box, enter the sorting criteria.

5 Click OK to save the sort criteria and return to the Sort griddialog box.

Notice that the name you entered in the Sort Name box appearsin this grid. After the sort order is defined, select it any time fromthe Sort list in this dialog box.

--End--


NN43050-602 03.04 28 May 2009


.



NN43050-602 03.04 28 May 2009


.

187.

Consolidated Reporting System



• “CRS Interface” (page 188)

• “Configuring CRS” (page 189)

• “Using CRS” (page 190)

IntroductionThis chapter provides basic information about configuring and runningthe Consolidated Reporting System (CRS). It also includes exampleprocedures and reference information to assist you in configuring the CRS.

The CRS is used to generate reports by consolidating data from theTBS and the GCAS. By defining filtering and sorting criteria, you cangenerate custom reports that detail organizational and employee spendingcharacteristics.

Each report is broken down into sub-reports that detail user costs forspecific applications within Telephony Manager. The report is summarizedby aggregating all the costs associated with the chargeable entity (that is,the sum of all the sub-report totals).

The following are some of the features of CRS:

• Generation of reports of all chargeable costs to departments orpersons within your organization.

• Combines data from the TBS and GCAS applications detailingproducts or services purchased, and the appropriate chargeable entity.Management can then monitor and isolate specific costs to variousbusiness lines within your organization.

• You can quickly use this information to determine how organizationalentities are utilizing corporate funds and resources.


NN43050-602 03.04 28 May 2009


.

188 Consolidated Reporting System

• The user-friendly Tree View interface allows for quick, easy, andeffective generation of your reports.

• The Report Engine prints professional-looking reports using TrueTypefonts and customizable report logos.

CRS InterfaceThis section contains a brief overview of the CRS main window. Forcomplete details on each of the functions within the main window, refer tothe online Help.

Main windowThe CRS main window, shown in Figure 55 "CRS main window" (page188), is the interface for generating consolidated reports.

Figure 55CRS main window

In the main window you can:

• Select a report

• Define filters and sorts (optional)

• Define an output method

• Schedule or execute a report


NN43050-602 03.04 28 May 2009


.

Configuring CRS 189

The main window has the following menu commands:

• File

• Help

File menuThe File menu contains the following commands. To access thesefunctions, select File from the main window, and then select the desiredcommand.

• Print—immediately launch your report

• Schedule—define a time and date when you want to launch the report

• Exit—exit from the CRS program

Help menuThe Help menu offers commands which provide you with assistance asyou use the CRS.

This menu contains the following commands:

• Help Topics

• About the CRS

Configuring CRSBefore using the CRS, you must install and configure it as part ofTelephony Manager. You must then assign it to a site and system. Referto Telephony Manager 4.0 Installation and Commissioning (NN43050-300)for complete details on installing this application and assigning it to a siteand system.

System accessTo access the CRS from the Telephony Manager Navigator,select the desired site and system, and select CRS , locatedunderTelemanagement. The CRS main window appears, as shown inFigure 55 "CRS main window" (page 188).


NN43050-602 03.04 28 May 2009


.


Using CRSConsolidated reports

The CRS allows you to generate the following consolidated reports, whichare structured as shown in Figure 56 "Consolidated report structure" (page190).

• Organizational Roll-Up Reports

• Entity Detail Report

• Entity Summary Report

Figure 56Consolidated report structure

Organizational Roll-up ReportsOrganizational Roll-up Reports consolidate organizational billinginformation (for example, corporate, divisional, and departmental). TheOrganizational Roll-Up Reports folder contains a report for each level inyour organizational hierarchy (for example, Corporation Roll-Up Report,Division Roll-Up Report, and Department Roll-Up Report).

These reports provide a grouping of information based on theorganizational level identified in the report name. For example, theDepartmental Summary Report provides a grouping of information bydepartment (for example, a report for Sales, Accounts, Administration,Engineering, and so on). The Engineering grouping displays a summaryof all chargeable items incurred by any entity, person, or organizational


NN43050-602 03.04 28 May 2009


.

Using CRS 191

unit immediately attached to the Engineering node, such as theEngineering Manager, the Quality Assurance Team, and the Research andDevelopment Team. The latter two are roll-ups of the chargeable items oftheir respective members.

Entity Detail ReportThe Entity Detail Report consolidates the costs for the different entities(for example, employees, external parties, or roles and projects) fromeach of the supported Telephony Manager applications. By consolidatinginformation in this manner, you can quickly and effectively determine entitycosts.

This report details a listing of individual billing costs within each TelephonyManager application for each entity. The entity’s chargeable records foreach application are listed under separate headings called sub-reports (forexample, TBS and GCAS). Each of these sub-reports contains a detailedlisting and a sub-report summary of the incurred costs for that applicationfor that entity. These summary costs are then combined to produce agrand total cost/charge for that entity (that is, the sum of all the sub-reporttotals).

Entity Summary ReportThe Entity Summary Report is fundamentally the same as the Entity DetailReport. However, unlike that report, the Entity Summary Report providesonly a summary of consolidated bills for each entity in the organizationalhierarchy.

Generating reports

ATTENTIONAll filters apply to all reports.

You can either generate a report that incorporates all entity informationfrom all the Telephony Manager applications, or you can definesub-reports. When you select sub-reports, you choose which TelephonyManager applications to include in the report, and their order of inclusion.This example includes a sub-report.

Procedure 91Generating an Entity Detail Report

Step Action

1 From the navigator tree in the main window, do one of thefollowing:

• To generate an Organizational Roll-up Report:


NN43050-602 03.04 28 May 2009


.


a. Select Organizational Roll-up Report.

b. Select the report type from the list of report typesapplicable to you organization.

• To generate an Entity Detail Report, select Entity DetailReport.

• To generate an Entity Summary Report, select EntitySummary Report.

2 (Optional) Select sub-reports.

a Right-click the dialog box.

b Select Select Sub-report.

c From the Available Applications list, select one or moreof the available applications that you want to include assub-reports (for example, TBS or GCAS).

d Use the arrow keys next to the Available Applications list tomove the applications to the Selected Applications list.

e Order the chosen applications using the arrow keys next tothe Selected Applications section.

3 Click OK to accept the settings, or click Cancel to return to themain window without changing the previous configuration.

4 (Optional) Select application-specific filters and sort definitions.

ATTENTIONAll filters apply to all reports.

You may also select filter and sort criteria that determine thedata ranges that are reported on. These filter and sort optionscan be applied to each sub-report (for example, TBS or GCAS).

a From the navigator tree view in the main window, select thetree view node expander button.

b Select the application.

c To select a current reporting filter or sort option, select it fromthe corresponding Filter or Sort list.

d To add new filters or sorts for this application:

1. Click the ellipsis (...) next to the Filter field or Sort field.

2. In the Filter or Sort dialog box, click Add.You now have access to the application’s own filter tabsor sort options.

3. Navigate the filter tabs or sort options to define yourfiltering or sorting criteria.

e Click OK to save the filter or sort options, or click Cancel toreturn to the Filter or Sort dialog box without saving.


NN43050-602 03.04 28 May 2009


.

Using CRS 193

5 Select output device.

a Click the report in the navigator tree view in the main screen.

b Select an output device from the Output Type list in theOutput group box.

The CRS can send reports to output devices, such asa printer (configured in the operating system), the PCscreen, or to a file. To output your report to a file, selectthe appropriate file type from the Output Type list. Click theellipsis (...) to the right of the File Name field. From the SaveAs dialog box, select the desired name and location for theoutput file.

6 (Optional) Select additional report filters or sort options in theEntity Detail Report Profile group box to add additional reportfilters and sort definitions.

These are additional report filter or sort options, and are usedover and above application-specific filter or sort options, detailedin step 2.


• To generate your report immediately, select File > Print, orclick the Printer icon on the toolbar.

• To schedule the report to be generated at a specific date andtime, select File > Schedule, or click the Schedule icon onthe toolbar.

--End--


NN43050-602 03.04 28 May 2009


.



NN43050-602 03.04 28 May 2009


.

195.

AppendixTBS scripts



• “Real-time CDR data collection” (page 195)

• “CDR data collection from MDR 2000” (page 195)

• “CDR data collection from PollCat III and PollNet Netlink” (page 196)

• “CDR data collection from SEB II” (page 197)

• “Sample data collection” (page 197)

IntroductionThis section contains the script files used by the TBS to perform datacollection. Select the script file that matches your data collection andprocessing requirements.

Real-time CDR data collectionThe following script files are used for real-time CDR data collection fromthe Meridian 1(no buffer unit is required):

SL1OLD.COL Real-time data collection script for Old format CDR.

SL1NEW.COL Real-time data collection script for New format CDR.

CDR data collection from MDR 2000The following script file is used for data collection from an MDR 2000buffer unit:


NN43050-602 03.04 28 May 2009


.

196 TBS scripts

MDR2000.COL Data collection script, which collects New format CDR from MDR2000 to produce normalized CDR (erases contents of buffer). MDR2000 requires a chip that is compatible with X11 Release 23.

M2KIMG_SL1NEW.COL Data collection script, which collects New format CDR from MDR2000 to produce normalized CDR (erases contents of buffer).

Use this script to collect B and X type records. The buffer must beconfigured to collect in image mode. Refer to the MDR 2000 ISDdocumentation for more information about configuring the buffer toimage mode.

ATTENTIONStoring records in image mode reduces the number of records thatcan be stored in the buffer unit. If your buffer unit is nearing itsmaximum capacity, increase the polling frequency.

M2KIMG_SL1OLD.COL Data collection script, which collects Old format CDR from MDR 2000to produce normalized CDR (erases contents of buffer). The buffermust be configured to collect in image mode. Refer to the MDR 2000ISD documentation for more information about configuring the bufferto image mode.

ATTENTIONStoring records in image mode reduces the number of records thatcan be stored in the buffer unit. If your buffer unit is nearing itsmaximum capacity, increase the polling frequency.

CDR data collection from PollCat III and PollNet NetlinkFor the PollNet Netlink through FTP collection scripts, POLLNET_FTP_SL1NEW.COL and POLLNET_FTP_SL1OLD.COL, you must:

• Access the Data Collection Configuration function.

• Set the Collection Type to Ethernet.

• Enter the following information:

— the IP address of the buffer unit

— the name of the file from which collection occurs after the IPaddress value (for example, 10.12.0.23:PNLAST)

If a filename is not specified, then PNLAST is used as the defaultfilename

— the required Logon Name and Password

The following script files are used for data collection from the PollCat IIIand PollNet Netlink buffer units.


NN43050-602 03.04 28 May 2009


.

Sample data collection 197

POLLSL1NEW.COL Data collection script, which collects Newformat CDR from the PollCat III to producenormalized CDR.

POLLSL1OLD.COL Data collection script, which collects Oldformat CDR from the PollCat III to producenormalized CDR.

POLLNET-SL1NEW.COL Data collection script, which collects Newformat CDR from the PollNet Netlink toproduce normalized CDR.

POLLNET-SL1OLD.COL Data collection script, which collects Oldformat CDR from the PollNet Netlink toproduce normalized CDR.

POLLNET_FTP_SL1NEW.COL Data collection script, which collects Newformat CDR from the PollNet Netlinkthrough FTP to produce normalized CDR.

POLLNET_FTP_SL1OLD.COL Data collection script, which collects Oldformat CDR from the PollNet Netlinkthrough FTP to produce normalized CDR.

CDR data collection from SEB IIThe following script files are used for data collection from the SEB II bufferunit:

SEBSL1NEW.COL Data collection script, which collects New format CDRfrom the SEB II to produce normalized CDR.

SEBSL1OLD.COL Data collection script, which collects Old format CDRfrom the SEB II to produce normalized CDR.

Sample data collectionThe following script file is used to collect CDR data from a sample file.This is used for testing purposes:

SAMPLE.COL Data collection script, which collects sample CDR datafrom the sample file in the TBS directory.


NN43050-602 03.04 28 May 2009


.

198 TBS scripts


NN43050-602 03.04 28 May 2009


.

199.

AppendixTBS reports



• “Windows reports” (page 199)

• “Web Navigator reports” (page 222)

IntroductionTelecom Billing System (TBS) provides detailed reports that give youspecific information about the telephone system’s usage and costs that areassociated with the entities in your organization. By providing statisticson your system, the reports help you assess the effectiveness of yourtelephone services.

TBS reports can be accessed from the Telephony Manager Windowsinterface and the Telephony Manager Web interface.

This section describes the reports provided by TBS, and provides severalexamples.

Windows reportsWhen you are creating Windows reports with filters, note that not all filtersapply to all reports.

Cost Analysis reportsExtension DetailThe Extension Detail Report, shown in Figure 57 "Extension Detail Report"(page 200), provides a detailed listing of calls and summary totals for eachextension. If an external party’s phone number matches the digits dialed,the external party’s name is displayed in the comments field. If a matchbetween the digits dialed and an external parties phone number does notexist, the comment field contains the call type.


NN43050-602 03.04 28 May 2009


.

200 TBS reports

Figure 57Extension Detail Report

Extension Detail with Account CodesThe Extension Detail Report with Account Codes, shown in Figure 58"Extension Detail Report with Account Codes" (page 201), shows all thecalls made from a particular extension. If an account code is used tomake a call, this report shows the account code used and the owner ofthat account code in the comments field. If an account code is not used,the comments field shows the call type, for example, Local. Similar to theExtension Detail report, this report includes such information as digitsdialed, location, and the call date, time, and duration. Each extensionbegins a new page on the report. The Extension Detail report with AccountCodes report is based on the Extension Detail report.


NN43050-602 03.04 28 May 2009


.

Windows reports 201

Figure 58Extension Detail Report with Account Codes

Exceptional ChronologicalThe Exception/Chronological Report, shown in Figure 59 "Exception/Chronological Report" (page 201), provides a detailed listing of calls that matchthe specified filter criteria. It is useful for identifying exception calls, suchas calls made to particular phone numbers or whose cost has exceededa specific threshold.

Figure 59Exception/Chronological Report


NN43050-602 03.04 28 May 2009


.

202 TBS reports

Entity DetailThe Entity Detail Report, shown in Figure 60 "Entity Detail Report" (page202), is similar to the Extension Detail Report and provides a detailedlisting of calls and summary information for each user (Employee, ExternalParty, or Role/Project) entered in the system. Outgoing, incoming, andinternal calls are assigned to each user based on the extension from whichthe call was placed. Tandem calls can also be assigned to a user basedon the trunk numbers on the call. If the trunks fall within one of the trunkranges assigned to a user in the Corporate Directories, the call appearson that user’s report.

Figure 60Entity Detail Report

DNIS SummaryThe DNIS Summary Report, shown in Figure 61 "DNIS Summary Report"(page 202), summarizes the information in the DNIS Detail Report. Itprovides the number of calls made to each DNIS number and the totalduration and cost of those calls.

Figure 61DNIS Summary Report


NN43050-602 03.04 28 May 2009


.

Windows reports 203

DNIS DetailThe DNIS Detail Report, shown in Figure 62 "DNIS Detail Report" (page203), provides details for each DNIS number used individually. It lists eachcall made to that number, which extension handled the call, the date, time,duration, and cost. If CLID information is available for the call, the reportalso displays the location from which the call was made.

Figure 62DNIS Detail Report

Auxiliary ID DetailThe Auxiliary ID Detail Report, shown in Figure 63 "Auxiliary ID DetailReport" (page 204), provides a detailed listing of calls and summaryinformation for each Auxiliary ID or extension user (Employee, ExternalParty, or Role/Project). Calls having an Auxiliary ID are charged backusing the Auxiliary ID on the call, while calls with no Auxiliary ID arecharged back using the extension on the call.


NN43050-602 03.04 28 May 2009


.

204 TBS reports

Figure 63Auxiliary ID Detail Report

Authorization Code DetailThe Authorization Code Detail Report, shown in Figure 64 "AuthorizationCode Detail Report" (page 205), provides a detailed listing of callsand summary information for each authorization code user (Employee,External Party, or Role/Project). Calls having no authorization code oran authorization code that is not assigned to another user are chargedback using the extension on the call. If an external party’s phone numbermatches the digits dialed, the external party’s name is displayed in thecomments field. If a match between the digits dialed and an externalparty’s phone number does not exist, the comment field contains the calltype.


NN43050-602 03.04 28 May 2009


.

Windows reports 205

Figure 64Authorization Code Detail Report

Account Code SummaryThe Account Code Summary Report, shown in Figure 65 "Account CodeSummary Report" (page 205), provides a summary of calling statistics andcall charges for each account code used for calls within the system.

Figure 65Account Code Summary Report


NN43050-602 03.04 28 May 2009


.

206 TBS reports

Account Code DetailThe Account Code Detail report, shown in Figure 66 "Account CodeDetail report" (page 206), provides a detailed listing of calls and summaryinformation for each user (Employee, External Party, or Role/Project) towhich one or more account codes are assigned. Calls that do not have anaccount code are not included on the report.

Figure 66Account Code Detail report

Account Code Detail with EmployeesThe Account Code Detail with Employees report, shown in Figure 67"Account Code Detail with Employees report" (page 207), shows details forcalls made with your company’s assigned account codes. It displays allof the calls made using a particular account code. Each call includes theextension from which the call was made along with the extension’s owner.Calls that do not have an account code are not included in this report. Likethe Account Code Detail report, this report includes such information asthe extension number, employee name, digits dialed, and the call date,time, duration, and cost. This report is based on the Account Code Detailreport.


NN43050-602 03.04 28 May 2009


.

Windows reports 207

Figure 67Account Code Detail with Employees report

Entity by Duration graphThe Entity by Duration graph, shown in Figure 68 "Entity by Duration"(page 207), displays the duration of calls per entity.

Figure 68Entity by Duration


NN43050-602 03.04 28 May 2009


.

208 TBS reports

Organizational Summary graphs

• Corporate Summary by Calls

• Cost Center Summary by Costs

• Department Summary by Duration

Corporate Account Code SummaryThe Corporate Account Code Summary report, shown in Figure 69"Corporate Account Code Summary report" (page 208), provides asummary of telephone usage rolled up to each organizational unit at theselected level in the Organizational Hierarchy. Calls are allocated to a unitbased on the users (Employees, External Parties and Projects) assignedto that unit and its subunits. A user is responsible for all calls having anaccount code that is assigned to them. Calls that do not have an accountcode are not included on the report.

Figure 69Corporate Account Code Summary report

Cost Center Authorization Code SummaryThis Cost Center Authorization Code Summary report, shown in Figure 70"Cost Center Authorization Code Summary report" (page 209), providesa summary of telephone usage rolled up to each organizational unit atthe selected level in the Organizational Hierarchy. Calls are allocated toa unit based on the users, (Employees, External Parties, and Projects)assigned to that unit and its subunits. Users are responsible for all callsmade with their authorization code and also any calls made from any oneof their primary extensions, when the authorization code on the call iseither nonexistent or not assigned to another user.


NN43050-602 03.04 28 May 2009


.

Windows reports 209

Figure 70Cost Center Authorization Code Summary report

Department Entity SummaryThe Department Entity Summary report, shown in Figure 71 "DepartmentEntity Summary report" (page 209), provides a summary of telephoneusage rolled up to each organizational unit at the selected level in theOrganizational Hierarchy. Calls are allocated to a unit based on the users(Employees, External Parties, and Projects) assigned to that unit and itssubunits. A user is responsible for all normal calls made from any one oftheir primary extensions as well as those tandem calls which utilize a trunkthat falls within a range of trunks assigned to those users.

Figure 71Department Entity Summary report


NN43050-602 03.04 28 May 2009


.

210 TBS reports

Department Extension SummaryThe Department Extension Summary report, shown in Figure 72"Department Extension Summary report" (page 210), provides a summaryof telephone usage rolled up to each Organizational Unit at the selectedlevel in the Organizational Hierarchy. Calls are allocated to a unit basedon the users (Employees, External Parties, and Projects) assigned to thatunit and its subunits. A user is responsible for all calls made from any oneof their primary extensions.

Figure 72Department Extension Summary report

Directory InformationRole/Project DirectoryThe Role/Project Directory report, shown in Figure 73 "Role/ProjectDirectory" (page 210), lists the roles and projects that are entered in theRoles and Projects Directory. In addition to listing their names, the reportalso includes their extensions, account code, and organizational unit towhich they are assigned.

Figure 73Role/Project Directory


NN43050-602 03.04 28 May 2009


.

Windows reports 211

External Party DirectoryThe External Party Directory report, shown in Figure 74 "External PartyDirectory" (page 211), lists the external parties that are entered in theExternal Party Directory. In addition to listing their names, the report alsoincludes their addresses, account codes and phone numbers.

Figure 74External Party Directory

Employee Directory (by organizational unit)This Employee Directory report provides an alphabetic listing of theemployees within their assigned organizational units. In addition to listingtheir names, the report also includes their extensions and job titles.

Employee Directory (alphabetic)This Employee Directory report, shown in Figure 75 "Employee Directoryreport" (page 212), provides an alphabetic listing of the employees enteredin the Employee Directory. In addition to listing their names, the report alsoincludes their extensions, job titles and the organizational unit to whichthey are assigned.


NN43050-602 03.04 28 May 2009


.

212 TBS reports

Figure 75Employee Directory report

FrequencyUndispersed VerificationThe Undisbursed Verification report provides a detailed listing of callsthat have no account code assigned to them. The calls on the report aregrouped by the extension from which the calls were placed. After thisreport is printed, it can be used as a reference for assigning account codesback to these calls using the Call Database Editor.

Location SummaryThe Location Summary report summarizes calling patterns by call location.The report includes the total count, duration, and cost of calls that aremade to each location.

Hold Time DetailThe Hold Time Detail report provides a detailed listing of calls, includingthe amount of time the call was placed on hold. This report can be usedto provide details of any unusually long calls appearing on the Hold TimeSummary Report. Hold-time information is not available in the CDR of allphone systems. If this is the case for your phone switch, the Hold TimeReport does not display any data.


NN43050-602 03.04 28 May 2009


.

Windows reports 213

Frequently Called NumbersThe Frequently Called Numbers report summarizes calling patterns bydigits dialed for outgoing calls and Calling Line Id for incoming calls. Thereport includes the number of times a phone number was dialed as well asthe total duration and cost of the calls to that number.

External Party SummaryThe External Party Summary report provides a detailed listing of calls thatwere made to external parties listed in the External Party Directory. Callsare assigned to an External Party when their phone numbers match thedigits dialed in the call records.

Duration Summary by Call Type graphThe Duration Summary by Call Type graph, shown in Figure 76 "DurationSummary by Call Type" (page 213), displays the number and duration ofcalls by call type.

Figure 76Duration Summary by Call Type


NN43050-602 03.04 28 May 2009


.

214 TBS reports

Call Duration Summary graphThe Duration Summary Graph shown onFigure 77 "Call DurationSummary" (page 214) displays the duration of calls by DN.

Figure 77Call Duration Summary

Digits DetailThe Digits Detail report provides a detailed listing of calls and summarytotals for each phone number dialed.

Calling Area SummaryThe Calling Area Summary report summarizes calling patterns byNPA-NXX/dial code and location. The report includes the total count,duration, and cost of calls that are made to each of the NPA-NXX/dial codeand location combinations.


NN43050-602 03.04 28 May 2009


.

Windows reports 215

Area Code SummaryThe Area Code Summary report summarizes calling patterns by areacode. The report includes the total count, duration, and cost of calls thatare made to each area code.

Area Code Location SummaryThe Area Code Location Summary report summarizes calling patternsby area code and calling location. The report includes the total count,duration, and cost of calls that are made to each area code and location.

Area Code Summary graphs (Calls, Costs, and Duration)The Area Code Summary graphs summarizes calling patterns by areacode. The graphs display each for total count, duration, and cost of callsthat are made to each area code.

Location Summary graphs (Calls, Costs, and Duration)The Location Summary graphs display incoming and outgoing callingpatterns by location. The graphs display each for total count, duration, andcost of calls made at each location.

For example, the Location Summary by cost graph, shown in Figure78 "Location by cost summary" (page 215), displays the costs ofincoming/outgoing calls per location.

Figure 78Location by cost summary


NN43050-602 03.04 28 May 2009


.

216 TBS reports

SurchargeException/Chronological SurchargeThe Exception/Chronological Surcharge report provides a detailed listingof calls that match the specified filter criteria, and includes a breakdownof the total call cost into Cost, Surcharge, and Total Cost amounts. Itis particularly useful for identifying exception calls, such as calls madeto particular phone numbers or whose cost has exceeded a specificthreshold. This profit version of the Exception/Chronological reportprovides a breakdown of the total call cost into Cost, Surcharge, and TotalCost amounts.

Entity Surcharge SummaryThe Entity Surcharge Summary report sums up information on calls byEntity (Employee, External Party, Role/Project). The Entity value assignedto each call is based first on the Authorization Code associated with it—forexample the Authorization Code’s Primary Entity. For calls without anassociated Authorization Code, the Entity value assigned is the BillableExtension’s Primary Entity. Tandem calls can also be assigned to an Entitybased on the trunk numbers on the call. If the trunks fall within one of thetrunk ranges assigned to an Entity in the Corporate Directories, the callappears within that Entity’s data.

Entity Surcharge DetailThe Entity Surcharge Detail report, shown in Figure 79 "Entity SurchargeDetail report" (page 217), provides a detailed listing of calls and summaryinformation including a breakdown of the total call cost into Cost,Surcharge and Total Cost amounts for each authorization code user/Entity(Employee, External Party or Role/Project). Outgoing, incoming andinternal calls are assigned to each Entity based on the authorization codeused to place the call. Calls that have either no authorization code or anunassigned authorization code are charged back using the extension onthe call. Tandem Calls can also be assigned to an Entity based on thetrunk numbers on the call. If the trunks fall within one of the trunk rangesassigned to an Entity in the Corporate Directories, the call appears on thatEntity’s report.


NN43050-602 03.04 28 May 2009


.

Windows reports 217

Figure 79Entity Surcharge Detail report

Entity Surcharge SummaryThis Entity Surcharge Summary report provides a summary of telephoneusage rolled up to each Organizational Unit at the selected level in theOrganizational Hierarchy, and includes a breakdown of total call costinto Cost, Surcharge, and Total Cost amounts. Calls are allocated to aunit based on the Entities (Employees, External Parties, and Projects)assigned to that unit and its subunits. An Entity is responsible for all callsmade with their authorization code and also any calls made from any oneof their primary extensions when an authorization code on the call is eithernonexistent or not assigned to another Entity. Tandem Calls can also beassigned to an Entity based on the trunk numbers on the call. If the trunksfall within one of the trunk ranges assigned to an Entity in the CorporateDirectories, the call appears within that Entity’s data.

UtilitiesTrunk DiagnosticThe Trunk Diagnostic Report, shown in Figure 80 "Trunk DiagnosticReport" (page 218), compares trunk ranges you have entered in theTelephone Configuration with the trunks that have actual call activity. Thereport lists all of the trunks that are entered in the Telephone Configurationbut have no call activity as well as all of the trunks that have call activitybut have not been entered in the Telephone Configuration.


NN43050-602 03.04 28 May 2009


.

218 TBS reports

Figure 80Trunk Diagnostic Report

Configuration ReportThe Configuration Report, shown in Figure 81 "Configuration Report"(page 218), displays the system configuration and rating informationentered in the Telephone Configuration. It can be used to review thecost configuration for each of the services defined in the TelephoneConfiguration editor.

Figure 81Configuration Report


NN43050-602 03.04 28 May 2009


.

Windows reports 219

System ConfigurationThe System Configuration report, shown in Figure 82 "SystemConfiguration report" (page 219), displays the configuration parametersthat indicate how TBS processes, collects, and transmits call data. Italso provides information about the various alarms and alarm thresholdsconfigured in the system.

Figure 82System Configuration report

Extension DiagnosticThe Extension Diagnostic Report, shown in Figure 83 "ExtensionDiagnostic Report" (page 220), compares the extensions assigned to users(Employees, External Parties, Roles/Projects) in the Corporate Directorieswith the extensions that have actual call activity. The report lists all of theextensions that are listed in the Directories but have no call activity, as wellas all of the extensions that have call activity but are not assigned to auser in the Directories.


NN43050-602 03.04 28 May 2009


.

220 TBS reports

Figure 83Extension Diagnostic Report

Authorization Code DiagnosticThe Authorization Code Diagnostic Report, shown in Figure 84"Authorization Code Diagnostic Report" (page 220), compares theauthorization codes assigned to users (Employees, External Parties,Roles/Projects) in the Corporate Directories with the authorizationcodes that were actually used on call records. The report lists all of theauthorization codes that are listed in the Directories but are not used, aswell as all of the authorization codes that are used but are not assignedto a user in the Directories.

Figure 84Authorization Code Diagnostic Report

Account Code DiagnosticThe Account Code Diagnostic Report, shown in Figure 85 "Account CodeDiagnostic Report" (page 221), compares the account codes assignedto users (Employees, External Parties, Roles/Projects) in the CorporateDirectories with the account codes that were actually used on call records.The report lists all of the account codes that are listed in the Directoriesbut are not used, as well as all of the account codes that are used but arenot assigned to a user in the Directories.


NN43050-602 03.04 28 May 2009


.

Windows reports 221

Figure 85Account Code Diagnostic Report

Traffic ReportsTrunk Group Utilization graphs (Calls, Costs, and Duration)The Trunk Group Utilization graphs display trunk group utilization by calls,costs, and duration.

For example, the Trunk Group Utilization by Duration graph, shown inFigure 86 "Trunk Group Utilization by Duration" (page 221), displays theincoming/outgoing calls and their duration by Trunk Group.

Figure 86Trunk Group Utilization by Duration

Trunk UtilizationThe Trunk Utilization Report, shown in Figure 87 "Trunk Utilization Report"(page 222), provides call usage details for each trunk assigned to TrunkGroups or Services in the Telephone Configuration Database.


NN43050-602 03.04 28 May 2009


.

222 TBS reports

Figure 87Trunk Utilization Report

Trunk DetailThe Trunk Detail Report provides a detailed listing of calls and summarytotals for each trunk line.

Web Navigator reportsThe following reports are accessible from the Telephony Manager WebNavigator. Refer to Telephony Manager 4.0 System Administration(NN43050-601) for more information.

Cost ReportsExtension SummaryThe Extension Summary report provides a summary of calls and totals foreach extension. Clicking on any entity that is hyper-linked gives a detailedlisting of calls for that entity.

Authorization Code SummaryThe Authorization Code Summary Report, shown in Figure 88"Authorization Code Summary Report" (page 223), gives total costs forcalls made using an authorization code grouped by the prime owner.Authorization codes are not shown for security reasons. Clicking on anyentity that is hyperlinked gives a detailed listing of calls for that entity.


NN43050-602 03.04 28 May 2009


.

Web Navigator reports 223

Figure 88Authorization Code Summary Report

Account Code SummaryThe Account Code Summary Report displays the total number of calls,sum of duration, and sum of cost. The account code’s data is thengrouped by the CostField which can be Internal, Local, LD (Long Distance)and so on.

Clicking on any entity that is hyperlinked gives a detailed listing of callsfor that entity.

Level ReportsExtension Roll-UpThe Extension Roll-Up Report gives total costs for calls made usingextensions grouped by the levels of the company OrganizationalHierarchy. Clicking on any entity that is hyperlinked gives a detailed listingof calls for that entity.

Authorization Code Roll-UpThe Authorization Code Roll-Up Report, shown in Figure 89 "AuthorizationCode Roll-Up Report" (page 224), generates cost totals for calls madeusing an authorization code grouped by the company organizational levelsAuthorization Codes are not shown for security reasons. Clicking on anyentity that is hyperlinked gives a detailed listing of calls for that entity.


NN43050-602 03.04 28 May 2009


.

224 TBS reports

Figure 89Authorization Code Roll-Up Report

Account Code Roll-UpThe Account Code Roll-Up Report generates cost totals for calls madeusing account codes grouped by the company’s organizational levels.Clicking on any entity that is hyperlinked gives a detailed listing of callsfor that entity.

ATTENTIONFor account codes to be grouped, the prime owner must be assigned to theOrganization node.

Frequency/Digits ReportsFrequently Called NumbersThe Frequently Called Numbers Report, shown in Figure 90 "FrequentlyCalled Numbers Report" (page 225), provides total number of times eachtelephone number listed was called and the total duration and cost ofthose calls. Clicking on the hyperlinked telephone number gives a detailedlisting of those calls including who made them.


NN43050-602 03.04 28 May 2009


.


Figure 90Frequently Called Numbers Report

Frequently Called LocationsThe Frequently Called Locations Report, shown in Figure 91 "FrequentlyCalled Locations Report" (page 225), provides the total number of timeseach telephone location listed was called and the total duration and cost ofthose calls. Clicking on the hyperlinked telephone location gives a detailedlisting of those calls including who made them.

Figure 91Frequently Called Locations Report


NN43050-602 03.04 28 May 2009


.

226 TBS reports

Area Code SummaryThe Area Code Summary Report, shown in Figure 92 "Area CodeSummary report" (page 226), lists the total number of calls, sum ofduration, and sum of cost for each area code. Clicking on the hyperlinkedarea code displays a detailed listing of the calls including who made themfor that area code.

Figure 92Area Code Summary report

Ring Time by Time of DayThe Ring Time by Time of Day Report summarizes calls within eachhalf hour time period of the day. This report displays the total number ofcalls, the number of unanswered calls, the average time and maximumring times for the unanswered calls, and the number of answered callsand average and maximum ring times for the answered calls. Clicking onthe hyperlinked Time Period provides a list of detailed calls for that timeperiod.

Ring Time by ExtensionThe Ring Time by Extension Report lists each extension that received callswithin the Time Period selected from the previously displayed Ring TimeReport by Time Period.

Hold Time by Time of DayThe Hold Time by Time of Day Report summarizes calls within eachhalf-hour time period of the day and displays the total number of answeredcalls, the number of calls placed on hold, the total duration time for these


NN43050-602 03.04 28 May 2009


.


calls, the average hold time and the maximum hold time. The time is inseconds, and overall totals, average, and maximum are provided. Clickingon the hyperlinked Time Period provides a detailed listing of the callsmade during that time period.

Hold Time by ExtensionThe Hold Time by Extension Report, shown in Figure 93 "Hold Time byExtension Report" (page 227), is accessed by clicking on the hyperlinkedTime Period from the previous report. All time is in seconds. Overall totals,hold time average, and hold time maximum are provided.

Figure 93Hold Time by Extension Report

Trunk ReportsTrunk Group UtilizationThe Trunk Group Utilization Report, shown in Figure 94 "Trunk GroupUtilization Report" (page 228), provides call usage details for each TrunkGroup or Service in the Telephone Configuration Database. This reportgives total calls, total incoming and outgoing calls, total duration, and totalcosts. Clicking on the hyperlinked Trunk Group provides a list of eachTrunk Group member.


NN43050-602 03.04 28 May 2009


.

228 TBS reports

Figure 94Trunk Group Utilization Report

Trunk UtilizationThe Trunk Utilization Report, shown in Figure 95 "Trunk Utilization Report"(page 228), is accessed by selecting a Trunk Group link in the previousreport. Clicking on the hyperlinked Trunk Group member provides a list ofall calls made on that trunk member.

Figure 95Trunk Utilization Report

Diagnostic ReportsExtension DiagnosticThe Extension Diagnostic Report lists all the extensions that are enteredin the Telephone Configuration that have no call activity as well as allthe extensions that have call activity but have not been entered in theTelephone Configuration.


NN43050-602 03.04 28 May 2009


.


Trunk DiagnosticThe Trunk Diagnostic Report, shown in Figure 96 "Trunk DiagnosticReport" (page 229), lists all the trunks that are entered in the TelephoneConfiguration that have no call activity as well as all of the trunks that havecall activity but have not been entered in the Telephone Configurations.

Figure 96Trunk Diagnostic Report


NN43050-602 03.04 28 May 2009


.

230 TBS reports


NN43050-602 03.04 28 May 2009


.

231.

AppendixField Data Type Formatting for Exportand Transmission



• “Data type” (page 231)

• “Data format” (page 232)

IntroductionThis section describes the data type fields and the permissible format ofcharacters and examples for each data type.

Data typeYou define the fields to be exported in the various export utilities ortransmitted during TBS Transmission. For each field, you specify theproperties, which can include the position in the output file, the width, thejustification, and the format.

Each exportable field holds a certain type of data. This data type controlsthe type of information a field contains. A currency field, for example,cannot hold letters, only numbers; the same applies to duration columns.

The data type of each of the fields falls into one of five categories. SeeTable 9 "Field data type" (page 231).

Table 9Field data type

Data Type Description

String The String data type holds any character, number, orpunctuation symbol. You cannot format this data type.


NN43050-602 03.04 28 May 2009


.

232 Field Data Type Formatting for Export and Transmission

Table 9Field data type (cont’d.)

Date The Date data type holds date values that you can format toappear in a wide variety of forms.

Time The Time data type holds time values that you can format toappear in a wide variety of forms.

Duration The Duration data type holds numbers that can be formatted toappear as whole numbers or in time format that includes, forexample, a colon—the typical time format separator.

Currency The Currency data type holds numbers that can be formattedwith a thousands separator, grouped around the decimal,include zero or more decimal numbers, and rounded up.

The data type for a field appears at the top right of the Export Formatdialog or the Transmission Record Format dialog, immediately below thefield name.

Data formatThe format defines how each value is represented in the output. Forexample, a format applied to a date column can change the output orderfrom Month-Day-Year to Year-Month-Day.

You can modify the field value and its appearance in the export file ortransmission stream with a user-defined format string. See the followingsections for the definition of the permissible format characters andexamples for each data type.

DATE data typeThe permissible format characters for data type DATE are as follows:

• d = day

• M = month

• y = year

You can combine the base format characters to create format specifiersas shown in Table 10 "Permissible format characters for DATE data type"(page 233).


NN43050-602 03.04 28 May 2009


.

Data format 233

Table 10Permissible format characters for DATE data type

Characters Specifiers

d Day of the month (1–31). No padding of leading zero for days1 through 9.

dd Day of the month (01–31). A leading zero is prefixed on daysof the month 1 through 9.

ddd Day of the week, abbreviated to three characters (Sun–Sat).

dddd Day of the week, full name of the day (Sunday–Saturday).

M Month of the year (1–12). No padding of a leading zero formonths from 1 through 10.

MM Months of the year (01–12). A leading zero is prefixed tomonths from 1 through 9.

MMM Month of the year, abbreviated to three characters (Jan–Dec).

MMMM Month of the year, full name of the month (January–December).

y Single-digit year number (1–9) where the last two digits of theyear are from 01 through 09. If the last two digits of the yearare greater than 10, then y produces a two-digit number from10 through 99.

yy Two-digit year number (01–99). A leading zero is prefixed onyears ending in 1 through 9 (such as 2001–2009).

yyy or yyyy Four-digit year number.

You can repeat these date format specifiers to duplicate the output ofany particular value; however, any character other than d, M or y mustseparate the specifier. A format specifier of yy yy is not the same as yyyy.The first might produce 06 06, while the second might produce 2006. Aformat specifier of yyyyy produces the same result as yyyy.

Format specifiers can be combined to produce the desired output. Acommon North American date specifier is MM/dd/yyyy. Also common aredd-MM-yyyy and yyyy-MM-dd.

Any character can separate format specifiers and any number ofcharacters may be specified. The most common separator is the forwardslash (/). Any character other than d, M, and y is considered a separatorand is included in the result.

See Table 11 "Examples of DATE format and output" (page 234) forexamples of DATE format, assuming a date of April 7, 2006.


NN43050-602 03.04 28 May 2009


.


Table 11Examples of DATE format and output

Format Specifier Output

MM/dd 04/07

dd-MM-yyyy 07-04-2006

MMM MMMM d, yyyy Fri April 7, 2006

yyyyMMdd 20060407

MM --- M === y 04 --- 4 === 6

dd (day) 04 (day)

TIME data typeThe permissible format characters for data type TIME are as follows:

• h = hour

• H = hour

• m = minute

• s = second

• t = a.m./p.m.

You can combine the base format characters to create format specifiersas shown in Table 12 "Permissible format characters for TIME data type"(page 234).

Table 12Permissible format characters for TIME data type

Characters Specifiers

h Hour of the day (1–12). No padding of leading zero for hours1 through 9. There is no differentiation between a.m. and p.m.with this specifier. Lowercase h is typically used when theformat specification includes an a.m./p.m..

hh Hour of the day (01–12). A leading zero is added for hours 1through 9. There is no differentiation between a.m. and p.m.with this specifier. Lowercase h is typically used when theformat specification includes an a.m./p.m. designator.

H Hour of the day (1–23). No padding of a leading zero for hours1 through 9. Uppercase H is typically used when the formatspecification does not include an a.m./p.m. designator.

HH Hour of the day (01–23). A leading zero is added for hours1 through 9. Uppercase H is typically used when the formatspecification does not include an a.m./p.m. designator.


NN43050-602 03.04 28 May 2009


.

Data format 235

Table 12Permissible format characters for TIME data type (cont’d.)

m Minute of the hour (1–59). No padding of a leading zero forminutes 1 through 9.

mm Minute of the hour (01–59). A leading zero is added forminutes 1 through 9.

s Second of the minute (1–59). No padding of a leading zero forseconds 1 through 9.

ss Second of the minute (01 – 59). A leading zero is added forseconds 1 through 9.

t A/P designator, corresponding to either a.m. or p.m.. Thisspecifier can be used independently of h, hh, H, or HH.

tt a.m./p.m. designator. This specifier can be used independentlyof h, hh, H, or HH.

These time format specifiers can be repeated to duplicate the output ofany particular value; however, the specifier must be separated by at leastone character.

Format specifiers can be combined to produce the desired output. Themost common time specifier is HH:mm:ss. For example, 10:06 p.m. isoutput as 22:06:00.

Any character can separate format specifiers and any number ofcharacters may be specified. The most common separator is the colon(:). Any character other than h, H, m, and t, is considered a separator andwill be included in the result.

See Table 13 "Examples of TIME format and output" (page 235) forexamples of TIME format, assuming a time of 8:12 p.m.

Table 13Examples of TIME format and output

Format Specifier Output

hh:mm:ss 08:12:00

h:m:s 8:12:00

Hh:mm 20:12

h:mm:ss t 8:12:00 P

HH:mm tt 20:12 p.m.

HHmmss 201200

s 0


NN43050-602 03.04 28 May 2009


.


DURATION data typeThe permissible format characters for data type DURATION are as follows:

• h, H = hours

• m, M = minutes

• s, S = seconds

• d, D = decimal minutes

All duration fields store their data in seconds. The base format charactersconvert the value from seconds to seconds, minutes, hours, or decimalminutes, and each with or without one or more leading zeroes.

Be aware of the following rules when you create a format specifier for aduration field:

1. The capital letter format characters (H, M, S, and D) are placeholdersfor a number, and holds zero if the duration is not large enough toconsume all format characters. For example, a specifier of MM for aduration of 60 seconds returns 01. The first M is a placeholder for theleading zero.

2. Related to the previous rule, if the duration is larger than the formatspecifier length, the duration is not truncated or reduced based on thespecifier length. For example, a specifier of SS for a duration of 145seconds returns 145. However, based on the maximum field widthspecified, the duration digits may be truncated (left or right) based onthe justification.

3. The base format characters are assigned priority for durationconsumption. The characters are ordered as follows: h/H, m/M/d/D,and s/S, where m/M and d/D have the same priority. You can seeconsumption when more than one type of format character is present.For example, a format specification of HH:MM for a duration of 4230seconds (1 hour, 10 minutes, and 30 seconds), returns a value of01:10. HH takes priority and consumes 3600 seconds, leaving 600seconds for consumption by MM. If the format specification wereonly MM, it would return 70, not 10, because HH was not present toconsume the time.

4. Duplicate format characters do not individually consume more time. Aformat specification of H:H for a duration of 3600 seconds, returns 1:1.The first H does not consume all the time such that nothing is left to fillthe spot for the second H.

5. Results are not rounded. For example, a specifier of M for a durationof 150 seconds (2 minutes and 30 seconds), is output as 2. It is notrounded up or down to the nearest minute. Rounding can be controlledby the rounding interval options in Telephone Configuration. However,


NN43050-602 03.04 28 May 2009


.

Data format 237

not all fields can be rounded. The Billed Duration field can be roundedas it affects charge amounts, but the Duration field, which holds theoriginal call duration, cannot be rounded.

6. Results are always right-aligned and extra base characters are alwaysassumed to prefix the result. That is, a format specifier of SSSS for aduration of 95 seconds results in an output of 0095. The result may beleft, center, or right-aligned in the column within which it is output.

The following rules apply to decimal time and the m, M, d, and Dspecifiers:

1. Decimal time is supported only with minutes. Decimal hours andseconds is not supported. The D and d specifiers convert the totalduration (in seconds) to minutes, and the decimal part of the output isbased on the remaining seconds.

2. The number of digits following the decimal is controlled by the use ofd, D, and the number and location of zeros following the decimal. Asingle d means show one decimal place, but do not include the decimaland number if that one digit following the decimal is a zero. A single Dmeans one digit always shows following the decimal. For example, aspecifier of d against 61 seconds produces the output of 1 because 61seconds = 1.0167 minutes and D produces 1.0. The same specifiersagainst 66 seconds both produce results of 1.1.

3. Combining upper- and lowercase m with either uppercase or lowercased produces the same result. However, any character (separator)between the m/M and the d/D appears in the output preceding thedecimal. For example, a specifier of M D against a duration of 66produces 1.1.

4. The d and D specifiers imply a decimal place. If you include anotherdecimal, such as a specifier of m.d, results in a duplicate decimalcharacter.

CURRENCY data typeThe permissible format characters for data type CURRENCY are asfollows:

• # - The format character is a placeholder for significant digits.Insignificant zeros are not displayed to the right of the decimal andleading zeros are also not output.

• 0 - This placeholder always displays insignificant zeros for digits to theright of the decimal. It displays zero if the number has fewer digits thanthere are zeros in the format.


NN43050-602 03.04 28 May 2009


.


The CURRENCY data type is a numeric field, which may contain zeros,positive numbers, and negative numbers. A format specification can beconstructed to control how each type of number appears in the output.

The format specification for the CURRENCY type may contain betweenone and three sections, each separated by semicolons. For example,format for positive numbers; format for negative numbers; format for zeros.

The following rules apply when you define sections:

1. If all three sections are defined, each is used to format the numbersduring export or transmission.

2. If only two sections are defined, the first is used for positive numbersand zeros, and the second is used for negative numbers.

3. If only one section is defined, all numbers use that format. Negativenumbers are still output as negative, because of regional settings, eventhough the negative number format section can be missing.

To skip a section, include an ending semicolon.

Each format can use the number placeholders (# and 0), and othercommon nonplaceholders such as ( - ), ( ( ), and ( ) ).

If the output number has more digits to the right of the decimal pointthan there are format characters, the number rounds to the number ofplaceholders.

If the output number has more digits to the left of the decimal point thanthere are placeholders, the output is comprised of extra digits.

See Table 14 "Examples of CURRENCY format and result" (page 238) forexamples of CURRENCY format. These examples exclude the currencysymbol for display purposes.

Table 14Examples of CURRENCY format and result

Format Sample Value Result

#.00 123.8 123.80

#.00 0.1234 .12

0.# 10.66 10.7

0.# 10.0 10

#,##0.0 100.81 100.8

#,##0.0 19123 19,123.0


NN43050-602 03.04 28 May 2009


.

Data format 239

Table 14Examples of CURRENCY format and result (cont’d.)

# ##0 19123.9 19 124

0.00;(0.000) -100.0 (100,000)

0.00;(0.00) 100.1 100.10

0.0;;0 0.8 0.8

0.0;;0 0.0 0

0.0;;0 -1.0 -1.0


NN43050-602 03.04 28 May 2009


.



NN43050-602 03.04 28 May 2009


.

241.

List of termsAccess Code

The number dialed to connect the user with an outgoing trunkgroup (for example, 9 for local calls).

Account CodeAn optional series of dialed digits used for internal corporatepurposes of identifying a customer or client. These codes areused for client billing or tracking purposes.

AIOD/SMDRAutomatic Identification of Outward Dialing or Station MessageDetail Recording. Suggests a method of capturing completedetails of outgoing calls, which may be further processed.

Area CodeA three-digit number used to identify toll centers that are not in theNumbering Plan Area of the calling party.

AttendantConsole operator for the CS 1000 or Meridian 1 system, oftenreferred to as the switchboard operator.

Authorization CodeA series of dialed digits that identify the caller and cause the CS1000 or Meridian 1 system to grant access to services that areotherwise restricted.

BandA geographical area to which a subscriber is entitled to call. Band1 entitles the subscriber to call fewer area codes than Band 5. It isalso referred to as Zone.


NN43050-602 03.04 28 May 2009


.

242 List of terms

BaudA measure of data transmission speed. It is expressed in bits persecond, which roughly represents the character speed multipliedby 10. For example, 300 Baud is roughly 30 characters persecond.

CBXSee Private Branch Exchange.

CCSSee Centi-Call Seconds.

CDRCall Detail Recording. See Station Message Detail Recording.

Centi-Call SecondsA unit used for the measurement of telephone traffic analysis,equivalent to one hundred seconds of telephone usage.

Central OfficeRefers to the telephone company office to which incoming andoutgoing lines are connected for the subscriber.

DatabaseA file or group of files, which are interrelated or serve a commonpurpose.

DDDSee Direct Distance Dialing.

Direct Distance DialingThe service that allows dialing to areas outside the local areawithout the assistance of the operator.

DNDirectory Number. A user’s telephone extension number.

DurationThe length of time taken for a call. The CS 1000 or Meridian 1system records the duration as an estimate, because no signal isavailable to determine when the called party answers. Therefore,many short calls may be recorded for which no conversation tookplace. The limit for call duration is often adjustable.

EAS NPASee Extended Area Service.


NN43050-602 03.04 28 May 2009


.

243

ErlangThe telephone traffic’s international unit of measurement. Oneerlang is a trunk occupied for an hour; this is equivalent to 36CCS.

ExchangeAn area in which there is a uniform set of charges for thetelephone service. It often refers to a central office and the firstthree digits dialed for a local call. It is also referred to as NXX.

Extended Area ServiceA local telephone calling area, which is larger than normal.

FieldOne data item, which is part of a group of data items making upa data record.

FileA group of data records.

Flat Rate ServiceA uniform fee paid for services regardless of usage.

Foreign ExchangeA telephone number from a remote exchange working in a localexchange. Mileage charges usually apply.

FXSee Foreign Exchange.

Grade of ServiceThe probability of getting a busy signal when trying to access aline.

LCRSee Least Cost Route.

Leased LinesRefers to private lines between two switching centers.

Least Cost RouteSome CS 1000and Meridian 1 systems have the ability todetermine the least expensive call route.


NN43050-602 03.04 28 May 2009


.

244 List of terms

Measured ServiceMeasured service charges are dependent on the time of day,duration of the call, and the distance to the point dialed. Localcalls in some cities are charged by measured unit, which ismeasured service.

Message UnitA unit for charging local calls comprised of length of call, distancecalled, and time of day.

NodeUsed to indicate a CS 1000 or Meridian 1 system in a network. Itcan also mean any endpoint in a network.

NPASee Area Code.

NXXSee Exchange.

Other Common CarrierA private company that has filed tariffs with the FCC to providelong-distance telephone service to subscribers.

PABXSee Private Branch Exchange.

PBXSee Private Branch Exchange and Node.

Peg CountA counting device within the CS 1000 or Meridian 1 system, whichindicates the number of calls placed, received, or blocked.

Private Branch ExchangeA privately owned telephone system, which supplies the interfacebetween the business user and the public network. It is alsoreferred to as PABX (Automatic) and CBX (computerized).

Pro-rated CostingWhen the cost per minute for calls (using a specific trunk or trunkgroup) is calculated automatically by the system based on thetotal fixed cost of the trunks and divided by the actual usage ofthose trunks.


NN43050-602 03.04 28 May 2009


.

245

SDI portSee Serial Data Interface port.

Serial Data Interface portA port on the CS 1000 or Meridian 1 system that can beconfigured to output CDR data.

SMDRSee Station Message Detail Recording.

Station Message Detail RecordingThe ability of a CS 1000 or Meridian 1 system to outputinformation to supply reports which include time of call, callingextension, duration of call, number dialed, trunk group, and date.Additional information may also be output.

TariffA document filed with the FCC which details the services,equipment, and costs offered by a communications carrier. Atariffed item has a fixed cost.

TELCOA telephone company.

TIE LineA dedicated circuit linking two CS 1000 or Meridian 1 systems.

TrunkA circuit used to connect two telephones. Trunks can beincoming, outgoing, two-way, or interoffice. Trunks are alsoidentified by the type of service they provide (that is, DDD, FX).

Trunk GroupA group of trunks categorized by the type of service they provide.For example, trunks with DDD access are contained in a singletrunk group.


NN43050-602 03.04 28 May 2009


.

246 List of terms

ZoneSee Band.


NN43050-602 03.04 28 May 2009


.

247.

Index

Aaccess rights 161Account Code Detail Report 43Account Code Diagnostic Report 45Account Code Roll-up Report 142, 159Account Code Roll-up Summary

Reports 43Account Code Summary Report 43,

142, 158Account Code Surcharge Detail Report 45Account Code Surcharge Roll-up

Summary Reports 45Account Code Surcharge Summary

Report 45Archive Call Database 38Area Code Location Summary Report 44Area Code Summary Report 44, 159Authorization Code Detail Report 43Authorization Code Diagnostic Report 45Authorization Code Roll-up Report 159Authorization Code Roll-up Summary

Reports 43Authorization Code Summary Report 158Auxiliary ID Detail Report 43

BBill Party Surcharge function 117bill types 175buffer boxes

MDR-2000 ISD 61MDR2000/2000e 137

buffer units 19

CCall Area Summary Report 44Call Database 38, 49

call detail informationbenefits of 18

Call Digit Translation 85call records 19

collection 21costing 23

Call Type Definition 80call usage details 159campus billing in Telecom Billing

System 117Carrier Pricing Template 82Carrier Pricing Templates 81CDR output format 60CDR record 19Consolidated Call Cost Reports

corporate properties 144costing configuration 144install and configure 146interface 140overview 14

Consolidated Reporting Systemaccess 189Entity Detail Report 191Entity Summary Report 191Organizational Roll-up Reports 190overview 15

consolidated reports 190Consolidated Server 148Consolidated Server list 143context-sensitive Help 15corporate properties 144Cost Analysis Reports 42Cost reports 158creating custom logos on reports 41currencies

alternate 151local 151


NN43050-602 03.04 28 May 2009


.

248

Custom Reports 46

Ddata collection in Telecom Billing

System 50data collection troubleshooting 108Diagnostic reports 159Dialed Number Identification Service 136Digits Detail Report 44Directory Information Reports 43DNIS 136DNIS Detail Report 43DNIS Summary Report 43Duration Summary Graph 44Duration Summary Graph by Call Type 44

EE-mail reports 40Employee Database 33Employee Directory Report 43Employee Editor 33

access 33Entity Detail Report 43, 142Entity Roll-up Report 142Entity Roll-up Summary Reports 43Entity Summary Graphs 43Entity Summary Report 142Entity Surcharge Detail Report 44Entity Surcharge Roll-up Summary

Reports 45Entity Surcharge Summary Report 44Exception Chronological Report 43Exception Chronological Surcharge

Report 44Export data 39export utility 127Extension Detail Report 43Extension Diagnostic Report 45, 159Extension Roll-up Report 159Extension Roll-up Summary Reports 43Extension Summary Report 158External Parties Database 46External Party Directory Report 43External Party Summary Report 44

FFilter Definitions 41Filters and configurations 160Frequency Reports 43

Frequency/Digits reports 159Frequently Called Location Report 159Frequently Called Numbers Report 44

, 159

GGeneral Cost Allocation System

bill types 175creating billing records 179overview 14

HHelp 15hierarchy 24Hold Time by Extension Report 159Hold Time by Time of Day Report 159Hold Time Detail Report 44Hold Time Summary Graph 44hospitality and campus billing in

Telecom Billing System 117HTML format output 40

IImport data 39import utility 122installation of rate tables and location

books 71Internet Information Server (IIS) 161

LLevel reports 159list of the telemanagement applications 13List Trunk and Member (LTM) report 78Location Books 48Location Summary Report 44Long Distance Service Definition 95

MMask characters 177MDR 2000

connection to switch 62customization strings 67security precautions 62

MDR2000/2000e buffer boxes 137

Oonline Help 15


NN43050-602 03.04 28 May 2009


.

249

Organization Roll-up Summary Graphs 43Organizational Hierarchy Database 24Organizational Hierarchy Editor 24

access 25add node 26delete node 28employee selector 28employee sort 32organization levels 26

overlay 15 60overlay 16 61overview of Telecom Billing System

Web Reporting main Webinterface 158

PPurge Call Database 39

RRate tables 49Refresh Site List 143report filters 160reports 158reports available in Telecom Billing

System 39Restore Call Database 38Rich Text Format (RTF) output 40Ring Time Analysis Report 44Ring Time by Extension Report 159Ring Time by Time of Day Report 159Ring Time Report 44Role/Project Directory Report 43Roles/Projects Database 47roll-up summaries 159

Sscreen output 40Script Configuration initialization file 22Server configuration 161server PC 160Setup utility 161Snapshot format output 40Surcharge Reports 44Synchronize Corporate Data 141System Configuration Report 45system requirements 160

TTandem Tie Summary Report 45Telecom Billing System

call detail information 18configuring 59data collection 50hospitality and campus billing 117interface 35operating procedures 106reporting options 39reports 39surcharges for hospitality billing 86System Alarm section 37System Monitor section 37System Tasks section 36taxes 49telephone configuration 78

Telecom Billing System Web Reportingfeatures 158Filters page 160how to access 160list of reports 158overview 14

Telecom Billing System Web Reports 158telemanagement applications

description of 14list of 13

Telephone Configuration Database 47, 79

Telephone Configuration Report 45telephone configuration table 166Traffic Reports 45Trunk Detail Report 45Trunk Diagnostic Report 45, 159Trunk Graph 45Trunk Group Utilization Graphs 45Trunk Group Utilization Report 159Trunk reports 159Trunk Usage Reports 45Trunk Utilization Report 45, 159

UUnanswered Call Detail Report 44Unanswered Calls Summary Report 44Undisbursed Verification Report 44using Telecom Billing System Web

Reporting 160utilities

export 127import 122


NN43050-602 03.04 28 May 2009


.

250

Utility Tools Reports 45

Vviewing Web reports 166

WWeb Reports 158


NN43050-602 03.04 28 May 2009


.

Nortel Communication Server 1000

Telephony Manager 4.0 Telemanagement ApplicationsFundamentalsRelease: 6.0Publication: NN43050-602Document revision: 03.04Document release date: 28 May 2009


While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed to in writingNORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF ANY KIND, EITHER EXPRESSOR IMPLIED. The information and/or products described in this document are subject to change without notice.

Nortel, Nortel Networks, the Nortel logo, and the Globemark are trademarks of Nortel Networks.

All other trademarks are the property of their respective owners.

To provide feedback or to report a problem in this document, go to www.nortel.com/documentfeedback.

www.nortel.com

Telephony Manager-Full 100102894

Documents

Transcript of Telephony Manager-Full 100102894