hotel applications - step by step

nten

ts

PREFACE...........................................................................................................2

1. HOW TO CONFIGURE A CCS SYSTEM (IS3070/IS3090) WITH MANAGEMENT@NET ....................................................................................3

2. HOW TO CONFIGURE A CPU3000 SYSTEM WITH

MANAGEMENT@NET ..................................................................................10

3. HOW TO CONFIGURE MANAGEMENT@NET FOR FDCR WITH

TABS 7.X .......................................................................................................15

3.1. IMPORTING COSTING TABLES ............................................................................ 173.2. DEFINING MARKUPS, FIXED CHARGES AND TAXES ........................................ 17

4. HOW TO PROJECT THE EXTERNAL APPLICATION INTERFACE ...........18

5. HOW TO PROJECT AN IASA .......................................................................20

6. HOW TO PROJECT AN ALC-G ....................................................................23

7. HOW TO PROJECT THE HOWLER FUNCTION .........................................25

8. HOW TO PROJECT DND ..............................................................................27

9. HOW TO PROJECT ANALYSIS GROUPS IN THE ISPBX ..........................30

10. HOW TO PROJECT MEM ..............................................................................33

11. HOW TO PROJECT AEM ..............................................................................35

12. HOW TO PROJECT A VOICEMAIL SERVER ................................................39

13. HOW TO PROJECT BAR/UNBAR ................................................................41

14. HOW TO PROJECT GROUP ARRANGEMENTS FOR SERVICE EXTENSIONS ................................................................................................42

15. HOW TO SETUP TERMINAL SERVICE DISPLAYS: TSD/CNND ...............48

16. HOW TO PROJECT SINGLE DIGIT DIALLING ...........................................51

17. HOW TO PROJECT WAKE-UP .....................................................................54

18. HOW TO PROJECT COST CENTRE DIALLING WITH TABLE

VALIDATION / PID DIALLING .....................................................................60

i

Tab

le o

f Co

ii

Table of C

ontents

1

Release date : 01/Oct/2010

iS3000 Series / Management@NetHotel Application - Step by Step

2

PREFACE

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

• Any iS3000 model running Call@Net 2.8 or higher or running SIP@Net 4.0 or higher• Management@Net, release 3.0 or higher• SuperVisor 60E, release 3.2 or higher• A suitable Property Management System (PMS)

3

1. HOW TO CONFIGURE A CCS SYSTEM (iS3070/iS3090) WITH Management@Net

PROCEDURE: SETUP THE ISPBX: PORT ALLOCATION AND DEVICE ASSIGNMENT

Preconditions

Licenses:

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:

Figure 1-1 Connection between BIM and Management@Net

Actions

1. Assign V.24 Port.ASPORT:<SHELF>,<BRD>,<CRT>,<PROTOCOL-TYPE>,<CONNECTION-TYPE>;Example: Local Management@Net connection to port 2 of the CIE:ASPORT:1014,10,2,2;

2. Assign Devices.ASDEVC:<SHELF>,<BRD>,<CRT>,<LND>,<EQUIPMENT-TYPE>;Example: Local Management@Net connection to port 2 of a CIE with Full Detailed Call Recording, Switching Services and OM:

CIE

(CCS)

FDCR/SS/OMBIM

Management@Net

4

ASDEVC:1014,10,2,FDCRIP,33; Equipment type 33 is for FDCR over IP.ASDEVC:1014,10,2,SYSMSS,29;ASDEVC:1014,10,2,VDU020,20;ASDEVC:1014,10,2,VDU021,21;

3. Set port in service:SETINS:1014,10,2;

4. To display the settings, use:DIPORT:<SHELF>,<BRD>,<CRT>;

5. 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 Management@Net 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:

Note: This command must only be executed for the unit to which Management@Net is connected.

2. Assign the TMS logical name relation (this is only needed for the "high" windows).CHTMSL:<WINDOW>,<LDN>[,<UNIT>];Examples:

ASTMSW:2,2,1; Used for wake upASTMSW:3,3,1; Used for message waiting without announcementASTMSW:4,3,1; Used for automatic directory diallingASTMSW: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 CNNDASTMSW:83,1,1; Used for Automatically Entered Messages and wake up requests

