You are on page 1of 66

AMENDMENTS

The items that follow are incorporated in the update of this manual from issue 0008 to 0104:

CHAPTER/SECTION DESCRIPTION
Preface Text updated.
Chapter 1, 2, 3 and 4 Changed: wake up via window 2 instead of
window 6.
Chapter 5 TABS Setup procedure adapted.
Chapter 8 Only the ALC-G is mentioned.
Chapter 17 Boundaries adapted for Call@Net 2.6. TSD
for SV25 and SV35 added.
Chapter 19 Changed: ring tone for wake up.

1
PREFACE
This manual is valid for the Hotel Application, when using the following equipment :

• all SOPHO iS3000 models running SOPHO Call@Net (previously known as SSW 810)
• SOPHO SysManager 410, release 4.5 or higher
• SOPHO SuperVisor 60E, release 2.5 or higher
• A suitable Property Management System (PMS)

2
1. HOW TO CONFIGURE A CPU-ME/MT SYSTEM WITH
SysManager - ONLY FOR SSW 805

PROCEDURE: SETUP THE ISPBX: PORT ALLOCATION AND DEVICE


ASSIGNMENT

Preconditions

Check if your ISPBX has a license for System Management with DILICS:; .

You should have: System Management Yes .

For port allocation, the following configuration is assumed:

iS3010
IS3030
iS3050

FDCR/SS/OM CPU-
ME/MT

SOPHO SysManager

Figure 1-1 Connection between CPU-ME/MT and SysManager

Actions

1. Assign V.24 Port.


ASPORT:<SHELF>,<BRD>,<CRT>,<PROTOCOL-TYPE>,<CONNECTION-TYPE>;
Example: Local SysManager connection to port 21 on the CPU-ME in an iS3030:
ASPORT:12,8,21,1,0;
2. Change Speed on V.24 Port.
CHPORT:<SHELF>,<BRD>,<CRT>,<BAUDRATE>;
Example: Speed of port 21 on the CPU-ME set to 19200 bps:
CHPORT:12,8,21,17;
3. Assign Devices.
ASDEVC:<SHELF>,<BRD>,<CRT>,<LDN>,<EQUIPMENT-TYPE>;

3
Example: Local SysManager connection to port 21 on the CPU-ME in an iS3030 with Full
Detailed Call Recording, Switching Services and OM:
ASDEVC:12,8,21,FDCR,25;
ASDEVC:12,8,21,SYSMSS,29;
ASDEVC:12,8,21,VDU210,20;
ASDEVC:12,8,21,VDU211,21;
4. If MAC-Manager is used:
ASDEVC:12,8,21,RBU01,26;
5. To display the settings, use:
DIPORT:<SHELF>,<BRD>,<CRT>;

PROCEDURE: SETUP THE ISPBX FOR SWITCHING SERVICES

Preconditions

The following boundary must be sufficient:

NEBOUND 076 - Maximum number of TMS Slots.

The contents of this boundary can be checked by DIMDAT:0,76,1;


Actions

1. Assign TMS the windows.


ASTMSW:<WINDOW>,<WINDOW-SIZE>[,<UNIT>];
Examples:

ASTMSW:2,2,1; Used for wake up


ASTMSW:3,3,1; Used for message waiting without announcement
ASTMSW:4,3,1; Used for automatic directory dialling
ASTMSW:5,3,1; Used for 'changing PBX data' like bar/unbar, set/reset DND and
'PID Info / Set or Change PID Budget'
ASTMSW:81,9,1; Used for TSD and CNND
ASTMSW:83,1,1; Used for Automatically Entered Messages and wake up requests

Note: This command must only be executed for the unit to which SysManager is connected.
2. Assign the TMS logical name relation (this is only needed for the "high" windows).
CHTMSL:<WINDOW>,<LDN>[,<UNIT>];
Examples:

4
CHTMSL:81,SYSMSS,1; Used for TSD and CNND
CHTMSL:83,SYSMSS,1; Used for Automatically Entered Messages and wake up
requests

Note: This command must be executed for each unit in the system.

PROCEDURE: SETUP THE ISPBX FOR FULL DETAILED CALL


RECORDING

Preconditions

Check if your ISPBX has a license for FDCR with DILICS:;

You should have: FDCR Yes.

Options:

LOSYSOP060 - FDCR instead of toll ticketing = Yes.

For reaching the PSTN, route number 1 is assumed.


Actions

1. Display the route data with:


DIROUT:1;
And assign toll ticketing on the route.
CHRTCG:<ROUTE>,<GEN-OPTS>,<GEN-TONE>;
Example: CHRTCG:1,XXX1XXXXXX,XXXXXX;
2. Assign the FDCR characteristics.
CHFRCR:<FDCR-CALL-TYPE>,<OFF-ON>;
Example: CHFRCR:7,1;
3. Assign the FDCR output device.
CHFROD:<LDN>,<OUTPUT-FORMAT-VERSION>[,UNIT];
Example: CHFROD:FDCR,0,1;

Note: For 16 digit Costcentre/PID, OUTPUT-FORMAT-VERSION = 1.

4. Start the FDCR output.


STRTFR:<FILE-NAME>;
Example: STRTFR:TICKET;

5
PROCEDURE: SETUP SysManager: CONNECTION TO ISPBX

Preconditions

Use chapter "Connection Manager" from the SOPHO SysManager Customer Engineer manual
or the online help in the CM Database Configurator to set up the connection to the ISPBX.
Perform the steps and use the information described below:
Actions

1. Start the CM Database Configurator. From the Start menu choose Programs/SysManager
410/Configurators/CM Database Configurator.
2. In the 'Connection Wizard - Connection type' dialogue box, choose 'Direct connection to
ISPBX without add-on box'.
3. In the 'Connection Wizard - Unit' dialogue box, set the 'CPU type:' to 'CPU-ME'.
4. In the 'Connection Wizard - Destination port protocol and purposes' dialogue box, set the
protocol to 'BCS' and the purposes to 'Operational Maintenance', 'FDCR' and 'Switching
Services'.
5. In the 'Connection Wizard - COM port' dialogue box, select a free COM port, COM1 for
example.
6. In the 'Connection Wizard - COM port modem settings' dialogue box, set the speed to
38400 bps'.
7. Press 'Finish' and close the CM Database Configurator.
Testing

Use the ISPBX Destination Activator to test the interface between the ISPBX and SysManager.

6
2. HOW TO CONFIGURE A CPS SYSTEM (iS3070) WITH
SysManager - ONLY FOR SSW 805

PROCEDURE: SETUP THE ISPBX: PORT ALLOCATION AND DEVICE


ASSIGNMENT

Preconditions

Check if your ISPBX has a license for System Management with DILICS:; .

You should have: System Management Yes .

Check the DIP-switches and/or straps on the CIM. For FDCR choose SSM (BCS protocol) and
use only circuit 7 on the CIM (port 1).

For port allocation, the following configuration is assumed:

iS3070
(CPS)

FDCR
SS CIM
OM

SOPHO SysManager

Figure 2-1 Connection between CIM and SysManager


Actions

1. Assign V.24 Port.


ASPORT:<SHELF>,<BRD>,<CRT>,<PROTOCOL-TYPE>,<CONNECTION-TYPE>;
Example: Local SysManager connection to a CIM with one port for Full Detailed Call
Recording, one port for Switching Services and one port for OM:
ASPORT:14,16,3,2;
ASPORT:14,16,4,2;
ASPORT:14,16,7,2;
ASPORT:14,16,14,2;
2. Assign Devices.

7
ASDEVC:<SHELF>,<BRD>,<CRT>,<LDN>,<EQUIPMENT-TYPE>;
Example: Local SysManager connection to a CIM with one port for Full Detailed Call
Recording, one port for Switching Services and one port for OM:
ASDEVC:14,16,3,VDU030,20;
ASDEVC:14,16,4,VDU031,21;
ASDEVC:14,16,7,FDCR,25;
ASDEVC:14,16,14,SYSMSS,29;

Note: For FDCR choose SSM (BCS protocol) and use only circuit 7 on the CIM (port 1)

3. To display the settings, use:


DIPORT:<SHELF>,<BRD>,<CRT>;

PROCEDURE: SETUP THE ISPBX FOR SWITCHING SERVICES

Preconditions

The following boundary must be sufficient:

NEBOUND 076 - Maximum number of TMS Slots

The contents of this boundary can be checked by DIMDAT:0,76,1;


Actions

1. Assign TMS the windows.


