Accounting Cem

CONFIGURATION GUIDE
Accounting
Issue:
0703
CONFIGURATION GUIDE
Accounting
A Publication of
NEC PHILIPS Unified Solutions Nederland B.V.
HILVERSUM, THE NETHERLANDS
Order No.:
3522 009 12651
Manual No.:
Date:
March 2007
Great care has been taken to ensure that the information

contained in this handbook is accurate and complete.
Should any errors or omissions be discovered or should any
user wish to make a suggestion for improving this handbook,
they are invited to send the relevant details to :
NEC PHILIPS Unified Solutions Nederland B.V.
P.O. BOX 32
1200 JD HILVERSUM
THE NETHERLANDS
NEC PHILIPS Unified Solutions Nederland B.V. 2007

All right are reserved. Reproduction in whole or in part is
prohibited without the written consent of the copyright owner.
All brand names and product names in this document are
trademarks or registered trademarks of their respective companies.
Cut out one of the labels below corresponding to the title

display pocket of the binder in which you wish to keep this
publication.
Accounting
CONFIGURATION GUIDE
Accounting
CONFIGURATION GUIDE
Accounting
CONFIGURATION GUIDE
1.
ISPBX PROJECTING FOR ACCOUNTING ....................................................3
1.1.
1.3.
HOW TO CONFIGURE IS3000 FDCR OUTPUT .................................................... 3

1.1.1. FDCR OUTPUT OVER V.24 CONNECTIONS ........................................... 3
1.1.2. DIRECT FDCR OUTPUT OVER IP (SINGLE SITE) ...................................... 3
1.1.3. BUFFERED FDCR OUTPUT OVER IP (MULTI SITE) .................................. 4
1.1.4. ENABLE FDCR OUTPUT ............................................................................. 5
HOW TO CONFIGURE 2000IPS SMDR OUTPUT .................................................. 5
1.2.1. SMDR Output over a V.24 connection (MP or AP00) ................................... 6
1.2.2. SMDR Output over an IP connection (MP) ................................................... 7
HOW TO CONFIGURE SV7000 SMDR OUTPUT ................................................... 8
2.
INSTALL AND CONFIGURE BUFFER BOXES ........................................... 11
2.1.
DATA XPRESS REMOTE ACCESS BUFFER BOX .................................................. 11

2.1.1. Configuration of the Data Xpress Remote Access Buffer Box .................... 11
2.1.2. Calculating How Often You Need to Access the Smart Buffer Plus Box .... 12
ComboX .................................................................................................................. 13
2.2.1. Making Physical Connections ....................................................................... 13
2.2.2. Configure Connections using the Connection Manager Database
Configurator ................................................................................................ 13
TOPS BOX ............................................................................................................... 14
2.3.1. Calculating How Often You Need to Access the TOPS Box ...................... 15
1.2.
2.2.
2.3.
3.
CALL REPORTING MODULE INSTALLATIONS .........................................16
3.1.
3.2.
3.3.
3.4.
INTRODUCTION ................................................................................................... 16
BEFORE USING THE TABS CALL REPORTING MODULE .................................. 16
HOW TO CONNECT TABS v7 USING MANAGEMENT@NET ........................ 16
CONNECT STAND ALONE TABS v7 SUITE TO AN 2000IPS ............................. 17
4.
EXPENSE CONTROL SUITE INSTALLATIONS ..........................................21
4.1.
4.2.
4.3.
4.4.
4.5.
INTRODUCTION ................................................................................................... 21
BEFORE USING MAS v9 .......................................................................................... 22
MASv9 LICENSE MECHANISM ............................................................................... 22
INSTALLATION OF MASv9 .................................................................................... 22
CONFIGURATION OF MASv9 ............................................................................... 22
4.5.1. How to Backup the MASv9 Database ......................................................... 23
4.5.2. How to Use the MASv9 Installation Wizard ................................................ 24
4.5.3. How to Manually Define a Data Source ...................................................... 26
4.5.4. How to Manually Create a Data Collector .................................................. 27
4.5.5. How to use the Generic Personnel Import tool ........................................ 31
Table of Contents
PREFACE ...........................................................................................................2
4.6.
4.7.
Table of Contents
ii
4.5.6. How to Manually add a Range of Extensions ...............................................33

MAS version 9.5.5 SYNCHRONISATION WITH MA4000 ......................................34
MAS v9 GENERAL MAINTENANCE AND TROUBLESHOOTING .......................35
4.7.1. Patches .........................................................................................................35
4.7.2. Management Utility ......................................................................................36
4.7.3. Raw Data Exporter ......................................................................................38
4.7.4. Stop and Start Services .................................................................................38
4.7.5. Migration TABS v7 to MAS v9 ......................................................................38
4.7.6. Reset the Administrator Password ...............................................................39
Accounting - Configuration Guide
Release date : 1/mrt/2007
PREFACE
This book describes specific settings for Call Reporting Module (TABS 7) and the Expense
Control Suite (MAS v9) on NEC-Philips platforms. This book is valid for:
-
Management@Net, release 3.1.1

Call Reporting Module (TABS) 7.027
Expense Control Suite (MAS) 9.5.0
This book assumes the products to be installed, for more information refer to the various
product Installation Guides.
1.
ISPBX PROJECTING FOR ACCOUNTING
1.1.
HOW TO CONFIGURE IS3000 FDCR OUTPUT
A SOPHO IS3000 must be prepared to deliver FDCR records to the Accounting Server. Some
assistance, is given below. More information can be found in the FDCR section of the ' OM
Commands Manual'.
1.1.1. FDCR OUTPUT OVER V.24 CONNECTIONS

V.24 connections are used in connections to ISPBX's with software packages older than
Call@Net 2.8.
On a CPU3000 system, the LBU can be used as buffer for FDCR records; this saves a TOPS
Box or ComboX. The CPU software package must be Call@Net 2.4 or higher.
1. Assign a V.24 port with BCS protocol using command ASPORT:<SHELF>,<BRD>
,<CRT>,<PROTOCOL-TYPE>[,<CONNECTIONTYPE>];. If the BCS communication
protocol is chosen, the optional parameter 'connection-type' determines whether remote
communication with modems is needed. Example: ASPORT:11,18,21,1,0; assign local
BCS port on EHWA 11,18,21,
2. Assign OM and Disk emulator devices to this port using command: ASDEVC:<SHELF>,
<BRD>,<CRT>,<LDN>,<EQUIPMENT-TYPE>;. The logical device names must be VDUxx0
(equipment type 20), VDUxx1 (equipment type 21) and DSKxx (equipment type 26),
where xx must be equal to the unit number of this system. Example: ASDEVC:11,18,21,
VDU020,20; assigns OM 1 keyboard device with LDN 'VDU020' on port 11,18,21
3. Set the port in service with command SETINS.
1.1.2.
DIRECT FDCR OUTPUT OVER IP (SINGLE SITE)
A Client Server Profile must be set in the ISPBX for FDCR over IP, see steps below. Direct
output FDCR is for single site installations only. It uses a special FDCR device with equipment
type 33.
Note: A Client Server Profile is used as a protection mechanism. The Accounting Server is
connected to an ISPBX and operates as IP client via a Client Server Profile. The Call@Net
software in the ISPBX operates as IP server and checks the rights through the Client Server
Profile.
To activate direct output FDCR, take the following steps:
1. Look for a FDCR device on the V.24 ports of the CPU (or CIE-2). Example:
2.
3.
4.
5.
DIPORT:11,18,20&&25; where 11,18 is the CPU address. If necessary assign devices

with ASDEVC. The logical device name is free to choose, FDCRIP is most commonly used.
Check if the client is related to a Client Service Profile. Example: DIIPPR:192.168.1.5;
where 192.168.1.5 is the IP address of the Accounting server.
If needed, assign a Client Service Profile to the client. Example:
CHIPPR:192.168.1.5,1; where 192.168.1.5 is the IP address of the Accounting
server and 1 is the Client Service Profile id.
Check the services on this Client Service Profile. Example: DIPROF:1; where 1 is the
Client Service Profile id.
If needed, assign FDCR service to the Client Service Profile. Example:
CHPROF:1,3,1,FDCRIP; where 1 is the Client Service Profile id, 3 means FDCR, 1
means allowed and FDCRIP is the logical device name of the FDCR connection found in
step 1.
Other IP related OM commands that may be useful, are:

