PREFACE ...........................................................................................................2 1. 2. 2.1. 2.2. INTRODUCTION ............................................................................................3 SOPHO IS3000 SETUP ....................................................................................4 PABX Requirements ..................................................................................................

4 Configuring the MyMail@Net application Lines in ISPBX ......................................... 4 2.2.1. Configuring Analogue Lines Without Polarity Reversal .................................. 5 2.2.2. Configuring Analogue Lines WITH Polarity Reversal ..................................... 6 SOPHO iS3000 - MyMail@Net integration ............................................................... 9 2.3.1. MyMail@Net 510 Integration ........................................................................ 9 2.3.2. MyMail@Net 560 Integration ...................................................................... 10 SOPHO 2000 IPS SETUP ..............................................................................12 Centralized Voice mail ............................................................................................. 17 SOPHO 2000 IPS - MyMail@Net integration .......................................................... 18 3.2.1. MyMail@Net 510 Integration ...................................................................... 18 3.2.2. MyMail@Net 560 Integration ...................................................................... 19

2.3.

3. 3.1. 3.2.

Table of Contents i

Table of Contents

ii

MyMail@Net 510-560 PABX Setup Guide

Release date : 20/oct/2006

PREFACE
This document describes the steps to configure the SOPHO iS3000 and the SOPHO 2000 IPS for a correct inter working with the MyMail@Net 510 and MyMail@Net 560 application. REFERENCES ISPBX documentation MyMail@Net Installation Guide MyMail@Net System Manager Guide

1.

Introduction

The PABX is connected to the MyMail@Net application by means of analogue lines. The physical connection is made between an ALC board in the PABX and one or more Dialogic boards in the MyMail@Net Server computer. The SOPHO iS3000 PABX uses the off hook protocol to inform the MyMail@Net application. The SOPHO 2000 IPS uses a dedicated MCI link (V.24) for this purpose. The PABX configuration is described per type of PABX. Refer to chapter 2. "SOPHO iS3000 Setup" if the PABX is a SOPHO iS3000. Refer to chapter 3. "SOPHO 2000 IPS Setup" if the PABX is a SOPHO 2000 IPS.

2.

SOPHO iS3000 Setup

This chapter describes the steps needed to configure the SOPHO iS3000 for a correct inter working with the MyMail@Net 510-560. There is no difference between the MyMail@Net 510 and the MyMail@Net 560 regarding the interface to the SOPHO iS3000, therefore the following information is applicable for the MyMail@Net 510 as well as for the MyMail@Net 560.

2.1.

PABX Requirements

The system will work, only when you have the correct values for the ISPBX options for the MyMail@Net application configuration. Use the DIMDAT command to read out the values. If necessary, correct them. To correct them, make a retrieve, make changes, restore the projecting files into the system and reproject the system. The Second Line Maintenance Manual describes how to do this. Options: LOSYSOP 019 - Off hook Voice Mail Protocol must be set to "Yes". Use the OM command DIMDAT to check this option. If not correct, use the OM command: CHOPTI:19,1 to correct this.

Note: This is only applicable if the "Voice Mail Interf." licence is granted Check with the DILICS command Licence 010 "Voice Mail Interf" LOSYSOP051 - Ignore Progress Indicator in ISDN Release Protocol. If you use Polarity Reversal on the Analogue lines to the MyMail@Net application, It is stongly recommended to set this option to "Yes". (When you set this option to "Yes", the progress indicator on digital line is ignored after receiving a "disconnect" message. Polarity reversal uses the same mechanism as the digital lines, however, it does not use the Progress Indicator.) Use the OM command: CHOPTI:51,1 to set to "Yes".

2.2.

Configuring the MyMail@Net application Lines in ISPBX

The MyMail@Net application uses analogue lines to connect the ISPBX to the Dialogic voice boards. For this purpose, the ISPBX must be equipped with ALC boards. There are two options for the line configuration: Analogue Lines without Polarity Reversal; The MyMail@Net application uses noise to detect if a phone is answered, by means of the voice of the person on the phone.