ASTMSW:<WINDOW>,<WINDOW-SIZE>[,<UNIT>];
Examples:

ASTMSW:2,2,1; Used for wake up


ASTMSW:3,3,1; Used for message waiting without announcement
ASTMSW:4,3,1; Used for automatic directory dialling
ASTMSW:5,3,1; Used for 'changing PBX data' like bar/unbar, set/reset DND and
'PID Info / Set or Change PID Budget'
ASTMSW:81,9,1; Used for TSD and CNND
ASTMSW:83,1,1; Used for Automatically Entered Messages and wake up requests

Note: This command must only be executed for the unit to which SysManager is connected.
2. Assign the TMS logical name relation (this is only needed for the "high" windows).
CHTMSL:<WINDOW>,<LDN>[,<UNIT>];
Examples:

8
CHTMSL:81,SYSMSS,1; Used for TSD and CNND
CHTMSL:83,SYSMSS,1; Used for Automatically Entered Messages and wake up
requests

Note: This command must be executed for each unit in the system.

PROCEDURE: SETUP THE ISPBX FOR FULL DETAILED CALL


RECORDING

Preconditions

Check if your ISPBX has a license for FDCR with DILICS:;

You should have: FDCR Yes.

Options:

LOSYSOP060 - FDCR instead of toll ticketing = Yes.

For reaching the PSTN, route number 1 is assumed.


Actions

1. Display the route data with:


DIROUT:1;
And assign toll ticketing on the route.
CHRTCG:<ROUTE>,<GEN-OPTS>,<GEN-TONE>;
Example: CHRTCG:1,XXX1XXXXXX,XXXXXX;
2. Assign the FDCR characteristics.
CHFRCR:<FDCR-CALL-TYPE>,<OFF-ON>;
Example: CHFRCR:7,1;
3. Assign the FDCR output device.
CHFROD:<LDN>,<OUTPUT-FORMAT-VERSION>[,UNIT];
Example: CHFROD:FDCR,0,1;

Note: For 16 digit Costcentre/PID, OUTPUT-FORMAT-VERSION = 1.

4. Start the FDCR output.


STRTFR:<FILE-NAME>;
Example: STRTFR:TICKET;

9
PROCEDURE: SETUP SysManager: CONNECTION TO ISPBX

Preconditions

Use chapter "Connection Manager" from the SOPHO SysManager Customer Engineer manual
or the online help in the CM Database Configurator to set up the connection to the ISPBX.
Perform the steps and use the information described below:
Actions

1. Start the CM Database Configurator. From the Start menu choose Programs/SysManager
410/Configurators/CM Database Configurator.
2. In the 'Connection Wizard - Connection type' dialogue box, choose 'Direct connection to
ISPBX without add-on box'.
3. In the 'Connection Wizard - Unit' dialogue box, set the 'CPU type:' to 'CPS'.
4. In the 'Connection Wizard - Destination port protocol and purposes' dialogue box, set the
protocol to 'CHARACTER' and the purposes to 'Operational Maintenance'. Note that you
have to define two additional ISPBX ports: define a port with the protocol set to 'BCS' and
the purpose to 'FDCR' and define a port with the protocol set to 'BCS' and the purpose to
'Switching Services'.
5. In the 'Connection Wizard - (Select) COM port' dialogue box, select a free COM port,
COM1 for example. Note that you have to define two more COM ports for the ISPBX
connections (COM2 and COM3 for example).
6. In the 'Connection Wizard - COM port modem settings' dialogue box, set the speed to
max 9600 bps'.
7. Press 'Finish' and close the CM Database Configurator.
Testing

Use the ISPBX Destination Activator to test the interface between the ISPBX and SysManager.

10
3. HOW TO CONFIGURE A CCS SYSTEM (iS3090) WITH
SysManager

PROCEDURE: SETUP THE ISPBX: PORT ALLOCATION AND DEVICE


ASSIGNMENT

Preconditions

Check if your ISPBX has a license for System Management with DILICS:; .

You should have: System Management Yes .

For port allocation, the following configuration is assumed:

iS3090
(CCS)

FDCR/SS/OM
BIM CIE

SOPHO SysManager

Figure 3-1 Connection between BIM and SysManager


Actions

1. Assign V.24 Port.


ASPORT:<SHELF>,<BRD>,<CRT>,<PROTOCOL-TYPE>,<CONNECTION-TYPE>;
Example: Local SysManager connection to port 2 of the CIE:
ASPORT:14,10,2,2;
2. Assign Devices.
ASDEVC:<SHELF>,<BRD>,<CRT>,<LND>,<EQUIPMENT-TYPE>;
Example: Local SysManager connection to port 2 of a CIE with Full Detailed Call
Recording, Switching Services and OM:
ASDEVC:14,10,2,FDCR,32;
ASDEVC:14,10,2,SYSMSS,29;
ASDEVC:14,10,2,VDU020,20;
ASDEVC:14,10,2,VDU021,21;

11
3. To display the settings, use:
DIPORT:<SHELF>,<BRD>,<CRT>;
4. For port settings on the BIM, use the BIM configuration menu with the example of the SSM
configuration in appendix C of the BIM manual.

Note: Set call records buffering to 'yes'. This is used in case the connection to SysManager is
temporarily not available.

PROCEDURE: SETUP THE ISPBX FOR SWITCHING SERVICES

Preconditions

The following boundary must be sufficient:

NEBOUND 076 - Maximum number of TMS Slots

The contents of this boundary can be checked by DIMDAT:0,76,1;


Actions

1. Assign TMS the windows.


ASTMSW:<WINDOW>,<WINDOW-SIZE>[,<UNIT>];
Examples:

ASTMSW:2,2,1; Used for wake up


ASTMSW:3,3,1; Used for message waiting without announcement
ASTMSW:4,3,1; Used for automatic directory dialling
ASTMSW:5,3,1; Used for 'changing PBX data' like bar/unbar, set/reset DND and
'PID Info / Set or Change PID Budget'
ASTMSW:81,9,1; Used for TSD and CNND
ASTMSW:83,1,1; Used for Automatically Entered Messages and wake up requests

Note: This command must only be executed for the unit to which SysManager is connected.
2. Assign the TMS logical name relation (this is only needed for the "high" windows).
CHTMSL:<WINDOW>,<LDN>[,<UNIT>];
Examples:

CHTMSL:81,SYSMSS,1; Used for TSD and CNND


CHTMSL:83,SYSMSS,1; Used for Automatically Entered Messages and wake up
requests

12
Note: This command must be executed for each unit in the system.

PROCEDURE: SETUP THE ISPBX FOR FULL DETAILED CALL


RECORDING

Preconditions

Check if your ISPBX has a license for FDCR with DILICS:;

You should have: FDCR Yes

Options:

LOSYSOP060 - FDCR instead of toll ticketing = Yes.

For reaching the PSTN, route number 1 is assumed.


Actions

1. Display the route data with:


DIROUT:1;
And assign toll ticketing on the route.
CHRTCG:<ROUTE>,<GEN-OPTS>,<GEN-TONE>;
Example: CHRTCG:1,XXX1XXXXXX,XXXXXX;
2. Assign the FDCR characteristics.
CHFRCR:<FDCR-CALL-TYPE>,<OFF-ON>;
Example: CHFRCR:7,1;
3. Assign the FDCR output device.
CHFROD:<LDN>,<OUTPUT-FORMAT-VERSION>[,UNIT];
Example: CHFROD:FDCR,0,1;

Note: For 16 digit Costcentre/PID, OUTPUT-FORMAT-VERSION = 1.

4. Start the FDCR output.


STRTFR:<FILE-NAME>;
Example: STRTFR:TICKET;

PROCEDURE: SETUP SysManager: CONNECTION TO ISPBX

Preconditions

Use chapter "Connection Manager" from the SOPHO SysManager Customer Engineer manual

13
or the online help in the CM Database Configurator to set up the connection to the ISPBX.
Perform the steps and use the information described below:
Actions

1. Start the CM Database Configurator. From the Start menu choose Programs/SysManager
410/Configurators/CM Database Configurator.
2. In the 'Connection Wizard - Connection type' dialogue box, choose 'Direct connection to
ISPBX without add-on box'.
3. In the 'Connection Wizard - Unit' dialogue box, set the 'CPU type:' to 'CCS'.
4. In the 'Connection Wizard - Destination port protocol and purposes' dialogue box, set the
protocol to 'BCS' and the purposes to 'Operational Maintenance', 'FDCR' and 'Switching
Services'.
5. In the 'Connection Wizard - COM port' dialogue box, select a free COM port, COM1 for
example.
6. In the 'Connection Wizard - COM port modem settings' dialogue box, set the speed to
38400 bps'.
7. Press 'Finish' and close the CM Database Configurator.
Testing

