System & Applications Manual

SysManager 410

Contents

1. 2.

INTRODUCTION ........................................................................................................ 2 SYSTEM ARCHITECTURE......................................................................................... 3 2.1 2.2 Hardware .......................................................................................................... 3 Software............................................................................................................ 3

3.

THE SYSMANAGER PLATFORM ............................................................................... 5 3.1 3.2 3.3 Connection Manager.......................................................................................... 5 Licence Manager ............................................................................................... 6 Login Module..................................................................................................... 7

4.

MODULES ................................................................................................................. 8 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 4.9 4.10 The MAC-Manager (MM).................................................................................... 8 The Call Reporting Module (CRM) .................................................................... 10 The Operational Maintenance Module (OM)....................................................... 15 The Announcement Management Module (AMM)............................................... 16 The Directory Services Module (DSM)............................................................... 16 The Fault Report Module (FRM)........................................................................ 18 The DECT Management Module (DMM)............................................................ 19 The External Application Interface Module (EAI) ................................................ 20 The Data Distribution Module (DDM)................................................................. 21 The ISPBX File Management module (IFM)....................................................... 24

5. 6.

MULTI-USER SUPPORT .......................................................................................... 25 SMART CARD TELEPHONY.................................................................................... 30 6.1 6.2 6.3 6.4 6.5 Budget Dialling ................................................................................................ 31 Personal Number............................................................................................. 31 Smart card properties....................................................................................... 31 Security........................................................................................................... 32 EAI interface.................................................................................................... 33

7. 8. 9.

DIRECTORY DISTRIBUTION SERVICE.................................................................... 34 OVERVIEW OF THE SYSMANAGER PORTFOLIO.................................................... 35 EXAMPLES OF CONFIGURATIONS......................................................................... 36

10. LIST OF USED ABBREVIATIONS ............................................................................ 39

SysManager 410

System & Applications Manual

1.

Introduction

The SysManager is a powerful set of PC-based management applications that run on Windows 2000 - Professional or Windows NT. The SysManager includes various optional applications, called modules. Easy-to-use modules are available for operational maintenance, call accounting, announcement management, fault management and daily management of a telephone network. The SysManager requires an ISPBX with system software 805 or higher. This book is a guide to the: modules available with release 4.5. (unless mentioned otherwise); features available; possible requirements; possible limitations or boundaries. This book is not: a detailed technical description of all aspects of SysManager; a detailed installation manual. This book should be read by those who: are involved with the sales of a SysManager system; want to have an impression of the SysManager product. Disclaimer: No rights can be derived from this document. This document is subject to changes because we continue to develop and improve our products. For more information on required materials, please refer to the SalesBUILDER. The SalesBUILDER is a Windows application that assists in specifying an offered configuration. It helps you to configure new systems, system expansions or upgrades, spares and PC applications (like the SysManager). For presentations and demonstrations purposes to (potential) customers, a demo CD-ROM is made available. This CD can be ordered from Hoorn.

System & Applications Manual

SysManager 410

2. 2.1

System Architecture Hardware

SysManager 410 is basically a software package, running on a Windows 2000 - Professional or NT PC. A suitable PC available at the customer can be used; i.e., it is not always necessary for the customer to buy a new PC. The IPSC-Hoorn also offers an installation service whereby the SysManager 410 can be installed and delivered together with the standard PC. The minimum system requirements: Pentium 233 MHz system (Pentium II 350 MHz recommended) ; including keyboard, SVGA monitor, high density diskette drive, CD-ROM drive, mouse etc.; Operating system Microsoft Windows 2000 - Professional or NT release 4 or higher; 64 Mbytes of memory (128 when Windows NT is used); In case of a server, additional 128 Mb is recommended. 4.3 Gbyte Hard-disk (6.4 recommended); 2 serial ports; 1 parallel port. It is important to follow the minimum specifications, to prevent that hardware needs to be upgraded when migrating to a new release and/or expanding the configuration. The SysManager package may also include one or more of the following hardware components, if not already supplied: 8 multi-port card PCI-FAST 8 (Chase) or Smartio C168H/PCI (Moxa); Dongle (for licensing); Hayes compatible modem(s) (PSTN or ISDN), for example: US Robotics Sportster; Buffer box for Full-Detailed Call Recording and Toll Ticketing (FDCR/TT) records; ComboX (for alarm and call accounting buffering in one box); RadlinX box (for connection via a Local Area network and in combination with a ComboX). Note: SysManager can be used in NT domains or NT workgroups, but not mixed. 2.2 Software

SysManager offers the following software: 1. SysManager General The SysManager General software creates the SysManager program group on the desktop and in the Start menu, and installs software that is used by several other SysManager modules. 2. Announcement Management Module This is used to manage announcements stored on Integrated Announcement Server (IAS/IASA) boards used by the VoiceManager 110 and VoiceManager 150. 3. Call Reporting Module This is used to collect FDCR/TT call record data from the ISPBX, and to generate reports based on the data collected. 4. Connection Manager This is used to specify details of connections and set up connections between PCs and ISPBXs. The specified details are used by the various modules to establish a connection with the ISPBX. 5. Data Distribution Module This module is used to keep the joined databases of the SysManager modules synchronized. 6. DECT Manager Module This module is used to subscribe DECT sets. 7. Directory Service Module This module only has a user interface for set-up purposes like the configuration of the Terminal Service Display. The Directory Services Module is an interface between the

SysManager 410

System & Applications Manual

8.

9.

10. 11. 12. 13.

14.

15.

PhoneWare Database (corporate phone directory) and SysManager. This enables integration of the SOPHO SuperVisor 60E and the SysManager. PhoneWare Phonebook Manager This software application is part of the DSM. It allows changes (add, change and delete) of name related data in the DSM name database. External Application Interface Module This module is used to give external applications access to ISPBX and SysManager related services. Fault Reporting Module This module is used to collect alarm information from the ISPBX and to generate reports based on the data collected. ISPBX File Management Module This module is used to extend ISPBXs with an external back-up device. Licence Manager This is used to load and view the licences for the SysManager modules. Login Module This module is used by the system administrator to control access to most modules. MAC-Manager This is used for daily management of a telecommunication network, including, for example, moving and adding extensions. MML Files The MML Files are used in the Operational Maintenance Module and MAC-Manager to convert coded OM in readable text. MML help files on MML are enclosed. Operational Maintenance Module This is used to perform operational maintenance by entering OM commands.

The SysManager is available in the following languages: Brazilian Portuguese Danish Dutch English French German Italian Spanish Swedish The following applications are only available in English: Fault Reporting Module; External Application Interface Module; ISPBX File Management Module; Directory Service Module; Connection Manager Module.

System & Applications Manual

SysManager 410

3.

The SysManager Platform

The following modules of the SysManager application range are always necessary: the Connection Manager (CM), the Licence Manager (LM) and the Login Module (LIM). Together they form the basis of the SysManager. When a user starts an application, the application 'asks' the LM if the application is allowed (e.g. if the customer has a licence for the MACManager) and how many ISPBXs the application is allowed to manage (e.g. the MACManager is allowed to manage 3 iS3010 systems and 2 iS3030 systems in a network). With the LIM customers can manage user access to the applications. Collectively the CM, LM and LIM are known as the SysManager platform. The most important aspects about the SysManager platform: The platform is open, in the sense that not only Philips itself, but also third parties are able to develop office- and management applications that can fit. An open interface (SNMP) is provided for fault management to open platforms like HP OpenView. The platform is scale-able, meaning that SysManager provides its services for small to large systems, single-, multi-site and networks, single- and multi-user. The SysManager 4.x software applications are 32 bit applications, designed for Windows 2000 - Professional and Windows NT on standard PC hardware. SysManager is based on standard LAN/TCP-IP technology. 3.1 Connection Manager

The Connection Manager connects SysManager applications like the MAC-Manager and Call Reporting Module with their counter applications in the ISPBX(s), hiding all physical and lower level protocol details. The Connection Manager does this by offering a COM based interface to the applications. The applications ask for a connection to a specific ISPBX for a certain type of function. The Connection Manager knows the details of connections and set-up connections between the PC and ISPBXs. This information is used by the other modules of the SysManager to establish a connection with the ISPBX. The Connection Manager also co-operates with the Licence Manager, to check whether the application is allowed to set-up the requested connection. TCP/IP has to be installed on the PC for the Connection Manager. The Connection Manager consists of four foreground applications and three background applications. The following foreground applications can be found in the Configurators group in the SysManager program group: 1. CM Database Configurator; used to: store network information; configure and store the connections between SysManager applications and destinations in the ISPBX network; print all properties of a connection, ComboX, SPB, or BIM. The CM Database Configurator can be completely wizard-driven. Although you must use the wizard to configure all connections, you can specify items and add them to the database while working outside the wizard. By using the wizard, you ensure that no part of the procedure for creating a connection is forgotten. SysManager can automatically select the fastest modem available when it connects a SysManager module to an ISPBX. You create an ordered list of all modems potentially available for any connection, with the preferred (normally fastest) modem at the top of the list, the slowest last. The CM Database Connection Wizard guides you through this task. When configuring a connection which includes a ComboX it is no longer necessary for the box to be physically connected to the network during configuration, since you can download the configuration settings later. The CM Database Configurator uses the familiar Windows GUI. It uses one main screen divided into two panes. Each pane offers a contrasting view of the CM Database: The left pane displays database items in a structured hierarchy. You can often double-click on parent icons to reveal the items they contain. The right pane generally shows details of any item you select in the left pane.

SysManager 410

System & Applications Manual

2. 3.

4.

Together, the two panes comprise an intuitive environment for exploring the contents ISPBXs, ports, add-on boxes and configured connections in the CM Database. CM Monitor; used to monitor the data sent over a connection. This can be used for trouble shooting purposes, for instance when a connection fails. CM Modem Configurator; only used for non-standard modems. In the Modem Configurator information is entered about the modem types, and which modem type is used on which COM Port of the SysManager PC. ISPBX Destination Activator; detects whether or not the destinations configured in the Connection Manager database have a valid licence available for them to run.