Analogue lines with Polarity Reversal. Polarity Reversal on the IVR Lines provides a reliable way to inform the MyMail@Net application that a person has answered his/her phone.

Determine which line type you need to configure and select the appropriate subsection.

2.2.1.

Configuring Analogue Lines Without Polarity Reversal

Execute the following procedure to configure the analogue lines WITHOUT Polarity Reversal in the ISPBX. 1. Check if the Signalling Group that is used for the analogue lines to the MyMail@Net application supports "Hookflash". Use the OM command DIBRDS to display the Signalling Group that is used. The most commonly used Signalling Group for hookflash is SG 3208. For other Signalling Groups, consult the Appendix "Boards and PCT Types" in the OM Commands Manual or the Signalling Data Manual. Also, check if you need more than 8 circuits on an ALC that require SG3208. If so, you need to change the byte in the signalling group that specifies the maximum number of hook flash circuits on the board. 2. If you need to change the maximum number of circuits using hookflash on an ALC from 8 to 16, change byte 6 in Signalling Group 3208 to value 16 (default setting is 8). Execute the following OM commands: CHPMPD and STWARM. Example for a single Unit system:
CHPMPD:0,3208; <ITEM-NBR>,<BIT/BYTE>[,<DATA>]:6,1,16; <ITEM-NBR>,<BIT/BYTE>[,<DATA>]:;

Execute a warm start to make these settings active, use OM command STWARM:; 3. If the Signalling needs to be changed to SG 3208, due to step 1 in this procedure, you can assign a Signalling Group to one or more individual circuits on the ALC, leaving the other circuits with their default Signalling Group. To change the Signalling group of an individual circuit, use OM commands DEPCTB and ASPCTB 4. The hookflash time should be set long enough to recognize hookflashes between 90 and 700 milliseconds. To change the hookflash timers, modify the appropriate signalling group with OM command CHPMPD as follows: Byte 0 = 70 (upper hookflash boundary = 700 ms), Byte 1 = 9 (lower hookflash boundary = 90 ms).

Example for a single Unit system:

CHPMPD:0,3208; <ITEM-NBR>,<BIT/BYTE>[,<DATA>]:0,1,70; <ITEM-NBR>,<BIT/BYTE>[,<DATA>]:1,1,9;

5. Execute a warm start to make these settings active, use OM command STWARM:; 6. Check System Option 19 (Offhook Protocol). This should be set to "Yes". To check, use OM command: DIMDAT:1,19; To change, use the second line maintenance command: CHOPTI:19,1; 7. Assign Facility Class Mark 33 (voicemail server) to each line that is connected to the MyMail@Net application. Use OM command ASFACM: Example:
ASFACM:33,200&&203;

8. It is recommended to assign FCM 47 (overrule CLIR) as well, to the MyMail@Net application lines. Use OM command ASFACM: Example:
ASFACM:47,200&&203;

9. Put the MyMail@Net application lines in a hunting group. Use OM Command CRGRPA with group property 17. Example:
CRGRPA:299,17; 200,0,0; 201,0,1; 202,0,2; 203,0,3;

DNR 299 is now the access number for customers to your MyMail@Net application. At this moment the PABX configuration is finished. Continue with the installation and configuration of the MyMail@Net application, refer to the Installation Manual and the System Management Manual of the MyMail@Net application.

2.2.2.

Configuring Analogue Lines WITH Polarity Reversal

This section describe how to set up "Polarity Reversal" in the ISPBX. Also in the MyMail@Net application, you must enable "Polarity Reversal". This is explained in the MyMail@Net System Management Guide.

System Requirements for Polarity Reversal: Call@Net 2.7b or higher; PMC firmware F14100.801 or F15100.801 or higher; Analogue line circuit boards: ALC-F or ALC-G only.