Use the ISPBX Destination Activator to test the interface between the ISPBX and SysManager.

14
4. HOW TO CONFIGURE A CPU3000 SYSTEM WITH
SysManager - ONLY FOR Call@Net

PROCEDURE: SETUP THE ISPBX: PORT ALLOCATION AND DEVICE


ASSIGNMENT

Preconditions

Check if your ISPBX has a license for System Management with DILICS:; .

You should have: System Management Yes .

For port allocation, the following configuration is assumed:

iS3010
IS3030
iS3050

FDCR/SS/OM CPU3000

SOPHO SysManager

Figure 4-1 Connection between CPU3000 and SysManager

Actions

1. Assign V.24 Port.


ASPORT:<SHELF>,<BRD>,<CRT>,<PROTOCOL-TYPE>,<CONNECTION-TYPE>;
Example: Local SysManager connection to port 21 on the CPU-3000 in an iS3030:
ASPORT:12,8,21,1,0;
2. Change Speed on V.24 Port.
CHPORT:<SHELF>,<BRD>,<CRT>,<BAUDRATE>;
Example: Speed of port 21 on the CPU-3000 set to 19200 bps:
CHPORT:12,8,21,17;
3. Assign Devices.
ASDEVC:<SHELF>,<BRD>,<CRT>,<LDN>,<EQUIPMENT-TYPE>;

15
Example: Local SysManager connection to port 21 on the CPU-3000 in an iS3030 with Full
Detailed Call Recording, Switching Services and OM:
ASDEVC:12,8,21,FDCR,25;
ASDEVC:12,8,21,SYSMSS,29;
ASDEVC:12,8,21,VDU210,20;
ASDEVC:12,8,21,VDU211,21;
4. To display the settings, use:
DIPORT:<SHELF>,<BRD>,<CRT>;

PROCEDURE: SETUP THE ISPBX FOR SWITCHING SERVICES

Preconditions

The following boundary must be sufficient:

NEBOUND 076 - Maximum number of TMS Slots.

The contents of this boundary can be checked by DIMDAT:0,76,1;


Actions

1. Assign TMS the windows.


ASTMSW:<WINDOW>,<WINDOW-SIZE>[,<UNIT>];
Examples:

ASTMSW:2,2,1; Used for wake up


ASTMSW:3,3,1; Used for message waiting without announcement
ASTMSW:4,3,1; Used for automatic directory dialling
ASTMSW:5,3,1; Used for 'changing PBX data' like bar/unbar, set/reset DND and
'PID Info / Set or Change PID Budget'
ASTMSW:81,9,1; Used for TSD and CNND
ASTMSW:83,1,1; Used for Automatically Entered Messages and wake up requests

Note: This command must only be executed for the unit to which SysManager is connected.
2. Assign the TMS logical name relation (this is only needed for the "high" windows).
CHTMSL:<WINDOW>,<LDN>[,<UNIT>];
Examples:

CHTMSL:81,SYSMSS,1; Used for TSD and CNND


CHTMSL:83,SYSMSS,1; Used for Automatically Entered Messages and wake up
requests

16
Note: This command must be executed for each unit in the system.

PROCEDURE: SETUP THE ISPBX FOR FULL DETAILED CALL


RECORDING

Preconditions

Check if your ISPBX has a license for FDCR with DILICS:;

You should have: FDCR Yes.

Options:

LOSYSOP060 - FDCR instead of toll ticketing = Yes.

For reaching the PSTN, route number 1 is assumed.


Actions

1. Display the route data with:


DIROUT:1;
And assign toll ticketing on the route.
CHRTCG:<ROUTE>,<GEN-OPTS>,<GEN-TONE>;
Example: CHRTCG:1,XXX1XXXXXX,XXXXXX;
2. Assign the FDCR characteristics.
CHFRCR:<FDCR-CALL-TYPE>,<OFF-ON>;
Example: CHFRCR:7,1;
3. Assign the FDCR output device.
CHFROD:<LDN>,<OUTPUT-FORMAT-VERSION>[,UNIT];
Example: CHFROD:FDCR,0,1;

Note: For 16 digit Costcentre/PID, OUTPUT-FORMAT-VERSION = 1.

4. Start the FDCR output.


STRTFR:<FILE-NAME>;
Example: STRTFR:TICKET;

PROCEDURE: SETUP SysManager: CONNECTION TO ISPBX

Preconditions

Use chapter "Connection Manager" from the SOPHO SysManager Customer Engineer manual

17
or the online help in the CM Database Configurator to set up the connection to the ISPBX.
Perform the steps and use the information described below:
Actions

1. Start the CM Database Configurator. From the Start menu choose Programs/SysManager
410/Configurators/CM Database Configurator.
2. In the 'Connection Wizard - Connection type' dialogue box, choose 'Direct connection to
ISPBX without add-on box'.
3. In the 'Connection Wizard - Unit' dialogue box, set the 'CPU type:' to 'CPU3000'.
4. In the 'Connection Wizard - Destination port protocol and purposes' dialogue box, set the
protocol to 'BCS' and the purposes to 'Operational Maintenance', 'FDCR' and 'Switching
Services'.
5. In the 'Connection Wizard - COM port' dialogue box, set the speed to '38400 bps'.
6. Press 'Finish' and close the CM Database Configurator.
Testing

Use the ISPBX Destination Activator to test the interface between the ISPBX and SysManager.

18
5. HOW TO CONFIGURE SysManager FOR FDCR

PROCEDURE: CREATE A DIRECT (NON-BUFFERED) CONNECTION TO


A LOCAL SITE

Preconditions

This procedure assumes the installation of SysManager configuration "Full Hospitality" or "Basic
Hospitality". This means that the TABS Call Reporting Module will only accept one direct and
non-buffered connection (bcs or character protocol). The "Full Hospitality" or "Basic
Hospitality" are configurations with "PMS Billing", so the TABS Call Reporting Module will
calculate the bill from the FDCR record and will send the result to the EAI. Depending on the
configuration of the EAI, a Simple Bill (message 20), an Extended Bill (message 21) and/or a
Toll Ticket (message 22) is sent to the Hotel system (PMS). See also 6. HOW TO PROJECT
THE EXTERNAL APPLICATION INTERFACE.

The Connection Manager can handle a multi-unit system (FIN) where one FDCR output for
the complete FIN is used. Again, this is one direct and non-buffered connection (bcs or
character protocol). For FIN's, the restriction is 8 FDCR records per second (equivalent to 4
outgoing calls per second).
Actions

Note: Use chapter 3 of the SOPHO SysManager 410 TABS Call Reporting Module Installation
Guide along with the following actions.
1. When activating TABS Setup for the first time, the following message is displayed:
"Your system has not yet been fully configured. Press OK to complete the installation
process. Press Cancel to quit."
Press OK.
2. The next message is:
"To continue installing the TABS system, the following procedures must be performed:
Connecting to hardware devices; Importing Costing/Organizational data. Please select
Setup options."
Click both boxes and press OK.
3. The next message is:
"You may now define the connection(s) to your PBX(s) . . . . "
Press OK.
4. Now follow the Single Site Setup. Use chapter 3 of the TABS Call Reporting Module
Installation Guide.

19
5. In the "General" part of the "Define Site", choose the ISPBX name from the dropdown list.
With the help of other parts and the hints below, finish the configuration of this site.
- In the "Polling" part set "Connect Every: 1 Hour(s)" and choose "Collect All Calls".
- In the "Ignore Calls" part, choose "Do not Ignore Calls".
- In the "Hardware" part, press the "PBX" button.
- From the "PBX Formats" list, select the appropriate file, and press the "Edit" button.

CAUTION: AFTER SELECTION OF THE PBX FORMAT (SOPHO805 V.0N FOR


12 DIGIT PID OR SOPHO805 V.1N FOR 16 DIGIT PID) DO NOT
EDIT ANY FIELDS, SINCE THE PBX FORMAT CONTAINS ALL
NECESSARY FIELD DEFINITIONS.

- Be sure FDCR records are being sent by the ISPBX. If not, see chapter 1, 2, 3 or 4 on
how to start the FDCR output.
- Generate some calls and check that they appear in the proper format at the bottom
of the window.
- Close the edit window.
- Press the "Reset" button and press OK.
- Close the "Define Site" dialogue.