The three Connection Manager background applications run automatically when the PC is started. The associated icons are visible in the Windows icon tray, at the bottom right of the screen: 1. CM Protocol Server; sets up the connection to transfer data between the application and ISPBX, ensuring the correct protocol is used. In event of a problem. 2. CM Broker; selects the best possible protocol server and COM port for setting up the connection. The Broker also registers the call connections and disconnections in a logfile. 3. Process Guard; ensures that the following SysManager background functions are automatically (re)started when the PC is switched on: CM Broker; CM Protocol Server; External Application Interface Module; Directory Services Module. Call back Call back is used for remote service and security purposes. The general principle is to set up a modem connection to a remote device, terminate this connection and let the remote device set up a new connection back to the originating party using a pre-configured phone number. Call back is optional. Users specify in the Connection Manager whether or not to use a call back connection. The call back is always initiated by the SysManager and it expects to be called back. Call back is used by: 1. ISPBXs; 2. BIMs and SPBs (as functionality on the BIM). 3. TOPS box. These devices have to be configured explicitly for using call back. Call back can be used for the following applications: MAC-Manager, Call Reporting Module and Operational Maintenance Module. The number of call back destinations is 1. Call back support is only for remote modem connections. Just as normal (unidirectional) connections, multiple modems can be assigned to a call back modem pool in the Connection Manager Database Configurator. However, this requires a so called group arrangement of the modems. There is no support of dial-in. 3.2 Licence Manager

The Licence Manager offers scale-ability to a specific required configuration and provides easy means to modify and expand the configuration later. Therefore the Licence Manager provides system scale-ability in four dimensions (all of them per module): 1. The number of ISPBX systems per type; 2. Usage of module allowed; 3. Available functionality of the module; 4. Single/multi-user in terms of allowed number of users. Dimensions 1 and 3 are not applicable for all modules. With the Licence Manager, systems can easily be changed later, when customers want to expand functionality, number of users etc. This can be done remotely without on-site assistance. The mechanism is based on an encrypted licence file for each SysManager

System & Applications Manual

SysManager 410

system. This file contains licences for the required functionality and is loaded into the customers system. It can only be activated in combination with a dongle. A dongle is a connector that contains a unique identification. It must be attached to the parallel port of the PC. The dongle is transparent so a printer can also be attached to the parallel port. Note: The dongle should be attached on a different parallel port if the connected printer is occasionally out of paper or in error. This is because in those situations, the printer port is blocked. A licence file is always generated for a specific dongle and can therefore only be activated in a customer system containing this specific dongle. The dongle does not have to be replaced in case of upgrades. The encrypted licence files are produced by the so-called Licence Generator and can be (remotely) loaded (with pcANYWHERE) in the customer system. In this way upgrades (add-on licences) are much easier to handle. The time that a generated licence is valid is specified per module and can be permanent or temporary (try&buy). For Windows 2000 - Professional the USB dongle is supported. The following system licences can be generated for commercial purposes: Initial (new) licence normally generated in the IPSC-Hoorn after ordering a system; A temporary licence (try&buy) per application, having a 3 month lifetime allowing 1 ISPBX per type; Upgrade licence for expansion/upgrading purposes, replacing an initial or previous upgrade licence and containing both the existing and the new licences. The following system licences can be generated for maintenance purposes; Replacement licence for an existing system where a new dongle has to be used, e.g. in case the current dongle is faulty; Regenerated licence for the current dongle, for example because the licence file was lost; Service licence with licence for all applications, having a 1 week lifetime allowing 1 ISPBX per type; Installation tool licence with a licence for a MAC-Manager (used to install a SOPHO ISPBX), having a 1 month lifetime allowing 1 ISPBX per type. Before the Licence Manager can be used, the dongle must be connected to the parallel port of the PC on which the Licence Manager runs. 3.3 Login Module

The Login Module (LIM) is primarily meant for customers who want to manage user access to Philips modules. Thereby different languages per module can be specified for the users. An administrator can add users and assign a password, a personal language and the modules that the user is allowed to use. The administrator can choose out of the following login behaviour options: Login not required; Once per session; Users get the LIMs Login dialogue box the first time they try to open a module that can be governed by the Login Module. Provided that they open the application successfully, they are not presented with the Login dialogue box again, when they try to open other modules for which they have access permission. For each module. Users get the LIMs Login dialogue box every time they try to open a module that can be governed by the Login Module. The MAC-Manager, Call Reporting Module and Fault Reporting Module have their own login mechanism. For these modules, language selection is conform the Windows login, provided that the username that is used for Windows is the same as the username that is used for the Login Module. Users always have access to the Directory Service Module and the MML Files Module.

SysManager 410

System & Applications Manual

4. 4.1

Modules The MAC-Manager (MM)

The MAC-Manager module is the configuration management module for Moves, Adds and Changes. There are three basic steps in managing an ISPBX with the MAC-Manager: 1. Transferring data from the ISPBX to the MAC-Manager; 2. Making changes to the data off-line; 3. Sending changes from the MAC-Manager to the ISPBX. While it is not necessary to transfer data from the ISPBX each time the MAC-Manager is used, the data from the ISPBX should be updated periodically. Data transfer can be a lengthy process that is best done during non-working hours. The MAC-Manager can be programmed to update its ISPBX data automatically, on a regular basis. If an ISPBX network uses Free Numbering, then network management is very important. With the MAC-Manager you can easily move an extension number from one unit in the network to another, including Facility Class Marks, Display name etc. When a change is made this must be known throughout the network. The SysManager takes care that changes are administrated in all nodes of the network. If this would be done by hand, it would be very difficult to keep the system synchronised. The MAC-Manager consists of a number of main functional modules: Shell (PBXs/projects/scheduler/user definitions); Extension Moves&Changes; Group Moves&Changes; Trunk Moves&Changes; Operator Moves&Changes; DECT Subscriptions. Features Audit files;

Central directory dialling;

Data exchange;

Download of function keys;

Help; Inventory management; Logging; Multi unit;

An audit is a summarised view of the communication between the SysManager PC and the ISPBX. There are two types of audits that can be used for trouble shooting purposes (automatically created and saved): Communication audit; used to find information about the communication between the MAC-Manager and the ISPBX, i.e. the OM commands which are sent to the ISPBX in a project. Session audit; used to find information about the tasks which are performed in the MAC-Manager per user per session. Supports a directory for ErgoLines D330 and D340. The directory in the ISPBX contains internal names and numbers of the own ISPBX and of other ISPBXs in the same 'Central Directory Dialling domain'. This directory is located in each ISPBX of the CDD domain. The MACManager guarantees that each ISPBX of the CDD domain receives this directory. The data distribution functions also fills the CDD directory. The MAC-Manager database shares its data with the Call Reporting Module. Within SysManager, data only has to be input once because the modules exchange the relevant data. A range a SOPHO digital telephone sets can be managed from the MAC-Manager. Up to 256 function key templates can be easily defined and assigned to users telephones. Digitised layouts of the telephones provide easy overview. Context sensitive help. For extensions and trunks. Allows the system administrator to check all user actions in the MACManager. Manage multiple ISPBXs without the need for time consuming operational maintenance actions in every ISPBX. Centralised database

System & Applications Manual

SysManager 410

Multiple Create; Multiple Modify; Project structure;

Scheduler;

Security;

Smart card support;

Templating

User-friendly;

with configuration data of all ISPBXs in the network. Easy to create with one command a group of entities (like extensions) in one action. It can even be simplified more by using templating. For modification of groups of entities in one action, e.g. a call forwarding number can be changed for a complete department. Work that has been prepared in the MAC-Manager is organised in projects. Via projects it is easy to structure the outstanding work and spread it over a longer period. Used to schedule the execution of projects in the ISPBXs. The Scheduler executes immediate, at a certain time/date or as a recurrent process (e.g. to change the characteristics of the ISPBX every night). Access is provided with a user-id and a password. There are two main levels, System Administrator and user. The functionality for users can be determined by the system administrator as follows: Which ISPBX systems may be managed; Definition of the allowed way of using each MAC-Manager module (Extension-, Group-, Trunk- and Operator module) per function key (display only, modify, delete, create). Activity of users is logged and the system administrator can thus monitor all access to the MAC-Manager and see the activities that have been carried out. With the SmartCard Manager you can: program a new card; modify a card; delete records; block a lost or stolen card. Also see section Smart Card Telephony on page 30. Templating allows standardisation and simplification of the create activities in the MAC-Manager. The Templating facility provides a means for maintaining patterns for the use of creation actions, like extensions and groups within and across system components. With templating, the amount of user data entry and hence decision making is reduced. Perform all Moves, Adds, and Changes from a standard PC via a userfriendly interface. See also Free Numbering. All relevant and related data is presented in dedicated screens, e.g. for ISDN features, group arrangements, function key data of telephone sets and facility class marks. Input with easy selection of all relevant options by means of pulldown option lists. Easy and fast procedures for making queries and printing the results.

Optimised file transfer In the Connection Wizard is an option called "Optimise speed of MAC file transfer". If this is selected, then the Output Retrieve (OR) and Project Retrieve (PR) files are 'packed' after retrieve. This saves time in a 'Get Configuration' in the MAC Manager. Precondition is Call@Net 2.4 or higher, because 'ZIPFIL' is used to pack the files. It has no use to choose this option when an OM connection with character protocol is used, because that is already optimal (the fastest solution). However, if a bcs protocol port is needed anyway (because of switching services, for example), optimise speed of MACManager file transfer would be faster. Requirements The MAC-Manager requires a licence per SOPHO ISPBX. There is also a try&buy licence. The MAC-Manager also requires the MML-Files Module. When using the MAC-Manager in a CPU-ME/MT system, a Remote Back-up Unit (RBU) device must be assigned to the CPU-ME/MTs OM port, used by the MAC-Manager PC.

SysManager 410

System & Applications Manual

