VoiceMail Server CE Manual

8/13/2019 VoiceMail Server CE Manual

1/25i

Tableofcontents

AMENDMENTS 1

PREFACE 2

1. INTRODUCTION 3

1.1. GENERAL OVERVIEW 3

1.1.1. Layout of the Voice Server Interface (VSI) 3

1.1.2. Communication between a Voice Server and an ISPBX 4

1.1.3. Standard Connection 4

1.1.4. Integrated Connection 4

2. SERVERS 5

2.1. VOICE-MAIL SERVER (VMS) 5

2.1.1. VMS Units 5

2.1.2. Handshaking Protocols 5

3. HARDWARE INSTALLATION 6

3.1. CIRCUIT BOARDS 6

3.2. CABLES 6

4. SOFTWARE INSTALLATION (ON-HOOK PROTOCOL) 7

4.1. INTEGRATED CONNECTION 7

4.1.1. System Software 200/205/300/640 7

4.1.2. System Software 730/735/740/741/800/805/Call@Net 9

5. SOFTWARE INSTALLATION (OFF-HOOK PROTOCOL) 11

5.1. INTEGRATED CONNECTION 11

5.1.1. System Software 205/300 11

5.1.2. System Software 730/735/740/741/800/805/Call@Net 13

A . ON-HOOK PROTOCOL 15

A.1. CALLS FROM AN ISPBX TO A SERVER 15

A.1.1. Format of Calls 15

A.1.2. Timing of Calls 16A.1.3. Server Recovery from User Dialling Errors 16

A.1.4. Call Type Identification 17

B . OFF-HOOK PROTOCOL 18

B.1. CALLS FROM AN ISPBX TO A SERVER 18

B.1.1. Format of Calls 18

B.1.2. Timing of Calls 19

C . TONES AND SIGNAL LEVELS 20


2/25ii

Table

ofcontents

C.1. THE SERVER 20

C.2. THE ISPBX 20

D . EXTRA INFORMATION 21

D.1. CALLS FROM A SERVER TO AN ISPBX 21

D.1.1. Timing of Calls 22

D.1.2. Call Collision 22

D.2. MESSAGE WAITING TYPES 23


3/251

AMENDMENTS

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

CHAPTER/SECTION DESCRIPTION

All chapters Call@Net introduced.


4/252

PREFACE

This book describes the hardware and software installation required to create an interface that

can be used by various voice server products connected to a SOPHO ISPBX. Examples of

voice servers are:

VMS = Voice-mail server.

The VSI (Voice-server Interface) uses two different protocols (on-hook protocol or off-hook

protocol) and can be implemented in SOPHO ISPBX systems with the following System

Software (SSW):

PROTOCOL

ON-HOOK OFF-HOOK

200 ---

205 205.7

300 300.23

640 ---

SSW 730 730.30

735 735.25

740 740.23

741 741.21

800 800.23

805 and up 805 and up


5/253

1. INTRODUCTION

Voice servers are items of equipment that can be connected to an ISPBX to carry out various

voice functions. Examples of voice servers are:

- VMS (Voice-Mail Server).

A piece of equipment used for the purpose of storing and retrieving voice messages sent

to it by the ISPBX. The messages are stored in "mail boxes" and can be retrieved by the

ISPBX when requested.

- VoiceManager 5xx Series

Starting with a small in-switch Voice Mail solution (VM 505) up to the large VM 560 with

a lot a extra features, like hospitality, fax messages storage, networking of Voice Mail

systems, TeLANophy, remote maintenance, etc.

This book describes:

- the hardware needed to connect a Voice Server;

- the projecting required in the ISPBX;

- the signalling protocol used on the Voice Server Interface (VSI) between a server and the

ISPBX.

1.1. GENERAL OVERVIEW

1.1.1. Layout of the Voice Server Interface (VSI)

Voice Servers are connected to an Analogue Line Circuit (ALC) via two wires (a/b wires) as