Note: All Calls generated during the edit mode (that is all calls displayed in the edit window) are
not saved in the TABS database.

6. The following message is displayed:


"The following screen enables you to import organizational layout, costing and accounting
information from TDA files . . . . ". This step is needed to load the tariff data for the various
service providers into TABS. See section 5.1 below.
7. Finally click the OK button; the definition of the local site is finished.
8. Enter TABS Setup again and select "Site/Polling Options" from the menu. Select the site
you just defined as the default site. Close TABS Setup.
9. Edit the file "tabsite.ini" as follows:
- Find the file "tabsite.ini" in C:\Philips\Data Files\SysManager
410\Tabs\db\<ISPBX Name> . "C:" is assumed to be the drive where you installed
SysManager.
- Open tabssite.ini and search for the label [<ISPBX Name>.Connection]. If your site
was "Hilversum" you will find [Hilversum.Connection], for example.
- Insert the text line DisconnectAtTheEndOfPolling=False under [<ISPBX
Name>.Connection] .
- Save the changes.
10. Start the TABS Call Collector.

20
5.1. IMPORTING COSTING TABLES

For different countries and service providers (telecommuncation companies), different costing
tables exists. Configuring TABS for these service providers is outside the scope of this manual.

Use the section 'Importing Data' in chapter 3 of the TABS Call Reporting Module Installation
Guide to import the costing tables.

5.2. DEFINING MARKUPS, FIXED CHARGES AND TAXES

Probably the guests in the hotel will be charged extra for the telephone calls he makes. On top
of the cost of a call (for a service provider), a fixed amount of money and/or a percentage is
added. It is also possible to add a fixed amount of money (for hiring a sophisticated telephone
set, for example) and to add tax (VAT) to the guest's bill.

See the sections 'Markups', 'Fixed Charges' and 'Taxes' of chapter 7 of the TABS Call Reporting
Module Installation Guide.

21
6. HOW TO PROJECT THE EXTERNAL APPLICATION
INTERFACE

PROCEDURE: GENERAL EAI SETUP IN SysManager

Actions

Use chapter "Connection Manager" from the SOPHO SysManager Customer Engineer manual
or the online help in the CM Database Configurator to set up the connection to the External
Application (PMS). Perform the steps and use the information described below:

1. Start the CM Database Configurator. From the Start menu choose Programs/SysManager
410/Configurators/CM Database Configurator.
2. In the 'Connection Wizard - Connection type' dialogue box, choose 'Connection to
External Application'.
3. In the 'Connection Wizard - Select COM port' dialogue box, press 'New COM'. Select a
free COM port, COM2 for example.
4. In the 'Connection Wizard - COM port modem settings' dialogue box, set the speed
according to the PMS speed'.
5. Press 'Finish' and close the CM Database Configurator.
6. Start the EAI Configurator. From the Start menu choose Programs/SysManager 410/
Configurators/ EAI Configurator.
7. In the "Connection" tab, select the ISPBX and the external application. The names are
taken from the CM database.

22
8. In the "Bills and Toll Tickets" tab, select whether you want Bills (Simple Bills or Extended
Bills) and/or Toll Tickets to be sent to the external application (PMS system).
In PID Dialling, fill in the money value of one SOPHO unit.

23
24
7. HOW TO PROJECT AN IASA

PROCEDURE: HARDWARE INSTALLATION OF THE IASA

Actions

1. Set strap X3.1 to position 101-102 (battery connected).


2. Set strap X3.2 to position 101-102 (use PM bus from backpanel).
3. Load the IAS board with the IASA firmware (using the application loader, see Customer
Engineer Manual SOPHO VoiceManager 110).

25
Mark