-
DITCPC: to display the IP configuration of a CPU3000 or a CIE-2 board;

EXPING: to check if the Accounting Server can be reached over the network;
DIIPSE: to display the (running) IP sessions.
1.1.3.
BUFFERED FDCR OUTPUT OVER IP (MULTI SITE)
A Client Server Profile must be set in the ISPBX for FDCR over IP, see steps below. In case of
buffered FDCR output, the OM service is used for transport of buffered FDCR records.
Note: A Client Server Profile is used as a protection mechanism. The Accounting Server is
connected to an ISPBX and operates as IP client via a Client Server Profile. The Call@Net
software in the ISPBX operates as IP server and checks the rights through the Client Server
Profile.
To activate IP connections for OM, take the following steps:
1. Look for an OM devices on the V.24 ports of the CPU (or CIE-2). Example:
DIPORT:11,18,20&&25; where 11,18 is the CPU address. If necessary assign devices
with ASDEVC.
2. Check if the client is related to a Client Service Profile. Example: DIIPPR:192.168.1.5;
where 192.168.1.5 is the IP address of the Accounting server.
3. If needed, assign a Client Service Profile to the client. Example:
CHIPPR:192.168.1.5,1; where 192.168.1.5 is the IP address of the Accounting
server and 1 is the Client Service Profile id.
4. Check the services on this Client Service Profile. Example: DIPROF:1; where 1 is the
Client Service Profile id.
5. If needed, assign the required services to the Client Service Profile. Examples:
CHPROF:1,0,1,VDU010; where 1 is the Client Service Profile id, 0 means OM, 1 means
allowed and VDU010 is the logical device name of the OM connection found in step 1.
Other IP related OM commands that may be useful, are:
-
DITCPC: to display the IP configuration of a CPU3000 or a CIE-2 board;

EXPING: to check if the Call@Net Application Server can be reached over the network;
DIIPSE: to display the (running) IP sessions.
1.1.4.
ENABLE FDCR OUTPUT
When the Accounting program is configured and connected to the ISPBX execute the
following steps to enable FDCR output
1. Use the command DISPFR to display the FDCR call types and output file. Furthermore
this command displays the accumulated metering pulses and call duration time, which are
lost as result of congestion on accounting records.
2. Use the command CHFRCR: <FDCR-CALL-TYPE>s/r,<OFF-ON>;to add or remove a
FDCR call type to or from the list of recorded items. It allows you to perform call
recording on a restricted set of call types.
3. Before FDCR can be started the output device must be specified with: CHFROD:
[[<LDN>][,[<OUTPUT-FORMAT-VERSION>][,<UNIT>s/r]]];. The output device
can be a LBUxx, a PC, a direct output over IP device or a printer. If necessary use DICHAR
to obtain a list of valid devices. If the output device is changed while FDCR is active, the
old device remains valid until FDCR is restarted.
4. Start the FDCR using command STRTFR:<File name>;.The filename cannot be
ommitted. When FDCR is active, another FDCR start with a different file name may be
done. This redirects the output to the other file and the old one is closed. This to prevent
gaps in the output. For more information about this file, refer to the Facility
Implementation Manual (Management Facilities).
5. Finally the FDCR output can be stopped using the command STOPFR:;.
1.2.
HOW TO CONFIGURE 2000IPS SMDR OUTPUT
A SOPHO 2000 IPS must be prepared to deliver SMDR records to the Accounting Server. To
provide some assistance, a procedure is given below. More information can be found in the
SMDR section of the 'Feature Programming Manual'.
The Call Reporting Module version 7 (TABS) can handle only SMDR over V.24.
The Expense Control Suite version 9 (MAS) can handle both SMDR over V.24 and SMDR over
IP.
The SMDR format depends on the interface (V.24 or IP), the board (MP or AP00) and the
SOPHO 2000 IPS software version. An overview is shown in the following table:
Interface
IP connection via MP
V.24 connection via MP
Former
SMDR Format
Extended 1)
Yes 3)
Yes 3)
Yes
Yes
V.24 connection via AP00

(with AP00 package)
Yes 3)
V.24 connection via AP00 4)

(with MRCA package)
Yes 3)
Enhanced 2)
Yes 3)
Yes 3)
1) Available in R9 and higher.

2) Available in R10 and higher.
3) Available for local and centre office (centralized billing).
4) For the AP00-D card the package cannot be changed, it is fixed MRCA
Table 1-1 SMDR Formats and Interfaces
Enhanced format is part of Extended format and offers the abandoned call facility i.e. the time
of incoming call (next to the time of start conversation and the time of call completion). This
offers the ring time: if time of start conversation = 0, the ring time is difference between time
of incoming call and time of call completion. This is important for Ring Time Reports in TABS
1.2.1.
SMDR Output over a V.24 connection (MP or AP00)
For a single site, a direct V.24 connection to the Main Processor (MP) is sufficient (built-in
SMDR).
For multi-site connections, buffering is needed. For this buffering, Smart Buffer Plus boxes are
used. These boxes are connected through V.24 connections to the MP (main processor) or to
an Auxiliary Processor (AP00). The AP00 must be used in case of centralised billing.
For both direct and buffered connections the same cable is used: RS RVS-4S CA-C (12NC is
9600 511 51021):
-
For a direct connection, this cable is applied between the 2000 IPS SMDR output port and
a COM port of the Accounting Server.
For a buffered connection, this cable is applied between the 2000 IPS SMDR output port
and a Data Xpress buffer box.

Note: Collection of call records from the Data Xpress buffer box by the Call Reporting Module
is via IP (FTP) or via a dial-up connection (modem).
To provide some assistance, a simplified procedure for direct SMDR output from the Main
Processor (MP) is given below. More information can be found in the SMDR section of the
'SOPHO 2000 IPS Feature Programming Manual'.
1. Set Port 1 to Built-in SMDR:
4000>1>14
2. Set Data length to 8 bits:

4001>1>1
3. Set Parity to None:

4002>1>1
4. Set Stop bits to 1:

4004>1>0
5. Set DTR signal to high:

4005>1>1
6. Set RTS signal to high:

4006>1>1
7. Set Data Speed to 19200 bps:

4008>1>5
8. Set SMDR for Outgoing Calls from Station 203:

1306>203>1 (default)
9. Set SMDR for Incoming Calls to Station 203:
1305>203>0 (not default)
10. Set SMDR for Outgoing Calls on Route 10:
3514>10>1 (default)
11. Set SMDR for Incoming Calls on Route 10:
12. Allow SMDR for Station to Station calls in Service Restriction Class A (00-15)
15213>00-15>0 (not default, requires system software R11)
13. Save changes:
EC6>0>0
1.2.2.
SMDR Output over an IP connection (MP)
To provide some assistance, a simplified procedure for direct SMDR output from the Main
Processor (MP) is given below. More information can be found in the SMDR section of the
'SOPHO 2000 IPS Feature Programming Manual'.
1. Use MP built-in SMDR:

08>800>0
2. SMDR via LAN port:

0401>05>0
3. Extended SMDR Format (KH and KI records):

0401>08>00
OR
Former SMDR Format (KA and KE records):
0401>08>15
4. Set Parity on (required for Call Reporting Module version 9):

08>827>1
5. Set Odd Parity (required for Call Reporting Module version 9):
08>828>0
6. Set SMDR for Outgoing Calls from Station 203:

1306>203>1 (default)
7. Set SMDR for Incoming Calls to Station 203:
8. Set SMDR for Outgoing Calls on Route 10:
3514>10>1 (default)
9. Set SMDR for Incoming Calls on Route 10:
10. Allow SMDR for Station to Station calls in Service Restriction Class A (00-15)
15213>00-15>0 (not default, requires system software R11)
11. Save changes:
EC6>0>0
1.3.
HOW TO CONFIGURE SV7000 SMDR OUTPUT
A SOPHO SV7000 must be prepared to deliver SMDR records to the Accounting Server. To
provide some assistance, a procedure for direct SMDR output from the SOPHO SV7000 is
given below. More information can be found in the SMDR section of the ' Business Data
Programming Guide'.
For receiving SMDR records from a SOPHO SV7000 an IP connection is sufficient.
General settings:
1. ASYD SYS=1, INDEX=3, bit0, bit7
bit0: 1=SMDR output per tenant.
bit7: (Optional) 1=SMDR output for internal station to station calls.
2. ASYD SYS=1, INDEX=18, bit4
SMDR incomplete message output: 0=Out of Service 1=In Service.