shown in figure 1.1.

Figure 1-1 Connection of a Voice Server to an ISPBX


6/254

1.1.2. Communication between a Voice Server and an ISPBX

There are two types of connection between a voice server and an ISPBX, they are the

Standard Connection and Integrated Connection. Both types of connection use DTMF digitsand other tones such as dial-tone and ring-tone.

1.1.3. Standard Connection

With a Standard Connection, the ISPBX treats the server as an ordinary analogue telephone

set; it does not send information that describes the kind of call being sent to the server. The

server has the same facilities assigned to it by the ISPBX as those that can be assigned to an

ordinary analogue telephone set.

1.1.4. Integrated Connection

With an integrated Connection, the ISPBX sends "calling extension number" and "called

extension number" to the server. This can be used to identify the type of call being sent, for

example an internal, external or diverted call.


7/255

2. SERVERS

An example of a voice server is the VMS (Voice-mail server); it is described below.

2.1. VOICE-MAIL SERVER (VMS)

There are various manufacturers of Voice-Mail Server (VMS) equipment and there are two

different handshaking protocols for communicating with ISPBXs.

2.1.1. VMS Units

VMS units used with ISPBXs are made by various manufacturers.

Note: The VMS units used must conform to the protocols offered by the ISPBXs; see

appendices A and B.

2.1.2. Handshaking Protocols

The protocols used are:

- oN-hookVoice-Mail protocol: NVM;

- oFf-hookVoice-Mail protocol: FVM.

Note: The ISPBX with the various System Soft Ware (SSW) will use one protocol or the

other depending on projecting and licensing, it will not support both protocols at

the same time; see table 2.1.

Table 2-1 VMS Makers and Protocols Used

SYSTEM SOFTWARE (SSW)PROTOCOLSUPPORTED

VSI LICENCEREQUIRED * DONGLE NEEDEDISPBXs TBX

SSW 200/205/300/615/

620/630/640/730/740/741/800/805/Call@Net

SSW 615/620/630 NVM NO NO

SSW 205/300 - FVM YES NO

SSW 730/740/741/800/805/Call@Net

- FVM YES YES

* If the ISPBX user has purchased a licence for the VMS facility, it is programmed into the dongle installed in the ISPBX.

In a network of exchanges, a dongle containing an off-hook VSI licence is needed only in the ISPBXs where the off-hookprotocol is used, therefore, not in ISPBXs where the VSI off-hook protocol is not used.


8/256

3. HARDWARE INSTALLATION

3.1. CIRCUIT BOARDS

The Voice-mail server can connected to one or more (depending on the number of lines

between the server and the ISPBX) ordinary ALC circuits.

- Insert an ALC board in a shelf of the ISPBX (or use one that is already installed but not all

circuits are allocated yet);

- Connect the a/b wires of front connectors to the MDF;

- Connect the Voice server to a/b wires in the MDF.

3.2. CABLES

Servers from different manufacturers may have different connectors for the a/b wires that

need to be connected to the MDF. Consult the server handbook to see what cable is

necessary.


9/257

4. SOFTWARE INSTALLATION (ON-HOOK PROTOCOL)

4.1. INTEGRATED CONNECTION

The things that must be projected are:

- System Boundaries and System Options;

- System Timers;

- System Ring Rhythms;

- Number Analysis;

- Group Arrangements;

- Facility Class Marks;

- Message Waiting;- Traffic Class;

- Signalling type for the ALC.

4.1.1. System Software 200/205/300/640

System Boundaries and System Options

System Timers

SSW PE COMMANDS FUNCTION

PROJPA:2039,0; OFF-HOOK Voice-mailprotocol

: OFF

200/205/300 (Selects ON-HOOK Voice-mail protocol)

PROJPA:2032,1; Digit regeneration during aconnection

: YES

PROJPA:1042,1; Service Displays required : YES

640 PROJPA:2027,0; External control of servicedisplays