X3.1
LEDs 103 101
Green 102 Extra memory board BP
Red
20 X3.2
Yellow X2.
103 101
X6.3
to SN 3 1 102
4 2
FAC * 20
(SCU X2.

20 20
BA
X2. X2.
X6.2 X6.1
3 1 3 1
4 2 4 2
1 20 20
X4.1
2 X2. X2.

Extra memory board Extra memory board


These are connectors onto which memory boards can be

Factory
test only BB
FCC
V.24

1 102/201 108/208
X1.1 X5.1
BIST Connector
8

* This connector is not used by the IASA

Figure 7-1 IASA Board Layout

PROCEDURE: PROJECTING THE IASA

Actions

1. Assign the board.


ASBRDS:<SHELF>,<BRD>,<BOARD-TYPE>,<SIG-GROUP>,<HW-TYPE>;
Example: ASBRDS:1012,7,9,280D,255;

Note: For projecting an IASA with 14 ports, use board type 5 and signalling group 2807.

26
2. Assign DNRs to the circuits that are going to be used as synchronous announcers.
CHDNRC:<BSP-ID>,<SHELF>,<BRD>,<CRT>;
Example: CHDNRC:1300,1012,7,2;

Note: Circuit two must have a DNR assigned and is used for the IASA Manager.

3. If there are circuits on the IASA which have to be projected as continuous (asynchronous)
announcers these circuits have to be deleted and assigned again.
DEPCTB:<SHELF>,<BRD>,<CRT>;
ASPCTB:<SHELF>,<BRD>,<CRT>,<PCT-TYPE>,<SIG-GROUP>;
Example:
DEPCTB:1012,7,30;
ASPCTB:1012,7,30,15,280D;

Note: Continuous (asynchronous) announcers have PCT-TYPE 15 and are not assigned a DNR.

4. Set board and all circuits in service.


SETINS:<SHELF>,<BRD>,<CRT>;
Example:
SETINS:1012,7;
SETINS:1012,7,2&&30;

PROCEDURE: STORING VOICE (ANNOUNCEMENTS) OR MUSIC

Preconditions

The memory of the IASA board must be loaded with voice or music (whatever is required).
The easiest way to record an announcement is by means of a telephone set. If the
announcement is recorded by means of a SOPHO Business telephone with analogue input, it
is also possible to record an announcement from a tape or a compact disk.

See the 'Online Help' of the Announcement Manager module how to record a message/
announcement.

27
8. HOW TO PROJECT AN ALC-G

PROCEDURE: HARDWARE INSTALLATION OF THE ALC-G

Preconditions

It is possible to connect up to three analogue telephone sets in parallel. However, an ALC-G


circuit can drive only ONE message Waiting LED ! The Message Waiting LED can be disabled
by means of a built in switch in the extension for Hotel applications. So, if there is more than
one set connected to an ALC-G port, be sure that you enable the LED on only one of the sets.
Actions

1. For the hardware installation of the ALC-G, see SOPHO iS3000 Series Maintenance
Manual, Part 3.

PROCEDURE: PROJECTING THE ALC-G

Actions

1. Assign the board.


ASBRDS:<SHELF>,<BRD>,<BOARD-TYPE>,<SIG-GROUP>,<HW-TYPE>;
Example: ASBRDS:1011,9,6,3210,35;
2. Change PM projecting data.
CHPMPD:<PM-OBJECT>,<OBJ-INDEX>;
Example: CHPMPD:0,3210;
Enter <ITEM-NBR>,<BIT-BYTE>[,<DATA>]:01,01,06;
Enter <ITEM-NBR>,<BIT-BYTE>[,<DATA>]:;

Note: This change is required to set a timer for the enquiry button recognition on the analogue
hotel extension (SOPHO-SET 125 or 225).

3. Assign DNRs to the circuits of the board.


CHDNRC:<BSP-ID>,<SHELF>,<BRD>,<CRT>;
Example: CHDNRC:1000,1011,9,0;
4. Set board and all circuits in service.
SETINS:<SHELF>,<BRD>,<CRT>;
Example:
SETINS:1011,9;
SETINS:1011,9,0&&15;

28
5. Assign the facility class mark 'Message Waiting Indication on ALC' to all SOPHO-SETs 125
connected to the ALC-F/G.
ASFACM:<FCM>,<BSP-ID>;
Example: ASFACM:52,1000;

Note: This facility class mark is required, to enable the message waiting indication on a SOPHO-
SET 125.

29
9. HOW TO PROJECT THE HOWLER FUNCTION

PROCEDURE: HOW TO PROJECT THE HOWLER FUNCTION IN THE


ISPBX

The howler function is a loud tone of two alternating frequencies of 1400 Hz and 1800 Hz
each for a duration of 200 ms each at 0 dBm and is repeated.

In this procedure tone function 21 will be used with tone sources 6 (1400 Hz) and 7 (1800 Hz)
as loud as possible (0 dBm) to produce the howler tone. The howler function is switched on
using signalling group 9800, byte 32, bit 0.
Preconditions

The PMC package must be 405.6 or higher. Tone function 21 must not be used for any other
function than the howler tone. Tone sources 6 and 7 are used to the maximum level (as loud
as possible) and must not be used within any other tone function.

Timers:

NETIMER000 - Internal dial tone time.

NETIMER006 -Tone limit time.


Actions

1. Assign tone sources 6 and 7 to tone function 21.


CHPMPD:5,21,2,0,1;
Where 5=PMC tone data, 21=tone function, 2=two items, 0=start with item 0 after
item 1 and 1=unit number.
Enter <ITEM-NBR>[,<TONE-SRC>,<T-VALUE>,<UNIT-T>]:0,6,2,1;
Where 0=item 0, 6=tone source 1400 Hz, 2=two units and 1=units of 100 ms. This
means a duration of 200 ms.
Enter <ITEM-NBR>[,<TONE-SRC>,<T-VALUE>,<UNIT-T>]:1,7,2,1;
Where 1=item 0, 7=tone source 1800 Hz, 2=two units and 1=units of 100 ms. This
means a duration of 200 ms.
Enter <ITEM-NBR>[,<TONE-SRC>,<T-VALUE>,<UNIT-T>]:;
2. Set the tone levels to 0 dBm for tone sources 6 and 7.
CHPMPD:1,9,,,1;
Where 1=slave data, 9=tone level and 1=unit number.
Enter <TONE-SRC>,<LEVEL-INDICATOR>:6,0;
Where 6=tone source 1400 Hz and 0=tone level of 0 dBm.

30
Enter <TONE-SRC>,<LEVEL-INDICATOR>:7,0;
Where 7=tone source 1800 Hz and 0=tone level of 0 dBm.
Enter <TONE-SRC>,<LEVEL-INDICATOR>:;
3. Set the howler function on.
CHPMPD:0,9800,,,1;
Where 0=signalling data, 9800=signalling group and 1=unit number.
Enter <ITEM-NBR>,<BIT-BYTE>[,<DATA>]:32,1,1;
Where 32=byte number, 1=byte and 1=bit 0 set to 1.
Enter <ITEM-NBR>,<BIT-BYTE>[,<DATA>]:;
4. Activate the howler function.
To activate the howler function for a shelf (PM1100), do SETOUT with the hardware
address of the PMC followed by SETINSwith the hardware address of the PMC.
To activate the howler function for the full system, perform a warm start using STWARM.

31
10. HOW TO PROJECT DND

PROCEDURE: SETUP THE ISPBX FOR DND FROM AN EXTENSION

Preconditions

Boundaries:

LOBOUND260 - 'Do Not Disturb' reset time in minutes.

LOBOUND261 - Maximum number of temporary 'Do Not Disturb' cases.

Options:

LOSYSOP015 - Rerouting of 'Do Not Disturb' calls to operator = Yes.

The bypass tone is defined in tone function 15 and can be changed by CHPMPD if required.
Actions

1. Assign the set and reset DND prefixes in the initial extension dialling analysis tree.
ASINTN:<TREE>,<NUMBER>,<TRFC>,<RESULT-ID>[,[<DEST/NUMBER][,<NUMBER-
LENGTH>]];
Example:
ASINTN:0,*53,1,66;
ASINTN:0,#53,1,67;
2. Assign the operator bypass code in the post dialling analysis tree.
ASINTN:<TREE>,<NUMBER>,<TRFC>,<RESULT-ID>[,[<DEST/NUMBER][,<NUMBER-
LENGTH>]];
Example: ASINTN:3,7,1,59;
3. Assign facility class mark 'Do Not Disturb entitled' to all extensions which may use the
DND facility.
ASFACM:<FCM>,<BSP-ID>;
Example: ASFACM:25,1000;

Note: There should be no restriction on changing the facility class mark 25; the facility class mark
restriction level can be changed with OM command: CHFCMR:0,25,0;

32
PROCEDURE: SETUP SysManager FOR DND

Preconditions

The External Application Interface is installed with Full Licence.

The External Application Interface basics are setup, see 6. HOW TO PROJECT THE
EXTERNAL APPLICATION INTERFACE.

Switching Services connection must be operational and window 5 must be running.


Actions

1. Define a 'set Do Not Disturb' prefix by defining an Automatically Entered Message that
Activates DND. See also 13. HOW TO PROJECT AEM.
2. Define a 'reset Do Not Disturb' prefix by defining an Automatically Entered Message that
Deactivates DND.

Note: There should be no restriction for SysManager on changing facility class mark 24; this can
be set unrestricted with OM command: CHFCMR:3,24,0;

Testing

DND can easily be tested with the following sequence:

1. Dial the 'set Do Not Disturb' prefix at an extension in a room.


2. From another extension, try to set up a call to this extension. If the DND facility is correct
your call will be rerouted to the operator (LOSYSOP015 = Yes).
3. Make a call to this extension from the operator position. This call must be unsuccessful.
Dial the operator bypass code; this call must be successful.
4. Dial the 'reset Do Not Disturb' prefix at the extension.
5. From another extension, try to set up a call to this extension. Now you must be able to
setup a call.

PROCEDURE: SETUP DND USING OM

Preconditions

Options:

33
LOSYSOP015 - Rerouting of 'Do Not Disturb' calls to operator = Yes.
Actions

1. Assign the operator bypass code in the post dialling analysis tree.
ASINTN:<TREE>,<NUMBER>,<TRFC>,<RESULT-ID>[,[<DEST/NUMBER][,<NUMBER-
LENGTH>]];
Example: ASINTN:3,7,1,59;
2. Assign facility class mark 'Do Not Disturb' to all extensions for which DND must be set.
ASFACM:<FCM>,<BSP-ID>;
Example: ASFACM:24,1000;
3. Erase facility class mark 'Do Not Disturb' from all extensions for which DND must be
reset.
ERFACM:<FCM>,<BSP-ID>;
Example: ERFACM:24,1000;

Note: There should be no restriction on changing the facility class mark 24; the facility class mark
restriction level can be changed with OM command: CHFCMR:0,24,0;
Testing

1. Use OM command ASFACM to set Do Not Disturb for an extension.


2. From another extension, try to set up a call to this extension. If the DND facility is correct
your call will be rerouted to the operator (LOSYSOP015 = Yes).
3. Make a call to this extension from the operator position. This call must be unsuccessful.
Dial the operator bypass code; this call must be successful.
4. Use the OM command ERFACM to reset Do Not Disturb for the extension.
5. From another extension, try to set up a call to this extension. Now you must be able to
setup a call.

34
11. HOW TO PROJECT ANALYSIS GROUPS IN THE
ISPBX

PROCEDURE: PROJECTING ANALYSIS GROUPS IN THE ISPBX

Preconditions

Boundaries:

NEBOUND072 - Maximum number of analysis groups.

The maximum number of Analysis Groups must at least be set to the number of the highest
Analysis Group plus 1.

As an example, the following configuration is assumed:

35
Hotel SOPHO

Floor 3
Analysis Group 13 Analysis Group 0
Guests on 3rd Floor Services on 3rd Floor

Floor 2
Analysis Group 12
Guests on 2nd Floor Services on 2nd Floor

Floor 1
Analysis Group 11
Guests on 1st Floor Services on 1st Floor

Ground
Floor Analysis Group 1
Staff

Figure 11-1 Hotel Example with Analysis Groups


Actions

1. Assign an analysis group to extensions.


CHAGCV:<BSP-ID>,<AG>;
Example:
CHAGCV:101&&189,11; Analysis group for guests at the first floor
2. Do the same for all other extensions.
Example:

CHAGCV:201&&289,12; Analysis group for guests at the second floor


CHAGCV:301&&389,13; Analysis group for guests at the third floor
CHAGCV:1900&&1999,0; Analysis group for service extensions at the first floor
CHAGCV:2900&&2999,0; Analysis group for service extensions at the second floor

36
CHAGCV:3900&&3999,0; Analysis group for service extensions at the third floor
CHAGCV:9900&&9999,1; Analysis group for staff extensions

37
12. HOW TO PROJECT MEM

PROCEDURE: SETUP THE ISPBX FOR MESSAGE WAITING NO


ANNOUNCEMENT

Preconditions

Boundaries:

NEBOUND145 - TMS Message Waiting Type.

Type 0 is steady on, Type 1 is flashing and Type 2 is winking; only used by SOPHO-SETs
(Digital SOPHO Business telephones).

LOBOUND331 - Message Waiting Dial Tone.

Dial tone to be given when an extension user starts a call while message waiting is active.
Default 28 meaning "no specific dial tone".

Options:

LOSYSOP027 - Message waiting queuing softring = Yes.

Timers:

NETIMER036 - Message waiting trigger time (5 minutes).

The service B ring current (tone function 106) is used for softring. It can be changed by
CHPMPD if required.

PROCEDURE: SETUP SysManager FOR MESSAGE WAITING NO


ANNOUNCEMENT

Preconditions

The External Application Interface basics are setup, see also 6. HOW TO PROJECT THE
EXTERNAL APPLICATION INTERFACE .

The SOPHO SuperVisor that is used to enter the Manually Entered Messages must be
configured to use the same PhoneWare database as the SysManager.
Testing

38
Testing the MEM functionality is done by using the facility. The following procedure represents
an application which can be used to test the facility:

1. Login on to the SuperVisor 60E.


2. Select a person in the Operator Directory and leave him a message (press the envelope).
3. The action depends on the type of telephone set of this person:
- If the telephone set is a normal analogue telephone set, it has to ring softly with certain
time intervals (15 minutes).
- If the telephone set is a dedicated analogue hotel extension with message waiting LED,
like a SOPHO-SET 125 or 225, check that this LED is lit.
- If the telephone set is a digital SOPHO business telephone with message waiting LED,
like an ErgoLine D310 or D320, check that this LED is lit.
- If the telephone set is a digital SOPHO business telephone a function key programmed
for message waiting, like an ErgoLine D330 or D340, check that the LED in the
function key is lit.
- On any other telephone set, check that you hear a special dial tone (if LOBOUND331
has been programmed).

39
13. HOW TO PROJECT AEM

PROCEDURE: SETUP THE ISPBX FOR AEM

Actions

1. Assign the AEM prefixes in the initial extension dialling analysis tree for the analysis groups
which are allowed to dial this facility.
ASINTN:<TREE>,<NUMBER>,<TRFC>,<RESULT-ID>[,[<DEST/NUMBER][,<NUMBER-
LENGTH>]];
Example:
ASINTN:2,*593,2,82,,2;
ASINTN:2,*573,2,82,,6;
2. Assign the TMS Digit Position.
ASTMSD:<DIGIT-POSITION>;
Example: ASTMSD:4;
For the AEM's (window nr. 83) defined in step one the "3" in *593 or *573 (which is the
service digit) is located on the fourth position.