Note: An error message will be output when the PBX's responds to a Data Request but does not
receive a Client Response Ack.
3. ASYD SYS=1, INDEX=20, bit7
Who is billed in the case of Station-A calls Station-B who is Call Forwarded-Outside:
0=Station A billed 1=Station B billed.
4. ASYD SYS=1, INDEX=32, bit0, bit1, bit2, bit5, bit6 and bit7
Bit0: Hotel/Motel Feature. When SMDR fails, outgoing calls are: Allowed (0) or Restricted
(1).
Bit1: Tenant number for station and route will appear in SMDR record: 0=No 1=Yes.
Bit2: What appears in SMDR Fields 59~61: 0=ARNP Code 1=Route Number.
Bit5: Include 'dialled' access code in SMDR Called Party field: 0=No 1=Yes.
Bit6: Include digits dialled or digits sent in SMDR except access code 0=No 1=Yes.
Note: This bit will affect the entire PBX. Also see ARTD CDN121
Bit7: 1=SMDR enabled.
5. ASYDL SYS=1, INDEX=576, bit2
bit2: 1=SMDR interface is TCP/IP.
6. ASYDL SYS=1, INDEX=578, bit0 and bit4
bit0: 1=SMDR Format is Flexible Interface format.
bit4: 1=SMDR A LAN interface is enabled.
7. ASYDL SYS=1, INDEX=589, bit0
bit0: MA-ID included in SMDR: 0=No 1=Yes.
The next steps are optional. If you use one system, do not execute these steps.
bit4: 1=SMDR B LAN interface is enabled.
bit4: 1=SMDR C LAN interface is enabled.
bit4: 1=SMDR D LAN interface is enabled.
To enable SMDR for a route (CCIS, for example):
1. ARTD get route data (only for real routes; not for dummy routes) and assign:
CDN10=1: outgoing SMDR in service
CDN16=1: outgoing and incoming calls

CDN28: Is Answer Supervision In Service
To enable SMDR for stations:

1. ASFC(N) assign SMDR service for the appropriate SFCs, enable:
SFI=14: SMDR for trunk calls
SFI=58: SMDR for internal station to station calls: 0=No 1=Yes
Note: If this CDN is set to '1', then the SMDR record will begin when Answer Supervision has
taken place. If this CDN is set to '0', then ASYD System Data 1, Index 156 (for overlap
trunks) or Index 157 (for en-block trunks) will be followed.
10
2.
INSTALL AND CONFIGURE BUFFER BOXES
Buffer boxes are mainly used in 2000IPS installations with TABS v7 because of the small buffer
capacity of the switch. However the box can also be used for other platforms. We support 3
types of buffer boxes:
1. Data Xpress Remote Access Buffer Box (Smart Buffer Plus Box), used to buffer SMDR
records from 2000IPS switches or FDCR records from iS3000;
2. ComboX, used to buffer FDCR records from iS3000 with system software 8.05
3. TOPS box, used to buffer FDCR records from iS3000 with system software 8.05
2.1.
DATA XPRESS REMOTE ACCESS BUFFER BOX
A Data Xpress buffer box is used to buffer the SMDR records produced by the SOPHO 2000
IPS or FDCR records from the IS3000. The Data Xpress buffer box is the successor of the
Smart Buffer Plus box. The box is accessed by the Accounting Module on polling bases to
collect and process the SMDR/FDCR records.
Note: The existing Smart Buffer Plus boxes are still supported, configuration is exactly the same
as described here for the Data Xpress buffer box
The Data Xpress buffer box has two 9-pin V.24 connectors; one is marked as PC and the other
as AUX. When the AUX port is connected to a SOPHO 2000 IPS port (MP or AP00), the
maximum speed between the Data Xpress buffer box and the 2000 IPS or is3000 IS 19200
bps. The PC port is used to configure the Data Xpress buffer box. The SMDR/FDCR collection
is done using FTP (File Transfer Protocol) over a LAN or by dialling in with a modem (using a
proprietary protocol). The Data Xpress buffer box comes in two versions: one with a NIC and
one with a NIC and a built-in modem.
The minimum capacity of the Data Xpress box is 4 Mbyte. Assuming that an SMDR/FDCR
record is 128 bytes, the capacity is 32000 call records.
2.1.1.
Configuration of the Data Xpress Remote Access Buffer Box
A Data Xpress buffer box is delivered with a CD-ROM that contains the Data Xpress
configuration software. For configuration, you must connect the PC port of the Smart Buffer
Plus box to a COM port of the PC with a 'Null modem' cable, supplied with the Data Xpress.
PROCEDURE: How to configure the Data Xpress Remote Access Buffer

Box
Actions
11
1. Install the Data Xpress program from the CD (\Data Express

Software\setup.exe) on an available PC, this can be your labtop, since the software is
only used to configure the box.
2. Connect the COM1 port of the PC to the PC port of the Data Xpress box.
3. Run the Data Xpress Setup via Start>Program Files>Data Xpress>Data Xpress
4. Select COM1 in the Port/Modem field and press OK
5. Select FTP Server in the Calls Download Configuration field and enter the IP address,
subnet mask and Router information. This is the fixed IP address you want the Data Xpress
box to use. Press Send to send the information to the box.
6. Press Configure to the set the communication details:
- Speed: 19200;
- Parity: None;
- Data Length: 8;
- Stop bits: 1;
Press Send to send the information to the box.
7. Press Info, select User the current username (ANONYMOUS) and password (Empty)
is shown. Press Close and OK to reboot the box.
8. From now on the box can be reconfigured via the TCP/IP link. The address is: http://
IP-address of the box/fifoftp.htm and login as ANONYMOUS. This way you can
also change the username.
2.1.2.
Calculating How Often You Need to Access the Smart Buffer Plus
Box
The Smart Buffer Plus box holds up to 32000 call records. The length of time the Smart Buffer
Plus box can be left without being accessed, depends on the amount and type of calls that the
ISPBX is expected to handle within a given time.
Use the following formula to calculate how often the Smart Buffer Plus box needs to be polled:
Number of generated records = 1.10 * (number of internal calls + 1.05 * number
of incoming calls + 2 * 1.05 * number of outgoing calls)
This formula allows for a 10% overhead caused by transferred calls and 5% caused by
operator assistance; and assumes all SMDR/FDCR options are switched on. If SMDR/FDCR
records are generated for outgoing calls only, the Smart Buffer Plus box can store y calls.
If this information is not available, the following formula can be used to predict the number of
SMDR/FDCR records during office hours:
Number of generated records per hour = number of extensions * 5 * 1.10
12
This formula is based on the following assumptions:

-
all SMDR/FDCR options are switched on

for internal calls 0.04 E is generated with holdtime of 60 seconds
for incoming calls 0.04 E is generated with holdtime of 120 seconds
for outgoing calls 0.04 E is generated with holdtime of 120 seconds
5% of the incoming and outgoing calls are established via operator assistance
10% of the calls are transferred to another extension
2.2.
ComboX
The TOPS box supported for installations of TABS v7 and SOPHO iS3000 only.
A ComboX can be used for storing FDCR records. For details about the ComboX, see
Management@Net TABS Call Reporting Module Installation Guide. The formula's given in
the previous section also apply to the ComboX. The following sections are based on the use
of the ComboX only for storage of FDCR records.
2.2.1.
Making Physical Connections
PROCEDURE: Connecting the ComboX to the ISPBX and the modem at

the Remote Site
Actions
1. Using OM commands, prepare a port on the ISPBX for FDCR. This port must use
Character protocol, and must be set to 19200 bps in order to match the default port
setting on the ComboX.
2. Reset the ComboX to its factory settings as follows:
- Set Dipswitch 1 to OFF.
- Press the 'RESET' button on the rear of the ComboX.
- Set Dipswitch 1 to ON.
3. Connect Port 2 on the ComboX to the ISPBX FDCR port.
4. Make sure that the dip switches on the ComboX are all set to 'On'.
5. Connect Port 3 on the ComboX to a modem.
2.2.2.
Configure Connections using the Connection Manager Database

Configurator
This procedure includes downloading data to the ComboX.