: NO

PROJPA:2032,1; Digit regeneration during aconnection

: YES


PROJPA:2308,C40; Tone Time Limit = 40 seconds

200/205/640 PROJPA:2341,C40; Tone Timeout on DDI calls = 40 seconds

PROJPA:2300,C20; Dialling Timeout on DialTone

= 20 seconds


10/258

System Ring Rhythms (TMS)

Number Analysis

The numbers chosen as prefixes are examples only.

Group Arrangements

Group arrangements are optional and depend on how the server is used.

Facility Class Marks

Facility class mark 47 'Preferent to operator' must be assigned; this is useful when server

transfers incoming calls to operator.

PROJPA:2394,C05; SSM Ringing time "A" = 5 seconds of soft ring

PROJPA:2308,0,40; Tone Time Limit = 40 seconds

300 PROJPA:2341,0,40; DDI Tone Time Limit = 40 seconds

PROJPA:2300,0,20; Dial Tone Time Limit = 20 seconds

PROJPA:2394,0,05; SSM Ringing time "A" = 5 seconds of soft ring


200/205 PROJPA:2437,,58; SSM Ringing rhythm "A" = 60 ms ON

300/640 800 ms OFF


PROJPA:6095, 00, *590,, 085; Set message waiting prefix

PROJPA:6095, 00, #590,, 086; Cancel message waiting prefix

200/205 PROJPA:6095, 00, *591,, 085; Set message waiting prefix

300/640 PROJPA:6095, 00, #591,, 086; Cancel message waiting prefix

PROJPA:6095, 00, *592,, 085; Set message waiting prefixPROJPA:6095, 00, #592,, 086; Cancel message waiting prefix

SSW OM COMMANDS FUNCTION

200/205 CRGRPA:2000, group DNR,,,; Create group arrangement

300/640



11/259

Message Waiting

Traffic Class

The traffic class of the server DNRs must be set to maximum: usually traffic class 6.

4.1.2. System Software 730/735/740/741/800/805/Call@Net

The ISPBX must be projected as follows:


ASFACM: 29&47&51&57&72, serverDNRs;

Assigns facilities to server DNRs

or 29 = Data protected


47 = Preferent to operator

205/300 51 = Test call entitled

57 = Service display extension

72 = Post dialling allowed

94 = Voice-mail server (preferred fornew installations)


Assigns facilities to server DNRs

29 = Data protected

200/640 47 = Preferent to operator 51 = Test call entitled

57 = Service display extension



200/205 CHMWRE:0, *590, #590; Set/cancel message-waiting

type:

0

300/640 CHMWRE:1, *591; #591; 1

CHMWRE:2, *592, #591; 2

PG2 PARAMETERS FUNCTION VALUE SELECTED

BOUND018 = 50 Message-waiting softring time 50x100ms

LOSYSOP019 = NO Voice-mail protocol selection On-hook protocol

LOSYSOP027 = YES Message-waiting queuing softring yes

LOSYSOP047 = YES Postdialling available yes

NETIMER000 = 20 Internal dial tone time 20 seconds


12/2510

Group Arrangements

Group arrangements are optional and depend on how the server is used: use group properties

type number 16.



transfer incoming calls to operator.

Traffic Class


Signalling Type for ALC

The ALC circuit(s) to which the server is connected must be projected with signalling type

3208 'Enquiry by hook-flash'.

NETIMER006 = 40 Tone limit time 40 seconds

NETIMER041 = 40 DDI tone time 40 seconds

OM COMMANDS FUNCTIONS

ASINTN:0, *590, 0, 76; Message-waiting LED on/off type: 0 = ON

ASINTN:0, #590, 0, 79; 0 = OFF

ASINTN:0, *591, 0, 77; 1 = ON

ASINTN:0, #591, 0, 80; 1 = OFF

ASINTN:0, *592, 0, 78; 2 = ON

ASINTN:0, #592, 0, 81; 2 = OFF