PROCEDURE: SETUP SysManager FOR AEM

Preconditions

The SysManager and the (Master) SOPHO SuperVisor 60E must be configured to use the
same PhoneWare database.

The External Application Interface basics are setup, see also .


Actions

1. Start the EAI Configurator. From the Start menu choose Programs/SysManager 410/
Configurators/ EAI Configurator.
2. In the "Prefixes" tab, check that all prefixes that you have assigned for AEM in the ISPBX
are present. If not : add these prefixes.

40
3. In the "Extension Messages" tab, check that all messages needed for AEM are defined. You
can use "Test with Prefix" to test the prefix / message combination.

41
4. Select whether SysManager must send message information to the external application
(PMS System).

Note: The prefixes and the number of digits that follow (being the message number and possible
extra digits) which you have defined must agree with the prefixes and number lengths
defined in the ISPBX. The 'Test with Prefix' option assumes that the ISPBX is configured
correctly, thus does not detect any mismatch.
Testing

Testing the AEM functionality is done by using the facility. The following procedure represents
an application which can be used to test the facility:

1. Login on the SOPHO SuperVisor 60E


2. On an extension activate an AEM that involves the setting of Do Not Disturb.
For example: conform the information in the figures above: dial *573 02 0108.
3. Make a call from another set to this extension
4. Because the extension is set to Do Not Disturb, you will be redirected to the operator.
5. When the operator picks up the call, an envelope will appear on the screen of the SOPHO
SuperVisor 60E
6. When the operator selects this envelope, the message "On holiday until 01/08" will appear.

42
Additional Information

Extension messages from SysManager to PMS can be used for:

- Mini-bar accounting;
- Guest room status;
- Telephone lock.

The messages are transparently sent to the PMS and the PMS should take adequate actions.

43
14. HOW TO PROJECT A VoiceMail SERVER

PROCEDURE: SETUP THE ISPBX FOR A VoiceMail SERVER

Preconditions

Check if your ISPBX has a license for Voice Mail with DILICS:;

You should have: Voice Mail Interface Yes

Options:

LOSYSOP019 - Off Hook Voice Mail Protocol = Yes

LOSYSOP027 - Message waiting queuing softring = Yes

LOSYSOP047 - Post dialling available = Yes

The ALC circuits to which the server is connected must be projected with signalling group
3208: Enquiry by hook-flash.

The DNRs assigned to the ALC circuits must have Facility Class Marks:

• 4 = Data protection;
• 11 = Preferent to operator;
• 32 = Keytone post dialling allowed;
• 33 = Voice mail server.
Actions

1. Assign the 'message waiting LED on/off' prefixes in the initial extension dialling analysis
tree.
ASINTN:<TREE>,<NUMBER>,<TRFC>,<RESULT-ID>[,[<DEST/NUMBER][,<NUMBER-
LENGTH>]];
Example:
ASINTN:0,*57,1,76;
ASINTN:0,*58,1,77;
ASINTN:0,*59,1,78;
ASINTN:0,#57,1,79;
ASINTN:0,#58,1,80;
ASINTN:0,#59,1,81;
2. Assign the required facility class marks to any circuit (DNR) to which the Voice Mail Server

44
is connected.
ASFACM:<FCM>,<BSP-ID>;
Example: ASFACM:4&11&32&33,1200;
Additional Information

For more information, see the Voice-Server Interface Customer Engineer Manual.

45
15. HOW TO PROJECT BAR/UNBAR

PROCEDURE: SETUP THE ISPBX FOR BAR/UNBAR

Preconditions

Boundaries:

NEBOUND004 - Default traffic service class night.

NEBOUND005 - Default traffic service class day.


Actions

1. Check that no restriction exists on changing the traffic class:


DITFCR:3;
If needed change the traffic class restriction level with OM command:
CHTFCR:<TERMINAL-TYPE>,<TRFC>,<RESTRICTION>;
Example: CHTFCR:3,0&&7,0;
Testing

Execute the following procedure:

1. Login on to the external application.


2. Check in a person on a free room.
3. Make an external call from the room extension. Check that the external call is possible.
Go on-hook again.
4. Check out the person in this room.
5. Make an external call from the room extension. Check that you get NU tone (the call is
not possible). Go on-hook again.
6. Restore the original setting for this room.

46
16. HOW TO PROJECT GROUP ARRANGEMENTS FOR
SERVICE EXTENSIONS

PROCEDURE: MULTI-MEMBER GROUP ARRANGEMENTS FOR


SERVICE EXTENSIONS

Preconditions

As an example, the following configuration is assumed:

Service Group
Guest Extensions

Extension X - Member Rank 0


ISPBX Only used for Ringing

2 dialled Single Digit DNR-X


to DNR 9992 Group
DNR-A
Conversion sent DNR
DNR-B
Extension A - Member Rank 1

Extension B - Member Rank 2

Figure 16-1 Multi-member Group Arrangement

Actions

1. Assign the service group.


CRGRPA:<GROUP-DNR>,<GROUP-PROPS>;
Example:
CRGRPA:9992,4;
Enter <MEMBER-BSP-ID>,[<SWITCH-ALL>],<RANK>
[,[<LINE-POS>][,<PARK-POS>]]: 1428,0,0;
Enter <MEMBER-BSP-ID>,[<SWITCH-ALL>],<RANK>
[,[<LINE-POS>][,<PARK-POS>]]: 1304,1,1;

47
Enter <MEMBER-BSP-ID>,[<SWITCH-ALL>],<RANK>
[,[<LINE-POS>][,<PARK-POS>]]: 1306,1,2;
Enter <MEMBER-BSP-ID>,[<SWITCH-ALL>],<RANK>
[,[<LINE-POS>][,<PARK-POS>]]: ;
The actual group properties of this group are:
- Fixed hunting.
- Call Pickup Group / Member is 'yes'.
- Empty Group allowed 'no'.
- Automatic Camp-On-Busy 'yes'.