1. Start the CM Database Configurator on the Management@Net PC and run the
13
Configuration Wizard (by default, this starts automatically).

2. On the 'Connection Wizard - Connection type' dialogue box, select 'Remote connection
to ISPBX via buffer or port selector'.
3. Complete the Connection Wizard screens for the FDCR connection, making sure that
you:
- Select 'Buffer' and 'ComboX' in the 'Connection Wizard - Destination buffer or port
selector' dialogue box.
- Do not change any modem settings in the Connection Wizard - ComboX modem
settings dialogue box.
- Do not change any passwords in the Connection Wizard - ComboX FDCR Port
Passwords dialogue box.
- Check that the port speed is 19200 in the Connection Wizard - FDCR Port Settings
dialogue box, in order to match the default port setting on the ComboX.
- Select a port speed of 19200 in the Connection Wizard - COM Port Modem Settings
dialogue box (or choose suitable previously-specified COM port(s) in the Connection
Wizard - Select COM Port dialogue box). You must select a speed of 19200 to match Port
3 on the ComboX - the baud rate of which cannot be changed.
4. Update the ComboX settings as you are prompted. You should get a message box with
text: ComboX settings have been modified. Do you want to update ComboX settings
now? Press Yes.
5. You can manually update the ComboX settings using Tools: Send ComboX settings (this
is in the main menu, outside of the Connection Wizard). This can only be done if you have
selected the correct ComboX from the list of ComboXs in Connection Manager
Database.
6. Continue with the Site Setup as described in the Management@Net TABS Call Reporting
Module Installation Guide.
2.3.
TOPS BOX
The TOPS box supported for installations of TABS v7 and SOPHO iS3000 only.
A local or remote TOPS box is used to buffer the FDCR records produced by the ISPBX. Then
the TOPS box is accessible by the TABS Call Reporting Module to process the FDCR records.
The maximum speed between TOPS and Management@Net is 38400 bps.
The maximum speed between TOPS and ISPBX is 4800 bps for a TOPS box containing a 6
MHz crystal and 9600 bps for a TOPS box wit a 12 MHz crystal. This crystal is the middle one
on the PCB of the TOPS box. The EPROM (the one on a socket) must be of type 2DQ-TGL.
14
To check this, you need to open the TOPS box.

Note: Your TOPS box might even contain a more modern EPROM version. Different EPROM types
can have influence on the amount of records, that can be stored in the TOPS box. For more
information on the used hardware: activate the Site Setup in the TABS module and consult
the hardware tab in Sites/Define Site. After TOPS is connected with the
Management@Net, the screen will give information about the used hardware inside the
TOPS box. (This procedure can be found in the TABS Installation guide).
2.3.1.
Calculating How Often You Need to Access the TOPS Box
The TOPS box holds up to 6382 FDCR records. The length of time the TOPS box can be left
without being polled, depends on the amount and type of calls that the ISPBX is expected to
handle within a given time.
Use the following formula to calculate how often the TOPS box needs to be polled:
Number of generated records = 1.10 * (number of internal calls + 1.05 * number
of incoming calls + 2 * 1.05 * number of outgoing calls)
This formula allows for a 10% overhead caused by transferred calls and 5% caused by
operator assistance; and assumes all FDCR options are switched on. If FDCR records are
generated for outgoing calls only, the TOPS box can store 6382 / 2 = 3191 calls.
If this information is not available, the following formula can be used to predict the number of
FDCR records during office hours:
Number of generated records per hour = number of extensions * 5 * 1.10
This formula is based on the following assumptions:
-
all FDCR options are switched on

for internal calls 0.04 E is generated with holdtime of 60 seconds
for incoming calls 0.04 E is generated with holdtime of 120 seconds
for outgoing calls 0.04 E is generated with holdtime of 120 seconds
5% of the incoming and outgoing calls are established via operator assistance
10% of the calls are transferred to another extension
Note: A TOPS Box is not required if the ISPBX has a BIM or a ServicePlus Box, since a BIM or
ServicePlus Box can also buffer FDCR records.
15
3.
CALL REPORTING MODULE INSTALLATIONS
3.1.
INTRODUCTION
TABS Call Reporting Module is used to collect SMDR/FDCR call records from the switch and
to generate reports based on the data collected. A CRM application licence is required and a
CRM equipment licence for each connected PBX (unit). NEC Philips delivers the TABS v7
Call Reporting module as part of Management@Net for IS3000 networks and a
stand alone version for 2000IPS installations.
The TABS Call Reporting Module consists of the following applications:
TABS
TABS is used to generate reports and to define the site parameters, pricing structure etc.
TABS is located in the program group.
TABS Call Collector
The TABS Call Collector is responsible for the collection of data, in accordance with the
settings made in TABS and can be found via the Start menu, in Programs, Startup.
The TABS Call Collector is started automatically, upon 'login'.
TABS Web Access
TABS Web Access is the web based user interface used to generate reports.
For more information about the TABS Call Reporting Module, see also:
-
Management@Net TABS Call Reporting Module Installation Guide.

The TABS Call Reporting Module's on-line help.
3.2.
BEFORE USING THE TABS CALL REPORTING MODULE
The TABS Call Reporting Module Licence is required and an equipment licenses for each
connected ISPBX (unit).
Before you are able to do Reporting in TABS, a printer must be defined. Even if you only do
Preview or Print-to-file.
3.3.
HOW TO CONNECT TABS v7 USING MANAGEMENT@NET
When TABS v7 is part of a Management@Net installation connections are based on the

Management@Net Connection Manager. Furthermore data is shared between TABS and
other modules (MAC Manager and Phonebook). To configure this correctly, closely follow the
Initial filling procedure as described in the Data Distribution chapter of the
Management@Net Installation Guide.
16
3.4.
CONNECT STAND ALONE TABS v7 SUITE TO AN 2000IPS
This section describes the procedure to follow to configure to TABS v7 Suite to an 2000IPS
switch. There are three possible configurations:
1. TABS Single Site, direct connection over V.24;
2. TABS Multi Site, connection via Smart Buffer Plus box over IP;
3. TABS Multi Site, connection via Smart Buffer Plus box via a modem;
Access to TABS is restricted after configuration the default user TABS, password TABS can
be used to gain access to the system. After installation the system is not completely initialised
follow the procedure below to do so, and then continue with one of the
PROCEDURE: Starting TABS for the first time

If you start TABS for the very first time, you get a number of screens that you have to go
through before you get to the site setup. Follow the procedure below and, above all, be
patient with the system.
Actions
1. After starting TABS, you get a Setup box showing: Initializing on first entry. Please wait...
Just be patient and wait for the next screen.
2. The Setup box shows:
Your system has not yet been fully configured. Press OK to complete the installation
process. Press Cancel to quit
Press OK.
3. The Setup box shows: To continue installing the TABS system, the following procedures
must be performed: followed by two check boxes: Connecting to hardware devices and
Importing Costing/Organizational data and Please select Setup options.
Select Connecting to hardware devices and press OK.
Note: Importing Costing/Organizational data (the VLISTs) can always be done later.
4. Now, an Install box shows:
You may now define the connection(s) to your PBX(s)...
Press OK.
5. You now enter the site setup screen. Follow one of the procedures described below.
PROCEDURE: TABS Single Site Direct V.24 Connection

The following procedure describes the TABS Setup for a SOPHO 2000 IPS Site with a direct
SMDR connection. This also requires special settings to force TABS to stay on this site. These
17
settings are mentioned under Additional Information in the procedure below.

Actions
1. Start TABS.
If this is the first time, follow the procedure Starting TABS for the first time as described
above and then go to step 4 below.
2. Select Setting Up and Define Site.
3. Press Add.
4. Select the General tab.
5. After Name, enter a site name.
6. Under Hardware Location, select None.
7. Under Site Directory Type, select Not Shared.
8. Select the Polling tab.
9. Under Connect Every, set the Frequency and Period to once per day or longer.
10. Under Polling policy, select Collect all records.
11. Select the Communication tab.
12. Under Communication Parameters, select the COM port.
13. Select the Hardware tab.
14. Press the PBX button and select SOPHO 2000 IPS from the list. Press Edit
15. In the Edit screen, select the speed (Baud) from the drop down list.
16. Select Save from the File menu and Exit.
17. Press Apply and Reset this site.
Additional Information
Additional settings to ensure that the Call Collector stays connected to this single site:
1. Find the file tabsite.ini in the site directory (Hilversum, for example). Open this file
with Notepad.
- Find the tag [<site name>.Connection]. For example [Hilversum.Connection]
- Add the following line under this tag: DisconnectAtTheEndOfPolling=False
Note that it is one string and that it is a combination of small and capital letters
- Save and close the file.
2. Make sure that the site is NOT default site. Open TABS and select Setting Up/Setup/
Polling Options and check that you have No Default Site.
3. Change the startup setting of the Call Collector as follows:
- Right click on the TABS Call Collector (Startup group) and select properties.
- Change the Target field to C:\Program Files\Philips\TABS\callproc.exe
-FromApp So, in fact you add after the existing target a space and -FromApp
18
PROCEDURE: TABS Multi Site Buffered Connection over IP