Limitations and Boundaries The MAC-Manager can manage an iSNet MAN distributed ISPBX configuration of up to 14 networked SOPHO ISPBXs. Note that this is not a limitation of the MAC-Manager but of the ISPBXs. In case of free numbering, an open numbering scheme is not supported. When the MAC-Manager is used in a distribution configuration, the department field is hidden. The CRM and DSM should be used to maintain the organisation structure. Central directory dialling is not supported for SSW 805. 4.2 The Call Reporting Module (CRM)

The Call Reporting Module consists of three applications: 1. Call Collector: an application that runs automatically and collects all Full-Detailed Call Recording or Toll Ticketing (FDCR/TT) data from the ISPBX(s) that it is connected to. Incoming data can be viewed in a graph; 2. Set-up: In Set-up, the user can enter specific ISPBX configuration data, information of the organisation and the pricing structure, to customise the CRM; 3. TABS: the application in which the system configuration is defined and reports are made. The power of the reporting application is to be found in the extent to which the detailed data contained within the call records can be turned into useful information, such as cost-related reports or traffic-related reports. This can be done as easily for a single ISPBX with less than 100 extensions, as for several sites and over several thousands of extensions. The system report library of the Call Reporting Module (CRM) includes standard reports. In general each report has a set of selection criteria that can be specified by means of the related dialog box. Although working with standard reports, extensive filtering capabilities let the user just select the specific information that is required in the report. As alternative for standard reports and filtering, the user can also completely specify customised reports, which can be put in a menu. Once a report is defined it can be given a specific name and added to the list of userdefined reports. The reports may be run individually on demand or they may be scheduled as a user-defined group of reports. Features Accounts;

Alert of no activity; Automatic report scheduling; Back up;

Carrier comparison (what-if); Cost centres;

Accounts are used to assign costs to certain callers or projects, regardless of which extension the call is made from. To use an account, the caller must dial a certain prefix which indicates the account, before making a call. The account codes use the cost centre codes as in the FDCR/TT record caused by cost-centre and PID dialling of the ISPBX. Note that accounts in CRM are called Cost Centres in the MAC-Manager. When an account is added in CRM, it is not known in the ISPBX. A new cost centre with the same no. as the account in CRM has to be defined in the MAC-Manager to really make it. If it is not entered in CRM, CRM will add the no. to the list of accounts when the no. is dialled and use no special mark-ups. An alert will be given if no call is collected within a defined period. With the scheduler it is possible to automatically generate reports for e.g. the monthly reporting of the costs to departments. Scheduled reports can be directed to file, to E-mail and to printer. CRM lets the user back up call data, extensions, trunks, accounts and authorisation data files to an archive. CRM saves each month records in a separate file in the archive. This data can also be retrieved to restore the database. It is possible to use the historical call data to compare the costs of a specific carrier with an alternative carrier to determine which is the most cost effective alternative. Cost centres are used to create a group of extensions from different parts of the organisation, to make a report. Extensions can be assigned to cost centres. This can be used when, for example, people from different departments work for the same project for several weeks and you want a report that shows the cost of calls for
this project.

10

System & Applications Manual

SysManager 410

Database aspects; Data manipulation;

Edit calls;

Export;

Extra charges (e.g. taxes, equipment costs);

E-mail; Filters;

Fonts; General purpose fields;

Graphing facility; Hierarchy;

History;

Standard database (FoxPro), accessible by standard applications. Different options of manipulating the data received, such as addressing a call to another extension by using an account or stripping and adding digits to the dialled number. Calls can be edited according to user rights. All users are allowed to edit the account code. Only designated users with specific rights can edit/add/delete a call. The CRM data can be easily accessed by other (external) applications. The options are ODBC access (e.g. used by standard report generator) and data export in standard used format (e.g. for use in Microsoft Excel). Call data can be exported in a flexible format (without headings) to a file for customised interface with other applications. Beside the actual costs of a call, extra charges can be assigned to an extension. For example in a hotel, when some profit must be made out of the telephone calls, or when equipment fee has to be charged to extensions, or the taxes. These charges are usually not found on the actual telephone bill, but can be added in CRM. Up to ten equipment items and their costs can be assigned to each extension and included in reports. Up to four different taxes can be added to the reports. Reports can be run and scheduled to run to e-mail addresses. Used to customise standard system reports, to help access segments of the FDCR/TT information. Filtering on both conditions and values is possible. Examples of usage: Report a certain part of the organisation; Report on trunk, accounts, authorisation, group or cost-centre; Reporting by number of calls, charge, units, duration; Display by amount or percentage; Selection of call type and call class; Distinct between business/private calls; Distinct between answered and unanswered calls. Lost calls per element in the hierarchy; Ring-time analyses on lost calls; Traffic overview on trunks in Erlang. The systems fonts and colours can be easily modified for customer customisation. Up to ten general fields can be defined for ISPBX data when setting up the ISPBX format. These fields are then used for either routing (select the service on which costing is calculated) and/or as filters in reports. For example a voice/data field can be added to an ISDN environment. While calls are collected, an on line graph (which changes every; minute) displays the amount of calls per minute. The Organisation Layout table specifies the companys organisational hierarchy (the various departments within the company), and the extensions allocated to each hierarchical level. The main purpose of the Organisation Layout is to enable reporting by the desired organisational level, for better management of the companys telephone resources. In CRM, every organisation comprises up to eight hierarchical levels where the last level is always the extension level. The names of the levels and the maximum number of levels that can be used are defined when installing CRM. The default number of levels is five. Each hierarchical level is assigned a name, such as Organisation, Division, Department or Subdivision. Within an IMP telephone network, it is possible to collect call records from multiple sites under one database. In this way a virtual ninth organisation level (all sites) is created. When changing the Hierarchy or moving extensions from one Cost Centre to another, CRM saves the changes. When you run any

11

SysManager 410

System & Applications Manual

Import;

Monitors for call collector and exceptions;

Multi-site reporting; Multi-user; Recalculation; Security levels;

Standard reports;

Tariff structure with multi tariff time zones;

Organisation or Cost Centre Report, the extensions calls are reported according to the dates and the corresponding organisation location. Extracting annual reports is possible. Costing tables can be imported with the use of VLISTS. Every service provider which is used by a site will have its own costing tables. Also, in a multi-site telephone network, each site in the system will have its own set of costing tables. Call data can be exported to external files. The format of these files can be defined in CRM. For example DOS Comma Delimited files. Other applications, like Microsoft Excel, can be used to generate reports with the exported data. Call record traffic is being monitored at all times and can be viewed through the On-line Call Monitor. The contents can be defined by a number of selection possibilities (filters). Different views can be created and assigned to the Views menu, for fast access of frequently required data (e.g. a summary of the long distance calls made in a specified time range). The defined Views display either on-line calls or calls from the database. This means that the user fully automatically gets real-time information about the occurrence of a specific type of call (e.g. calls more expensive than $20,-, calls to certain destinations etc.). CRM can combine the records of a number of sites into one report for the complete organisation. Multiple users can have access via a LAN to different reports according to specified rights. The costs of calls can be recalculated according to changes made to the costing tables. Access is provided with a user-id and a password. The access level to data and functionality can be defined per user. Four levels are available: none, low, medium and high. These levels have to be defined for each of the main functionality groups: Report level, for referencing reports; Data access level, for gaining access to the Call Reporting Module data; Maintenance level, for using the maintenance facilities; Set-up level, for accessing set-up routines. Activity of all actions that influence the CRM is logged. Therefore all user log-in/outs are logged and every change to the settings of the CRM. Running queries is not logged. CRM provides different types of reports, which serve as the basis for defining all reports. They can be used in different ways: by selecting different report levels, having all details or a summary, having a graphical presentation and by using filters. See the overview of standard reports further on. With the use of costing tables (VLISTs), the actual costs of outgoing calls can be calculated. Multiple call tariffs can be defined for day/week time zones.

Overview of standard reports in the Call Reporting Module: Report tittle Annual organisation history; Call class breakdown Explanation Summarises call information per month over the past year. Lists outgoing calls summary information for an organisational level according to the area or zone dialled. Defines detailed or summary reports according to: organisational level, account, authorisation, trunk, cost centre.
Graph/ Report Report Graph/ Report Graph/ Report

Call details/summary

12

System & Applications Manual

SysManager 410

Report tittle Call type breakdown Destination distribution

Explanation Lists call summary information for an organisational level according to the call type (outgoing, internal etc.). Summarises the number of calls and cost according to the selected call category (local, area, long distance, international) and the first digits of the dialled number within the selected category. Provides a detailed list of calls to selected destination categories (local, area, long distance, international) whose cost, duration and/or units were above a minimum value and summarises all the other calls, sorted by the selected organisation level. Provides a list of all outgoing calls in ascending numerical order, and the extensions from which they were placed. Summarises call information per month or per year. Lists the top 15 most frequently dialled numbers. Lists the top 15 in each of the following categories: extensions with the most calls, with the longest calls, with the highest charge, with the most units (where available). Lists phone calls, sorted by extension, that have not been charged to an account. Lists accounts with no call activity during a specified time range. Lists extensions with no call activity during a specified time range. Lists trunks with no call activity during a specified time range. A list of company extensions sorted one of four ways: by name, by extension number, by both department and extension name (the organisation level is the level above the extension which depends on systems set-up), by both department and extension number. Summarises for each of the selected organisation levels the number of calls, duration, units and monthly charge. It allows to compare monthly telephone usage between organisation levels and between entities within the selected level. Lists the no. of incoming calls; total maximum and average ring times, total and average duration on an hour-by-hour basis. Lists all incoming calls, grouped according to the length of time (short, medium and long time period) that elapsed before they were answered or before terminated by originator. Compares the cost of calls for each carrier (and costing tables) presented for each trunk. It enables to make comparisons among different carriers using actual telephone usage data. Summarises for each trunk the yearly call information. Summarises for each selected trunk the number of calls, duration, units, and monthly charge. It allows to compare monthly telephone usage between trunks Provides detailed or summary information about calls that have been placed during defined business hours. Overview of total, average and % of use for trunks and for organisation entities.

Graph/ Report Graph/ Report Report

Details and summary combined

Report

Dialled number summary History Hit parade by dialled no. Hit parade by extension

Report

Report Report Report