Note: The first DNR (1428 in the example) may be just a bell instead of a telephone set. When
the group members are too far away to hear the bell, more bells can be put (in parallel)
closer to the members.
2. Assign the 'pickup general' prefix in the initial extension dialling analysis tree.
ASINTN:<TREE>,<NUMBER>,<TRFC>,<RESULT-ID>[,[<DEST/NUMBER][,<NUMBER-
LENGTH>]];
Example: ASINTN:0,*42,1,33;
3. Assign the present / absent prefixes in the initial extension dialling analysis tree.
ASINTN:<TREE>,<NUMBER>,<TRFC>,<RESULT-ID>[,[<DEST/NUMBER][,<NUMBER-
LENGTH>]];
Example:
ASINTN:0,#48,1,35;
ASINTN:0,*48,1,36;
4. Assign facility class mark 'External Service Display' to all extensions of the group.
ASFACM:<FCM>,<BSP-ID>;
ASFACM:28,1428&1304&1306;

PROCEDURE: MAPPING ON EXISTING GROUPS: DIVERSION BY NO


MEMBER ACD GROUP

Preconditions

As an example, the following configuration is assumed:

48
Guest Extensions

ISPBX
No Member
7 dialled Single Digit
to DNR 9997 Group ACD
Conversion sent DNR Group
Service Group

Call
Forwarding
on Night
Extension X - Member Rank 0
Only used for Ringing

2 dialled Single Digit DNR-X


to DNR 9992 Group
DNR-A
Conversion sent DNR
DNR-B
Extension A - Member Rank 1

Extension B - Member Rank 2

Figure 16-2 Diversion to an Existing Group


Actions

1. Assign the 'No Member ACD' group.


CRGRPA:<GROUP-DNR>,<GROUP-PROPS>;
Example:
CRGRPA:9997,29;
Enter unit number :<UNIT>;
Enter ACD group threshold priority [<THRESHOLD-PRIOTITY>],
(default=0):;
Enter 'Full Threshold' [<ACD-THRESHOLD>], (default=100) :;
Enter 'Busy Threshold' [<ACD-THRESHOLD>], (default=100) :;
Enter 'Forced Absent time' [<ACD-TIME-PERIOD>], (default=infinite):;
Enter 'After Call Work time' [<ACD-TIME-PERIOD>], (default=0 sec.):;
Enter 'Call in Queue time' [<ACD-TIME-PERIOD>], (default=infinite):;
Enter Pause tone [<ANN-PAUSE-TONE>], (default=Silence):;
Enter CallManager MIS logical device ACDxxy [<LDN>],
(default='none'):;

49
Enter 'Queue Position Algorithm' [<Q-POS-ALGORITHM>],
(default=absolute):;
Enter ACD group 'Queue Priority' [<Q-PRIORITY>], (default=lowest):;
Enter <MEMBER-BSP-ID>,[<SWITCH-ALL>],<RANK>
[,[<LINE-POS>][,<PARK-POS>]]: ;
2. Assign 'Call Forwarding on Night'.
CHCALF:<CF-TYPE>,<ORIGIN-BSP-ID>,<DEST-NUMBER>;
Example: CHCALF:5,9997,9992;
3. Assign facility class mark 'External Service Display' to all extensions of the group.
ASFACM:<FCM>,<BSP-ID>;
Example: ASFACM:28,1428&1304&1306;

PROCEDURE: SINGLE-MEMBER GROUP ARRANGEMENTS FOR


SERVICE EXTENSIONS

Preconditions

As an example, the following configuration is assumed:

Guest Extensions

ISPBX Service Group

3 dialled Single Digit


to DNR 9993 Group
DNR-A
Conversion sent DNR

Extension A - Member Rank 0

Figure 16-3 Single-member Group Arrangement


Actions

1. Assign the service group.


CRGRPA:<GROUP-DNR>,<GROUP-PROPS>;
Example:
CRGRPA:9993,12;
Enter <MEMBER-BSP-ID>,[<SWITCH-ALL>],<RANK>

50
[,[<LINE-POS>][,<PARK-POS>]]: 1430,1,0;
Enter <MEMBER-BSP-ID>,[<SWITCH-ALL>],<RANK>
[,[<LINE-POS>][,<PARK-POS>]]: ;
The actual group properties of this group are:
- Fixed hunting.
- Call Pickup Group / Member is 'yes'.
- Empty Group allowed 'yes'.
- Automatic Camp-On-Busy 'yes'.

2. Assign 'Call Forwarding on Empty Group'.


CHCALF:<CF-TYPE>,<ORIGIN-BSP-ID>,<DEST-NUMBER>;
Example: CHCALF:3,9993,9992;