Note: You need to make changes in SG3208 to enable Polarity Reversal. These changes disable the Message Waiting Indication lamp on analogue telephone sets connected via ALC-F or ALC-G using Hook Flash. In PMC packages higher than F1410.10.01 or F1510.10.01, you do not need to change the signalling group anymore, because later versions support a new dedicated signalling group for IVR Polarity Reversal. This is signalling group 321E. Philips recommends to use the new signalling group if polarity reversal is required. Execute the following procedure to configure the analogue lines with Polarity Reversal. 1. Check if the Signalling Group that is used for the analogue lines to the MyMail@Net application supports "Hookflash". Use the OM command DIBRDS to display the Signalling Group that is used. The most commonly used Signalling Group for hookflash is SG 3208. For other Signalling Groups, consult the Appendix "Boards and PCT Types" in the OM Commands Manual or the Signalling Data Manual. Also, check if you need more than 8 circuits on an ALC that require SG3208. If so, you need to change the byte in the signalling group that specifies the maximum number of hook flash circuits on the board. 2. If you need to change the maximum number of circuits using hookflash on an ALC from 8 to 16, change byte 6 in Signalling Group 3208 to value 16 (default setting is 8). Execute the following OM commands: CHPMPD and STWARM. Example for a single Unit system:
CHPMPD:0,3208; <ITEM-NBR>,<BIT/BYTE>[,<DATA>]:6,1,16; <ITEM-NBR>,<BIT/BYTE>[,<DATA>]:;

Execute a warm start to make these settings active, use OM command STWARM:; 3. If the Signalling needs to be changed to SG 3208, due to step 1 in this procedure, you can assign a Signalling Group to one or more individual circuits on the ALC, leaving the other circuits with their default Signalling Group. To change the Signalling group of an individual circuit, use OM commands DEPCTB and ASPCTB 4. The hookflash time should be set long enough to recognize hookflashes between 90 and 700 milliseconds. To change the hookflash timers, modify the appropriate signalling group

with OM command CHPMPD as follows: Byte 0 = 70 (upper hookflash boundary = 700 ms), Byte 1 = 9 (lower hookflash boundary = 90 ms). Note: Only applicable for Analogue connections (ALC boards). Example for a single Unit system:
CHPMPD:0,3208; <ITEM-NBR>,<BIT/BYTE>[,<DATA>]:0,1,70; <ITEM-NBR>,<BIT/BYTE>[,<DATA>]:1,1,9;

5. Set bit 9 in SG3208 to "1" to enable Polarity Reversal" on the circuits using SG3208. Execute OM command CHPMPD. Example for a single Unit system:
CHPMPD:0,3208; <ITEM-NBR>,<BIT/BYTE>[,<DATA>]:9,0,1; <ITEM-NBR>,<BIT/BYTE>[,<DATA>]:;

Note: In PMC packages higher than F1410.10.01 or F1510.10.01, you do not need to change the signalling group anymore, because later versions support a new dedicated signalling group for IVR Polarity Reversal. This is signalling group 321E. Philips recommends to use the new signalling group if polarity reversal is required. 6. Execute a warm start to make these settings active, use OM command STWARM:; 7. Check System Option 19 (Offhook Protocol). This should be set to "Yes". To check, use OM command: DIMDAT:1,19; To change, use the second line maintenance command: CHOPTI:19,1; 8. Assign Facility Class Mark 33 (voicemail server) to each line that is connected to the MyMail@Net application. Use OM command ASFACM: Example:
ASFACM:33,200&&203;

9. It is recommended to assign FCM 47 (overrule CLIR) as well, to the MyMail@Net application lines. Use OM command ASFACM: Example:
ASFACM:47,200&&203;

10. Put the MyMail@Net application lines into a hunting group. Use OM Command CRGRPA with group property 17. Example:

CRGRPA:299,17; 200,0,0; 201,0,1; 202,0,2; 203,0,3;

DNR 299 is now the access number for customers to your MyMail@Net application. At this moment the PABX configuration is finished. Continue with the installation and configuration of the MyMail@Net application, refer to the Installation Manual and the System Management Manual of the MyMail@Net application.

2.3.

SOPHO iS3000 - MyMail@Net integration

This chapter describes the configuration of the MyMail@Net application for a correct integration with the SOPHO iS3000. The integration is described in two sections: The MyMail@Net 510 settings are described in chapter 2.3.1. "MyMail@Net 510 Integration". The MyMail@Net 510 settings are described in chapter 2.3.2. "MyMail@Net 560 Integration". Only the most important settings are described in this manual. For more information regarding integration, refer to the MyMail@Net Integration guide.