The following procedure describes the TABS Setup for a SOPHO 2000 IPS Site with a Data
Xpress Remote Access Buffer Box connected via a LAN (IP).
Preconditions
The Data Xpress buffer box is configured and connected to the system see: 2.1. "DATA
XPRESS REMOTE ACCESS BUFFER BOX"
Actions
1. Start TABS.
3. Press Add.
CAUTION:
IF 'SHARED' DIRECTORY IS USED, THE PBX NAME IS LIMITED TO

FOUR CHARACTERS!
6. Under Hardware Location, select File.
7. Under Collection Type, you see Voice. Do not change.
8. Under Site Directory Type, select Not Shared or Shared.
CAUTION:
FOR CENTRALISED BILLING, YOU HAVE TO CHOOSE 'SHARED'

DIRECTORY.
10. Under Communication Parameters, select FTP and Ethernet.
11. Under Destination Parameters, enter the file name (fifoftp.txt) after File Path.
12. As Remote Access Parameters, fill in the IP Address and the Login name (ANONYMOUS)
and a possible Password of the Smart Buffer Plus box.
14. Press the PBX button and select SOPHO 2000 IPS from the list. Press OK.
16. After Base Connection Time, set the time that the polling should start.
17. Under Polling Policy, select Collect for x Minutes.
18. Under Get File Data, set the Frequency and Period.
20. Repeat this procedure until all sites have been defined.
19
PROCEDURE: TABS Multi Site Buffered Connection via a Modem

The following procedure describes the TABS Setup for a SOPHO 2000 IPS Site with a Data
Express Remote Access Buffer Box connected via modems.
Preconditions
The Data Express buffer box is configured and connected to the system see: 2.1. "DATA
XPRESS REMOTE ACCESS BUFFER BOX".
Actions
1. Start TABS.
3. Press Add.
CAUTION:
IF 'SHARED' DIRECTORY IS USED, THE PBX NAME IS LIMITED TO

FOUR CHARACTERS!
6. Under Hardware Location, select Other and SBP from the drop down list.
7. Under Collection Type, you see Voice. Do not change.
8. Under Site Directory Type, select Not Shared or Shared.
CAUTION:
FOR CENTRALISED BILLING, YOU HAVE TO CHOOSE 'SHARED'

DIRECTORY.
10. Under Communication Parameters, select COM port (Via Ports), speed (Baud Rate) and
Dial-Up-PhoneNo.
12. Press the PBX button and select SOPHO 2000 IPS from the list. Press OK.
14. After Base Connection Time, set the time that the polling should start.
15. Under Connect Every, set the Frequency and Period.
16. Under Polling Policy, you see Collect all records. This is OK.
18. Repeat this procedure until all sites have been defined.
20
4.
EXPENSE CONTROL SUITE INSTALLATIONS
4.1.
INTRODUCTION
Like the Call Reporting Module, the Expense Control Suite (MAS v9) is used to collect call
records from the switch and to generate reports based on the data collected. MAS v9 is the
successor of TABS v7 but is based on a complete new design.
The main design changes in MAS v9 are:
SQL Based
MAS v9 is a web based UI on top of a MSDE/SQL server. Everything the user does is
translated into SQL commands and can be scheduled as a SQL agent job. The SQL Agent
must be running on the MAS MSDE/SQL instance at all times.
Call Collector
There is no separate Call Collector the MAS v9 The collection and parsing of data, is done
via services that run in the Background of the Management@Net server.
The TABS Call Collector is started automatically, upon 'login'.
License
The licensing in MAS v9 is based on a capacity licence, i.e. a license per device that is
monitored.
Note: Devices are extensions, trunks, pin-codes, virtual numbers etc.
WARNING: MAS V9 LICENSES ARE DEPENDABLE ON THE HARDWARE AND
CAN ONLY BE GENERATED BY THE ORDERDESK AFTER
INSTALLATION. MAKE SURE YOU SEND THE REQUEST FOR THE
LICENSE FILE IMMEDIATELY AFTER INSTALLATION.
Direct output via TCP/IP for multiple sites
The licensing in MAS v9 is based on a capacity licence, i.e. a license per device that is
monitored.
Self learning
New devices will be added to the MAS v9 database automatically when the SMDR record
arrives.
Data Distribution
MAS v9 is a stand alone application, however data synchronisation with MA4000 is
included in the product. Synchronisation with MAC manager and Phonebook (spider) is
not supported.
21
4.2.
BEFORE USING MAS v9
SMDR output has to be configured on the PBXs, see also 1. "ISPBX PROJECTING FOR
ACCOUNTING".
When you start the Expense Control Suite you have to login with a user registered in
Management@Net. In Central Authentication it is registered for this user which user to use
to login to MAS v9. The default user that is in the MAS database is Admin, password doe.
when you login the first time the system requires you to set a new password for this user.
4.3.
MASv9 LICENSE MECHANISM
With the introduction of the MAS 9 stand alone version, we also introduce the standard MTS
licensing mechanism. This mechanism differs from the NEC-Philips licensing mechanism and
does not use the dongle any more. The new licence mechanism requires information of the
PC, where the application will be installed. This information is gathered in a so called
'protect.dat'
Activation of the licences will be done on site. Note: You must obtain a licence for MAS 9
within 30 days of installing the product. The following procedure should be followed to
activate the licences:
-
To get a MAS 9 licence and you want the licence the same day, you're advised to begin
with MAS 9 installation at the start of your customer visit. Make sure you have the
product's order number and the MAS 9 file protect.dat. Instructions are given on the
Licence activation sheet, which is sent together with the MAS 9 order by NEC Philips.
The order number and protect.dat file should be sent to the supply centre (the email
address will be specified on the Licence Activation sheet). Supply centre of NEC Philips
sends a new protect.dat file to the email address where the protect.dat file was coming
from.
4.4.
INSTALLATION OF MASv9
This book does not describe the actual installation of the product. Refer to the Expense
Control Suite MAS v9 Installation Guide. At the end of the installation the configuration wizard
starts automatically, please skip this and reboot the server first to finalise the installation.
4.5.
CONFIGURATION OF MASv9
This manual describes the basic configuration steps required to collect calls from a supported
PBX and enter them into the database. For more information on configuration see the
22
Expense Control Suite (MAS 9) Installation Guide. This Installation Guide is leading, this section
provides information on NEC Philips specific settings and useful tasks to perform:
1.
2.
3.
4.
5.
6.
How to backup the MASv9 database;

How to use the MASv9 Installation Wizard;
How to manually define a data source;
How to manually create a data collector;
How to use the Generic Personnel Import tool
How to manually assign a range of extensions;
4.5.1.
How to Backup the MASv9 Database
The MASv9 is SQL based, creating backups on an SQL server is done via the SQL Server
Agent. In the following tasks you will import user/extension information and create the data
collectors. If there are problems during the execution of these tasks you might want to go back
to the initial situation. Please execute this backup procedure before entering any other
information into the database. Repeat this procedure at the end of this section.
PROCEDURE: Create backups in MASv9.

Preconditions
Make sure the SQL server Agent is up and running. MASv9 must be installed and ready to use,
see the Expense Control Suite (MAS 9) Installation Guide for more info.
Actions
1.
2.
3.
4.
5.
Login to MASv9 with username Admin (Default password doe).