OM COMMANDS FUNCTION

ASFACM:4&11&32&33, server DNR/BSP-IDs Assigns facilities to server DNRs

4 = Data protection


32 = Keytone postdialling allowed

33 = Voice-mail server



13/2511

5. SOFTWARE INSTALLATION (OFF-HOOKPROTOCOL)

5.1. INTEGRATED CONNECTION

The things that must be projected are:

- System Boundaries and System Options;

- System Timers;

- System Ring Rhythms (TMS);

- Number Analysis;

- Group Arrangements;

- Facility Class Marks;- Message Waiting;

- Traffic Class;

- Signalling type for the ALC.

5.1.1. System Software 205/300

System Boundaries and System Options

System Timers


205/300 PROJPA:2039, 1; OFF-HOOK Voice-mailprotocol

: ON

PROJPA:2032, 1; Post-dialling available : YES


PROJPA:2308, C40; Tone Time Limit = 40 seconds

205 PROJPA:2341, C40; DDI Tone Time Limit = 40 seconds

PROJPA:2300, C20; Dial Tone Time Limit = 20 seconds

PROJPA:2394, C05; TMS Ringing time "A" = 5 seconds of soft ring

PROJPA:2308, 0, 40; Tone Time Limit = 40 seconds

300 PROJPA:2341, 0, 40; DDI Tone Time Limit = 40 seconds

PROJPA:2300, 0, 20; Dial Tone Time Limit = 20 seconds

PROJPA:2394, 0, 05; TMS Ringing time "A" = 5 seconds of soft ring


14/2512

System Ring Rhythms (TMS)

Number Analysis

The numbers chosen as prefixes are examples only.

Group Arrangements

Group arrangements are optional and depend on how the server is used.



tranfers incoming calls to operator.

PE COMMANDS FUNCTIONPROJPA:2437,, 58; TMS Ringing rhythm "A" = 60 ms ON

800 ms OFF

PE COMMANDS FUNCTION








CRGRPA:2000, group DNR,,,; Create group arrangement


ASFACM:29&47&51&72,server DNRs; Assigns facilities to server DNRs

29 = Data protected


51 = Test call entitled


94 = Voice-mail server (preferred for new installations)


15/2513

Message Waiting

Traffic Class