5

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

PROCEDURE: SETUP THE ISPBX FOR FULL DETAILED CALL RECORDING

Preconditions

Licenses:

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

You should have: FDCR Yes and Cost Accounting 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:FDCRIP,2,1;

4. Start the FDCR output.STRTFR:<FILE-NAME>;Example: STRTFR:TICKET;

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

requests

6

PROCEDURE: PROJECT IP CONNECTION IN THE CCS

A Client Server Profile must be set in the ISPBX and is needed for PVE, OM, SS and FDCR over IP, see steps below.Preconditions

Check the Options and Boundaries as specified in the Management@Net CE Manual for the iS3000.

Also check how to use a BIM as a router as specified in the Management@Net CE Manual for the iS3000.Actions

1. Use the OM, SS and FDCR devices of one of the ports of the CIE-2. You can use the devices defined earlier in this chapter on port 1014,10,2.

2. 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 Management@Net server and 1 is the Client Service Profile id.

3. Assign the required services to the Client Service Profile. Examples: CHPROF:1,0,1,VDU210; where 1 is the Client Service Profile id, 0 means OM, 1 means allowed and VDU020 is the logical device name of the OM connection from step 1; CHPROF:1,1,1,SYSMSS; where 1 is the Client Service Profile id, 1 means SS, 1 means allowed and SYSMSS is the logical device name of the SS connection from step 1; 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 from step 1.

PROCEDURE: SETUP Management@Net: CONNECTION TO ISPBX

Preconditions

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

1. Start the CM@Net Configurator. From the Start menu choose Programs/Management@Net/Configurators/CM@Net Connection Configurator.

2. In the CM@Net Configurator, from the menu, select Create and PBX CCS.3. In the Connection Wizard: Fill in the Destination Name, select the Unit Number, and

enter the IP Address of the BIM. Press Finish.

7

4. For a multi unit system, add additional units to the PBX in the list. This is needed for the equipment licenses in Management@Net.

5. Select the main unit from the list. Select the Advanced Settings check box and make sure that the following check boxes are set:- Call Reporting Module (FDCR); The check box ‘Buffered’ must NOT be set!!- Switching Services;- Optionally, PVE.

Note: The main unit in a multi unit system is the unit that has the direct connection to Management@Net for FDCR and Switching Services.

6. Select the any other unit from the list. Select the Advanced Settings check box and make sure that NO check boxes are set.

7. Press Apply and close the CM@Net Configurator.Testing

Use the ISPBX Destination Activator to test the interface between the ISPBX and Management@Net.

8

Figure 1-2 CCS configuration example in the CM@Net Configurator - main unit

9

Figure 1-3 CCS configuration example in the CM@Net Configurator - any other unit

10

2. HOW TO CONFIGURE A CPU3000 SYSTEM WITH Management@Net

PROCEDURE: SETUP THE ISPBX: PORT ALLOCATION AND DEVICE ASSIGNMENT

Preconditions

Licenses:

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:

Figure 2-1 Connection between CPU3000 and Management@Net

Actions

1. Assign V.24 Port.ASPORT:<SHELF>,<BRD>,<CRT>,<PROTOCOL-TYPE>,<CONNECTION-TYPE>;Example: Local Management@Net connection to port 21 on the CPU-3000 in an iS3030:ASPORT:12,8,21,1,0; BCS protocol.

iS3010IS3030iS3050

CPU3000

Management@Net

FDCR/SS/OM

11

2. Assign Devices.ASDEVC:<SHELF>,<BRD>,<CRT>,<LDN>,<EQUIPMENT-TYPE>;Example: Local Management@Net connection to port 21 on the CPU-3000 in an iS3030 with Full Detailed Call Recording, Switching Services and OM:ASDEVC:12,8,21,FDCRIP,33; Equipment type 33 is for FDCR over IP.ASDEVC:12,8,21,SYSMSS,29;ASDEVC:12,8,21,VDU210,20;ASDEVC:12,8,21,VDU211,21;

3. Set port in service:SETINS:12,8,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:

Note: This command must only be executed for the unit to which Management@Net is connected.