Browse to the Maintenance>Task Manager part.
Select DB Maintenance from the list on the left, a wizard starts.
Enter a name for and description for the job you are creating and press Next
Select Database Backup from the drop-down list and change the backup directory if
required. The default backup directory is C:\Program Files\TABS\BACKUPS\. Press
Next.
6. Press Schedule If you want to schedule this job to run repeatedly, for instance once every
day at 01:00. To make sure the job will run make sure the SQL Server Agent is set to startup automatically.
7. Press Save to save the job. The focus returns to the current jobs in the Task Manager
window. The backup job can be found in the list. Enable the job with the action button at
the top of the list and execute it to create the default empty database backup.
23
WARNING: EVERY BACKUP IS SEPARATELY STORED IN A FOLDER WITH THE

TIMESTAMP OF THAT BACKUP. BACKUP FILES ARE NOT
AUTOMATICALLY REMOVED FROM THE SYSTEM. EVENTUALLY
THE HARDDISK WILL BE FULL. MAKE SURE BACKUP FILES ARE
REMOVED FROM THE SYSTEM AND STORED IN A SAFE PLACE.
4.5.2.
How to Use the MASv9 Installation Wizard
The Installation wizard is skipped at the end of the installation to allow for a system reboot and
creation of a default backup of the empty database. The wizard can be started after the reboot
via c:\program files\TABS\Bin\Setup Wizard.exe.
PROCEDURE: MASv9 Installation Wizard

Preconditions
MASv9 must be installed and ready to use, see the Expense Control Suite (MAS 9) Installation
Guide for more info. Also the procedure: PROCEDURE: "Create backups in MASv9." must be
executed to obtain a backup of the empty database.
Actions
1. Start the Installation Wizard and select Create New Site
2. Enter the following parameters before pressing Next:
- Root Name - this can be best compared with the name of the network;
- Site Name - when you want to create a new site, the site in MASv9 is the name of the
network, not the unit like in TABSv7;
- Select the correct time zone in the GMT Offset drop-down list;
- Select a Business Hours Scheme or create a new one.
- Select the Routing priorities according to which the calls must be routed in the cost
plan. I.E. if your costplan provides for multiple providers with different trunks, make
sure that the By Trunk priority is higher than the Default Service priority, else all
calls will automatically be calculated according to the cost plan of the default provider.
if you do not know this at this point the priority can be changed later.
24
3. In the Create new data source window add the following information before pressing
Next:
- Name - the name of the data source. The collection of calls in MASv9 is based on data
sources. For every connection to a PBX or PBX network a separate data source must
be defined. A data source in MASv9 can be compared with the site in TABSv7;
- Node - can be ommitted;
- Type - select PBX.
4. In the Define Collection Parameters window add the following information before
pressing Next:
- Name - the name of the Data collector job responsible for collection the calls;
- Description - any description;
- DC Type - the data collector type. Select DC TCP (NEC) for 2000IPS or Sv7000
connections, select DC IS3000 Buffered for IS3000 connection with buffering on the
LBU, select DC IS3000 Streaming for direct output FDCR IS3000 connections, or
select DC FTP for connections to a buffer box;
- CR Type - the calls record type, select CR Raw Data;
- Ini file path - select for all NEC Philips switches the config.ini file;
- PD9 file path - the PD9 file translates raw call data into readable records, select
SOPHO 2000 IPS 2400.PD9 for the 2000IPS, select SOPHO810.PD9 for the IS3000
or select NECFusion.PD9 for the SV7000.
25
5.
6.
7.
8.
9.
Press the Schedule button to schedule the data collection (polling). In case of direct
output this can be skipped.
In the Define Data Collector window add the connection parameters for the data
collector and press Next
In the Define Call Recognizer window parameters can be set to ignore out of scope calls.
This can also be done by the customer in the reports definition. Press Finish to execute
the job.
Login to MASv9 with username Admin (Default password doe) and check the Org
Utilities part for the site and data source Org Utilities>Facilities>Telephony
resources.
Browse to the Maintenance>Task Manager part, and select the data collector, just
created. Enable and start the data collector job using the action buttons at the top of the
list.
Browse to the Maintenance>Monitor> part, and select Online Calls Monitor. Check if
the calls are collected.
4.5.3.
How to Manually Define a Data Source
The collection of calls in MASv9 is based on data sources. For every connection to a PBX or
PBX network a separate data source must be defined. A data source in MASv9 can be
compared with the site in TABSv7;
26
PROCEDURE: Define a data source