Missing accounts No traffic for accounts No traffic for extensions No traffic for trunks Organisation directory (telephone directory)

Report Report Report Report Report

Organisation history annual

Graph/ Report

Ring time by hour

Graph/ Report Graph/ Report

Ring-time statistics

Service comparison by trunk

Report

Trunk history Trunk trends

Report Report

Usage details/summary

Report

13

SysManager 410

System & Applications Manual

Report tittle Volume (call-) by hour

Explanation Summarises the number of calls , their total duration, average duration and total charge per 15, 30 or 60 minutes (depending on the selected resolution). It is used to analyse busy and light business hours. Provides for each selected organisation entity, a usage breakdown summary for each day, over a 24-hour period. Provides traffic measurements for trunks in Erlang. Lists unnamed accounts that have been accessed.

Graph/ Report Report

Weekly usage

Report

Wrong accounts

Report

Additional lost call reports that are always available as User-Defined Reports: Report tittle Company ring time lost calls; Explanation Shows the percentage of each of the following categories: answered calls, calls that were handled by the operator and lost calls. It enables you to understand the extent to which calls are lost by your system. Shows at which time of day the highest numbers of calls were lost. Which part of the organisation (division/department/section, etc.) has the highest number of lost calls. Shows the time that it took callers to hang-up the phone without being answered. It displays the percentages of calls that were lost in less than the specified ring time.
Graph/ Report Graph/ Report

Department lost calls volume by hour; Lost calls by department; Ring time lost calls;

Report Graph/ Report Graph/ Report

Requirements The Call Reporting Module needs a licence for each ISPBX. There are different types of licence: CRM This is the standard multi-site Call Reporting application that should default be used in SysManager configurations. The CRM uses all the possibilities that FDCR/TT generation offers, such as lost call analysis, call statistics and so on. It has dedicated licences depending on the iS3000 type. CRM alike CRM-alike works with older SOPHO-S and iS3000 software releases. It has multi-site capabilities with dedicated licences depending on the iS3000 type. Note that the CRMalike cannot be used in combination with other SysManager applications, such as the MAC-Manager. The CRM-alike uses either the standard toll-ticket format or FDCR/TT, depending on the iS3000 model it is connected to. Note that, depending on the input format, not all call analysis functions are available. The CRM-alike licence is also known as the Pre 805 ISPBX type licence. CRM background This is a version of CRM that is used in combination with the External Application Interface (EAI). It only collects and transports toll ticket information from the iS3000 system(s) to an external front office system, such as used in hotels. Only a limited user interface for configuration aspects is offered. It has dedicated licences depending on the iS3000 type. Try&buy CRM buffers A buffer device may be required. This can be a TOPS box, a ComboX, the BIM in case of an iS3070/3090 or in case of a CPU3000 the ISPBX's local disk (LBU). To save time, the FDCR file on the LBU is 'packed' before transfer; i.e. ZIPFIL is used. It is also possible to use the old Service Plus Box. Precondition is Call@Net 2.4 or higher. A buffer device is used to buffer the FDCR/TT records produced by an ISPBX. Buffering is necessary when the ISPBX runs on software older than SSW805.24.

14

System & Applications Manual

SysManager 410

Use the Call Reporting Module to access the buffer device, at regular intervals, to process the FDCR/TT records. Limitations and Boundaries If the EAI module is installed, then there is only 1 FDCR stream supported. TABS Setup automatically detects the presence of the EAI module and makes sure that only 1 FDCR stream can be defined. In a FIN the FDCR records for that complete FIN can be collected from one unit. Only one single non-buffered direct FDCR connection is needed towards one of the units of the FIN. The FDCR records from all units can now be collected via that connection. The mechanism to collect the calls properly, is automatically activated if a Direct connection to ISPBX without buffer is defined to one of the units of the FIN with purpose FDCR (character or bcs protocol). This mechanism (FDCR sequencer) will keep the Standard and Accounting records (as generated for outgoing calls) together. The restriction is that it only works for a direct connection without buffering. The total traffic for which call records are generated must not exceed 8 call records per second for the complete FIN. It is advised to activate FDCR only for outgoing (toll-ticketing) calls in the FIN. The restriction of 8 call records per second then comes down to 4 outgoing calls per second. For Hospitality configurations (Basic Hospitality and Full Hospitality) where you have one single connection to a destination (FIN), this restriction is acceptable. Note: an equipment licence is still needed for EACH unit in the FIN! In the ISPBX must be configured that all FDCR records are sent to one output device. In the Connection Manager only 1 FDCR connection must be defined. Also in CRM only one site has to be configured. Updates made on a CRM client in a multi-user SysManager are added in the CRM database, but not distributed to the DDM. Only updates done on the CRM server are distributed. The CRM puts a high demand on the network, since it requires a lot of data transfers. Therefore the number of TABS clients is limited to 3. To be able to use the iS3000's local disk as buffer device, the ISPBX needs Call@Net 2.4 or higher. 4.3 The Operational Maintenance Module (OM)

The Operational Maintenance module enables the user to communicate with the ISPBX (through the physical V.24/OM connection) in its Man-Machine Language (MML). This is the standardised language that allows the system manager/administrator or the engineer to manage system resources, such as assigning boards, changing service conditions, etc. The OM module is only intended for special actions in the ISPBX that cannot be dealt with by means of the MAC-Manager. If the OM module is used for actions that are normally intended for the MAC-Manager, then a synchronisation between the ISPBX and the MAC-Manager database is required. The connection interface to the ISPBX(s) is being handled by the Connection Manager module. Features Help;

History;

Log files;

Script files;

Two types of Help are available, general OM module usage guide and OM command descriptions (MML help). Users may access both forms. Context sensitive help is available. Each time a command is executed (via the command prompt), the command is saved in a command history list (default size of the history buffer is 50 commands). After a command is recalled from the history list, it can be edited before it is executed. Logging of OM sessions. Log files are read-only. Log files can be created always or only on demand. There is an option to automatically create a new log file weekly or monthly. With script files a series of OM commands can be executed from an open text file (normally not larger than 64 Kbytes). The commands in the file are sent to the ISPBX. Script files can be edited. Making coded OM MML commands and responses human readable.

User friendly;

15

SysManager 410

System & Applications Manual

Requirements This module requires a licence. There is also a try&buy licence. The OM module uses information contained in the so-called "MML files". These are separately available (part of the iS3000 system software deliverables) and are installed separately from the SysManager 410. 4.4 The Announcement Management Module (AMM)

The Announcement Management Module provides an interface to the user for managing an Integrated Announcement Server (IAS) board. There are two versions of the IAS; VoiceManager 110 (IASA) and VoiceManager 150 (IAS). The AMM recognises which application is installed on the iS3000 and adjusts its services accordingly. Features Announcement management;

Back up; Configuration; Reports;

Controls the recording, playing and erasing announcements. Announcements are voice messages in a digital form. They can be used for personal announcements, wake-up service, music on hold, music on camp on busy, trunk announcements and information lines. Backup and restore announcements to/from PC. Configure individual ports to play selected announcements prior to terminating or transferring the call. Generate reports, listing announcements and their attributes including usage statistics if required, on paper and/or in a text file. Generate reports on alarm events and port settings.

Requirements This module requires a licence. There is also a try&buy licence. Limitations and Boundaries The AMM does not support a database of announcement servers that can be dialled, nor does it select the communications port or baud rate; these are handled by the SysManagers Connection Management Module. The AMM cannot be used in combination with the ACD manager (CallManager). The existing IAS/A Manager product remains available for this purpose. There are no factory configurable settings via the defaults.exe tool (e.g. copyright message, colours, .LST file). The .LST file (containing a list of all announcements on the announcement server) is not stored upon exiting the program. 4.5 The Directory Services Module (DSM)

The Directory Services Module is part of a series of SOPHO Directory Services. These consist of a number of components based on the PhoneWare directory server package and can be inter-connected via a LAN. The following list provides an overview of the components: SuperVisor 60E (SV60E): This PC-based operator desk uses the PhoneWare directory. SV60E can be used file-shared, distributed and client/server with the SQL server package. SQL Directory Server: A server that can be added for client/server operation of the directory components. Directory Service Module: A module in SysManager with two main functions, expansion of Calling Name and Number Display features with DPNSS and ISDN numbers, and linking system management modules to directory services, for example for messaging and LoB (Lines of Business) applications. The ISPBX feature Calling Name and Number Display provides the information on display telephones. Another feature Terminal Service Display, offers more information of the calling party. This is mainly used in hotels at dedicated service points, such as room service (guest information). The DSM can be used in different LAN configurations: 1. Stand-alone; 2. File update; There is one master system from which the directory updates are done to the other systems (e.g. SV60E consoles) at pre-defined times, for example once a day. Each

16

System & Applications Manual

SysManager 410

3.

4.

system has its own database and can work also when the LAN is down. No performance limitations during use. File sharing; All systems share the same file, which is located on the master system. So the directory is always up to date. Drawback: when the LAN is unavailable, the other systems do not have directory access. File sharing is loading-sensitive so the amount of systems is limited (typical 3 active PhoneWare applications). SQL client/server. For large directories or many systems, a separate SQL server is used.

Features Directory Distribution; External Application Interface; CNND;

Directory distribution to SV60E for consistent name information. Directory functions to external applications, e.g. in hotels. The ISPBX offers Central Name and Number Directory (CNND). The DSM offers the external PhoneWare database. This database provides name information when: no name is found in the internal database of the ISPBX; it concerns an external number; the internal database of the ISPBX is not used at all. Automatically Entered Messages and Manually Entered Messages between telephone users and SV60E operators. Display of calling party information on the display of dedicated telephone sets (specified by means of a facility class mark). The DSM administration tool is used to specify how and which items are to be displayed.

Messaging; Terminal Service Display;