2.3.1.
-

MyMail@Net 510 Integration

Connecting the systems: The physical connections between the PABX and the MyMail@Net are described in the MyMail@Net 510 Integration Guide.

Note: The RS-232 connection is only required for a 2000 IPS PABX that makes use of the MCI integration. For a iS3000 only the analogue connections are required between the Dialogic board and the ALC boards. Select the correct switch: Select "Switch" from the System menu. Select "PHILIPS - Sopho iS3000" from the pull down menu. Configure the access numbers: Select "Configuration" from the System menu. Select "Access Numbers" Enter in the field "Pilot #" the IVR group number. Enter the extensions in the field "Station numbers". Make sure that the sequence is correct, start with the extension that is connected to the 1st Dialogic line followed by the extension connected to the 2nd Dialogic line etc.

Port Configuration: Select "Ports" from the System menu Select "Answer/Dial out" for all ports that are used. If a lot of dial out actions are required, you may consider to select "Dial out only" for the last couple of ports. As indication, a iS3000 requires more dial out actions than a 2000 IPS with MCI integration. MWI configuration: Select "Switch" from the System menu. Select MWI. Check in the PABX which prefixes are used for activating and deactivating MWI. Enter the activate MWI prefix in the field "On (activation) code" followed by a comma and a "X" (e.g. *610,X). The "X" represents the extension that must be activated. Enter the de-activate MWI prefix in the field "Off (deactivation) code" followed by a comma and a "X" (e.g. #610,X). Live Record: Select "Switch" from the System menu. Select "Live Record" Check in the PABX which prefix is used for "break in" (res-ID 58). Enter a "X" followed by a comma and enter the "break in" prefix. (e.g. X,*1) in the field "Barge-in code" Hookflash Time Definition: Select "Switch" from the menu System. Select "Dialout" Check that the Hookflash Time Definition for the "percent (%)" is set to 10 Centiseconds. (100 ms) Select "Switch" from the menu System. Select "Dialing codes" Change the "&" in the fields "initiate sequence" , "recall sequence" and "busy recall sequence" to an "%"

2.3.2.
-

MyMail@Net 560 Integration

Connecting the systems: The physical connections between the PABX and the MyMail@Net are described in the MyMail@Net 560 Integration Guide.

Note: The RS-232 connection is only required for a 2000 IPS PABX that makes use of the MCI integration. For a iS3000 only the analogue connection are required between the Dialogic board and the ALC boards. Select the correct switch: During the software installation you can select the correct switch. It is also possible to select the switch after installation. Open the Switch Selector utility from, Start/Programs/Repartee for Windows 2000/ Server Utilities. Select Philips from the "Manufacturer" pull down menu And select the correct switch from the "Model" pull down menu. Select "Sopho iS3000 w/INT" from the pull down menu.

10

Configure the access numbers: Select "Switch" from the Console Root. Double click "Switch Settings". Select the "General" tab. Enter in the field "Pilot number" the IVR group number. Select "Supported Ports" from the "Ports" menu. Select the "General" tab. Double click each port and enter the correct IVR extension in the field "Station number" Make sure that the sequence is correct, start with the extension that is connected to the first Dialogic line followed by the extension connected to the second Dialogic line etc. Port Configuration: Select "Supported Ports" from the "Ports" menu. Select the "General" tab. Select "Answer/Dial out" for all ports that are used. If a lot of dial out actions are required, you may consider to select "Dial out only" for the last couple of ports. As indication, a iS3000 requires more dial out actions than a 2000 IPS with MCI integration. MWI configuration: Select "Switch" from the Console Root. Double click "Switch Settings". Select the "MWI" tab. Check in the PABX which prefixes are used for activating and deactivating MWI. Enter the activate MWI prefix in the field "On (activation) code" followed by a comma and a "X" (e.g. *610,X). The "X" represents the extension that must be activated. Enter the de-activate MWI prefix in the field "Off (deactivation) code" followed by a comma and a "X" (e.g. #610,X). Live Record: Select "Switch" from the Console Root. Double click "Switch Settings". Select the "Live Record" tab Check in the PABX which prefix is used for "break in" (res-ID 58). Enter a "X" followed by a comma and enter the "break in" prefix. (e.g. X,*1) in the field "Barge-in code" Hookflash Time Definition: Select "Switch" from the Console Root. Double click "Switch Settings". Select the "Dialout" tab. Check that the Hookflash Time Definition for the "percent (&)" is set to 100 milliseconds.

More detailed information can be found in the MyMail@Net 560 Integration Guide and the on-line Help function in the HTML console.

11

3.

SOPHO 2000 IPS Setup

The SOPHO 2000 IPS offers analog lines for connecting Voicemail systems. The analog lines support DTMF integration (off-hook protocol), but the functionality is limited to post dialing and offering the identity of the party, who set call forwarding only. For full integration, the SOPHO 2000 IPS offers serial integration, called the MCI (Message Center Interface) integration. The MCI link is a V24 link between the MM@Net system and an RS232 port of the SOPHO 2000 IPS. This RS232 port can be a port of the AP00-B card or a port on the MP card. Each voice port of the MM@Net system needs a connection to an analog port on the SOPHO 2000 IPS. When the MM@Net system uses 8 ports, 8 LCA circuits on the SOPHO 2000 IPS are needed and this is covered by one 8LCA card. To make sure voicemail users are attached to a free voice port as much as possible, a hunting group is created on the SOPHO 2000 IPS, which comprises a pilot (group) number with the analog ports as group members. A programming and setup example is described below: Extension numbers of the voicemail users: 300 ~ 399 (user extensions). Extension numbers of the analog ports for the voice ports: 200 ~ 203(vms extension). Pilot number of the group, containing the analog ports: 299 (vms - pilot extension).

PROCEDURE: Hunting group for the Voicemail ports

This section describes the steps to create a hunting group - terminal for the Voicemail ports. This procedure can also be found in the SOPHO 2000 IPS Feature Programming Manual chapter Station Hunting - Terminal. Actions 1. Create a (virtual) extension and force this extension into the BUSY state: 11 >000>299 Create the (virtual) extension. E50 >299>0 Force the extension in the BUSY state: hunting will start towards the physical extensions. 2. Assign the virtual extension and the Voicemail port extensions to a hunting group terminal and define the hunting sequence: 180 >299>200 Extension 299 will hunt to extension 200 (always, because of BUSY state). 180 >200>201 Extension 200 will hunt to extension 201, when 200 is busy. 180 >201>202 Extension 201 will hunt to extension 202, when 201 is busy. 180 >202>203 Extension 202 will hunt to extension 203, when 202 is busy. 180 >203>200 Extension 203 will hunt to extension 200, when 203 is busy. The loop is closed.

12

3. Define the Pilot (Group) number of the hunting group - terminal and the ordinary members: 181 >299>1 Extension 299 is the Pilot number. 181 >200>0 Extensions 200 ~ 203 are members.
181 >201>0 181 >202>0 181 >203>0

Note: A single hunting group can have a maximum of 60 members, including the Pilot extension. There is no limit regarding the amount of terminal hunting groups.

PROCEDURE: Voicemail System with MCI integration

This section describes the steps to setup SOPHO 2000 IPS to work with Voicemail systems using MCI integration. This procedure can also be found in the SOPHO 2000 IPS Feature Programming Manual chapter Message Center Interface. Actions 1. Specify MCI integration is used with the Voicemail system: 08 >443>0 VMS type defined by command 1225. 08 >444>0 MW lamp control from VMS with MCI to all stations enabled. 1225>200>3 All Voicemail ports are set as "Voicemail with MCI"
1225>201>3 1225>202>3 1225>203>3

2. Define Voicemail Service and Off-hook protocol for all voicemail ports: 1310>200>0 Set Voicemail Service to the voicemail ports.
1310>201>0 1310>202>0 1310>203>0 1322>200>0 1322>201>0 1322>202>0 1322>203>0

Assign Off-hook protocol to the voicemail ports.

3. Assign settings related to MWI (Message Waiting Indication): 08 >444>0 Enable MW control by the VMS with MCI. 08 >376>0 Enable MW set on display when forwarded over CCIS link. 1303>3xx>0 Enable MW set / cancel for all user extensions. (3xx : 300 ~ 399) 08 >025>1 Mailbox users will see MSG x on their display when a voicemail message has been received. "X" indicates the number of voicemail messages.

13

PROCEDURE: Define an MP port as MCI port

This section describes the steps to setup the second RS232 port of the MP card as MCI port. This procedure can also be found in the SOPHO 2000 IPS Feature Programming Manual chapter Message Center Interface. Actions 1. Select the second port of the MP card to be used as MCI port: 08 >708>0 Extension numbers in the MCI messages are limited to 6 digits. 0401> 01>1 Connection port for MCI is port number 1 of the MP card. (Port 0 for MAT) 2. Define the communication parameters of the MCI port: 4000> 1>10 The port is used for MCI ONLY . 4001> 1>1 Data length: 8 bit. 4002> 1>1 Parity check: off. 4003> 1>1 Parity type: odd. 4004> 1>0 Stop bits: 1. 4005> 1>1 DTR signal: high. 4006> 1>1 RTS signal: high. 4008> 1>4 Data speed: 9600 baud. 3. Enable ANI information sent to the Voicemail System, when provided by the Network: 08>709>0 MCI message sent with ANI info for MP port used for MCI. 35138>rtn>0 Enable ANI sending of the incoming route (rtn = 00 ~ 63). 4. Save changes and reset the PABX: EC6 > 0>0 Wait for this command to finish and press the reset button on the MP card. The MCI Port can be configured on the MP board (two available com ports). There is also a AP00 board which gives 4 extra COM ports. There are two type of AP00 boards: AP00-B and AP00-D (MRCA program). Select the matching procedure to configure a MCI port on the AP00 board

PROCEDURE: Define an AP00-D port as MCI port

Note: This procedure is ONLY used, when no MP port is used for MCI integration. This section describes the steps to setup the first RS232 port of the AP00-D card as MCI port. This procedure and the way how to initialize the AP00-D card can also be found in the SOPHO 2000 IPS Feature Programming Manual chapter Message Center Interface .

14

Actions 1. Select a port of the AP00-D card to be used as MCI port: (in this example port 0 is used) 0401> 01>2 Connection port for MCI is a port of the AP00-D with MRCE program. DD01>100>10 Selects first port on the AP00-D for MCI 2. Define the communication parameters of the MCI port: DD10> 001>5 Data speed: 9600 baud. DD10> 002>0 Stop bits: 1. DD10> 003>1 Data length: 8 bit. DD10> 004>0 Parity check: off. DD10> 005>48 Station address: 0. DD10> 006>33 Unit address: ! DD10> 007>0 Enables message sending after a reset of the AP00 board DD10> 008>0 Extension numbers in the MCI messages are limited to 6 digits. DD10> 017>5 Guard timer between texts: 512- 640ms. 3. Enable ANI information sent to the Voicemail System, when provided by the Network: DD10 > 009>1 MCI message sent with ANI info for AP00-B port used for MCI. 35138>rtn>0 Enable ANI sending of the incoming route (rtn = 00 ~ 63). 4. Reset the AP00-D card, see for the procedure the SOPHO 2000 IPS Feature Programming Manual chapter Message Center Interface.

PROCEDURE: Define an AP00-B port as MCI port

Note: This procedure is ONLY used, when no MP port is used for MCI integration. This section describes the steps to setup the first RS232 port of the AP00-B card as MCI port. This procedure and the way how to initialize the AP00-B card can also be found in the SOPHO 2000 IPS Feature Programming Manual chapter Message Center Interface . Actions 1. Select a port of the AP00-B card to be used as MCI port: (in this example port 0 is used) 0401> 01>7 Connection port for MCI is a port of the AP00-B card. D000>136>0 Enable MW control text sending from AP00 to VMS. D000>137>0 Extension numbers in the MCI messages are limited to 6 digits. 2. Define the communication parameters of the MCI port: D001> 20>5 Data speed: 9600 baud. D001> 21>0 Stop bits: 1. D001> 22>1 Data length: 8 bit. D001> 23>0 Parity check: off. D001> 80>24 The port is used for MCI. D001> 81>0 Data processing priority: 1st priority.

15

Station address: 0. Unit address: ! End Of Block detection timing: 512 ms. Guard timer between texts: 1 - 128 ms. 3. Enable ANI information sent to the Voicemail System, when provided by the Network: D001 > 36>1 MCI message sent with ANI info for AP00-B port used for MCI. 35138>rtn>0 Enable ANI sending of the incoming route (rtn = 00 ~ 63). 4. Reset the AP00-B card, see for the procedure the SOPHO 2000 IPS Feature Programming Manual chapter Message Center Interface .
D001> D001> D001> D001> 85>48 86>33 89>5 98>0

PROCEDURE: Enable Live recording feature of the Voicemail system

This section describes how to setup live recording support on the PABX. This procedure can also be found in the SOPHO 2000 IPS Feature Programming Manual, chapter Executive override. Actions 1. Assumed is that all normal extension users are allowed to use the executive override feature. (Also known as break-in or barge-in) 200 > *4>A006 Default Break-in feature access code: *4 (System C-load). 456 > CFT>1 CFT (00 - 15): MP conference circuits; must be in service. 9000>3xx,01>F0006 Program key 1 on users' Dterm for Executive override. 2. To test the function using a telephone: - Setup a call between 2 extensions. - Use a third extension to call one of the busy extensions of the former step. - On receiving busy tone, press the Executive override key for the Dterms. Press hook-flash and then the break-in code on an analog telephone. - Now a three party conference exists and ticker tone is heard. Note: Live recording configuration needs to be set in the Voicemail application. See the application documentation and/or help how to do this.

PROCEDURE: Provide Call redirection to Voicemail w/o answering

This section describes how to identify and redirect callers to the Voicemail system without answering the call. The caller will be handled the same as Call Forward on No Answer. This procedure can also be found in the SOPHO 2000 IPS Feature Programming Manual, chapter Call Redirect.

16

Actions 1. Program the redirect destination (VMS) and a feature key on the users' extension for this feature: 5118> 01>299 Call redirection (system wide) to the VMS pilot number. 9000>3xx,02>F5012 CRD key for transferring inc. calls w/o answering. 2. Executing procedure for the users: - A call (internal or external) comes in and the my-line key lights up during alerting. - User presses the CRD key to identify the caller. - When the user wants to redirect this call to the Voicemail system without answering, the incoming line key (my-line key) must be pressed WITHIN 6 seconds after the CRD key is pressed. The caller will be rerouted to the Voicemail system just as with CF-NA. - The user can also answer the call in a normal way by going off-hook. Note: For Call forward - busy / no answer / all calls: See the SOPHO 2000 IPS documentation.

3.1.

Centralized Voice mail

When additional SOPHO 2000 IPS PABX systems make use of a MyMail@Net application as their voice mail system, some additional programming is required to provide calling and called party numbers. Note: The SOPHO 2000 IPS PABX systems must be linked together using CCIS networking protocol to use Centralized voice mail. For all PABX systems, that have a CCIS link to the PABX, which holds the MyMail@Net application, the following programming is required:
08> 08> 443>1 444>1

VMS with DTMF. MW lamp control from VMS with MCI to all stations disabled.

For all PABX systems, including the one which holds the MyMail@Net application, the following additional programming is required:
08> 08> 063>0 253>0

Call transfer from a station before called party answers enabled. Ring transfer for CF- All to a trunk when a station holds another station

enabled.
08> 333>0 Mail box nr sent to VMS when VMS is recalled after transferring the call to an unanswered station enabled.

17

08>

373>0

Send CF station information over CCIS link enabled.

08> 376>0 When a forwarded call is terminated to VMS via CCIS, whether MW from VMS is provided for the called station set to enabled.

3.2.

SOPHO 2000 IPS - MyMail@Net integration

This chapter describes the configuration of the MyMail@Net application for a correct integration with the SOPHO 2000 IPS. The integration is described in two sections: The MyMail@Net 510 settings are described in chapter 3.2.1. "MyMail@Net 510 Integration". The MyMail@Net 510 settings are described in chapter 3.2.2. "MyMail@Net 560 Integration". Only the most important settings are described in this manual. For more information regarding integration, refer to the MyMail@Net Integration guide.

3.2.1.
-

MyMail@Net 510 Integration

Connecting the systems: The physical connections between the PABX and the MyMail@Net are described in the MyMail@Net 510 Integration Guide. Select the correct switch: Select "Switch" from the System menu. For a 2000 IPS with MCI interface, select "PHILIPS - SOPHO 2000 IPS w MCI" Configure the access numbers: Select "Configuration" from the System menu. Select "Access Numbers" Enter in the field "Pilot #" the pilot number of the IVR group. Enter the extensions of the Hunting-group terminal in the field "Station numbers" Make sure that the sequence is correct, start with the extension that is connected to the first Dialogic line followed by the extension connected to the second Dialogic line etc. Port Configuration: Select "Ports" from the System menu Select "Answer/Dial out" for all ports that are used. If a lot of dial out actions are required, you may consider to select "Dial out only" for the last couple of ports. As indication, a iS3000 requires more dial out actions than a 2000 IPS with MCI integration.

18

MWI configuration: Select "Switch" from the System menu. Select MWI. Check that in the fields "On (activation) code" and "Off (deactivation) code" the string "@X" is entered Live Record: Select "Switch" from the System menu. Select "Live Record" Check in the PABX which prefix is used for "Executive Overide" Enter "X,%," followed by the "Executive Overide" prefix in the field "Barge-in code" Hookflash Time Definition: Select "Switch" from the menu System. Select "Dialout" Check that the Hookflash Time Definition for the "percent (%)" is set to 10 Centiseconds. (100 ms) Select "Switch" from the menu System. Select "Dialing codes" Change the "&" in the fields "initiate sequence" , "recall sequence" and "busy recall sequence" to an "%"

3.2.2.
-

MyMail@Net 560 Integration

Connecting the systems: The physical connections between the PABX and the MyMail@Net are described in the MyMail@Net 560 Integration Guide. Select the correct switch: During the software installation you can select the correct switch. It is also possible to select the switch after installation. Open the Switch Selector utility from, Start/Programs/Repartee for Windows 2000/ Server Utilities. Select NEC from the "Manufacturer" pull down menu And select the correct switch from the "Model" pull down menu. Select "AD64" from the pull down menu. Configure the access numbers: Select "Switch" from the Console Root. Double click "Switch Settings". Select the "General" tab. Enter in the field "Pilot number" the pilot number of the IVR group. Select "Supported Ports" from the "Ports" menu. Select the "General" tab. Double click each port and enter the correct extensions of the Hunting-group terminal in the field "Station number" Make sure that the sequence is correct, start with the extension that is connected to the first Dialogic line followed by the extension connected to the second Dialogic line etc.

19

Port Configuration: Select "Supported Ports" from the "Ports" menu. Select the "General" tab. Select "Answer/Dial out" for all ports that are used. If a lot of dial out actions are required, you may consider to select "Dial out only" for the last couple of ports. As indication, a iS3000 requires more dial out actions than a 2000 IPS with MCI integration. MWI configuration: Select "Switch" from the Console Root. Double click "Switch Settings". Select the "MWI" tab. Check that in the fields "On (activation) code" and "Off (deactivation) code" the string "@X" is entered. Live Record: Select "Switch" from the Console Root. Double click "Switch Settings". Select the "Live Record" tab Check in the PABX which prefix is used for "Executive Overide" Enter "X,%," followed by the "Executive Overide" prefix in the field "Barge-in code" Hookflash Time Definition: Select "Switch" from the Console Root. Double click "Switch Settings". Select the "Dialout" tab. Check that the Hookflash Time Definition for the "percent (&)" is set to 100 milliseconds.

More detailed information can be found in the MyMail@Net 560 Integration Guide and the on-line Help function in the HTML console.

20