DPNSS NETWORKING MITEL 3300

AND

AVAYA INDEX SYSTEMS

The following document is based upon Mitel’s testing of interworking between 3300 ICP’s and Avaya Index with the
addition of an actual working configuration, programmed and tested by Chris McAndrew

Basically there are three rules;

1/. Put voice mail on the Mitel

2/. Put Node ID’s on everything

3/. Route calls via the Node ID’s (ARS and Digit Mod or Speed Dials)

Note

It should be noted that if the Node ID’s on an Index is not programmed then a simple call from the 3300 ICP to the
Index will appear as an external call to the Index, also some DPNSS features are lost on the Index.
When dialling off switch from the 3300 ICP to the Index it is strongly recommended that the index node ID is part of
the dialling string.
INTERWORKING TESTING MITEL NETWORKS 3300 ICP V. AVAYA INDEX

The results of the DPNSS interoperability testing carried out at Mitel, Wales, Technical Support laboratory have shown that
the following functionality has been tested and confirms inter working between the Mitel 3300 ICP and the Avaya Index at
the stated level: -

The Index was tested with the following configurations and software levels.

CPU X Level 9.2.2

CPU V Level 9.2.2
CPU X Level 10.0.4
3300 ICP R 4.1.6.4

Supplementary Services (BTNR 188)

BTNR Service Index 3300 ICP

Section
6 Simple Call Control Supported Supported
7 Circuit Switch data Call Supported Supported
8 Swap Not Supported Not Supported
9 Call back when free Supported Supported
10 Executive Intrusion Supported Supported
11 Diversion Supported Supported
12 Hold Supported Supported
13 Three party Supported Supported
14 call offer Supported Supported
15 Non-specified Information Supported Supported
16 Service Independent String Supported Supported Note 1
17 Call waiting Supported Supported
18 Bearer Service selection Not Supported Supported Note 2
19 route optimisation Not Supported Supported
20 Extension status Supported Supported Note 3
21 Controlled Diversion Not supported Supported
22 Redirection Not Supported Supported Note 3
23 Series call Not supported Supported Note 3
24 Three Party take-over Supported Supported Note 4
25 night Service Supported Supported Note 5
26 Centralised Operator Supported Supported
27 Traffic Channel Maintenance Not Supported Not Supported
28 Remote alarm reporting Supported Supported Note 5
29 Add-on conference Supported Supported
30 Time sync Not Supported Supported Note 6
31 Call back when next used Supported Supported
32 do not disturb Supported Supported Note 7
33 Remote REG of diversion Not Supported Supported Note 8
34 Remote REG of do not disturb Not supported Supported Note 8
35 Priority breakdown Not supported Not Supported
36 call back messaging Supported Supported
37 loop avoidance Supported Supported
38 Force Release Not Supported Not Supported
39 Text Message Not supported Not Supported
40 Charge reporting Supported Supported Note 9
41 Network address ext. Supported Not Supported Note 10
42 Call Park Supported Supported Note 5
43 Call distribution Not supported Not Supported
 44 R.O Capacity Control Not Supported Not Supported
45 Wait On Busy Not Supported Not Supported
46 Call Pick Up Not Supported Not Supported
47 Travelling Class Of Service Not Supported Not Supported Note 5
48 Number Presentation Restriction Not Supported Not Supported

Note1: The BTNR section has numerous subsections of which both the Mitel 3300 ICP and Avaya Index support “Text”
i.e. the ability to send names.

Note 2: This feature is not available from the Mitel 3300 ICP, but can be induced via BRI or PRI (Euro) and passed
transparently

Note 3 This only supported on the 3300 ICP from an Operators console.

Note 4 The Index supports this feature. However, it was noted that when the 3300 ICP attempted to put the conf on Hold
to take control of the conference the Index sent a Rejection hence this feature does not work between a Mitel and
Index.

Note 5 The feature is not supported as per BTNR but both switches has a method to achieve the goal