2. Assign the TMS logical name relation (this is only needed for the "high" windows).CHTMSL:<WINDOW>,<LDN>[,<UNIT>];Examples:

ASTMSW:2,2,1; Used for wake upASTMSW:3,3,1; Used for message waiting without announcementASTMSW:4,3,1; Used for automatic directory diallingASTMSW: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 CNNDASTMSW:83,1,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

Licenses:

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

You should have: FDCR Yes and Cost Accounting 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:FDCRIP,2,1;

4. Start the FDCR output.STRTFR:<FILE-NAME>;Example: STRTFR:TICKET;

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

requests

13

PROCEDURE: PROJECT IP CONNECTION IN THE CPU3000

A Client Server Profile must be set in the ISPBX and is needed for PVE, OM, SS and FDCR over IP, see steps below.Preconditions

Check the Options and Boundaries as specified in the Management@Net CE Manual for the iS3000.Actions

1. Use the OM, SS and FDCR devices of one of the V.24 ports of the CPU3000. You can use the devices defined earlier in this chapter on port 12,8,21.

2. 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 Management@Net server and 1 is the Client Service Profile id.

3. Assign the required services to the Client Service Profile. Examples: CHPROF:1,0,1,VDU210; where 1 is the Client Service Profile id, 0 means OM, 1 means allowed and VDU210 is the logical device name of the OM connection from step 1; CHPROF:1,1,1,SYSMSS; where 1 is the Client Service Profile id, 1 means SS, 1 means allowed and SYSMSS is the logical device name of the SS connection from step 1; 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 from step 1.

PROCEDURE: SETUP Management@Net: CONNECTION TO ISPBX

Preconditions

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

1. Start the CM@Net Configurator. From the Start menu choose Programs/Management@Net/Configurators/CM@Net Connection Configurator.

2. In the CM@Net Configurator, from the menu, select Create and PBX CPU3000.3. In the Connection Wizard: Fill in the Destination Name, select the Unit Number, and

enter the IP Address of the CPU3000. Press Finish.4. Select the PBX from the list. Select the Advanced Settings check box and make sure that

the following check boxes are set:- Call Reporting Module (FDCR); The check box ‘Buffered’ must NOT be set!!

14

- Switching Services;- Optionally, PVE.

5. Press Apply and close the CM@Net Configurator.Testing

Use the ISPBX Destination Activator to test the interface between the ISPBX and Management@Net.

Figure 2-2 CPU3000 configuration example in the CM@Net Configurator

15

3. HOW TO CONFIGURE Management@Net FOR FDCR WITH TABS 7.x

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

Preconditions

This procedure assumes the installation of Management@Net 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 4. "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 Management@Net - 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.

16

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 tab, make sure that the polling interval is once a day or longer. This is

under 'Connect Every'- In the Polling tab, make sure that the Polling policy is set to 'Collect all records'- 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 OR SOPHO805 V.1N OR SOPHO805 V.2N) DO NOT EDIT ANY FIELDS, SINCE THE FORMAT FILES CONTAIN 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. 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.9. Edit the file "tabsite.ini" as follows:

- Find the file "tabsite.ini" in C:\Philips\Data Files\Management@Net\Tabs\db\<ISPBX Name>. "C:" is assumed to be the drive where you installed Management@Net.

- 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. 5. Change the startup setting of the Call Collector as follows:

17

- 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 -FromApp11. Start the TABS Call Collector.

3.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.

3.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.

18

4. HOW TO PROJECT THE EXTERNAL APPLICATION INTERFACE

PROCEDURE: GENERAL EAI SETUP IN Management@Net

Actions

Use chapter "Connection Manager" from the Management@Net 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 EAI Configurator. From the Start menu choose Programs/Management@Net/Configurators/EAI Configurator.

2. In the "Connection" tab, select the ISPBX. The name is taken from the CM database.

3. Choose COM / V.24 if the connection to the PMS system is over a V.24 cable. Then select the COM port from the drop down list. After pressing the Settings button, you can set the

19

speed, number of data bits, parity bit, stop bits and flow control.Choose TCP?IP if the connection to the PMS system is over Ethernet. Note that the TCP/IP port is 4000 by default, but it can be changed.

4. 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. For example 10 means 1 SOPHO Unit is 10 Euro cents.