About CNND Although often referred to as 'Calling Name and Number Display', the official commercial term for CNND is 'Central Name and Number Directory'. CNND is a service provided by the ISPBX. It provides information about the calling/called party on digital telephone sets with a display, on SuperVisor 25/35 consoles and on DECT sets. When the information is not available in the ISPBX's internal database, an external name database is used. This is the PhoneWare database which is consulted by the DSM. To distinguish CNND for names found in the ISPBX internal database, from names found in the external database, in this manual we use the terms Internal-CNND (I-CNND) and External-CNND (E-CNND). The decision to make use of the external database is done with a dedicated system option in the iS3000 ISPBX (option 999). The iS3000 database contains internal numbers; i.e. all DNRs, with associated names, that are connected to the iS3000 (node). The database is filled by means of OM procedures. The best way to attach a name to a DNR is to make use of the SysManager. The DSM database contains besides internal also external and network numbers. For regular external contacts, the ISDN CLI can be stored in the DSM. This enables the display of names of for example regular customers. Translation of ISDN or DPNSS numbers (CLI) depends on the status of a route option in the general route characteristics of the particular route. The database is filled and maintained by means of the Phonebook Manager (or the Property Management System). The DSM administration tool is used to specify how and which items are to be displayed in case of E-CNND. The DSM database may be large and the link to the iS3000 ISPBX has limited performance. Roughly the DSM is capable of approximately two number-to-name translations per second. To prevent unacceptable waiting times, a timer (default set to one second, maximum value 6 seconds) guards the external name search. When this timer expires and no name is found, the call is set through to the destination terminal without the name. The iS3000 ISPBX may be part of a network. In case of an IMP network, 1 connection to the DSM is sufficient to do the number-to-name

17

SysManager 410

System & Applications Manual

translations for the complete network. In case of a DPNSS network, each individual DPNSS node must have its own DSM module. The maximum message length is restricted by the ISPBX to 20 characters. E-CNND layout example: Initials (1 char), Surname (13), Extension (4). (1+13+4+2 spaces = 20) Notes: 1) Name changes made in the MAC-Manager are automatically (when the project is sent) sent to the I-CNND database. See also the description of the "one time data entry" feature in chapter 4.9. 2) If immediate updates of CNND display information is required, it is recommended to use ECNND. Otherwise it takes about 1 minute before the updates are distributed, or, if they are entered in the MAC, when the project is sent. Requirements This module requires a licence. There is also a try&buy licence. If the database has more than 5000 entries or if also a SuperVisor 60E is used, a separate SQL server may be needed. CNND is a licensed function (software licence 20). Per iS3000 node a dedicated licence is required. Limitations and Boundaries In a multi-node system based on DPNSS/Q-Sig, each node requires a connection to SysManager (direct, bcs protocol with switching services). Organisation names must be unique for all hierarchy levels for all sites. The DSM stores the hierarchy in the Hierarchy 1 tab of the Phonebook. The SV60E's secondary search feature uses the hierarchy in the GroupX tab of the Phonebook. Only changes made in Phonebook Hierarchy1 tab are distributed. 4.6 The Fault Report Module (FRM)

With the Fault Reporting Module, the user can centrally manage the ISPBX alarms. The FRM sets up a connection through the ComboX that is directly connected to each ISPBX. It works through direct communication or via a modem. The FRM supports the Simple Network Management Protocol (SNMP) link to enable for example graphical network presentation and/or integration of the network management for switching, data and datacom, and transmission equipment. The link is between SysManager and the rest of the management equipment. More than 1 link is possible. By using a RadlinX box, it is possible to connect to an ISPBX via the local area network. The RadlinX box gets an IP address and uses virtual COM ports to define connections to the ISPBX destination. For connection to an ISPBX for fault reporting, at least 3 virtual COM ports are needed on the SysManager server: 1. Incoming FRM calls; 2. Outgoing FRM calls; 3. Operational Maintenance. While the TCP port is in use for Incoming/Outgoing FRM or Operational Maintenance, it cannot be used for other SysManager applications. Benefits of the RadlinX box: : more economical than modem connections; It creates up to 256 Hayes-compatible software modems. : faster by Internet instead of the phone line; Date rates move up to the speed of the Internet connection. : connects to any network-enabled server application on the Internet or a TCP/IP local area network. The RadlinX box is connected to a COM port using a null modem cable. The Network Add-On Kit wizard helps the user to configure a connection between SysManager and an ISPBX destination. The Network Add-On Kit is a combination of a RadlinX box and a SysManager PC.

18

System & Applications Manual

SysManager 410

*) With a CPU-ME system, the MAC-Manager cannot be used in this configuration. Figure 1. Configuration with a RadlinX box. Features Alarm description; Alarm history; Alarm notification; Geographical map display; Inventory report; Multi-user; Information is available in human words and not in alarm codes. History or tracking of previous alarms. Display on screen. An overview of the ISPBX network and alarms status. A list of ISPBX parts, cards, telephone units etc., its status and serial number. Several users can monitor the FRM activity simultaneously. Several user categories are included. Each category enables access to different functions and operating levels. These definitions can be modified by the system administrator and new categories can be added. The system administrator can also define who should be notified in case of emergency, according to the time shift, responsibility etc. This is done according to predefined parameters, directing alarm notifications to the appropriate technician via a pager or e-mail. Information how to handle the alarm. Recommended action(s) for a selected alert displayed in a so-called trouble ticket. If recommended solutions are insufficient, users can add remarks in a trouble ticket to expand the knowledge database.

Notification to technicians; Recommended solutions; Technician notes of actual solutions;

Requirements There is a licence for basic configuration and one for enhanced configuration. Both can be used in combination with (or without) an SNMP Gateway licence. The basic configuration only supports alarm notification and alarm description. There is also a try&buy licence. A ComboX must be connected to each of the ISPBXs in the network. The FRM needs at least one dedicated modem. If the central site is connected to more than 15 remote sites, it will usually use more than two modems for assuring the high grade of service in communication with the remote sites. In such a case, a Specialix multi-port card may be added to the computer, adding COM ports to the PC. 4.7 The DECT Management Module (DMM)

The DECT Management Module provides functions for managing a DECT system, for example subscribe and disable portable telephones (handsets). The DMM may be applied as part of SysManager, in which case it co-operates with the MAC-Manager, or it may be applied independently. Features Subscription management; Radio Management; Board Survey; Copy subscription

Before it can be used, a portable telephone must be subscribed to the DECT system. This means that it must be registered by the DMM. For each Radio Fixed Part (RFP) connected to the DECT system, the status is displayed. With the DMM the status of an individual RFP can be set to installed. This enables alarming on the functioning of the RFP. A list of installed boards, their operational status, address and no. of users. A service engineer can pre-subscribe portables on its host DECT system and store the subscription records into a data-file. With this data-file and the pre-subscribed portables the engineer can go to the customer and import

19

SysManager 410

System & Applications Manual

Move subscription

SNMP support

the file with the subscription records into the customers DECT system. The portables are directly operational. It is even possible to send the file with the subscription records and the subscribed portables to the customer, who only has to import the file himself (or this can even be done remotely). The presubscribed portables can be used immediately. The service engineer can move a subscription (because of changes in the DAS hardware configuration) from one board to another board. The move subscription is taken place without first removing the subscription and then subscribe the portable again on-air as done with the normal move of DNRs via the MAC manager. The Move subscription saves the service engineer the time to collect the portables and re-subscribe them. It is an attractive solution to save maintenance costs. SNMP connection to DCC (instead of DCMIP).

Requirements This module requires a licence. There are different type of licences: DECT configuration licence; DECT management option on the MAC-Manager licence. Background licence (needed when the DMM is managed via the MAC-Manager); Limitations and Boundaries The DMM does not provide Board Management. This belongs to the jurisdiction of the MACManager or the Operational Maintenance module. 4.8 The External Application Interface Module (EAI)

The main purpose of the EAI module is to give external applications access to the ISPBX and SysManager related services. Examples of such applications are central management systems, hotel and hospital applications, external messaging applications such as Vakans and NetWise. Functions like Do Not Disturb, message waiting indication and wake-up with announcement in the language of a guest are supplied by the ISPBX. Functions like call accounting (billing), assigning extensions and management of a name database are supplied either by the SysManager or by external applications (front office systems). Additionally the EAI performs tasks that are required by the external applications. For more information please refer to the External Application Interface manual. The EAI supports PID dialling. Personal Identification Dialling (PID) is used for the allocation of call costs to a particular person. It is also available in the MAC-Manager. With the Data Distribution Module they can be used together. Also see section 6.5 on page 33 about the EAI in combination with smart card dialling. Requirements This module requires a licence. There are two different types of licences: Full licence (using the V.24 port); Messaging only licence, when only Do Not Disturb and Automatically Entered Messages need to be supported. Depending on the required functionality, also the following modules are required: Directory Services Module for external applications that use names/numbers; Call Reporting Module (no reporting) for external applications that use call records. Limitations and Boundaries EAI budgeting and EAI messaging is only possible in a single unit system, due to the one FDCR stream limitation. So no FIN network can be supported for EAI-Budgeting. Via the EAI an "add PID message with DNR and without traffic class is not possible because the OM command ASPICC rejects it. A traffic class is always needed. Via the EAI the following fields of the add PID message are not supported: Private/Business/Special, Check on budget, Bill on PID. See also Table 4. Attribute allowance., on page 33. Synchronisation of a PMS database with a SysManager database is not supported.

20

System & Applications Manual

SysManager 410

If the ISPBX does not support Advise of Charge, then the ISPBX can not decrease the budget. In that case budget control has to be done by the PMS. EAI-Messaging is not possible in a DPNSS network. 4.9 The Data Distribution Module (DDM)