Preconditions
Actions
1. Login to MASv9 with username Admin (Default password doe) browse to the Org
Utilities part to create the data source Org Utilities>Facilities>Telephony
resources.
2. In the top left of the screen click on the New button (next to the search field. A new
group can be defined (e.g. company name) within a site or a site can be defined directly
under the main group.
3. If Site is selected a Web Page Dialog window is displayed, enter the following information:
- Name - enter the site name;
- GMT Offset - select the correct time zone;
- Status - select Active if this is a site you want to collect calls for;
- Business Hours - select an existing scheme or create a new one.
- Routing priorities - select the priority according to which the calls must be routed in
the cost plan. I.E. if your costplan provides for multiple providers with different trunks,
make sure that the By Trunk priority is higher than the Default Service priority, else
all calls will automatically be calculated according to the cost plan of the default
provider. if you do not know this at this point the priority can be changed later.
Press Update to store the information in the database.
4. Select the site you have just created and click on the same New button at the top of the
screen, now select Data source. A Web Page Dialog window is displayed, enter the
following information:
- Name - the name of the data source;
- Node - can be ommitted;
- Type - select PBX.
Press Update to store the information in the database.
4.5.4.
How to Manually Create a Data Collector
The data collector of MASv9 is a SQL based job that has to be created in the Maintenance
> Task Manager part of the UI. The properties of each data collector differ based on the
connection type and PBX. At the end of this section is an overview of the most important
27
properties (Table 4-1 "Data Collector Property Overview"). To manually add a new data
collector follow the next procedure:
PROCEDURE: Create a Data Collector

Preconditions
Actions
1. Browse to the Maintenance>Task Manager part, and select Data collector from the
left pane. A wizard is started.
2. In the General tab add the following information before pressing Next:
- Name - the name of the Data collector job responsible for collection the calls;
- Select the Data source from the drop-down list, every data-source requires its own
data collector. If the data collected is from a file that also contains the data-source (i.e.
a export file from MASv9) select the option Obtained from CDR (Call Details
Record).
3. In case of IS3000 streaming direct output FDCR, add the following information in the
Collector tab before pressing Next:
- DC Type - the data collector type. select DC IS3000 Streaming;
- Output to Parser - select True if the calls need to be parsed and stored in the
database directly, select False if the calls need to be stored into a file;
- Output File Path - enter name and path of the output file if Output to parser is false;
- Log File Path - the default log is xyz.log, this log is used to investigate errors if they
occur;
- Name of the PBX - enter a unique name for this connection;
- Host name or IP address - add the IP address of the switch.
- Socket Number - add the TCP/IP port number 2599;
- Unit Number - add the unit number of the PBX;
4. In case of IS3000 FDCR output buffered on the LBU, add the following information in the
- DC Type - the data collector type. select DC IS3000 Buffered;
28
Output File Path - enter name and path of the output file if Output to parser is false;
Log File Path - the default log is xyz.log, this log is used to investigate errors if they
occur;
- Name of the PBX - enter a unique name for this connection;
- Host name or IP address - add the IP address of the switch.
- Socket Number - add the TCP/IP port number 23;
- Unit Number - add the unit number of the PBX;
5. In case of 2000IPS/SV7000 streaming SMDR output, add the following information in the
- DC Type - the data collector type. select DC TCP (NEC) for direct TCP/IP;
- Port - add the TCP port number 60010;
- Protocol File Path - select NEC.dctcp.xml;
occur;
- Address - add the IP address of the switch.
6. In case of FDCR/SMDR output via a buffer box, add the following information in the
- DC Type - the data collector type, select DC FTP for connections to a buffer box;
- Path to Input File on FTP - enter the file name of the call data file on the buffer box
fifoftp.txt;
- Delete input file - select True;
- Port - add the TCP port number 60010;
- Ini File Path - select config.ini;
- Username - enter the FTP user configured on the buffer box (default
ANOYNYMOUS);
- Password - enter the password of the FTP user (default empty);
occur;
- Address - add the IP address of the buffer box.
- Use Remote Access Connection - select False.
7. For all data collectors add the following information in the Parser tab before pressing
Next:
- PD9 file path - the PD9 file translates raw call data into readable records, select
SOPHO 2000 IPS 2400.PD9 for the 2000IPS, select SOPHO810.PD9 for the IS3000
or select NECFusion.PD9 for the SV7000.
29
Output to Inserter - select True if the calls need to be stored in the database directly,
select False if the calls need to be stored into a file;
- Output file path - enter name and path of the output file if Output to inserter is false;
- Log Rejected - select True to log rejected calls in the xyz.log;
- Log Processed - only select True if error occur to log all calls in the xyz.log;
- Ini File Path - select config.ini;
- Ignore Out of Scope Calls - select True if you want to use one of the parameters
below, lime Minimal Call Duration, this can save space in the database, by for instance
excluding calls of less than 2 seconds. These calls can also be filtered out of the reports
later.
8. Press Schedule If you want to schedule this job to run repeatedly, for instance once every
hour from 0:00 to 23:59. Streaming Data Collectors do not need to be scheduled.
However in a multi-PBX environment include the streaming Data Collectors in
the polling schedule. The streaming collectors can stop unexpectedly when
polled collectors are started. Since data collection in MAS v9 is a SQL server job make
sure the SQL Server Agent is set to start-up automatically.
window. The data collector can be found in the list. Enable the job with the action button
at the top of the list and execute it to start the job.
30
PBX
iS3000
2000IPS
SV7000
Connection DC Type
Protocol File INI File PD9 File

-
Config.ini
SOPHO810.pd9
Config.ini
SOPHO810.pd9
DC IS3000
Buffered
Config.ini
SOPHO810.pd9
Buffer Box
DC FTP
NEC.dctcp.xml
Config.ini
SOPHO2000 IPS 2400.pd9
Direct IP
DC TCP (NEC)
NEC.dctcp.xml
Config.ini
SOPHO2000 IPS 2400.pd9
Direct IP
DC TCP (NEC)
NEC.dctcp.xml
Config.ini
NECFusion.pd9
Buffer Box
DC FTP
Direct streaming
DC IS3000
Streaming
Buffered on LBU
Table 4-1 Data Collector Property Overview
4.5.5.
How to use the Generic Personnel Import tool
MASv9 is self learning, if a call is collected from a device that is not yet in the database the
device is automatically assigned to the data source and a new device record is added to the
database. The device can be found in the Unassigned devises since the call is not assigned to
a user or hierarchy level yet, see Org Utilities > Personnel > Unassigned devices.
When you need to assign devices to the hierarchy structure the best way to do this is to use
the Generic Personnel Import based on an input file, for an example see Figure 4-2 "Example
genericimport.txt file.".
PROCEDURE: Generic Personnel Import

Actions
1. Browse to the Maintenance>Task Manager part, and select Generic Personnel
Import from the left pane. A wizard is started.
- Name - the name of this import job;
- Hierarchy - select Administrative to import the hierarchy of the company.
- Default Data Source - select the data source where this import is intended for, if the
data source name is in the input file, select Default Data Source;
- Full Update - Select the Full Update thick box for initial filling, all existing data will be
lost;
- Base Org Unit - If the database already contains a hierarchy and the import is intended
for one department instead of the complete company, select the department as Base
Org Unit;
3. In the Input tab add the following information before pressing Next
31
Local - select Local if the input file (genericimport.txt) is stored in the C:/Program
files/TABS/Bin/Input Files folder;
Upload - select Upload to upload the input file (genericimport.txt) to the C:/
Program files/TABS/Bin/Input Files folder;
On FTP - select On FTP if the input file is stored on a remote FTP server. Enter the
correct FTP parameters.
4. In the Fields tab the input file is mapped to MAS database fields this depends on the input
file that is provided by the customer mandatory fields are:
- Site Name (50 characters);
- Data Source (50 characters);
- Device (20 characters);
- Device Type - EXT (Extension), PIN (Pin Code); CC (Calling Card); or CEL (Mobile
phone);
- Employee ID (50 characters), preferred not mandatory;
- First Name (20 characters), optional if Org Unit Path exist;
- Last Name (20 characters), optional if Org Unit Path exist;
- Org Unit Path (32 characters) mandatory if no first and last name exist (example:
Company\Division\Department);
- E-mail Address (50 characters) preferred not mandatory;
Figure 4-1 Generic Personnel Import Wizard
32
Figure 4-2 Example genericimport.txt file.

5. Enter the following information before pressing next:
- Start at row - enter 1 if the input file has no header, enter 2 if the import file has a
header. The example above has a header line;
- Field Delimiter - enter the character that separates the fields in the import file, in the
example above it is a comma (,);
- OU Path Delimiter - enter the character that separates the company form the
divisions and the departments in the Organizational Unit (hierarchy), in the example it
is a backslash (\)
- To map the import file to the database press the Select Fields button, a wizard opens.
Now add the import field in the correct order to the import job. In the example the
first field is Site, then Data Source, then Device etc. Every time a new field is added it
will get an index number. This index is crucial, index 1 means first column in the import
field, index 2 means second column, etc. Press OK to save the changes.
- The job is now ready for the import, review the settings closely, you can change the
index of an import field by selecting the field and than change the value in the Index
of field in input row box. When all is correct press next.
window. The Generic Personnel Import job can be found in the list. Enable the job with
the action button at the top of the list and execute it to start the import. The job can be
scheduled to run as well.
4.5.6.
How to Manually add a Range of Extensions
When you need to assign devices to the hierarchy structure the best way to do this is to use
the Generic Personnel Import based on an input file See 4.5.5. "How to use the Generic
Personnel Import tool". If the customer does not provide a input file and you still have to
assign the devices to a hierarchy structure follow this procedure.
PROCEDURE: Manually add a range of extensions

Actions
33
Guide for more info. Data sources must be defined.
1. Browse to the Org Utilities > Facilities part, and select the Data source you
want to add the extension to. In the middle pane click the button Add Device Range to
add a range of devices a wizard starts. Select Device Type: Extension and the range;
2. Browse to the Org Utilities > Personnel part, and manually create the hierarchy.
To do so use the New button next to the search field at the top of the UI;
4.6.
MAS version 9.5.5 SYNCHRONISATION WITH MA4000
MAS version 9.5.5 integrates with MA4000 version 5.0. Roughly speaking this includes:
Synchronization of Application Suite's database with MA4000's database. This can be done in
one of two ways:
1. The DataSync job for synchronizing with the MA4000. The Application Suite requests this
process. The DataSync is always Full - data which was imported from the MA4000 and
exist in the Application Suite but not exist any more in the MA4000 DB will be deleted.
2. Notification. - MA4000 updates the Application Suite automatically with every action
which is performed (add, edit, delete). This process is started automatically after the
DataSync job is enabled started for the first time.
Note: The synchronisation is one direction only. After synchronisation MA4000 becomes leading,
any device, or contact that came from the synchronisation cannot be changed in the MAS
UI. This to avoid the databases to get out of sync.
PROCEDURE: Synchronise MAS v9 with MA4000

Actions
34
1. Start MAS, Select the Maintenance > System Settings.

2. From the dropdown box select NEC Settings.
3. Fill in the MA4000 database properties and save them.
- Remember MA4000 runs on its own database instance, so include the instancename
in the servername field.
- Instead of using SA as a username use the default MA4000 user name: agile, the
password for this user can be found in Agile.config (C:\Program
Files\NEC\Agile\Manager\PrivateBin).
4. Go back to the Maintenance > Task Manager and select Import\Export from the list,
a wizard starts.
- Name - the name of this import job, i.e. MA4000 DataSync;
- Description - any description.
6. In the Component tab add the following information before pressing Next:
- Data Source Type - MA4000;
- Site Name - enter Default Site if this is a new installation or the name of an existing
site.
window. The MA4000 DataSync job can be found in the list. Enable the job with the
action button at the top of the list and execute it to start the import. This will create the
Data collectors, Data Sources (Sites) and import the extension, user and hierarchy
information from MA4000. The job can be scheduled to run as well, mind you the job is
always a Full synchronisation, every time it runs.
4.7.
MAS v9 GENERAL MAINTENANCE AND TROUBLESHOOTING
This section contains a number of procedures to be used for maintenance and trouble
shooting.
4.7.1.
Patches
PROCEDURE: How to Check for Installed Patches

Actions
1. Use SQL server Enterprise Manager
2. Select the MAS database instance and open the System database
3. Open the View table VersionInfo, the value VersionValue is the patch number.
Or
1. login to MAS and Launch the about About Window via the link in the top of the screen.
35
2. Check 5th position in the version, that value means the # of the latest patch (e.g.
9.5.2.1.85 is patch 85)
PROCEDURE: How to Install Patches