20

5. 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 VoiceManager 110).

Figure 5-1 IASA Board Layout

Mark

BP

BB

BA

FAC *(SCU

FCCV.24

LEDsGreenRedYellow

to SN

BIST Connector

1

X4.1

X5.1X1.1102/201 108/208

Factorytest only

Extra memory board

Extra memory board Extra memory board

8

X3.1103 101

102

X3.2103 101

102

20

X6.3

X2.

1

20X2.

324

20

X6.2

X2.

20X2.

3 121

2

420

X6.1

X2.

1

20X2.

324

* This connector is not used by the IASA

These are connectors onto which memory boards can be

21

The IASA can have up to three extra memory boards which increase the speech recording capacity:

PROCEDURE: PROJECTING THE IASA

Actions

1. Assign the board (for 30 ports).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.

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,31;ASPCTB:1012,7,31,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>;

NUMBER OF MEMORY BOARDS

CAPACITY WITH 1 MB MEMORY BOARDS

CAPACITY WITH 4MB MEMORY BOARDS

0 31 seconds 31 seconds




22

Example:SETINS:1012,7;SETINS:1012,7,2&&31;

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 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.

23

6. 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 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;

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>;

24

Example: ASFACM:52,1000;

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

25

7. 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.Enter <TONE-SRC>,<LEVEL-INDICATOR>:7,0;Where 7=tone source 1800 Hz and 0=tone level of 0 dBm.

26

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.

27

8. 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;

PROCEDURE: SETUP Management@Net FOR DND

Preconditions

28

The External Application Interface is installed with Full Licence.

The External Application Interface basics are setup, see 4. "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 11. "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 Management@Net 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:

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

29

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.

30

9. 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:

31

Figure 9-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 floorCHAGCV:301&&389,13; Analysis group for guests at the third floorCHAGCV:1900&&1999,0; Analysis group for service extensions at the first floor

Hotel SOPHO

Analysis Group 13

Guests on 3rd Floor

Analysis Group 12

Guests on 2nd Floor

Analysis Group 11

Guests on 1st Floor

Analysis Group 1

Staff

Floor 3

Floor 2

Floor 1

GroundFloor

Analysis Group 0

Services on 3rd Floor

Services on 2nd Floor

Services on 1st Floor

32

CHAGCV:2900&&2999,0; Analysis group for service extensions at the second floorCHAGCV:3900&&3999,0; Analysis group for service extensions at the third floorCHAGCV:9900&&9999,1; Analysis group for staff extensions

33

10. 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 ErgoLines (Digital 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 Management@Net FOR MESSAGE WAITING NO ANNOUNCEMENT

Preconditions

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

The SuperVisor that is used to enter the Manually Entered Messages must be configured to use the same PhoneWare database as the [email protected]

Testing the MEM functionality is done by using the facility. The following procedure represents

34

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 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 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).

35

11. 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 Management@Net FOR AEM

Preconditions

The Management@Net and the (Master) 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/Management@Net/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.

36

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.

37

4. Select whether Management@Net 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 SuperVisor 60E2. 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 extension4. Because the extension is set to Do Not Disturb, you will be redirected to the operator.

38

5. When the operator picks up the call, an envelope will appear on the screen of the SuperVisor 60E

6. When the operator selects this envelope, the message "On holiday until 01/08" will appear.Additional Information

Extension messages from Management@Net 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.

39

12. HOW TO PROJECT A VoiceMail SERVER

PROCEDURE: SETUP THE ISPBX FOR A VoiceMail SERVER

Preconditions

Licenses:

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

40

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.

41

13. 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.

42

14. HOW TO PROJECT GROUP ARRANGEMENTS FOR SERVICE EXTENSIONS

PROCEDURE: MULTI-MEMBER GROUP ARRANGEMENTS FOR SERVICE EXTENSIONS

Preconditions


Figure 14-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;Enter <MEMBER-BSP-ID>,[<SWITCH-ALL>],<RANK>[,[<LINE-POS>][,<PARK-POS>]]: 1306,1,2;

DNR-X

DNR-ADNR-B

GroupDNR

Single Digitto DNRConversion

2 dialled9992sent

ISPBX

Guest Extensions

Extension X - Member Rank 0Only used for Ringing

Extension A - Member Rank 1

Extension B - Member Rank 2

Service Group

43

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


44

Figure 14-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>],