Note 6 The time sync is supported by the 3300 ICP, currently the only time it is used is for Time and Date from the Mitel
BRI NSU.

Note 7 The Index on version 9.2.2 generates a No call which is returned to the 3300 ICP as a Number Unobtainable.
The Index on version 10.0.4 generates a no call which is returned to the 3300 ICP as a Incoming call Barred
The Mitel generates Busy message + a message to specify DND. The Index simply looks at the Busy
message and plays a Busy tone

Note 8 The feature is not supported as per BTNR – Mitel ICP has the ability to support between switches.

Note 9 The Index will pass AOC over DPNSS

Note 10 The feature is supported by the index using Index Net - This is only available via CPU X.

N.B

All the testing was performed with the Index and 3300 ICP having Node Id’s set. Problem encountered without node ID’s
set on the Index are: -

All calls will appear as though they are from an external source and not display the name. In addition, as many features of
the Index DPNSS are linked to node ID’s without them many features that are specified above as supported from the Index
perceptive will fail and example of such is call backs.
CONFIGURATIONS

Single Index connected to Single 3300 ICP

There were no issues raised in this configuration irrespective of where the Voicemail resides.

The Index requires a Node ID, otherwise some DPNSS Features are lost. As the Index requires the Node ID the only way to
dial off switch between the 3300 ICP and the Index is to either request that user on the 3300 ICP dial Node ID + index
extension, or to add the Node ID with the Digit Mod via ARS. If the latter is chosen then problems will arise on a divert.

If the voicemail resides on the 3300 ICP, then a 4-digit mailbox, which equates to the Index extension, is programmed and
you match a 6-digit Extension against this.

Mailbox Number: 4000 Index Extension Number

Name: Smith,Fred
Extension Number: 204000 Index Node ID + extension number
Passcode: *******
Mailbox Type: Extension
Prompt Language: System Default
Operator Extension (0): 0
Type: Extension
Number:
User Access: Disabled

The extension 4000 is the true Index number, but you need to add the node ID as this is what is passed into voicemail from
the Index.
The 3300 ICP mailboxes will be a 4-digit Mailbox and a 4-digit Extension. Both 4 and 6 digit extensions can reside on the
Voicemail at the same time.

To ensure the passing of CLI you must have the Class Of service of the Extensions and Trunks on the 3300 ICP setup as per
the following table

DASS/Euro IP SC1000 IP
DPNSS Trunks Consoles Sets

ANI/DNIS/ISDN Number Delivery Trunk No No No No

DASS II OLI/TLI Provided Yes No No Yes
Display ANI/ISDN Calling Number Only No Yes No Yes
Display ANI/DNIS/ISDN Calling/Called number No Yes Yes Yes
Single Index connected to two 3300 ICP’s.

All the features of the previous section will work in this configuration. The one feature that has issues is when the voicemail
resides on the Index.
When the 3300 is the voicemail, there are no issues.

When Index is the voicemail, if the call was from extension 2001 to extension 3000 and this was divert on no answer then
we have a 40B*5555# 59*813000, the issue is with the *59 which the originating called party number.

It appears as though the Index does not like the *59 Message.

Ext 4000 Ext 4001

Index

DPNSS

3300
3300
Op console
2000

Ext 2001 Ext 2002

Ext 3000 Ext 3001
I
Index connected to two 3300 ICP via DPNSS

The issues here are the same as above

Ext 4000 Ext 4001

Index

DPNSS DPNSS

3300 3300
Op console
2000

Ext 2001 Ext 2002

Ext 3000 Ext 3001
Multiple Index’s connected to Multiple 3300 ICP’s

Any Index feature that is available when two Index’s are connected via DPNSS these features are still available when the
3300 ICP’s are in between. This is also true if the connection between the 3300 ICP is IP trunk.

If the 3300 ICP is acting as the V/M this works fine.