The Data Distribution Module (DDM) distributes common data between the MAC-Manager Module, the Call Reporting Module, the Directory Services Module and the External Application Interface Module. For example, the name of a person related to a specific DNR is used in the MAC-Manager database, the Call Reporting Module database and the Phonebook database. When this name is updated in one of these databases, the DDM will be notified of this update. Then the DDM will inform the other modules about this update. This way the update will automatically be entered in all databases keeping this information up-to-date. The ISPBX data is maintained via the MAC-Manager. Other modules, like PID updates in the EAI module and name updates in the CRM, initiate changes of the ISPBX data. These changes are stored in the MAC-Manager database. A project is automatically scheduled that is sent to the ISPBX 1 minute after the receipt of the changes. If the project has failed, it is rescheduled. This is realised by SNAPI. See requirements later on in this section. The following distributed configurations are supported: MODULES CONFIGURATION NAME Basic Distribution Full Distribution Full Distribution without CRM Basic Hospitality Basic Hospitality, no PMS billing Full Hospitality Full Hospitality, no PMS billing Full Hospitality without CRM Messaging No Distribution NA: Not Applicable Table 1. Supported distributed configurations. During installation the user selects which data distribution configuration will be used. Notes: 1) Configurations using the EAI (and a link to a Property Management System) only support a single site (ISPBX). 2) Where the CRM is also used: hardware or software buffering for FDCR records coming from the ISPBX is not allowed (i.e. no TOPS box or remote data collection). 3) The messaging configuration supports single site, with or without a PMS link. Upgrade scenarios are No Distribution No Distribution No Distribution No Distribution available for the following cases: Basic Distribution; Messaging; Full Distribution, no CRM; Full Hospitality, no CRM; EAI No No No Yes Yes Yes Yes Yes Yes No DSM No Yes Yes Yes Yes Yes Yes Yes Yes No CRM Yes Yes No Yes Yes Yes Yes No No No MM Yes Yes Yes No No Yes Yes Yes No No Standalone Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes ENVIRONMENT Multi user single server Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Multi user dual server Yes Yes NA Yes Yes Yes Yes NA NA Yes

21

SysManager 410

System & Applications Manual

Messaging Basic Hospitality Basic Hospitality Basic Hospitality Basic Distribution Full Distribution

Basic Hospitality; Full Hospitality; Basic Hospitality, no PMS Billing; Full Hospitality, no PMS Billing; Full Distribution; Full Hospitality, no PMS Billing.

The configurations can be expanded with the following modules: OMM, AMM and FRM for multi user configurations. On top of that the IFM and DMM modules can be installed in a single user configuration. Because data field lengths may be different in various databases, it is advised to use a common length as preferred length. DATA NDNR DNR Name Department Hierarchy levels USE 12 6 20 32 7 MAC 12 6 32 CRM 12 6 32 32 7 DSM 12 6 30 36 no limit EAI 6 20 ISPBX 12 6 20 -

The NDNR is a Network DNR, i.e. the DNR preceded by the cluster-id.

Table 2. Preferred database field lengths. Full hospitality This is the most extended configuration. It is especially meant to be used in the healthcare environment, due to the external interface. Budgets related to a PID can be modified via an external Property Management System (PMS). The requests are sent via the MAC-Manager to the ISPBX, where the budget is kept. Supports: Terminal Service Display (TSD), Calling Name and Number Display (CNND) and Central Directory Dialling (CDD). Basic hospitality This configuration is meant to be used in the hotel or healthcare market where budget dialling is not used. Supports: TSD and CNND. Messaging This configuration supports all messages required for the Swedish Message Intercept Systems (MIS), such as Vakans, Netwise and Preseco. A physical connection to the Message Intercept System can be offered. Supports: Automatically and Manually Entered Messages (AEM/MEM), Do Not Disturb (DND) and Message Waiting. Full Data Distribution This configuration combines the PhoneWare world and its operator consoles (SV60E) with the ISPBX. There is no interaction with a PMS. This will probably be the most common configuration. It is the ideal solution when name display or browsing is required in combination with the operator console. Supports: TSD, CNND and CDD. Basic Data Distribution This configuration only integrates Call Accounting, thus the CRM with the MACManager.

22

System & Applications Manual

SysManager 410

Full Distribution or Full Hospitality configuration without CRM Both the Stand-Alone and Multi-User SysManager (Single-Server only) support an extra configuration similar to the existing Full Distribution or Full Hospitality but without the CRM module.

Basic or Full Hospitality configuration, no PMS billing Both the Stand-Alone and Multi-User SysManager support an extra configuration similar to the existing Basic or Full Hospitality but where CRM will not send FDCR+ records to EAI. This means that CRM can support multiple sites, but EAI only supports single sites. The kind of data distributed is the same as in the existing Basic or Full Hospitality except that EAI will not be an Update Receiver for FDCR.

Features Buffering;

Disable/enable;

One time data entry;

Synchronise;

SNAPI Support

The DDM buffers data that has to be distributed. If the DDM can not reach a module for some reason, the data will be stored for a maximum subscription delay (default 2 hours). If the data is not delivered to at least one module within that delay, then the concerned data is removed from the resident buffers. Each module informs the user about these problems in its own way. The CRM logs all events in the TABS events server. The MM dumps the errors in the communication audit. The DSM has counters in the DSM admin utility. It is possible to disable distribution. This can be used to update a database without distribution. Note that when you switch to enable, the updates performed during the disable period are not distributed. With the synchronise feature the databases can be made consistent again. You do not have to enter the same data twice. Depending on the type of SysManager configuration some data (for example names) must be entered in one module, and other data (for example hierarchy information) in another module. Which data needs to be entered where, can be found via the online help available in the Configurators group (Where to enter which data). It is advised to follow this procedure. The reason for this is that it might happen that for some reason data entered in one module is not sent to other modules. If SysManager 410 recognises this, a message will be displayed. If you see a message about Data Distribution, or if you have any doubt about the consistency of data between the modules, you need to synchronise. If data is entered in the advised place, then the synchronisation procedure can be used to obtain consistency. How and where to synchronise when databases are inconsistent is described in the online help available in the Configurators group. If the procedure for entering data is not followed, then consistency after synchronisation is not guaranteed. The DDM contains a background program called SNAPI (Second Nature Application Programming Interface), which is used to exchange data between the MAC-Manager database(s) and other modules (Call Reporting Module, Directory Services Module and External Application Interface) and between the MAC-Manager databases(s) and the ISPBXs. SNAPI only runs in data distribution configurations that include the MACManager. SNAPI is licensed and called the Background licence. However, not in all configurations a customer has to pay for the license (see NPA 144).

Requirements The DDM is always installed. In a No Distribution configuration the DDM is disabled. Not in all configurations a customer has to pay for the DDM license: only for Full Distribution and Full Hospitality (both full charge) and basic Distribution (lower charge). The Hotel configuration as generated by SalesBuilder is a subset of Basic Hospitality and requires the DDM license, but this is not charged. The DDM contains a background program called SNAPI (Second Nature Application Programming Interface), which is used to exchange data between the MAC-Manager database(s) and other modules (CRM, DSM and EAI). SNAPI runs in data distribution

23

SysManager 410

System & Applications Manual

configurations that include the MAC-Manager. SNAPI is licensed and called the Background license. However, not in all configurations a customer has to pay for the license: only for Full Distribution and Full Hospitality. Limitations and Boundaries Department names must be unique over all organisations on all levels of the hierarchy. The CRM allows the same department name in different parts of an organisation, but the DSM (Phonebook) will refuse this. Since the CRM is the place to enter an organisation, in various configurations, the user should take great care in keeping the department names unique. In multi-site configurations, the user should be aware that the organisation is entered per site in the CRM. This means that after selecting a site, the user must take extra care in keeping the department names unique, because the user sees only one site at a time. An alternative for possible user mistakes in CRM, would be to enter the organisation in the Phonebook. However, a common top level organisation can not be entered in the Phonebook. Note that the term department applies to any organisation level. 4.10 The ISPBX File Management module (IFM)

The ISPBX File Management module is primarily meant for those customers who want to do regular ISPBX system back-ups themselves. Features Disk emulation; File conversion;

Provides the back-up functionality to the ISPBX. It can be used to transfer files between the ISPBX and an external PC application. File conversion from ASCII to iS3000 file formats (internal ISPBX file format) and vice versa. It is possible to run the file conversion program without a connection to the iS3000, allowing for example, POM files, COM files and ISPBX licence files to be converted.

Requirements This module requires a licence.

24

System & Applications Manual

SysManager 410

5.

Multi-user Support

Multi-user refers to computer systems that support two or more simultaneous users on different computers. This is different from multiple-account systems (referred to as multiuser in previous documents) which enable many users to use SysManager, but not concurrently. With Windows NT, the SysManager supports multi-user operation. This can be based on file sharing, client/server or file distribution configuration. The SysManager modules are the same for both configurations. The only difference is the server part. A combination of client/server and file sharing is possible. It is also possible to combine servers on one PC or clients of several modules on one PC. Multi-user operation requires client licences, additional user licences and server licence(s). Definitions Multi-user: File sharing: Client/Server:

SysManager server: SM server: CRM server: SM client: Multi-user domain: Single server configuration: Dual server configuration:

User accounts:

Multiple users on several computers can access the same data on a server concurrently. Multi-user, based on sharing files. Same as multi-user, but on the server a database engine is running that improves performance and possible the security. It does not change the SysManager functionality. An example is the MAC-Manager Faircom server. (This is not to be confused with a Windows NT server/client network.) a SysManager computer on the Dual Server configuration, that supports MM, DSM and FRM server. a SysManager computer that supports MM, FRM, DSM and/or CRM server. a SysManager computer on the Dual Server configuration, that supports CRM server. a SysManager computer on which only client modules are running. a SysManager operating in a multi-user environment. Only one client in a multi-user domain is possible. all available server applications are installed on one PC (SysManager server PC). The CRM server application is split from the SysManager server and installed on a separate PC (CRM server PC). The reason for using two servers is to increase performance when supporting large ISPBX configurations. Both PCs use the same dongle. Multiple users can use the same computer, but not concurrently. Each user can have specific access rights.

Notes: 1) Only in combination with the MAC-Manager, where subscription is integrated with the MAC-Manager Client. The standalone DMM can not be used in a Multi-user environment. 2) DSM in combination with other PhoneWare applications, like SV60E, is possible with SQL server. The DSM itself does not have a user interface. Changes to the database of DSM, PhoneWare database, can be made with the Phonebook Manager. The number of PCs mentioned in the previous table, are the minimal required PCs. In case of dual server solution, two PCs are required but only one dongle is used. The DMM and OMM are part of the multi-user domain and will be installed on the same PC as the other multi-user applications. Simultaneous access by the clients is however not possible.