Note: When the server is dialled via inter-ISPBX links (for example, DPNSS, CLC, tie-

lines, it might be useful to set the route option to "keytone regeneration" (PE5057). If this were done then it would allow users, with extension sets such as

SOPHO-SET P171, K365, to postdial to the server.

5.1.2. System Software 730/735/740/741/800/805/Call@Net

The ISPBX must be projected as follows (the prefixes shown are examples only):

Boundaries, Options and Timers

Number Analysis

OM COMMANDS FUNCTIONCHMWRE:0, *590, #590; Set/cancel message-waiting type: 0

CHMWRE:1, *591, #591; 1

CHMWRE:2, *592, #592; 2


LOSYSOP019 = YES Voice-mail protocol selection Off-hook protocol

LOSYSOP027 = YES Message-waiting queuing softring yes

LOSYSOP047 = YES Postdialling available yes

NETIMER000 = 20 Internal dial tone time 20 seconds

NETIMER006 = 40 Tone limit time 40 seconds

NETIMER041 = 40 DDI tone time 40 seconds

NETIMER165 = 30(only for SSW 730)

POM DTAP inform guard time 30 seconds


ASINTN:0, *590, 0, 76; Message-waiting LED on/off type: 0 = ON

ASINTN:0, #590, 0, 79; 0 = OFF

ASINTN:0, *591, 0, 77; 1 = ON


16/2514

Group Arrangements

Group arrangements are optional and depend on how the server is used: use group properties

type number 16.



transfers incoming calls to operator.

Traffic Class


Signalling Type for ALC

The ALC circuit(s) to which the server is connected must be projected with signalling type

3208 'Enquiry by hook-flash.'

ASINTN:0, #591, 0, 80; 1 = OFF

ASINTN:0, *592, 0, 78; 2 = ON

ASINTN:0, #592, 0, 81; 2 = OFF


ASFACM:4&11&32&33,server DNR/BSP-IDs Assigns facilities to server DNRs

4 = Data protection


32 = Keytone postdialling allowed

33 = Voice-mail server



17/2515

A . ON-HOOK PROTOCOL

Communication between an ISPBX and a server uses CCITT Q.23 DTMF signalling. This

appendix tells you:

- the format of the information the ISPBX sends to a server;

- the errors that might occur in the information sent to a server;

- how a server is expected to react when errors occur;

- how a server is expected to identify the type of a call that it receives.

A.1. CALLS FROM AN ISPBX TO A SERVER

A.1.1. Format of Calls

Figure A.1. shows the information sent from the ISPBX to the server when the ISPBX is setting

up a call. In the figure you see, as an example, a string of digits and letters (D 123456 A 654321

C DC), followed by ringing current (see note 5).

Figure A-1 ISPBX to Server Call Setup Sequence

Note: The digits shown are only an example of what a calling DNR might be.

- With internal calls this field contains up to 6 decimal digits (0...9),

representing the DNR of the calling party or operator. Look also at sectionA.1.3. "Server Recovery from User Dialling Errors".

- With external calls this field contains 4 stars (****).

Note: ISPBXs with SSW 200/205/300 and TBX will send the identifier digit and called

number only on diversion, or when the called number was a hunt group number. If

the server extension number was dialled directly, the identifier and called number

will be suppressed.

The digits shown are only an example of what a called DNR might be.


18/2516

- With non-diverted calls, this field contains up to 6 decimal digits (0 ... 9),

representing the DNR of the server. Look also at section A.1.3. "Server

Recovery from User Dialling Errors".

- With diverted calls, this field contains up to 6 decimal digits (0 ... 9),

representing the DNR of the diversion initiator.

Note: At the end of a voice-mail call, when the caller and called party both go on-hook,

the ISPBX and TBX send a clear display sequence ("DC") to the server ("DC" is sent

to the server by SSW 200/205/300/640, "DC" is not sent by SSW 730/735/740/

741/800/805 and up).

Ringing current is sent to the server after the setup data has been sent.

A.1.2. Timing of Calls

The ISPBX sends the calling number and the called number to the server in a DTMF string,

followed by ringing current; see figure A.1. After the data (calling number and called number)

is received, the server expects to receive ringing current within a specified time (specified in

the server).

If ringing does not start within this specified time the data received is discarded.

A.1.3. Server Recovery from User Dialling Errors

The "Calling Number" and "Called Number" fields in figure A.1. can have a maximum of 6characters in them: look at the notes 1 and 3 above. Nevertheless, a user might dial the wrong

number of digits, or a digit that is not allowed; this section tells you what the server equipment

is expected to do in such cases.

Table A-1 User Dialling Errors and Server Action

USER DIALLING ERROR SERVER ACTION

CALLING NUMBER CALLED NUMBER

More than six digits sent to server Correct (no error) Calling number discarded

Called number retained

Correct (no error) More than six digits sent to server Called number discarded

Called number discarded

Correct (no error) Contains * or # Caller prompted to supply

mailbox number

Contains * or # (**** is allowed) Correct (no error) Calling number discarded

Number contains error Number contains error System reverts to "standardconnection" for that call, rather than"integrated connection".


19/2517

A.1.4. Call Type Identification

Table A.2. shows the types of call that a server might receive from an ISPBX. The server

should recognise these.

Table A-2 Server Type of Call Identification

TYPE OF CALL CALLING NUMBER IS ****

CALLED NUMBER IS SERVERDNR OR SERVER HUNT GROUP

DNR

Direct internal call NO YES

Diverted internal call NO NO

Direct external call YES YES

Diverted external call YES NO


20/2518

B . OFF-HOOK PROTOCOL

Communication between an ISPBX and a Server uses CCITT Q.23 DTMF signalling. This

appendix tells you the format and timing of the information the ISPBX sends to a server.

B.1. CALLS FROM AN ISPBX TO A SERVER

B.1.1. Format of Calls

Figure B.1. shows the information sent from the ISPBX to the server when the ISPBX is setting

up a call. In the figure you see, as an example, a string of digits and letters (X Y 123456 A

654321 C). The caller hears ringing tone while the ISPBX is sending digits, as shown in figure

B.1.

Figure B-1 ISPBX to Server Call Setup Sequence

Note: 1. X = 0: no diversion

1: diversion on busy

2: diversion on no reply

3: other diversion cause (e.g. follow me)

4: diversion on not reachable (empty S0 bus or handset out of reach/switched off)

2. Y = 0: external party, identified by route number (analogue trunk)

1: internal party or party connected to a local network via DPNSS or CLC2: external party, identified by calling line identity (ISDN)

3. The digits shown are only an example of what a calling DNR might be. Look at

table B.1. to see what the digits mean.

4. ISPBXs with SSW 205/300 will send the identifier digit and called number only

on diversion, or when the called number was a hunt group number. If the server

extension number was dialled directly, the identifier and called number will be

suppressed.


21/2519

As from SSW 300.32: when facility class mark 50 is assigned SS to the voice mail

server, the Called Line Identity (preceeded by A) is included in the digit string that

is sent to the voice mail server after answering the call.

5.

- Diverted calls: up to 20 digits (0 ... 9, *, #) DNR of the diversion initiator.

- Non-diverted calls: up to 20 digits (0 ... 9, *, #) DNR of the server.

Note: 6. When the server has received the stop digit it must wait 1 second before sending

an announcement; this time is needed for path switching in the ISPBX.

Table B-1 Meaning of Digits in Calling DNR

B.1.2. Timing of Calls

ISPBXs send the calling number and the called number to the server in a DTMF string; while

this is happening, the user hears ringing tone (see figure B.1.). After the data (calling number

and called number) is sent, the ISPBX connects the caller to the server.

CALLING PARTYTYPE see note 2

MAX. NBR OFDIGITS AND

SPACES TYPE OF DIGITSNUMBER

REPRESENTS REMARKS

Y = 0 20 0 ... 9, * Route number of trunkline. Line number of

trunk line.

Format = ROUTE *LINE (Two numbersseparated by *)

Y = 1 20 0 ... 9, *, # DNR of the callingextension or operator.

Y = 2 20 0 ... 9, *, # Unrestricted calling lineidentity of the callingparty.

If the calling line identityis restricted (SSW 205/300 or SSW 740 andhigher) the route and linenumber are displayedinstead of the calling lineidentity.


22/2520

C . TONES AND SIGNAL LEVELS

The signal levels of the the server and the ISPBX both have to be programmed correctly in

order for the two to interface properly; this means the following should be programmed:

- Audio levels;

- DTMF signalling levels.

Look at table on page 20to see what these levels should be: they are the same for both the

on-hook protocol and the off-hook protocol.

Table C-1 Audio and DTMF Signal Levels

Note: The Audio and DTMF signal levels are specified across an a/b wire pair with an

input impedance of 600 ohms.

C.1. THE SERVER

The Programming of tones and signal levels in the server should already have been done bythe manufacturer of the server; these settings have been chosen to suit the telephone system

requirements of the country in which the server is used; If you need to change the settings

look in the server manufacturer's handbook to see how to do this.

C.2. THE ISPBX

Transmit and receive signal levels of an ALC are country dependent. These signal levels and

DTMF tones are defined in the ALC card being used.

SIGNAL DIRECTION

AUDIO (SPEECH)

SIGNALS

DTMF SIGNALLING LEVELS

LOW GROUP HIGH GROUP

Transmit : Server to ISPBX - 6 to - 12 V - 11 to - 2 dbm - 9 to - 2 dbm

Receive : ISPBX to Server 0 to - 50 V - 5 to - 35 dbm - 5 to - 35 dbm


23/2521

D . EXTRA INFORMATION

D.1. CALLS FROM A SERVER TO AN ISPBX

A server often supports several kinds of messages, such as:

- Standard messages;

- Priority messages;

- Fax messages.

These can be classed as different message waiting types, for example:

- text message 1;- text message 2;

- text message 3.

In an ISPBX, each of these can have a message-waiting activation and deactivation prefix.

When a message is received in a mailbox of the server, the server may initiate a call to the

ISPBX telling it there is a message waiting. The server will tell the ISPBX to turn on the

message waiting indicator (usually an LED or soft ring) on a particular telephone extension and

will indicate what type of message is waiting (with simple sets, only one message type can be

indicated, because the set may have only one lamp or soft ring). The following examples show

how a standard message-waiting indication would be turned on or off.

Turn the standard message waiting indication ON

- Connect to a line;

- Detect dial tone;

- Send the message waiting activation prefix: you defined this (*590) in the number

analysis section of chapters 4 and 5)

- send the DNR of the telephone set;

- Wait for confirmation tone;

- Disconnect.

Turn the standard message waiting indication OFF

- Connect to a line;

- Detect dial tone;

- Send the message waiting deactivation prefix: you defined this (#590) in the number

analysis section of chapters 4 and 5)

- Send the DNR of the telephone set;

- Wait for confirmation tone;

- Disconnect.


24/2522

Note: The DNR is the extension number of the user whose message waiting indicator is

to be changed.

DNRs in other DPNSS nodes are allowed (only in SSW 805)

The DNR may contain up to:

6 digits (0 ... 9) (On-hook protocol)

12 digits (0 ... 9, *, #) (Off-hook protocol)

D.1.1. Timing of Calls

When the server connects to a line it expects to receive dial tone within a certain period of

time; if no dial tone is detected within this period the server disconnects.

On receiving dial tone, the server will send a string of DTMF digits to the ISPBX and wait for

confirmation tone, if no confirmation tone is received within a certain time then the server will

disconnect. The tone and timeout value of the confirmation tone are projectable within theISPBX and must also be projectable within the server.

If the call from the server to the ISPBX fails it might be because dial tone or confirmation tone

are not detected, or the timeouts are exceeded. In this situation the server will make another

two attempts to establish a connection. If these two also fail, the server will make no further

attempts. The maximum number of call setup attempts will therefore be three. Look at figure

D.1. for an indication of the call setup protocol.

Figure D-1 Server to ISPBX Call Setup Sequence (Server Actions)

D.1.2. Call Collision

If the server seizes a line in order to make a call to the ISPBX but receives a keytone digit

instead of dial tone, then it is obvious that an incoming call is colliding with the outgoing call;call collision is occurring.

When call collision occurs, the server should withdraw its outgoing call to the ISPBX and give

precedence to the incoming call from the ISPBX.

It is recommended that the server should wait a few seconds after the last call is finished

(incoming or outgoing), before it sets up any new call to the ISPBX. This should avoid collisions

with new incoming calls, from the ISPBX to the server, that had been waiting as "camped on

busy" calls.


25/25

D.2. MESSAGE WAITING TYPES

The three message waiting types mentioned in section D.1. can be indicated only on feature

telephone sets. On simple sets only one message waiting type can be indicated because thesimple set has only one lamp or soft ring.

This means that, on a simple set, only one message waiting type should be used because

switching other message waiting types off on simple sets will result in switching off all message

waiting types.

If all three message waiting types are to be used, the server must know the types of sets in an

installation and which of the telephone sets are simple sets.

VoiceMail Server CE Manual

Documents

Transcript of VoiceMail Server CE Manual