Both switches having voicemail boxes on the 3300 ICP worked perfectly well and the message waiting lamps of each
switch could be lit and extinguished by the voicemail.

The call to Auto Attendant works well. The external caller simply dials a 4-digit extension for the Index user this is mapped
to the 4-digit mailbox and as such will dial the cross-referenced 6-digit extension.

When the Index was acting as the Voicemail the following resulted:

Simple call from 3300 ICP to an Extension on the Index, which diverts to voicemail and the Voicemail and extension reside
on the same switch, this works Ok. The message waiting lamps on the 3300 ICP extension will be lit.

The 3300 ICP extension can retrieve the voicemail but it is not able to press the message Key on the 3300 ICP extension
and press call back. The reason this fails is the Index is using Voice Fast access and as such the Index is expecting a Index
specific DPNSS string that is a *58 (NSI) hence the Mitel can not generate this and as such the Key strokes fail.

Hence, the only way to access the Index voicemail is via the dialled access code and then following the prompts.

The message-waiting lamp will be extinguished by the voicemail when the message has been completed.

If the call is from a 3300 ICP to an Index extension whose voicemail resides on the other Index switch then you will have
issues on a Divert on Busy and Divert Immediate scenario as outlined below.

If you make a call from ext 2002 and dial 4501. if 4501 rings then a message will be sent back to the 3300 ICP updating it
with the correct number for 4501 i.e. it’s node ID + extension number , in this situation if the call is diverted to the other
Index V/M the call lands in the correct voicemail box and will work. If on the other hand you have dialled 4501 and the
Extension does not ring i.e. a Divert Immediate or a Divert on Busy then the message that is passed to the V/M index simply
contains the dialled digits 4501 which is incorrect and hence the call fails.

The only way to get over this is too dial the node ID + extension number. This is as per the NOTE on the Introduction.

Ext 4000 Ext 4001 Ext 4500

Ext 4501
Index Index

DPNSS DPNSS

V/M on 3300
3300
Op console
2000

Ext 2001 Ext 2002

IP Ext 3000 Ext 3001
Note

Also, note that the voicemail issue raised in above will exist in the multiple networks.

The Index extension number can be no longer than 6 digits therefore if you have a scenario of 4-digit Index number + 3 or
More digit node ID this will prevent the 3300 ICP acting as the voicemail.

If the ARS has a route for the extension numbers then the Digit Mod must add the Node ID, however for the Auto attendant
you must also have routes for the node ID’s + extension numbers
Diagram of the following example
DPNSS
Dip Switches

1 2 3 4 5 6

75Ohm Up UP Up Up Down Up for NT / Down for LT

Message Link Dip Switch Up for Primary – Down for Secondary

1/. Program the NSU on the controller

2/. Configure the DPNSS Links
3/. Associate the link descriptor to the required NSU port(s)
4/. Configure the trunk descriptor
5/. Specify COS and COR and REMEMBER to set incoming digit mod to 0
6/. Turn on the trunks
7/. Synchronise the circuit
8/. Place the correct number of trunks into a trunk group
9/. Configure Digit Mod
10/. Build a route to send the calls down

COR group 6 has no calls barred

Digits before out pulsing = 2 digit Node ID + 3 digit extension number

11/. Configure ARS

7 routes between Mitel’s

8 routes between Index’s

9 dials out
Nodes
Configure the Node ID’s as required

71 is the local machine

72 is the remote 3300

81 is the Index on the local machine

82 is the Index on the remote 3300

Voice Mail
Configure the voice mail ports – see the notes above – remember to add the NODE ID

4 digit mailbox number associated to a 2 digit node ID + 3 digit extension – with the exception of the extensions on the
local machine.
Routing Calls Between Systems
In this instance, we have routed calls by digit translation via system speed dials. In the following example dialling ‘201’ is
being translated to ‘81201’ or extension 201 node 81.
Index
Call Routing