25

SysManager 410

System & Applications Manual

dongle

Server FDCR (TT) OM/MAC DECT AMM ALARM

MM s DSM s PC DMM s EAI s CRM s DDM s OMM s LIM s LM s MML s AMM s CM CM s Db FRM s

TCP / IP

Client MM c DMM c CRM c OMM c MML c FRM c AMM c PC DDM c LIM c LM c CM c MM c DMM c CRM c OMM c MML c FRM c AMM c

Client PC DDM c LIM c LM c CM c

Figure 2. Single SysManager server configuration. Notes: 1) All client computers use the CM database of the SysManager Server computer 2) Depending on the number of ISPBXs you might need several COM ports for the same protocol.

SysManager Server PC MM s EAI s ALARM DMM s DDM s OM/MAC FRM s OMM s LIM s DECT MML s LM s AMM s AMM CM s CM Db DSM s dongle

CRM Server PC DDM c CRM s LIM c LM c CM s CM Db FDCR (TT) OM

TCP / IP

Client MM c DMM c CRM c OMM c MML c FRM c AMM c PC DDM c LIM c LM c CM c MM c DMM c CRM c OMM c MML c FRM c AMM c DDM c LIM c LM c CM c

Client PC

Figure 3. Dual SysManager servers configuration.

26

System & Applications Manual

SysManager 410

Notes: 1) Both Server computers need a separate Connection Manager Database. 2) All client computers use the CM database of the SysManager Server computer. 3) Depending on the number of ISPBXs you might need several COM ports for the same protocol. 4) The SysManager Server computer does not have a CRM client, and the CRM Server computer does not have an MM client. Client/server configuration In this configuration, a dedicated database server is added to a PC network. All SysManager PCs access this central database server. The server consists of Windows NT hardware (a fast PC) with server software plus client licences for every user. The following modules can be used in a client/server configuration: MAC-Manager Module; Directory Service Module. As the server package includes one user (client), the number of additional user licences is the total number of users minus one. Only one dongle is required in a client/server configuration. All licence information (clients as well as server) is combined in one licence file. Advantage: It offers high performance and/or security. Server restrictions: 1. Windows NT server is not supported. This means that it runs on a workstation only. 2. Support of NTFS (New Technology File System) only. 3. Unattended W-NT is not supported; always an NT user must be logged on. The workstation can be locked via a password. Client restrictions: 1. Windows NT or Windows 2000 Professional workstations. 2. Support of NTFS (New Technology File System) only. Client/server with the MAC-Manager Module The MAC-Manager module uses a server with the Faircom database server package. The client PCs run the standard MAC-Manager package, installed as a client. One client is standard (running on the server). Additional clients (users) are licensed. Default the Faircom server licence comes with 8 Faircom user licences. The server occupies one user licence. The installation of the Faircom server is a separate installation and is not integrated with the SysManager installation. When using a Faircom MAC-Manager database, it is strongly advised to install an uninterruptable power supply for the MAC-Manager server. This prevents damage to the Faircom database in case of a power failure. When and why using a Faircom Server The basic MAC-Manager package (without the Faircom Server) can support up to 3 simultaneous users, without a dramatic loss on computer performance (depending on network load and traffic). However, when more than 3 simultaneous users are wanted, the additional software package from Faircom Corporation is required to handle the higher number of requests made to the database. Client/server with the Directory Service Module (DSM) The DSM uses a PhoneWare server with the Microsoft SQL database server package. Clients can be SuperVisor 60E operator consoles, several DSMs (every iS3000 node requires a local DSM for E-CNND). The DSM requires a dedicated server if either there are more than: 5000 entries in the database; 3 PCs in a file sharing configuration; 10 PCs in a file distribution configuration. File sharing configuration A number of PCs in a network can share a database that is located on one of the PCs. Due to performance, up to three SysManager users can work simultaneously with a database.

27

SysManager 410

System & Applications Manual

Most SysManager modules with a user interface can be used in a file-sharing configuration. As a SysManager application always includes one user licence, the number of additional user licences is the total number of simultaneous users on client systems. Advantage: It is much cheaper than using a client/server configuration. Disadvantages: 1. Performance decreases when multiple users access the same data simultaneously. 2. Restricted number of simultaneous users. The file sharing configuration can also be used to create a SysManager workstation on a number of locations. Multi-user access of data is in most cases not simultaneous. Multiuser access can for example be applied in order to provide the customer workstations on a number of locations. Note that pricing is based on the number of concurrent users and that installing more clients for flexible workplaces does not increase the price. File update configuration (combination with SV60E, also known as master/slave configuration) Another form of file sharing is file update. In this case one PC has the master database. At predefined times (e.g. once a day) this database is distributed to the other SysManager PCs on the PC network. The file update configuration is not supported by the CRM and the MAC-Manager. Advantages: 1. It is much cheaper than using a client/server configuration. 2. No network load. 3. Failure of one component (PC or LAN) does not affect operation of the other PCs. Disadvantages: 1. Changes are not distributed to the other PCs immediately! 2. Distribution can only be done while the PC is on but when the SysManager modules are not running!

SuperVisor 60E operator consoles

ISPBX LAN SQL server SysManager

Figure 4. SysManager with the DSM client/server configuration.

28

System & Applications Manual

SysManager 410

Multi-user PC Requirements: WINDOWS NT MINIMAL REQUIRED Pentium 233 MHz 128MB RAM 4.3 GB Hard Drive RECOMMENDED Pentium II 350 MHz 128MB RAM 6.4 GB Hard Drive

29

SysManager 410

System & Applications Manual

6.

Smart Card Telephony

A smart card is a plastic card holding a chip, that can be programmed for different applications. The Philips' smart card is used in combination with a SOPHO-SET 510.

Figure 5. SOPHO-SET 510 with smart card. What is the use of a smart card ? Institutes like hospitals, universities or hotels have people that use the institutes ISPBX. It is common practice that you have to pay for this usage. The use of smart cards is a perfect solution for this. Benefits : Generating income: by offering telephony to guests. : Controllable administration: by reducing the number of administrative tasks. : High service class: by offering personal telephony. : Pre-paid telephony. Eliminate the need for a telephone bill and the risk of unpaid telephone bills. : The guest or patient is in control of his or her telephone budget. This avoids unpleasant surprises because of unexpected high telephone bills. : Possible integration with other services: for example by offering a single plastic card for telephony and access control. : Prevention of unauthorized usage of guest or patient telephones. Telephone operation is minimised without the smart card inserted. This makes the phone useless for others and prevents the institute for unpaid (international) telephone calls. Required material SmartCard Manager (as integrated part of MAC Manager) licence. The MAC-Manager is expanded with an option (SmartCard Manager) to manage the smart cards. The SmartCard Manager can program a new card, modify a card, delete records and block a lost or stolen card. Telephones with smart card reader (the De La Rue SmartCard Reader DE128 or compatible readers are supported) The SOPHO-SET 510 is a SOPHO-SET 125/225 (Hotel sets) look-a-like. It is an attractively priced analogue telephone with an integrated smart card reader in a hospital clean white housing. It features 5 speed dial keys, redial key, message waiting lamp and ringer volume control. There is also a SOPHO-SET 520, which is basically a SOPHO-SET 510 with TV/Radio control possibilities and headset connection. For TV/Radio control it offers an interface to a dedicated television set. For the headset a volume control is available. This set is (up to now) mainly used in the German market. D2000 smart cards. De La Rue smart card programmer DE128. The DE128 smart card programmer from DeLaRue Card Systems is a standard, low priced off-the-shelf product to read and write smart cards. The card programmer is connected to the serial port of a PC. It requires no additional power supply. In a multiuser configuration, multiple PCs can have programmers connected. It is not possible to access programmers over the network; only the PC that a programmer is connected to can access that programmer. PIDs (budgets).

30

System & Applications Manual

SysManager 410

Figure 6. Smart card programmer. In the hospital environment two main applications for smart card telephony are distinguished: budget dialling and personal number. 6.1 Budget Dialling

With budget dialling a patient pays an amount of money in advance for telephone calls. This is also called pre-paid telephony. The amount of money is registered in the ISPBX. It can be manipulated with the MAC-Manager or via a Property Management System (PMS). Budgets can be expressed in SOPHO units or in currencies. It is possible to define both local currencies as Euro currency. The MAC-Manager uses a background process, which allows the fast handling of the budgets between ISPBX and SysManager. The normal scheduling mechanism is not used. The MAC-Manager generates a personal identification (PID) code in the ISPBX and attaches an initial budget. When a call is made via a smart card telephone, the bill is sent to the PMS system. The PMS system calculates the new budget and sends the new budget to the ISPBX. When the budget is zero, no new calls are allowed. Note that calculation is done after the call. It is not a call break at zero solution. The call break at zero budget functionality based on SOPHO units is also available. Budget dialling is related to password dialling, a facility that restricts the use of telephones by only allowing external calls on password base. Password dialling is not restricted to a particular telephone. A patient can move around and use any telephone, as long as the password is still valid. 6.2 Personal Number

The personal number facility, allows patients to have one number during their whole stay in the hospital. It does not matter how many times they change room. All the time they will be reachable on the same number, for internal as well as external callers. When a patient changes room, the personal number is de-activated by pressing a certain digit and the smart card is taken out of the phone. Arriving in the new room the personal number is activated by inserting the smart card and pressing the required digit. Due to the personal number facility, the hospital staff does not have to take any action on the telephone system when patients change room. 6.3
2

Smart card properties

The I C Bus memory cards of the type D2000 (or compatible) complying with ISO7816.I are supported. General card layouts can be read and displayed as well. Up to 28 digits are available on the smart Card for other purposes. Up to four applications can be programmed on one smart Card.

31

SysManager 410

System & Applications Manual