Note: When the user of 1430 dials absent (using #48 for example) call forwarding can be done
to another group of service extensions.
3. Assign facility class mark 'External Service Display' to the group extension.
ASFACM:<FCM>,<BSP-ID>;
Example: ASFACM:28,1430;

PROCEDURE: CALL PICK-UP FROM OTHER SERVICE GROUPS

Preconditions

To allow members of a service group to pickup calls from another service group, the group of
which the call is picked up should have the "unrestricted call pickup allowed" set.

CRGRPA:<GROUP-DNR>,<GROUP-PROPS>,,,,<EXT-PROPS>;

Example:

CRGRPA:9992,4,,,,0000001;

Enter <MEMBER-BSP-ID>,[<SWITCH-ALL>],<RANK>

[,[<LINE-POS>][,<PARK-POS>]]: 1428,0,0;

Enter <MEMBER-BSP-ID>,[<SWITCH-ALL>],<RANK>

[,[<LINE-POS>][,<PARK-POS>]]: 1304,1,1;

Enter <MEMBER-BSP-ID>,[<SWITCH-ALL>],<RANK>

[,[<LINE-POS>][,<PARK-POS>]]: 1306,1,2;

51
Enter <MEMBER-BSP-ID>,[<SWITCH-ALL>],<RANK>

[,[<LINE-POS>][,<PARK-POS>]]: ;

The actual group properties of this group are:

- Fixed hunting.
- Call Pickup Group / Member is 'yes'.
- Empty Group allowed 'no'.
- Automatic Camp-On-Busy 'yes'.
- Unrestricted call pickup allowed.

Note: Any extension (within the unit) can pickup a call from a group that has "unrestricted call
pickup allowed" using individual call pickup.

Actions

Assign the 'pickup individual' prefix in the initial extension dialling analysis tree.

ASINTN:<TREE>,<NUMBER>,<TRFC>,<RESULT-ID>[,[<DEST/NUMBER][,<NUMBER-
LENGTH>]];

Example: ASINTN:0,*41,1,34;

52
17. HOW TO SETUP TERMINAL SERVICE DISPLAYS:
TSD/CNND

PROCEDURE: SETUP THE ISPBX FOR TSD/CNND

Preconditions

Check if your ISPBX has a license for CNND with DILICS:;.

You should have: CNND Yes .

Boundaries:

NEBOUND342 - Max number of internal CNND (and CDD) database entries, since
Call@Net 2.6.

NEBOUND350 - Max number of external CNND (and CDD) database entries, since
Call@Net 2.6.

Options:

LOSYSOP099 - Access external CNND database for internal translation.

LOSYSOP101 - Local CNND function active.

LOSYSOP105 - TSD for supervisors active (SuperVisor 25/35).

Timers:

NETIMER185 - SysManager response time limit for service displays (3 seconds).


Actions

For all extension you want TSD to:

Assign facility class mark 'External Service Display'.

ASFACM:<FCM>,<BSP-ID>;

Example: ASFACM:28,1430;

To activate TSD for a SuperVisor 25 or SuperVisor 35, use:

53
CHOPTI:105,1;

Check with: DIMDAT:1,105;

WARNING: MAKE SURE YOU HAVE A CNND LICENSE (DILICS:;).

PROCEDURE: SETUP SysManager FOR TSD/CNND

Preconditions

Make sure that a PhoneWare database (Phonebook) is present and that this database has been
setup correctly using the PhoneWare Phonebook Manager.

For details, see PhoneWare Phonebook Manager Getting Started, section "To Populate an
empty database".

Also see SOPHO SysManager 410 Customer Engineer Manual, chapter "Directory Services
Module" for notes on the field mapping in the Phonebook.
Actions

1. Open the 'Directory Services' from the SysManager configurators menu


2. Select 'Configure'/'Phonebook' from the menu and assign the appropriate database.
3. Select 'Configure'/'Display' from the menu
4. Assign the layout for TSD (internal calling party/guest calling party) and CNND
Use the help information available in the 'Directory Services' menu on composing the
layout.

CAUTION: DO NOT ASSIGN A TSD OR CNND MESSAGE OF MORE THAN 20


CHARACTERS.

Testing

To test TSD/CNND take the following steps:

1. Make a call to an extension with facility class mark 'External Service Display'.
2. Check that a message appears on the display of the extension conform a TSD layout
definition.
3. Make sure that no CNND information about your extension is available in the ISPBX but

54
in the PhoneWare database.
Make a call to an extension with no facility class mark 'External Service Display.'
4. Check that a message appears on the display of the extension conform the CNND layout
definition.

55
18. HOW TO PROJECT SINGLE DIGIT DIALLING

PROCEDURE: SETUP THE ISPBX FOR SINGLE DIGIT DIALLING

Preconditions

Boundaries:

NEBOUND072 - Maximum number of analysis groups.

NEBOUND111 - DNR radix number.

Timers:

NETIMER197 - Overlay dialling time (3 seconds)

As an example, the following configuration is assumed:

Overlay
Analysis tree Timeout Group Pool
1.....9 Overlay Analysis
for Extension Dialling Abbreviated
and Enquiry Digit
Res ID 134 Dialling
Guest Dialling Timeout = 1 conversion via 9991
02 14 Res ID 24
Extensions Overlay Timeout Abbreviated
0 Trunk 9 Oper. Dialled Dialling
Dialling
Access Res ID 11
Res ID 21*

Digit
8 conversion via 9998
Abbreviated
Dialling

Overlay
Continue
Analysis
100... 189
200 … 289
No Timeout = x00 ...x89
15
Overlay Continue 9991 … 9998
Dialling To an Analysis
Tree for
extension
dialling

* If digit zero is used as leading zero for DNRs, trunk access


Code 0 requires overlay dialling

Figure 18-1 Overlay Dialling for Guest Extensions

56
Actions

1. Assign the analysis tree for initial extension dialling for the analysis group.
ASTREE:<TREE>,<DIAL-TYPE>,<AG>;
Example: ASTREE:2,0,11;
2. Assign the analysis tree for enquiry dialling for the analysis group.
Example: ASTREE:2,1,11;
3. Assign the analysis tree for overlay timeout dialling for the analysis group.
Example: ASTREE:14,8,11;
4. Assign the analysis tree for overlay continue dialling for the analysis group.
Example: ASTREE:15,9,11;
5. Define the internal extension numbers in the overlay continue dialling tree.
ASBLCK:<TREE>,<NUMBER>,<TRFC>,<NUMBER-LENGTH>,<RESULT-ID>;
Example:
ASBLCK:15,10,1,3,10;


ASBLCK:15,18,1,3,10;
6. Define the single digits in the initial extension / enquiry dialling tree as overlay dialling.
ASINTN:<TREE>,<NUMBER>,<TRFC>,<RESULT-ID>[,[<DEST/
NUMBER],[,<NUMBER-LENGTH>]];
Example:
ASINTN:2,1,1,134;


ASINTN:2,9,1,134;
7. Define the single digits in the overlay timeout dialling tree as group pool abbreviated
dialling.
ASBLCK:<TREE>,<NUMBER>,<TRFC>,<NUMBER-LENGTH>,<RESULT-ID>;
Example:
ASBLCK:14,1,1,1,24;


ASBLCK:14,8,1,1,24;
8. Define the conversion from abbreviated into expanded number.
CHABNR:<ABBR-NUMBER>[,[<EXP-NUMBER>],[<TRFC>][,<AG>s/r]];
Example:
CHABNR:1,9991,1,11;


CHABNR:8,9998,1,11;

57
Note: The traffic class of the extension must be higher than or equal to the traffic class assigned
in CHABNR to be able to use abbreviated dialling.

58
19. HOW TO PROJECT WAKE-UP

PROCEDURE: SETUP THE ISPBX FOR WAKE-UP

Preconditions

Timers:

NETIMER011 - ARB ringing time.

The internal ring current (tone function 100) is used for wake-up.
Actions

1. Assign the wake-up prefixes in the initial extension dialling analysis tree for the analysis
groups which are allowed to dial this facility.
ASINTN: <TREE>,<NUMBER>,<TRFC>,<RESULT-ID>[,[<DEST/
NUMBER][,<NUMBER-LENGTH>]];
Example:
ASINTN:2,*523,2,82,,4;
ASINTN:2,#523,2,82,,0;
2. Assign the TMS Digit Position.
ASTMSD:<DIGIT-POSITION>;
Example: ASTMSD:4;
Since wake-up is an AEM (window nr. 83), for the wake-up defined in step one the "3" in
*523 and #523 (which is the service digit) is located on the fourth position.
3. Assign TMS announcement code relation for every synchronous announcer.
CHTMST:<ANNOUNCEMENT-CODE>,<ANNOUNCEMENT-SOURCE>[,<UNIT>];
CHTMST:74,1,1;
Enter <DNR> of synchronous announcer:9800;
4. Assign TMS announcement code relation for every continuous (asynchronous) announcer.
Example:
CHTMST:80,3,1;
Enter <SHELF>,<BRD>,<CRT> of continuous announcer:1012,7,29;

PROCEDURE: SETUP SysManager FOR WAKE-UP

Preconditions

The External Application Interface basics are setup, see also .


Actions

59
1. Start the EAI Configurator. From the Start menu choose Programs/SysManager 410/
Configurators/ EAI Configurator.
2. In the "Wake Up Calls" tab, check the general settings for wake up calls.
Select whether SysManager must send wake up status messages to the external
application (PMS System).

3. In the "Languages" tab, define all languages that you have available in the IASA board. Use
the same language abbreviations as used by the external application (PMS system) during
check-in.

60
4. In the "Announcement Devices" tab, define which port/extension is related to each
language (including the 'UNKNOWN' and 'DEFAULT' language). Use the same
announcement codes as defined in the ISPBX. (OM command: CHTMST).

61
5. Check that the prefixes you have assigned for wake-up in the ISPBX are present in the
"Prefixes" tab of the EAI configurator.

62
Testing

When you want to test language dependent announcers use a guest extension, because only
for guests languages are supported.

To test the wake-up facility, take the following steps:

1. Lift the handset of the extension. Dial the wake-up prefix (*523) followed by the test code
9999.

Note: You can also use a wake-up time in HHMM format (0710, for example).
2. Wait for confirmation tone and replace the handset.
3. Now the telephone must start ringing at the time which you have defined.
4. Lift the hand set and check the type of announcement that is to be expected. If a specific
language is used, check that the language is correct.
5. Lift the handset of the extension. Dial the wake-up prefix (*523) followed by the test code
9999.

63
Note: You can also use a wake-up time in HHMM format (0710, for example).

6. Wait for confirmation tone and replace the handset.


7. Lift the handset of the extension. Dial the cancel prefix (#523).
8. Wait for confirmation tone and replace the handset.
9. Check that the extension does not start ringing at the defined time.

64
20. HOW TO PROJECT COST CENTRE DIALLING WITH
TABLE VALIDATION / PID DIALLING

PROCEDURE: SETUP THE ISPBX COST CENTRE WITH TABLE


VALIDATION / PID DIALLING

Preconditions

Boundaries:

BOUND275 - Maximum Number of Integrated Password Dialling (IPD) Entries is filled-in.

Options:

LOSYSOP060 - FDCR instead of Toll-Ticketing = Yes

LOSYSOP084 - Integrated Password Dialling (IPD) = Yes.


Actions

1. Assign the cost centre with table validation / PID prefix (res.id.112) in the initial/enquiry
analysis tree.
ASINTN:<TREE>,<NUMBER>,<TRFC>,<RESULT-ID>[,[<DEST/NUMBER][,<NUMBER-
LENGTH>]];
Examples:
ASINTN:0,#03,1,112,,12;
ASINTN:0,#02,1,112,,16;

Note: If the length of the cost centre number differs from the length of the PID code then different
prefixes with different number lengths must be defined, both with result identity 112.
Testing

Execute the following procedure:

1. Assign a PID or cost centre using the MAC-Manager or using OM command ASPICC.
2. Dial the Cost Centre with Table Validation prefix (res.id.112) followed by a cost centre
number / PID (the cost centre number 999999 is not available a it is reserved for the
malicious call trace facility). If the prefix and the cost centre number / PID are accepted,
then dial tone is sent to the user and the user can initiate a normal external call. If the prefix

65
or the cost centre number is not accepted, the user gets number unobtainable tone.
3. Remove the PID or cost centre using the MAC-Manager or using OM command ERPICC.
Additional Information

Usually, PIDs or cost centres are created using the MAC-Manager or through the PMS.

66