Actions
New MAS v9 patches come in the form of a *.zip file. This file can be loaded by a special utility
tool.
1. Verify that the zip file has the following structure: Patches - PatchXX
2. Copy the zip file into the <Program Files>\MAS\Patches folder
3. Launch Utilities.Management.exe from the Utilities directory in <Program
Files>\TABS\Utilities and select tab System.
4. Select Run to install the patches.
4.7.2.
Management Utility
The Management Utility window holds a set of tools created for individual with System
Administrator access. Its assists the user to:
1. Create additional system settings
2. Fix administrator or user errors, e.g., If the IS Virtual Director was deleted my mistake
3. Change some settings from the default ones created during installation
To access the Management Utilities window, navigate to the <Program
Files>\TABS\Utilities. Double-click on Utilities.Management.exe.
36
Figure 4-3 MAS Management Utility tool

The following tasks can be performed with this tool:
1. Restore tab
- To restore a backup or archived calls, select the backup or archive file and click
Restore data
2. System tab
- When a new system language is chosen the cache memory can be cleared, cache
memory usage can be disabled altogether.
- To restore the virtual directory of the web pages to the default values click Recreate
Virtual Directory
- To delete duplicate calls from the database click Delete Duplicate Calls
37
To unlock the Systems Administrator after 3 attempts to login (which has lead to a
system lock), click Unlock administrators
- To install patches browse to the Unlock administrators
3. Clean DB tab
- Organisational data, Rating data or both can be cleared, select the required option an
click Clear
4. Vlist Convert tab
- MAS v9 uses XML based vlists, old TABS v7 vlists can be converted. Select the import
and output file, and click Prepare Vlist Unselect Default ANSI encoding if the Vlist
contains its own encoding, e.g German characters.
5. Printers tab
- Select a network printer which will be used for output from MAS, e.g., Reports, and
click Apply
4.7.3.
Raw Data Exporter
Unlike TABS v7 raw data is not stored in the database by MAS v9. The application stores the
calls into the database after calculation of the costs, this to improve search an report
capabilities. In some cases raw data is required, for instance to import the calls into a new
installation. The Raw Data Exporter can be used to recreate the raw data from the call data.
To access the Raw Data Exporter, navigate to the <Program Files>\TABS\Utilities.
Double-click on Utilities.RawdataExporter.exe.
4.7.4.
Stop and Start Services
MAS v9 operates based on a number of services and background processes. These are
automatically started after a reboot of the server. To stop and start services in the correct
order without a reboot the Utilities.ConfigForm tool is added to the system.
To access the Utilities.ConfigForm, navigate to the <Program Files>\TABS\Bin. Doubleclick on Utilities.ConfigForm.exe.
4.7.5.
Migration TABS v7 to MAS v9
It is possible to migrate the following information from TABS v7 to MAS v9:

-
38
Sites (= Data source)

Extensions (= Device type extension)
Accounts (= Device type PIN codes)
Trunks (= Device type trunk)
Organization layout (= Organisational unit)
Cost centres
Costing
Calls
PROCEDURE: How to migrate TABS v7 to MAS v9

Actions
1. Install MAS v9 on a new server or upgrade the existing server.
2. When a new server is used copy the following TABS v7 files/folders to the new server,
keep the exact same drive and folder names:
- Db folder (C:\Philips\Data Files\TABS\db)
- Tabswin.exe (C:\Program Files\Philips\TABS\tabswin.exe)
- Tabsetup.ini (C:\Program Files\Philips\TABS\tabsetup.ini)
- Tabscom.ini (C:\Program Files\Philips\TABS\tabscom.ini)
- Tabspath.ini (C:\WINNT\tabspath.ini or C:\WINDOWS\tabspath.ini)
3. Start the migration via the Migration.Process.exe tool from the directory: Program
Files\MAS\Bin\
4. Wait till the migration is finished, be patient with the system.
4.7.6.
Reset the Administrator Password
The default MAS user is Admin, if the password of that user is lost you can reset it in the
database.
PROCEDURE: How to reset the Admin user password

Preconditions
The password of the MAS users are stored in the Organization database of MASv9, to rest the
password you must have access to that database, for instance via Enterprise Manager.
Actions
1. Login to the MASv9 SQL database instance using Enterprise Manager and Browse to the
Organization table.
2. Open the Users table.
3. Search for the Admin user and delete the password, the password is stored encrypted.
4. Set the value UserBlocked=0
5. Set the value CurrentRetry=0
Now the user Admin can login without a password. A new password can be set in the
Organizational Unit past of the UI.
39
40

Accounting Cem

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Accounting Cem

Uploaded by

Copyright:

Available Formats

CONFIGURATION GUIDE

3522 009 12651

Great care has been taken to ensure that the information

NEC PHILIPS Unified Solutions Nederland B.V. 2007

Cut out one of the labels below corresponding to the title

ISPBX PROJECTING FOR ACCOUNTING ....................................................3

HOW TO CONFIGURE IS3000 FDCR OUTPUT .................................................... 3

INSTALL AND CONFIGURE BUFFER BOXES ........................................... 11

DATA XPRESS REMOTE ACCESS BUFFER BOX .................................................. 11

CALL REPORTING MODULE INSTALLATIONS .........................................16

EXPENSE CONTROL SUITE INSTALLATIONS ..........................................21

4.5.6. How to Manually add a Range of Extensions ...............................................33

Accounting - Configuration Guide

Release date : 1/mrt/2007

Management@Net, release 3.1.1

ISPBX PROJECTING FOR ACCOUNTING

HOW TO CONFIGURE IS3000 FDCR OUTPUT

1.1.1. FDCR OUTPUT OVER V.24 CONNECTIONS

DIRECT FDCR OUTPUT OVER IP (SINGLE SITE)

DIPORT:11,18,20&&25; where 11,18 is the CPU address. If necessary assign devices

Other IP related OM commands that may be useful, are:

DITCPC: to display the IP configuration of a CPU3000 or a CIE-2 board;

BUFFERED FDCR OUTPUT OVER IP (MULTI SITE)

DITCPC: to display the IP configuration of a CPU3000 or a CIE-2 board;

ENABLE FDCR OUTPUT

HOW TO CONFIGURE 2000IPS SMDR OUTPUT

V.24 connection via AP00

V.24 connection via AP00 4)

1) Available in R9 and higher.

SMDR Output over a V.24 connection (MP or AP00)

and a Data Xpress buffer box.

2. Set Data length to 8 bits:

3. Set Parity to None:

4. Set Stop bits to 1:

5. Set DTR signal to high:

6. Set RTS signal to high:

7. Set Data Speed to 19200 bps:

8. Set SMDR for Outgoing Calls from Station 203:

SMDR Output over an IP connection (MP)

1. Use MP built-in SMDR:

2. SMDR via LAN port:

3. Extended SMDR Format (KH and KI records):

4. Set Parity on (required for Call Reporting Module version 9):

6. Set SMDR for Outgoing Calls from Station 203:

HOW TO CONFIGURE SV7000 SMDR OUTPUT

SMDR incomplete message output: 0=Out of Service 1=In Service.

CDN16=1: outgoing and incoming calls

To enable SMDR for stations:

INSTALL AND CONFIGURE BUFFER BOXES

DATA XPRESS REMOTE ACCESS BUFFER BOX

Configuration of the Data Xpress Remote Access Buffer Box

PROCEDURE: How to configure the Data Xpress Remote Access Buffer

1. Install the Data Xpress program from the CD (\Data Express

This formula is based on the following assumptions:

all SMDR/FDCR options are switched on

Making Physical Connections

PROCEDURE: Connecting the ComboX to the ISPBX and the modem at

Configure Connections using the Connection Manager Database

This procedure includes downloading data to the ComboX.

Configuration Wizard (by default, this starts automatically).

To check this, you need to open the TOPS box.

Calculating How Often You Need to Access the TOPS Box

all FDCR options are switched on

CALL REPORTING MODULE INSTALLATIONS