The smart cards contain the following identification data: - Program-ID Used to determine whether the card was programmed by SmartCard Manager or by another program. - Card-Version Indicates the format of the data on the smart card. This will allow future versions of SmartCard Manager to read old format cards. - PBX-ID The name of the ISPBX associated with the card. - Card-ID SmartCard identification number. The number is unique within the smart Cards ISPBX. The combination of PBX-ID and Card-ID identifies the smart card across the ISPBXs within one MAC-Manager installation. The smart cards can contain 4 items of the following application data: - Personal PID; prefix + personal-PID - General PID; prefix + general-PID - Desksharing activation (PID validation); prefix + personal-PID + DNR - Desksharing activation (no validation); prefix + DNR - Desksharing deactivation (PID validation); prefix + personal-PID + DNR - Desksharing deactivation (no validation); prefix + DNR - Other; up to 28 digits The prefix differs per application. Smart cards can be customised. On the front side of the smart card, a name or logo can be printed. The backside can be used for advertising purposes or user instructions. 6.4 Security

Security is offered via: Licensing Access to the SmartCard Manager if there is no smart card license is not allowed. User privileges The MAC-Manager allows you to assign privileges to create/display/modify/delete smart cards per end user. The same applies to PIDs. Smart card operations, however, supersede PID privileges. If you dont have PID creation privilege, but you do have smart card creation privilege, then you will be able to create smart cards including PIDs. Card security The telephone set normally hides the contents of the card from the card owner. If the card owner, however, somehow detects what PIDs are on the card, then the card owner can make PID calls without the card. This can be prevented by the use of not 'diallable' digits (ABC-prefixes). Uniqueness In case prefix and PID on the card also exist in another ISPBX, then the card can be used for that ISPBX as well. By using the maximum PID length in combination with ABC-prefix, the risk is almost zero.

32

System & Applications Manual

SysManager 410

6.5

EAI interface

The following messages are relevant on the EAI interface: MESSAGE Add PID DESCRIPTION A PMS adds a PID or costcentre in the ISPBX. Attributes are PID, DNR, traffic class and budget. Note that not all combinations are possible. See the next table. The additional budget is added to the current budget in the ISPBX. A PMS deletes a PID or costcentre from the ISPBX. Same as Add PID, only this time budget is given in SOPHO units. Replaces the budget in the ISPBX with the new budget. The budget is given in SOPHO units. The PMS can request the PID related information by using PID or DNR. The budget may be requested in SOPHO units or money. The result of the message does not contain the DNR of a personal PID. Result of the get PID info request. Table 3. Relevant EAI messages. Note: Traffic class update is part of the message, but is not supported in the EAI. The following table shows the attributes in relation to the PID function. PID FUNCTION General costcentre General PID General PID with budget Personal PID Personal PID with budget ALLOWED COMBINATION PID PID and traffic class PID, traffic class and budget PID, DNR and traffic class PID, DNR, traffic class and budget

Update PID Delete PID Add PID SOPHO Units Set PID SOPHO Units Get PID info

Get PID info result

Table 4. Attribute allowance.

33

SysManager 410

System & Applications Manual

7.

Directory Distribution Service

The Directory Distribution Service can be installed on SysManager 410, SuperVisor 60E or another PC (e.g. the SQL server). Part of the Directory Distribution Service is Electronic Data Transfer (EDT), which is used to update name-number relations in all involved ISPBXs in a DPNSS network if name-number information changes have been made in the PhoneWare database. When the Directory Distribution Service is installed on the SysManager 410, only EDT is added. On a stand-alone PC the CM, LM, LIM and EDT are installed. On the SuperVisor 60E the CM and EDT are installed. The name-number relations in the ISPBXs are used for Central Name and Number Directory (CNND) and for name browsing on ErgoLines D325, D330 and D340 (CDD). Name browsing on the ErgoLines uses name-number information stored in the ISPBX name directory. This applies to both internal and external name-number relations. Name-number information is typically entered or changed in the PhoneWare database (Phonebook) by the operator, whereby the PhoneWare database is the leading database. EDT updates name-number relations in the ISPBXs if changes have been made in the PhoneWare database.

Figure 7. Concept of Electronic Data Transfer. EDT consists of two type of components: an EDT server and one or more EDT clients. The EDT server queries the PhoneWare database retrieving the name-number relations and determines the changes since the previous time. The EDT clients will store these changes in the applicable ISPBXs. Because the EDT server and EDT clients perform these tasks independently of each other, the changes are temporarily saved in the transfer database. Also, the result of storing the changes in the ISPBXs by the EDT client is put in the transfer database and the EDT server collects it for you to monitor. Further information can be found on the PC Applications CD-ROM.

34

System & Applications Manual

SysManager 410

8.

Overview of the SysManager Portfolio

The following table shows the licensing and pricing structure of the SysManager. Equipment licence Module MAC MAC-DMM Management MAC SmartCard Manager MAC server licence MAC add. User licence Faircom server licence DMM Background DMM Configuration CRM CRM Alike CRM Background CRM add. User licence OM AM DSM FRM Full FRM Basic FRM SNMP option EAI EAI Messaging only IFM DDM T&B: Try&buy licence Inf. (Infinite): application licence Note: Try&buy licences are single-site only! X X X X X X T&B X Inf. 3010 X X X X 3030 X X 3050 X X 3070 X X 3090 X X Option on MAC, also requires DMM background. Remarks

X X X X X X X X X X X X X X X X X X X External use X X X X X X X X X X X X X X X X X X X X X Pre SSW805.23 EAI-hotel

35

SysManager 410

System & Applications Manual

9.

Examples Of Configurations Direct local connections (single site) Connection to a local ISPBX is done using minimum two PC ports: for example one for connecting to an ISPBX FDCR/TT port; another for connecting to the OM or the IAS/A port. If the AMM is installed, then it is recommended to use the optional multi-port card. This card adds four COM ports to the PC. A remote connection (via an extra COM port ) may be used by a service centre.

SysManager PC with multi-port card

iS3030 MM (OM), DSM CRM/FRM DMM CPU ComboX DCC

AMM

IAS/A

Modem PC with pcANYWHERE for remote service

Modem

Figure 8. Local SysManager connections with FDCR/TT buffer and remote access.

iS3090 SysManager PC MM, DSM, CRM DMM AMM CIE DCC IAS/A

Modem PC with pcANYWHERE for remote service

Modem

Figure 9. Local SysManager with BIM. Note that if fault management is also required, a ComboX is needed for the FRM.

36

System & Applications Manual

SysManager 410

SysManager PC with multi-port card

Directory sharing via LAN MM (OM), DSM, CRM DMM

SuperVisor 60E PC S-interface

0

iS3030

CPU DCC IAS/A

Link to PMS via EAI

AMM

Figure 10. Example of a hotel configuration. The SysManager PC may have a link to a so-called Property Management System (PMS); an external application suited for hotels that uses the SysManagers EAI module. In hotel configurations there is no hardware buffering of FDCR/TT records coming from the ISPBX. The reason for this is that a buffer creates a possible delay so that the guest bill comes too late (maybe after check-out). Connections in a multi-site configuration For Public Switched Telephone Network (PSTN) or private networking connections to remote sites, modems or LAMs are required on both sides (local and remote). To save modems (or LAMs) at a remote iS3070/3090, the port-selector functionality of the BIM can be used. Note: If a ComboX is used as a port-selector, the connection can be used either for the combination MM, CRM and OM or the combination FRM, CRM and OM. The MM needs a BCS protocol connection to a CPU-ME. This cannot be combined with the FRM function. The modem port used for remote OM & IAS/A connections can also be used for dialling the local IAS/A port through the PSTN. This is another alternative solution to the problem of having only 2 PC COM ports available for connections to the local ISPBX. At the remote site the FDCR/TT connection must always be buffered via a buffer box. Note: If the ISPBXs are networked, available capacity on network links could be used as an alternative to using separate connections. The usual loop back way (either through a modem or, in case of digital links through a SOPHO-LAM P375 or telephone set with data port, and the ISPBX) should then be used.

37

SysManager 410

System & Applications Manual

Remote sites iS3030 Local iS3030 ComboX CPU iS3090 Modem BIM 9600 bps Modem 2400 bps CIE DCC IAS/A CRM/FRM/OM ComboX CPU

FRM, CRM, OM or MM, CRM, OM Simple Network Management Protocol (SNMP) link 1 2 3 SysManager PC with multi-port card 4

Modem Modem Modem Modem Modem Modem Modem iS3090 CIE BIM 9600 bps DCC 2400 bps IAS/A

1) Incoming alarms from the FRM 2) CRM or FRM (polling) 3) DECT, AMM, MM, OM 4) Remote access from service centre

PC with pcANYWHERE for remote service

Figure 11. Remote SysManager connections.

38

System & Applications Manual

SysManager 410

10. List Of Used Abbreviations AMM CDD CLI CM CNND COL CRM DMM DPNSS DSM EAI E-CNND EDT FDCR/TT FRM IAS IASA I-CNND IFM IPSC-Hoorn ISDN ISPBX LAM LAN LIM LM LoB MAC MIS MM MML MTS ODBC OM PBC PMS RAP SNAPI SNMP SPB SQL SSW SV60E Announcement Management Module Central Directory Dialling Called Line Identification Connection Manager Calling Name and Number Display Connected Line identification Call Reporting Module DECT Management Module Digital Private Network Signalling System Directory Services Module External Application Interface Extended Calling Name and Number Display Electronic Data Transfer Full-Detailed Call Recording and Toll Ticketing Fault Report Module Integrated Announcement Server (VoiceManager 150) Integrated Announcement Server Autonomous (VoiceManager 110) Internal Calling Name and Number Display ISPBX File Management International Production And Supply Centre Integrated Services Digital Network Integrated Services Private Branch Exchange Line Adapter Module Local Area Network Login Module Licence Manager Line of Business Moves, Adds and Changes Message Intercept System MAC-Manager Man Machine Language MER Telemanagement Solutions Open DataBase Connectivity Operational Maintenance Philips Business Communications Property Management System Risk Assessment Procedure Second Nature Application Programming Interface Simple Network Management Protocol Service Plus Box Structured Query Language System SoftWare SuperVisor 60E

39

SysManager 410

System & Applications Manual

TABS TAPI TSD

Telephone Accounting and Billing System Telephone Application Program Interface Terminal Service Display

40