ISPBX

CallForwardingon Night

No MemberACDGroup

DNR-X

DNR-ADNR-B

GroupDNR


2 dialled9992sent

Extension X - Member Rank 0Only used for Ringing


Extension B - Member Rank 2

Service Group

GroupDNR


7 dialled9997sent

Guest Extensions

45

(default='none'):;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


Figure 14-3 Single-member Group Arrangement

Actions

1. Assign the service group.CRGRPA:<GROUP-DNR>,<GROUP-PROPS>;Example:

DNR-AGroupDNR


3 dialled9993sent

ISPBX

Guest Extensions


Service Group

46

CRGRPA:9993,12;Enter <MEMBER-BSP-ID>,[<SWITCH-ALL>],<RANK>[,[<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;


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


47

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


[,[<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;

48

15. HOW TO SETUP TERMINAL SERVICE DISPLAYS: TSD/CNND

PROCEDURE: SETUP THE ISPBX FOR TSD/CNND

Preconditions

Licenses:

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

You should have: CNND Yes .

[Optionally, on top of CNND you can have CDD. CDD is Central Directory Dialling and is used to browse (and dial) from an ErgoLine D325/D330/D340 using the internal CNND or external CNND database. For internal CDD, you should have CDD Yes; for external CDD, you should have ECDD Yes. A full decription of CDD is outside the scope of the Hotel Application.]

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 - Management@Net response time limit for service displays (3 seconds).Actions

For all extension you want TSD to:

Assign facility class mark 'External Service Display'.

49

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

Example: ASFACM:28,1430;

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

CHOPTI:105,1;

Check with: DIMDAT:1,105;

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

PROCEDURE: SETUP Management@Net 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 Management@Net for iS3000 - Customer Engineer Manual, chapter "Directory Services Module" for notes on the field mapping in the Phonebook.Actions

1. Open the 'Directory Services' from the Management@Net configurators menu2. Select 'Configure'/'Phonebook' from the menu and assign the appropriate database.3. Select 'Configure'/'Display' from the menu4. 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:

50

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

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.

51

16. 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)


Figure 16-1 Overlay Dialling for Guest Extensions

Actions

02

1.....9 OverlayDialling

0 Trunk

Res ID 134

AccessRes ID 21*

Analysis treefor Extensionand EnquiryDiallingGuest

ExtensionsTimeout = 14

Group PoolAbbreviated

Digitconversion viaAbbreviated

Dialling

Digitconversion viaAbbreviated

Dialling

OverlayTimeoutAnalysis

9 Oper. Dialled

DiallingRes ID 24

Res ID 11

Overlay TimeoutDialling

No Timeout = 15

OverlayContinueAnalysis

To an AnalysisTree forextensiondialling

* If digit zero is used as leading zero for DNRs, trunk access Code 0 requires overlay dialling

99911

99988

9991 … 9998

100... 189200 … 289x00 ...x89

Overlay ContinueDialling

52

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;••

53

CHABNR:8,9998,1,11;

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.

54

17. 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 Management@Net FOR WAKE-UP

Preconditions

The External Application Interface basics are setup, see also .Actions

1. Start the EAI Configurator. From the Start menu choose Programs/Management@Net/

55

Configurators/EAI Configurator.2. In the "Wake Up Calls" tab, check the general settings for wake up calls.

Select whether Management@Net 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.

56

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).

57

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

58

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

59

9999.

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.

60

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

PROCEDURE: SETUP THE ISPBX COST CENTRE WITH TABLE VALIDATION / PID DIALLING

Preconditions

Licenses:

Check if your ISPBX has a license for Integrated Password Dialling with DILICS:;

You should have: IPD Yes

Note that this is a numeric license. It defines the maximum numder of allowed password entries. For the actual number of entries, see also BOUND275 below.

Boundaries:

BOUND275 - Maximum Number of IPD Entries. This is the sum of all Password, PID and Cost Centre relations.

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

61

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.....9 is not available as 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 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.

hotel applications - step by step

Documents