MIVOICE OFFICE 400

MITEL 415/430
AS OF VERSION R4.1
SYSTEM MANUAL

syd-0580_en / 1.2 – R4.1 – © 08.2016

NOTICE
The information contained in this document is believed to be accurate in all respects
but is not warranted by Mitel Networks Corporation.
The information is subject to change without notice and should not be construed in
any way as a commitment by Mitel or any of its affiliates or subsidiaries. Mitel and its
affiliates and subsidiaries assume no responsibility for any errors or omissions in this
document. Revisions of this document or new editions of it may be issued to incor-
porate such changes.
No part of this document can be reproduced or transmitted in any form or by any
means - electronic or mechanical - for any purpose without written permission from
Mitel Networks Corporation.

TRADEMARKS
The trademarks, service marks, logos and graphics (collectively “Trademarks”)
appearing on Mitel's Internet sites or in its publications are registered and unregistered
trademarks of Mitel Networks Corporation (MNC) or its subsidiaries (collectively
"Mitel") or others. Use of the Trademarks is prohibited without the express consent
from Mitel. Please contact our legal department for additional information:
[email protected].
For a list of the worldwide Mitel Networks Corporation registered trademarks, please
refer to the website: http://www.mitel.com/trademarks.

PATENT NOTE ON POWER OVER ETHERNET

Mitel’s Power Over Ethernet (PoE) Powered Device (PD) products are covered by one
or more of the U.S. patents (and any foreign patent counterparts thereto) identified at
Mitel’s website: www.mitel.com/patents.
For more information on the PD patents that are licensed, please refer to .
www.cmspatents.com.

Mitel 415/430 as of R4.1

syd-0580/1.2 – 08.2016
®, ™ Trademark of Mitel Networks Corporation
© Copyright 2016 Mitel Networks Corporation
All rights reserved

2
Content

1 Product and Safety Information . . . . . . . . . . . . . . . . 9

1. 1 About Mitel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1. 2 Product information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1. 3 Safety Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1. 4 Data protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1. 5 About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1. 6 Limited Warranty (Australia only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2 System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2. 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2. 2 Communication server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2. 2. 1 Installation versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2. 2. 2 Positioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2. 3 Networking Possibilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2. 4 Mitel system phones and clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2. 5 Various phones, terminals and equipment . . . . . . . . . . . . . . . . . . . . . 27
2. 6 Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2. 7 Applications and application interfaces . . . . . . . . . . . . . . . . . . . . . . . . 28
2. 7. 1 Mitel Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2. 7. 2 Application interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2. 7. 2. 1 Mitel Open Interfaces Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2. 7. 2. 2 Message and alarm systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
2. 7. 2. 3 CTI - Computer Telephony Integration . . . . . . . . . . . . . . . . . . . . . . . . 35
2. 7. 2. 4 ISDN interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2. 7. 2. 5 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2. 7. 2. 6 System monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2. 7. 2. 7 Call logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2. 7. 2. 8 Hospitality/Hotel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2. 7. 2. 9 Voice over IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2. 8 First steps... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2. 9 Connection options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3 Expansion Stages and System Capacity. . . . . . . . . 39
3. 1 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3. 2 Basic system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3. 2. 1 Interfaces, display and control elements . . . . . . . . . . . . . . . . . . . . . . . 40
3. 2. 2 Power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3. 2. 3 Media resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3. 3 Expansion with cards and modules . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3. 3. 1 System modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3. 3. 1. 1 DSP modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

3 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
3. 3. 2 Interface cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
3. 3. 2. 1 Trunk cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3. 3. 2. 2 Terminal cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
3. 3. 2. 3 Options card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
3. 3. 3 Wiring Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3. 4 System capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
3. 4. 1 Media resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
3. 4. 2 General system capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
3. 4. 3 Terminals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
3. 4. 4 Terminal and network interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
3. 4. 5 Software assurance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
3. 4. 6 Licences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
3. 4. 6. 1 Description of available licences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
3. 4. 7 Restricted operating mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
3. 4. 8 Temporary offline licences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
3. 4. 9 Trial licences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
3. 4. 10 Power supply capacity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
3. 4. 10. 1 Supply power available for terminals. . . . . . . . . . . . . . . . . . . . . . . . . . 79
3. 4. 10. 2 Power supply per terminal interface . . . . . . . . . . . . . . . . . . . . . . . . . . 80
4 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
4. 1 System components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
4. 2 Fitting the communication server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
4. 2. 1 Equipment supplied . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
4. 2. 2 Mounting options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
4. 2. 2. 1 Cable cover set for Mitel 415/430 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
4. 2. 2. 2 Mitel 415 rack-mounting set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
4. 2. 2. 3 Mitel 430 rack-mounting set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
4. 2. 3 Location requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
4. 2. 4 Safety regulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
4. 2. 5 Wall mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
4. 2. 5. 1 Minimum distances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
4. 2. 5. 2 Drilling plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
4. 2. 5. 3 Drilling template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
4. 2. 5. 4 Wall-mounting procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
4. 2. 6 Desktop installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
4. 2. 7 Rack-mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
4. 2. 7. 1 Rack-mounting procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
4. 2. 7. 2 Installing the fan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4. 2. 7. 3 Installing the cable cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
4. 3 Earthing and protecting the communication server . . . . . . . . . . . . . . . 92
4. 3. 1 Connecting the earthing wire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
4. 3. 2 Connecting the cable screening . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
4. 4 Powering the communication server . . . . . . . . . . . . . . . . . . . . . . . . . . 95
4. 4. 1 115/230 V power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

4 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
4. 4. 2 Uninterruptible power supply (UPS) . . . . . . . . . . . . . . . . . . . . . . . . . . 96
4. 5 Equipping the Basic System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
4. 5. 1 Interface card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
4. 5. 2 Wiring Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
4. 5. 3 DSP module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
4. 5. 4 Component mounting rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
4. 6 Connecting the communication server . . . . . . . . . . . . . . . . . . . . . . . 101
4. 6. 1 Direct connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
4. 6. 2 Indirect connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
4. 6. 2. 1 Connection via main distribution board . . . . . . . . . . . . . . . . . . . . . . . 102
4. 6. 2. 2 Connection to a universal building cable installation (UBC) . . . . . . . 104
4. 7 Cabling interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
4. 7. 1 Port addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
4. 7. 2 Network interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
4. 7. 2. 1 Basic rate interface BRI-T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
4. 7. 2. 2 Primary rate interface PRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
4. 7. 2. 3 FXO network interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
4. 7. 3 Terminal interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
4. 7. 3. 1 DSI terminal interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
4. 7. 3. 2 BRI-S terminal interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
4. 7. 3. 3 FXS terminal interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
4. 7. 4 Emergency fan-out-panel (EFOP) . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
4. 7. 5 Equipment on the ODAB options card. . . . . . . . . . . . . . . . . . . . . . . . 138
4. 7. 5. 1 Connection of a door intercom (TFE) . . . . . . . . . . . . . . . . . . . . . . . . 138
4. 7. 5. 2 Control outputs and control inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . 141
4. 7. 6 Audio interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
4. 7. 7 Ethernet interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
4. 8 Installing, powering, connecting and registering terminals . . . . . . . . 147
4. 8. 1 IP system phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
4. 8. 2 Mitel 6700 SIP / 6800 SIP series SIP phones . . . . . . . . . . . . . . . . . . 148
4. 8. 3 Standard SIP phones and standard SIP terminals . . . . . . . . . . . . . . 149
4. 8. 4 Mobile/external phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
4. 8. 5 OIP and other applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
4. 8. 6 Digital system phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
4. 8. 6. 1 General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
4. 8. 6. 2 MiVoice 5361 / 5370 / 5380. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
4. 8. 6. 3 Office 25, Office 35, and Office 45/45pro . . . . . . . . . . . . . . . . . . . . . 153
4. 8. 6. 4 Office 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
4. 8. 7 DECT radio units and cordless phones . . . . . . . . . . . . . . . . . . . . . . . 156
4. 8. 7. 1 Installing the radio units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
4. 8. 8 Analogue phones Mitel 6710 Analogue, Mitel 6730 Analogue . . . . . 159
5 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162
5. 1 WebAdmin Configuration Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
5. 1. 1 Integrated and auxiliary applications . . . . . . . . . . . . . . . . . . . . . . . . . 164

Mitel 415/430 as of R4.1 5

syd-0580/1.2 – R4.1 – 08.2016
5. 2 Access types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
5. 3 User access control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
5. 3. 1 User accounts and authorization profiles . . . . . . . . . . . . . . . . . . . . . 169
5. 3. 1. 1 User accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
5. 3. 1. 2 Authorization profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
5. 3. 2 Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
5. 3. 2. 1 Password syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
5. 3. 2. 2 Change password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
5. 3. 2. 3 Access with incorrect password . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
5. 3. 2. 4 Lost password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
5. 3. 3 Password-free access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
5. 3. 4 Automatic exit from the configuration . . . . . . . . . . . . . . . . . . . . . . . . 172
5. 3. 5 Access log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
5. 4 Remote access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
5. 4. 1 Access enabled by local users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
5. 4. 2 Function code for remote maintenance access. . . . . . . . . . . . . . . . . 173
5. 4. 3 Function keys for remote maintenance access . . . . . . . . . . . . . . . . . 174
5. 5 Configuring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
5. 6 Configuration Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
5. 6. 1 Licences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
5. 6. 2 File management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
5. 6. 3 System reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
5. 6. 4 Data backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
5. 6. 4. 1 Auto backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
5. 6. 4. 2 Distribution service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
5. 6. 4. 3 Manual backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
5. 6. 4. 4 Restore backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
5. 6. 5 Importing and exporting configuration data . . . . . . . . . . . . . . . . . . . . 180
5. 6. 6 Mitel 6700 SIP / 6800 SIP phones . . . . . . . . . . . . . . . . . . . . . . . . . . 181
6 Operation and Maintenance . . . . . . . . . . . . . . . . . 182
6. 1 Data Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
6. 1. 1 What data is stored where. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
6. 1. 1. 1 System software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
6. 1. 1. 2 File system of the communications server . . . . . . . . . . . . . . . . . . . . 183
6. 1. 1. 3 Boot software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
6. 1. 1. 4 System-specific data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
6. 1. 2 Updating configuration data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
6. 2 Update Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
6. 2. 1 System software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
6. 2. 2 Firmware for corded system phones . . . . . . . . . . . . . . . . . . . . . . . . . 186
6. 2. 3 Firmware System MiVoice Office 400 DECT. . . . . . . . . . . . . . . . . . . 187
6. 2. 4 Firmware System Mitel SIP-DECT . . . . . . . . . . . . . . . . . . . . . . . . . . 188
6. 3 Hardware update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
6. 3. 1 Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

6 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
6. 3. 2 Licenses and EIM card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
6. 3. 2. 1 Licences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
6. 3. 2. 2 EIM card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
6. 3. 3 Interface cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
6. 3. 3. 1 Replacing a defective interface card . . . . . . . . . . . . . . . . . . . . . . . . . 191
6. 3. 3. 2 New card with fewer ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
6. 3. 3. 3 New card with more ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
6. 3. 3. 4 Change slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
6. 3. 4 System modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
6. 3. 4. 1 Changing the DSP module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
6. 3. 5 System cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
6. 3. 5. 1 Replacing the EIM card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
6. 3. 6 Mainboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
6. 3. 7 Replacing system terminals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
6. 3. 7. 1 DSI system phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
6. 3. 7. 2 DECT terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
6. 4 Display and control panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
6. 4. 1 LED display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
6. 4. 2 Pilot key (CTRL key) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
6. 4. 3 Operating modes and display priorities . . . . . . . . . . . . . . . . . . . . . . . 202
6. 4. 3. 1 Startup Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
6. 4. 3. 2 Normal Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
6. 4. 3. 3 Feature Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
6. 4. 3. 4 Application Command Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
6. 4. 3. 5 Boot Command Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
6. 4. 3. 6 Wiring Adapter Malfunction Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
6. 4. 3. 7 Warning Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
6. 4. 3. 8 Boot Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
6. 4. 3. 9 Shutdown Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
6. 4. 3. 10 Error Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
6. 4. 4 Carrying out functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
6. 4. 4. 1 Shutting down the communication server . . . . . . . . . . . . . . . . . . . . . 209
6. 4. 4. 2 Normal restart with database backup . . . . . . . . . . . . . . . . . . . . . . . . 209
6. 4. 4. 3 Forced restart without database backup . . . . . . . . . . . . . . . . . . . . . . 210
6. 4. 4. 4 Enabling / disabling password-free access . . . . . . . . . . . . . . . . . . . . 210
6. 4. 4. 5 Enabling / disabling the dial-up connection to the AIN . . . . . . . . . . . 210
6. 4. 4. 6 Carrying out a first start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
6. 4. 4. 7 Resetting the IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
6. 4. 4. 8 Thorough RAM test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
6. 4. 4. 9 Emergency Upload via LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
6. 5 Operations supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
6. 5. 1 Event message concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
6. 5. 1. 1 Event types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
6. 5. 1. 2 Event tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
6. 5. 1. 3 Signal destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Mitel 415/430 as of R4.1 7

syd-0580/1.2 – R4.1 – 08.2016
6. 5. 2 Operating state and error displays . . . . . . . . . . . . . . . . . . . . . . . . . . 236
6. 5. 2. 1 System operating state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
6. 5. 2. 2 System error displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
6. 5. 2. 3 Terminals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
6. 5. 2. 4 Operating state of the Mitel DECT radio units . . . . . . . . . . . . . . . . . . 237
6. 5. 2. 5 Malfunction of the Mitel DECT radio unit . . . . . . . . . . . . . . . . . . . . . . 239
6. 5. 2. 6 Malfunctions of Mitel DECT cordless phones . . . . . . . . . . . . . . . . . . 239
6. 5. 2. 7 Malfunctions of the DECT charging bays . . . . . . . . . . . . . . . . . . . . . 240
6. 5. 2. 8 Longclicks on Mitel DECT cordless phones . . . . . . . . . . . . . . . . . . . 241
6. 5. 2. 9 Overload code displays Office 135 / Office 160 . . . . . . . . . . . . . . . . 242
6. 5. 3 Other aids . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
6. 5. 3. 1 System logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
6. 5. 3. 2 File system state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
6. 5. 3. 3 File browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
6. 5. 3. 4 Measuring equipment for cordless systems . . . . . . . . . . . . . . . . . . . 243
7 Annex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
7. 1 Systematic designation system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
7. 2 Rating Plate and Designation Stickers . . . . . . . . . . . . . . . . . . . . . . . 245
7. 3 Equipment Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
7. 4 Technical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
7. 4. 1 Network interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
7. 4. 2 Terminal interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
7. 4. 3 Communication server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
7. 4. 4 Design of interface cards, modules and wiring adapters. . . . . . . . . . 249
7. 4. 5 LAN switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
7. 4. 6 Digital and IP system phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
7. 4. 7 Mitel DECT radio units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
7. 5 Operation of digital system phones . . . . . . . . . . . . . . . . . . . . . . . . . . 255
7. 5. 1 Digit key assignment of system phones . . . . . . . . . . . . . . . . . . . . . . 255
7. 5. 2 Alpha keyboardMiVoice 5380 / 5380 IP . . . . . . . . . . . . . . . . . . . . . . 256
7. 5. 3 Function commands (macros) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
7. 6 Functions and terminals no longer supported . . . . . . . . . . . . . . . . . . 258
7. 7 Licensing information of third-party software products . . . . . . . . . . . 259
7. 8 Documents and online help systems with further information . . . . . . 261

8 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Product and Safety Information

1 Product and Safety Information

Here you will find information relating to safety, data protection and legal matters
besides product and documentation information.
Please read through the product and safety information carefully.

1. 1 About Mitel
Mitel (Nasdaq:MITL) (TSX:MNW) is a global leader in business communications that
easily connect employees, partners and customers - anywhere, anytime and over any
device, for the smallest business to the largest enterprise. Mitel offers customers maxi-
mum choice with one of the industry’s broadest portfolios and the best path to the
cloud. With more than US$1 billion in combined annual revenue, 60 million customers
worldwide, and #1 market share in Western Europe, Mitel is a clear market leader in
business communications. For more information, go to www.mitel.com.

1. 2 Product information
Purpose and function
MiVoice Office 400 is an open, modular and comprehensive communication solution
for the business sector with several communication servers of different performance
and expansion capacity, an extensive telephone portfolio and a multitude of expan-
sions.
The expansion possibilities for the Mitel 415/430 communication server include an
FMC Controller for integrating mobile/external phones, an open interface for applica-
tion developers and a multitude of expansion cards and modules.
The business communication solution with all its elements was designed to cover the
full spectrum of communication requirements of businesses and organizations in a
user and maintenance-friendly way. The individual products and parts are co-ordinated
and cannot be used for other purposes or replaced by outside products or parts (ex-
cept to connect up other authorized networks, applications and phones to the inter-
faces certified for that purpose).

User groups
The phones, soft phones and PC applications of the MiVoice Office 400 communica-
tion solution are particularly user friendly in design and can be used by all end users
without any specific product training.
The phones and PC applications for professional applications, such as the PC operator
consoles or call centre applications, do require training of the personnel.

Mitel 415/430 as of R4.1 9

syd-0580/1.2 – R4.1 – 08.2016
Product and Safety Information

Specialist knowledge of IT and telephony is assumed for the planning, installation, con-
figuration, commissioning and maintenance. Regular attendance at product training
courses is strongly recommended.

User information
MiVoice Office 400 products are supplied with safety and product information, quick
user guides and user guides.
These and all other user documents such as system manuals are available for down-
load from the MiVoice Office 400 DocFinder as individual documents or as a documen-
tation set. Some user documents are accessible only via a partner login.
It is your responsibility as a specialist retailer to keep up to date with the scope of func-
tions, the proper use and the operation of the MiVoice Office 400 communication solu-
tion and to inform and instruct your customers about all the user-related aspects of the
installed system:

• Please make sure you have all the user documents required to install, configure and
commission an MiVoice Office 400 communication system and to operate it effi-
ciently and correctly.
• Make sure that the versions of the user documents comply with the software level of
the MiVoice Office 400 products used and that you have the latest editions.
• Always read the user documents first before you install, configure and put an
MiVoice Office 400 communication system into operation.
• Ensure that all end users have access to the User Guides.

Download the MiVoice Office 400 documents from the internet: www.mitel.com/DocFinder
© The information, graphics and layouts featured in the user information are subject to copyright and may not be
duplicated, presented or processed without the written consent of Mitel Schweiz AG.

Conformity
Mitel Schweiz AG hereby declares, that the MiVoice Office 400 products

• comply with the basic requirements and other stipulations of Directives EMC
(2014/30/EU) and LVD (2014/35/EU).
• are manufactured in conformity with RoHS according to Directive 2011/65/EU.

You can find the product specific declarations of conformities under www.mi-
tel.com/regulatory-declarations.

10 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Product and Safety Information

Use of third party software

MiVoice Office 400 products comprise, or are partially based on, third-party software
products. The licence information for these third-party products is listed in the user's
guide of the MiVoice Office 400 product in question.

Exclusion of Liability
(Not valid for Australia. See the chapter "Limited Warranty (Australia only)", page 15.)
All parts and components of the MiVoice Office 400 communication solution are manu-
factured in accordance with ISO 9001 quality guidelines. The relevant user information
has been compiled with the utmost care. The functions of the MiVoice Office 400 prod-
ucts have been tested and approved after comprehensive conformity tests. Nonethe-
less errors cannot be entirely excluded. The manufacturers shall not be liable for any
direct or indirect damage that may be caused by incorrect handling, improper use, or
any other faulty behaviour. Potential areas of particular risk are signalled in the appro-
priate sections of the user information. Liability for loss of profit shall be excluded in
any case.

Environment
MiVoice Office 400 products are delivered in recycled, chlorine-free corrugated card-
board packaging. The parts are also wrapped inside a protective fleece made of poly-
ethylene foam fleece or polyethylene film for added protection during shipping. The
packaging is to be disposed of in accordance with the guidelines stipulated under cur-
rent legislation.
MiVoice Office 400 products contain plastics based on a pure ABS, sheet
steel with an aluminium-zinc or zinc finish, and epoxy resin-based PCBs.
These materials are to be disposed of in accordance with the guidelines stip-
ulated under current legislation.
MiVoice Office 400 products are disassembled exclusively using detachable screwed
connections.

Mitel 415/430 as of R4.1 11

syd-0580/1.2 – R4.1 – 08.2016
Product and Safety Information

1. 3 Safety Information
Reference to hazards
Hazard warnings are affixed whenever there is a risk that improper handling may put
people at risk or cause damage to the MiVoice Office 400 product. Please take note of
these warnings and follow them at all times. Please also take note in particular of haz-
ard warnings contained in the user information.

Operating safety
MiVoice Office 400 communication servers are operated on 115 or 230 VAC mains
power. Communication servers and all their components (e.g. telephones) will not op-
erate when mains power fails. Interruptions in the power supply will cause the entire
system to restart. A UPS system has to be connected up-circuit to ensure an uninter-
ruptible power supply. Up to a specific performance limit a Mitel 470 communication
server can also be powered redundantly using an auxiliary power supply. For more in-
formation please refer to your communication server's system manual.
When the communication server is started for the first time, all the configuration data is
reset. You are advised to backup your configuration data on a regular basis as well as
before and after any changes.

Installation and operating instructions

Before you begin with the installation of the MiVoice Office 400 communication server:

• Check that the delivery is complete and undamaged. Notify your supplier immedi-
ately of any defects; do not install or put into operation any components that may be
faulty.
• Check that you have all the relevant user documents at your disposal.
• During the installation follow the installation instructions for your MiVoice Office 400
product and observe to the letter the safety warnings they contain.

Any servicing, expansion or repair work is to be carried out only by technical personnel
with the appropriate qualifications.

12 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Product and Safety Information

1. 4 Data protection
Protection of user data
During operation the communication system records and stores user data (e.g. call
data, contacts, voice messages, etc.). Protect this data from unauthorised access by
using restrictive access control:

• For remote management use SRM (Secure IP Remote Management) or set up the
IP network in such a way that from the outside only authorised persons have access
to the IP addresses of the MiVoice Office 400 products.
• Restrict the number of user accounts to the minimum necessary and assign to the
user accounts only those authorisation profiles that are actually required.
• Instruct system assistants to open the remote maintenance access to the communi-
cation server only for the amount of time needed for access.
• Instruct users with access rights to change their passwords on a regular basis and
keep them under lock and key.

Protection against listening in and recording

The MiVoice Office 400 communication solution comprises features which allow calls
to be monitored or recorded without the call parties noticing. Inform your customers
that these features may only be used in compliance with national data protection provi-
sions.
Unencrypted phone calls made on the IP network can be recorded and played back by
anyone with the right resources:

• Use encrypted voice transmission whenever possible.

• For WAN links used for transmitting calls from IP or SIP phones, use as a matter of
preference either the customer's own dedicated leased lines or VPN encrypted con-
nection paths.

Mitel 415/430 as of R4.1 13

syd-0580/1.2 – R4.1 – 08.2016
Product and Safety Information

1. 5 About this document

This document contains information on the expansion stages, system capacity, installa-
tion, configuration, running and maintenance as well as the technical data of the
MiVoice Office 400 communication servers. The system functions and features, the
DECT planning and the possibilities for networking several systems into a private net-
work (PISN) or an Mitel Advanced Intelligent Network (AIN) are not part of this Manual;
they are described in separate documents.
The document is intended for planners, installers and system managers of phone
equipment. Basic knowledge of phones, especially ISDN and IP technology, is required
to understand the content.
The system manual is available in Acrobat Reader format and can be printed out if
necessary. Navigation in PDF format is based on the bookmarks, table of contents,
cross references and index. All these navigation aids are linked, i.e. a mouse click
takes you directly to the corresponding places in the Manual. We have also ensured
that the page numbering in the PDF navigation corresponds to the page numbering of
the Manual, making it much easier to jump to a particular page.
Referenced menu entries and parameters appearing on terminal displays or on the
user interfaces of the configuration tools are highlighted in italics and in colour for a
clearer orientation.

Document information
• Document number: syd-0580
• Document version: 1.2
• Valid as of / based on: R4.1 / R4.1
• © 08.2016 Mitel Schweiz AG
• In PDF viewer, click on this link to download the latest version of this document:
https://pbxweb.aastra.com/doc_finder/DocFinder/syd-0580_en.pdf?get&DNR=syd-0580

Hazard alert messages

Special hazard alert messages with pictograms are used to signal areas of particular
risk to people or equipment.

Hazard:
Failure to observe information identified in this way can put people and hardware at risk through
electrical shock or short-circuits respectively.

Warning:
Failure to observe information identified in this way can cause a defect of the product or to a
module.

Note:
Failure to observe information identified in this way can lead to equipment faults or malfunctions
or affect the performance of the system.

14 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Product and Safety Information

General Considerations
Special symbols for additional information and document references.

Note
Failure to observe information identified in this way can lead to equipment faults or malfunctions
or affect the performance of the system.

Tip
Additional information on the handling or alternative operation of equipment.

See also
Reference to other chapters within the document or to other documents.

Mitel Advanced Intelligent Network

Particularities that have to be observed in an AIN.

References to the MiVoice Office 400 configuration tool WebAdmin

If an equals sign is entered in the WebAdmin search window , followed
by a two-digit navigation code, the view assigned to the code is directly displayed.
Example: Licence overview ( =q9) view
The corresponding navigation code is available on the help page of a view.

1. 6 Limited Warranty (Australia only)

The benefits under the Mitel Limited Warranty below are in addition to other rights
and remedies to which you may be entitled under a law in relation to the products.

In addition to all rights and remedies to which you may be entitled under the Competi-
tion and Consumer Act 2010 (Commonwealth) and any other relevant legislation, Mitel
warrants this product against defects and malfunctions in accordance with Mitel's au-
thorized, written functional specification relating to such products during a one (1) year
period from the date of original purchase ("Warranty Period"). If there is a defect or
malfunction, Mitel shall, at its option, and as the exclusive remedy under this limited
warranty, either repair or replace the product at no charge, if returned within the war-
ranty period.

Exclusions
Mitel does not warrant its products to be compatible with the equipment of any particu-
lar telephone company. This warranty does not extend to damage to products resulting
from improper installation or operation, alteration, accident, neglect, abuse, misuse,
fire or natural causes such as storms or floods, after the product is in your possession.
Mitel will not accept liability for any damages and/or long distance charges, which re-
sult from unauthorized and/or unlawful use.

Mitel 415/430 as of R4.1 15

syd-0580/1.2 – R4.1 – 08.2016
Product and Safety Information

To the extent permitted by law, Mitel shall not be liable for any incidental damages, in-
cluding, but not limited to, loss, damage or expense directly or indirectly arising from
your use of or inability to use this product, either separately or in combination with
other equipment. This paragraph, however, is not intended to have the effect of exclud-
ing, restricting or modifying the application of all or any of the provisions of Part 5-4 of
Schedule 2 to the Competition and Consumer Act 2010 (the ACL), the exercise of a
right conferred by such a provision or any liability of Mitel in relation to a failure to com-
ply with a guarantee that applies under Division 1 of Part 3-2 of the ACL to a supply of
goods or services.
This express warranty sets forth the entire liability and obligations of Mitel with respect
to breach of this express warranty and is in lieu of all other express or implied warran-
ties other than those conferred by a law whose application cannot be excluded, re-
stricted or modified. Our goods come with guarantees that cannot be excluded under
the Australian Consumer Law. You are entitled to a replacement or refund for a major
failure and for compensation for any other reasonably foreseeable loss or damage.
You are also entitled to have the goods repaired or replaced if the goods fail to be of
acceptable quality and the failure does not amount to a major failure.

Repair Notice
To the extent that the product contains user-generated data, you should be aware that
repair of the goods may result in loss of the data. Goods presented for repair may be
replaced by refurbished goods of the same type rather than being repaired. Refur-
bished parts may be used to repair the goods. If it is necessary to replace the product
under this limited warranty, it may be replaced with a refurbished product of the same
design and color.
If it should become necessary to repair or replace a defective or malfunctioning product
under this warranty, the provisions of this warranty shall apply to the repaired or re-
placed product until the expiration of ninety (90) days from the date of pick up, or the
date of shipment to you, of the repaired or replacement product, or until the end of the
original warranty period, whichever is later. Proof of the original purchase date is to be
provided with all products returned for warranty repairs.

Warranty Repair Services

Procedure: Should the product fail during the warranty period and you wish to make a
claim under this express warranty, please contact the Mitel authorized reseller who
sold you this product (details as per the invoice) and present proof of purchase. You
will be responsible for shipping charges, if any.
Limitation of liability for products not of a kind ordinarily acquired for personal, domestic
or household use or consumption (eg goods/services ordinarily supplied for business-
use).

16 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Product and Safety Information

Limitation of liability
1.1 To the extent permitted by law and subject to clause 1.2 below, the liability of Mitel to you for any non-compli-
ance with a statutory guarantee or loss or damage arising out of or in connection with the supply of goods or
services (whether for tort (including negligence), statute, custom, law or on any other basis) is limited to:
a) in the case of services:
i) the resupply of the services; or
ii) the payment of the cost of resupply; and
b) in the case of goods:
i) the replacement of the goods or the supply of equivalent goods; or
ii) the repair of the goods; or
iii) the payment of the cost of replacing the goods or of acquiring equivalent goods; or
iv) the payment of the cost of having the goods repaired.
1.2 Clause 1.1 is not intended to have the effect of excluding, restricting or modifying:
a) the application of all or any of the provisions of Part 5-4 of Schedule 2 to the Competition and Consumer
Act 2010 (the ACL); or
b) the exercise of a right conferred by such a provision; or
c) any liability of Mitel in relation to a failure to comply with a guarantee that applies under Division 1 of Part
3-2 of the ACL to a supply of goods or services.

After Warranty Service

Mitel offers ongoing repair and support for this product. If you are not otherwise entitled
to a remedy for a failure to comply with a guarantee that cannot be excluded under the
Australian Consumer Law, this service provides repair or replacement of your Mitel
product, at Mitel's option, for a fixed charge. You are responsible for all shipping
charges. For further information and shipping instructions contact:

Manufacturer: Note:
Mitel South Pacific Pty Ltd ("Mitel") Repairs to this product may be made only by the manufacturer and its
Level 1, 219 Castlereagh Street authorized agents, or by others who are legally authorized. Unauthor-
Sydney, NSW2000, Australia ized repair will void this express warranty.
Phone: +61 2 9023 9500

Mitel 415/430 as of R4.1 17

syd-0580/1.2 – R4.1 – 08.2016
System Overview

2 System Overview

This chapter provides a brief overview of the Mitel 415 and Mitel 430 communica-
tion servers with the installation versions, the positioning within the MiVoice
Office 400 series and the networking possibilities. It also features the system
phones, the applications and the application interfaces.

2. 1 Introduction
MiVoice Office 400 is a family of IP-based communications servers for professional
use in companies and organizations operating as small and medium-sized businesses
in all industries. The family consists of four systems with different expansion capacities.
The systems can be expanded using cards, modules and licences, and adapted to the
specific requirements of companies.
The family covers the growing demand for solutions in the area of unified communica-
tions, multimedia and enhanced mobile services. It is an open system that supports
global standards and is therefore easily integrated into any existing infrastructure.
With its wide range of networking capabilities the system is particularly well suited for
companies that operate in several locations. Coverage can even be extended to the
smallest branch offices at low cost.
MiVoice Office 400 communication systems handle “Voice over IP” technology with all
its benefits. What’s more, the systems operate just as easily with traditional digital or
analogue phones and public networks.
With the integrated Media Gateways any hybrid forms of an IP-based and digital or an-
alogue communication environment are also possible. This enables customers to
make the switch from traditional telephony to IP-based multimedia communication ei-
ther in just one step or, gradually, in several stages.

2. 2 Communication server
The Mitel 415 and Mitel 430 communication servers are at the lower end of the
MiVoice Office 400 family in terms of system capacity and expansion possibilities.
However all MiVoice Office 400 communication servers are equipped with the same
system software and offer the full scope of performance.
All the connections and control elements are accessible from the front. The display el-
ements are arranged so that they remain visible whatever the installation position.

18 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
System Overview

Fig. 1 Mitel 430

The communication server can be expanded using interface cards and system mod-
ules. The number of available slots and sockets depends on the type of communication
server.

2. 2. 1 Installation versions
Mitel 415 and Mitel 430 are suitable for both desktop installation, wall mounting and in-
stallation in a 19" rack. Covers for connecting cables and special installation covers for
rack installation are available separately.

Desktop installation
Wall mounting with
cable cover

Rack-mounted installation

Fig. 2 Installation versions

Mitel 415/430 as of R4.1 19

syd-0580/1.2 – R4.1 – 08.2016
System Overview

2. 2. 2 Positioning
Applications range from very small offices and branches (Mitel 415) to small and me-
dium-sized companies (Mitel 430).
The diagram below shows the MiVoice Office 400 communication servers with their ex-
pansion capacity for IP system phones.

Virtual Appliance

Mitel 470 Mitel 470 with expansion licence

Mitel 430

Mitel 415

5 10 20 30 40 60 80 100 200 300 400 800 1200

Number of users with IP system phones

Fig. 3 MiVoice Office 400 communication servers and their expansion capacity

2. 3 Networking Possibilities
MiVoice Office 400 communication servers at different company locations, even be-
yond national borders, can be linked together to form an enterprise-wide private com-
munication network with a common numbering plan. The following networking types
are possible:

Mitel Advanced Intelligent Network (AIN)

In an AINseveral communication servers of the MiVoice Office 400 series can be con-
nected up to form a homogeneous communication system. The single systems are
connected with one another via the IP network, thereby forming the nodes of the over-
all AIN system One node acts as the Master and controls the other (satellite) nodes. All
the features are then available at all the nodes.
No call charges are incurred as the internal voice traffic between locations is routed via
the system’s own data network. All the AIN nodes are configured and set up centrally
via the Master.
If a node is isolated from the rest of the AIN by an interruption in the IP connection, it
restarts with an emergency configuration after a set amount of time. The connections
are then routed to the public network via local links, for example with ISDN or SIP con-
nections, until contact with the AIN is restored.
For the Virtual Appliance communication server, AIN networking (Virtual Appliance as
master) with at least one satellite is mandatory.

20 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
System Overview

SIP networking
Networking based on the open global SIP protocol is the universal way of connecting
several systems with one another via the private data network or the internet. MiVoice
Office 400 communication platforms can be used to network up to 100 other Mitel sys-
tems or SIP-compatible third-party systems. All the main telephony features such as
call number and name display, enquiry call, hold, brokering, call transfer and confer-
ence circuits are supported. The transmission of DTMF signals and the T.38 protocol
for Fax over IP between the nodes is also possible.

Virtual and leased-line networking via BRI/PRI interfaces

With this type of With this type of connection the nodes are connected via basic rate in-
terfaces (BRI) or primary rate interfaces (PRI).
With virtual networking all the nodes are connected via the public ISDN network. This
type of networking is particularly well suited for geographically dispersed locations
which have such a low volume of calls between locations that leased lines or setting up
a private data network are not worthwhile. The range of services available in a virtual
network depends on the range of services offered by the network provider. The DSS1
ISDN protocol is the main protocol used.
With leased line networking the nodes are connected via dedicated or leased lines.
One advantage of leased line networking are the fixed costs, regardless of the number
of call connections. The most common protocol used is QSIG/PSS1, which supports
several more features than the DSS1 protocol.
Virtual and leased-line networking can also be used in combination. Mitel systems are
well as third-party systems can be used.

Mitel 415/430 as of R4.1 21

syd-0580/1.2 – R4.1 – 08.2016
System Overview

2. 4 Mitel system phones and clients

Mitel system phones stand out by virtue of their high level of user convenience and
their attractive design. The broad range of products ensures there is a suitable model
for every use.

Tab. 1 Mitel 6800 SIP series SIP phones

Additional model-specific fea-
Product Principal common features
tures
• User-friendly registration, configura- Mitel 6863 SIP:
tion and operation of system features • Integrated 10/100 Mbit Ethernet
Mitel 6863 through MiVoice Office 400 integra- switch for connecting a PC
SIP Phone
tion. Mitel 6865 SIP, Mitel 6867 SIP,
• XML browser compatible Mitel 6869 SIP and Mitel 6873 SIP:
• Automatic update of the terminal soft- • Integrated 1 Gbit Ethernet switch
ware for connecting a PC
Mitel 6865 • Web-user interface • Backlit display
SIP Phone • Excellent voice quality due to Mitel • Expansion key modules can be
Hi-Q™ wideband audio technology connected
• Full-duplex hands-free operation • Headset socket (DHSG standard)
(speakerphone) Mitel 6867 SIP and Mitel 6869 SIP:
• Several configurable line keys • Magnetic keyboard connector
Mitel 6867 • Three-party conference possible Mitel 6867 SIP, Mitel 6869 SIP and
SIP Phone
locally on the phone Mitel 6873 SIP:
• Wall mounting possible • USB Interface
• Power over Ethernet • Replaceable keyboard covers
Mitel 6873 SIP:
Mitel 6869 • Bluetooth interface
SIP Phone General:
• Additional model-specific features
include the resolution, the display
type and size, and the number of
Mitel 6873 configurable or fixed function keys.
SIP Phone

22 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
System Overview

Tab. 2 Mitel 6730 SIP series SIP phones

Additional model-specific fea-
Product Principal common features
tures
• User-friendly registration, configura- Mitel 6731 SIP:
tion and operation of system features • Integrated 10/100 Mbit Ethernet
Mitel 6730
SIP Phone through MiVoice Office 400 integra- switch for connecting a PC
tion. Mitel 6735 SIP , Mitel 6737 SIP and
• XML browser compatible Mitel 6739 SIP:
• Automatic update of the terminal soft- • Integrated 1 Gbit Ethernet switch
Mitel 6731 ware for connecting a PC
SIP Phone • Web-user interface • Backlit display
• Excellent voice quality due to Mitel • Expansion key modules can be
Hi-Q™ wideband audio technology connected
• Full-duplex hands-free operation • Headset socket (DHSG standard)
Mitel 6735 (speakerphone) Mitel 6739 SIP:
SIP Phone • Several configurable line keys • Bluetooth interface
• Three-party conference possible • USB Interface
locally on the phone General:
• Wall mounting possible • Additional model-specific features
Mitel 6737 • Power over Ethernet (except include the resolution, the display
SIP Phone Mitel 6730 SIP) type and size, and the number of
configurable or fixed function keys.

Mitel 6739
SIP Phone

Tab. 3 Mitel 6750 SIP series SIP phones

Product Principal common features Additional model-specific features
• User-friendly registration, configura- Model-specific features include the
tion and operation of system features resolution, the display type and size,
Mitel 6753
SIP Phone through MiVoice Office 400 integra- and the number of configurable or
tion. fixed function keys.
• XML browser compatible
• Automatic update of the terminal soft-
ware
Mitel 6755
SIP Phone • Web-user interface
• Excellent voice quality due to Mitel
Hi-Q™ wideband audio technology
• Full-duplex hands-free operation
Mitel 6757 (speakerphone)
SIP Phone • Several configurable line keys
• Three-party conference possible
locally on the phone
• Wall mounting possible
• Integrated 10/100 Mbit Ethernet
switch for connecting a PC
• Power over Ethernet

Mitel 415/430 as of R4.1 23

syd-0580/1.2 – R4.1 – 08.2016
System Overview

Tab. 4 SIP Multimedia Terminal Mitel BluStar 8000i

Product Main features
• Intelligent multimedia terminal with intuitive operation
• Video conferencing solution, collaboration tool and application platform in
one.
• XML browser compatible
• Bluetooth interface
• Can be connected to a laptop
• HD video camera with 30 frames per second
• Three loudspeakers for voice transmission in HD audio quality
Mitel BluStar 8000i • Four microphones to eliminate unwanted background noise
• 13 inch colour touch-screen display
• Biometric fingerprint reader
• Desktop sharing
• SIP-based

Tab. 5 IP system phones (softphones) and clients

Product Main features
• Autonomous and powerful SIP-based BluStar PC phone with video function-
ality
Mitel BluStar
• Can be used with headset or handset via PC audio interface, USB or
for PC
Bluetooth
• Graphical user interface with mouse and keyboard operation
• User-friendly contact search
• HD audio and HD video calls
• Outlook integration
• Link to e-mail client
• Click to Call
• Connection to an MS Lync server or an IBM Sametime server
• Autonomous and powerful, IP-based PC system phone with intuitive user
interface
MiVoice 2380
• Can be used with headset or handset via PC audio interface, USB or
Softphone
Bluetooth
• Graphical user interface with mouse and keyboard operation
• Displayable expansion keypad for team keys, functions and phone numbers
• Displayable keypad
• Ring tones expandable using .mp3, .mid and .wav files
• Call contacts directly from Outlook
• All the system features can be used
• OIP client application for a professional PC operator console
• Can be used purely as an IP softphone (MiVoice 1560) or together with a sys-
MiVoice 1560
tem phone (MiVoice 1560)
PC Operator
• Graphical user interface with mouse and keyboard operation
• Can be used in an AIN as a network-wide PC operator console
• Call management with internal and external queues
• Presence indicator, presence profiles, phone book and journal
• Operator groups and agent control
• Line keys and calendar functions
• Possibility of synchronisation with a Microsoft Exchange server
• All the system features can be used

24 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
System Overview

Product Main features

• OIP client application for PC-based call management
• Used in conjunction with a system phone
Mitel Office Suite • Graphical user interface with mouse and keyboard operation
• Configuration of the coupled system phone
• Call manager with extensive functions and options
• Presence indicator of other users
• Configurable presence profiles
• Phone book with address books and personal contacts
• Journal with call lists, text messages and notes
• Workgroups (agent control)
• Possibility of synchronisation with a Microsoft Exchange server
• Possibility of displaying various additional windows
• All the system features can be used
• FMC client for mobile phones (runs on various operating systems)
• Integrates the mobile phone into the Mitel communication system
Mitel Mobile Client • User is always reachable under the same call number (One Number con-
(MMC) cept)
• Various telephone functions can be menu-operated both in the idle state and
during a call
• Other system features can be used via function codes
• With MMC Controller handover is possible between internal WLAN and
mobile radio network.

Tab. 6 MiVoice 5300 IP series IP system phones (hardphones)

Product Principal common features Additional model-specific features
• Intuitive and user-friendly menu MiVoice 5370 IP/MiVoice 5380 IP:
MiVoice 5361 prompting with Foxkey and central • Expansion key modules can be
IP Phone navigation key connected
• All the system features can be used • Headset socket with DHSG stand-
• Excellent voice quality due to Mitel ard
MiVoice 5370 Hi-Q™ wideband audio technology • Integrated switch for connecting a
IP Phone • Automatic update of the phone soft- PC
ware MiVoice 5380:
• Connection via Ethernet • Backlit display
• Powered via Ethernet (POE) or • Optional Bluetooth module
MiVoice 5380
IP Phone power supply • Can be used as operator console
• Wall mounting possible when combined with expansion
• Web configuration interface key module
Note:
The MiVoice 5360 IP IP system phone is supported as before.

Mitel 415/430 as of R4.1 25

syd-0580/1.2 – R4.1 – 08.2016
System Overview

Tab. 7 Digital system phones of the MiVoice 5300 family

Product Principal common features Additional model-specific features

MiVoice 5361
Digital Phone
• Intuitive and user-friendly menu MiVoice 5370/MiVoice 5380:
prompting with Foxkey and central • Expansion key modules can be
MiVoice 5370
Digital Phone

MiVoice 5361
MiVoice 5380
Digital Phone

Digital Phone navigation key connected

• All the system features can be used • Headset socket with DHSG stand-
• Automatic update of the phone soft- ard
MiVoice 5370 ware MiVoice 5380:
Digital Phone • Connection via DSI interface • Backlit display
• Two phones can be connected per • Optional Bluetooth module
DSI interface • Can be used as operator console
• Powered via DSI bus or power supply when combined with expansion
MiVoice 5380
Digital Phone • Wall mounting possible key module

Note:
The digital system phones of the Office family (Office 10, Office 25, Office 35, Office 45 and Office 45pro) are sup-
ported as before (not all system features can be used).

Tab. 8 Cordless system phones of the Mitel 600 DECT family

Product Principal common features Additional model-specific features
• Intuitive and user-friendly menu Mitel 622 DECT/Mitel 632 DECT/Mit
prompting with Foxkey and central el 650 DECT:
navigation key • 3 configurable side keys
• Colour display • Vibra call
• All the system features can be used • Bluetooth interface
Mitel 612 Mitel 622 • Automatic update of the phone soft- • USB Interface
DECT Phone DECT Phone ware • micro-SD card interface
• Backlit display and keyboard • Power battery (optional)
• Headset socket Mitel 632 DECT:
• Automatic handover and roaming • Complies with industry standard
• Can be operated on both the DSI (IP65)
radio units SB-4+, SB-8, SB-8ANT • With emergency button and sensor
and the SIP-DECT® radio units RFP alarms, suitable for personal pro-
L32 IP, RFP L34 IP and RFP L42 tection
Mitel 632 Mitel 650
WLAN Mitel 650 DECT:
DECT Phone DECT Phone
• Supports the DECT standard CAT-
iq (Cordless Advanced Technology
– internet and quality) for high-
quality broadband telephony (can
be used with Mitel SIP-DECT only).
Note:
The Mitel 610 DECT, Mitel 620 DECT, Mitel 630 DECT, Office 135/135pro and Office 160pro/Safeguard/ATEX
cordless system phones are supported as before (not all system features can be used).

26 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
System Overview

Tab. 9 Analogue Mitel phones

Product Principal common features Additional model-specific features
• Destination dialling keys Mitel 6730 Analogue:
• Frequency dialling or pulse dialling • Three-line display
Mitel 6710
• Handsfree • 100 phone book contacts
Analogue Phone
• Adjustable volume (handset and • 50 entries each on call list and redial
loudspeaker) list
• System features can be used via • Number/name display for incoming
Mitel 6730 function codes calls
Analogue Phone • Headset connection • Clock with wake-up function
• Wall mounting possible • Functions controllable via communi-
• Functions controllable via communi- cation server: Delete call lists and
cation server: Message display local phone book, set date, time and
on/off, delete redial key memory. language.
• Ideally suited for hospitality and
hotel environments
Note:
The Aastra 1910 and Aastra 1930 analogue phones are still supported.

2. 5 Various phones, terminals and equipment

Thanks to the use of international standards other clients, terminals and phones, Mitel
and third-party, can be connected and operated on the communication server:

• SIP-based phones
With the integrated SIP protocol SIP-based phones (softphones, hardphones) - or
via an SIP access point also WLAN and DECT phones - can be connected to the
communication server. Besides the basic telephony functions, features such as call
transfer, conference calls or CLIP/CLIR are also supported. Function codes can
also be used to operate various system functions.
• Cordless phones
The sturdy 9d DECT phones from the Ascom Wireless Solutions product portfolio
can be logged on to the communication server as system phones. User-friendly
messaging and alarm systems can thus be implemented in combination with the
IMS (Integrated Message Server). Other DECT phones can also be operated in
GAP mode.
• Analogue terminals
All terminals (phones, fax, modem, etc.) approved by the network operator can be
connected on the analogue terminal interfaces. The communication system sup-
ports pulse and frequency dialling modes.
• ISDN terminals
ISDN terminals that comply with the Euro ISDN standard can be connected to the

Mitel 415/430 as of R4.1 27

syd-0580/1.2 – R4.1 – 08.2016
System Overview

BRI-S terminal interfaces. The communication system provides a series of ISDN

features at the S bus.
• Mobile/external phones
Mobile/external phones can also be integrated into the communication system.
They can then be reached under an internal call number, and their status is moni-
tored and displayed. Internal/external calls can be made via the integrated mo-
bile/external phone; system functions can also be executed using function codes.
With the Mitel Mobile Client for mobile phones application all the main telephony
functions are available with menu prompting (see "Mitel Applications", page 29).

2. 6 Solutions
• Alarming and Health care
Thanks to the components Mitel Alarm Server, I/O-Gateway and the OpenCount
application, flexible solutions are available for hospitals and old people's nursing
homes. MiVoice Office 400 communication-server-integrated functions such as "Di-
rect response" "Hotline alarm" or "PIN telephony" allow easy deployment of availa-
ble features.
• Hospitality/Hotel
The hospitality software package provides functions to implement a user-friendly ac-
commodation and hotel solution in the range of 4 to 600 rooms. This solution is also
ideally suited for the management of care homes and retirement homes. The func-
tions are operated using the MiVoice 5380 / 5380 IP reception phone or the web-
based Mitel 400 Hospitality Manager application. Connection to a Property Manage-
ment System (PMS) via the communication server's Ethernet interface is also possi-
ble. The commercially available FIAS protocol is provided for this purpose.
• Mobility
Mobility solutions, especially Mitel Mobile Client (MMC), enable employees to log on
to the company network using their mobile phones. The MMCC Compact and
MMCC 130 controllers allow mobile users to move back and forth between the inter-
nal WLAN coverage and the mobile radio network without the call being interrupted.
Moreover, with Mitel SIP-DECT and Mitel 600 DECT series phones comprehensive
solutions can be provided for wireless telephony on IP-based networks. In so doing,
RFP radio units are directly connected to the LAN like a VoIP device.

2. 7 Applications and application interfaces

A distinction is made among applications between Mitel-specific applications and certi-
fied applications supplied by third parties.
The Mitel application Mitel Open Interfaces Platform (OIP), as well as the certified
third-party applications, are installed on a customer server. They communicate with the

28 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
System Overview

communication server via standardised interfaces (see "Application interfaces",

page 31).
Auxiliary applications for planning and the configuration and park management are
available as a web application.

2. 7. 1 Mitel Applications
Tab. 10 Mitel applications
Application Main features
• Simple first party CTI application
• Dial, answer, hang up
• Integration in Outlook, Lync 2013 and Office 365
Mitel Dialer • Search in directories
• Compatibility with MiVoice 5300, MiVoice 5300 IP, Mitel 6700 SIP /
6800 SIP, Mitel 600 DECT series phones
• Installation via SSP or WebAdmin
• Application interface for deep integration of applications by Mitel or other
manufacturers (see "Application interfaces", page 31)
• Easy to manage through an integrated web-based application
• Integrates the MiVoice 1560 PC Operator and Mitel OfficeSuite applications
• Presence-controlled communication coupled with Outlook diary entries
• Integration of contact databases and directories (Outlook, Exchange, Active
Directory, LDAP directories, phone book CD)
Mitel Open Interfaces
• Integration of building automation equipment and alarm systems
Platform (OIP)
• Call centre functions with flexible routing algorithms, skill-based agent
groups and emergency routing
• Unified messaging with notification whenever new voice messages are
received via email (incl. message attachment)
• Partner program for integrating and certifying applications by other manufac-
turers
• Also available as OIP Virtual Appliance, for installation on a VMware server.
Comprehensive Unified Communications and Collaboration solution:
• Central software provided for industry standard servers or virtual environ-
ments
• Integration of Microsoft® Outlook®, IBM® Lotus Notes® Google®, Micro-
soft® Lync® etc.
UC clients for desktop, web and mobile applications:
Mitel MiCollab
• Comprehensive real-time presence information
• Dynamic call distribution
• Real collaboration with joint use of the desktop and documents
• Easy retrieval of voice messages
• Secure instant messaging (IM) and data transmission
• Audio, web and video conferences
• Mitel 400 CCS is an additional application for the Mitel 400 Call Center, and
Mitel 400 CCS provides statistics / reporting functions and agent monitoring (CCS = call
centre supervision). The licensing of the application is made via OIP.

Mitel 415/430 as of R4.1 29

syd-0580/1.2 – R4.1 – 08.2016
System Overview

Application Main features

• MitelOpenCount is a software package used for the call logging manage-
Mitel OpenCount ment on the communication system. It consists for selected sectors of basic,
comfort and premium solutions and is installed on an external server.
• Powerful Unified Communications solution
• Presence management with calendar integration
• Instant Messaging (chat), video, SMS and e-mail functions
• Compatibility with the federation between Mitel Business CTI servers and/or
Microsoft Lync and OCS
Mitel BusinessCTI
• Easy integration into CRM and ERP systems
• Compatible with other call managers
• Clients for PC (Windows, Mac) and mobile phones/tablets (Android/IOS)
available
• Optional additional modules Mitel BusinessCTI Analytics
• Contact Center on a location with up to 80 agents
• Progress reports
• Real-time monitoring
MiContact Center
• Dynamic agents and wait loop control
Business
• Screen pop
• Intelligent Messaging
• Multimedia compatibility
• Highly scalable solution which offers mobile and external workers secure
Mitel Border Gateway
and seamless access to the company's voice and data applications, regard-
(MBG)
less of their location.
Mitel Alarm Server • Specially designed for use in hospitals and nursing homes, industries and
businesses as well as public domains.
• Mitel Alarm Server monitors processes, activates the required services, sets
off alarms based on predefined samples or notifies selected recipients via
paging, e-mail, SMS or voice message.
• The alarm can be set off via a nurse call or fire-alarm system (ESPA inter-
face), via a key predefined on the Mitel DECT or system phone, an alert but-
ton, web client, or by calling the alarm server (audio guide), or via e-mail
(subject line analysis).

Tab. 11 Planning and configuration applications

Application Main features
• Web-based planning application for Mitel communication platforms (CPQ = Con-
figuring Planning Quoting)
• Uses project data to calculate the necessary communication server complete with
Mitel CPQ terminals, interface cards, modules and licences
• Country-specific adaptations possible for accessories
• Stored price lists and configurable quote compilation
• No installation necessary
• Web-based configuration tool for configuring and monitoring a single system or
an entire network (AIN)
• Access control with user accounts and predefined authorization profiles
WebAdmin
• Special accesses for hospitality solutions
• Integrated online help and configuration assistant
• Integrated in the communication server software package

30 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
System Overview

Application Main features

• Integrated web-based application used to operate functions in the hospitality sec-
tor
Mitel 400 Hospitality
• List view and floor-by-floor view of the rooms
Manager
• Functions such as check-in, check-out, group check-in, notification, wake-up call,
retrieval of call charges, maintenance list, etc.
Web-based application for end-users, which allows personalised configuration of a
telephone:
• Functions key assignment and printing of labels
Self Service Portal • Setting the idle text and language
(SSP) • Setting the presence profiles, personal call routing, voice mail, forwarding, etc.
• Setting up dial-in conference rooms
• Creating private phone book contacts
• Managing personal data such as e-mail address, password, PIN, etc.
• Server-based solution for secure IP remote management
Secure IP Remote • No router and firewall configuration or VPN connection setup required
Management (SRM) • Allows configuration via WebAdmin once the connection has been set up
• No installation necessary

2. 7. 2 Application interfaces
The most important interface for own and third-party applications is the interface of the
Mitel Open Interfaces Platform (OIP). This open interface allows the applications to be
deeply integrated with telephony. Third-party applications can also be integrated on
MiVoice Office 400 series systems via different interfaces without OIP.

2. 7. 2. 1 Mitel Open Interfaces Platform

OIP applications OIP TAPI Third party

service provider applications

Open Interfaces Platform (OIP)

OIP connectors

Automation and
Communication systems External directories
alarming systems

Fig. 4 OIP as middleware between communications system, external data sources and applications

Mitel 415/430 as of R4.1 31

syd-0580/1.2 – R4.1 – 08.2016
System Overview

OIP services
The OIP services are the central components of OIP. They are used to control the sys-
tem and make the OIP features and interfaces available. Thanks to the modular organ-
isation and vast configuration possibilities, versatile and customer-specific solutions
can be set up.

OIP applications
Sophisticated Softphones are available as OIP applications and are controlled as cli-
ents via OIP.

• Mitel OfficeSuite is a rich-client application, which significantly broadens the range

of functions of the coupled fixed and cordless phones.
• MiVoice 1560 PC Operator is an operator application which can be used as rich-cli-
ent application together with a fixed or cordless phone or alone as Softphone.

Possible OIP application fields are listed in the following sections:

OIP as directory server

Already available directories, databases and phone books are linked to OIP and made
useful for name dialling and identification.
Integration is compatible with many standard databases such as Microsoft Exchange,
Microsoft Outlook, Microsoft Active Directory, communication server directories, LDAP
and ODBC directories and electronic phone books.
Moreover, Microsoft Exchange directories can be directly synchronised.

Unified Communications - OIP as telephony server

When OIP is used as telephony server, telephony integrates in a scalable manner into
IT communication: Top-class Softphones, PC-operated fixed and cordless phones,
presence-controlled call, voice mail control and calendar coupling via presence pro-
files, name dialling and call number identification via all linked company directories,
synchronisation of Microsoft Exchange contacts, e-mail notifications, etc. facilitate daily
communication.

OIP as operator centre

Several multi-functional operator applications can be organised with call centre func-
tions in operator groups.

OIP as Free Seating Server

OIP supports and expands the MiVoice Office 400 free seating function: A user logs on
at a free seating workstation and the phone automatically takes over his call number
and device configuration.

32 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
System Overview

OIP as call center

The powerful Mitel 400 Call Center is an integral part of OIP and provides all the main
features such as flexible routing algorithms (cyclical, linear, longest time available,
CLIP-based, last agent), skill-based agent groups as well as an analysis of the call
centre data (online and offline) with chart-based evaluation. In the event of a network
interruption the emergency routing ensures the maximum availability of the system.
The agent functionality is available on all system phones including Softphones. This
applies equally to home workstations and to all the users on a Mitel Advanced Intelli-
gent Network. The one number user concept can also be set up for agents, which pro-
vides the staff of a Call Center with maximum mobility within the company.
The Mitel 400 Call Center is easy to manage and configure thanks to OIP WebAdmin.
Various monitoring functions, simple statistical evaluations and work group control can
be comfortably implemented using the administration interface.
Mitel 400 CCS is an extension of the Mitel 400 Call Center and offers several possibil-
ities of statistically evaluating the call centre operation. Offline and online reports ena-
ble the call center operator to analyse and optimise call centre operations.

OIP as application interface

Certified third-party manufacturers can, for instance, integrate sector-specific applica-
tions into the MiVoice Office 400 and OpenCom communication environment.

OIP as automaton and alarm system

External alarm systems and building automation equipment (e.g. KNX) are easily mon-
itored through the connection to the communication system. This allows information to
be exchanged in a simple way between the systems. In this way the user can use his
system phone for voice communications and for monitoring external systems.
The I/O service offers a wide range of features which allows very flexible uses and ver-
satile applications. Some of its examples are listed below:

• Alarming equipment for maintenance personnel

• Monitoring of production processes
• Forwarding messages as e-mails
• Connection to building automation systems (KNX)

With the graphical interface (tree structure) events and the relevant actions are easily
linked with one another.

OIP in a networked environment

An OIP server can also be used in an AIN. To do so, it will be linked to the Master. In
addition, several communication systems can also be connected to an OIP server. It is
then possible for instance to obtain network-wide call logging for all the systems, to dis-

Mitel 415/430 as of R4.1 33

syd-0580/1.2 – R4.1 – 08.2016
System Overview

play call charge information on the system phones or to display status in the presence
indicator field of a PC operator console for all the users connected.

See also:
More information can be found in the Mitel Open Interfaces Platform system manual and in the
OIP WebAdminOnline help.

2. 7. 2. 2 Message and alarm systems

MiVoice Office 400 supports several message formats and message protocols for im-
plementing messaging, monitoring and alarm systems.

Internal messaging system for system phones

The internal messaging system for system terminals allows users to exchange prede-
fined or user-defined text messages between system phones. Text messages can also
be sent to individual users or message groups.
The internal messaging system does not have an interface with which it can be ad-
dressed directly. However it can also be operated via OIP.

External messaging, monitoring and alarm systems

The powerful ATAS/ATASpro protocol is available via the communication server’s
Ethernet interface for applications in the security and alarming sector. This protocol
can be used to implement customised alarm applications. An alarm appears on the dis-
play of system phones, complete with the freely definable user functions that apply
only to that alarm. In addition the duration of the tone as well as its volume and melody
can be freely defined by the user for each alarm.
The Mitel Alarm Server is a flexible solution which can be used in all sectors to process
and record alarms. It can be used, for instance, in old people's nursing homes and as-
sisted-living homes, as well as in other different facilities such as hotels, industrial
plants, shopping centres, schools or administrations. When used together with Mitel
SIP-DECT it is even possible to dynamically determine the environment of the alarm
solution using the location feature provided by the DECT system.
The cordless DECT phone Mitel 630 DECT is specially designed for applications in the
security and alarming sector. Besides a special alarm button it also features a man-
down alarm, a no-movement alarm and an escape alarm. Sensors inside the phone
constantly check the handset’s position and motion. An alarm is triggered if the phone
remains in a virtually horizontal position or motionless for some time or if the handset is
shaken violently.

34 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
System Overview

2. 7. 2. 3 CTI - Computer Telephony Integration

The Computer Telephony Integration (CTI) integrates telephony services in the com-
pany process. Besides conventional telephony features Mitel Open Interfaces Platform
(OIP) offers many other convenient functions, which supports the employees with their
daily work, for instance:

• Dialling by name for outgoing calls and CLIP display for incoming calls offers an
added value by the integration of external directories and databases.
• Notification of Microsoft Outlook appointments on the system phones
• Presence-controlled communications with Busy Indicator
• Automatic Call Distribution
• Access to system configuration, what a maximum integration of different systems
ensures

And of course the communication system supports also First and Third-Party CTI inter-
faces for commercial CTI applications based on the Microsoft TAPI 2.1 standard.
Terminal supervision/control on the communication server by third-party applications
via the CSTA protocol is also supported.

First-party CTI
A first-party CTI is the direct physical connection between a phone terminal and a te-
lephony Client (workstation PC). Telephony functions and telephone states are con-
trolled and monitored on the telephony Client. A first-party CTI solution is ideal for a
small number of CTI workstations and is easily implemented.
MiVoice Office 400 supports First-Party CTI on all system phones via the Ethernet in-
terface. For this purpose the First-Party TAPI Service Provider (AIF-TSP) is required.
For first-party CTI applications which use the CSTA protocol (for instance Mitel Dialer),
the ECSTA driver (Mitel CSTA-to-TAPI Link) is required.

Application example

• Dialling from a database (phone book CD, etc.)

• Caller identification (CLIP)
• Creating a call journal
• Mitel Dialer (see Tab. 10, página 29)

Mitel 415/430 as of R4.1 35

syd-0580/1.2 – R4.1 – 08.2016
System Overview

Third-party CTI
Third-party CTI is an user-friendly multi-station solution. In contrast to first-party CTI,
third-party CTI controls and monitors several system phones (including cordless
phones) via the central telephony server, which is connected with the communication
server. In addition phones on ISDN and analogue interfaces can also be monitored. PC
and phone allocation is handled by the telephony server.
The third-party CTI connection is effected via Ethernet using the Mitel Open Interfaces
Platform (OIP). To this end the OIP is installed on the telephony server. Third-party
connections via Ethernet with CSTA are also possible.

Application example

• Busy indicator
• Group functionality
• Networked CTI solution
• Automatic Call Distribution (ACD)

2. 7. 2. 4 ISDN interface
MiVoice Office 400 supports the ISDN protocols ETSI, DSS1 and QSIG. Besides the
possibility of networking various systems into a PISN (Private Integrated Services Net-
work) via the ISDN interface, these protocols also provide various functions that can be
used for connecting external applications (e.g. IVR systems, fax server, voice mail sys-
tems, unified messaging systems, DECT radio systems).

2. 7. 2. 5 Configuration
The MiVoice Office 400 communication server is configured via the web-based
WebAdmin application. Other components of the application include special accesses
for hospitality and hotel solutions as well as a configuration wizard.

2. 7. 2. 6 System monitoring
The system status is monitored with event messages which can be sent to various in-
ternal or external destinations. Examples of message destinations are: system phones,
events log (WebAdmin), e-mail recipients, SRM servers, alarm servers (ATAS) or
SNMP destination. Event messages are also accessible via the Mitel Open Interfaces
Platform for application manufacturers.

36 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
System Overview

2. 7. 2. 7 Call logging
The Call Logging Manager includes data acquisition for incoming traffic (ICL), outgoing
traffic (OCL) and the counting of the acquired call charges according to a variety of cri-
teria. The data can be retrieved via different interfaces and subsequently processed.

2. 7. 2. 8 Hospitality/Hotel
The MiVoice Office 400 communication servers offer you several possibilities to imple-
ment a hospitality and hotel solution, with different operation applications and inter-
faces. Configuration is via WebAdmin. The MiVoice 5380 / 5380 IP reception phone or
the web-based Mitel 400 Hospitality Manager application is available to operate the
functions. A connection to a Property Management System (PMS) via the communica-
tion server's Ethernet interface is also possible. The commercially available FIAS pro-
tocol is provided for this purpose.

2. 7. 2. 9 Voice over IP
MiVoice Office 400 is a native VoIP solution. Apart from the possibility to operate IP
system phones and SIP phones via the Ethernet interface, MiVoice Office 400 systems
can also be networked over IP.

2. 8 First steps...
If you are setting up an MiVoice Office 400 communication system for the first time, it
may be useful to set up a test system step by step on site. We have provided you with
a "getting started package" for this.

Getting-started package
The getting-started package contains a beginner's guide for learning how to set up a
MiVoice Office 400 communication server, a Mitel CPQ configuration file and the
search and help tool System Search (not available for Virtual Appliance). The getting-
started package is available for downloading via the following hyperlinks:

Tab. 12 Getting started

Communication server English English
Getting-started package Mitel 415/430 syd-0599 syd-0600
Getting-started package Mitel 470 syd-0604 syd-0605
Getting-started package Virtual Appliance syd-0630 syd-0631

Mitel 415/430 as of R4.1 37

syd-0580/1.2 – R4.1 – 08.2016
System Overview

2. 9 Connection options

Digital terminals
WE 23
Aug 16:58
Week
Office 34
Menu 80IP

Digital system phones

telephony network

DSI
Analogue public

DTMF / IMP FXO

DSI
Integrated DECT system
DSI

DSI WE 23
Aug
Week
Office
16:58
34

PC operator consoles
Menu 80IP
Public network

BRI-S
SIP Provider

ISDN phones
Gateway

Ethernet
IP

BRI-S External applications

Fax servers
Public telephony network

BRI-Sextern
Fax 1...3
(2B+D) BRI-T
ISDN (DSS1)

IP phones
(30B+D) PRI
PC operator consoles (softphones) IP
system phones (softphones) SIP
Ethernet
phones (softphones)
IP

IP system phones (desk phones) SIP

phones (desk phones)
Private network

OMM RFP
network PISN (QSIG /

BRI-Sextern
Private telephony

SIP-DECT with
Mitel 415/430

Ethernet OpenMobilityManager
BRI-T
PSS1)

PRI Analogue interfaces

FXS Pulse dialling / Frequency
dialling phones
FXS
Fax machines, Group 3,
answering machine
FXS
General bell
network AIN or SIP
Private IP data

Ethernet
FXS Door intercoms with DTMF
control functions
FXS
Control outputs

FXS Control inputs for switch group

control

Management CTI and TAPI

DSI
Self Service Portal (SSP) First-Party CTI via LAN with
WebAdmin digital system terminal
Hospitality Manager Ethernet
Ethernet
IP

Secure IP remote management

(SRM)
Ethernet Third-Party CTI with telephony
server
Special interfaces
DSI
ODAB

VGA
Door intercom system CTI /call centre workstations

Door opener
Controller
Fixed Mobile Convergence
USB
Bell input Ethernet Mitel Mobile Client

Audio source (input) Applications server

Ethernet
Open Interfaces Platform (OIP)
Telephony Web Interface (TWP)
Messaging and Alarm Systems
Hotel Management Systems

Fig. 5 Overview of interfaces with possible terminal equipment

38 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

3 Expansion Stages and System Capacity

The basic systems can be expanded using interface cards, system modules and li-
cences. The expansion possibilities available and the maximum system capacities
need to be known so the communications system can be ideally adapted to cus-
tomer requirements. With the project data the optimum hardware configuration is
easily determined using the project planning application Mitel CPQ.

3. 1 Summary
The expansion possibilities of the basic systems Mitel 415 and Mitel 430 at a glance.
The equipment is powered by an external power supply. The same power supply unit is
used for Mitel 415 and Mitel 430.
The mounting options are described in the Chapter "Fitting the communication server",
page 82.

Communica- Interface cards System Wiring adapter Mounting

tion server module options
2 x BRI-T/S 1 x DSP T/S Typ0 Cable cover set
TIC-2TS SM-DSPX1 WA-TS0
Mitel 415
basic system 3 x BRI-T/S, 1 x BRI-T 2 x DSP T/S Typ1 Rack-mounting set
TIC-4TS SM-DSPX2 WA-TS1 Mitel 415

2 x FXO 2 Draht Rack-mounting set

TIC-2AB WA-2W Mitel 430
Mitel 430
basic system
4 x FXO PRI
TIC-4AB WA-1PRI

1 x PRI
TIC-1PRI
4 x DSI
EADP4

4 x FXS
ETAB4
FXS: Foreign Exchange Station
Door/Outputs/Inputs FXO: Foreign Exchange Office
ODAB DSI: Digital Station Interface

Fig. 6 Overview of the expansion possibilities

Mitel 415/430 as of R4.1 39

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

3. 2 Basic system
Mitel 415and Mitel 430 are based on the same basic system, they differ in terms of the
components fitted to the mainboard, the expansion possibilities and the system capac-
ities. The basic systems consists of the following components:

• Mainboard with front panel, screw covers and designation label integrated in metal
housing with detachable plastic cover
• Power supply unit with power cord

3. 2. 1 Interfaces, display and control elements

The following mainboard interfaces can be accessed only when the housing cover of
the communication server is open:

Tab. 13 Mainboard
Interfaces Mitel 415 Mitel 430 Designation / Remarks
Slots for interface cards 2 4 IC1...IC4 / with snap mechanism
Slots for system modules, type 1 1 1 SM1 / three system modules, stackable
Slots for system modules, type 2 – 11) SM2
Slots for wiring adapters 2 4 WA1...WAx / one slot per wiring adapter
Slot for EIM card 1 1 EIM / card holder
Fan interface2) – 1 FAN / 3-pin connector (Mitel 430 only)
1) Not used at the moment
2) The fan is required only if the Mitel 430 is rack-mounted

The following interfaces, display and control elements of the mainboard are routed to
the front panel:

Tab. 14 Front panel

Interfaces Mitel 415 Mitel 430 Note
DSI terminal interfaces 2 4 RJ45 socket
FXS terminal interfaces 2 2 RJ45 socket
Ethernet interfaces 10/100BaseT, half/full-duplex 2 2 RJ45 socket
RJ45 sockets on front panel, total 16 24 RJ45 socket
Audio input 1 1 3-pin jack socket
Supply input 1 1 2-pin supply socket
Pilot key 1 1
LED display 1 1

The diagram below shows the position of all the interfaces and slots on the mainboard
display and control elements and on the front panel.

40 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

Mainboard EIM
Cardholder for
EIM card
SM1

Connector
for fan

FAN
SM2 (Mitel430)

(Mitel430)

IC1 IC2 IC3 IC4

(Mitel430) (Mitel430)

Internal interfaces
Ethernet FXS DSI

WA0 WA1 WA2 WA3 WA4

(Mitel430) (Mitel430)

LED display

(Mitel430)

Socket for Audio Front Pilot key

plug-in input panel
power
supply unit

Legend:
IIC1...4 Slots for interface cards (trunk cards, terminal cards and options cards)
WA1...4 slots for wiring adapters
SM1 Slot for stackable system modules, type 1 (DSP(X) modules)
SM2 Slot for stackable system modules, type 2 (not used for the moment)

Fig. 7 Mainboard interfaces, display and control elements and front panel

Mitel 415/430 as of R4.1 41

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

3. 2. 2 Power supply
The system is powered as standard with 230 VAC or 115 VAC using the supplied
power supply. The communications server is powered with 19V DC from the power
supply. All other voltages are generated directly on the mainboard. To ensure that its
operation is maintained even in the event of a mains outage, an external uninterrupti-
ble power supply (UPS) must be used. For more details about the power supply see
"Powering the communication server", page 95.

3. 2. 3 Media resources
Media resources are used for complex signal processing functions, and made availa-
ble by DSP chips. (DSP stands for Digital Signal Processor). They provide functions for
conference circuits, DTMF sender and receiver, compression of voice data, etc. A DSP
chip is fitted permanently to the mainboard.
Part of these media resources is allocated to fixed functions and can be used without li-
cences (see Tab. 15).
Another part is allocated to selectable functions, according to requirements. These
functions are partly subject to licence (see Tab. 16).
The basic resources of the communication server can be expanded by fitting DSP
modules. The functions of the DSP chips on the modules can also be configured (see
Tab. 23 and Tab. 22).

Fixed functions of the mainboard DSP

The table below provides an overview of the fixed functions of the mainboard DSP. No
licences or additional hardware is required to use the functions.

Tab. 15 Fixed functions of the mainboard DSP

Max. number of simultaneous ... Mitel 415 Mitel 430
Total circuits for the functions1) three-party conference, six-party conference, intrusion 4 4
and silent intrusion.2)
Circuits for the Call Waiting function 2 2
DTMF sender 3 3
DTMF receiver for voice mail or auto attendant 2 2
DTMF receiver for analogue terminals 4 4
Dialling tone receiver 2 4
Busy tone receiver 4 4
Ring receiver 2 2
FSK receiver for CLIP detection on analogue network interfaces 2 2
FSK transmitter for CLIP display on analogue terminals 2 2
Total audio channels for basic voice mail (G.711)3) or auto attendant2) 2 2
1) The functions can all be of the same type or used as a mix.

42 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

2) Licence required
3) Can be used without licence subject to the following restrictions: Voice memory capacity approx. 20 minutes,
no e-mail notification in the event of new voice messages, no forwarding of voice messages, no call record-
ing, restricted voice mail menu by remote retrieval.

Selectable functions of the mainboard DSP

The DSP on the mainboard provides selectable functions. A description of the individ-
ual functions can be found as of page 45.
The functions are determined in the Media resources ( =ym) view. In Tab. 16 all the
possible combinations are listed, with the maximum number of channels. For this the
DSP chip on the mainboard has to be loaded with different firmware. Additional func-
tions require the use of one or more DSP modules. Some of these functions are sub-
ject to a licence.

Tab. 16 Selectable functions of the mainboard DSP

DECT VoIP1) Audio1) GSM1) CAS2) Modem Remarks
4 Standard configuration
2 2 8
2 2 30
4 8
4 30
3 G.711 VoIP channels only, two of them can
be used licence--free.
1
1) Licences required (see also "Licences", page 62)
2) Of relevance only to certain countries such as Brazil

Notes
– To be able to configure VoIP channels on the mainboard’s DSP, make sure that in the Media
resources ( =ym) view the VoIP mode parameter is set to G.711.
The configured VoIP mode is valid for all the DSP chips of a node. The following also applies
to this mode:
- Two G.711 VoIP channels per system can be used without a licence.
- The G.711 VoIP channels of the mainboard can be combined with G.711 VoIP channels of
DSP modules.
– If voice mail channels are configured and licensed, the two G.711 basic voice mail channels
that can be used without a licence are redundant (see Tab. 15).
– Voice mail channels can only be configured on one DSP chip per node.
– The Modem function is used for remote maintenance via an analogue modem and can only
be configured on the mainboard’s DSP.
– The system has to be restarted for the configuration changes of the DSP to take effect.

Mitel 415/430 as of R4.1 43

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

3. 3 Expansion with cards and modules

A basic system can be individually expanded using interface cards and system mod-
ules. The number of available expansion slots depends on the type of the basic system
(see "Interfaces, display and control elements", page 40).

3. 3. 1 System modules
System modules expand the resources of the communication server, allowing the sys-
tem to be expanded step by step in line with requirements.

3. 3. 1. 1 DSP modules
Processor-intensive system functions require media resources. The communication
server’s DSP capacity increases through the use of DSP modules.

Fig. 8 Design of the DSP module

DSP modules belong to the category of system modules 1 and are stacked to the SM1
slot (see Fig. 7). The different types of modules can be used as a mix.

Note
The SM1 and SM2 slots are not identical (the space between the two connector rails is differ-
ent). Fitting DSP modules on the SM2 slot is thus not mechanically possible.

Tab. 17 DSP modules

Number of DSP chips Max. number of Max. number of
Type
per module Mitel 415 modules Mitel 430 modules
SM-DSPX1 1
SM-DSPX2 2
3 3
SM-DSP11) 1
SM-DSP21) 2
1) Although no longer available, the module is still supported.

44 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

Compared with DSP modules, modules with the designation DSPX are fitted with more
powerful DSP chips. They are used to transmit VoIP data among others using the
SRTP protocol (Secure VoIP).

Allocatable functions
One or more functions can be allocated to the individual DSP chips on the DSP mod-
ules. For this the DSP chips have to be loaded with different firmware. The additional
media resources can be used for DECT telephony, Voice over IP, fax transmissions,
audio services, integrated mobile/external phones or for remote maintenance via mo-
dem. This means that for each DSP chip a specific number of channels is available for
the corresponding functions. Some of these functions are subject to a licence (see also
"Licences", page 62).
Functions are allocated in WebAdminin the Media resources ( =ym) view.

• DECT
Operation of a DECT system on DSI interfaces with cordless phones. The voice
data must be transformed on connections between DECT and non-DECT end-
points. This process requires DSP capacity.
Purely DECT-DECT connections set up already do not require any media re-
sources. On the other hand, media resources are required to set up connections.
DECT channels can be used without a licence.
• VoIP
Connections between IP and non-IP endpoints are made via an IP media gateway.
This is carry out by the integrated standard media switch that switches VoIP chan-
nels for call connections in the IP network. The Standard Media Switch uses media
resources for the real-time processing of the call data. VoIP channels are always re-
quired between IP and non-IP endpoints, e.g. for internal connections between an
SIP/IP phone and a digital system phone or e.g. for an external user who is routed
to the internal Voice Mail System via an SIP network interface. In an AIN VoIP chan-
nels are also used for call connections between the nodes (see "Use of VoIP chan-
nels", page 46 for an overview).
The number of configurable VoIP channels depends on both the type of DSP chip
(see "Configuration of DSP chips", page 49) and the configured mode (see "Stand-
ard Media Switch modes of operation", page 48).
If the VoIP mode is set to G.711, two G.711 VoIP channels per system can be used
without a licence. One VoIP Channels for Standard Media Switch licence is required
for each additional VoIP channel.
• FoIP
For reliable real-time fax transmissions via an IP network using the T.38 fax protocol
(ITU-T). FoIP channels can be used without a licence.
• Audio services
The audio channels are used to play back and record audio data. Additionally, each

Mitel 415/430 as of R4.1 45

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

audio channel is assigned a DTMF receiver for enabling user inputs during play-
back. Licences (Enterprise Voice Mail, Audio Record & Play Channels, Auto Atten-
dant) and media resources are required for this.
Audio channels can be used for voice mail, auto attendant, queue with announce-
ment, call recording, announcement with audio file, or conference bridge. The allo-
cation is configurable (see "Reserving audio channels", page 48). Announcement
service and music on hold use their own resources.
The number of configurable audio channels depends on both the configured mode
(see "Voice-mail system modes of operation", page 49) and the type of DSP chip
(see "Configuration of DSP chips", page 49).
• GSM
Enhanced functionality is achieved for integrated mobile/external phones by provid-
ing special DTMF receivers during the call connection. Suffix dialling functions (such
as enquiry calls or setting up a conference with function codes ) can be carried out
as a result. The number of GSM channels – and therefore the number of DTMF re-
ceivers – depends on the number of users with integrated mobile/external phones
who want to use this functionality simultaneously.
One Mobile or External Phone Extension licence is required for each integrated mo-
bile/external phone.
• CAS
CAS (Channel-associated signaling) is a signalling protocol for PRI network inter-
faces used in certain countries (e.g. Brazil). This setting provides the tone sender
and receiver for transmitting signalling information.

Use of VoIP channels

VoIP channels are always required between IP and non-IP endpoints. They are freely
available, i.e. they are always used wherever they happen to be needed. The figure
below gives an overview of the cases where VoIP channels are needed and how many
of them

46 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

Tab. 18 Required VoIP channels between two possible endpoints

Master

1 VoIP channel
Non-IP endpoint IP endpoint

Direct switching: No VoIP channel

No VoIP channel Indirect switching: 2 VoIP channels

Non-IP endpoint IP endpoint

2 VoIP channels 1 VoIP channel

Satellite

Non-IP endpoint

No VoIP channel

Non-IP endpoint

Non-IP endpoints: IP endpoints

• Analogue terminal (FXS) • IP system phone
• Digital system terminal (DSI) • Mitel SIP terminal
• DECT cordless phone (DSI) • Standard SIP terminal
• ISDN phone (BRI-S) • DECT cordless phone via SIP-DECT
• External via analogue exchange (FXO) • WiFi cordless phone via SIP-DECT
• External via ISDN exchange (BRI-T/PRI) • WiFi cordless phone via SIP access point
• Internal voice mail system • WiFi mobile phone via MMC controller
• Auto attendant • External via SIP provider
• Internal announcement service IP endpoints on satellites:
• Music on hold In normal operation all IP endpoints are registered with the
• Conversation recording master, even if they are located on the satellite.
• Announcement with audio file
• Queue with announcement
• Conference bridge

Mitel 415/430 as of R4.1 47

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

Standard Media Switch modes of operation

The operation mode of the integrated standard media switch is defined with the VoIP
mode parameter in the Media resources ( =ym) view. The configured mode is al-
ways valid for the entire node.

Tab. 19 Integrated Standard Media Switch modes of operation

VoIP mode Explanation Licences
No VoIP No VoIP channels can be configured.
G.711 Although more voice channels are available Two VoIP channels per system can be used
per DSP in mode G.711 than in hybrid mode, without a licence. One VoIP Channels for
the volume of voice data is greater and Standard Media Switch licence is required
requires a greater bandwidth. for each additional VoIP channel.
G.711/G.729 The VoIP hybrid mode G.711/G.729 handles One VoIP Channels for Standard Media
both G.711 and G.729 for coding voice data. Switch licence is required for each VoIP
channel.
Secure G.711 Same as G.711 but with a more secure data One VoIP Channels for Standard Media
transmission using the SRTP protocol. Switch licence is required for each VoIP
channel. The Secure VoIP licence, valid
right across the system, is also required.
Secure G.711/G.729 Same as G.711/G.729 but with a more One VoIP Channels for Standard Media
secure data transmission using the SRTP Switch licence is required for each VoIP
protocol. channel. The Secure VoIP licence, valid
right across the system, is also required.

Reserving audio channels

The allocation of audio channels between voice mail, auto attendant, call recording
and announcements is set in the general voice mail settings ( =u1).
An audio channel is always used for Auto attendant when an incoming call triggers
greetings from mailboxes which are assigned an Auto Attendant profile. Audio chan-
nels of auto attendant are also used for queues with announcement. In all other cases
one audio channel is used for voice mail in connection with the voice mail system.
Audio channels for call recording are used exclusively for the manual or automatic re-
cording of phone calls.
Audio channels for announcements are used if the announcements have audio files.
No audio channels are required for normal announcements by phone.
If no audio channel is reserved for any of the functions described above, or if all re-
served audio channels are already used, audio channels from the Non-re-
served/shared pool are used.
No audio channels can be reserved for conference bridges. Audio channels from the
Non-reserved/shared pool are always used for the conference bridge.
Announcement service and music on hold use their own resources.

48 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

Tab. 20 Reserving audio channels

Parameter Explanation
Available audio channels Maximum available audio channels on this node. This value
depends on the configuration of the media sources.
Reserved for Auto-Attendant Number of audio channels on this node used for auto atten-
dant and queue with announcement only.
Reserved for voice mail Number of audio channels on this node that can be used
exclusively for voice mail.
Reserved for call recording1) Number of audio channels on this node that can be used
exclusively for call recording.
Reserved for announcements Number of audio channels on this node that can be used
exclusively with audio file.
Non-reserved/shared Number of audio channels on this node which can be used
by voice mail, auto attendant, queue with announcement,
call recording, announcement with audio file or conference
bridge, depending on how they are needed at that time.
Announcement service and music on hold use their own
resources.
1) Note for Voice mail mode = Extended (G.729 only): For each audio channel reserved for call recording, the
number of possible audio channels reserved for voice mail is reduced by 3. The possible combinations of
voice mail/call recoding are as follows: 12/0, 9/1 and 6/2.

No audio channels are reserved after a first start and they can be used for voice mail,
auto attendant, call recording or announcement.

Voice-mail system modes of operation

The voice mail system mode of operation is set in the Media resources ( =ym) view
using the Voice mail mode parameter. The configured mode is always valid for the en-
tire node.

Tab. 21 Voice-mail system modes of operation

Voice mail mode Explanation Licences
Normal (G.711 or G.729) The Normal (G.711 or G.729) hybrid Two voice mail channels are available
mode handles both audio formats; how- with the Enterprise Voice Mail licence.
ever, the number of audio channels per Each additional voice mail channel
node is limited to 4. requires an additional Audio Record &
Play Channels licence.
Expanded (G.729 only) In Expanded (G.729 only) mode there Two voice mail channels are available
are more audio channels available per with the Enterprise Voice Mail licence.
node than in hybrid mode. However the Each additional voice mail channel
quality of the audio data is somewhat requires an additional Audio Record &
poorer as a result of the compression. Play Channels licence.

Configuration of DSP chips

The functions which can be allocated to each DSP chip are determined in the Media
resources ( =ym) view. The DSP modules provide additional functions as indicated in

Mitel 415/430 as of R4.1 49

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

the following table. All the possible combinations are listed, with the maximum number
of channels.

Tab. 22 Max. number of channels per DSP chip on SM-DSPX1 or SM-DSPX2

DECT VoIP1) FoIP Audio1) GSM1) CAS2) Remarks
8 2
8 8
6 4
6 2 8
4 4/6 8 6 channels if Voice mail mode = Expanded (G.729 only)
4 6 30
4 8 Only if Voice mail mode = Expanded (G.729 only)
4 2 2 8
5...8 Depends on the parameter VoIP mode:
• G.711: 8 channels
• Secure G.711: 7 channels
• G.711/G.729: 6 channels
• Secure G.711/G.729: 5 channels
4 2 30
4 4 Only for VoIP mode = G.711 or G.711/G.729
4 2 8 Only for VoIP mode = G.711 or G.711/G.729
3 1/2 1 channel for Mitel 415
2 channels for Mitel 430
12 8 Only if Voice mail mode = Expanded (G.729 only)
12 30 Only if Voice mail mode = Expanded (G.729 only)
1) Licence(s) required (see also "Licences", page 62).
2) Of relevance only to certain countries such as Brazil

Tab. 23 Max. number of channels per DSP chip on SM-DSP11) or SM-DSP21)

DECT VoIP1) FoIP Audio1) GSM1) Remarks
8 8
6 2 8
4 4/6 8 6 channels if Voice mail mode = Expanded (G.729 only)
4 8 Only if Voice mail mode = Expanded (G.729 only)
4/8 4 channels if VoIP mode =G.711/G.729
8 channels if VoIP mode = G.711
2 4
12 8 Only if Voice mail mode = Expanded (G.729 only)
1/2 1 channel for Mitel 415
2 channels for Mitel 430
1) Licences required (see also "Licences", page 62).

1) Although no longer available, the module is still supported.

50 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

Notes
– To configure VoIP channels on the DSP chip of a DSP module, make sure the VoIP mode
parameter in the Media resources ( =ym) view is not set to No VoIP. The setting is valid
for all the DSP chips of a node. If VoIP mode is set to G.711, two G.711 VoIP channels per
system can be used without a licence. The G.711 VoIP channels of the mainboard can be
combined with G.711 VoIP channels of DSP modules.
– If audio channels are configured and licensed, the two basic audio channels that can be
used without a licence are redundant (see Tab. 15).
– Audio channels and FoIP channels can only be configured on one DSP chip per node.
– The Modem function is used for remote maintenance via an analogue modem and can only
be configured on the mainboard’s DSP.
– The system has to be restarted for the configuration changes of the DSP to take effect.
– After a first start all the DSP chips are configured on DECT.

3. 3. 2 Interface cards
Interface cards can be assigned to three categories:

• Trunk cards
These cards provide interfaces for connection to public dial-up networks or for net-
working systems to create a private telephony network.
• Terminal cards
These cards provide interfaces for connecting digital and analogue voice and data
terminals.
• Options cards
This category comprises the ODAB card, the interfaces for connecting a door inter-
com, for controlling external devices, and for switching over internal switch groups.

On some cards some of the interfaces are configurable (BRI-S/T). This means that
these cards cannot be clearly assigned to any particular category. They are listed both
among the trunk cards and the terminal cards.
Interface cards are fitted into slots IC1...IC4 (see Fig. 7).
The interfaces are routed to the front panel using the Wiring Adapters (see "Wiring
Adapter", page 55).
The length varies depending on the type of interface card. For precise dimensions see
the Chapter "Technical data", page 246.

Mitel 415/430 as of R4.1 51

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

Fig. 9 Design of the interface cards

3. 3. 2. 1 Trunk cards
The trunk cards contain interfaces for connection to the analogue public network
(PSTN), the digital public network (ISDN) or for networking systems to create a private
telephony network (PISN). The trunk cards can be used and operated on any slots for
interface cards.
Some trunk cards contain both network interfaces (BRI-T) and terminal interfaces
(BRI-S). On these cards the ratio of BRI-S interfaces to BRI-T interfaces is determined
by the use and plug-in orientation of the Wiring Adapters (see "Wiring Adapter",
page 98).

Note
On the ESST terminal card the jumper must always be fitted in position T (see Fig. 24).

Tab. 24 Trunk cards

Network interfaces Max. number of Max. number of
Type Remarks
per card Mitel 415 cards Mitel 430 cards
TIC-1PRI 1 × PRI 2 2 • Contains 30 B channels
• 10 B channels can be used licence-
free
TIC-4TS 3 × BRI-S/T + 1 × BRI- 2 4 • Three BRI-T interfaces configurable
T to BRI-S
• One fixed BRI-T interface
TIC-2TS 2 × BRI-S/T 2 4 • Both BRI-T interfaces configurable to
BRI-S
ESST1)2) 1 × BRI-S/T + 1 × BRI- 2 4 • One BRI-T interface configurable to
S BRI-S, one fixed BRI-S interface
• The jumper on this card must always
be fitted to position T.
TIC-4AB 4 × FXO 1 2
TIC-2AB 2 × FXO 2 4
EAAB22) 2 × FXO 2 4
1) Cards with hardware version "-2" only. The ESST-1 card is not operational in Mitel 415/430.
2) Although no longer available, the card is still supported.

52 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

3. 3. 2. 2 Terminal cards
Terminal cards are used for connecting digital and analogue voice and data terminals
such as:
FXS cards are an exception. Their analogue interfaces are multifunctional. In addition
they provide interfaces for controlling external devices and switching over internal
switch groups. Depending on the terminal or function, the interfaces are configured in-
dividually and switched over internally accordingly (see "Multifunctional FXS inter-
faces", page 127).
DSI cards are used for connecting digital system terminals such as phones. 2 terminals
can be connected to each DSI interface.
Terminals to ETSI standard are connected via BRI cards. The cards contain both termi-
nal interfaces (BRI-S) and network interfaces (BRI-T). On these cards the ratio of BRI-
S interfaces to BRI-T interfaces is determined by the type and plug-in orientation of the
Wiring Adapters (see "Wiring Adapter", page 98).

Tab. 25 Terminal cards

Terminal inter- Max. number of Max. number of
Type Remarks
faces per card Mitel 415 cards Mitel 430 cards
EADP4 4 × DSI 2 4
EAD4V1) 4 × DSI 2 4 • Voice mail functionality of the card can-
not be used
• Cannot be fitted to slot IC4 on Mitel 430
EAD4C1) 4 × DSI 2 4 • Announcement service functionality of
the card cannot be used
• Cannot be fitted to slot IC4 on Mitel 430
ETAB4 4 × FXS 2 4 • Interfaces individually configurable
TIC-4TS 3 × BRI-S/T 2 4 • Three BRI-S interfaces configurable to
1 × BRI-T BRI-T
• One fixed BRI-T interface
TIC-2TS 2 × BRI-S/T 2 4 • Both interfaces configurable to BRI-T
ESST1)2) 1 × BRI-S/T 2 4 • One BRI-S interface configurable to
1 × BRI-S BRI-T, one fixed BRI-S interface
• The jumper on this card must always be
fitted to position T.
1) Although no longer available, the card is still supported.
2) Cards with hardware version "-2" only. The ESST-1 card is not operational in Mitel 415/430.

Note
On the ESST terminal card the jumper must always be fitted in position T (see Fig. 24).

Mitel 415/430 as of R4.1 53

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

3. 3. 2. 3 Options card
The ODAB options card contains control outputs, control inputs and an analogue termi-
nal circuit for connecting a door intercom (TFE). The I/Os of the options card are partly
configurable and can be used for the following purposes:

• The control outputs are used to switch any external devices or equipment. Any au-
thorized user can operate the control ouputs.
• Floating contacts are connected to the control inputs. This means that the con-
nected control inputs can control switch group positions.
• Connection of a door intercom (TFE):
– Bell input, which can be configured to any internal destination depending on the
position of a switch group.
– Door intercom system, which can be dialled using a separate number and oper-
ated via a phone by any authorized user.
– Door opener, which can be activated via a phone by any authorized user.
– Input for feeding the voice path (switching the door intercom on/off).

Tab. 26 Options card

Control outputs Analogue terminal circuit for Max. number of Max. number of
Type
or control inputs connecting a door intercom Mitel 415 cards Mitel 430 cards
ODAB 41) 1 1 2
1) 1 control output or 1 control input is available in the configuration as a door intercom. If the option card is
used for other purposes, 2 control outputs and 2 control inputs can be used.

Note
If the options card is used to connect a door intercom, it must be fitted to slot IC2 (Mitel 415) or
slot IC4 (Mitel 430). This means that only one options card can be used for this purpose on
each communication server. If using control outputs and control inputs only, use the slots IC1
slots (Mitel 415) or IC1, 2 and 3 (Mitel 430).

Mitel Advanced Intelligent Network:

A total of 22 ODAB options cards can be used in an AIN with Mitel 430 as Master. However the
maximum number of cards per communication server has to be taken into account. An author-
ized user has the possibility of operating all the door openers, door intercom system and control
outputs in an AIN. One of the switch groups can be switched over using the switch group inter-
face on the options cards.

54 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

3. 3. 3 Wiring Adapter
The wiring adapters route the interfaces of the various interface cards with the right
connection diagram to the RJ45 sockets on the front panel. The adapters are fitted to
WA1...WA4 sockets.

:$76 :$76 :$: :$35,

Fig. 10 Types of wiring adapters

There are four types of wiring adapters, of which two (WA-TS0 and WA-TS1) have dif-
ferent plug-in orientations. This determines the ratio of BRI-S interfaces to BRI-T inter-
faces.

Note
A configuration with wiring adapter is mandatory. An incorrect or missing configuration gener-
ates the corresponding error display on the LED display (F1...F4).

Tab. 27 Wiring Adapter

Type Use with... Remarks
WA-TS0 TIC-4TS, TIC-2TS, ESST1) Included in the equipment supplied with TIC-
4TS and TIC-2TS
WA-TS1 TIC-4TS, TIC-2TS, ESST1), ODAB Included in the equipment supplied with ODAB
WA-2W Mainboard interfaces, TIC-4AB, TIC-2AB, Included in the equipment supplied with TIC-
ETAB4, EAAB2, EADP4, EAD4C, EAD4V 4AB, TIC-2AB, ETAB4 and EADP4 (with
ETAB4 and EADP4 only with order variant
Mitel 415/430).
WA-1PRI TIC-1PRI Included in the equipment supplied with TIC-
1PRI
1) On the ESST terminal card the jumper must always be fitted in position T (see Fig. 24).

The assignment to the RJ45 sockets depending on the Wiring Adapters is shown in
Tab. 36.

Mitel 415/430 as of R4.1 55

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

3. 4 System capacity
System capacities are defined on the one hand by the existing hardware with its ex-
pansion possibilities and on the other by the limits set in the software. The software lim-
its can be partly expandable by licences.

3. 4. 1 Media resources

3. 4. 2 General system capacity

The number of slots, interface cards and system modules per communication server
have already been mentioned in the previous chapters and are not listed separately in
this chapter.

Tab. 28 General system capacity

AIN with
Max. number... Mitel 415 Mitel 430 Mitel 430 as
Master
Nodes in a transparent network (AIN) – – 11
Nodes with SIP networking 100 100 –
Users 121) 502) 502)
Terminals per user3) 16 16 16
Simultaneous connections
• Without IP and without DECT (internal / external) 104) 30 50
• IP – not IP (internal / external) 8 18 50
• IP – IP (internal) 64) 254) 50
• IP – IP via SIP access channels (external) 12 32 32
• DECT – not DECT (internal / external) 104) 20 per node
• DECT – DECT (internal) 54) 20 per node
5)
Voice channels VoIP (Standard Media Switch) ) 8 18 per node
Audio channels, call recording 2 2 per node6)
7)
audio channels in Normal (G.711 or G.729) voice mail mode 4 4 per node
audio channels in Extended (G.729 only) in total 7) 12 12 per node
voice mail mode
Voice channels FoIP (T.38) 1 2 per node
CAS transmitter/receiver for PRI network interfaces8) 60 60 per node
Configurable conference bridge 24 24 24
Active conferences see Tab. 15
Trunk group 200 200 200
Trunk groups in route 8 8 8
Network interfaces per trunk group 8 8 8
Routes 1369) 1369) 1369)

56 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

AIN with
Max. number... Mitel 415 Mitel 430 Mitel 430 as
Master
B channel groups 200 200 200
SIP provider 10 10 10
SIP user account 500 500 500
Direct dialling plans 10 10 10
Total DDI numbers 500 500 500
Call distribution elements 500 500 500
Queue with announcement 8 8 8
User groups 21 21 21
Members per trunk group "normal" 810)/16 810)/16 810)/16
Members per user group "large" 20 100 100
Abbreviated dialling numbers + PISN users 1500 1500 1500
Line keys per key telephone (except Mitel 6700 SIP / 6800 SIP) 39 39 39
Line keys per key telephone on Mitel 6700 SIP / 6800 SIP 2...1211) 2...1211) 2...1211)
Line keys per CDE on Mitel 6700 SIP / 6800 SIP 812) 812) 812)
Total line keys on Mitel 6700 SIP / 6800 SIP see 13) see 13) see 13)
Switch groups 20 20 20
Positions per switch group 3 3 3
Hotline destinations 20 20 20
Emergency destinations 50 50 50
Emergency numbers 10 10 10
Allocations of external call numbers to internal call numbers 50 300 300
External digit barring 8 8 8
Internal digit barring 8 8 8
Predefined text messages 16 16 16
Announcement / message groups 16 16 16
User per announcement / message group 16 16 16
Data service tables 8 8 8
User accounts for user access control 25 25 25
Authorization profiles for user accounts 25 25 25
Log entries per user account 20 20 20
First-party CTI users via LAN 10 32 32
First-party CTI users via Mitel Dialer 10 32 32
Third-party CTI interfaces 1 1 1
Third-Party CTI interface (Basic, Standard) 10 50 50
Groups, Agents (OIP Call centre) 10 30 50
Mailboxes with Basic or Enterprise voice mail system 20 100 100
Greetings per mailbox 3 3 3
Profiles per mailbox for auto attendant 3 3 3

Mitel 415/430 as of R4.1 57

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

AIN with
Max. number... Mitel 415 Mitel 430 Mitel 430 as
Master
Backup communication servers for Dual Homing 50 50 50
Primary communication servers for Dual Homing 50 50 50
Blacklist 1 1 1
Call number entries in the blacklist 1000 1000 1000
Number of CLIP based routing tables 10 10 10
Total call number entries in call distribution tables 250 250 250
Call data memory internal (number of records)14) 300 300 300
Private contacts 8000 8000 8000
Call list entries for each of the 3 call lists per phone 30 30 30
Total call list entries 15000 15000 15000
Configured keys 4000 4000 4000
Busy lamp field keys on Mitel SIP phones in total 200 200 200
Busy lamp field keys per Mitel SIP phone 50 50 50
Same users on busy lamp field keys on Mitel SIP phones 10 10 10
Expansion key modules on DSI terminals 304) 60 100
Expansion key modules on IP system phones 304) 60 100
Expansion key modules Mitel M670, Mitel M675, Mitel M680, 304) 60 100
Mitel M685
Alpha keyboardMitel K680 10 50 50
Alpha keyboard (AKB) 10 40 50
1) Up to 20 users are possible with virtual terminals and integrated mobile/external phones.
2) Up to 100 users are possible with virtual terminals and integrated mobile/external phones.
3) Only 1 operator console, 1 MiVoice 2380 IP, 1 BluStar 8000i , 1 Mitel BluStar for PC, 1 Mitel SIP-DECT and
2 DECT- cordless phones are possible for each user.
4) Limited by the maximum number of terminals
5) In the Secure VoIP modes the maximum values cannot be achieved with the selection i the DSP settings:
Mitel 415: Secure G.711 VoIP mode: 1 7 = 7 channels, VoIP mode Secure G.711/G.729: 1 × 5 = 5 channels.
Mitel 430: Secure G.711 VoIP mode: 2 7 = 14 channels, VoIP mode Secure G.711/G.729: 3 × 5 = 15 chan-
nels.
6) For IP-IP connections maximum 8
7) Audio channels can be used for voice mail, auto attendant, queue with announcement, call recording, an-
nouncement with audio file, or conference bridge. Announcement service and music on hold use their own
resources.
8) Of relevance only to certain countries such as Brazil
9) 12 of them are masked (not configurable)
10)With global call distribution
11)Depending on the phone type
12)The value applies to CDE with destination KT line. With MiVoice Office 400 multiple destinations (User + KT
or KT + UG) the value is reduced to 4.
13)Depending on the highest number of line keys, configured for the same line. The following pairs apply (line
keys per line / total line keys): (8/24), (7/28), (6/36), (5/50), (4/60), (3/60), (2/60), (1/60).
14)The call data memory is only used if the output destination is blocked (e.g. printer jam).

58 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

3. 4. 3 Terminals
Tab. 29 Maximum number of terminals per system and interface
AIN
per
Inter- Mitel Mitel with
Terminal type Terminal inter-
face 415 430 430 as
face
Master
Miscella- Terminals (including virtual terminals and integrated 20 100 100
neous mobile/external phones)
Miscella- Terminals (excluding virtual terminals and integrated 121) 50 50
neous mobile/external phones)
DSI Terminals on DSI interfaces (total) 10 40 50
DSI Digital system phones MiVoice 5360 10 40 50 2
MiVoice 5361
MiVoice 5370
MiVoice 5380
Office 10
Office 25
Office 35
Office 45
DSI Operator consoles / operator applica- MiVoice 5380 4 8 16 2
tions MiVoice 1560
Office 45
DSI Cordless system SB-4+ radio unit 10 20 32 1
2)
DSI Cordless system SB-8 / SB-8ANT radio 5 10 32
units
DECT Cordless phones Mitel 610/612 DECT 10 50 50
Mitel 620/622 DECT
Mitel 630/632 DECT
Mitel 650 DECT
Office 135
Office 160
GAP terminals

Mitel 415/430 as of R4.1 59

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

AIN
per
Inter- Mitel Mitel with
Terminal type Terminal inter-
face 415 430 430 as
face
Master
LAN Terminals on LAN interfaces (total) 121) 50 50
LAN DHCP clients on the internal DHCP server 50 50 50
LAN IP terminals MiVoice 2380 IP 12 50 50
MiVoice 5360 IP
MiVoice 5361 IP
MiVoice 5370 IP
MiVoice 5380 IP
LAN IP operator consoles / IP operator MiVoice 5380 IP 4 8 16
applications MiVoice 1560
LAN Mitel SIP terminals Mitel 6863 SIP 10 50 50
Mitel 6865 SIP
Mitel 6867 SIP
Mitel 6869 SIP
Mitel 6873 SIP
Mitel 6730 SIP
Mitel 6731 SIP
Mitel 6735 SIP
Mitel 6737 SIP
Mitel 6739 SIP
Mitel 6753 SIP
Mitel 6755 SIP
Mitel 6757 SIP
LAN Mitel SIP-DECT Cordless phones 10 50 50
LAN Standard SIP terminals 10 50 50
LAN Mitel BluStar 8000i 10 50 50
LAN Mitel BluStar Softphones 10 50 50
LAN Mitel Mobile Client Controller 10 10 10
– Virtual terminals 20 100 100
– Integrated mobile/external phones 20 100 100
– Integrated mobile/external phones (with or without MMC) 10 50 50
– Integrated mobile phones per MMCC Compact 10 50 50
– Integrated mobile phones per MMCC 130 10 50 100
BRI-S Terminals on DSI-S interfaces (total) 10 50 50 83)
BRI-S Terminals as per ETSI standard 10 50 50
• ISDN terminals
• ISDN PC cards
• ISDN LAN routers
• ISDN Terminal Adapters
FXS Terminals on FXS interfaces (total) 10 18 50 1

60 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

AIN
per
Inter- Mitel Mitel with
Terminal type Terminal inter-
face 415 430 430 as
face
Master
FXS Analogue, nationally approved terminals 10 18 50
• Pulse dialling (PUL)
• Frequency dialling (DTMF)
• Radio units for cordless phones
• Door intercoms with DTMF control functions
• Group 3 fax machines4)
• Answering machines
• Modems
FXS External equipment can be switched via control outputs 1 1 1
FXS External switches for controlling internal switch groups via con- 10 18 50
trol inputs
FXS General bell 1 1 1 per
node
1) Of which at least 2 are IP system phones
2) Operation on 2 DSI interfaces in each case
3) Maximum of 2 simultaneous call connections.
4) Transmission with the T.38 protocol is recommended for Fax over IP. The corresponding media resources
need to be allocated.

3. 4. 4 Terminal and network interfaces

Tab. 30 Terminal and network interfaces
AIN with
Max. number... Mitel 415 Mitel 430 Mitel 430 as
Master
Ethernet interfaces 2 2 per node
Network interfaces, total (FXO, BRI-T, PRI, BRI-Sext.) 4 8 20
Terminal interfaces, total (DSI, FXS, BRI-S) 12 22 50
DSI terminal interfaces 101) 201) 50
Analogue terminal interfaces FXS 101) 181) 50
BRI-S terminal interfaces 61) 121) 64
Door intercom (with ODAB card) 1 1 11
Analogue network interfaces FXO 4 8 20
Basic connections, total (BRI-T, PRI, BRI-Sext.) 4 8 20
Primary rate interfaces PRI2) 2 4 20
SIP access 10 10 10
SIP access channels3) 16 32 32
1) In maximum expansion network access is possible only via IP
2) 30 B channels per PRI network interface, of which 10 B channels each can be used without licence.
3) Licences required

Mitel 415/430 as of R4.1 61

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

3. 4. 5 Software assurance
Software Assurance (SWA) is Mitel’s comprehensive support offer which gives access
to new software releases, support services and SRM remote access to the communi-
cation server.
The software assurance agreement has a fixed runtime and defines the number of au-
thorised users on the communication system. You can see at a glance whether a valid
(active) SWA is available for the communication server, via the SWA state in the
WebAdmin title bar.
The SWA state is retrieved via an encrypted direct link on the licence server. If there is
no connection to the licence server, the last known state is displayed
The number of users covered via SWA and the number of configured users can be
seen in the System information ( =1v) view. SWA becomes invalid if the number of
configured users exceeds the number of users covered via SWA . Each entry in the
User category counts as configured user in the numbering plan ( =g4).

3. 4. 6 Licences
Use of the call manager software requires a licence. Additional licences are required in
order to use a number of enhanced functions and protocols, to enable voice channels
or to operate certain terminals. The Mitel CPQ application automatically plans the nec-
essary licences, which are then enabled on the communication server using a licence
code.
The licence code (LIC) contains all the enabled licences. When you purchase a new li-
cence from your authorised dealer, you obtain a new licence code in return. Enter this
in WebAdmin and store it in the communication server in the Licences ( =q9) view.

Notes:
– A licence code is not transferable to another communication server.
– If you receive a voucher instead of a licence code, log on with your partner login at
Mitel Connect https://connect.mitel.comand generate the licence code yourself using the
EID number. Detailed instructions about this can be found in the WebAdmin help on the
Licences ( =q9) view.

62 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

3. 4. 6. 1 Description of available licences

Software

• Software Release
Updating to a new software release requires a licence. A valid software assurance
(SWA) entitles you to upgrade the communication server to a new software level for
a specific period., and to operate it with a specific number of users.
A valid software assurance is the prerequisite for being able to acquire an update li-
cence (Software Release licence) for a particular software version. Without a valid
Software Release licence you can update the communication server to a new soft-
ware level, but after four hours of operating time it will switch over to the restricted
operating mode (see "Restricted operating mode", page 71). The communication
server will switch back to normal operation as soon as you enter a licence code that
comprises the Software Release licence. You do not need to restart the communica-
tion server.

Note:
The purchase of a new communication server also includes a software assurance for a spe-
cific period. Log on with your partner login to Mitel Connect https://connect.mitel.com and
obtain a new licence code using the EID number and the voucher. The licence code issued
as a result contains the appropriate Software Release licence (and any other licences you
may have acquired). You can now activate the communication system with this licence
code. Detailed instructions about this can be found in the WebAdmin help on the Licences
( =q9) view.

Mitel Advanced Intelligent Network

In an AIN, a valid Software Release licence must be available on the master only. Exception:
For long-term offline mode, for operation with Secure VoIP and use as backup communica-
tion server, the satellite must also have a valid Software Release licence.
– Behaviour of satellites in online mode:
Although satellites must also have a release licence, they must not necessarily match
the current software status. If satellites do not have any release licence, they restart
every four hours.
– Behaviour of satellites in offline mode:
Satellites with an incorrect release licence change over to restricted operating mode
after thirty-six hours. Satellites without any release licence change over to restricted
operating mode after four hours.

Users

• Basic User (licence bundle)

This licence bundle contains any phone licence and is explicitly assigned to a user.
This allows the user to change the phone type without having to change the licens-
ing.

Mitel 415/430 as of R4.1 63

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

• The following three UCC licence bundles contain any eight phone licences, video li-
cences for all phones licensed together, ten SIP Terminals licences for MiCollab
AWV, the Enterprise Voice Mail licence and activates MiCollab functions for the cor-
responding MiCollabrole. With a specific number of UCC licence bundles more ter-
minal licences (SIP Terminals) as well as voice mail licences (Enterprise Voice Mail
Channels) are added.
– Entry UCC User
This licence bundle contains the licences described in the above section and ac-
tivates MiCollab functions for the MiCollab role UCC Entry. The licence is explic-
itly assigned to a user.
– Standard UCC User
This licence bundle contains the licences described in the above section and ac-
tivates MiCollab functions for the MiCollab role UCC Standard. The licence is ex-
plicitly assigned to a user.
– Premium UCC User
This licence bundle contains the licences described in the above section and ac-
tivates MiCollab functions for the MiCollab role UCC Premium. The licence is ex-
plicitly assigned to a user.

Terminals

• MiVoice 2380 IP Softphones

One licence per terminal is required to operate the IP softphones MiVoice 2380 IP.
The licences are needed to register the terminals on the system.
• MiVoice 5300 IP Phones
One licence per terminal is required to operate the IP system phones
MiVoice 5360 IP, MiVoice 5361 IP, MiVoice 5370 IP and MiVoice 5380 IP. The li-
cences are needed to register the terminals on the system. If the required licences
are missing, the relevant event message is output on the system. The licences can
also be used if the Mitel SIP Terminals licences are missing (but not the other way
round).
• Mitel SIP Terminals
To operate Mitel SIP terminals of the Mitel 6700 SIP / 6800 SIP series, for Mitel
BluStar 8000i Desktop Media Phone, for cordless terminals logged on via Mitel SIP-
DECT or Mitel SIP WLAN base stations, one licence is required per terminal or user.
The licences are needed when registering the terminals or the user on the system. If
the licences are missing, Mitel SIP terminals can also be operated with SIP Termi-
nals or MiVoice 5300 IP Phones licences (but not the other way round).
• Mitel 8000i Video Options
To use the video functions of a Mitel BluStar 8000i Desktop Media Phone or Mitel
BluStar for Conference Room, in addition to the Mitel SIP Terminals licence, you
need to also purchase a Mitel 8000i Video Options licence. The two licences are

64 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

needed to register the terminals on the system. Use is not possible if Video Termi-
nals licences are missing.
• Mobile or External Phone Extension
With this licence it is possible to integrate mobile phones or other external phones
into the communication system. One licence has to be purchased for each phone.

Note:
This licence does not allow comfortable integration with the Mitel Mobile Client application.
• MMC Extension
With this licence mobile phones can be integrated into the communication system
together with an Mitel Mobile Client Controller and Mitel Mobile Client. The MMC
Controller allows mobile users to move back and forth between the internal WLAN
coverage and the mobile radio network without the call being interrupted.
• SIP Terminals
One licence is required per terminal to operate standard SIP terminals. The licences
are needed when registering the terminals on the system and can be used even if
Mitel SIP Terminals licences are missing (but not the other way round).
• Video Terminals
To be able to use the video functionality of a standard SIP video terminal you need
to acquire a Video Terminals licence in addition to a SIP Terminals licence. The li-
cences can also be used if the Mitel 8000i Video Options licences are missing.
• Dual Homing
In the event of failure of the primary communication server or an interruption in the
IP connection to the primary communication server, SIP phones in the
Mitel 6700 SIP / 6800 SIP series can automatically register on a backup communi-
cation server. On the backup communication server one licence is required per
phone. The licences are needed to register the clients on the system.

BluStar

• BluStar Softphones
This is a BluStar client licence. One licence per client is required to operate BluStar
softphones. The licences are needed to register the clients on the system.
• BluStar Softphone Video Options
This licence is required for using the video functionality of a BluStar softphone. A
BluStar client licence must be in place.

Audio services

• Conference Bridge
This licence allows the use of a conference bridge. The internal or external confer-

Mitel 415/430 as of R4.1 65

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

ence participants choose a specific call number and are connected with the confer-
ence after entering a PIN. One licence is required per system /AIN.
• Enterprise Voice Mail
If the functionality of the basic voice mail system is insufficient, the voice mail sys-
tem can be expanded. This licence provides two audio channels for recording or
playing back audio data for voice mail, auto attendant or call recording. The licence
also increases the voice memory capacity and allows e-mail notification whenever
new voice messages are received as well as the forwarding of voice messages and
call recording.

Notes
– Additional audio channels require additional Audio Record & Play Channels licences. An
Auto Attendant licence is required to use the auto attendant function.
– In a VoIP environment VoIP channel licences are also required for converting the voice
data when using the internal voice mail system.
• Audio Record & Play Channels
This licence enables an additional audio channel for recording or playing back audio
data for voice mail, auto attendant or call recording. This licence can only be used in
conjunction with the Enterprise Voice Mail licence.

Mitel Advanced Intelligent Network

In an AIN the Enterprise Voice Mail and Audio Record & Play Channels licences are all
acquired for the Master. The number of Audio Record & Play Channels licences determines
the maximum number of simultaneously active audio channels, regardless of the nodes on
which they are currently being used. Requirement: The media resources on each node must
be available and allocated accordingly.
• Auto Attendant
This licence enables the use of the auto attendant function and is independent of
the Enterprise Voice Mail licence. It means it can also be used in conjunction with
basic voice mail. One licence is required per system /AIN.

Note
In a VoIP environment VoIP channel licences are also required for converting the voice data
when using the auto attendant.
• Number in Queue
This licence is required for using the functionality of "Queue with announcement".
The Auto Attendant licence is required here. One licence is required per system
/AIN.

Features

• Secure VoIP
This licence allows encrypted VoIP connections with the aid of SRTP (Secure Real-
Time Transport Protocol) and TLS (Transport Layer Security).

66 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

Mitel Advanced Intelligent Network

For legal reasons (Trade Control Compliance) in an AIN a Secure VoIP licence is required
for both the Master and for each satellite.
• Silent Intrusion
This licence is needed for the Silent intrusion feature, which is similar to the Intru-
sion feature. The difference is that the user intruded upon receives neither a visual
nor an acoustic signal of the intrusion. The feature is used mainly in call centres.
One licence is required per system /AIN.
• Analogue Modem
This licence allows remote maintenance of an Mitel 415/430 using an analogue mo-
dem. For this the Modem function must be allocated to the mainboard DSP. Trans-
mitting event messages via an analogue modem is also possible.

Mitel Advanced Intelligent Network

In an AIN the licence is always acquired on the Master. The licence allows the remote main-
tenance of the AIN via any Mitel 415/430 node.
Note: The master node can also be of Mitel 470 or Virtual Appliance type.

Resources

• VoIP Channels for Standard Media Switch

Note:
This licence is required for Mitel 415/430 and Mitel 470 only. For Virtual Appliance, the VoIP
channels of the integrated Mitel Media Server are made available and do not require any
licences.
This licence enables the conversion of voice channels for VoIP-non-VoIP connec-
tions and is used for IP terminals, SIP terminals, SIP access channels or to operate
an Mitel Advanced Intelligent Network. High voice data compression is possible with
the G.729 VoIP channels. An additional voice channel is activated with each licence.

Notes:
– If VoIP mode is set to G.711, two G.711 VoIP channels per system can be used without a
licence.
– Theoretically there are no VoIP channel licences in a pure VoIP environment (only IP/SIP
phones on the system and connection to the public network via an SIP provider). How-
ever, as soon as voice mail functions, the announcement service or music on hold is
used, VoIP channel licences are required as the use of these functions entails a conver-
sion of the voice data.

Mitel Advanced Intelligent Network

In an AIN the licence can also be used for the connections between the nodes. Two VoIP
channel licences are required for each node connection. The licences are always acquired
for the Master. The number of licences determines the maximum number of simultaneously
active conversions, regardless of the nodes on which they are currently being used.
Requirement: The media resources on each node must be available and allocated accord-
ingly.

Mitel 415/430 as of R4.1 67

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

If Virtual Appliance is used as Master, the VoIP channels of the master node are made avail-
able without a licence from the integrated Mitel Media Server. However, for the satellites'
VoIP channels, the licences must be purchased.
• G.729 Codec
This licence allows the use of a G.729 codec for the voice channel of Mitel SIP
phones, IP system phones and SIP network interfaces (also for SIP networking).
The licences are always used wherever they are required. Mitel SIP-DECT and
standard SIP terminals do not require this licence. Likewise, calls to the emergency
number do not require a licence.

Note
If several emergency destinations are defined in a system, the following points need to be
considered:
– Sufficient G.729 Codec licences must be available.
– No phone and no SIP network interface is configured exclusively to G.729 Codec.

Networking

• B-Channels on PRI Cards

Ten B-channels can be used without licences for each PRI interface. These chan-
nels cannot be transferred to other PRI interfaces. An additional channel is acti-
vated with each licence. These licences are in a pool and are used from any PRI in-
terface, if necessary (per call) .

Mitel Advanced Intelligent Network

In an AIN the licence is always acquired on the Master. For each licence an additional B
channel is available on a PRI interface of any node, depending on where the B channel is
currently being used.
• SIP Access Channels
The connection of the system to a SIP service provider or the networking of the sys-
tems via SIP requires one licence per channel.

Mitel Advanced Intelligent Network

In an AIN all the SIP licences are always acquired for the Master. The number of licences
determines the maximum number of simultaneously active voice channels, regardless of the
nodes on which they are currently being used. Requirement: The media resources on each
node must be available and allocated accordingly.
• Lync Option for SIP Access Channels
This additional licence enables the use of a SIP access channel with Lync-specific
options and features. It is required for each channel in addition to a SIP Access
Channels licence.

Private networking

• QSIG Networking Channels

These licences are used to implement a private leased-line network with QSIG by

68 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

enabling a specific number of simultaneously outgoing QSIG channels. Two licence

levels are available (see Tab. 31).
Note: For Virtual Appliance this licence is only relevant to the QSIG networking of an
AIN satellite.
• Base Mitel AIN
This licence allows a Mitel Advanced Intelligent Network to be set up and operated
with one Master and one satellite.
Note: This licence is not available for Mitel 415.
• Mitel AIN Satellites
An upgrade licence for each additional satellite is required to integrate more than
one satellite in an Mitel Advanced Intelligent Network. An existing basic AIN licence
has to be in place already.
Note: This licence is not available for Mitel 415.

Applications

• Mitel Dialer
This licence allows you to use the Mitel Dialer CTI application. The number of li-
cences determines the simultaneously active, user-assigned Mitel Dialer applica-
tions.
• Hospitality Manager
This licence allows you to use the Mitel 400 Hospitality Manager. The Mitel 400
Hospitality Manager is a web-based application for receptionists in the hospitality
sector. One licence is required per system /AIN.
• Hospitality PMS Interface and Hospitality PMS Rooms
The Hospitality PMS Interface licence is used to connect the communication server
to a hotel management system using the FIAS protocol. One licence is required per
system /AIN. Moreover, one Hospitality PMS Rooms licence is required per room.
• OpenCount licences
MitelOpenCount is a software package used for the call logging management on the
communication system. It consists for selected sectors of basic, comfort and pre-
mium solutions and is installed on an external server. The licences are stored in
MiVoice Office 400. OpenCount obtains the licences via the XML based interface
Open Application Interface.
– Mitel OpenCount Basic Package
This basic licence is a prerequisite for all OpenCount additional licences. The li-
cence contains the “Company” branch package, enables the connection to
MiVoice Office 400 and allows basic functions to be used.
– Mitel OpenCount Healthcare Branch Package
This additional licence offers extra functions for care and retirement homes.

Mitel 415/430 as of R4.1 69

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

– Mitel OpenCount Public Authorities Branch Package

This additional licence offers extra functions for municipalities, communities and
ministries.
– Mitel OpenCount Functional Upgrade to Comfort
This additional licence offers extra functions such as PIN telephony.
– Mitel OpenCount Functional Upgrade to Premium
This additional licence offers extra functions such as intermediate statements, in-
voicing etc.
– Mitel OpenCount Users
This additional licence enables a defined number of users to be monitored via
OpenCount. All OpenCount users must be licensed, otherwise a warning is gen-
erated.
• Advanced Messaging
Enables the SMPP protocol to be used for integrating an SMS server and 9d cord-
less phones to be logged on as system phones (Ascom Wireless Solutions prod-
ucts). User-friendly messaging systems can then be implemented. One licence is
required per system /AIN.
Note: This licence is not available for Mitel 415.
• CTI First Party via LAN
This basic licence enables the CTI basic functions via Ethernet interface (e.g. for us-
ing a PC dial help) for a specific number of users (see "General system capacity",
page 56). It cannot be combined with CTI third-party licences.

interfaces

• ATAS Interface / ATASpro Interface

With ATAS licences external alarm and messaging sources can be connected via
the Ethernet interface. The licences also offer additional possibilities compared with
ATPCx (e.g. displaying the Fox menu on system phones and triggering an alarm
with the Redkey).
The ATASpro Interface licence can also be used to determine the position of users
of Mitel DECT cordless phones, which can be viewed with the appropriate applica-
tions.

Note:
If you use the Mitel Open Interfaces Platform, OIP takes the licences from the communica-
tion server. So always acquire these licences for the communication server so you can use
ATAS even without OIP.
• BSS Licence
This licence allows a BluStar server to be connected.
• BSS-Lync Interface
This licence allows the use of the BluStar Lync interface.

70 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

• CSTA Sessions
This licence allows third-party applications to monitor/check a terminal on the com-
munication server using the CSTA protocol. If a terminal is monitored or checked by
several applications or instances, one licence is required for each monitoring/check.
• Presence Sync. via SIMPLE and MSRP
SIMPLE (Session Initiation Protocol for Instant Messaging and Presence Leverag-
ing Extensions) is a protocol for exchanging presence information, and is used be-
tween SIP endpoints (terminals, network interfaces and nodes). MSRP (Message
Session Relay Protocol) is a protocol used for exchanging data between SIP clients
(e.g. for chats). This combined licence defines the number of users who can use
one or both protocols for third-party applications. Only one licence is needed for a
user with several SIP phones.
• SMPP
This licence allows the use of the SMPP protocol. The licence cannot be purchased
individually but is part of the Advanced Messaging licence.

3. 4. 7 Restricted operating mode

Without a valid Software Release licence the communication server switches over to a
restricted operating mode four hours after each restart. The restriction concerns the fol-
lowing aspects:
Restricted operating features:

• No call information for incoming calls and during the call connection.
• Dialling by name is deactivated.
• Functions cannot be invoked via the menu or function key (likewise no enquiry calls
can be made).
• The team keys do not work.
• Functions codes are not carried out (except remote maintenance on/off).
• Dialling from PC and other CTI functions are not supported.

Restricted services and routing functions:

• Calls are not routed to integrated mobile/external phones.

• Call centre functions are out of service (no routing to ACD).
• Voice mail functions are out of service (no call routing to voice mail).
• The announcement service is out of service.

Mitel 415/430 as of R4.1 71

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

3. 4. 8 Temporary offline licences

If the connection to the master is interrupted in an AIN, the satellites restart in offline
mode. The licences acquired on the master are no longer visible for the satellites in of-
fline mode. To ensure autonomous VoIP and QSIG traffic temporarily, certain licences
are enabled in the satellites concerned for the duration of offline operation or for a max-
imum of 36 hours (the licences are not visible in WebAdmin). The licence overview
(Tab. 31) shows which licences are affected. To ensure longer offline operation, the
necessary licences must also be acquired on the satellites.

3. 4. 9 Trial licences
Trial licences are available for some functions. This means that functions or features
that require a licence can be used and tested, licence-free, for a period of 60 days. The
trial licences are automatically enabled the first time a particular function is used and
then listed in WebAdmin in the Licenses ( =q9) view, complete with the date on
which they expire. This procedure can only be used once for each function or feature.
Thereafter you must acquire a licence. The licence overview (Tab. 31) shows which
trial licences are available.

Overview of licences
Tab. 31 Overview of licences
Without Licences for Offline Trial
Licence Licensed attributes With licence
licence networking licence licence
Software
Software Release Allows a particular soft- Restricte Unrestricted per node (also – –
ware release to be oper- d1) in AIN)
ated
Users
Basic User Licence bundle: 0 Limited only by In the AIN, only – –
1 User licence the system on the Master;
1 phone licence (any one) capacity otherwise per
node.
Entry UCC User Licence bundle: 0 Limited only by In the AIN, only – –
• 1 licence User the system on the Master;
• 8 phone licences (any capacity otherwise per
one) node.
• Video licence for all
licensed phones.
• MiCollab role UCC
Entry

72 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

Without Licences for Offline Trial

Licence Licensed attributes With licence
licence networking licence licence
Standard UCC Licence bundle: 0 Limited only by In the AIN, only – –
User • 1 User licence the system on the Master;
• 8 phone licences (any capacity otherwise per
one) node.
• Video licence for all
licensed phones.
• MiCollab role UCC
Standard
Premium UCC Licence bundle: 0 Limited only by In the AIN, only – –
User • 1 User licence the system on the Master;
• 8 phone licences (any capacity otherwise per
one) node.
• Video licence for all
licensed phones.
• MiCollab role UCC Pre-
mium
Terminals
MiVoice 2380 IP Number of registered 0 Per licence 1 In the AIN, only ✓ ✓
Softphones MiVoice 2380 IP IP soft- additional IP soft- on the Master;
phones phone otherwise per
node.
MiVoice 5300 IP Number of registered , 0 1, 20 or 50 addi- In the AIN, only ✓ ✓
Phones2) MiVoice 5360 IP, tional IP system on the Master;
MiVoice 5361 IP, phones per otherwise per
MiVoice 5370 IP and licence node.
MiVoice 5380 IP IP sys-
tem phones
Mitel SIP Termi- Number of registered 0 1, 20 or 50 addi- In the AIN, only ✓ ✓
nals Mitel SIP terminals tional Mitel SIP on the Master;
terminals per otherwise per
licence node.
Mitel 8000i Video Use of the video function- 0 Additional licence In the AIN, only ✓ ✓
Options ality of an Mitel SIP termi- for Mitel SIP Ter- on the Master;
nal minals. 1, 20 or otherwise per
50 additional node.
Mitel SIP termi-
nals with video
functionality per
licence.
Mobile or External Number of mobile/exter- 0 One additional In the AIN, only ✓ ✓
Phone Extensions nal phones that can be mobile/external on the Master;
registered (without Mitel phone per licence otherwise per
Mobile Client) (without Mitel node.
Mobile Client)

Mitel 415/430 as of R4.1 73

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

Without Licences for Offline Trial

Licence Licensed attributes With licence
licence networking licence licence
MMC Extensions Number of mobile phones 0 Per licence 1 In the AIN, only – –
that can be registered additional mobile on the Master;
with Mitel Mobile Client phone (with Mitel otherwise per
for operation with an Mitel Mobile Client) node.
Mobile Client Controller
(MMCC)
SIP Terminals Number of registered 0 1 additional In the AIN, only ✓ ✓
standard SIP terminals standard SIP ter- on the Master;
minal per licence otherwise per
node.
Video Terminals Use of the video function- 0 Additional licence In the AIN, only ✓ ✓
ality of a standard SIP ter- for SIP Terminals. on the Master;
minal 1 additional otherwise per
standard SIP ter- node.
minal with video
functionality per
licence.
Dual Homing Number of registered 0 Per licence 1, 20 Always on the – ✓
Mitel 6700 SIP / or 50 additional backup com-
6800 SIP SIP phones on phones munication
a backup communication server
server
BluStar
BluStar Soft- Number of registered 0 1, 20 or 50 addi- In the AIN, only ✓ ✓
phones BluStar softphones tional BluStar on the Master;
softphones per otherwise per
licence node.
BluStar Softphone Use of the video function- 0 Additional licence In the AIN, only ✓ ✓
Video Options ality of a BluStar soft- for BluStar soft- on the Master;
phone phone. 1, 20 or 50 otherwise per
additional BluStar node.
softphones with
video functionality
per licence.
Audio services
Conference Bridge Use of conference bridge Locked Enabled In the AIN, only – ✓
on the Master;
otherwise per
node.
Enterprise Voice Voice compression, Locked Enabled (includ- In the AIN, only ✓ ✓
Mail expanded voice memory ing 2 audio chan- on the Master;
capacity, and e-mail noti- nels for voice otherwise per
fication whenever new mail, Auto Atten- node.
voice messages are dant or call
received, forwarding of recording)
voice messages, call
recording.

74 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

Without Licences for Offline Trial

Licence Licensed attributes With licence
licence networking licence licence
Audio Record & Audio channels for Locked Per licence 1 In the AIN, only – –
Play Channels recording or playing back additional audio on the Master;
audio data. channel for voice otherwise per
mail, Auto Atten- node.
dant or call
recording
Auto Attendant Use of the auto attendant Locked Enabled In the AIN, only ✓ ✓
function on the Master;
otherwise per
node.
Number in Queue Use of the function 'queue Locked Enabled In the AIN, only ✓ ✓
with announcement ' on the Master;
otherwise per
node.
Features
Secure VoIP Encrypted VoIP connec- Non- Encrypted trans- Per node – –
tions using SRTP and encrypte mission
TLS. d trans-
mission
Silent Intrusion Use of the Silent intrusion Locked Enabled In the AIN, only – –
feature on the Master;
otherwise per
node.
Analogue Modem Use of the modem func- Locked Enabled In the AIN, only ✓ ✓
tionality on an on the Master;
Mitel 415/430. otherwise per
node.
Resources
VoIP Channels for VoIP functionality 0 / 2 4) Per licence 1 In the AIN, only ✓ ✓
Standard Media additional VoIP on the Master;
Switch3) channel otherwise per
node.
G.729 Codec Use of a G.729 codec for 0 Per licence 1 In the AIN, only ✓ –
the voice channel of Mitel voice channel on the Master;
SIP phones, IP system with G.729 codec otherwise per
phones and SIP network node.
interfaces.
Networking
B-Channels on B channels that can be 10 Per licence 1 In the AIN, only – –
PRI Cards used simultaneously on additional B- on the Master;
the PRI interface channel otherwise per
node.
SIP Access Chan- Simultaneously usable 0 Per licence 1 In the AIN, only ✓ ✓
nels channels to an SIP pro- additional SIP on the Master;
vider access channel otherwise per
node.

Mitel 415/430 as of R4.1 75

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

Without Licences for Offline Trial

Licence Licensed attributes With licence
licence networking licence licence
Lync Option for Enables using a SIP 0 Additional licence In the AIN, only ✓ ✓
SIP Access Chan- access channel with for SIP Access on the Master;
nels Lync-specific options and Channels. Per otherwise per
features. licence one addi- node.
tional channel
with Lync-spe-
cific options and
features.
Private networking
QSIG Networking QSIG channels 0 Per licence 4 or n Per node ✓ ✓
Channels5) QSIG channels (n
limited by the sys-
tem capacity)
Base Mitel AIN6) Operation of an AIN Locked AIN with master Only on the – –
and one satellite Master
Mitel AIN Satel- Additional satellite in an 0 Additional licence Only on the – –
lites6) AIN for Base Mitel Master
AIN. 1 additional
satellite per
licence
Applications
Hospitality Man- Use of Mitel 400 Hospital- Locked Enabled In the AIN, only – ✓
ager ity Manager on the Master;
otherwise per
node.
Hospitality PMS Use of the PMS interface Locked Enabled In the AIN, only – ✓
Interface and therefore the FIAS on the Master;
protocol. otherwise per
node.
Hospitality PMS Number of rooms when 0 1, 20, 50 or 100 In the AIN, only – ✓
Rooms using the PMS interface. rooms per licence on the Master;
otherwise per
node.
Mitel OpenCount Basic licence: Prerequi- Locked Enabled In the AIN, only ✓ ✓
Basic Package site for all other on the Master;
OpenCount licences. otherwise per
Enables connection to the node.
MiVoice Office 400 and
the use of basic functions.
Mitel OpenCount Additional licence: Offers Locked Enabled In the AIN, only ✓ ✓
Healthcare Branch extra functions for care on the Master;
Package homes and retirement otherwise per
homes. node.

76 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

Without Licences for Offline Trial

Licence Licensed attributes With licence
licence networking licence licence
Mitel OpenCount Additional licence: Offers Locked Enabled In the AIN, only ✓ ✓
Public Authorities extra functions for munic- on the Master;
Branch Package ipalities, communities and otherwise per
ministries. node.
Mitel OpenCount Additional licence: Offers Locked Enabled In the AIN, only ✓ ✓
Functional extra functions such as on the Master;
Upgrade to Com- PIN telephony. otherwise per
fort node.
Mitel OpenCount Additional licence: Offers Locked Enabled In the AIN, only ✓ ✓
Functional extra functions such as on the Master;
Upgrade to Pre- intermediate statements, otherwise per
mium invoicing etc. node.
Mitel OpenCount Additional licence: Ena- 0 1, 20 or 50 addi- In the AIN, only ✓ ✓
Users bles a defined number of tional users per on the Master;
users to be monitored via licence otherwise per
OpenCount. node.
Advanced Mes- SMPP protocol for inte- Locked Enabled In the AIN, only – –
saging gration of an SMS server on the Master;
and registration of 9d otherwise per
cordless phones as sys- node.
tem phones. (Includes
licence SMPP)
CTI First Party via First-party CTI clients 0 Enabled for a In the AIN, only – ✓
LAN with basic functions on specific number on the Master;
Ethernet interface of users (see otherwise per
"General system node.
capacity",
page 56)
interfaces
ATAS Interface Use of the ATAS interface Locked Enabled In the AIN, only – ✓
on the Master;
otherwise per
node.
ATASpro Interface Use of the ATASpro inter- Locked Enabled In the AIN, only – –
face on the Master;
otherwise per
node.
BSS Licence Right to connect a BluStar unavail- enabled In the AIN, only – –
server able on the Master;
otherwise per
node.
BSS-Lync Inter- Right to use the BluStar unavail- enabled In the AIN, only – –
face Lync interface able on the Master;
otherwise per
node.

Mitel 415/430 as of R4.1 77

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

Without Licences for Offline Trial

Licence Licensed attributes With licence
licence networking licence licence
CSTA Sessions Number of monitored ter- 0 1, 20, 50 or 100 In the AIN, only ✓ ✓
minals via the CSTA pro- CSTA sessions on the Master;
tocol. per licence otherwise per
node.
Presence Sync. Number of users who can 0 1, 20 or 50 addi- In the AIN, only ✓ ✓
via SIMPLE and use one (or both) proto- tional users per on the Master;
MSRP cols for the third-party licence who may otherwise per
applications. use both proto- node.
cols.
SMPP7) SMPP protocol Locked Enabled In the AIN, only – –
on the Master;
otherwise per
node.
1) four hours after the new software has been uploaded or after a restart operation, the communication server
switches over to a restricted operating mode (see "Restricted operating mode", page 71).
2) The licences can also be used if the Mitel SIP Terminals licences are missing.
3) If Virtual Appliance is used as Master, the VoIP channels of the master node are made available without a li-
cence from the integrated Mitel Media Server. However, for the satellites' VoIP channels, the licences must
be purchased.
4) If VoIP mode is set to G.711, two G.711 VoIP channels per system can be used without a licence.
5) For Virtual Appliance this licence is only relevant to the QSIG networking of an AIN satellite.
6) In a AIN with Virtual Appliance as Master, these licences are part of the Virtual Appliance licences and must
not be purchased individually.
7) This licence cannot be purchased separately; it is part of the Advanced Messaging licence.

All the licences are offered in separate licence packages. Depending on the sales
channels the packages may differ from the licences in Tab. 31. The systems ship out
unlicensed. Back-licensing is not provided for.However, resetting to the factory setting
is possible.

OIP licences
OIP licences are managed by OIP itself. A detailed description of the OIP licences can
be found in the System Manual Mitel Open Interfaces Platform.

3. 4. 10 Power supply capacity

The maximum number of terminals connected to the system can be limited by the sup-
ply power available for terminals. It is also important to take note of the maximum load
per terminal interface.

78 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

3. 4. 10. 1 Supply power available for terminals

The 40 VDC power supply required for the connected terminals is rated for the power
requirements of a typical system configuration.

Tab. 32 Power output of the 40 VDC power supply

Mitel 415 Mitel 430
Available power output 24 Watt 24 Watt

The number of permissible terminals per system depends on the power requirements
of the individual terminals. To check the power requirements refer to Tab. 33 for details
of the average power requirements of the terminals.
The total power requirements of all connected terminals must not exceed the available
power output of the power supply.

Note
The actually required power supply depends strongly on the call traffic, the wire diameter and
the line length to the connected terminals. The values in the following table are average values
under the following assumption:
– Phones traffic volume: Call Connection 38%, Ringing 2%
– SB-4+ radio unit: Active call connection on 2 channels
– SB-8 radio unit: Active call connection on 4 channels
– Background lighting MiVoice 5380: 30% active
– LEDs on terminals and expansion key modules: 20% active.
– Wire diameter: 0.5 mm
– Line length: 200 m
The table below shows the average power requirements of the terminals for a line
length of approx. 200 m and a wire diameter of 0.5 mm.

Tab. 33 Average power requirements of terminals

Terminals Socket Output P [mW]
MiVoice 53601) DSI-AD2 interface 280
MiVoice 5361 DSI-AD2 interface 680
MiVoice 5370 DSI-AD2 interface 680
MiVoice 5380 DSI-AD2 interface 820
MiVoice 5370, MiVoice 5380 with power supply DSI-AD2 interface 0
unit
Expansion key module MiVoice M530 MiVoice 5370 110
Expansion key module MiVoice M530 MiVoice 5380 120
Expansion key module MiVoice M535 MiVoice 5370, MiVoice 5380 0 2)
Radio unit without power supply unitSB-4+ DSI-AD2 interface 1500 3)
Radio unit without power supply unitSB-8 2 DSI-AD2 interfaces 1350 4)
Radio unit with power supply unit SB-4+/SB-8 1 or 2 DSI-AD2 interfaces < 100
Office 101) DSI-AD2 interface 340

Mitel 415/430 as of R4.1 79

syd-0580/1.2 – R4.1 – 08.2016
Expansion Stages and System Capacity

Terminals Socket Output P [mW]

Office 251) DSI-AD2 interface 380
Office 351) DSI-AD2 interface 280 5)
Office 45/45pro1) DSI-AD2 interface 660 5)
Office 45pro power supply unit1) DSI-AD2 interface < 10
Expansion key module (EKP)1) Office 35, Office 45 80
Alphanumerical keyboard (AKB)1) Office 35, Office 45 20
ISDN terminal BRI-S interface approx. 500 6)
Analogue terminals FXS interface approx. 500
1) Although no longer available, the phone is still supported.
2) An MiVoice M535 always requires a power supply unit
3) The value applies to radio units with hardware version "-2". The value for hardware version "-1" is 300 mW
lower.
4) The value applies to each interface and to radio units with hardware version "-2". The value per interface for
radio units with hardware version "-1" is 150 mW lower.
5) The value applies to phones with hardware version "-2". The value for phones with hardware version "-1" is
60 mW lower.
6) The value depends greatly on the terminal type.

Tip
With the planning application Mitel CPQ the power supply available for terminals is checked
automatically.

Overload shutdown
If the rated power is exceeded the power supply is disconnected. It is restored after ap-
prox. 20 s.
If an overload occurs, reduce the required supply power (e.g. by powering DECT radio
units and/or system phones locally).

3. 4. 10. 2 Power supply per terminal interface

The power supply per terminal interface is determined by the interface type. The inter-
face load depends on the following variables:

• Terminals used incl. auxiliary devices

• Bus configuration
• Line length and conductor cross-section

For information on the calculations refer to "Terminal interfaces", page 114.

80 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

4 Installation

This Chapter tells you how Mitel 415/430 can be installed and the conditions to be
observed. It also includes the mounting into a 19” rack, the correct way to connect
the earthing, and the power supply. Other topics described in this Chapter comprise
fitting with system modules, interface cards and the relevant Wiring Adapters. Finally
the Chapter also describes the network- and terminal-side connection of the inter-
faces and the installation, powering and connection of system terminals.

4. 1 System components
The figure below shows the components of the Mitel 415/430 communication server
complete with mounting options.

Plastic cover with

Screening Fan-out-panel
EFOP

Mainboard Power supply

Fan

Power cord

Left-hand bracket
Mounting plate
for cable cover
for rack
installation
Front panel Right-hand bracket
for cable cover
Screw covers Snap-on tag

Left-hand bracket
for cable cover Cable cover

Fig. 11 System components with mounting options

Mitel 415/430 as of R4.1 81

syd-0580/1.2 – R4.1 – 08.2016
Installation

4. 2 Fitting the communication server

The Mitel 415/430 communication server is suitable for both wall and desktop installa-
tion as well as for mounting in a 19” rack. Different mounting sets are available in each
case.

4. 2. 1 Equipment supplied
The equipment supplied with the Mitel 415/430 includes:

• Mitel 415 or Mitel 430 communications server

• Set of screws for wall or desktop installation and earthing connection
• Snap-on tag
• Power supply
• Power cord
• Product information

4. 2. 2 Mounting options
Mitel 415/430 includes all the materials required for wall or desktop installation. Addi-
tional rack installation sets are required for a 19” rack installation. These sets for
Mitel 415 and Mitel 430 are different.
For wall mounting all the connecting cables can be concealed behind a cable cover.
This set can be ordered as an option.

4. 2. 2. 1 Cable cover set for Mitel 415/430

Equipment supplied:

• Cable cover
• Left-hand bracket for cable cover
• Right-hand bracket for cable cover
• Screw set

4. 2. 2. 2 Mitel 415 rack-mounting set

Equipment supplied:

• 2 mounting plates for rack installation

• Screw set

82 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

4. 2. 2. 3 Mitel 430 rack-mounting set

Equipment supplied:

• 2 mounting plates for rack installation

• Screw set
• Fan

4. 2. 3 Location requirements
The following location requirements must be observed when positioning the communi-
cation server.

Hazard
Failure to observe the location requirements can cause the communication server to overheat,
damaging electrical components and/or the surrounding area.
An event message is generated if the heat dissipation is insufficient. Appropriate measures
must be taken immediately to improve the heat dissipation, e.g. by providing the required clear-
ances, lowering the ambient temperature or installing the fan from the rack-mounting set
(Mitel 430 only).

Tab. 34 Mitel 415/430 Location requirements

Heat radiation • Do not position in direct sunlight, near radiators or near other heating sources
EMC • Do not position in strong electromagnetic fields of radiation
(e.g.near x-ray equipment, welding equipment or similar).
Heat dissipation • Do not place any objects on top of the communication server.
• Observe the clearance requirements for wall mounting and desktop installation (see Fig. 12
and Fig. 13).
• In a rack-mounted installation the space to the left and right between the communication server
and the wall of the 19” rack must remain empty. The installation of a fan is also mandatory for
the Mitel 430.
Environment • Ambient temperature 5 °C...45 °C
• Relative humidity 30…80%, non-condensing

Mitel 415/430 as of R4.1 83

syd-0580/1.2 – R4.1 – 08.2016
Installation

4. 2. 4 Safety regulations
Be sure to observe the following safety regulations before carrying out work inside a
communication server:

Warning
Components, interface cards or system modules can be damaged by electrical voltage.
Always disconnect the communication server from the power supply before removing the hous-
ing cover.

Warning
Components can be damaged by electrostatic discharge when touched.
Always touch the earthed metal case of the communication server before carrying out work
inside the housing. This also applies to interface cards and system modules that are no longer
packed inside the ESD protective wrapping.

4. 2. 5 Wall mounting
There are two possibilities for wall mounting. In the first variant the front panel faces
right (see Fig. 12); in the second, it faces downwards (see Fig. 13). The wall-mounting
option chosen will depend on the way the cables are routed. The LED display remains
visible whatever the mounting position, even when the cable cover is fitted.

Warning
A wall-mounting option in which the front panel faces upwards or to the right is not permitted.
Inadequate heat dissipation can damage the communication server.

4. 2. 5. 1 Minimum distances
To ensure adequate heat dissipation, minimum distances need to be maintained with
other objects such as cable ducts, cabinets or mobile objects. Maintaining minimum
distances also allows the installation of the cable cover and the possibility of suspend-
ing the communication server into and out of the wall-mounted screws.
The two diagrams below illustrate the two wall-mounting possibilities.

84 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

t

t

t t t

All dimensions in mm

Fig. 12 Minimum distances for wall mounting (front panel facing to the right)

t

t

t t t

All dimensions in mm

Fig. 13 Minimum distances for wall mounting (front panel facing downwards)

Mitel 415/430 as of R4.1 85

syd-0580/1.2 – R4.1 – 08.2016
Installation

4. 2. 5. 2 Drilling plan
The communication server is suspended into two premounted wall screws using the
suspension points in the housing base. Depending on the type of mounting, these are
the suspension points marked under position A or B on the drilling plan. The communi-
cation server is secured with a third screw to prevent it from being dislodged acciden-
tally (position C).

"

#

$

" #

All dimensions in mm

Fig. 14 Drilling plan for Mitel 415/430 wall mounting

86 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

4. 2. 5. 3 Drilling template
The packaging box of the communication server can also be used for marking out the
drill holes. To do so it is best to detach the part of the inner packaging box that contains
the drill holes.
Note: The holes on the cardboard box are not labelled.

"

$

Fig. 15 Drilling template

4. 2. 5. 4 Wall-mounting procedure
Materials required:

• Screw set for wall/desktop installation

• 6 mm drill
• Screwdriver

Mitel 415/430 as of R4.1 87

syd-0580/1.2 – R4.1 – 08.2016
Installation

To mount the communication server to the wall, proceed as follows:

1. Using the drill template or the instructions on the drill plan to mark out the three drill
holes. Make sure you observe the minimum distances to other objects, walls or ceil-
ings as shown in Fig. 12 and Fig. 13.
2. Drill the three dowel holes.
3. Insert the dowel plugs.
4. Screw in the two shorter upper dowel screws (position A or B). Observe the distance
between the screw heads and the wall as shown in Fig. 14.
5. Shut down the communication server (see "Shutdown Mode", page 206) and dis-
connect it from the power supply.

Warning
Be sure to observe the "Safety regulations", page 84.
6. Remove the housing cover.
7. Connect the earthing (see "Connecting the earthing wire", page 93).
8. Suspend the housing of the communication server onto the screws.
9. To secure the communication server screw in the long lower dowel screw (position
C).
10.Fit the housing cover.
11.Secure the snap-on tag to the front panel or to a suitable position on the housing
cover. The holes in the housing cover are spaced in such a way that the snap-on tag
can be secured both lengthways and crossways.
12.Reconnect the communication server to the power supply.

4. 2. 6 Desktop installation
To protect the cable connections the communication server can also be secured using
three screws. The same drilling plan (see Fig. 14) and the same procedure apply as for
wall mounting (see "Wall-mounting procedure", page 87).

Warning
To ensure adequate heat dissipation make sure that no objects are placed on top of the commu-
nication server (see also "Location requirements", page 83). Minimum distances must also be
observed as shown in Fig. 12.

88 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

4. 2. 7 Rack-mounting
The rack-mounting set Mitel 415 or Mitel 430 allows the communication server to be in-
stalled horizontally into a 19” rack. Be sure to observe the following:

• The communication server takes up the space of 1.5 height units inside the 19”
rack. (1 Unit corresponds to 44.45 mm).
• The holes in the mounting plates allow two communication servers to be placed di-
rectly above each other with a space requirement of three units. Different holes in
the mounting plates are used for this purpose (see Fig. 16).
• The space on the left and right between the communication server and the panels of
the 19” rack is for heat dissipation and must remain clear.
• The installation of a fan is mandatory whenever an Mitel 430 is rack-mounted; the
fan is included in the Mitel 430 rack-mounting kit.
Note: The rack-mounting set always includes fastening screws for the fan. On the
Mitel 415 these two screws are superfluous.

6OJU

&75/

6OJUT

6OJU

&75/

6OJU

6OJUNN

Fig. 16 Placing two communication servers above each other inside a 19” rack

Mitel 415/430 as of R4.1 89

syd-0580/1.2 – R4.1 – 08.2016
Installation

4. 2. 7. 1 Rack-mounting procedure
Materials required:

• Mitel 415 and Mitel 430 rack-mounting kit

• Screw set for wall/desktop installation
• Screwdriver

To rack-mount an Mitel 415/430 proceed as follows:

1. Pull off the screw covers on the left and right of the front panel.
2. Secure the mounting plates to the communication server using the M4 screws.
Make sure the front panel and the mounting plate are aligned.
3. Shut down the communication server (see "Shutdown Mode", page 206) and dis-
connect it from the power supply.

Warning
Be sure to observe the "Safety regulations", page 84.
4. Remove the housing cover.
5. Mitel 430 only:
Install the fan (see "Installing the fan", page 91).
6. Connect the earthing (see "Connecting the earthing wire", page 93).
7. Fit the housing cover.
8. Secure the cage nuts in the appropriate positions in the rack’s fastening rails (see
Fig. 16).
9. Secure the communication server to the rack’s fastening rails using the M6 screws,
the plastic washers and the cage nuts.
10.Fasten the snap-on tag to the front panel.
11.Reconnect the communication server to the power supply.

90 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

4. 2. 7. 2 Installing the fan

Materials required:

• Fan from the Mitel 430 rack-mounting kit

• 2 screws from the Mitel 430 rack-mounting set
• Screwdriver

To install the fan proceed as follows:

1. Shut down the communication server (see "Shutdown Mode", page 206) and dis-
connect it from the power supply.

Warning
Be sure to observe the "Safety regulations", page 84.
2. Remove the housing cover.
3. Use the two screws to fit the fan to the inside of the housing. Take note of the arrows
on the fan. They indicate the direction of rotation and the air flow. The air must flow
out of the housing of the communication server (see Fig. 17).
4. Plug the fan connector into the socket marked "FAN" on the mainboard.
5. Fit the housing cover.
6. Reconnect the communication server to the power supply.

Note
The fan only turns if required by the equipment temperature.

!
N
A
F

Fig. 17 Installing the fan in Mitel 430

Mitel 415/430 as of R4.1 91

syd-0580/1.2 – R4.1 – 08.2016
Installation

4. 2. 7. 3 Installing the cable cover

Materials required:

• Cable cover set for Mitel 415/430

• Screwdriver

To install the cable cover proceed as follows:

1. Pull off the screw covers on the left and right of the front panel.
2. Use the M4 screws of the cable cover set to secure the brackets for the cable cover
to the communication server.

Note
The two brackets are not identical. Compare the cable brackets with the figures in Fig. 18.
3. Fit the cable cover over the brackets from above until they are felt to engage.

Fig. 18 Installing the brackets for the cable cover

Tip
To remove the cable cover reach into the side openings of the cover, gently press the two
(engaged) lugs outwards and remove the cover.

4. 3 Earthing and protecting the communication server

The protective earth and equipotential bonding are important integral parts of the
safety concept: Standard EN 60950 relevant to safety matters stipulates protective
earthing.

Warning
High leakage currents can occur as a result of connecting to the communication network.
Establish an earth connection before connecting to the communications network.
Disconnect the communication server from the communications network before carrying out
maintenance work.

92 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

Warning
Transient overvoltage can occur on the mains and on the communications network.
Protect each line installation leading from the building by using one surge voltage protector per
core at the isolating point (main) distribution frame or entry point into the building.
Operation on an IT current distribution system:
The communication server can be operated on an IT power distribution system as per
EN/IEC 60950 with voltages of up to 230 VAC.

4. 3. 1 Connecting the earthing wire

The communication server’s earthing connection is located at the front left on the un-
derside and can only be connected once the housing cover has been removed. The
earthing wire is secured by a screw, spring washer and serrated lock washer, which
are included in the screw set Mitel 415/430. The serrated lock washer must rest
against the metal housing of the communication server.

Fig. 19 Earthing connection

Mitel 415/430 as of R4.1 93

syd-0580/1.2 – R4.1 – 08.2016
Installation

Direct connection Indirect connection

Socket-outlet Socket-outlet
Mains power Mains power

Protective wire Protective wire

Power supply Power supply

(Main)
distribution
board

Mitel Mitel
415/430 415/430

Copper wire yellow/ green Copper wire yellow/ green

2,5 mm2 protected 4,0 2,5 mm2 protected 4,0
Building earth mm2 unprotected Building earth mm2 unprotected

Fig. 20 Earthing of the communication server in the case of an indirect cabling and direct cabling

Note
In the case of an indirection connection make sure that the communication server’s earthing
wire does not form any earth loops with the earthed cable screenings of the installation cables
leading up to the (main) distribution frame. The cables should be kept as short as possible and
laid out in parallel.

94 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

4. 3. 2 Connecting the cable screening

When using shielded installation cables also use shielded RJ45 connectors. In this
way the shielding of the installation cables is automatically connected with the housing
of the communication server and therefore with the building earth.

Note
Connect the cable screens to one another at the splitting point only. Observe the tree structure
principle to prevent earth loops.

Socket-outlets
(Main) distribution
board

Communica-
tion server

No earth
X loops

Fig. 21 Tree structure principle

4. 4 Powering the communication server

The communication server is powered as standard with 230 VAC or 115 VAC. To en-
sure that its operation is maintained even in the event of a mains outage, an external
uninterruptible power supply (UPS) must be used.

4. 4. 1 115/230 V power supply

The communication server is powered by the supplied power supply unit. The power
supply unit is connected to the mains using a two-pin standard power cable.

Hazard:
Hazard due to heat generation in the event of short-circuits. The mains power supply connec-
tion must be protected with 16 A maximum in countries with 230 V mains power (for instance in
Europe), and with 20 A maximum in countries with 115 V mains power (e.g. in North America).

Mitel 415/430 as of R4.1 95

syd-0580/1.2 – R4.1 – 08.2016
Installation

Please also note the following points:

• The mains connector acts as a disconnecting device and must be positioned so that
it is easily accessible.
• Only ever use the supplied power supply unit.

Mains power

1.8 m Power supply 1.5 m

Fig. 22 Powering the communication server from the mains

4. 4. 2 Uninterruptible power supply (UPS)

The use of an external uninterruptible power supply (UPS) guarantees operation even
in the event of a mains outage.
The UPS battery capacity is rated according to the communication server’s primary
power requirements and the required bridging time. The table below shows the maxi-
mum power requirements of the communication server in its maximum configuration
and maximum traffic volume.

Tab. 35 Maximum power requirements of the communication server

Communication server Maximum power requirements
Mitel 415 100 VA
Mitel 430 150 VA

The battery capacity required [Ah] can be calculated using the battery voltage and the
maximum bridging time. It is important to note that the battery must never be allowed to
become completely discharged and that in typical conditions only approx. 60% of the
maximum power requirements is needed.

Note
The uninterrupted operation of the communication server is ensured if the UPS takes over the
power supply within 20ms of the mains outage.

96 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

See also
For more technical details see "Technical data", page 246.

4. 5 Equipping the Basic System

For an individual expansion the Mitel 415/430 basic system can be equipped with inter-
face cards, the appropriate wiring adapters and system modules. An overview can be
found in the Chapter "Expansion Stages and System Capacity", page 39.

4. 5. 1 Interface card
Interface cards are fitted to slots IC1…IC4. IC3 and IC4 can be found only on the
Mitel 430 (see Fig. 7).

Warning
Be sure to observe the "Safety regulations", page 84.

1. Shut down the communication server (see "Shutdown Mode", page 206) and dis-
connect it from the power supply.
2. Remove the housing cover.
3. Place the interface card at a slight angle into the required slot (see Fig. 23). Make
sure the angled side of the interface card is facing backwards (i.e. it must not project
over the wiring adapter slots).
4. Carefully press the interface card downwards until the two lateral metal clamps en-
gage.
5. Fit the corresponding wiring adapter (see "Wiring Adapter", page 98) into the appro-
priate wiring adapter slot WA1…WA4.
6. Fit the housing cover.
7. Reconnect the communication server to the power supply.

Mitel 415/430 as of R4.1 97

syd-0580/1.2 – R4.1 – 08.2016
Installation

Interface card

1
Metal clamp 50 - 60°

Slot 25°

Mainboard

Fig. 23 Fitting an interface card

Notes
– The ODAB options card must be fitted to slot IC2 (Mitel 415) or slot IC4 (Mitel 430) if it is to
be used for connecting a door intercom (see "Equipment on the ODAB options card",
page 138).
– The interface cards EAD4V and EAD4C cannot be fitted to slot IC4 of an Mitel 430 due to
their mechanical dimensions.

4. 5. 2 Wiring Adapter
Wiring adapters are used to route the interfaces of the interface cards to the RJ45
sockets on the front panel and are fitted to slots WA1…WA4. The WA0 slot is never
equipped. Slots WA3 and WA4 are to be found only on the Mitel 430 (see also Fig. 7).
The table below provides an overview of the combinations of wiring adapters and inter-
face cards. Unless specified otherwise, the corresponding wiring adapter is included in
the equipment supplied with each interface card.

Tab. 36 Combinations of wiring adapters / interface cards

Plug-in ori- Port number
Wiring Adapter Interface card
entation X.1 X.2 X.3 X.4
WA-TS0 TIC-4TS TTTT T T T T
TIC-4TS STTT S T T T
TIC-2TS TTTT T T – –
TIC-2TS STTT S T – –
ESST1)2) STTT S T – –

98 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

Plug-in ori- Port number

Wiring Adapter Interface card
entation X.1 X.2 X.3 X.4
WA-TS1 TIC-4TS1) SSTT S S T T
TIC-4TS1) SSST S S S T
TIC-2TS1) SSTT S S – –
TIC-2TS1) SSST S S – –
ESST1)2) SSTT S S – –
ESST1)2) SSST S S – –
ODAB SSTT I/O 1,2 I/O 3,4 ab/Door –
Intercom
WA-2W ETAB43) – FXS FXS FXS FXS
EADP43) – DSI DSI DSI DSI
EAD4C1) – DSI DSI DSI DSI
EAD4V1) – DSI DSI DSI DSI
EAAB21) – – – FXO FXO
TIC-4AB – FXO FXO FXO FXO
TIC-2AB – FXO FXO – –
WA-1PRI TIC-1PRI – PRI Test4) – –

1) The wiring adapter is not part of the equipment supplied with this interface card and must be ordered sepa-
rately.
2) On the ESST terminal card the jumper must always be fitted in position T (see Fig. 24).
3) The wiring adapter is only part of the equipment supplied with order variant Mitel 415/430.
4) For test purposes the PRI interface is also routed in parallel to port X.2.

Please note:

• The arrows on the wiring adapters specify the plug-in orientation of the required port
assignment.
• On the ESST terminal card the jumper must always be fitted in position T (see figure
below). The port assignment is specified by the wiring adapter alone.

Mitel 415/430 as of R4.1 99

syd-0580/1.2 – R4.1 – 08.2016
Installation

Card ESST-2 Card ESST-2

T T
S S
Jumper in NC Jumper in NC
NC NC
position T: S/T position S: S/T

RIGHT WRONG

Fig. 24 Jumper position on ESST card

Note
Any incorrectly fitted or missing wiring adapters are signalled by a red flashing LED on the dis-
play after start-up (see "Wiring Adapter Malfunction Mode", page 205).

4. 5. 3 DSP module
DSP modules belong to the category of system modules and are fitted to the SM1 slot
(see Fig. 7). Three DSP modules are stackable.

Warning
Be sure to observe the "Safety regulations", page 84.

1. Shut down the communication server (see "Shutdown Mode", page 206) and dis-
connect it from the power supply.
2. Remove the housing cover.
3. Remove the fastening screw from module slot SM1.
4. Instead of the fastening screw, screw in the spacer sleeve enclosed with the mod-
ule.
5. Place the module on slot SM1 of the communication server (or onto a module al-
ready fitted in that slot) and press down evenly on both connectors as far as the
stop.
6. Secure the module with the fastening screw.
7. Fit the housing cover.
8. Reconnect the communication server to the power supply.

4. 5. 4 Component mounting rules

The component mounting rules mentioned in the previous chapters are listed here in
an overview:

• In principle the interface cards can be used in all the card slots.
Exceptions:

100 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

– The interface cards EAD4V and EAD4C cannot be fitted to slot IC4 of an
Mitel 430 due to their mechanical dimensions.
– If the ODAB options card is used to connect a door intercom, it must be fitted to
slot IC2 (Mitel 415) or slot IC4 (Mitel 430).
– If the ODAB options card is used to control switch group positions and external
devices, it must be fitted to slot IC1 (Mitel 415) or slot IC1, 2 or 3 (Mitel 430).
• DSP modules are stackable and must always be fitted to slot SM1. Slot SM2 on the
Mitel 430 communication server is provided for future expansions.
• On the ESST terminal card the jumper must always be fitted in position T (see
Fig. 24).
• The interfaces are enabled sequentially when the communication server is started
up. The following rules apply:
– The number of interfaces actually enabled is determined in each case by the sys-
tem capacity (see "System capacity", page 56). If a limit value is reached, all the
interface cards or all the interfaces of the last card may not be enabled.
– The interfaces are enabled in accordance with their designation, starting with the
lower designations. This means that the terminal interfaces on the mainboard are
always enabled before those on the interface cards.

4. 6 Connecting the communication server

There are two possibilities for connection to the telephone network and the terminal-
side cabling:

• Direct connection
• Indirect cabling via (main) distribution frame and any universal building cable instal-
lation (UBC) (see also Fig. 28 and Fig. 29).

Communica-
tion server

NT1 Communica-
NT1 tion server

NT1
NT1

(Main) distribution
board

Fig. 25 Direct cabling (left) and indirect cabling (right)

On the front panel all the connections are made using RJ45 connectors.

Mitel 415/430 as of R4.1 101

syd-0580/1.2 – R4.1 – 08.2016
Installation

4. 6. 1 Direct connection
Standard commercial cables are used to connect directly to the telephone network. De-
tails can be found in the Chapter "Network interfaces", page 106.

4. 6. 2 Indirect connection
There are two possibilities for connecting the communication server indirectly to the
telephone network and terminal-side cabling:

• Connection via main distribution board

• Connection to a universal building cable installation (UBC)

4. 6. 2. 1 Connection via main distribution board

Communica-
tion server

NT1
NT1
(Main)
distribution
board

Fig. 26 Connection via main distribution board

The interface sockets on the front panel are connected with the (main) distribution
frame or the patch panels using either patch cables or prefabricated system cables
(see "Equipment Overview", page 245).

Prefabricated system cable 12 x RJ45

The cable is 6 m long and, at one extremity, has 12 RJ45 connectors for the interfaces
on the front panel. Two of them have 4 cores; the others, 2 cores. This means the ca-
ble is suitable for connecting the following interfaces:

• 2 network interfaces BRI-T or 2 terminal interfaces BRI-S or a combination thereof.

• 10 terminal interfaces (DSI, FXS) or a combination thereof.

102 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

Notes:
– This cable cannot be used to connect PRI and Ethernet interfaces (see also "Connection of
PRI primary rate interface", page 110 and "Connection of Ethernet interfaces", page 145).
– It is not possible to connect an ODAB door intercom interface with only one cable (see also
"Connection of a door intercom (TFE)", page 138).

Tip
Use standard commercial connecting cables not just for the PRI and Ethernet interfaces but
also for connecting the BRI-T interfaces.

Tab. 37 Schematic diagram of prefabricated system cable 12 × RJ45

Stranded Cable desig- RJ45 Signal
Core colour
element nation Pin Connection four-wire Two-wire connection
1 white 1 4 f a
blue 5 e b
turquoise 6 d –
violet 3 c –
2 white 2 4 f a
orange 5 e b
turquoise 6 d –
violet 3 c –
3 white 3 4 – a
green 5 – b
turquoise 4 4 – a
violet 5 – b
4 white 5 4 – a
brown 5 – b
turquoise 6. 4 – a
violet 5 – b
5 white 7 4 – a
grey 5 – b
turquoise 8 4 – a
violet 5 – b
6 red 9. 4 – a
blue 5 – b
turquoise 10 4 – a
violet 5 – b
7 red 11 4 – a
orange 5 – b
turquoise 12 4 – a
violet 5 – b

Mitel 415/430 as of R4.1 103

syd-0580/1.2 – R4.1 – 08.2016
Installation

A B

View A View B
Fig. 27 Pin numbering, RJ45 connector

4. 6. 2. 2 Connection to a universal building cable installa-

tion (UBC)
Patch panel
User

EDV 2nd floor

Phone

User

Communi- EDV 1st floor

cation
server Phone

User

NT1 EDV Ground floor

NT1 Phone

(Main) distri-
bution frame

Fig. 28 Connecting to a UBC via a (main) distribution board (example)

104 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

Communica-
tion server User Patch panel

EDV

Phone User side

Phone Exchange side

NT1
Public
NT1 exchange

Fig. 29 Connecting to a UBC via wiring centre (example)

4. 7 Cabling interfaces
All the interfaces are routed to the front panel and are therefore accessible without
opening the communication server.

Fig. 30 Interfaces on the front panel with port designation (Mitel 430)

4. 7. 1 Port addressing
A port address is always of the type x.y. x is the number of the card slot, and y, the port
number.
The slot numbering begins with 0 (=mainboard) and ends with 2 (for Mitel 415) or 4 (for
Mitel 430).
With BRI-S interface and DSI interface addresses, the terminal selection digit (TSD) is
relevant, in addition to the slot and port numbers. This is always -1 in analogue termi-
nal interfaces.

Mitel 415/430 as of R4.1 105

syd-0580/1.2 – R4.1 – 08.2016
Installation

Tab. 38 Examples of interface addressing

Slot Port address
Mainboard; DSI interface x.5 0.5
Interface card on slot IC1; interface x.3 1.3
Terminal with TSD2 on interface card in IC3; interface x.4 3.4-2

4. 7. 2 Network interfaces
Equipping the system with interface cards provides the necessary network interfaces.
With the exception of the Ethernet interface, which also represents a network interface
via SIP access, there are no network interfaces on the Mitel 415/430 mainboard.

4. 7. 2. 1 Basic rate interface BRI-T

With the appropriate interface cards and Wiring Adapters, BRI network interfaces can
be made available at RJ45 sockets 1.x...4.x (for Mitel 415 1.x and 2.x only). The possi-
ble RJ45 sockets are highlighted in colour in the figure below.

Fig. 31 Connection possibilities for BRI network interfaces

Notes
– The interfaces can be configured on BRI-S using the wiring adapters (see "Wiring Adapter",
page 98).
– The maximum number of interfaces per communication server has to be taken into account
(see Tab. 30).
– Circuit type as per EN/IEC 60950: SELV
The connection from the front panel to the NT1 (Network Termination) is via standard
commercial straight patch cables with 8-pin RJ45 connectors on both sides. With the
appropriate tools you can also create your own cables.

Cable Requirements
Tab. 39 Cable requirements for basic rate interface BRI-T
Core pairs × cores 1×4o2×2
Stranded yes
Wire diameter, core 0.4…0.6 mm

106 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

Screening recommended
Characteristic impedance < 125 Ω (100 kHz), < 115 Ω (1 MHz)
Wave attenuation < 6 dB/km (100 kHz), < 26 dB/km (1 MHz)
Near/crosstalk attenuation > 54 dB/100 m (1 kHz to 1 MHz)

BRI basic rate interface network-side

Mains power

[1] Communica-
NT1 tion server
U BRI-T BRI-T
c c
a d d
Exchange b e e
[2] f f

[1] Do not connect power supply NT1

[2] Do not fit the jumper

Fig. 32 Basic access on NT1

The assignment of the RJ45 connector is identical on the NT-side and on the side of
the communication server.

Tab. 40 Wiring of the BRI basic rate interface network-side

Cable cores
NT1 Communication server
Straight patch cable
BRI-T sig- BRI-T sig-
Socket Pin Pin Socket
nal nal
1 – – 1
2 – – 2
3 c c 3


4 f f 4


5 e e 5

6 d d 6
7 – – 7
8 – – 8

Mitel 415/430 as of R4.1 107

syd-0580/1.2 – R4.1 – 08.2016
Installation

Basic access in the private leased-line network

BRI-Sextern Copper line BRI-T

PINX 1 PINX 2
max. 1,000 m 4

Fig. 33 BRI-S basic rate interface external, networked with copper line

Tab. 41 Connection of BRI-S basic rate interface external, networked with copper line
PINX 1 signal PINX 2 signal
Cable cores
Basic access BRI-S ext. Basic rate interface BRI-T
c c
f f
e e
d d

Bus configuration
BRI-S ext. is subject to the conditions that apply to terminal interface BRI-S (see "BRI-S
terminal interfaces", page 122).

Leased-line
BRI-T or dial-up BRI-T
PINX 1 NT1 NT1 PINX 2
connection

Fig. 34 Basic rate interface BRI-T, networked with leased-line or dial-up connection

Tab. 42 Cabling for basic rate interface BRI-T, networked with leased-line or dial-up connection
PINX1 signal, PINX 2 signal,
basic rate inter- Cable cores NT1 Network NT1 Cable cores basic rate inter-
face BRI-T face BRI-T
c c c c
f f f f
e e e e
d d d d

See also
Chapter "Connections with basic accesses" in the PISN/QSIG Networking System Manual.

108 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

4. 7. 2. 2 Primary rate interface PRI

With the appropriate interface cards and Wiring Adapters, PRI network interfaces can
be made available at RJ45 sockets 1.1, 2.1, 3.1 and 4.1 (Mitel 415 only 1.1, 2.1). For
test purposes the PRI interface is also routed in parallel to ports x.2. The possible RJ45
sockets are highlighted in colour in the figure below.

7(67 7(67 7(67 7(67

Fig. 35 Connection possibilities for PRI network interfaces

Notes
– In normal operation the x.2 test socket must not be connected; otherwise faults may occur.
– Circuit type as per EN/IEC 60950: SELV

Cable Requirements
The connection to NT1 (Network Termination) is implemented using commercially
available screened cables with 8-pin RJ45 connectors at both ends, e.g. S-FTP 4P,
PVC, Cat. 5e.

Tab. 43 Cable requirements for the primary rate interface)

Core pairs × cores 2 × 2 (short distances also 1 × 4)
Stranded yes
Wire diameter, core 0.4...0.6 mm
Screening yes
Characteristic impedance 90 to 130 Ω (1 MHz)
Wave attenuation < 6 dB/km (100 kHz), < 26 dB/km (1 MHz)
Near/crosstalk attenuation > 54 dB/100 m (1 kHz to 1 MHz)

Mitel 415/430 as of R4.1 109

syd-0580/1.2 – R4.1 – 08.2016
Installation

PRI primary rate interface, network-side

Mains power

NT1
RXA
Exchange RXB Communication
U PRI TXA server
TXB

Fig. 36 PRI primary rate interface on NT1

Tab. 44 Connection of PRI primary rate interface

Cable cores
NT1 Communication server
Straight patch cable
PRI sig-
Socket Pin PRI signal Pin Socket
nal1)
1 TxA RxA 1
2 TxB RxB 2
3 – – 3


4 RxA TxA 4


5 RxB TxB 5

6 – – 6
7 – – 7
8 – – 8
1) Other designations are also possible on the NT1 such as: "S2m ab" instead of "TxA/TxB" and "S2m an" in-
stead of "RxA/RxB".

Primary rate access in the private leased-line network

4-wire
PRI Copper line PRI
PINX 1 PINX 2
max. 200 m

4-wire
PRI Copper line PRI
PINX 1 PINX 2
max. 200 m

Fig. 37 Primary rate access, networked with copper line

110 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

Tab. 45 Cabling for primary rate access PRI, networked with copper line
RJ45 PRI PINX 1 Cable cores PRI PINX 2 RJ45
Pin signal Crossed patch cable signal Pin

1 RxA RxA 1

2 RxB RxB 2

3 — — 3

4 TxA TxA 4

5 TxB TxB 5

6 — — 6

7 — — 7

8 — — 8

Transmission facilities

PRI PRI
PINX 1 PINX 2
max. max.
200 m 200 m

Fig. 38 Primary rate interface, networked with transmission equipment

Mitel 415/430 as of R4.1 111

syd-0580/1.2 – R4.1 – 08.2016
Installation

Tab. 46 Cabling for primary rate access PRI, networked with transmission equipment
PRI Cable cores, Transmis- Transmis- Cable cores PRI
RJ45 RJ45
PINX 1 straight patch sion equip- sion equip- Straight patch PINX 2
Pin Pin
signal cable ment signal ment signal cable signal

1 RxA RxA RxA RxA 1

2 RxB RxB RxB RxB 2

3 — — 3

4 TxA TxA TxA TxA 4

5 TxB TxB TxB TxB 5

6 — — 6

7 — — 7

8 — — 8

Leased-line
PRI PRI
PINX 1 NT1 or dial-up NT1 PINX 2
connection

Mains power Mains power

Fig. 39 Primary rate access PRI, networked with leased-line or dial-up connection

112 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

Tab. 47 Cabling for primary rate interface, PRI, networked with leased-line or dial-up connection
Cable cores, Cable cores
RJ45 PRI PINX 1 PRI signal Net- PRI signal PRI PINX 2 RJ45
straight patch Straight patch
Pin signal NT1 work NT1 signal Pin
cable cable

1 RxA RxA RxA RxA 1

2 RxB RxB RxB RxB 2

3 — — 3

4 TxA TxA TxA TxA 4

5 TxB TxB TxB TxB 5

6 — — 6

7 — — 7

8 — — 8

See also:
System Manual “PISN / QSIG Networking”

4. 7. 2. 3 FXO network interfaces

With the appropriate interface cards and Wiring Adapters, FXO network interfaces can
be made available at RJ45 sockets 1.x...4.x (for Mitel 415 only 1.x and 2.x) The possi-
ble RJ45 sockets are highlighted in colour in the figure below. The maximum number of
interfaces per communication server has to be taken into account (see Tab. 30).

Fig. 40 Connection possibilities for FXO network interfaces

Tip
To be able to make emergency calls even in the event of a mains power failure, you have the
possibility of running up to 8 analogue FXO exchange lines via the EFOP emergency fan-out
panel. In the event of a power failure the EFOP switches exchange lines automatically and
directly over to up to 8 analogue phones (see "Emergency fan-out-panel (EFOP)", page 132).

Mitel 415/430 as of R4.1 113

syd-0580/1.2 – R4.1 – 08.2016
Installation

In a direct connection the RJ45 connector is connected directly to the trunk cable using
a crimp clip.
With an indirection connection you need to observe the cable requirements.

Note
Circuit type as per EN/IEC 60950: TNV-3

Connection
Assignment of the RJ45 sockets on the front panel:

Tab. 48 Connection FXO network interface

Communication server
Public analogue network
FXO signal Pin Socket
– 1
– 2
– 3

a a 4

b
b 5

– 6
– 7
– 8

Cable Requirements
Tab. 49 Cable requirements for FXO network interface
Core pairs × cores 1×2
Stranded not required
Wire diameter, core 0.4 … 0.8 mm
Screening not required
Resistance max. 2 × 250 Ω

4. 7. 3 Terminal interfaces
The number of available terminal interfaces on the mainboard can be increased by fit-
ting interface cards.
The RJ45 connector assignment is the same for interfaces of the mainboard and termi-
nal cards.

114 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

4. 7. 3. 1 DSI terminal interfaces

The DSI terminal interfaces of the mainboard (for Mitel 415 only 0.5 and 0.6) are per-
manently routed to the front panel and labelled accordingly. With the appropriate inter-
face cards and Wiring Adapters, additional DSI terminal interfaces can also be made
available at the RJ45 sockets 1.x...4.x (with Mitel 415 only 1.x and 2.x). The possible
RJ45 sockets are highlighted in colour in the figure below.

Fig. 41 Connection possibilities for DSI terminal interfaces

Note
Circuit type as per EN/IEC 60950: SELV

Connection
Tab. 50 Connection of DSI terminal interfaces
Communication server Cable cores Connection socket
Socket Pin DSI signal DSI signal Pin Socket
1 – – 1
2 – – 2
3 – – 3


4 a a 4


5 b b 5

6 – – 6
7 – – 7
8 – – 8

DSI bus configuration

Depending on the line length, 1 or 2 system phones of the MiVoice 53001) series can
be connected on each DSI-AD2 interface. The following requirements apply with re-
gard to the bus length to ensure that the maximum permissible signal delay is not ex-
ceeded:

1) Office 10, Office 25, Office 35, Office 45/45pro are supported as before

Mitel 415/430 as of R4.1 115

syd-0580/1.2 – R4.1 – 08.2016
Installation

Tab. 51 DSI-AD2 bus length and number of phones

Distance between the 1st and 2nd ones Connec-
Number of phones Total length of DSI-AD2 bus
tion point (without connection cable)
1 A: max. 1200 m –
2 B: max. 1200 m C: max. 10 m

1. Connection
point
Communica-
tion server

1. Connection 2. Connection
point point
Communica-
tion server

C
B

Fig. 42 DSI-AD2 bus

Notes
The total length of the cables from the communication server to the system phone must not be
less than 10 m.

Restrictions
The maximum length of an DSI-AD2 bus is further restricted by:

• the maximum power requirements of the connected system phones and their sup-
plementary equipment. In this context the SB-4+ and SB-8 DECT radio units are
also considered as system phones.
• the line resistance (depending on the line length and wire diameter)

Tab. 52 Maximum power requirements of the system phones on the DSI bus
Max. power input
System phone1) Socket
[mW]
MiVoice 53602) DSI-AD2 interface 900
MiVoice 5361 DSI-AD2 interface 1220 3)
MiVoice 5370 DSI-AD2 interface 1220 3)
MiVoice 5380 DSI-AD2 interface 1340 3)
MiVoice 5370, MiVoice 5380 with power supply unit DSI-AD2 interface 0
Expansion key module MiVoice M530 MiVoice 5370 300
Expansion key module MiVoice M530 MiVoice 5380 500

116 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

Max. power input

System phone1) Socket
[mW]
Expansion key module MiVoice M535 MiVoice 5370, MiVoice 5380 0 4)
DECT radio unit without power supply unit SB-4+ DSI-AD2 interface 1700 5)
DECT radio unit without power supply unit SB-8 2 DSI-AD2 interfaces 1550 6)
DECT radio unit with power supply unit SB-4+/SB-8 1 or 2 DSI-AD2 interfaces < 100
Office 102) DSI-AD2 interface 900
Office 252) DSI-AD2 interface 900
Office 352) DSI-AD2 interface 630 7)
Office 452) DSI-AD2 interface 1110 7)
2)
Office 45pro power supply unit DSI-AD2 interface < 10
Expansion key module (EKP)2) Office 35 150
Expansion key module (EKP)2) Office 45 210
Alpha keyboard2) Office 35, Office 45 30
1) Assumptions:
System phones: In hands-free mode, loudspeaker on maximum volume, all LEDs lit
MiVoice 5380: Backlighting with maximum brightness
Expansion key modules: All LEDs lit
Radio units: Active call connection on all channels
2) Although no longer available, the phone is still supported.
3) The value can increase to approx. 600 mW if the power available at the DSI-AD2 bus allows it.
4) An MiVoice M535 always requires a power supply unit
5) The value applies to radio units with hardware version "-2". The value for hardware version "-1" is 300 mW
lower.
6) The value applies to each interface and to radio units with hardware version "-2". The value per interface for
radio units with hardware version "-1" is 150 mW lower.
7) The value applies to phones with hardware version "-2". The value for phones with hardware version "-1" is
60 mW lower.

The two diagrams below show the power available on the DSI-AD2 bus in relation to
the line length and the wire diameter. The table can then be used to determine the
number and type of system phones that can be connected to the DSI-AD2 bus under
the given conditions. The power available can be calculated by measuring the loop re-
sistance where the wire diameter is known.
Due to the different hardware versions of the radio units, basic systems and interface
cards, the power available on the DSI-AD2 bus is not the same in every case:

Mitel 415/430 as of R4.1 117

syd-0580/1.2 – R4.1 – 08.2016
Installation

Power available A:

• Applies to all the system phones of the MiVoice 5300 series and the Office series.
• Applies to the SB-4+/SB-8 DECT radio units with hardware version "-1".
• Applies to the SB-4+/SB-8 DECT radio units with hardware version "-2" if they are
not connected to a basic system with hardware version "-2" or are not connected to
an EADP4 interface card with hardware version "-3".

3000 500
2900 d: Wire diameter 480
2800 460
d = 0.6 mm
2700 440
d = 0.5 mm
2600 420
Power available A on the DSI-AD2 bus Pmax [mW]

2500
d = 0.4 mm
400
2400 380
d=0.6mm
2300 360
d=0.5mm
2200 340
2100 320
Pmax [mW]

Loop resistance R [Ohm]

d=0.4mm
2000 300
1900 280
1800 260
1700 240
1600 220
1500 200
1400 180
d=0.4mm
1300 160
1200 140
R [Ohm] d=0.5mm
1100 120
d=0.6mm
1000 100
900 80
800 60
700 40
600 20
500 0
0

50

100

150

200

250

300

350

400

450

500

550

600

650

700

750

800

850

900

950

1000

1050

1100

1150

1200

Line length L [m]

Fig. 43 Power available A on the DSI-AD2 bus

118 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

Power available B:
Applies to the SB-4+/SB-8 DECT radio units with hardware version "-2" if they are con-
nected to a basic system with hardware version "-2" or to an EADP4 interface card with
hardware version "-3".

3600 620
3500 600
d: Wire diameter
3400 580
d = 0.6 mm
3300 560
d = 0.5 mm 540
3200
3100 d = 0.4 mm 520
3000 d=0.6mm 500
Power available B on the DSI-AD2 bus Pmax [mW]

2900 d=0.5mm 480

2800 460
2700 440
Pmax [mW] d=0.4mm
2600 420
2500 400
2400 380
2300 360

Loop resistance R [Ohm]

2200 340
2100 320
2000 300
1900 280
1800 260
1700 240
1600 220
1500 200
1400 180
d=0.4mm
1300 160
1200 140
R [Ohm] d=0.5mm
120
1100
d=0.6mm 100
1000
900 80
800 60
700 40
600 20
500 0
0

50

100

150

200

250

300

350

400

450

500

550

600

650

700

750

800

850

900

950

1000

1050

1100

1150

1200

Line length L [m]

Fig. 44 Power available B on the DSI-AD2 bus

Notes
– If another system phone is operated on the DSI-AD2 bus in addition to an MiVoice 5361,
MiVoice 5370 or MiVoice 5380, at least one phone must be powered by a local power supply
unit.
– An MiVoice 5370 or MiVoice 5380 with an MiVoice M535 expansion key module always
requires a power supply unit.
– An MiVoice 5380 with 3 MiVoice M530 expansion key modules always requires a power
supply unit. With 2 expansion key modules the use of power supply unit depends on the line
length and the line cross-section.

Mitel 415/430 as of R4.1 119

syd-0580/1.2 – R4.1 – 08.2016
Installation

Automatic detection of critical power supply situations

Only MiVoice 5360, and phones of the Office series:
When a system phone (or a second such phone) is connected to the DSI bus, the max-
imum power input is automatically determined; all the system phones (incl. expansion
key module and alphanumerical keyboard) connected to the interface are taken into
account. The maximum power available is also determined based on the calculated
line length (assumption: Diameter = 0.5 mm). If the calculated power available is below
the maximum possible power input of the connected system phones, the message
Power supply critical xy m is generated on the phones connected last (accuracy ap-
prox.150 m).
System phones MiVoice 5361, MiVoice 5370 and MiVoice 5380 only:
During start-up, these system phones carry out a detailed measurement of the availa-
ble power. A warning is shown on the display if the result is inadequate: Line power too
weak: External power supply required!

Notes
– Depending on the power available based on the line length on the DSI-AD2 bus the ringing
and hands-free volume decreases accordingly.
– The backlighting of the MiVoice 5380 display is brighter if the phone is powered by a power
supply unit.

Rating examples
Example 1:
MiVoice 5370
Maximum power requirements as per Tab. 52: 1220 mW
Fig. 43 indicates:

• Maximum line length for a wire diameter of 0,4 mm: 840 m

• Maximum line length for a wire diameter of 0,5 mm: 1200 m
• Maximum line length for a wire diameter of 0,6 mm: 1200 m

Example 2:
An MiVoice 5380 with 2 MiVoice M530 expansion key modules
Power requirements as per Tab. 52: 1340 + 300 + 300 = 1940 mW.
Fig. 43 indicates:

• Maximum line length for a wire diameter of 0,4 mm: 520 m

• Maximum line length for a wire diameter of 0,5 mm: 820 m
• Maximum line length for a wire diameter of 0,6 mm: 1170 m

Example 3:

120 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

Evaluation of an existing line installation

Line diameter: 0.5 mm
Loop resistance: 120 Ω
Fig. 43 indicates:

• Line length: 660 m

• Power available: 2120 mW

Cable Requirements
Tab. 53 Requirements for an DSI bus cable
Core pairs × cores 1×2o1×4
Stranded yes1)
Wire diameter, core 0.4…0.6 mm
Screening recommended
Characteristic impedance < 130 Ω (1 MHz)
1) Note: max. 25 m can be crossed unstranded.
(CH: Applies also to cable type G51)

Installation rules
• If an Mitel DECT radio unit is used, do not connect any other system phone to the
same DSI bus.
• Do not use any terminating resistors at the bus extremity.
• Avoid using different cable cross-sections on the same bus
• Use the supplied cables for connecting the system phones
• Cabling of AD2 terminals is restricted to pairs of a separate dedicated cable(s).1).

Terminals
The following system terminals can be operated on the DSI-AD2 bus:

• MiVoice 5300 series system phones2)

• Mitel DECT radio units

The system phones on an DSI-AD2 bus are addressed via a single-digit terminal selec-
tion digit (TSD).
Example:
The address of a system phone with TSD 2 on DSI interface 3.5 is 3.5-2.
1) Applies in Australia only
2) Office 10, Office 25, Office 35, Office 45/45pro are supported as before

Mitel 415/430 as of R4.1 121

syd-0580/1.2 – R4.1 – 08.2016
Installation

4. 7. 3. 2 BRI-S terminal interfaces

With the appropriate interface cards and Wiring Adapters, BRI-S terminal interfaces
can be made available at RJ45 sockets 1.x...4.x (for Mitel 415 only 1.x and 2.x). The
possible RJ45 sockets are highlighted in colour in the figure below.

Fig. 45 Connection possibilities for BRI-S terminal interfaces

Notes
– Some of the interfaces can be configured on BRI-T using the wiring adapters (see "Wiring
Adapter", page 98).
– The maximum number of interfaces per communication server has to be taken into account
(see Tab. 30).

Connection
Tab. 54 Connection of BRI-S terminal interfaces
Communication server Cable cores Connection socket
BRI-S sig- BRI-S sig-
Socket Pin Pin Socket
nal nal
1 – – 1
2 – – 2
3 c c 3


4 f f 4


5 e e 5

6 d d 6
7 – – 7
8 – – 8

S bus configuration
The S bus is a four-wire, serial ISDN bus based on the DSS1 protocol (ETSI standard).
It starts in each case at an BRI-S interface of the communication server. Four bus con-
figurations are possible, depending on the line length and the number of terminals:

122 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

Tab. 55 S bus configurations depending on line length and the number of terminals.
S bus Short Short, V-shaped Long Point-to-point
Length (max.)
Server ↔ terminal 150 m 2 × 150 m 500 m 1’000 m
Terminal 1 ↔ Terminal 4 – – 20 m –
Number of terminals (max.) 8 8 4 1

Note
The maximum number of terminals per S bus depends on the power requirements of the termi-
nals (see "Restrictions", page 124).

8. Connection
1. 2. 3. point
Communica-
2 x 100 Ω
tion server

max. 150 m

Fig. 46 S bus, short

Communication
server

(Main)
max. 3 m

distribution 8. Connec-
1. 2. 3. frame tion point

2 x 100 Ω 2 x 100 Ω

max. 150 m max. 150 m

Fig. 47 S bus, short, V-shaped

4. Connection
1. 2. point
Communica-
tion server 2 x 100 Ω

max. 20 m

max. 500 m

Fig. 48 S bus, long

Mitel 415/430 as of R4.1 123

syd-0580/1.2 – R4.1 – 08.2016
Installation

Connection
point
Communi-
cation 2 x 100 Ω
server

max. 1000 m

Fig. 49 S bus, point-to-point

Greater distances (up to 8km) can be achieved using a standard commercial S bus ex-
tension.

Restrictions
The maximum number of terminals per S bus is further restricted by the power require-
ments of the terminals and their supplementary equipment:

Tab. 56 Power balance on the S bus

Power available [W]
S bus short 51)
S bus, long 3.51)
1) These values are based on a wire diameter of 0.5 mm.

The number of terminals is the sum of the power requirements of the individual termi-
nals and the power available on the S bus.

Connection sockets
RJ45, 8-pin
100 Ω

1 a
2 b
1 c 3 c
2
3 f 4 f Front view of
4
e
65 5 e RJ45
7 d 6 d
8
7 g
100 Ω

8 h

Fit resistors at bus extremity only

Fig. 50 RJ45 connection, single socket

124 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

RJ45, double

1
2
c 3
f 4 Front view of
e 5 RJ45
d 6
7
8

Connect housing
screens

1
2
3
4
5
6
7
2x100 Ω 8

Fit resistors at bus extremity only

Fig. 51 RJ45 connection, double socket

Installation rules
Always terminate the bus extremity with 2 × 100 Ω (0.25 W, 5%)!

Note
Circuit type as per EN/IEC 60950: SELV

Cable Requirements
Tab. 57 Requirements for an S bus cable
Core pairs × cores 1 × 4 or 2 × 2
Stranded yes
Wire diameter, core 0.4…0.6 mm
Screening recommended
Ohmic resistance < 98 Ω/km (conductor), < 196 Ω/km (loop)
Characteristic impedance < 125 Ω (100 kHz), < 115 Ω (1 MHz)
Wave attenuation < 6 dB/km (100 kHz), < 26 dB/km (1 MHz)
Near/crosstalk attenuation > 54 dB/100 m (1 kHz to 1 MHz)

Mitel 415/430 as of R4.1 125

syd-0580/1.2 – R4.1 – 08.2016
Installation

Terminals
The ETSI protocol must be set in the interface configuration.
Up to 8 terminals of different types can be connected to one S bus.

• Standard ISDN terminals

• ISDN Terminal Adapter
• PC with ISDN card
• Group 4 fax machines1), etc.

Two call connections are possible simultaneously for each S bus.

4. 7. 3. 3 FXS terminal interfaces

The FXS terminal interfaces of the mainboard are permanently routed to the front
panel and labelled accordingly. With the appropriate interface cards and Wiring Adapt-
ers, additional FXS terminal interfaces can also be made available at the RJ45 sockets
1.x...4.x (with Mitel 415 only 1.x and 2.x). The possible RJ45 sockets are highlighted in
colour in the figure below.

Fig. 52 Connection possibilities for FXS terminal interfaces

Tip
To be able to make emergency calls even in the event of a mains power failure, you have the
possibility of running up to 8 analogue FXS lines via the EFOP emergency fan-out panel. In the
event of a power failure the EFOP switches the connected analogue phones automatically and
directly over to the analogue FXO exchange lines (see "Emergency fan-out-panel (EFOP)",
page 132).

1) Not possible within an AIN

126 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

Connection
Tab. 58 Connection of FXS terminal interfaces
Communication server Cable cores Connection socket
Analogue Analogue
Socket Pin Pin Socket
signal signal
1 – – 1
2 – – 2
3 – – 3


4 a a 4


5 b b 5

6 – – 6
7 – – 7
8 – – 8

Multifunctional FXS interfaces

The analogue interfaces of the FX cards are multifunctional. Depending on the terminal
or function they are configured individually in the Interface configuration using and
switched over internally accordingly.

Tab. 59 Mode of the FXS interfaces

FXS mode Socket
Phone/fax Analogue DTMF and pulse dialling terminals such as phones, fax, modem, answering
machines, etc.
2-wire door Analogue two-wire door intercom
Control output Ports for switching external equipment.
Control input Ports for switching internal switch groups.
General bell Commercial auxiliary bells

After a first start all the FXS interfaces are configured on Phone / Fax.

Warning
Terminals connected to FXS interfaces can be damaged if the configuration of the FXS inter-
face mode is unsuitable.

Note
Circuit type as per EN/IEC 60950: TNV-2

Mitel 415/430 as of R4.1 127

syd-0580/1.2 – R4.1 – 08.2016
Installation

FXS mode: Phone/fax

In this mode the following analogue terminals can be connected:

• Analogue phones with DTMF or pulse dialling (earth key is not supported)
• Radio units for cordless phones
• Group 3 fax1)
• Answering machines
• Modem

FXS interface

Fig. 53 Connection for FXS mode: Phone/fax

The no-load voltage at the ports is approx.53 VDC. The loop current is limited to 25
mA.

Tab. 60 Cable requirements for FXS mode: Phone/fax

All ports
Core pairs × cores 1×2
Stranded only with lengths > 200 m
Wire diameter, core 0.4 … 0.8 mm
FXS resistance max. 2 × 625 Ω
Line length 0.6 mm diameter max. 10 km
Screening not required

1) Transmission with the T.38 protocol is recommended for Fax over IP. The corresponding media re-
sources need to be allocated.

128 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

FXS mode: 2-wire door

In this mode 2-wire door intercoms with DTMF control functions can be connected. The
no-load voltage in this mode is 24 VDC. The loop current is limited to 25 mA.

FXS interface

Fig. 54 Connection for FXS mode: 2-wire door

Tab. 61 Cable requirements for FXS mode: 2-wire door

Core pairs × cores 1×2
Stranded only with lengths > 200 m
Wire diameter, core 0.4 … 0.8 mm
FXS resistance max. 2 × 200 Ω
Line length 0.6 mm diameter max. 3 km
Screening not required

FXS mode: Control output

If an FXS interface is configured as a control output, the signal can be used to control
external devices or equipment (e.g. heating, alarm or outdoor lighting systems).
The no-load voltage is 24 VDC; the current is limited to 25 mA. A connected relay must
be of the type 24 VDC and must not draw more than 300 mW in power.
There are no special requirements for the cables.

Warning
Control outputs must have a floating connection.

Mitel 415/430 as of R4.1 129

syd-0580/1.2 – R4.1 – 08.2016
Installation

a max. 25mA [1]

24 VDC
b

FXS interface

[1] The diode is necessary, in order to avoid unwanted voltages at the control output during the the start-up phase of
the communication server.

Fig. 55 Connection for FXS mode: Control output

See also
Besides the control outputs on FXS interfaces control outputs on ODAB cards can also be used
to control external devices and equipment (see "Equipment on the ODAB options card",
page 138).

FXS mode: Control input

If FXS interfaces are configured as control inputs, one or more of the switch groups
can be switched between Positions 1, 2 and 3. An external switch or a relay is con-
nected for this purpose. An LED can be connected to the circuit to indicate the switch
state. The no-load voltage is 24 VDC; the current is limited to 25mA.
The permissible switch and loop resistances are as follows:

• Active state (On): < 1 kΩ

• Passive state (Off): > 4 kΩ

There are no special requirements for the cables.

Warning
Control inputs must have a floating connection.

a 25mA

24 VDC
b

FXS interface

Fig. 56 Connection for FXS mode: Control input

130 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

In the switch group configuration in ( =xb) the ports are assigned to the control inputs
of a switch group. To be able to control all 3 switch positions of a switch group, you
need 2 control inputs which switch the switch position of the switch group depending
on the status.

Tab. 62 Switch group control via the control inputs

FXS control input 1 FXS control input 2 Switch positions of the switch group
Off Off Position 1
On Off Position 2
any On Position 3

Other conditions:

• The same control inputs can control one or more switch groups.
• The same switch group can only be switched by the 2 assigned control inputs.
• Control of the switch groups using the control inputs takes priority over control using
function codes.

See also
The control inputs of ODAB cards can also be used to control switch groups (see "Equipment
on the ODAB options card", page 138).

FXS mode: General bell

One FXS interface per communication server can be configured for the connection of a
general bell. It is possible to use commercial auxiliary bells designed for connection in
parallel to analogue terminals as a general bell. However the impedance of the con-
nected general bell (or total impedance in the case of several devices connected in
parallel) must not fall below 1 kΩ. The ringing voltage is 48 VAC. A 48 V relay must be
interposed when connecting a large number of auxiliary bells.

48 VAC
b

48 VAC
FXS interface

Fig. 57 Connection for FXS mode: General bell

See also
"General bell on FXS interface" in the "System Functions and Features" System Manual.

Mitel 415/430 as of R4.1 131

syd-0580/1.2 – R4.1 – 08.2016
Installation

4. 7. 4 Emergency fan-out-panel (EFOP)1)

To be able to make emergency calls even in the event of a mains power failure, you
have the possibility of running up to 8 analogue FXO exchange lines via the EFOP
(emergency fan-out-panel). In the event of power failure, the EFOP automatically and
directly switches over exchange lines to up to 8 analogue phones.
The EFOP fan-out-panel also monitors the voltage of the FXS lines to the communica-
tion server. If for example ports are switched off due to overloading, the corresponding
exchange lines switch over automatically and directly to the analogue phones.
3671 );6 3671 );6

3671 );2 3671 );2

Fig. 58 Front panel, EFOP fan-out-panel

In the following, these analogue phones are referred to as emergency phones. In nor-
mal operation emergency phones act like ordinary internal phones. Only phones capa-
ble of operating without their own power supply are suitable as emergency phones.
Both DTMF and pulse dialling phones are supported. It is recommended to identify
emergency phones as such.
The fan-out panel EFOP takes up the space of one height unit in a rack and can be fit-
ted directly above or below the communication server.

Detailed Description
The block diagram below illustrates how the EFOP fan-out-panel operates. The lines
are switched over by relays. When relays are in a de-energised idle state, the emer-
gency phones are connected directly with the analogue exchange lines (PSTN). For
each port the relay switching status is indicated by an LED.

1) Available as of R2.1 SP1

132 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

PSTN

EFOP 1… 8 1… 8
Mains power
115/230 VAC 1… 8

AC / DC
C o n tro l

V oltage
detec tion

1… 8 1… 8

FXS FXO

Communication server

Fig. 59 Block diagram, EFOP fan-out-panel

Tab. 63 LED on the EFOP fan-out-panel

8 LEDs (2 x LED 1...4) Meaning Result
All LEDs lit Normal operation All the emergency phones and
the analogue exchange lines are
connected with the ports of the
communication server.
Individual LEDs off There is no power to these FXS lines. Possible The emergency phones on these
causes: ports are directly connected with
• The FXS card is defective. the corresponding analogue
• Individual FXS lines to the communication server exchange lines.
are interrupted.
All LEDs off All the FXS lines are without power. Possible All the emergency phones are
causes: directly connected with the corre-
• The power supply to the communication server sponding analogue exchange
has failed or there is a complete mains power out- lines.
age.
• As a result of a defect the communication server
is temporarily or permanently out of service.
• All the ports are switched off due to overloading.
• One or more FXS cards are defective.
• All the FXS lines to the communication server are
interrupted.

Mitel 415/430 as of R4.1 133

syd-0580/1.2 – R4.1 – 08.2016
Installation

Notes:
– The EFOP fan-out-panel is reset from emergency operation to normal operation with a delay
of 3 minutes. This allows the communication server to reboot after a power failure. The
delay also applies to individual FXS lines.
– If individual FXS lines are in emergency operation, the corresponding analogue exchange
line from the communication server can no longer be used. Unexpected faulty switching
may occur if an active call was being made on the FXS line and the exchange line prior to
the emergency operation.
– In emergency operation the emergency phone is connected directly with the analogue
exchange line so no exchange access prefix has to be dialled.

Connection
The EFOP fan-out-panel comprises 5 connection blocks of 10 RJ45 sockets each. The
line switchover is carried out on the two left-hand connection blocks. The three right-
hand connection blocks are used for separating the four-fold assigned RJ45 sockets
FXS1-4 and FXO1-4. The unassigned connection blocks can be used for other pur-
poses.
The diagram below shows the connection between an EFOP fan-out-panel and 4
emergency phones and 4 analogue exchange lines.

PSTN

EFOP
1 3 1 PSTN 3 FXS 1-4 1 3 1 PSTN 3 FXS 1-4 1 3 5 7 1-4 1 3

1 1
2 2
3 3
4 4

2 4 2 PSTN 4 FXO 1-4 2 4 2 PSTN 4 FXO 1-4 2 4 6 8 5-8 2 4

PSTN
2

FXS FXO
1...4 1...4

Fig. 60 Connection of EFOP fan-out-panel (example)

134 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

The patch cables are available separately in lengths of 1 and 2 m (see "Equipment
Overview", page 245).
The internal wiring of the 3 connectors right is shown in the table below. The wiring is
shown for sockets 1 - 4. Sockets 5 - 8 are wired accordingly.

Tab. 64 Wiring of sockets 1–4 in the fan-out panel EFOP

EFOP fan-out-panel Internal wiring EFOP fan-out-panel
Socket Pin Signal Signal Pin Socket
– 1 1
– 2
– 3

1a 4

1b 5


– 6
– 7
– 8
– 1 2
– 2
– 3

2a 4

1-4 1 3a 2b 5


2 3b – 6

3 2a – 7

4 1a – 8

5 1b – 1 3


6 2b – 2
7 4a – 3

8 4b 3a 4

3b 5


– 6
– 7
– 8
– 1 4
– 2
– 3

4a 4

4b 5


– 6
– 7
– 8

Mitel 415/430 as of R4.1 135

syd-0580/1.2 – R4.1 – 08.2016
Installation

Power supply
The EFOP fan-out-panel needs its own power supply and is powered by the supplied
power supply unit FSP065 via one of the two equivalent supply sockets. The power
supply unit is connected to the mains using a two-pin standard power cable.
Input values EFOP fan-out-panel 19 VDC / 0.5 A

Hazard:
Hazard due to heat generation in the event of short-circuits. The mains power supply connec-
tion must be protected with 16 A maximum in countries with 230 V mains power (for instance in
Europe), and with 20 A maximum in countries with 115 V mains power (e.g. in North America).
Please also note the following points:

• The mains connector acts as a disconnecting device and must be positioned so that
it is easily accessible.
• Original power supply units FSP065 (19 VDC / 3.42 A) are to be used exclusively.
• The EFOP fan-out-panel is designed for installation in a 19” rack and must be fitted
in rack only.

Earthing
The EFOP fan-out-panel has 4 equivalent connections for the protective earthing (see
Fig. 61).

Warning
Because analogue trunk lines are to be routed via the fan-out panel EFOP, for safety reasons
the fan-out panel must be connected to the protective earth.

136 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

Mains power

Power supply

To the earth
Copper wire yellow/ green connection
2,5 mm2 protected
4,0 mm2 unprotected

Stranded copper
yellow/ green
4,0 mm2
unprotected

EFOP
To the
communica-
tion server

Fig. 61 Connection of an EFOP fan-out-panel

Tip
Use the same mains socket to connect the power supply of the communication server and the
power supply of the EFOP fan-out-panel to the mains power. This prevents an unwanted
switchover in the event of a mains failure on the EFOP fan-out-panel only.

Mitel 415/430 as of R4.1 137

syd-0580/1.2 – R4.1 – 08.2016
Installation

4. 7. 5 Equipment on the ODAB options card

The ODAB options card contains the following equipment:

• 1 analogue terminal interface for connecting a door intercom

• Control outputs and control inputs for connecting a door intercom and/or other pur-
poses.

With the aid of jumpers the options card is configured for connecting a door intercom or
provides control inputs and control outputs:

• In the configuration as a door intercom the option card must be fitted to slot IC2
(Mitel 415) or IC4 (Mitel 430). The interfaces are then available at RJ45 sockets
2.1...2.3 (Mitel 415) and 4.1...4.3 (Mitel 430).
• If the option card is used for other purposes, it must be fitted to slot IC1 (Mitel 415)
and IC1...3 (Mitel 430). The RJ45 socket x.1 then provides two control outputs and
the RJ45 socket x.2 two control inputs.
• The possible RJ45 sockets are highlighted in colour in the figure below.

Fig. 62 Interfaces of the ODAB options card

4. 7. 5. 1 Connection of a door intercom (TFE)

If the options card is fitted to slot IC2 (Mitel 415) or slot IC4 (Mitel 430), an analogue
terminal interface is available for connecting a door intercom.

Note:
This analogue terminal interface cannot be used for other purposes as the software does not
support it.

Jumper Configuration
The jumper configuration is shown in the following diagram. Three of the four IO ports
are used for connecting the door intercom. A control input or a control output is availa-
ble for other purposes.

138 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

free control input (marked ) or control

Port 4 IO4 output (signified)

Port 3 TO

Port 2 TS Configured for connecting a door intercom

Port 1 KT

Fig. 63 Jumper configuration for connecting a door intercom

Note
If the options card is fitted on slot IC2 (Mitel 415 or slot IC4 (Mitel 430), the jumpers of Ports 1, 2
and 3 must be fitted as shown in Fig. 63.

Connection
Tab. 65 Connection in Slot 2 (Mitel 415) or Slot 4 (Mitel 430)
Communica- Communication
RJ45 RJ45
tion server server
Socket X1 Pin Signal Socket X3 Pin Signal
1 – 1 –
2 – 2 –
3 KT1 3 Tb (without DC)


4 TS2
4 Ta’ (with DC)

5 TS1 5 Tb’ (with DC)

6 KT2 6 Ta (without DC)
7 – 7 –
8 – 8 –
Socket X2 Pin Signal Socket X4 Pin Signal
1 – 1 –
2 – 2 –
3 TO2 3 –


4 IO4
4 –

5 IO4 5 –

6 TO1 6 –
7 – 7 –
8 – 8 –

Mitel 415/430 as of R4.1 139

syd-0580/1.2 – R4.1 – 08.2016
Installation

Tab. 66 Connections for the options card ODAB

IO port Socket Function Value
– Ta, Tb Floating connection (without power supply) for 600 Ω
2-wire TFE signal
– Ta’, Tb’ Non-floating connection (with power supply) 24 V / 25 mA / 600 Ω
for 2-wire TFE signal
1 KT 1, 2 Bell input 40 V / 4 mA
2 TS1, 2 Floating contact, ”Switch on / off power supply max. 24 VAC, 30 VDC, 1 A
for door intercom system”
3 TO1, 2 Floating contact, "Door release" max. 24 VAC, 30 VDC, 1 A

Connection for door intercom with 600 Ohm speech path

Door intercom (TFE) Door loudspeaker (TL)

Tb
B
Ta’
Tb’ Speech path

A Ta
TS1 Speech path
power supply
TS2
TO1
Door
TO2

115/230 VAC
KT1
Bell key switch must
KT2 be floating
ODAB

Fig. 64 Schematic circuit diagram

Points to be observed for the connection as indicated in Fig. 64:

• The door intercom system requires an external power supply.

• The signal circuit does not require a power supply.
• The speech path (DC-free) is connected to Ta and Tb.
• The door intercom system is switched on via the TS contact output.
• The door release is actuated via the TO contact output.

Warning
– The bell key switch does not require an external power supply, but must have a floating con-
nection.

140 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

– Component damage due to double power supply:

If the voice path is powered via the door intercom, it should not be connected to Ta’ and Tb’.

Connection of port 4
The free port IO4 can be used as a floating control output or as a control input. Config-
ured as a control output (O4) an external device or an external equipment can be con-
nected. Configured as a control input (I4) one or more switch groups can be switched
between position 1 and 2. Otherwise the same statements apply as described in the
following Chapter "Control outputs and control inputs".

Tab. 67 Switch group control via the control inputs

Control input I4 Switch positions of the switch groups
Passive state (Off) Position 1
Active state (On) Position 2

4. 7. 5. 2 Control outputs and control inputs

If the options card is fitted to slot IC1 (Mitel 415) or slot IC1, 2 or 3 (Mitel 430), the ana-
logue terminal interface cannot be used. However two control inputs can be used for
switching a switch group and two control outputs for controlling external devices or
equipment.

Jumper Configuration
The jumper configuration is shown in the following diagram.

Port 4 Control input 2

Port 3 Control input 1

Port 2 Control output 2

Port 1 Control output 1

Fig. 65 Jumper configuration for control outputs and control inputs

Note
If the options card is fitted in slot IC1 (Mitel 415) or slot IC1, 2 or 3 (Mitel 430), the jumpers must
be fitted as shown in Fig. 65.

Mitel 415/430 as of R4.1 141

syd-0580/1.2 – R4.1 – 08.2016
Installation

Tab. 68 Connection in slot IC1 (Mitel 415) or slot IC1, 2 or 3 (Mitel 430)
Communication Communication
RJ45 RJ45
server server
Socket X1 Pin Signal Socket X3 Pin Signal
1 – 1 –
2 – 2 –
3 O1-1 3 –


4 O2-1
4 –

5 O2-2 5 –

6 O1-2 6 –
7 – 7 –
8 – 8 –
Socket X2 Pin Signal Socket X4 Pin Signal
1 – 1 –
2 – 2 –
3 I3-1 3 –


4 I4-1
4 –

5 I4-2 5 –

6 I3-2 6 –
7 – 7 –
8 – 8 –

Tab. 69 Connections of control inputs and outputs

IO port Signal Function
1 O1-1, O1-2 Floating contact, relay 1
2 O2-1, O2-2 Floating contact, relay 2
3 I3-1, I3-2 Control input 1
4 I4-1, I4-2 Control input 2

Freely connectable relay contacts

The two freely connectable relay contacts can be used to control external devices or
equipment such as heating, alarm or outdoor lighting systems (possibly via external re-
lay for 115/230 VAC).
There are no special requirements for the cables.

Tab. 70 Relay operating data

Parameter Value
Number of changeover switches per relay 1
Insulation between the changeover switches 0.5 kV
Type of contact no (normally open, NO contact, make contact)
max. contact loading 24 VDC, 30 VAC, 1 A

142 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

Switch group interface

The routing elements of switch groups are controlled via control inputs I3 and I4. Con-
trol is effected using external switches (door contacts, time switches, etc.). The signal
no-load voltage is approx. 40 VDC, the short-circuit current approx. 4 mA.
The permissible switch and loop resistances are as follows:

• Active state (On): < 4.5 kΩ

• Passive state (Off): > 11 kΩ

Warning
The control inputs do not require an external power supply but they must have a floating con-
nection.
There are no special requirements for the cables.

Tab. 71 Switch group control via the control inputs

Control input I3 Control input I4 Switch positions of the switch groups
Off Off Position 1
On Off Position 2
any On Position 3

Other conditions:

• The switch group configuration determines which of the switch groups are switched.
• An options card’s control inputs can control one or more switch groups.
• The same switch group can only be switched by the control inputs of one options
card.
• Control of the switch groups using the control inputs takes priority over control using
function codes.

4. 7. 6 Audio interface
The audio interface can be used for the following purposes:

• to play music or an announcement to connections with callers on hold ("Music on

hold" function).
• to play music or an announcement for the announcement service (announcement
prior to answering), voice mail greetings or for "Music on hold" and then to store it as
a wave file.

Any playback equipment (tape recorder, CD player, etc.) with a line output can be used
as the audio source.
The customer is responsible for all copyright matters relating to any music playback.

Mitel 415/430 as of R4.1 143

syd-0580/1.2 – R4.1 – 08.2016
Installation

Fig. 66 Audio interface

Tab. 72 Technical data of the audio interface

Input impedance approx. 15 kΩ
Input level 0.1…5 V (configurable in 8 levels)
Input circuit asymmetrical
Output resistance audio source < 1 kΩ
Installation cable NF cable screened (required for low levels)
Socket 3.5 mm stereo jack
Circuit type as per EN/IEC 60950: SELV

4. 7. 7 Ethernet interfaces
The Mitel 415/430 communication servers have a 10/100BaseT 2-port LAN switch.
The Ethernet interfaces are permanently routed to the front panel and labelled accord-
ingly. The RJ45 sockets are highlighted in colour in the figure below.

Fig. 67 Connection possibilities for Ethernet interfaces

Note
Circuit type as per EN/IEC 60950: SELV

144 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

Socket
Tab. 73 Connection of Ethernet interfaces
RJ45 socket Pin Signal
1 Tx+
2 Tx–
3 Rx+


4 —

5 —

6 Rx–
7 —
8 —

Settings
The IP address can either be taken from a DHCP server in the IP network or config-
ured statically. If a DNS server is used, the communication server can also be ad-
dressed via its host name.

Tab. 74 Default values, IP address

Parameter Parameter value
IP address 192.168.104.13
Subnet mask 255.255.255.0
Gateway 0.0.0.0
DHCP yes
Host name <Model name>-<MAC-Address>1)
Example: Mitel430-00085d803100
1) This entry is hidden and does not appear in the parameter’s input field

First-start response
The IP addressing after a first start depends on whether a static IP addressing is al-
ready stored on the EIM card from a previous configuration. A static IP addressing (IP
address, subnet mask, gateway) entered manually is stored on the EIM card and re-
mains available after a first start. This means that the communication server remains
accessible via Ethernet interface in the same way as before the first start.
If no IP addressing is entered on the EIM card (e.g. after initial delivery), the communi-
cation server is started with DHCP after a first start. The communication server tries to
log on with the DHCP server and to enter its host name on the DNS server. If logon is
successful the communication server is accessible via the host name.
If the communication server cannot find a DHCP server within 90 seconds, it deacti-
vates the DHCP mode and is then accessible via the standard IP address (see
Tab. 74) with a direct connection.

Mitel 415/430 as of R4.1 145

syd-0580/1.2 – R4.1 – 08.2016
Installation

Note:
DHCP is deactivated only temporarily and is reactivated after a subsequent restart.

Cable types
The Ethernet switch on the communications server features Auto MDI/MDIX. With the
automatic detection straight or crossover LAN cables can be used for all connection
types.

Configuration
The Ethernet interfaces routed to the front panel can be configured individually in the
IP addressing ( =9g) view. In addition to Auto modes, manual settings are also possi-
ble for Speed and MDI type.

Status LED
The status of the Ethernet interface LAN1 is indicated on the LED display panel (see
"LED display", page 200).

Cable Requirements
Use commercial Cat. 5 cable, or choose a cable type with the following characteristics:

Tab. 75 Requirements for an Ethernet cable

Core pairs × cores 2 × 2 (short distances also 1 × 4)
Stranded yes
Wire diameter, core 0.4...0.6 mm
Screening yes
Category Cat. 5 minimum

See also:
For more information about the Ethernet interface on the application card, see the CPU2-S
application card installation manual.

146 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

4. 8 Installing, powering, connecting and registering termi-

nals

4. 8. 1 IP system phones
Accesses
Tab. 76 Socket connections of the IP system phones of the MiVoice 5300 IP series
PoE Ethernet interface for connection to the IP network

Socket connection for a workstation PC (integrated 100Base-T switch, available on MiVoice 5370 IP
and MiVoice 5380 IP)

Handset socket

Headset socket

Power supply socket for connecting a power supply if PoE is not available

Connect expansion key module MiVoice M530⁄MiVoice M535 (available on MiVoice 5370 IP and
MiVoice 5380 IP)

OUT IN
LAN PC

Integrated switch (MiVoice 5370 IP and MiVoice 5380 IP)

You can use the integrated 100Base-T mini-switch to connect other network terminals
(e.g. PC, printer), thereby reducing the amount of cabling required.

Power supply
If your network supports Power-over-Ethernet, the IP system phone is powered directly
via the LAN connection and there is no need to connect the power supply available as
an option.

Mitel 415/430 as of R4.1 147

syd-0580/1.2 – R4.1 – 08.2016
Installation

Tab. 77 Power over Ethernet

PoE power supply PoE power supply
RJ45 socket Pin Signal
(Variant 1) (Variant 2)
1 Rx DC+ —
2 Rx DC+ —
1 3 Tx DC- —
2
3
4 4 — — DC+
65
8
7 5 — — DC+
6 Tx DC- —
7 — — DC-
8 — — DC-

Depending on the power requirements different classes are defined in the IEEE
802.3af standard. The following table provides information on the class allocation of
the IP system phones.

Tab. 78 PoE class allocation

Class Max. load, PSE1) Max. power requirement, PD2) IP system phones
1 4.0 W 0.44...3.84 W MiVoice 5360 IP, MiVoice 5361 IP
2 7.0 W 3.84...6.49 W MiVoice 5370 IP3), MiVoice 5380 IP4)
3 15.4 W 6.49...12.95 W
1) PSE (Power Source Equipment) = power supply device, e.g. a switch
2) PD (Powered Device) = power consumer, e.g. an IP system phone
3) including an MiVoice M530 or MiVoice M535 expansion keypad
4) including up to three MiVoice M530 or MiVoice M535 expansion keypads

You can obtain information on how to operate and register the IP system phones on a
MiVoice Office 400 communication server in the WebAdmin online help.

4. 8. 2 Mitel 6700 SIP / 6800 SIP series SIP phones

Mitel SIP phones are platform-independent phones with a wide range of features. They
can also be perfectly integrated into one of the Mitel Platforms and used as a system
phone. Mitel SIP Phones on MiVoice Office 400 first support MiVoice Office 400 fea-
tures and have a separate user's guide. Many of the device-specific functions are less
significant or are not used at all. Please read the Mitel SIP administration instructions if
you wish to carry use device-specific functions or carry out device-specific settings.
Device-specific installation instructions are available for installing the phones. You can
obtain information on how to register a Mitel SIP phone on a MiVoice Office 400 com-
munication server in the WebAdmin online help.

148 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

4. 8. 3 Standard SIP phones and standard SIP terminals

For information on installation, powering and connection, please refer to the installation
instructions of the corresponding phones and terminals. Information on how to register
Mitel or third-party standard SIP phones and standard SIP terminals as internal users
in MiVoice Office 400 is given in WebAdmin.

4. 8. 4 Mobile/external phones
The integration of mobile/external phones in the MiVoice Office 400 communication
system is described in the System Manual "System Functions and Features".

4. 8. 5 OIP and other applications

Mitel Open Interfaces Platform (OIP) release 8.6 and later is also available as OIP Vir-
tual Appliance and can be installed on the same server as the Virtual Appliance com-
munication server. The operating requirements and installation instructions for the OIP
applications MiVoice 1560 PC Operator and Mitel OfficeSuite are described in the
"Mitel Open Interfaces Platform" System Manual.

4. 8. 6 Digital system phones

4. 8. 6. 1 General information
Accesses
The connections on the underside of the system phones are identified by the symbols.
The meaning of the symbols is described in the corresponding operating instructions.

DSI terminal interface

Tab. 79 DSI interface on the phone
RJ45 socket Pin Signal
1 —
2 —
3 b


4 a

5 —
6 —

Note:
The total length of the cables from the communication server to the system phone must not be
less than 10 m.

Mitel 415/430 as of R4.1 149

syd-0580/1.2 – R4.1 – 08.2016
Installation

Terminal selection
Two system phones can be connected to a DSI interface (DSI-AD2 only). The system
can only differentiate the two system phones by the position of the address switch on
the phone. The following settings are possible (TSD = Terminal Selection Digit):

• TSD1
• TSD2

Note:
In the following cases Not Configured is displayed along with the node number, the slot number
and the port number. In this state the system phone is not ready for operation:
– A terminal has been created at the connected port, but the address selection switch is incor-
rectly set.
– No terminal has yet been created at the connected port.

User allocation
In the configuration each terminal is assigned to a user or a free seating pool. If a ter-
minal has been created at the connected port and the address selection switch is cor-
rectly selected but no user or free seating pool is allocated to the terminal, the system
phone display reads No Number and indicates the terminal ID. In this state the system
phone is not ready for operation.

Terminal type
The terminal type is specified along with the configuration of the system. Lines are also
assigned to the line keys there.

Note:
If the terminal type configured is incorrect, the system phone display shows the warning Wrong
phone type. On the Office 10 the LED flashes slowly. In this situation, although the system
phone can be used for basic telephone operations, none of the added features will be available.
The terminal type must be entered via WebAdmin or on the terminal via login to the system con-
figuration.
Carrying out a logon on the system phone:
– Office 10: : Press the Foxkey twice.
– All other system phones: Long keypress (long click) on a function key. Set new phone type
appears next. Confirm with Foxkey Yes.

150 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

4. 8. 6. 2 MiVoice 5361 / 5370 / 5380

These IP system phones can be both desktop-mounted and wall-mounted.

Mounting the phone

The following points are described in detail in the User’s Guides for MiVoice 5361 /
5370 / 5380:

• Set-up as a desk phone (choice of two different set-up angles)

• Wall mounting
• Connecting one or more MiVoice M530 or MiVoice M535 expansion key modules.
• Connection of a headset to DHSG standard.

Note:
To prevent any damage to the phone, always disconnect the phone from the power supply
first before connecting a headset to DHSG standard.

Mounting the Bluetooth module

The MiVoice 5380 can also be equipped with a Bluetooth module as an option. To in-
stall (see Fig. 68), proceed as follows:

Fig. 68 Assembly of the Bluetooth module

Mitel 415/430 as of R4.1 151

syd-0580/1.2 – R4.1 – 08.2016
Installation

Warning
The system's reliability can be adversely affected by electrostatic discharges caused by touch-
ing electronic components and elements, and subsequent damage can result. Always observe
the ESD guidelines.

1. Fit foam spacers on the connector side of the Bluetooth module (for the position of
the foam spacer see ➀). The spacer ensures that the Bluetooth module sits se-
curely.
2. Carefully remove the cover for the Bluetooth module on the underside of the phone
using a suitable screwdriver (see ➁).
3. Connect the Bluetooth module. Make sure it is securely fitted (see ➂).
4. Fit the cover for the Bluetooth module back into place and press home until it snaps
into place (see ➃).

Powering the phone

The MiVoice 5360, MiVoice 5361 MiVoice 5370 and MiVoice 5380 system phones are
normally powered via the DSI bus. However there are several reasons that require
powering with a plug-in power supply:

• Long line
• 2 phones on the same bus
• 1 or more expansion key modules on the phone
• Terminal power supply of the communication server is overloaded

Only use the corresponding plug-in power supply unit with FCC connector available as
an option. It is connected either to the phone itself or, when using one or more expan-
sion key modules, on the last expansion key module.

See also
The power available on the DSI bus depending on the line length and the wire diameter, and the
power input of the system phones are described in the chapter "DSI terminal interfaces",
page 115 ff.

Connecting the phone

1. Setting the DSI bus address on the system phone’s underside:

– TSD1 = address switch on position 1
– TSD2 = address switch on position 2
2. Plug the connector into the socket-outlet.
3. If the system is configured, test the operation of the system phone.
4. Label the phone as indicated in the operating instructions.

152 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

4. 8. 6. 3 Office 25, Office 35, and Office 45/45pro

These system phones are desktop models. A wall-mounted bracket is available as an
option for Office 25 and Office 35.

Mounting the desktop model

Connect the handset cord and the phone cord to the phone as indicated in the operat-
ing instructions.

Installing the wall-mounted bracket (optional)

The wall assembly set consists of a baseplate, a wall plate and fastening screws (see
Fig. 69).

1. Secure the wall plate to the wall using the three longer screws. Feed the cord
through the middle opening on the wall plate (see ➀).
2. Remove the 4 plastic feet on the underside of the phone (see ➁).
3. Secure the baseplate of the wall assembly set to the underside of the terminal using
the 2 shorter screws (see ➂).
4. Suspend the baseplate with the phone onto the wall plate from above (see ➃) and
tilt downwards until it snaps into place (see ➄).
5. Plug the phone cord into the phone (see ➅).

Powering the phone

The system phones Office 25, Office 35, and Office 45 are powered via the DSI line.
The system phones Office 45pro need to be powered externally with a plug-in power
supply. Only use the corresponding plug-in power supply unit with FCC connector.

Connecting the phone

1. Set the DSI bus address under the system phone's designation label.
– TSD1 = Address switch not pressed (disengaged)
– TSD2 = Address switch pressed (engaged)
2. Plug the connector into the socket-outlet.
3. If the system is configured, test the operation of the system phone.
4. Label the phone as indicated in the operating instructions.

Connecting the expansion key module or the alphanumerical keyboard

The connection of the expansion key modules and the alphanumerical keyboard to
Office 35 and Office 45 is described in the relevant operating instructions.

Mitel 415/430 as of R4.1 153

syd-0580/1.2 – R4.1 – 08.2016
Installation

"
NN
NN

NN

" YNN # YNN

Y
#
Y

Fig. 69 Wall mounting of Office 25 and Office 35

154 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

4. 8. 6. 4 Office 10
The terminal is a desktop model. A wall-mounted bracket is available as an option.

Mounting the desktop model

1. Feed the connecting cable through the strain relief on the handset rest.
2. Position the handset rest as required and put the handset in place.

Installing the wall-mounted bracket (optional)

1. Feed the connecting cable through the strain relief on the wall-mounted bracket.
2. Screw the wall-mounted bracket onto the wall using the screws supplied and hook
the handset into position.

Powering the phone

The terminal is powered via the DSI line.

Connecting the phone

1. Set the DSI bus address (Fig. 70).

2. Plug the connector into the socket-outlet.
3. If the system is configured, test the operation of the terminal.
4. Label terminal.

TSD 2

TSD 1

Fig. 70 Set the DSI bus address

Note:
Make sure the TSD (address switch) is pushed in as far as the stop or the switchover will not
function correctly.

Mitel 415/430 as of R4.1 155

syd-0580/1.2 – R4.1 – 08.2016
Installation

4. 8. 7 DECT radio units and cordless phones

The locations determined for the cordless phones, charging bays and radio units dur-
ing the planning phase need to be checked against the following criteria:

• Influence on radio operation

• Ambient conditions

Influences on radio operation

Radio operation is affected by the following influences:

• Outside interference (EMC)

• Obstacles in the surrounding area affect the radio characteristic

To achieve optimum conditions for radio operation, observe the following points:

• Optimum radio operation depends on the radio unit → cordless phone line of sight.
• Walls act as an obstacle to the propagation of radio waves. Losses depend on the
wall thickness, construction material and reinforcement used.
• Do not place radio units and cordless phones in the immediate vicinity of TV sets,
radios, CD players or power installations (for reasons of EMC, e.g.distribution
boxes, rising power lines).
• Do not place radio units and cordless phones near X-ray installations (EMC).
• Do not place radio units and cordless phones near metal partitions.
• Observe the minimum distance requirements between adjacent radio units (see
Fig. 72).
• Minimum distance between cordless phones for fault-free operation: 0.2 m. (The
charging bays of the Office 135 can be linked using connecting strips. However, op-
erating several phones on interconnected charging bays can lead to malfunctions.)
• Minimum distance between charging bays with cordless phones on-hook for fault-
free operation: 0.2 m.

Ambient conditions

• When installing: Ensure convection (space for ventilation).

• Avoid excessive dust.
• Avoid exposure to chemicals.
• Avoid direct sunlight.
• See also technical data in Tab. 126.

156 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

Note:
If these requirements cannot be met (e.g.outdoor installation), use the appropriate protective
housing.

4. 8. 7. 1 Installing the radio units

Do not remove the cover of the radio unit. (Warranty protection will lapse if the cover is
removed)
Fit the mounting bracket (see Fig. 71 dimensional drawing for wall mounting). Observe
the minimum distances (see Fig. 72).
Position the DSI socket(s) near the radio unit.
Each radio unit requires one DSI bus (two optional on the SB-8): Do not connect any
other terminals.
The radio units can be powered from the communication server up to the maximum
line length of 1200 m specified for operation (wire diameter 0.5 mm). The plug-in power
supply unit for is the same as the one for the Office 135 charging bay.

160
37 100
84

ø screw : 4 mm
168

Mounting bracket

All dimensions in mm

Fig. 71 Dimensional drawing for wall-mounting the mounting bracket

Mitel 415/430 as of R4.1 157

syd-0580/1.2 – R4.1 – 08.2016
Installation

100 165 X [1] 165 100

100
170
X [1]
170
100
All dimensions in mm

[1] X = 200: Minimum distance if the radio units are connected to the same communication server (synchronous)
X = 2000:Minimum distance if the radio units are not connected to the same communication server (not synchro-
nous)
Make sure the minimum distances are observed

Fig. 72 Installation distances

Connecting the radio unit

115/230 VAC
(optional)

DSI interface

Socket 1

Socket 2

Sockets, external antennas

( SB-8ANT only)

Fig. 73 Underside of the radio units with connection points

158 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

Tab. 80 Connections on the Mitel DECT radio units

RJ12 sockets Pin Socket 1: DSI interface Socket 2: Power supply
SB-4+ SB-8 / SB-8ANT SB-4+ / SB-8 / SB-8ANT
1 Local power supply – Local power supply – Local power supply –
2 — b2 —


3 b1 b1 —

4 a1 a1 —
5 — a2 —
6 Local power supply + Local power supply + Local power supply +

If an SB-8 / SB-8ANT is operated on two DSI interfaces, it is recommended always to

use two neighbouring ports.

Mitel Advanced Intelligent Network:

As the DECT systems of the individual nodes in an AIN do not run synchronously, the two DSI
interfaces of an SB-8 / SB-8ANT must always be connected to the same node.

Tab. 81 Operating state display on Mitel DECT radio units

LED flashing (two LEDs on the SB-8) Information
green Operating state
red / green Startup procedure running
orange Transmission of DECT sequences
red Fault
not flashing and not lit LED switched off or radio unit defective or not in operation

For further display variants, see "Operating state of the Mitel DECT radio units",
page 237

4. 8. 8 Analogue phones Mitel 6710 Analogue, Mitel 6730

Analogue
The phones can be used as desktop model or as wall model.

Connecting the phone

1. Stick the connector on the longer, straight end of the handset cord on the underside
of the phone into the socket with the handset symbol until it snaps into place. Feed
the cable through the strain relief and connect the other end to the handset.
2. Feed the small connector of the phone connection cable on the rear side of the
phone into the socket until it snaps into place. Stick the connector on the other end
into the phone cord.

Mitel 415/430 as of R4.1 159

syd-0580/1.2 – R4.1 – 08.2016
Installation

Preparing the phone for message waiting indication (MWI)

The phone can detect various types of notifications (polarity reversal, high voltage and
frequency shift keying (FSK). The notification type is set with the MWI switch on the un-
derside of the phone. "0" = Off, "HV" = High voltage, "−/+" = Polarity reversal. The no-
tification type Frequency reversal (FSK) is always active, regardless of the switch set-
ting (Mitel 6730 Analogue only).
The MiVoice Office 400 communication servers support the following notification types:

Tab. 82 Supported notification types

Notification type MWI switch setting Mitel 415/430 Mitel 470
Switched off 0
Polarity reversal − and + – ✓
High voltage HV – –
Frequency reversal (FSK) No symbol ✓ ✓
(Any switch setting)

The red MWI LED under the notification key can only be controlled with the Mitel 470
communication server and the notification type Polarity reversal. Set the switch on the
underside of the phone to the symbol "−". This applies to a straight connecting cable
(provided with the phone). If the MWI LED is ON after the phone is connected, al-
though no message is waiting for the phone, the switch must be set to "+".

Notes:
– For the notification type FSK, a new message with a small envelope is displayed on the
screen of the phone Mitel 6730 Analogue. This variant is not recommended as the symbol
can be easily overlooked.
– The information in this section basically applies to analogue phones Aastra 1910 and
Aastra 1930 too. In these models the MWI switch is labelled on the rear side of the phone,
and the switch settings for polarity reversal, with PR1 and PR2.

Mounting the phone on the desktop

Feed the mounting feet into the corresponding cut-outs on the underside of the phone
until they engage. 4 different set-up angles are possible, by choosing the cut-outs and
turning the set-up feet.

Mounting the phone on the wall

1. Place the supplied drilling template for wall mounting on the wall position you want
and mark the positions for the mounting screws. Depending on the type of wall, you
may need some dowel plugs. Screws and dowel plugs are part of the delivery.
2. Put the telephone with the mounting openings over the heads of the wall screws
and pull the phone downwards to stop it.

160 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Installation

3. On the cradle is a small clamp which is flush with the cradle surface. Push it up with
a small flat head screwdriver and remove it from the phone.
4. With the cleat arm towards you and the flat side of the clamp towards the phone turn
the clamp 180° and push it again into the cut-out in the phone cradle. Press in the
clamp till it is flush with the surface and only the feet of the clamp are protruding.

Configuring keys
Configure the keys on analogue phones Mitel 6700 Analogue in the WebAdmin termi-
nal configuration. The phone must be connected during configuration so the key con-
figuration can be stored on the phone immediately. If not, you can load the key config-
uration on the phone after connecting the phone, by clicking Update key configuration
on phone.
To load the key configuration on all connected Mitel 6700 Analogue series phones,
click Update key configuration for all Mitel 6700 Analogue phones.
To load the key configuration stored in the WebAdmin from the connected phone, dial
the function code *#53.

Labelling the phone

1. Remove the cover with the logo on top of the control panel by pressing down slightly
and pushing up.
2. Pull out the designation label on the lugs, label it then push it back again into the
cut-out.
3. Carefully put back the cover with the logo, so that the paper lugs are covered.

Powering the phone

The phone is powered via the FXS line.

Mitel 415/430 as of R4.1 161

syd-0580/1.2 – R4.1 – 08.2016
Configuration

5 Configuration

This chapter describes the web-based configuration tool WebAdmin as well as

some additional options. With WebAdmin the installer configures and maintains the
communication server and its auxiliary equipment, and is supported in the process
by a set up and configuration assistant. WebAdmin offers different user interfaces for
administrators, system assistants and end-users as well as a special application for
accommodation and hotels. A context-sensitive online help provides valuable in-
structions on configuration, and step-by-step instructions. The chapter ends with
valuable information and instructions on how to configure your communication
system.

5. 1 WebAdmin Configuration Tool

This web-based configuration tool is available for the online configuration of MiVoice
Office 400 series communication servers. It offers a simple, user-friendly interface and
an online help, and with its different authorization levels it is aimed at different user
groups:

Fig. 74 WebAdmin Configuration Tool

162 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Configuration

Administrator authorization level:

The Administrator has access to all the views and functions of the configuration tool
(Expert mode). He can call up a set-up assistant, show a general configuration assis-
tant and a special hospitality configuration assistant, and configure all system parame-
ters. The administrator can switch back and forth between Expert mode and Standard
mode at any time.
Authorization level Administrator (Standard mode only):
In Standard mode the administrator has access to all the main views and functions of
the configuration tool. He can call up a set-up assistant, show a general configuration
assistant and configure the most needed system parameters.
System assistant authorization level:
The System Assistant only sees selected views of the configuration tool, and the scope
of functions is limited.
Hospitality-Administrator authorization level:
The Hospitality Administrator features all the views required to set up the Mitel 400
Hospitality Manager and the reception menu of the MiVoice 5380 / 5380 IP and specify
its default settings. A link can also be used to start the Mitel 400 Hospitality Manager
(see "Mitel 400 Hospitality Manager", page 164).
Receptionist authorization level:
This access starts the Mitel 400 Hospitality Manager directly (see "Mitel 400 Hospitality
Manager", page 164).
The WebAdmin is included in the file system of each communication server of the
MiVoice Office 400 family and does not have to be installed separately.
Access:
To access the registration page of WebAdmin, enter the communication server IP ad-
dress in your browser. You can find the registration data of a new communication
server in the chapter "Default user account for initial access", page 169.
If you do not know the communication server IP address, search for the communica-
tion server on the IP network with the auxiliary application System Search (see
page 166).

Note:
With the web-based administration two users are able to access the same communication
server simultaneously (and no fewer than five users at the Receptionist authorization level).
This can cause confusion if a configuration is being carried out in the same places.

Mitel 415/430 as of R4.1 163

syd-0580/1.2 – R4.1 – 08.2016
Configuration

5. 1. 1 Integrated and auxiliary applications

Mitel 400 Hospitality Manager
The Mitel 400 Hospitality Manager is a web-based application for receptionists in the
hospitality sector. It provides a clear, at-a-glance list view or floor-by-floor view of the
rooms and features functions such as check-in, check-out, notification, wake-up call,
retrieval of call charges, maintenance list, etc.

Fig. 75 Mitel 400 Hospitality Manager

Mitel 400 Hospitality Manager is integrated into WebAdmin and subject to a licence.
Access:
You have access to two types in Mitel 400 Hospitality Manager:

• Register on the WebAdmin registration page with the access data of a user account
to which an authorisation profile with the WebAdmin authorisation level Receptionist
has been assigned. This starts Mitel 400 Hospitality Manager directly.
• Register on the WebAdmin registration page with the access data of a user account
to which an authorisation profile with the WebAdmin authorisation level Hospitality
administrator has been assigned. Click the menu tree on the left side on the Hospi-
tality Manager input.

164 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Configuration

Self Service Portal

With the Self Service Portal, users can configure and adjust personal phone settings,
such as key configuration, labels, display language, directly and independently on the
PC. Users also have access to their personal mail boxes; they can configure and con-
trol presence profiles, personal call routing and call transfers, and create or search for
private phone book contacts.

Fig. 76 Self Service Portal

The Self Service Portal application is integrated into WebAdmin.

Access:
You can access a user's Self Service Portal by entering any of the following combina-
tions (registration data) on the WebAdmin registration page:

• Call number + PIN

• Windows user name + PIN
• Windows user name + password

The standard PIN "0000" is accepted, but must be changed during first login. You can
choose any 2 to 10-digit number combination.

Mitel 415/430 as of R4.1 165

syd-0580/1.2 – R4.1 – 08.2016
Configuration

System Search
The auxiliary application System Search is an independent help tool for detecting
MiVoice Office 400 series communication servers on the IP network. System Search
MiVoice Office 400 finds all communication servers connected to the IP network, pro-
vided they are located on the same subnet as the PC and are at least compatible with
Software release 1.0. (does not apply to Virtual Appliance). With System Search you
can also see the name, type, sales channel, EID number and operating mode of a se-
lected communication server. You can modify its IP address or directly start the
WebAdmin administration tool.
Moreover, with System Search you can load language files for the audio guide, Mitel
phones as well as for the user interface and online help of WebAdmin, Hospitality Man-
ager and Self Service Portal via MiVoice Office 400 FTP server onto your PC and up-
load them afterwards to the communication server with WebAdmin. Thus, an update
or an upload of new languages is possible without an internet connection of the com-
munication server.
With System Search you can also upload system software in boot mode (Emergency
Upload). This is particularly useful if the current software application on the communi-
cation server is no longer able to run or if you wish to load an older software application
(does not apply to Virtual Appliance).

Fig. 77 System Search

166 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Configuration

You can download the System Search application via Software download server. For
this, you must first log on to the Extranet with your partner login. The application must
not be installed but is started with a double-click.

Note:
For Virtual Appliance, System Search is only available for downloading language files for
the audio guide, Mitel SIP terminals as well as for the WebAdmin, Hospitality Manager
and Self Service Portal user interfaces and online help.

Mitel 400 WAV Converter

The auxiliary application Mitel 400 WAV Converter is an independent help tool for
compressing audio data. If the integrated voice mail system is operated in expanded
mode (Mitel 415/430 only), all the audio data must be available in compressed G.729
format. To be able to continue using existing, uncompressed greetings in G.711 format,
you need to compress them first. Mitel 400 WAV Converter is available for this.

Fig. 78 Mitel 400 WAV Converter

You can download the application via Software download server. For this, you must
first log on to the Extranet with your partner login.
The application must not be installed but is started with a double-click.

Mitel 415/430 as of R4.1 167

syd-0580/1.2 – R4.1 – 08.2016
Configuration

5. 2 Access types
There are the following possibilities to access the communication server with
WebAdmin:

• In the LAN with an Ethernet cable (directly or via a switch)

• Externally via SRM (secure IP remote management)

Note:
External access via dial-up access (ISDN/analogue) is only recommended on some conditions,
for performance reasons.

First access on LAN with System Search

For a first access to the communication server, it is easier if your computer is located
on the same subnet as the PC. If this is not the case, you can also connect the com-
puter directly to the communication server using a LAN cable.
With the auxiliary application System Search (see page 166) the communication
server (and other MiVoice Office 400 series communication servers on the same sub-
net) is searched and displayed. It is advisable to directly deactivate the normally acti-
vated communication server DHCP via System Search and to manually enter a static
IP address, the subnet mask and IP gateway. After login via the standard access (see
"Default user account for initial access", page 169), the data is stored in the communi-
cation server.

See also:
If you are setting up an MiVoice Office 400 communication system for the first time, we recom-
mend to you the Getting-started package (see "First steps...", page 37).

Accessing the communication server on the LAN

If the communication server IP address is known, it can be entered directly in the ad-
dress line of a web browser. WebAdmin is started after the access data is entered. The
computer only needs to be located on the same LAN, but not necessarily on the same
subnet.

Accessing the communication server from outside

For remote access to the communication server, we recommend SRM (Secure IP Re-
mote Management) secure IP remote management. For this, you need to install an
SRM agent on your computer with which you can set up a connection to the SRM
server. Thereafter, the SRM server calls the communication server via PSTN and
sends it the connection parameters. The communication server now sets up a secure
connection to the SRM server which switches together them with the connection to the
SRM agent.

See also:
You can find instructions on how to set up Secure IP Remote Management in the WebAdmin
help on the IP remote management (SRM) view ( =mw).

168 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Configuration

5. 3 User access control

Access to the configuration is password-protected. Any user wanting to log in to a com-
munication server is prompted for his user name and password (access data).

5. 3. 1 User accounts and authorization profiles

A user's authorizations are regulated by authorization profiles, which are assigned to
the user accounts.

5. 3. 1. 1 User accounts
Default user account for initial access
When a new communication server is opened or after a first start, the default user ac-
count (admin) and several authorization profiles are created. The default user account
is linked with the authorization profile Administrator. This authorization profile is as-
signed the administration rights for the User access control for Audio services and for
WebAdmin at the Administrator authorisation level.
The required user accounts and authorization profiles can be set up using the default
user account.
To access the default user account (Default User Account) enter the following:

Tab. 83 Standard user account and standard password

User name admin
Password password

Note:
To prevent unauthorised access to the communication server, it is necessary to modify the
default password during first access. For password selection and input, see "Password syntax",
page 171.

Other predefined user accounts

The predefined user account MMCC is meant for operating a Mitel Mobile Client Con-
troller.
The two predefined user accounts blustar and bucs are meant for BluStar terminals
and for a BluStar server.
You can see the predefined user accounts in the User account ( =a7) view.

Note:
The predefined user accounts cannot be deleted.

Mitel 415/430 as of R4.1 169

syd-0580/1.2 – R4.1 – 08.2016
Configuration

Personal user accounts

Subject to the administration right for user access control, personal user accounts can
be created in user access control ( =a7) and assigned some authorisation profiles.
The following rules apply to user names selection and spelling:

• An user name must consist of a minimum of 1 and a maximum of 25 alphanumerical

characters.
• Unlike the passwords, the user names are not case sensitive.
• The following special characters can be used: ?, /, <, >, -, +, *, #, =, full stop, comma
and space.
• German umlauts (e.g. ä, ö, ü) and other diacritical characters (e.g. é, à, â) are not
permitted.
• User names must be unique throughout the system.
• The user name and password must not be identical.

5. 3. 1. 2 Authorization profiles
Predefined authorization profiles
The predefined authorization profiles are assigned administration rights and interface
user rights. An overview of all predefined authorisation profiles with their administration
and access rights is available in the WebAdmin help on the Authorization profile
view( =u5).

Personal authorisation profiles

Subject to administration right for the administration right for user access control, no
personal authorisation profiles can be protected and assigned the desired rights. A de-
scription of the various administration and access rights is available in the WebAdmin
help on the Authorisation profile view( =u5).

Note:
Authorization profiles can only be viewed or created by Administrators in Expert mode.

5. 3. 2 Passwords
To ensure that the communication server can only be configured by authorized person-
nel, access to the configuration is password-protected.

170 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Configuration

5. 3. 2. 1 Password syntax
The following rules apply to password selection and spelling:

• A password must consist of a minimum of 8 and a maximum of 10 alphanumerical

characters.
• Unlike the user names, the passwords are case sensitive.
• The following special characters can be used: ?, /, <, >, -, +, *, #, =, full stop, comma
and space.
• German umlauts (e.g. ä, ö, ü) and other diacritical characters (e.g. é, à, â) are not
permitted.
• The default password password is not permitted.
• The password must not be the same as the user name.

5. 3. 2. 2 Change password
Any user who has been assigned an authorisation profile in which the User access
control administration right is released is authorised to modify the passwords of all user
accounts. It is therefore advisable to assign this administration right restrictively.
Users whose password has been changed are prompted to enter their newly assigned
password the next time they log in. The same applies to users whose accounts have
been newly created.
Users without the administration right User access control can only change their own
password.

5. 3. 2. 3 Access with incorrect password

After 15 failed login attempts using incorrect passwords the corresponding user ac-
count is blocked; it can then only be reactivated by a user with the User access control
administration right. He then replaces the old password with a new one. The next time
he logs in, the corresponding user is prompted to change the password and enter the
new one he has been assigned.

5. 3. 2. 4 Lost password
If another user has also been defined with the User access control administration right
released, he can simply overwrite with a new password the password lost by another
user. The next time he logs in, the corresponding user is prompted to change the pass-
word and enter the new one he has been assigned.

Mitel 415/430 as of R4.1 171

syd-0580/1.2 – R4.1 – 08.2016
Configuration

If the passwords of all administrators are lost, access can still be gained locally without
a password (see "Password-free access", page 172).

5. 3. 3 Password-free access
The control pilot key on the front panel can activate a function that enables via pass-
word-free, local access via LAN with administration right User access control. This is
useful for example if all the passwords have been lost. The procedure is described in
"Enabling / disabling password-free access", page 210.
There is no password-free access for remote maintenance.

5. 3. 4 Automatic exit from the configuration

Access to the configuration is interrupted if no changes are made to a parameter value
or the navigation system is not used during a specific timeout.

5. 3. 5 Access log
An access log with 20 entries is drawn up for each user account so that the history of
accesses to the configuration can be tracked. Denied access attempts using erroneous
or incorrectly type passwords are also logged. The logs can be read by each user (au-
thorization level) Administrator in Expert mode required).

Retrieving the log data

The system monitors all the accesses and failed access attempts and saves them in
the file system of the communication server. These lists can be retrieved locally or re-
motely. ( =ez or =z3).

CLIP verification
If in the general maintenance settings ( =t0) of the parameter CLIP required is acti-
vated, remote maintenance is only possible if the retrieving party is using a CLIP. The
CLIP number is also recorded by the access log.

Entering the processes in the log

Each access attempt generates an entry in the corresponding list.
In case of remote maintenance an entry will not be generated if remote maintenance is
barred or if CLIP required is activated in the configuration and no CLIP is received.

172 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Configuration

5. 4 Remote access
With a remote maintenance access the user is authenticated using his user name and
password. The user account must also be assigned an authorization profile in which
the interface access Remote maintenance dial-up access is enabled. This also applies
to SRM (Secure IP Remote Management), secure IP remote management.

5. 4. 1 Access enabled by local users

Remote maintenance access can be enabled in two ways:

• Using function codes (see page 173)

• With WebAdmin

It can be revoked again automatically or manually.

All enabling types have equal authorization status. This means that remote mainte-
nance access can be enabled using a function code for example, and then barred
again using the WebAdmin in general maintenance settings ( =t0).
When remote maintenance access is activated, the event message Remote mainte-
nance on is sent to the local printer and to all the terminals registered in message
group 8.
If remote maintenance is released, this can be recognised in the WebAdmin title bar of
the symbol.
Remote maintenance access can be enabled or barred using the function codes both
from the idle state and the talk state, e.g. after an enquiry.
The authorisation to activate or bar remote maintenance access using the function
code is defined and granted to the user with the parameter Remote maintenance ac-
cess in a permission set ( =cb).
After a first start of the communication server, the authorizations of all users are re-
stricted.

Note:
It is advisable not to keep the remote maintenance access permanently activated. This ensures
that the communication server data cannot be manipulated from a remote location by unauthor-
ized persons.

5. 4. 2 Function code for remote maintenance access

Tab. 84 Function code for remote maintenance access
Enable/bar a one-off remote maintenance access *754 / #754
Enable/bar a one-offpermanent maintenance access *753 / #753

Mitel 415/430 as of R4.1 173

syd-0580/1.2 – R4.1 – 08.2016
Configuration

When remote maintenance access is enabled using function code *754, access will
automatically be barred again once the remote maintenance process has been com-
pleted. It is possible to bar remote maintenance manually using #754 before it is initi-
ated.
Remote maintenance access can be enabled permanently using the function code
*753. To bar access, the authorized user must enter the function code #753 manually.
The enabling or barring of remote maintenance access using the function code is sig-
nalled in each case by an acknowledgement tone.
Remote maintenance access can also be enabled or barred in WebAdmin, if the rele-
vant authorization has been given.

Note:
In a QSIG network it is important to ensure that the authorization to change the remote mainte-
nance access is also denied to unauthorized PISN users. Otherwise, a PISN user would be
able to use an abbreviated dialling number defined for the destination PINX and containing the
appropriate function code to change the remote maintenance access to the destination PINX.

Mitel Advanced Intelligent Network:

In an AIN the remote maintenance access of all the nodes depends on the setting in the Master.
If remote maintenance access is enabled in the Master, both the AIN configuration and the
offline configuration of the satellites are enabled.
Remote maintenance access via an external dial-up connection to the AIN is also secured and
has to be explicitly enabled (see "Enabling / disabling the dial-up connection to the AIN",
page 210). This is irrespective of whether dial-up access is via a satellite or directly to the Mas-
ter.

5. 4. 3 Function keys for remote maintenance access

On system phones the function code for enabling/barring remote maintenance access
can be stored under a function key, provided the user has the appropriate authoriza-
tion.
The relevant LED lights up if remote maintenance access is enabled once or perma-
nently.
The relevant LED goes off as soon as remote maintenance access is denied again, ei-
ther automatically or manually, using the function code or WebAdmin.

174 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Configuration

5. 5 Configuring
The configuration steps are based on the information determined during the planning
and, where applicable, the installation.
Whenever possible, use the planning and ordering software Mitel CPQ, to set up your
communication system. Mitel CPQ can be operated online after logging in at
Mitel Connect https://connect.mitel.com . Mitel CPQ not only calculates the required
hardware – it also lists the required licences for the planned operation.

See also:
If you are setting up an MiVoice Office 400 communication system for the first time, we recom-
mend to you the Getting-started package (see "First steps...", page 37).

Setup wizard
The WebAdmin setup wizard takes you step by step through the setup of a basic con-
figuration and is suitable for initial communication server setup. The setup wizard is au-
tomatically called up when a new communication server is installed. Logging on as ad-
ministrator in WebAdmin (expert or default mode) allows you to also start the setup
wizard directly from the WebAdmin navigation tree.
The setup wizard comprises the following steps:

1. Activating licences
2. Setting up the IP addressing
3. Configuring media resources
4. Setting up the numbering plan
5. Setting up SIP providers
6. Setting up users, terminals and DDIs
7. Setting up the auto attendant

For each step you can display a help page or see it in the lower part of the window
where it is already displayed. You can skip individual steps of the setup wizard or exit
the setup wizard at any time in order to return to the WebAdmin start page.

Configuration assistant
The configuration assistant goes further than the setup wizard and helps you to config-
ure a communication system in sequence, from scratch. Logging on as administrator in
WebAdmin (expert or default mode) allows you to display the configuration assistant
on the WebAdmin start page.
The configuration assistant comprises the following steps:

1. Setting up the IP addressing

2. Regulating access control

Mitel 415/430 as of R4.1 175

syd-0580/1.2 – R4.1 – 08.2016
Configuration

3. Checking licences
4. Configuring media resources
5. Setting time and date
6. Checking network interfaces
7. Setting up SIP providers and accounts
8. Specifying user permissions
9. Create users and DDI numbers
10.Checking outgoing routing
11.Setting up the auto attendant
12.Setting up music on hold
13.Setting up an announcement service
14.Entering abbreviated dialling contacts
15.Saving configuration data

For each step, the upper half of the screen displays the configuration overview; the
right-hand side contains notes and instructions about the step you have selected. The
WebAdmin online help can be called up for further help.
You can skip individual configuration assistant steps or call up additional views of the
WebAdmin navigation tree. To hide the configuration assistant again, untick the control
box on the WebAdmin start page.

5. 6 Configuration Notes
The sections below contain information that may be useful before, during or after a
configuration.

5. 6. 1 Licences
All the features (even those subject to licences) can be configured without a valid li-
cence.
If you use a function or feature that requires a licence but do not actually have the rele-
vant licence, a trial licence is acquired automatically; it is also shown in the overview of
activated licences (Licenses =q9 view). With a trial licence you can now use the
function or feature free of charge for 60 days. The trial licence’s expiry date is indicated
under Status. This procedure can only be used once for each function or feature.
Thereafter you must acquire a licence. The licence overview (Tab. 31) shows which
trial licences are available.
All licences are contained in a licence code, which you can obtain from your authorised
dealer. Each licence code can only be used for one communication server. To licence

176 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Configuration

several communication servers, you will obtain separate licence codes to match the li-
cence information of the individual communication server. If a communication system
consists of several communication servers (e.g. in a AIN), normally only one licence
code is required on the Master.
A new communication system must be activated first after commissioning. Otherwise,
the communication server changes after 4 operating hours to limited operating mode.
Enter the licence code in the Licences ( =q9) view.
If you have received a voucher (or with the help of the Equipment ID), you can also ob-
tain the licence code via Mitel Connect https://connect.mitel.com (partner login re-
quired). You can find instructions about this in WebAdmin help.

See also:
"Licences", page 62

5. 6. 2 File management
You can gain access to the communication server’s file system in WebAdmin.

• Localization ( =e6)
You can adapt the communication system to your country's specifications, with the
help of localization. In this view language files can be manually or automatically
loaded for Mitel 6700 SIP / 6800 SIP SIP phones via FTP server. Moreover, you can
manually or automatically load the languages for the WebAdmin, Hospitality Man-
ager and Self Service Portal user interface and online help, as well as an external
numbering plan for the SIP connection via the FTP server.
• File system state ( =e3)
In this view you can see the thematically structured file system's memory load. In an
AIN the file systems for all nodes can be viewed.
• File browser ( =2s)
With the file browser you have access to the communication server file system and
create new folders as well as view, import, replace or delete files in the file system.

Note:
File management is only accessible for Administrators in Expert mode.

See also:
You can find detailed information about the functions in WebAdmin help for the corresponding
view.

Mitel 415/430 as of R4.1 177

syd-0580/1.2 – R4.1 – 08.2016
Configuration

5. 6. 3 System reset
Restart of the communication server
A restart reboots the entire communication system. The configuration data is pre-
served.
A new start can be achieved in the following ways:

• With the pilot key on the front panel

See "Carrying out a first start", page 211
• With WebAdmin in the maintenance settings
With the Restart button in the System reset( =4e) view.

Notes:
– Never disconnect the communication server from the power supply to trigger a restart. This
can result in data losses and prevent a restart.
– The restart is triggered immediately. All the active call and data connections are interrupted.

First start of the communication server

A first start has the effect of resetting the communication server from scratch. The sys-
tem-specific data such as the system ID, system type, sales channel, licence code,
software generation and IP address of the system are preserved.
A restart can be achieved in the following ways:

• With the pilot key on the front panel

See "Carrying out a first start", page 211
• With WebAdmin in the maintenance settings
With the First start button in the System reset ( =4e) view.

Notes:
– A first start deletes all the configuration data already stored and replaces it with the default
values of the sales channel. Therefore, back up your configuration data before a first start.
– The first start is triggered immediately. All the active call and data connections are inter-
rupted.

Starting the communication server for the first time and resetting the sales chan-
nel
With the First start and reset sales channel button for the maintenance settings in the
WebAdmin System reset ( =4e) view, you have the possibility for a first start to also
delete the sales channel and licence code. During the next start, you will be prompted
for the sales channel and licence code. Note that the licence code is dependent on the
sales channel and that you can no longer use the existing licence code.

Note:
This function is only accessible for Administrators in Expert mode.

178 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Configuration

5. 6. 4 Data backup
With a configuration data backup all the configuration data of the communication
server is stored in a compressed file in ZIP format. You can let the configuration data
backup run automatically (Auto backup) or as required (Manual backup).
You can automatically copy the backup files to an FTP server or e-mail them.
With an audio data backup all the audio data of the communication server is backed up
in a compressed file in ZIP format. The backup of the audio data can only be done
manually.
You can find the automatic data backup and distribution service settings in the
WebAdmin Maintenance / Data backup ( =um) view where you can also test the con-
figuration. Moreover, in this view, you can see the automatically and manually created
backup files and also restore or delete them.

Note:
The backup may consist of several files. They are compiled by the communication server and
compressed into a ZIP file. During the Restore process the ZIP file is extracted by the commu-
nication server itself. To ensure the restore process to run smoothly, make sure you do not mod-
ify the ZIP file. Never extract or modify a backup file yourself.

5. 6. 4. 1 Auto backup
The automatic data backup function creates a backup of the configuration data at regu-
lar intervals and saves the backup files on the communication server’s file manage-
ment system.
The Auto Backup function creates a backup of the configuration data at daily, weekly
and monthly intervals:

• Everyday at the set time a backup is created and stored in the ..\backup\day\ direc-
tory.
• When the week changes, a copy of the backup is stored in the ..\backup\week\ di-
rectory.
• When the month changes, a copy of the backup is stored in the ..\backup\month\ di-
rectory.

The backup directories are located on the file system of the communication server and
are directly accessible via the File browser ( =2s) or with an FTP connection.
A backup remains stored until the set storage time has expired; the .zip file is then de-
leted from the file system.

Mitel 415/430 as of R4.1 179

syd-0580/1.2 – R4.1 – 08.2016
Configuration

5. 6. 4. 2 Distribution service
You can use the distribution service to automatically copy the backup files to an FTP
server or e-mail them.

• The e-mail distribution service sends a copy of each backup file created to a pre-
configured e-mail address.
• The FTP distribution service stores a copy of each backup file created on an FTP
server.

5. 6. 4. 3 Manual backup
Configuration and audio data must be stored separately and stored as .zip files on any
data carrier you want. The configuration data is also backed up automatically as copy
on the communication server file system.
Situations in which you have to create a manual backup:

• Before running a first-start of the communication server (a first start resets all the
configuration data to their default values and deletes all audio data).
• Before and after you have expanded (or reduced) the communication server with
cards or modules.
• Before and after any major configuration changes.

5. 6. 4. 4 Restore backup
The available configuration data and audio data backup files can be restored at any
time.

Note:
– Restoring a backup irretrievably overwrites the current configuration data or audio data.
– Restoring a backup also resets the users' presence status, the personal routing settings and
any activated CFUs to the backup status.
– Some configuration changes only take effect after a restart. The communication server is
restarted after the configuration data is restored.

See also:
The procedure for creating and restoring a backup is described in detail in the WebAdmin help
in the Data backup ( =um) view.

5. 6. 5 Importing and exporting configuration data

You have the possibility to edit various configuration data outside WebAdmin, or to im-
port configuration data from other MiVoice Office 400 series communication systems.

180 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Configuration

Here you can create, with the help of the export function, a specific Excel file hereinaf-
ter referred to as Export file. The export file contains several spreadsheets. Each sheet
covers a specific configuration area. Subsequently, edit then re-import the export file.
Only the data belonging to the view, on which you have activated the import function,
will be imported. Example: The import function in the Phone book / Public view imports
only the data from the export file located on the spreadsheet Abbreviated dialling list.
Exception: The export function in the Backup view imports the data in all spread-
sheets.
You can find the export function in the following views:

• Overview (user data and key configuration of the terminals)

• Abbreviated dialling numbers
• PISN user
• Time controlled functions
• Ext./Int. Allocation
• LCR
• Blacklist
• CLIP based routing
• Data backup

Note:
You can activate the Replace existing configuration option with the import function. Activate this
function only if you are setting up the communication server from scratch. This action deletes all
previously configured user data and all user associated settings such as DDI numbers, CDE
targets, user group entries, assigned phones, configured keys, etc.

5. 6. 6 Mitel 6700 SIP / 6800 SIP phones

Prior to the registration, reset any phones that were already in operation back to the
factory setting. For security reasons, delete the phone's MAC address in WebAdmin.
This prevents problems during registration.
Use these procedures in the following cases:

• Assigning the phone to another user on the same system

• Transferring the phone to another system with the same software release
• Changing the software release from R4.0 SP1 to an earlier release
• Changing the communication server IP address.

Mitel 415/430 as of R4.1 181

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

6 Operation and Maintenance

This chapter describes maintaining the system and configuration data as well as up-
dating the system software. Replacing cards, modules and terminals are also de-
scribed. The display and control panel of the communication server as well as oper-
ations supervision using the event message concept, the operating state display, and
the error display are also topics covered in this chapter.

6. 1 Data Maintenance

6. 1. 1 What data is stored where

The communication server’s data storage system consists of different elements:

• In the Flash components are stored the system software, the boot software and the
configuration data. The contents of the memory are retained even when there is no
power supply.
• In the RAM components (main memory) are stored volatile data that cannot be
saved. It is available only when the system is in operation.
• The EIM card (Equipment Identification Module) contains the system-specific data
(system ID, system type, sales channel, licence code, generation, DECT identifica-
tion numbers, IP address of the configuration server). The contents of the memory
are retained even when there is no power supply.

182 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

Mainboard
Range of the RAM chips
EIM card

Range of
the Flash
chips

Fig. 79 Memories on the mainboard Mitel 415/430

6. 1. 1. 1 System software
The communication server's entire system software package is stored in compressed
form in the Flash memory.
The RAM components comprise the main memory for program data. When the PBX
starts up, the communication server software on the serial Flash memory is decom-
pressed, loaded into the main memory and started.

6. 1. 1. 2 File system of the communications server

The file system of the communication server comprises the system software, the soft-
ware for system phones, the system and terminal configuration data, the audio data,
system logs, data for WebAdmin, etc. The data is stored in the Flash memory. With
WebAdmin you have access to the file system via the menu item File management.
You can see the file system memory load and then load audio data, languages for the
user interface and online help, language files for Mitel 6700 SIP / 6800 SIP-series SIP
phones as well as an external numbering plan for SIP connection. Moreover, with the

Mitel 415/430 as of R4.1 183

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

file browser you have the possibility to view, upload, replace or delete the folders and
files in the file system. The file system can also be accessed with an FTP client (see
also "File management", page 177).
Functions for backing up and restoring configuration data and audio data are available
in the WebAdminMaintenance / Data backup ( =um) view (see also "Data backup",
page 179).

Note:
Modifying or deleting files on the file system of the communication server can result in a system
that is no longer able to run.

6. 1. 1. 3 Boot software
The boot software is stored in a different Flash memory, which allows the communica-
tion server to start up in the boot mode, even if without executable system software.

6. 1. 1. 4 System-specific data
The system-specific data (system ID, system type, sales channel, licence code, gener-
ation, DECT identification numbers, IP address of the communication server) is stored
on the EIM card (chip card). This data is not deleted by a first start of the PBX, and re-
mains available. It can be ported to a different communication server by replacing the
EIM card.

6. 1. 2 Updating configuration data

There are system-wide, user-related and terminal-related configuration data:

• System-wide configuration data can only be modified with WebAdmin.

• Terminal configuration data such as key assignments or ringing melodies can be
modified either directly on the terminal, with Self Service Portal or with WebAdmin.
With some system phones configuration is also possible using the web user inter-
face or with the help of configuration files.
• User-related configuration data such as private contacts or CFUs is valid for all the
terminals assigned to the user and can be configured using WebAdmin, partly via
Self Service Portal, or directly on the terminal itself.

Access to the configuration data via WebAdmin is regulated by a User Access Control
with user accounts, authorization profiles and authorization levels. More information
can be found in the Chapter "User access control", page 169.

184 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

6. 2 Update Software

6. 2. 1 System software
The communication server software is normally updated with WebAdmin. In excep-
tional cases (e.g. during downgrade), an Emergency Upload via System Search is re-
quired (see also page 186).
The firmware for MiVoice 5300/MiVoice 5300 IP, Mitel 600 DECT phones, DECT
phone Office 135/135pro, DECT radio units SB-4+/SB-8/SB-8ANT and WebAdmin is
also available in the system software.

Tip
The communication server software version can be displayed as follows on
MiVoice 5300/MiVoice 5300 IP phones:
1. Access the configuration menu Settings.
2. Long-click on the * key
Information can be retrieved on /Mitel 6700 SIP / 6800 SIP SIP phones as well as on
/Mitel 600 DECT DECT phones via the menu.
Depending on the phone, additional information is displayed.

Providing the system software and licence code

The new system software and the relevant licence code are provided by your sales
dealer. In most cases you will download the software from an internet site specified by
your sales partner. You will also receive a voucher. With this you can generate the new
licence code through the Mitel Connect internet portal https://connect.mitel.com and
transmit it to your communication system. You need a login to access Mitel Connect
(user name and password).

Load new system software with WebAdmin

New system software can conveniently and safely be loaded on the communication
server file system in the WebAdmin Maintenance / System software ( =m7) view. The
activation point of the new software is selectable. (Exception: The activation time on
the satellites AIN always depends on the master's demand).
In newly delivered systems it is possible to directly load new system software after
choosing the sales channel.

Notes:
– Most times a new licence code is also required for new system software. You can also install
and start up the new software without specifying the licence code. However, once you have
started to use the software you will need to enter the licence code within 4 hours; otherwise
the communication server will switch over to the restricted operating mode. In this mode,
only the basic functions of the communication server are available.
– Depending on communication server type, the upload operation (especially decompressing
the software package) may take some time.

Mitel 415/430 as of R4.1 185

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

– Never disconnect the communication server from the power supply during the update pro-
cess. This may prevent executable system software from being available on the communi-
cation server, and make an EUL (Emergency Upload) necessary.

See also:
A detailed description of the software upload procedure with WebAdmin is available in the
online help.

Loading new or older system software with System Search

Whenever a standard software upload is not possible, has proved faulty, or to replace a
Flash card or if you wish to load an earlier system software (Downgrade), you must
carry out a Emergency Upload. You need the search and help tool System Search.

Note:
A first start of the communication server is also performed with an Emergency Upload. All the
already stored configuration data is deleted and replaced with the default values of the sales
channel. Therefore, before an Emergency Upload back up your configuration data (if still possi-
ble).
To perform an Emergency Upload, proceed as follows:

1. Set the communication server to boot mode using the control key (see "Boot Mode",
page 206).
2. Start System Search and select Emergency Upload.
3. Enter the communication server IP address.
4. Select the system software package to be uploaded (zip file).
5. Click the Upload button.
→ Emergency Upload is started.

Note:
During an Emergency Upload the communication pattern for the start-up state is displayed for a
long time (up to 10 minutes) (Pattern [5], Tab. 92). This is normal since it takes a while to
decompress the system software..

6. 2. 2 Firmware for corded system phones

The communication server's software package contains the software for certain system
phones (DSI and IP), which is updated in each case along with the system software.
For other system phones (SIP) the firmware is located on a firmware server.
The Office 10, Office 25 and MiVoice 5360 system phones do not have their own mem-
ory. All other system phones have a Flash memory.

SIP system phones

The firmware for Mitel 6700 SIP / 6800 SIP series SIP phones as well as for Mitel
BluStar 8000i, Mitel BluStar clients and Mitel Dialer is preferably located on a firmware

186 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

server. In the WebAdmin Configuration / IP network / Firmware server ( =yv) view

Mitel FTP servers are already predefined. Various firmware releases are stored on this
server, according to different communication server software releases. The predefined
entry in WebAdmin is adjusted to each communication server release if necessary. You
can also indicate the address of another firmware server.
Whenever the phones are started the phone firmware version is compared with the
version on the firmware server. If the versions differ, the firmware is downloaded from
the firmware server to the phones.

DSI and IP system phones with Flash memory

The flash memory contains the boot software and the application software. DSI phones
also have an area with the interface software.
The firmware for the phones Office 35, Office 45, MiVoice 5370, MiVoice 5380 as well
as for all MiVoice 5300 IP series IP phones is contained in the communication server's
system software. The firmware versions are compared when the phones are started. If
the versions differ, the firmware is downloaded from the communication server to the
phones. When updating the system software this can take several minutes for each
DSI phone.
The expansion key modules MiVoice M530 and MiVoice M535 also have a flash chip
containing firmware. The update mechanism is the same as the one described above.
However a local power supply is always required (Power over Ethernet is also possible
with IP terminals).

6. 2. 3 Firmware System MiVoice Office 400 DECT

DECT radio units SB-4+, SB-8 and SB-8ANT
The Flash memory on the radio units contains an area that cannot be modified. It is
used for starting the radio unit and receiving the firmware for the radio unit.
The actual firmware for the radio unit is contained in the communication server's sys-
tem software. The loaded firmware is tested when the radio unit starts up. If the loaded
firmware is not identical to the version in the system software, the firmware will be
downloaded from the communication server on to the radio unit and stored in the Flash
memory of the radio unit.

Cordless DECT phones of the Mitel 600 DECT family

The firmware for the Mitel 600 DECT cordless phones, is updated via radio (Air-Down-
load). The update can be enabled or disabled individually for each cordless phone us-
ing the menu System - Download server on the cordless phones. If the cordless phone
is logged on to several systems, this menu defines which system the firmware update
is relevant to.

Mitel 415/430 as of R4.1 187

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

There is only one firmware for the cordless Mitel 600 DECT series phones. It is in-
cluded in the communication server's software package and stored in the file system of
the communication server.

DECT cordless phones Office 135 and Office 160

The firmware for the Office 135 and Office 160 cordless phones, is updated via radio
(Air-Download). This requires the cordless phone to be logged on to system A.
The memory in the cordless phones is a Flash memory. The Flash memory contains an
area that cannot be modified. This area contains the cordless phone's boot software.
The firmware for the cordless phones is contained in the communication server soft-
ware package. The loaded firmware is tested when the cordless phone starts up. If the
loaded firmware is not identical to the version in the system software, the system will
initiate an Air-Download. The firmware is loaded from the communication server onto
the cordless phones via radio and stored in the Flash memory.
To be able to run an Air-Download, you need to ensure that the cordless phone con-
tains a functional firmware.
The cordless phone remains fully functional during an Air-Download. The new loaded
firmware is activated only once the Air-Download has been successfully completed. A
restart is carried out on the cordless phone.

6. 2. 4 Firmware System Mitel SIP-DECT

With Mitel SIP-DECT and Mitel 600 DECT series phones comprehensive solutions can
be provided for wireless telephony on IP-based networks. This requires RFP radio
units that can be directly connected to other VoIP devices on the LAN.
OpenMobilityManager (OMM) is installed on one of the RFP radio units or on a PC,
which constitutes the management interface for the Mitel SIP-DECT solution.
Mitel 600 DECT phones have loaded a different firmware in an Mitel SIP-DECT system
from the one in an MiVoice Office 400 DECT system.
The firmware for the RFP radio units and for the Mitel 600 DECT cordless phones is
preferably located on a firmware server. Automatic firmware update is then possible.
The WebAdmin Configuration / System / DECT/SIP-DECT / SIP-DECT ( =9y) view
contains a global predefined Mitel FTP server. Various firmware versions are stored on
this server, according to different communication server software releases. The prede-
fined entry in WebAdmin is adjusted to each communication server release if neces-
sary. You can also indicate the address of another firmware server.
Firmware designations for Mitel SIP-DECT (examples):
aafon6xxd.dnld:
Firmware for Mitel 600 DECT cordless DECT phones.

188 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

iprfp3G.dnld:
Firmware for OpenMobilityManager (OMM).

6. 3 Hardware update
Hardware maintenance comprises replacing cards, modules and terminals when there
is a defect or for a generation change. Safety regulations must be observed and the
step-by-step procedure must be followed.

6. 3. 1 Preparations
The following preliminary steps apply to interface cards, system cards and system
modules as well as to the mainboard of the communication server itself.
First steps before cards are removed or added:

1. Inform users
2. Disconnect communication server power supply

Inform users
Inform all concerned users if the system has to be put out of operation during working
time.

Tip
To inform users, use the internal messaging system on the system phones.

Disconnect communication server power supply

Shut down the communication server (see "Shutdown Mode", page 206) and discon-
nect it from the power supply.

6. 3. 2 Licenses and EIM card

The license information and IP address of the communication server’s Ethernet inter-
face are stored on the EIM (Equipment Identification Module) card. The licence infor-
mation includes:

• The EID (Equipment Identification) serial number of the EIM card

• The sales channel identification CID (Channel Identification)
• Licence code LIC
• System type

Mitel 415/430 as of R4.1 189

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

6. 3. 2. 1 Licences
To expand a system already in operation or to re-order a licence for a new system, pro-
ceed as follows:

1. Order the licences you want from your authorised dealer and specify the EID num-
ber, which serves to identify the communication server.
2. The new licence code can be obtained either from your authorized dealer or via
Mitel Connect https://connect.mitel.com using the EID (partner login required).
3. Enter the licence code in the Licensing ( =q9) view and save it in the communica-
tion server. The licence code is stored on the EIM card.
4. The newly licensed features are enabled. It is not necessary to restart the communi-
cation server (exception: AIN licences).

The data stored on the EIM card is not deleted by a first start of the PBX, and remains
available.

See also:
"Licences", page 62

6. 3. 2. 2 EIM card
The EIM card must be replaced in the following cases:

• A licence is transferred to another communication server

• The mainboard is defective
• The EIM card is defective

A licence is transferred to another system of the same type

A licence can only be transferred to a communication server of the same type. To do so
you need to replace the EIM card with the licence information. For the procedure for
switching an EIM card see page 194.

The mainboard is defective

If you need to replace a defective mainboard, transfer the EIM card from the defective
mainboard onto the new one. For instructions on how to replace the mainboard, see
page 195.

The EIM card is defective

In the unlikely event of a defective EIM card, contact your authorized dealer to discuss
the procedure.
For the procedure for switching an EIM card see page 194.

190 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

6. 3. 3 Interface cards
The different card types, the number of slots and the maximum configuration are all de-
termined by the system capacity (see Chapter "3 Expansion Stages and System Ca-
pacity").
A number of rules have to be observed when fitting the cards (see "Component mount-
ing rules", page 100.
All configuration data is centrally stored in non-volatile Flash memory. This means that
configuration data is preserved whenever a defective interface card has to be replaced
by a new one.

6. 3. 3. 1 Replacing a defective interface card

A card is replaced by the same card type with the same number of ports.
Procedure:

Warning
Be sure to observe the "Safety regulations", page 84.

1. Carry out preparations (see "Preparations", page 189).

2. Remove the housing cover.
3. Remove the defective interface card by pressing the two lateral metal clamps out-
ward at the same time and gently lifting the interface card.
4. Place the new interface card at a slight angle into the required slot (see Fig. 23).
Make sure the angled side of the interface card is facing backwards (i.e. it must not
project over the wiring adapter slots).
5. Carefully press the interface card downwards until the two lateral metal clamps en-
gage.
6. Fit the housing cover.
7. Reconnect the system to the power supply.

6. 3. 3. 2 New card with fewer ports

A card is replaced by a similar card with fewer ports.
Procedure:
Change the card and put the system into operation again. Similar procedure as de-
scribed in "Replacing a defective interface card", page 191.

Mitel 415/430 as of R4.1 191

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

The following data is deleted:

• The system and terminal configuration data of the terminals on the interfaces that
are no longer present in the new configuration.
• The system configuration data of the network interfaces that are no longer present
in the new configuration.

Tab. 85 Example: Reducing the number of terminal or network interfaces

TIC-4TS → TIC-2TS The configuration data of terminal interfaces 3 and 4 are deleted.
TIC-4AB → TIC-2AB The configuration data of network interfaces 3 and 4 are deleted.

Note:
If the terminal configuration data of system terminals is deleted following the reconfiguration of
a card, a warning message will appear beforehand to give you the possibility of cancelling the
process. However, this is possible only if the configuration data of the original card was not
already deleted beforehand.

6. 3. 3. 3 New card with more ports

A card is replaced by a similar card with more ports.
Procedure:

1. Change the card and put the system into operation again. Similar procedure as de-
scribed in "Replacing a defective interface card", page 191.
2. In the WebAdmin view Cards and modules ( =4g) Confirm the new cards.
3. Configure new ports.

The system configuration data (User No., User configuration, etc.) of the terminals on
the new ports is created as new data (default values).

Tab. 86 Example: Expanding the number of terminal or network interfaces

TIC-2TS → TIC-4TS The configuration data of terminal interfaces 3 and 4 are created as new.
TIC-2AB → TIC-4AB The configuration data of network interfaces 3 and 4 are created as new.

6. 3. 3. 4 Change slot
Interface cards can be moved to a different slot. The terminal configuration data of the
system phones can be transferred.
Procedure:

1. Change the slot and put the system into operation again. Similar procedure as de-
scribed in "Replacing a defective interface card", page 191.

192 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

Note:
The wiring adapter must also be changed to the corresponding slot. Any incorrectly fitted or
missing wiring adapters are signalled by a red flashing LED on the display after start-up (see
"Wiring Adapter Malfunction Mode", page 205).
2. Connect the system terminals to the ports of the new slot.
3. Reconfigure the port assignment.
4. In the WebAdmin view Cards and modules ( =4g) Confirm card in the new slot
and Delete it from the old slot. The configuration data at the old slot location is now
deleted.

Note:
Not all cards can be equipped on all slots (see "Component mounting rules", page 100).

6. 3. 4 System modules
The category system modules comprises the DSP modules stacked in slot SM1. DSP
modules are available in various versions (SM-DSPX1, SM-DSPX2, SM-DSP1, SM-
DSP2). Compared with DSP modules, modules with the designation DSPX are fitted
with more powerful DSP chips.

6. 3. 4. 1 Changing the DSP module

The following describes how to replace a DSP module if it is defective or how to re-
place it for a more powerful module.
To change a DSP module, proceed as follows:

Warning
Be sure to observe the "Safety regulations", page 84.

1. Carry out preparations (see "Preparations", page 189).

2. Remove the housing cover.
3. Remove the old or defective module by loosening the fastening screw and carefully
pulling the module out vertically of the module slot.

Note:
If there are several modules fitted and the card to be replaced is not topmost, the spacing
sleeves have to be loosened and the modules pulled. The order of the modules on the slot is
relevant only if different types of modules are equipped.
4. Press the new module downward evenly on both connectors to the stop.
5. Secure the module with the fastening screw.
6. Fit the housing cover.
7. Reconnect the system to the power supply.

Mitel 415/430 as of R4.1 193

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

6. 3. 5 System cards
As the RAM and Flash chips are fitted directly to the mainboard, the category system
cards comprises only the EIM card.

6. 3. 5. 1 Replacing the EIM card

The EIM card is located in a chip-card holder that is secured directly on the mainboard.
The position of the chip-card holder on the mainboard is shown in Fig. 79.
To fit an EIM card, proceed as follows:

Warning
Be sure to observe the "Safety regulations", page 84.

1. Carry out preparations (see "Preparations", page 189).

2. Remove the housing cover.
3. Gently push the EIM card along the guide tongues out of the chip-card holder.
4. Push the new EIM card under the guide tongues and through to the stop in the chip-
card holder. Make sure the contacts of the EIM card are facing downwards and the
bevelled edge of the EIM card is pointing towards the edge of the mainboard (see
Fig. 80).
5. Fit the housing cover.
6. Reconnect the communication server to the power supply.

&*.

Fig. 80 EIM card

Notes:
– The EIM card must be fitted before the system is put into operation. The communication
server will not start without the EIM card.

194 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

– If the defective EIM card was replaced by a new one, all DECT cordless phones must be
logged on again. This is necessary because the DECT identification numbers are stored on
the EIM card.

6. 3. 6 Mainboard
If the components on the mainboard are defective or permanently faulty, the entire
communication server with the metal chassis must be replaced.
To replace the communication server, proceed as follows:

Warning
Be sure to observe the "Safety regulations", page 84.

1. Back up the configuration data and audio data, if still possible.

2. Carry out preparations (see "Preparations", page 189).
3. Remove the housing cover.
4. Remove the interface cards (see "Interface cards", page 191), the system modules
(see "System modules", page 193) and the wiring adapter.
5. Change the EIM card of the defective mainboard to the new mainboard (see "Re-
placing the EIM card", page 194).
6. Dismantle all the connected cables in such a way that the new communication
server can be identically reconnected.
Note: The mainboard is not dismantled but replaced complete with metal housing.
7. The new communication server can now be reassembled, fitted and installed in the
reverse sequence.
8. Carry out a first start of the system (see "First start of the communication server",
page 178) and upload the configuration data from a backup file back on to the com-
munication server.

6. 3. 7 Replacing system terminals

6. 3. 7. 1 DSI system phones

Phones with the same level of added features

Replacing a defective phone
Once the defective DSI system phone has been replaced by an identical phone the ter-
minal configuration data is automatically transferred.

Mitel 415/430 as of R4.1 195

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

Relocating a phone
The assigned port can be modified in the terminal configuration via WebAdmin, and the
phone connected on the new slot. The terminal configuration data is preserved.

Phones with a different level of added features

If a phone is replaced with another type of phone, most of the terminal configuration
data can be taken over using Multi edit. A separate Multi edit (keys) function is availa-
ble for the key configuration. Details can be found in the WebAdmin help for the view
Standard terminals ( =qd).

6. 3. 7. 2 DECT terminals

Replacing a radio unit

1. Dismantle the defective radio unit.
2. Fit the new radio unit.

Note:
If the ports of a radio unit are to be changed or if a radio unit is no longer used, it is important to
remove the radio unit in the system configuration. If not, start-up problems may occur when
another radio unit is connected to the same ports.

Replacing a cordless phone (a phone without microSD card)

1. Cancel the registration of the old cordless phone.
2. Register the new cordless phone. The cordless phone data is preserved until the
user number is also deleted.

Cancelling the registration of a cordless phone on the system

In WebAdmin in the edit view of the cordless phone, click Cancel registration.

Tip:
The identification of the cordless phone is deleted only if the cordless phone is located within
the coverage range of a radio unit; otherwise, it must be deleted manually on the cordless
phone (see the cordless phone’s User’s Guide). The user number and data in the system are
retained.

196 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

Registering a cordless phone on the system

1. Prepare the cordless phone for registration (see the cordless phone’s User’s
Guide).
2. Prepare system for registration. In WebAdmin in the edit view of the cordless phone,
click Register.

Note:
With some phone types, the user of the cordless phone may have to identify himself to the sys-
tem using an authentication code (AC). This authentication code is issued after the Register
button is clicked.

Replacing a cordless phone (a phone with microSD card)1)

The special microSD card is suitable for replacement with wireless DECT phones
Mitel 620/622 DECT, Mitel 630/632 DECT and Mitel 650 DECT. The card stores the
cordless phone's registration data on the communication server and the most impor-
tant local settings. This guarantees that in case of device defect - by taking the card
along - the operation on a replacement device can be continued within a short period
and without re-registering.
Each card (like each cordless phone) has its own, globally known unique serial number
for DECT devices (IPEI: International Portable Equipment Identity), used for the regis-
tration process on DECT communication systems. In an operation with the card, the
data stored on the card is always used.

Notes:
– The microSD card can only be used as from Device hardware 2 (concerns Mitel 620 DECT,
Mitel 630 DECT).
– Use the card only after reading this detailed description of the card functions. Failing to
observe these recommendations may cancel the registration of operational devices.
– All registration and device data on the card is encrypted and protected against copying.
– Do not use the card with other devices (e.g. camera) to avoid reformatting the card mistak-
enly and to have enough storage space.
– The card can no longer be used with the cordless phones after being erased or formatted.
– Commercially available microSD cards cannot be used (except to copy local settings, see
page 199).

1)Supported as of R2.1

Mitel 415/430 as of R4.1 197

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

Using a microSD card

Note:
The microSD card must be handled very carefully. The contacts must be free from dust, humid-
ity, oil, etc. Do not store the card in warm areas (exposed to direct sunlight, for example). Do not
bend the card as this may damage the contacts.

1. Switch off the cordless phone.

2. Open the battery compartment and remove the battery.
3. Push the card holder downwards and carefully tilt the cover sligghtly upwards (see
Fig. 81 on the left).

Warning
Never touch the now visible and shining golden contacts! Static discharges may lead to
device malfunction.
4. Place the card in the holder (with the contact surfaces downwards and the side card
interfaces leftwards).
5. Close the card holder then carefully push it upwards until it snaps into place.
6. Only for Mitel 620 DECT, Mitel 630 DECT with black card holder:
Take the protective cover provided with the card and put it on top of the card holder
(see Fig. 81 rightwards).

Note:
The protective cover should not be used for Mitel 620 DECT, Mitel 630 DECT with a white
card holder or in Mitel 622 DECT, Mitel 632 DECT and Mitel 650 DECT.
7. Insert the battery and cover the battery compartment.

Fig. 81 microSD card

Behaviour after inserting a new microSD card

After starting the cordless phone you will receive, in the start phase, a message inform-
ing you that a new card has been detected. The two typical cases are described below:
Cordless phone has not yet been registered:

198 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

Accept the new card.

→ The local settings are copied to the card.
Register the phone on the communication server.
→ The registration data is stored on the card.
→ Modifications on the local settings are henceforth also stored on the card.
Cordless phone is already registered:
Accept the new card.
→ The local settings are copied to the card.
→ The registration data is copied to the card and erased from the cordless phone
memory.
→ Modifications on the local settings are henceforth also stored on the card.

Behaviour after inserting a valid microSD card

After starting the cordless phone you will receive, in the start phase, a message inform-
ing you that a new card with a new ID has been detected.
Accept the card.
→ The cordless phone restarts.
→ The card's registration data and local settings are used.
→ The original data remains stored in the cordless phone and is reactivated once the
card is removed.

Copying local settings using a commercially available microSD card

This procedure is helpful if several cordless phones with the same local settings must
be preconfigured.

1. Carry out on a master cordless phone without microSD card the local settings you
want.
2. Switch off the master cordless phone, insert a commercially available microSD card
then restart the master cordless phone.
3. Confirm the information that the microSD card is invalid.
4. Select Menu - Settings - General - Administration - Diagnostics - File Mgmt. Device
then copy all user data to the microSD card.
-> The card is now specially marked as a copy card.
5. Switch off the master cordless phone, remove the card and insert the card in the tar-
get cordless phone to which the data must be copied.
6. Start the target cordless phone and confirm the information that the user data on the
card will be used.
7. Copy all user data from the card to the memory of the target cordless phone.
-> The target cordless phone restarts.
8. Switch off the target cordless phone and remove the card.
-> After the target cordless phone is switched on again the copied user data is used.

Mitel 415/430 as of R4.1 199

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

6. 4 Display and control panel

The display and control panel of the Mitel 415 and Mitel 430 communication servers on
the front panel consists of an LED display panel and a pilot key. It is used to indicate
operating states and carry out functions.

6. 4. 1 LED display
The front panel contains an LED display field with a total of 9 labelled LEDs. It is used
as an operating state and error indicator during the start-up phase and during opera-
tion.

Operating state and error display

Ethernet state

(For future expansions)

Power supply state

"PWR" lit Power supply in order

"LAN1" lit: Port has a connection with the network
LAN1" blinking Port is receiving or sending data
"F0, F1, F2, F3, F4, SYS": see "Operating modes and display priorities", page 202

Fig. 82 LED display

Each LED can take on one of four states: green (G), orange (O), red (R) and inactive.
In general the colours have the following meaning:

Tab. 87 Significance of the LEDs colours

Colour Meaning
Inactive – Switched off
Green G Normal operation / everything in order
Orange O Function is being carried out / is active
Red R Warning / error

An LED activation period lasts 1 second and is subdivided into 8 units of 125 ms. In
this way all the various flashing patterns can be displayed.

200 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

Example:
In the following display pattern the LED lights up green for 500 ms and is then inactive
for 500 ms. Then it lights up green again for 500 ms ... etc.

Tab. 88 Example of a display pattern

LED activation period
Description
1s
G G G G – – – – Slowly flashing green

The following display patterns and symbols have been defined for displaying the status
of the communication server:

Tab. 89 Defined display patterns

LED activation period
Description Symbol
1s
– – – – – – – – Inactive –
G G G G G G G G Steady green G
O O O O O O O O Steady orange O
R R R R R R R R Steady red R
G G G G – – – – Slowly flashing green G –
O O O O – – – – Slowly flashing orange O –
R R R R – – – – Slowly flashing red R –
G G G G O O O O Slowly flashing green/orange G O
O O O O R R R R Slowly flashing orange/red O R
R R R R G G G G Slowly flashing red/green R G
G G – – G G – – Rapidly flashing green G–G
G – G – G – G – Very rapidly flashing green G–G–G
R – R – R – R – Very rapidly flashing red R –R –R

6. 4. 2 Pilot key (CTRL key)

Pressing the pilot key carries out certain functions or switches the system to a particu-
lar mode.

$53-

Fig. 83 Pilot key

Mitel 415/430 as of R4.1 201

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

Different actions are carried out depending on how long the key is pressed and the
system’s current operating state. The duration of the keypress is divided into three time
intervals:

Tab. 90 Keypress duration, pilot key

Designation ID Keypress duration
Short keypress (Shortclick) SC 0...2 seconds
Long keypress (Long Click) LC 2...10 seconds
Very long keypress (Very Long Click) VLC More than 10 seconds

6. 4. 3 Operating modes and display priorities

The system software of the Mitel 415/430 recognizes various operating modes, which
are displayed with the LEDs F0, F1, F2, F3, F4 and SYS. In the following these dis-
plays are referred to as combination patterns or patterns and are numbered for easy
reference.
The various operating modes have different display priorities, i.e.a mode with a higher
display priority will cover up the combination pattern of a mode with a lower display pri-
ority. The combination patterns covered up are stored and continually updated in the
background, which means that no patterns are lost.
The table below lists all the operating modes and their display priorities. The highest
display priority is 1; the lowest, 7.

Tab. 91 Operating modes and display priorities

Display pri-
Operating mode Remarks
ority
Shutdown Mode 1 • After the system is shut down
• Shutdown mode lasts for 3 minutes. Thereafter the system
automatically changes to Startup Mode.
Error Mode 1 • System is no longer able to run
Startup Mode 2 • When power is supplied
• After a restart/first start
• Used as a progress indicator during startup
Application Command Mode 3 • Used for carrying out certain functions
Boot Command Mode • This mode is exited automatically if no input is made within 20
seconds.
Warning Mode 4 • System is still capable of running but the system function may
be impaired.
• Problem needs to be remedied as soon as possible.
Wiring Adapter Malfunction Mode 5 • System is running but a problem has been detected on one or
more wiring adapter slots.
Feature Mode 6 • System is running normally but one function is active.
Normal Mode 7 • System is running normally.

202 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

6. 4. 3. 1 Startup Mode
Startup begins as soon as power is supplied or after a restart/first start, and ends when
the system enters Normal Mode. The LED combination patterns [1]...[9] indicate the in-
dividual start-up phases in chronological order and also serve as a progress indicator.

Tab. 92 Combination patterns during startup

Dura-
Pattern
F0 F1 F2 F3 F4 SYS tion Meaning
No.
[s]
[1] R R R R R R ~3 Red LED test
[2] O O O O O O ~1,5 Orange LED test
[3] G G G G G G ~1,5 Green LED test
[4] G–G–G – – – – – ~7 RAM self-test
G – – – – – ~3
– – – – – – ~15
[5] G G – – – – – ~3 Startup State
[6] G G G – – – – ~1 Preparing system software loading
[7] G G G G – – – ~3 Loading the system software
[8] G G G G – – ~1 System software successfully loaded
– – – – – – ~10
[9] – – – – – G – G ~60 System software starting up

The startup phase is now completed and the system switches to Normal Mode. The pi-
lot key now accepts inputs; the terminal displays are visible shortly thereafter.

6. 4. 3. 2 Normal Mode
Normal Mode means that the system software is running fault-free. Depending on the
situation the LEDs display the following combination patterns:

Tab. 93 Combination patterns in Normal Mode

Pattern
F0 F1 F2 F3 F4 SYS Meaning
No.
[11] – – – – – G – System in normal operation
[12] G – – – – G – At least one internal port seized
[13] – G – – – G – At least one external port seized

Mutual combinations of patterns [12] and [13] are possible as are combinations with
patterns [14], [15] and [16].

Mitel 415/430 as of R4.1 203

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

6. 4. 3. 3 Feature Mode
Feature Mode means that the system software is running fault-free, but that a special
function (feature) is active. Depending on the function the LEDs display the following
combination patterns:

Tab. 94 Combination patterns in Feature Mode

Pattern
F0 F1 F2 F3 F4 SYS Meaning
No.
[14] – – – – – O – System is prebarred
[15] – – – O – G – Enable the password-free access for configura-
tion via Ethernet.
[16] – – – – O G – Remote access to AIN enabled via an external
dial-up connection.

Mutual combinations of patterns [14], [15] and [16] are possible as are combinations
with patterns [12] and [13].

Mitel Advanced Intelligent Network:

In an AIN the offline mode of a satellite is indicated by the green-orange flashing SYS-LED.
Combinations with the patterns of the Normal Mode and Feature Mode are possible.
Exception: Pattern [14] (prebarred system) takes priority over the offline mode display.

6. 4. 3. 4 Application Command Mode

The Application Command Mode can be used to shut down or restart the communica-
tion server with prior database backup. It is also used to enable or disable password-
free access (pattern[15]15) and remote access to the AIN via an external dial-up con-
nection (pattern[16]).
The Application Command Mode is indicated by the SYS-LED flashing green-orange.
The Application Command Mode is entered pressing and holding down the control key
(LC) in Normal Modus. Combination pattern [17] is displayed once the Application
Command Mode has been entered.

Tab. 95 Patterns after entering the Application Command Mode

Pattern
F0 F1 F2 F3 F4 SYS Meaning
No.
[17] R – – – – G O Application Command Mode active

The Application Command Mode is exited automatically if no input is made within 20

seconds; the system returns to Normal Mode.

204 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

6. 4. 3. 5 Boot Command Mode

The Boot Command Mode is used to carry out a first start or set a fixed IP address.
The Boot Command Mode is indicated by the SYS-LED flashing orange-red.
The Boot Command Mode is entered by pressing and holding down the control key
(LC) during the start-up state (see pattern[5], Tab. 92). Pattern[18] is displayed once
the Boot Command Mode has been entered.

Tab. 96 Patterns after entering the Boot Command Mode

Pat-
tern F0 F1 F2 F3 F4 SYS Meaning
No.
[18] R – – – – O R Boot Command Mode active

The Boot Command Mode is exited automatically if no input is made within 20 sec-
onds; the system returns to Startup Mode and restarts.

6. 4. 3. 6 Wiring Adapter Malfunction Mode

The system switches to this mode if an unsuitable wiring adapter is fitted into one of
the wiring adapter slots. Missing wiring adapters are also indicated.
The Wiring Adapter Malfunction Mode is indicated by one or more red flashing LEDs
F1...F4. The LED number corresponds to the number of the Wiring Adapter slot con-
cerned. The SYS-LED flashes green as in the Normal Mode.

Tab. 97 Sample pattern for Wiring Adapter Malfunction Mode

Pattern
F0 F1 F2 F3 F4 SYS Meaning
No.
[20] – – R – – – G – Wrong or missing wiring adapter in slot WA2

6. 4. 3. 7 Warning Mode
The system switches to the Warning Mode if a problem occurs that impairs the sys-
tem’s normal operation. The Warning Mode is indicated by the red-green flashing SYS-
LED and is exited only once the problem is remedied.
The different warnings are binary coded and are indicated by the LEDs (F0...F4).

Mitel 415/430 as of R4.1 205

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

Tab. 98 Warning Mode combination patterns

F0 F1 F2 F3 F4 SYS Category / Description Remedy
– – – – R R G Fan out of operation Check connections or
replace fan
– – – R – R G Oscillator Tuning Block miss- Contact Support. The Oscil-
ing (can cause DECT prob- lator Tuning Block has to be
lems) loaded.

6. 4. 3. 8 Boot Mode
The boot mode enables an Emergency Upload via the Ethernet interface. This is re-
quired whenever there is no longer any executable system software stored on the com-
munication server for whatever reason or if a downgrade to an older software version
is to be carried out.
The Boot Mode is indicated by the SYS-LED flashing red.
To access the boot mode press the control key during the LED test red, which is exe-
cuted during the start-up phase (see pattern[1], Tab. 92). The length of time the pilot
key is pressed is irrelevant. The red LEDs go off once the control key is pressed. After
a wait time of approx. 30 seconds, Pattern [21] of the boot mode is displayed.

Tab. 99 Combination patterns in Boot Mode

Pattern
F0 F1 F2 F3 F4 SYS Meaning
No.
[21] – – – – – R – Boot Mode active

The boot mode remains active until the Emergency Upload is completed or the system
is restarted manually.

6. 4. 3. 9 Shutdown Mode
If, for maintenance purposes, the communication server is disconnected from the
power supply, it must be shut down under control (see "Shutting down the communica-
tion server", page 209). It then remains in Shutdown Mode for three minutes before it
starts again automatically. During this period the communication server can be discon-
nected from power supply.

Notes:
Never disconnect the communication server from the power supply to trigger a restart. This can
result in data losses and prevent a restart.
Combination pattern [22] is displayed in shutdown mode.

206 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

Tab. 100 Combination patterns in Boot Mode

Pattern
F0 F1 F2 F3 F4 SYS Meaning
No.
[22] R – R – R – R – R – G – Shutdown Mode active

6. 4. 3. 10 Error Mode
The system switches to Error Mode if a problem or error occurs that prevents the sys-
tem’s normal operation. This can be a hardware error or a software installation error.
The Error Mode is indicated by the red SYS-LED flashing very rapidly and is exited
only once the error is remedied. In many cases this involves a system restart.
The different errors are binary coded and are indicated by the LEDs (F0...F4).

Tab. 101 Error Mode combination patterns

F0 F1 F2 F3 F4 SYS Category / Description Remedy
– – – – R R – R – R Hardware: Insert or replace EIM card
No licence: EIM card missing
or defective
– – – R – R – R – R Hardware: Run a first start or replace
No IP address data on the EIM EIM card
card
– – – R R R – R – R Hardware: Replace EIM card
EIM card not compatible
– – R – – R – R – R Hardware: Replace communications
DRAM defective server
– – R – R R – R – R Hardware: Replace communications
BBT Integrity Check: No free server
replacement blocks available
– – R R – R – R – R Hardware: Replace communications
BBT Integrity Check: Incon- server
sistent Bad Block Table
– – R R R R – R – R Hardware: Replace communications
BBT Integrity Check: ECC has server
detected an uncorrectable
read error
– R – – – R – R – R Hardware: Replace communications
BBT Integrity Check: Block 0 server
is faulty; the Bad Block Table
cannot be used
– R – – R R – R – R Software: Using WebAdmin set a dif-
Version transfer not possible: ferent EIM card and / or
The country and/or sales sales channel.
channel in the EIM card does
not match the configuration
data in the Flash

Mitel 415/430 as of R4.1 207

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

F0 F1 F2 F3 F4 SYS Category / Description Remedy

– R – R – R –R –R Software: Load new system software
Version transfer not possible: onto mainboard
Software release unknown.
– R – R R R – R – R Software: Contact Support. A differ-
Incompatible Boot software ent Boot software may
have to be loaded.
– R R – – R – R – R Software/Hardware: Load correct system soft-
General copy error ware onto mainboard or
replace communication
server.
– R R – R R – R – R Software: Load correct system soft-
Copy error between file sys- ware onto mainboard or
tem and DRAM replace communication
server.
– R R R – R – R – R Factory Server Error: For the manufacturer only
No DHCP
– R R R R R – R – R Factory Server Error: For the manufacturer only
No TCP connection
R – – – – R – R – R Software: Contact Support. The file
corrupt file system system must be reformat-
ted.
R R R R R R – R – R Software: New system software
Emergency Upload must be loaded with EUL
Functional system software no via LAN (see page 186).
longer available
– – – – – – Software: Contact Support. A differ-
General boot error ent Boot software may
have to be loaded.
R –R –R R –R –R R –R –R R –R –R R –R –R R – R – R Software: Load new software onto
General error mainboard. If unsuccess-
ful, contact Support.

208 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

6. 4. 4 Carrying out functions

The pilot key is used to carry out various functions. For certain functions the system
has to be in a particular operating state beforehand.

6. 4. 4. 1 Shutting down the communication server

The communication server can be shut down in a controlled manner. It then remains in
Shutdown Mode (see "Shutdown Mode", page 206) for three minutes before it starts
again automatically. Within these three minutes, the communication server can be dis-
connected from the power supply.
Requirement:
The system is in "Application Command Mode", page 204.

1. Press the pilot key with a short keypress (SC) until "F1" lights up.
2. Press the pilot key with a long keypress (LC)
→ After 2 second keypress "F1" lights up green by way of confirmation.
→ After the key is released the communication server is shut down and displays
Pattern [22] for three minutes.

Tip:
You can also shut down the communication server in a controlled manner via WebAdmin in the
Maintenance / System reset ( =4e) view.

6. 4. 4. 2 Normal restart with database backup

The following sequence carries out a database backup and saves the data on the com-
munication server’s internal file system. The communication server is then restarted
automatically:
Requirement:
The system is in "Application Command Mode", page 204.

1. Press the pilot key several times with a short keypress (SC) until "F2" lights up.
2. Press the pilot key with a long keypress (LC)
→ After 2 second keypress "F2" lights up green by way of confirmation.
→ Once the key is released, a database backup is carried out followed by a commu-
nication server restart.

Tip:
You can also restart the communication server via WebAdmin in the Maintenance / System
reset ( =4e) view.

Mitel 415/430 as of R4.1 209

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

6. 4. 4. 3 Forced restart without database backup

In all operating states a very long keypress (VLC) on the pilot key forces the communi-
cation server to restart. The restart is initiated after the key is released.

Note:
Forced restart is the same as power failure and can result in loss of data. This may prevent a
communication server start-up. Forced restart should only be initiated if normal restart (via the
control key or with WebAdmin) is no longer possible for any reason.

6. 4. 4. 4 Enabling / disabling password-free access

The following sequence changes the status of the password-free access:
Requirement:
The system is in "Application Command Mode", page 204.

1. Press the pilot key with a short keypress (SC) until "F3" lights up.
→ "F3" indicates the current status: steady red= disabled, steady orange = enabled.
2. Press the pilot key with a long keypress (LC)
→ After 2 second keypress "F3" lights up green by way of confirmation.
→ When the key is released, the status changes and the system jumps back to orig-
inal Mode.
→ "F3" indicates the current status: inactive = disabled, steady orange = enabled.

Note:
You are strongly advised to keep the password-free access open only for as long as necessary.
For security reasons it is automatically deactivated again after a restart or at the latest after 60
minutes.

6. 4. 4. 5 Enabling / disabling the dial-up connection to the

AIN
The following sequence changes the status of the remote access to the AIN via an ex-
ternal dial-up connection:
Requirement:
The system is in "Application Command Mode", page 204.

1. Press the pilot key several times with a short keypress (SC) until "F4" lights up.
→ "F4" indicates the current status: steady red= disabled, steady orange = enabled.
2. Press the pilot key with a long keypress (LC).
→ After 2 second keypress "F4" lights up green by way of confirmation.
→ When the key is released, the status changes and the system jumps back to orig-
inal Mode.
→ "F4" indicates the new status: inactive = disabled, steady orange = enabled.

210 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

Note:
You are strongly advised to keep the remote access to the AIN via an external dial-up connec-
tion open only for as long as necessary. There is no time limit to the access and it remains in
place even after a system restart.

6. 4. 4. 6 Carrying out a first start

The following sequence carries out a system first start.

Note:
A first start deletes all the configuration data already stored and replaces it with the default val-
ues of the sales channel. Therefore, always back up the configuration data before a first start.
The system-specific data such as the system ID, system type, sales channel, licence code, soft-
ware generation and IP address of the system are preserved.
Requirement:
The system is in "Boot Command Mode", page 205.

1. Press the pilot key briefly.

→ "F1" lights up red.
2. Press the pilot key with a long keypress (LC).
→ After 2 second keypress "F1" lights up green by way of confirmation.
→ The first start is initiated once the key is released.
→ The system now deletes the database. This is indicated with Pattern [19]. There-
after, the system changes to Normal Mode after a brief interruption. It now still re-
mains up to five minutes until the communication server is accessible with
WebAdmin.

Tab. 102 Patterns while the database is deleted as a result of a first start
Pattern Dura-
F0 F1 F2 F3 F4 SYS Meaning
No. tion [s]
[19] G G G G – – – ~5 Deleting the database

Tip:
You can also initiate a first start of the communication server via WebAdmin in the Maintenance
/ System reset ( =4e) view. There you can also reset the sales channel in addition to a first
start.

Mitel 415/430 as of R4.1 211

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

6. 4. 4. 7 Resetting the IP address

The IP address data is stored on the EIM card and is retained even after a first start.
The following sequence only resets the IP address data of the communication server to
the default values. All the other data is retained.
Requirement:
The system is in "Boot Command Mode", page 205.

1. Press the pilot key several times with a short keypress (SC) until "F2" lights up red.
2. Press the pilot key with a long keypress (LC)
→ After 2 second keypress "F2" lights up green by way of confirmation.
→ The IP address data is reset to the default values once the key is released. The
startup then continues normally.

Default values of the IP address data:

• IP address: 192.168.104.13
• Subnet mask: 255.255.255.0
• Gateway: 0.0.0.0

6. 4. 4. 8 Thorough RAM test

To carry out a thorough RAM test during startup, press the pilot key briefly (SC) during
the orange LED test (pattern[2]). The thorough RAM test lasts for approx. 2 minutes
and is displayed with Pattern [4]. The startup then continues normally.

6. 4. 4. 9 Emergency Upload via LAN

An Emergency Upload is required whenever there is no longer any executable system
software stored on the communication server for whatever reason or if a downgrade to
an older software version is to be carried out.
For this, proceed as described in "Loading new or older system software with System
Search", page 186.

212 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

6. 5 Operations supervision

6. 5. 1 Event message concept

The system generates an event message every time an event or error occurs. The
event tables are used to specify how often an event message of a particular type may
be generated by the system over a given period before the event message is sent to
the allocated signal destinations.
There are 7 event tables that can be allocated to 8 signal destinations:

Event message

Event tables

1 2 3 4 5 6 7
Event type Event type Event type Event type Event type Event type Event type
Time period

Time period

Time period

Time period

Time period

Time period

Time period
Occurrences

Occurrences

Occurrences

Occurrences

Occurrences

Occurrences

Occurrences
Signal
destinations

SRM
External Local destination
System phone Event log E-mail ATAS-Interface (Secure IP Remote
destination SNMP destination
Management)

System phone PC on TA / ISDN • PC on TA / ISDN WebAdmin Internal or Alarm server or SRM server
with display in gateway gateway external other external
message group • PC on Ethernet endpoints that equipment
Interface can receive
e-mails

Fig. 84 Distribution principle for an event message

6. 5. 1. 1 Event types
Event messages have a certain severity level: Normal (blue), Serious (yellow) and Crit-
ical (red). Many event messages have both a negative impact (error occurred) and a
positive impact (error corrected). Some event messages have no impact and, thus, no
match. Severity level and impact are indicated in the event table.
If an SRM server is indicated as signal destination, the event message severity level
results in a change of system status. This can be seen in the SRM agent and is dis-
played with the corresponding colour (see also section "SRM destination", page 235).

Mitel 415/430 as of R4.1 213

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

Tab. 103 Event types, in alphabetical order

Event message Trigger condition Details1) Severity
ATAS: Connection estab- ATAS: connection (re) established date, time critical
lished (positive,
with
match)
ATAS: Connection lost ATAS: connection lost Cause (0: Logoff, 1: critical
missing cycle signal), (negative,
date, time with
match)
BluStar Client back within the A sufficient number of licences is now available Parameter 1, licence Serious
licence limit again for BluStar clients. type, total purchased (positive,
Parameter 1: 0 (not used) licences, date, time with
Licence type: 0 and 1: (not used), 2: BluStar CTI, match)
3: BluStar Softphone, 4: BluStar video option,
5: BluStar Presence option
Card in service A card that was previously out of service is back Number of the critical
in service again. expansion slot, date, (positive,
time with
match)
Card out of service A card previously in operation has stopped func- Number of the critical
tioning. expansion slot, date, (negative,
time with
match)
Card reset A reset was carried out for one card Number of the Normal
expansion slot, date, (without
time match)
Charge counter overflow Individual cumulative counter or cost centre Cause (0: User / Serious
counter overflow 1: Cost centre / (without
2: Exchange line / match)
3: Room), number,
date, time
CL printer available again Printout on the system printer available once Date, time Serious
again (positive,
with
match)
CL printer blocked • No response from system printer for past 4 Interface, inter- Serious
minutes faces/card number, (negative,
• Printer out of paper or switched off port number, date, with
time match)
Compatible PMS application The external hotel management system (PMS Date, time critical
application) is suitable for communicating with (positive,
the communication server. with
match)
Configuration template avail- The missing configuration template for a Mitel Date, time Serious
able SIP terminal is now available in the communica- (positive,
tion server file system. with
match)

214 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

Event message Trigger condition Details1) Severity

Connection to IP remote IP remote management connection set up (SRM Cause, date, time Normal
management (SRM) failed = Secure IP Remote Management) has failed. (negative,
Cause parameter: with
1: Connection attempt failed, 2: Authentication match)
failed, 3: File upload rejected
Connection to IP remote IP remote management connection has been Date, time Normal
management (SRM) restored (SRM = Secure IP Remote Management) suc- (positive,
cessfully restored. with
match)
Connection to PMS system A connection with a hotel management system Date, time critical
established (PMS system) has now been successfully estab- (positive,
lished. with
match)
Connection to PMS system An unsuccessful attempt was made to establish Error, date, time critical
failed a connection with a hotel management system (negative,
(PMS system). with
Reason: 1: Call rejected, 2: Destination unob- match)
tainable, 3: Destination busy, 4: Connection
timeout, 5: Wrong address, 6: Unknown error
CPU2 applications card Data Data communications with the CPU2 applica- Date, time critical
communication out of service tions card have been interrupted for an unusu- (negative,
ally long period of time (> 1 hour) due to an error with
(after a Windows update or for other reasons). match)
CPU2 applications card Data Data communications with theCPU2 applica- Date, time critical
communications back in ser- tions card have been restored. (positive,
vice with
match)
Creation instance on backup The backup communication server was unable Instance type critical
communication server failed to create or modify a user or terminal instance (0: User, 1: terminal), (negative,
with the received configuration data. user number or ter- with
Note: minal ID, date, time match)
This event message is generated by the backup
communication server.
Creation instance on backup The backup communication server was able (fol- Instance type critical
communication server suc- lowing one or more previous failed attempts) to (0: User, 1: terminal), (positive,
cessful create or modify a user or terminal instance with user number or ter- with
the received configuration data. minal ID, date, time match)
Note:
This event message is generated by the backup
communication server.
CSTA sessions within the CSTA Sessions licences are now available Number of licences, Serious
licence limit again again. date, time (positive,
with
match)
CTI first party Connection The ATPC3 first-party link was (re)established User number, date, critical
established time (positive,
with
match)

Mitel 415/430 as of R4.1 215

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

Event message Trigger condition Details1) Severity

CTI first party Connection lost The ATPC3 first-party link was interrupted User number, date, critical
because the cycle signal is missing. time (negative,
with
match)
CTI third party: Connection The ATPC3 third-party link was (re)established Date, time critical
established (positive,
with
match)
CTI third party: Connection The ATPC3 third-party link was interrupted Cause (0: Logoff, 1: critical
lost missing cycle signal), (negative,
date, time with
match)
Definitive activation licence The initial temporary activation of the communi- Date, time critical
missing cation server for a certain duration (e.g. 90 days) (negative,
was started. After this period, the communica- with
tion server switches to restricted operating mode match)
(see "Restricted operating mode", page 71).
Definitive activation licence A licence code with a definitive activation licence Date, time critical
now present was entered. (positive,
with
match)
Dual Homing back within the There are now enough licences available for Date, time Serious
licence limit registering SIP phones in the Mitel 6700 SIP / (positive,
6800 SIP series on a backup communication with
server. match)
Note:
This event message is generated by the backup
communication server.
E-mail successfully sent The system has now successfully sent an e- Cause/action=0000, critical
mail. e-mail client, addi- (positive,
Meaning of the parameter values in Tab. 104 tional information, with
date, time match)
ESME reachable The LAN connection between the SMSC and the IP address, date, critical
ESME is now available time (positive,
with
match)
ESME unreachable The LAN connection between the SMSC and the IP address, date, critical
ESME is interrupted time (negative,
with
match)
Ethernet activated again The overload on the Ethernet interface no longer Date, time Normal
exists. The interface has been reactivated. (positive,
with
match)
Ethernet deactivated due to The system has detected an overload on the Date, time Normal
high load Ethernet interface. The interface is temporarily (negative,
deactivated. with
match)

216 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

Event message Trigger condition Details1) Severity

External auxiliary power sup- The external auxiliary power supply to the com- Date, time Normal
ply failed (Mitel 470 only) munication server has failed. If the auxiliary (negative,
power supply unit has been used for redundant with
operation, there are no short-term limitations. If match)
the auxiliary power supply unit has been used to
increase the power supply, the internal power
supply unit overflow must be calculated.
External auxiliary power sup- The external auxiliary power supply to the com- Date, time Normal
ply in service (Mitel 470 only) munication server is working. (positive,
with
match)
External event message des- External signal destination not automatically Cause (0: Busy Serious
tination not reachable reachable /1: Not available (negative,
/2:(not used), with
2: Barred /3: not match)
defined), date, time
External event message des- External signal destination is now reachable Date, time Serious
tination reachable (positive,
with
match)
Fan failure (Mitel 415/430 The fan is jammed or defective or the connection Parameter, date, critical
only) is no longer making contact. time (negative,
• Parameter = 0: No more fans in operation. with
→ Risk of overheating: Replace defective fan. match)
Fan failure (Mitel 470 only) The fan is jammed or defective or the connection Parameter, date, critical
is no longer making contact. time (negative,
• Parameter = 0: No more fans in operation. with
→ Risk of overheating: System shut down match)
after 2 minutes.
→ Replace defective fan.
• Parameter = 1: Only one fan left in operation.
→ System still running with only one fan.
→ Replace defective fan.
Fan in operation The fan is back in service again after a failure. Parameter, date, critical
(Mitel 415/430 only) • Parameter = 0: Fan back in service again. time (positive,
with
match)
Fan in operation (Mitel 470 The fan is back in service again after a failure. Parameter, date, critical
only) • Parameter = 0: A fan is back in service again. time (positive,
• Parameter = 1: Second fan back in service with
again. match)
FIAS command buffer full The command buffer to the PMS interface is full. Date, time critical
(negative,
with
match)

Mitel 415/430 as of R4.1 217

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

Event message Trigger condition Details1) Severity

FIAS interface usable again The command buffer to the PMS interface is Date, time critical
back below the critical limit. (positive,
with
match)
G.729 Codecs within the Free G.729 codecs are once again available for Date, time Serious
licence limit again connections. (positive,
with
match)
Inactive radio unit port Radio unit not responding Card number, port Serious
Reason: 0: Startup running, 1: Not registered, number, radio unit (negative,
2: Various nodes, 3: Port not permitted, 4: Local ID/reason, date, time with
power supply, 5: Not connected, 6: Port reset, match)
7: Startup error, 8: Unknown error
Incompatible PMS applica- The external hotel management system (PMS PMS SW version, critical
tion application) is not suitable for communicating PMS interface ver- (negative,
with the communication server. sion, PMS interface with
driver version, date, match)
time
Incorrect or no wiring adapter There is no wiring adapter in the wiring adapter Slot number, date, Critical
(Mitel 415/430 only) slot or the wiring adapter fitted is unsuitable. time (without
match)
Insufficient bandwidth An user in an AIN is trying to set up a connection Link ID, WAN link Normal
and the bandwidth currently available with the name, available (without
WAN link is insufficient. bandwidth in Kbit/s, match)
date, clock
Internal event message desti- Local output blocked or not available Cause (0: Busy Serious
nation not reachable /1: Not available (negative,
/2:(not used), with
2: Barred /3: not match)
defined), date, time
Internal event message desti- Local output available once again Date, time Serious
nation reachable (positive,
with
match)
Internal power supply unit The internal power supply unit of the communi- Date, time Normal
failed (Mitel 470 only) cation server has failed. If the auxiliary power (negative,
supply unit has been used for redundant opera- with
tion, there are no short-term limitations. If the match)
auxiliary power supply unit has been used to
increase the power supply, the external power
supply unit overflow must be calculated.
Internal power supply unit in The internal power supply unit of the communi- Date, time Normal
service (Mitel 470 only) cation server is in service. (positive,
with
match)

218 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

Event message Trigger condition Details1) Severity

IP address added to the DoS A DoS attack has taken place beyond the maxi- IP address, Cause Normal
black list mum configured admissible registration (0: Registration / (negative,
attempts or transactions. The IP address con- 1: Too many transac- with
cerned has been included in the black list and tions / 2: No session / match)
will remain blocked for a set period. 3: modified mes-
sage), date, time
IP address The IP address of the communication server has Date, time Normal
changed: Regenerate TLS changed. The TLS certificates have to be regen- (without
certificates erated. For terminals downcircuit from a NAT match)
without ALG the public NAT gateway address
has to be configured.
IP address removed from the An IP address added previously due to a DoS IP address, date, Normal
DoS black list (Denial of Service) attack was again removed time (positive,
from the black list and is no longer blocked. with
match)
IP phone: Connection lost An IP system phone is no longer connected to User number, termi- Serious
the communication server. nal ID, date, time (negative,
with
match)
IP phone: Connection re- An IP system phone has re-established the con- User number, termi- Serious
established nection to the communication server. nal ID, date, time (positive,
with
match)
IP system phone licence is A sufficient number of licences is now available Date, time Serious
now available again for MiVoice 5361 IP / 5370 IP / 5380 IP. (positive,
with
match)
Language file download The downloading of a language file via FTP Parameter 1: FTP Normal
failed server for an MitelSIP terminal has failed. server address, (negative,
Parameter 2: Lan- with
guage file type and match)
name, date, time
Language file download suc- The downloading of a language file via FTP Parameter 1: FTP Normal
cessful server for an Mitel SIP terminal has been suc- server address, (positive,
cessfully completed. Parameter 2: Lan- with
guage file type and match)
name, date, time
LCR on alternative network Automatic switch from primary network provider Provider ID, date, Normal
provider to secondary network provider using LCR func- time (without
tion match)
Licence for integrated A sufficient number of licences is now available Date, time Serious
mobile/external phone availa- again for integrated mobile/external phones. (positive,
ble with
match)
Licence for PMS interface The Hospitality PMS Interface licence or a suffi- Date, time Serious
available cient number of Hospitality PMS Rooms (positive,
licences are now available. with
match)

Mitel 415/430 as of R4.1 219

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

Event message Trigger condition Details1) Severity

Licence invalid, restricted The system software loaded requires a software Date, time Normal
operating mode 4 hours after release licence. Without this licence the system (without
restart software’s functionality is severely restricted 4 match)
hours after the restart.
Licences for offline opera- The maximum period of 36 hours for the tempo- Date, time Critical
tions expired rary licence activation has expired. (without
match)
Local supply error on radio Local power supply of a SB-4+ / SB-8 / SB-8ANT Card number, port critical
unit radio unit failed or unavailable number, date, time (negative,
with
match)
Local supply on radio unit Local power supply of a SB-4+ / SB-8 / SB-8ANT Card number, port critical
available is now again available number, date, time (positive,
with
match)
Mains voltage failure Event message once mains power is restored Date, time Normal
• Mains power has failed more frequently than (without
entered in the trigger table match)
Malfunction A hardware or software error has occurred. The Error ID, date, time Normal
error ID can help Support to pinpoint the possi- (without
ble cause of the error. match)
Mitel Dialer within the licence Mitel Dialer user licences are now available Date, time Normal
limit again again. (positive,
with
match)
Mitel SIP terminals within the Mitel SIP Terminals and Mitel 8000i Video Parameter 1=1: Mitel Serious
licence limit again Options licences are now available. SIP Terminals (positive,
licence, Parameter with
2=1: Mitel 8000i match)
Video Options
licence, date, time
Monitor event Monitor event Monitor Type, Date, Normal
Time (without
match)
No configuration template A configuration template for a Mitel SIP terminal No configuration Serious
is missing in the communication server file sys- template, date, time (negative,
tem. Without the configuration template, no con- with
figuration file can be generated for this terminal match)
type.
No DECT DSP channels DECT channels on DSP-0x overloaded Date, time Normal
available (without
match)
No DTMF receiver available A permanent DTMF receiver (for detection suffix BCS Ref., date, time Normal
for integrated mobile/exter- dialling function codes) could not be assigned to (without
nal phones an integrated mobile/external phone with match)
enhanced functionality.

220 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

Event message Trigger condition Details1) Severity

No response from network No answer to Call Setup on BRI-T/PRI interface Port number of the Normal
exchange line circuit, (without
date, time match)
No response from user No answer to incoming DDI call from user on S DDI No., date, time Normal
bus or DSI (without
match)
Node: Connection lost A node is not connected to the Master for a cer- Node number, date, critical
tain amount of time (configurable). time (negative,
with
match)
Node: Connection re-estab- A node is reconnected with the Master for a cer- Node number, date, critical
lished tain amount of time (configurable) after an inter- time (positive,
ruption. with
match)
Not enough licences for inte- The connection setup with an integrated Number of licences, Serious
grated mobile/external mobile/external phone has failed because the number of configured (negative,
phones number of configured mobile/external phones is mobile/external with
greater than the number of licences available. phones, date, time match)
All the integrated mobile/external phones
remain blocked until a sufficient number of
licences are available.
NTP: Time synchronisation Time synchronization via the NTP server (NTP = Date, time Serious
failed Network Time Protocol) has failed. (negative,
with
match)
NTP: Time synchronisation Time synchronization via the NTP server (NTP = Date, time Serious
re-established Network Time Protocol) has been restored. (positive,
with
match)
Outgoing call rejected Call rejected by the network Port number of the Normal
• On any line: error code 34 exchange line circuit, (without
• On required line group: cause, date, time match)
error code 44
Overheat (Mitel 415/430 The temperature inside the communication Card number, tem- critical
only) server is too high. The appropriate measures perature, date, time (negative,
must be taken immediately to improve the heat with
dissipation, e.g. by providing the required clear- match)
ances, lowering the ambient temperature or
installing the fan from the rack-mounting set
(Mitel 430 only).

Mitel 415/430 as of R4.1 221

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

Event message Trigger condition Details1) Severity

Overheat (Mitel 470 only) The temperature inside the communication Card number, tem- critical
server is too high. Appropriate measures must perature, date, time (negative,
be taken immediately to improve heat dissipa- with
tion. Measures are automatically adopted, match)
depending on where the overheating occurs:
FXO and FXS interface card:
• the ports are deactivated in groups of 4 ports.
• Once they have cooled down below a defined
card-specific value, the ports are automatically
reactivated group by group.
CPU2 applications card
• The card will be completely deactivated. Once
it has cooled down below a defined value, the
card is automatically reactivated.
Internal power supply unit PSU2U or call man-
ager card CPU1:
• the communication server will be shut down
completely.
Notes:
• To prevent the system from overheating, no
more than 30% of the FXS ports should be
active simultaneously per 32FXS card and no
more than 50 FXS ports per system.
• PRI, BRI and DSI cards do not have tempera-
ture sensors and are therefore never deacti-
vated due to overheating.
Overload detected on USB A (current) overload was detected on one of the Date, time Normal
port (CPU2) (Mitel 470 only) USB interfaces on the applications card (CPU2). (without
Note: The maximum current input at the USB match)
interfaces varies:
Port out of service A port previously in operation has stopped func- Number of the slot, Normal
tioning. relevant port number, (without
date, time match)
QSIG licence limit reached Maximum number of licensed outgoing connec- Route number, user Normal
tions with QSIG protocol exceeded number, date, time (without
match)
Radio unit port active The radio unit is responding again Card number, port Serious
number, date, time (positive,
with
match)
Register error • Card not fitted Card number, date, Normal
• Card not logged on time (without
• Card defective match)
Remote maintenance disa- Remote maintenance has been deactivated Date, time Normal
bled (positive,
with
match)

222 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

Event message Trigger condition Details1) Severity

Remote maintenance ena- The remote maintenance has been activated Date, time Normal
bled (The report is output unfiltered on local destina- (negative,
tions). with
match)
Restricted operating mode Restricted mode could be disabled again. Date, time critical
disabled (positive,
with
match)
Restricted operating mode The communication server has switched to Cause, date, time critical
enabled restricted mode. (negative,
Cause: 0: No valid licence with
match)
Satellites missing after super- After an AIN update (Master and all satellites) Total satellites miss- Normal
vision time some satellites no longer have a connection to ing, Satellites rolled (without
the Master. back, Date, Time match)
Send e-mail failed The system was unable to send an e-mail Cause/action, e-mail critical
because an error occurred. client, additional (negative,
Meaning of the parameter values in Tab. 104 information, date, with
time match)
SIMPLE/MSRP back within There are now enough licences available for Date, time Serious
the licence limit using the MSRP and/or SIMPLE protocol for (positive,
users. with
match)
SIP account available The SIP account has successfully registered Provider, account, critical
with the SIP provider. date, time (positive,
with
match)
SIP account not available The SIP account cannot register with the SIP Provider, account, critical
provider for a certain reason (0: Provider unob- date, time (negative,
tainable / 1: no permission). The event is trig- with
gered only if the parameter Registration required match)
is configured to Yes.
SMS gateway reachable External SMS gateway again reachable Date, time critical
(positive,
with
match)
SMS gateway unreachable External SMS gateway unobtainable by network Date, time critical
provider or incorrectly configured (negative,
with
match)
Software upgrade IP system The software update of an MiVoice 5361 IP / User number, termi- critical
phone failed 5370 IP / 5380 IP has failed for the stated rea- nal ID, reason, date, (negative,
son. time with
match)

Mitel 415/430 as of R4.1 223

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

Event message Trigger condition Details1) Severity

Software upgrade IP system The software update of an MiVoice 5361 IP / User number, termi- critical
phone successful 5370 IP / 5380 IP has now been successfully nal ID, date, time (positive,
completed after unsuccessful attempt(s). with
match)
Software upload During an upload in system status: Parameter 1: Normal
• Update running • 0: "New communi- (without
• Supervision running cation server soft- match)
• Normal operation ware loaded, start-
ing...",
• 1: New communi-
cation server soft-
ware crashed, roll-
back performed
• 3: New communi-
cation server soft-
ware started and
running well
Date, time
Standard SIP terminals within SIP Terminals and Video Terminals licences are Parameter 1=1: SIP Serious
the licence limit again now available. Terminals licence, (positive,
Parameter 2=1: with
Video Terminals match)
licence, date, time
Synchronisation loss on trunk A BRI/PRI interface entered in the clock pool Port number, date, Serious
has lost the system clock time (negative,
with
match)
Synchronisation re-estab- Synchronization with the network has been Date, time Serious
lished restored on at least one BRI/PRI interface. (positive,
with
match)
Synchronisation with backup The primary communication server was unable Backup communica- critical
communication server failed to transmit the configuration data to the backup tion server ID, date, (negative,
communication server. time with
Note: match)
This event message is generated by the primary
communication server.
Synchronisation with backup The primary communication server was able Backup communica- critical
communication server suc- (following one or more previous failed attempts) tion server ID, date, (positive,
cessful to transmit the configuration data to the backup time with
communication server. match)
Note:
This event message is generated by the primary
communication server.
Synchronization on trunk re- A BRI/PRI interface entered in the clock pool Port number, date, Serious
established has been successfully re-synchronized with the time (positive,
system clock. with
match)

224 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

Event message Trigger condition Details1) Severity

System memory usage below The memory usage in the file system for a spe- File type ID, memory Serious /
the critical range again cific purpose has again fallen below a defined usage in %, date, Critical
(Serious severity level) or critical (Critical sever- time (positive,
ity level) value. with
Purpose (file type ID): match)
0: File system, 1: Application, 2: Crash-Log,
3: Monitor-Log, 4: Announcement service,
5: Voice mail, 6: Music on hold, 7: Data backup,
8: Hospitality/Accommodation, 9: User folder
System memory usage over The memory usage in the file system for a spe- File type ID, memory Serious /
the critical range cific purpose has exceeded a defined (Serious usage in %, date, Critical
severity level) or critical (Critical severity level) time (negative,
value. with
Purpose (file type ID): match)
0: File system, 1: Application, 2: Crash-Log,
3: Monitor-Log, 4: Announcement service,
5: Voice mail, 6: Music on hold, 7: Data backup,
8: Hospitality/Accommodation, 9: User folder
System overload Network access attempted when all lines are Route number, user Normal
seized or the system is overloaded. number, date, time (without
match)
System phone in service A system phone on the DSI bus is ready for Card number, port critical
again operation again. number, user num- (positive,
ber, date, time with
match)
System phone out of service A system phone on the DSI bus is defective or Card number, port critical
was disconnected. number, user num- (negative,
ber, date, time with
match)
Temperature within normal Following overheating, the temperature inside Card number, tem- critical
range again the communication server is back in the normal perature, date, time (positive,
operating range. with
match)
Temporary activation expires Reminder of the missing, definitive activation Expiration date Normal
on licence following connection set-up with the [DD.MM.YYYY], (without
communication server. date, time match)
Terminal power Rated output slightly exceeded for > 4 s. Date, time critical
supply: Overload (Mitel 470 (negative,
only) with
match)
Terminal power Rated output clearly exceeded for 4 s Date, time critical
supply: Shutdown (Mitel 470 (negative,
only) with
match)
Terminal power The power supply to the terminals was switched Date, time critical
supply: Switching back on back on after deactivation due to overflow. (positive,
(Mitel 470 only) with
match)

Mitel 415/430 as of R4.1 225

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

Event message Trigger condition Details1) Severity

Terminal power The power supply to the terminals is back in the Date, time critical
supply: Within normal range normal rated output range following a slight, (positive,
again (Mitel 470 only) preceding overflow. with
match)
Test event message The configuration of message destinations can Date, time Serious
be tested with this event message. (without
match)
The communication server The communication server was restarted manu- Date, time Critical
has been restarted ally or automatically due to an error. (without
match)
The licence limit for BluStar A BluStar client was unable to register because Parameter 1, licence Serious
clients has been reached. there are too few licences for this client type. type, total purchased (negative,
Parameter 1: 0 (not used) licences, date, time with
Licence type: 0 and 1: (not used), 2: BluStar CTI, match)
3: BluStar Softphone, 4: BluStar video option,
5: BluStar Presence option
The licence limit for CSTA An application is unable to set up a CSTA ses- Max. number of Serious
sessions has been reached sion to monitor/check a terminal because there licences, date, time (negative,
are too few CSTA Sessions licences available. with
match)
The licence limit for Dual A SIP phone in the Mitel 6700 SIP / 6800 SIP Date, time Serious
Homing has been reached series has attempted to register on a backup (negative,
communication server and not enough licences with
are available. match)
Note:
This event message is generated by the backup
communication server.
The licence limit for G.729 An attempt was made to set up a G.729 connec- Max. number of Serious
codecs has been reached. tion, but there are no free G.729 codecs availa- licences, date, time (negative,
ble at present. with
match)
The licence limit for Mitel Mitel Dialer could not be linked to a user Total purchased Normal
Dialer has been reached because too few licences are available. licences, date, time (negative,
with
match)
The licence limit for Mitel SIP A Mitel SIP terminal is unable to register or use Parameter 1=1: Serious
terminals has been reached the video functionality because there are too few Missing Mitel SIP (negative,
Mitel SIP Terminals or Mitel 8000i Video Options Terminals licence, with
licences available. Parameter 2=1: match)
Missing Mitel 8000i
Video Options
licence, Parameter
3=3: Max. number of
licences, date, time
The licence limit for SIM- A third-party application wishes to use the Date, time Serious
PLE/MSRP has been MSRP and/or SIMPLE protocol for a user, but (negative,
reached not enough licences are available. with
match)

226 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

Event message Trigger condition Details1) Severity

The licence limit for standard A standard SIP terminal is unable to register or Parameter 1=1: Serious
SIP terminals has been use the video functionality because there are too Missing SIP Termi- (negative,
reached few SIP Terminals or Video Terminals licences nals licence, Param- with
available. eter 2=1: Missing match)
Video Terminals
licence, Parameter
3=3: Max. number of
licences, date, time
The licensing limit for the If in WebAdmin the 37. user is opened and no Date, time Serious
maximum number of users Mitel 470 Expansion licence is in place. (negative,
has been reached with
match)
The maximum number of A Mitel 470 Expansion licence is now available Date, time Serious
users is within the licence or the number of users has been reduced to 36. (positive,
limit again with
match)
TLS certificate expires soon A TLS certificate for a SIP node or SIP endpoint Type of endpoint Serious /
is about to expire (Serious severity level) or has (0: Mitel, 1: 3rd Critical
just expired (Critical severity level) and needs to party), node ID or (without
be renewed. certificate name, match)
If the endpoint type is = 0 (Mitel), then is param- date, time
eter 2 = node ID.
If the endpoint type is = 1 (3rd party), then the
remaining parameter data contains the first
eleven characters of the certificate name.
TLS certificate update failed The update of the TLS certificate for an SIP Type of endpoint critical
node or SIP endpoint via FTP has failed and (0: Mitel, 1: 3rd (negative,
needs to be renewed manually. party), node ID or with
If the endpoint type is = 0 (Mitel), then is param- certificate name, match)
eter 2 = node ID. date, time
If the endpoint type is = 1 (3rd party), then the
remaining parameter data contains the first
eleven characters of the certificate name.
TLS certificate update suc- A TLS certificate for a SIP node or SIP endpoint Type of endpoint critical
cessful was successfully renewed. (0: Mitel, 1: 3rd (positive,
If the endpoint type is = 0 (Mitel), then is param- party), node ID or with
eter 2 = node ID. certificate name, match)
If the endpoint type is = 1 (3rd party), then the date, time
remaining parameter data contains the first
eleven characters of the certificate name.
TLS certificate was A TLS certificate has been generated. If genera- Date, time Normal
generated: Upgrade non- tion is manual, the certificate must be imported (without
Mitel endpoints now manually into the Mitel SIP nodes. The certifi- match)
cate must always be imported manually on all
non-Mitel nodes and non-Mitel endpoints.
Too few FoIP channels Setting up a fax connection via T.38 failed Available FoIP chan- Normal
because no FoIP channel is available. nels on node (without
match)

Mitel 415/430 as of R4.1 227

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

Event message Trigger condition Details1) Severity

Too few licences for IP sys- A MiVoice 5361 IP / 5370 IP / 5380 IP was una- Date, time Serious
tem phones ble to register because there are too few IP sys- (negative,
tem phone licences. with
match)
Too few licences for PMS Either the Hospitality PMS Interface licence is Number of licensed Serious
interface missing or the number of Hospitality PMS rooms, number of (negative,
Rooms licences available is insufficient. configured rooms, with
date, time match)
Too few VoIP channel Connection setup failed because the licence No. of licensed VoIP Normal
licences limit for simultaneously active VoIP channels channels, Date, Time (without
has been reached. match)
Too few VoIP channels An user is trying to set up a connection that Available VoIP chan- Normal
requires one or more VoIP channels which are nels on this node, (without
currently not available. date, time match)
Too many errors with the An unusual amount of errors (more than 50 per Error ID, date, time Normal
same ID hour) with the same error ID have occurred. (without
match)
Too many event messages Number of message types exceeds limit entered Date, time Normal
in the table on: (without
• "Synch. "Synch.loss on BRI/PRI" match)
• "Outgoing Call Rejected"
• "No response from network"
Too much user data System capacity exceeded Date, time Critical
(without
match)
Total synchronization loss Network synchronisation has failed on all Date, time Serious
BRI/PRI interfaces (negative,
with
match)
Trial licence expired The duration for which a trial licence can be Licence ID, date, Normal
used for a specific feature has expired and there time (without
is no valid licence. match)
USER EVENT MESSAGE With *77[nnnn] from a terminal nnnn [0000...99999], Serious
user number, date, (without
time match)
User memory usage below The memory usage in the file system for a spe- User number, mem- Serious /
the critical range again cific user has again fallen below a defined (Seri- ory usage in %, date, Critical
ous severity level) or critical (Critical severity time (positive,
level) value. with
match)
User memory usage over the The memory usage in the file system for a spe- User number, mem- Serious /
critical range cific user has exceeded a defined (Serious ory usage in %, date, Critical
severity level) or critical (Critical severity level) time (negative,
value. with
match)

228 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

Event message Trigger condition Details1) Severity

Wake-up call failed The room wake-up call was not answered Room No., date, time Normal
(negative,
with
match)
Wake-up order confirmed The room wake-up call has now been answered Room No., date, time Normal
(positive,
with
match)
1) The node is also always indicated in an AIN.

Tab. 104 Meaning of the parameter values for the event message Send e-mail failed
Parameter 1 (XXYY) Parameter 2: Parameter 3:
Additional info
Value Reason (XX) Action (YY)1) E-mail client depending on the
e-mail client (XXYY)
00 Not defined Not defined Not defined
01 E-mail memory full Connection set up to Voice mail XX: Mailbox ID
SMTP server YY: Message ID
02 SMTP server access data invalid Extended registration Auto backup
on SMTP server
03 SMTP client cannot set up a connec- Registration on SMTP Call recording User number
tion to the server server
04 Authentication failed Transmission of e-mail Event message
address
05 Continuous negative answer from Transmission of e-mail Call logging for
SMTP server recipient address hospitality
06 Temporary negative answer from Prepare data transmis- Configuration XX: User ID
SMTP server sion files YY: Terminal ID
07 No answer from SMTP server Data transmission in
progress
08 E-mail attachment not found End data transmission
09 Invalid host, domain or IP address on Prepare authentication
the communication server (LOGIN)
10 E-mail text too long (body) User name authentica-
tion (LOGIN)
11 E-mail attachment too large Password authentica-
tion (LOGIN)
12 Format of e-mail attachment not sup- Authentication (PLAIN)
ported

Mitel 415/430 as of R4.1 229

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

Parameter 1 (XXYY) Parameter 2: Parameter 3:

Additional info
Value Reason (XX) Action (YY)1) E-mail client depending on the
e-mail client (XXYY)
13 No e-mail recipient address Prepare encrypted
authentication (CRAM-
MD5)
14 Invalid e-mail recipient address Encrypted authentica-
tion (CRAM-MD5)
15 Invalid e-mail sender address Preparing to send next
e-mail
1) Action carried out by the SMTP client at the point when the error occurred.

6. 5. 1. 2 Event tables
Event tables ( =f4) list all the event messages the system is capable of generating
(see Tab. ).
There are 7 event tables. After a first start, all event tables are assigned at least one
destination. This assignment can be modified in the Message destinations (( =h1))
view. Each event table can be configured individually. This means it is possible with a
filter to decide which event message – if any – should be sent to a particular signal
destination either immediately, with a delay or not at all.

• No event:
This type of incoming event messages are never sent to the linked destination.
• Every event:
This type of incoming event messages are all sent to the linked destination.
• Custom:
With this setting, you can determine how often the event message may appear for
each period, until they are sent to the linked destination.
The Frequency of an event message may range between 2 and 20. The Period is
indicated in hours, ranging between 1 and 672. The longest time period corre-
sponds to 28 days or 4 weeks.

Tab. 105 Example of event table

Event type Frequency Time period
Total synchronization loss 10 1

In this example an event message is sent to the message destinations if there is a To-
tal synchronization loss event message when the system generates the event mes-
sage 10 times within 1 hour.

230 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

6. 5. 1. 3 Signal destinations
After a first start, all event tables are exactly assigned to a message destination. (Ex-
ception: Local destination and SNMP destination use this event table.) You can assign
event tables to several or no message destinations
The destinations are configured in the Message destinations ( =h1) view.

Signal destination system phone

Depending on the allocated event table (normally Table 1), event messages are sent to
all the system phones that have a display and are entered in message group 8.

External signal destinations

Depending on the event table allocated, event messages (normally Table 2) are sent to
a specified external signal destination. Two external signal destinations can be speci-
fied:

• 1 primary external signal destination

• 1 alternative external signal destination

If the system issues an event message, the event message opens a PPP communica-
tion channel from the public network of the communication server to a terminal adapter
or modem. Once the event message has been confirmed, the system clears down the
PPP connection.

Mitel 415/430 as of R4.1 231

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

Signalling an event message to an external signal destination

Event message

Signalling delayed
up to 5/240 min.

Call external
event message
destination

Wait for 30 s
State
Busy external event Connection established
message
destination
?
Cannot be reached / blocked

J Dialling N
attempts Delay 40 sec.
<5/2

Alternative external
event message
destination?
Wait for 30 s

State
Busy external event Connection established
message
destination
?
Cannot be
reached / blocked
J Dialling N
attempts
<5/2

J Dialling
attempts
<2

External event
Output event
message destina-
message
tion not available

Fig. 85 Flowchart of the signalling of an event message to an external signal destination

The following principles govern the way event messages are signalled to an external
signal destination:

• Individual event messages are not signalled if they occur at short intervals. The
event messages are stored temporarily for 5 minutes and then sent together to the
external signal destination.
• If over a period of one hour an attempt is made unsuccessfully to send the event
messages to the external signal destination, the signalling period is extended from 5

232 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

minutes to 4 hours. As soon as the event messages are successfully output at the
external signal destination, the time period is reset to 5 minutes.
• If over a period of 1 hour an attempt is made unsuccessfully to send an event mes-
sage to an external signal destination, the number of dialling attempts is reduced
from 5 to 2. As soon as an event message has been successfully sent, the number
of dialling attempts is increased to 5 again.
• If the attempt to send an event message to an external signal destination was un-
successful, the system will generate the event message External event message
destination missing.

Note:
Event tables and signal destinations should be set in such a way that the event message
External event message destination missing is signalled immediately to any signal destina-
tion still available.

Local signal destinations

Depending on the event table allocated, event messages (normally Table 3) are sent to
a specified local signal destination.
PPP links:
Like with an external signal destination the event message opens a PPP communica-
tion channel from the communication server to a terminal adapter or modem. Once the
event has been confirmed, the system clears down the PPP connection.
Ethernet link:
A PC connected either directly to the Ethernet interface or to the communication server
via a LAN can be configured as the local signal destination.

Notes:
– The local destination is linked with the same event table as the SNMP destination. Any
changes to the link and/or filter criteria for the linked event table also apply to the SNMP
destination.
– Event tables and signal destinations should be set in such a way that the event message
External event message destination missing is signalled immediately to any signal destina-
tion still available.

SNMP destination
Depending on the event table allocated, event messages (normally Table 3) are sent to
a specified SNMP destinations.
SNMP stands for "Simple Network Management Protocol" and is used by Network
Management Systems (NMS).
If the Network Management System is to know the potential events of the communica-
tion system, the corresponding system components have to be defined in the form of

Mitel 415/430 as of R4.1 233

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

configurable objects (Managed Objects: MO). These objects and the related event
messages are stored in an object library referred to as the Management Information
Base (MIB). The current MIB version can be downloaded from
https://pbxweb.aastra.com. The user name and password are required in order to ac-
cess the data. Registration with the "Mitel Application Partner Programm" is required.
5 SNMP destinations can be defined. Forwarding to the SNMP destinations can be ac-
tivated and deactivated independently of the forwarding to the local and external signal
destinations.

Notes:
The SNMP destination is linked with the same event table as the local destination. Any changes
to the link and/or filter criteria for the linked event table also apply to the local destination.

Signal destination event log

Normally, the signal destination event log is assigned to Event table 4. The filter on this
event table is preconfigured for most event types in such a way that event messages
are entered in the event log once they arrive.
If the signal destination event log is assigned a different event table or if event table 4
is reconfigured, the event messages are entered in the event log in accordance with
the new event table or the new configuration.
The last 254 event messages are recorded in the Event log ( =r5). Active event mes-
sages ( =mr) and the last 10 Power failures ( =bn) are recorded in separate logs.
If the maximum number of entries is exceeded, the oldest entry in each case is de-
leted.
If active event messages are available, they are indicated in WebAdmin on the left,
with the symbol.

E-mail signal destination

With the e-mail client integrated in the communication server, event messages can be
sent to internal or external e-mail destinations. Normally, the signal destination E-mail
destination is automatically assigned to event table 5. Up to 5 e-mail destinations can
be defined, and e-mail notification can be activated or deactivated globally.
For the communication server to send the e-mails the access to the e-mail service pro-
vider's SMTP server must be configured in the SMTP server ( =rm) view.

234 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

Destination alarm server (ATAS)

Event messages can also be sent via the ATAS interface, for instance, to an alarm
server. This may be an Mitel Alarm Server or a third-party alarm server. The use of the
ATAS protocol is subject to a licence.
After a first-start of the communication server, the signal destination Alarm server
(ATAS) is automatically allocated event table 6. The notification service via the ATAS
interface to the alarm server can be globally switched on or off.

SRM destination
Event messages can also be sent to the SRM server. Depending on the severity level
in the SRM agent, this changes the system status on the corresponding communica-
tion server line. The line colour changes at the same time. If the corresponding positive
event message arrives later or if the event message is confirmed in WebAdmin, the
status and colour are restored again. The following system statuses are defined:

• Normal (Blue colour):

No active event messages with the severity level Serious or Critical is available.
• Serious (Yellow colour):
At least one event message is available and needs to be closely examined. (Exam-
ple: Charge counter overflow)
• Critical (Red colour)
At least one event message is available and is hampering the system's function.
(Example: Fan failure)

Note:
Not all negative event messages have a positive match. In this case, the event messages must
be confirmed manually in WebAdmin.
Event messages, which are not Serious or Critical, are not sent to the SRM server. The severity
of individual event messages is given in the Tab. 103 table.
Example:
Power output: There are no serious or critical event messages. The communication
server line in the SRM agent is blue and the system status is on Normal.

1. The event message Charge counter overflow reaches the SRM server.
→ The communication server's system status in the SRM agent changes to Serious,
and the destinations turn yellow.
2. The event message Fan failure reaches the SRM server.
→ The communication server's system status in the SRM agent changes to Critical,
and the destinations turn red.
3. The event message Charge counter overflow is confirmed in WebAdmin in the Ac-
tive event messages view ( =mr).

Mitel 415/430 as of R4.1 235

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

→ The system status of the communication server in the SRM agent remains on
Critical, and the destinations on red, because there is still an event message with
this severity.
4. The event message Fan failure reaches the SRM server.
→ The communication server's system status in the SRM agent changes to Normal,
and the destinations turn red.

After a first-start of the communication server, the SRM destination is automatically al-
located event table 7. The notification service to the SRM destination can be switched
on or off.
On the SRM server the status modification per communication server must be allowed
and configurations are also required in WebAdmin. You can find a configuration guide
in WebAdmin help under the Message destinations =h1 view.

Testing the signal destination configuration

To test the configuration, a test event message can be separately initiated for each
destination in the WebAdmin configuration (Message destinations =h1 view). The
event message is signalled without any delay, directly at the selected signal destina-
tion.
If the communication server is connected via a modem or terminal adapter, the test
event messages will be signalled only once the connection is cleared down.

6. 5. 2 Operating state and error displays

6. 5. 2. 1 System operating state

During the start-up phase, various self-tests are performed and the individual phases
are shown in the LED display on the front panel (see "Startup Mode", page 203).
When operation is OK, the SYS LED flashes green, regularly, and once per second in
the display on the front panel. The system is in normal mode. The assignment of inter-
nal or external ports, password-free access as well as remote access via an external
dial-up connection to AIN are shown as status in the LED display (see "Normal Mode",
page 203 and "Feature Mode", page 204).

6. 5. 2. 2 System error displays

Whenever the system detects an error, it displays the corresponding error code in the
LED on the front panel (providing the communication server is still powered and the
display is working).

236 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

There are 3 types of error:

• System is running but a problem has been detected on one or more wiring adapter
slots. (See "Wiring Adapter Malfunction Mode", page 205.)
• Warning. System is still capable of running but the system function may be impaired
(see "Warning Mode", page 205).
• Serious error. System is no longer able to run (see "Error Mode", page 207).

In the event of sporadic errors check the installation for earth loops.

6. 5. 2. 3 Terminals
Tab. 106 Malfunctions on the terminal side
Error description Error cause / error handling
Digital system phones on the DSI bus display Not No terminal has yet been created on the connected port or an
Configured along with the node number, the slot incorrect terminal selection digit (TSD) has been allocated to
number and the port number. the terminal:
• Check system and terminal configuration
• Check installation and connecting cable
System phones do not obtain any dial tone when Replace phone or interface card.
seizing a line; display reads Not available.
Terminals with configurable dialling method experi- System earth must not be connected on terminals configured
ence sporadic malfunctions whenever control key is for MFV/DTMF (double signalling on Flash/earth key).
pressed.
Analogue terminals do not obtain a dial tone when No terminal has been created on the connected port or the ter-
off-hook. minal created has not been allocated to a user.
• Create a terminal and allocate a user
• Check installation or connecting cable

6. 5. 2. 4 Operating state of the Mitel DECT radio units

Each radio unit is equipped with 3 LEDs. The operating state the radio units is indi-
cated by different colours and flashing sequences in cycles of 1 s, specifically by one of
the two outer LEDs on the SB-4+ and by both outer LEDs on the SB-8 / SB-8ANT (sep-
arately for each DSI bus). Each character (G, R or -) corresponds to 1/8 of a second.
Example:
During the synchronization phase GGGGRRRR the LED flashes periodically.
1/2 second green, 1/2 second red.

Mitel 415/430 as of R4.1 237

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

Tab. 107 Flashing sequences of the status LED on the DECT radio unit
State Cycle Meaning
No flashing – – – – – – – – LED switched off / software not running / RU not connected
Red Error:

R R R R R R R – DSI bus not in order

R – – – – – – – Power supply error or DSI line too long

Green / red Startup process:

G R R R R R R R DSI ok

G R G R G R G R Software is uploaded

G G G G G R R R Synchronizing

G G G G G G G R DECT is being started

G G G G G R G R HF Power Down / DECT System Status Passive1)

Green Normal operation (requirement: LED not switched off):

G – – – – – – – All B channels available

G G G G – – – – 1 to 3 B channels busy

G G G G G G G – 3 B channels busy
1) This operating state appears in the following situations:
- During a configuration data upload
- After a system first-start
- If in WebAdmin in the DECT view ( =sa) the parameter DECT system status is set to Passive.
- If no location area is assigned to a radio unit - (This may happen after adding a radio unit to a system with
several Location Areas, which is the case when a radio unit has already been set in a Location Area unequal
0). In this case the added radio unit has to be manually allocated to the selected Location Area.)

An orange status LED indicates that DECT signalling is active, i.e. DECT sequences
are currently being transmitted between the cordless phone and the radio unit. Exam-
ples:

• With each keystroke on the cordless phone the LED briefly lights up orange.
• During a cordless phone firmware download the orange LED remains lit until the
download is completed.

On an SB-8ANT radio unit the middle LED indicates whether the internal or external
antennas are active. If the LED is lit green, the external antennas are active.

Note:
After the system initialization the radio unit starts in status "DSI ok". It is only ready to operate
once at least one DECT user has been entered in the numbering plan or once in WebAdmin the
parameter DECT system status has been set to Active.

238 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

6. 5. 2. 5 Malfunction of the Mitel DECT radio unit

Tab. 108 Malfunction of the Mitel DECT radio unit
Error description Error cause / error handling
No radio connection in a coverage area. Check LED on radio unit:
LED is flashing red (short red phase):
• Check power supply / line length of DSI bus cable
LED is flashing red (long red phase):
• Check DSI bus cable
• Unplug DSI bus cable for one minute, then reconnect
LED is flashing green (long green phase):
• All B channels busy
Radio unit not activated. LED on radio unit is flashing red/green (various patterns):
• Radio unit in startup phase
LED on radio unit is flashing red (long red phase):
• Radio unit defective
If LED on radio unit not flashing:
• Check trunk connections
• Radio unit defective
• LED of the radio units deactivated throughout the system

6. 5. 2. 6 Malfunctions of Mitel DECT cordless phones

Tab. 109 Malfunctions of Mitel DECT cordless phones
Error description Error cause / error handling
No display. • Switch cordless phone on and test
• Replace or charge battery
No radio link to radio unit; no aerial symbol. Check coverage area (within range of a radio unit).
• Check radio units in this section
Cordless phone not registered with the system
• Cordless phone registered
Impossible to dial. Keypad blocked (keylock)
• Unlock keypad
No dial tone. • Check radio units in this section
Poor connection quality (echo effect). • Turn back loudspeaker opposite (for call parties)
Cordless phone beeps approx. every 10 s during a • Replace battery immediately, either after or during the call
call (or in standby) while battery indicator is flashing. (see cordless phone user’s guide)
Call breaking up. You are moving out of range.
• Find a location with a better radio contact

Mitel 415/430 as of R4.1 239

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

Error description Error cause / error handling

A cordless phone is called from a different system Busy tone obtained and display reads Busy
phone, but cannot be reached. • Cordless phone is busy
Congestion tone obtained and display reads Circuit overload.
• All radio channels busy
If congestion tone is obtained after 8 seconds and display
reads No answer. Reasons why the cordless phone could not
be reached:
• It is switched off
• It is not within reachable radio area
• No radio channels currently available
• It is not registered with the system
• Call diverted due to unobtainable
Cordless phone is not ringing. • Activate tone ringing
The cordless phone cannot be configured; PIN miss- • Reset PIN for user (overwrite)
ing (or forgotten).

6. 5. 2. 7 Malfunctions of the DECT charging bays

Tab. 110 Malfunctions of the DECT charging bay
Error description Error cause / error handling
The cordless phone will not charge. • Connect power supply
• Check the charging contacts
• Check battery and replace if necessary.
About the charging process:
• Battery symbol on the cordless phone is flashing
(Office 135) or filling up (Office 160, Mitel 600 DECT) when
the battery is being charged.
• Check tone indicates correct contact.

240 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

6. 5. 2. 8 Longclicks on Mitel DECT cordless phones

In normal DECT cordless phone operation, long-clicking the following keys accesses
additional functions directly.

Tab. 111 Longclicks on Mitel DECT cordless phones

Mitel 600
Function Office 135 Office 160
DECT
In a list box: change scroll direction. Long-click ">" switches to "<" and vice Foxkey Foxkey —
versa right right
Direct access to the configuration menu M M —
Switch cordless phone on/off C, 0 0 End key
Switches over to the next radio system temporarily. 1 1 2
Indicates the radio system parameters (cordless phone IPEI and radio system 2 2 —
PARK). With each additional call the next radio system is indicated in each
case if there are other logons.
Indicates the cordless phone’s internal diagnostics. 3 3 —
Switches to a special alarm menu of the cordless phone. — — 31)
Indicates the data of the valid radio unit (“Show Measurement Mode”, see 4 4 —
“Planning DECT Systems” in the User’s Guide).
Indicates the cordless phone’s firmware version. 5 5 —
Jumps to the cordless phone’s service menu. — — 5
Indicates battery charge status and the type. 6 — —
Indicates the communication server’s software version. 7 7 —
Activates "semi" key lock. See Operating Instructions for details. 8 8 —
Activates key lock. See Operating Instructions for details. 9 9 #
Switch dialling type DTMF on/off. See Operating Instructions for details. —
Switch tone ringing on/off. — —
Jumps to the cordless phone’s tone ring menu. Loud- Loud- —
speaker speaker
key key
Menu for display contrast, display backlighting, area tone and overload tone. # # —
See Operating Instructions for details.
Configuration mode for hotkey. See Operating Instructions for details. Hotkey Hotkey Hotkey
Switch error messages on/off (default value: Off). Messages relating to the fol- 5 + 3 5+3 —
lowing errors cannot be switched on/off: HS logon error, incorrect location reg-
istration, no locatable radio unit, network, system or radio unit overload.
1) Mitel 630 DECT only

Mitel 415/430 as of R4.1 241

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

6. 5. 2. 9 Overload code displays Office 135 / Office 160

The overload code displays on the cordless phones Office 135 and Office 160 can be
activated and deactivated using the following key combination (toggle function):
Long-click key 5 and then long-click key 3 (long = long-click = 2 seconds).
The overload code display is always deactivated after system initialization.

Tab. 112 DECT overload code displays Office 135

Code Name Error description Error handling
05 / 06 IPEI Not Accepted Cordless phone already registered with • Delete cordless phone registration.
the system under a different number. • Try again
10 Authentication failed Registration error Try again
51 DL 04 Expiry Timer (on cordless phone) has expired Try again
70 Timer Expired MM timer in system has expired (during Try again
registration)
44 Failure to set up traffic Connection cannot be set up as too • Try again
bearer many cordless phones are phoning • If still unsuccessful after several
within the same range attempts, restart cordless phone
and try again.
45 No Quiet Channel No channel available, same as code 44 Same measures as for code 44
80 Reject Location Area. Wrong mode during logon. Logon to the system < I5
Not allowed. Mis-used • Office 135: Longclick "Home"
to indicate wrong Logon to the system > I5:
"design" version. • Office 135: Shortclick "Home"

6. 5. 3 Other aids

6. 5. 3. 1 System logs
During operation or in the event of a malfunction the communication server stores the
current operating data in the file system in the directory /home/mivo400/logs.
You can open, view and back up these log files on any storage device, in WebAdmin in
the System logs( =1w) view.

6. 5. 3. 2 File system state

In the File system state ( =e3) view you can see the thematically structured file sys-
tem's memory load. In an AIN the file systems for all nodes can be viewed.

242 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Operation and Maintenance

6. 5. 3. 3 File browser
With the File browser ( =2s) you have access to the communication server file sys-
tem and you can create new folders as well as view, import, replace or delete files in
the file system.
There are the two main areas /home/mivo400/ and /ram/. Statistical data are stored in
the RAM area while all communication server folders and files are placed in the home
directory.

Note:
Be extremely careful while replacing or deleting files. The absence of files can hamper or even
render impossible the working of the communication server.

6. 5. 3. 4 Measuring equipment for cordless systems

The aids required for measuring out DECT systems are described under “Planning
DECT Systems” in the User’s Guide.

Mitel 415/430 as of R4.1 243

syd-0580/1.2 – R4.1 – 08.2016
Annex

7 Annex

This chapter informs you about the systematic designation system and provides you
with an equipment overview of the communication server with cards, modules and
optional components. It also provides the technical data for interfaces, communica-
tion server and system terminals as well as a table overview of the digit key assign-
ments and function keys for the system phones. Finally here is a list of functions and
products no longer supported, licence information on third-party software prod-
ucts, and a table summary of related documents and online help.

7. 1 Systematic designation system

Tab. 113 PCB Designation

###///--",,,,,,,,,,''(7

PCB type (three-digit)

Project number (three-digit)

Country code and sales channel

ID

Colour code on terminals

Generation and version

Tab. 114 Explanation of the PCB Designation

Part of the PCB designation Remarks and examples
PCB type (three-digit) LPB = Printed circuit board fitted
KAB = Cable fitted
PBX = Complete system
SEV = Set packed
EGV = Terminal packed
MOV = Module/card packed
Project number (three-digit) 957 (System Mitel 415/430)
Country code and sales channel Two-digit country code as per ISO 3166,
(one to three-digit, with full stops) Sales channel (1...9) for various sales channels.
Example:
EXP = Export channels (not country-specific)
Space = No country code

244 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Annex

Part of the PCB designation Remarks and examples

ID ETAB4 = analogue terminal card with 4 FXS interfaces
Colour code on terminals Colour designation in accordance with EU directive
Generation and version Example: –3C = 3. Generation, Version C
(Generation new modules: -1)
Notes:
• A generational change is effected following substantial changes
to the functionality of a PCB.
• A change of version is effected following small changes to func-
tions or once faults have been remedied. Backward compatibility
is guaranteed.

7. 2 Rating Plate and Designation Stickers

Power
specification
System
PCB designation Type
approval
Material no.
Production date Serial number

Fig. 86 Rating plate (example Mitel 430 communication server)

MOV957. EXP.TIC-2TS-1 Mat. No. PCB Designation

P . . . . - 20 . . . . . . No.

Fig. 87 Designation stickers (example interface card)

7. 3 Equipment Overview
Tab. 115 Equipment Overview
Designation Description
PBX957.EXP.A415-2 Mitel 415 basic system with power supply unit and power cable
PBX957.EXP.A430-2 Mitel 430 basic system with power supply unit and power cable
MOV957.EXP.SM-DSPX1-1 DSP module SM-DSPX1
MOV957.EXP.SM-DSPX2-1 DSP module SM-DSPX2

Mitel 415/430 as of R4.1 245

syd-0580/1.2 – R4.1 – 08.2016
Annex

Designation Description
MOV957.EXP.TIC-2AB-1 TIC-2AB trunk card (2 x FXO)
MOV957.EXP.TIC-4AB-1 TIC-4AB trunk card (4 x FXO)
MOV957.EXP.TIC-1PRI-1 TIC-1PRI ISDN primary trunk card
MOV957.EXP.TIC-2TS-1 TIC-2TS ISDN basic trunk card/terminal interface card
MOV957.EXP.TIC-4TS-1 TIC-4TS ISDN basic trunk card/terminal interface card
MOV957.EXP.EADP4-3 Terminal card EADP4 (4 x DSI-AD2)
MOV957.EXP.ETAB4-2 Terminal card ETAB4 (4 x FXS)
LPB520.EXP.ODAB-1 Options card ODAB
MOV957.EXP.WA-2W Wiring Adapter 2W
MOV957.EXP.WA-TS0 Wiring Adapter TS0
MOV957.EXP.WA-TS1 Wiring Adapter TS1
MOV957.EXP.WA-1PRI Wiring adapter 1PRI
MOV958.EXP.EFOP-1 EFOP fan-out-panel without power supply unit and power cable1)
ELE957 CABLE-RJ45-6M-1 Prefabricated system cable 12 x RJ45, 6 m
CABLE PATCH 8P 1M SHIELDED BLUE RJ45 patch cable, blue, screened, 1 m
CABLE PATCH 8P 2M SHIELDED BLUE RJ45 patch cable, blue, screened, 2 m
SEV957.EXP.RM-A150-1 Mitel 415 rack-mounting set
SEV957.EXP.RM-A300-1 Mitel 430 rack-mounting kit incl. fan
SEV957.EXP.CC-1 Cable cover set for Mitel 415/430
1) Available as of R2.1 SP1

Tab. 116 Overview of spare parts

Designation Description
SEV957 FAN-1 Mitel 430 fan
SEV957 PSU-60W-1 Power supply unit for basic system or EFOP fan-out-
panel
SEV957 MAINS CABLE-1 Two-pin standard power cable for basic system or EFOP
fan-out-panel power supply unit

7. 4 Technical data

7. 4. 1 Network interfaces
The following technical data applies to the network interfaces:

Basic rate interface BRI-T

• Standard Euro ISDN interface as per CTR-3

• Configurable for point-to-point or point-to-multipoint operation

246 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Annex

Analogue network interfaces

• Voice path with A/D and D/A conversion (standard PCM, A-law)
• Transmission as per ES 201 168 (level country-specific)
• Signalling as per TBR 21
• Pulse or DTMF dialling, Flash signal
• Loop current detection
• Call charge receive 12 or 16 kHz (frequency and level setting country-specific)
• CLIP detection in accordance with ETS 300 778-1

7. 4. 2 Terminal interfaces
The following technical data applies to the terminal interfaces:

Digital terminal interface DSI

• Proprietary interface, two-wire

• Two system phones of the MiVoice 5300 series can be connected per interface
(AD2 protocol)1)
• One SB-4+/SB-8 radio unit can be connected (with 8 channels the SB-8 radio units
requires two DSI interfaces)
• Power supply min. 75 mA, limiting at approx. 80 mA, terminal voltage 36…48 V
• Line termination in the phone
• Transparent transmission of 2 PCM channels

Digital terminal interface BRI-S

• Standard Euro ISDN interface

• Phantom power supply min. 140 mA, limiting at approx. 170 mA, terminal voltage
36…41 V
• Up to 8 terminals can be connected
• Maximum of 2 simultaneous call connections

Analogue terminal interface FXS

• Configurable multifunctional interface for connecting analogue terminals and equip-

ment.
• The following applies for the FXS mode Phone / Fax, two-wire door and general
bell:
1) Office 10, Office 25, Office 35, Office 45/45pro are supported as before

Mitel 415/430 as of R4.1 247

syd-0580/1.2 – R4.1 – 08.2016
Annex

– Voice path with A/D and D/A conversion (standard PCM, A-law)
– Transmission as per ES 201 168 (level country-specific)
– Constant-current loop supply approx. 25 mA (with loop resistance ≤ 1000 Ω)
– Receive pulse or DTMF dialling
– CLIP display on all analogue terminal interfaces (Mitel 415/430 only on 2 ana-
logue terminals simultaneously).
– Ringing supply 40…43 V 50 Hz at load 4kΩ; no DC voltage overlay (country-spe-
cific versions also with 25 Hz)
– No control key detection
– No charge signalling pulses
• For more technical details and cable requirements see "Multifunctional FXS inter-
faces", page 127.

7. 4. 3 Communication server
Tab. 117 Dimensions and weights
Mitel 415/430 for wall Mitel 415/430 in rack
mounting mounting
Height 65 mm 65 mm
Width 360 mm 483 mm
Depth 294mm 294mm
Weight (excl. mains cord, interfaces cards, modules and 2.4 kg 2.5 kg
packaging)

Tab. 118 Electrical isolation of interfaces

Interface Mitel 415/430
Analogue network interfaces 0.2 kV Operating isolation
Digital network interfaces BRI Operating isolation
Control input on ODAB no isolation, but input impedance > 8 kΩ
Freely connectable relay contacts on ODAB 0.2 kV
Door intercom interface on ODAB 0.2 kV
Control input on FXS interface no isolation
Control output on FXS interface no isolation
Audio input no isolation

Tab. 119 Ambient conditions

Condition Mitel 415/430
Ambient temperature 5 °C to 45 °C
Relative air humidity 30 % to 80 %, non-condensating

248 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Annex

Tab. 120 Electrical data

Mitel 415 Mitel 430
Class of protection 1
Input voltage 95 V…253 V, 48…62 Hz
Input current approx. 0.11 A...0.7 A approx. 0.11 A...1.0 A
Resistant to voltage breaks < 6ms
Power input with min. configuration approx. 15 W approx. 15 W
Power input with max. configuration approx. 50 W approx. 75 W
Undervoltage limit < 90 V
(system reset, data backup)

Tab. 121 Heat dissipation

Mitel 415 Mitel 430
Maximally configured system approx. 37 W = 135 kJ/h approx. 50 W = 180 kJ/h

7. 4. 4 Design of interface cards, modules and wiring adapt-

ers
Tab. 122 Design
Card/module Design
TIC-4TS B
TIC-2TS B
ESST C
TIC-4AB B
TIC-2AB B
TIC-1PRI C
EAAB2 B
EADP4 C
EAD4V A
EAD4C A
ETAB4 B
ODAB C
SM-DSP1 D
SM-DSP2 D
SM-DSPX1 D
SM-DSPX2 D
WA-TS0 F2
WA-TS1 F2
WA-2W F1
WA-1PRI F1

Mitel 415/430 as of R4.1 249

syd-0580/1.2 – R4.1 – 08.2016
Annex

"NN

#NN

$NN

NN

Fig. 88 Dimensions of interface cards (design A, B, C)

NN

NN

Fig. 89 Dimensions of system module (design D)

NN NN

' ' NN

Fig. 90 Wiring adapter dimensions (design F)

250 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Annex

7. 4. 5 LAN switch
%DVH7%DVH7;VZLWFK
)XOO\FRPSOLDQWZLWK,(((X
$XWR0',;$XWRSRODULW\$XWRQHJRWLDWLRQ
)ORZFRQWUROIXOO\VXSSRUWHGKDOIGXSOH[EDFNSUHVVXUHIORZFRQWUROIXOOGXSOH[,((([IORZFRQWURO
(PEHGGHG65$0IRUSDFNHWVWRUDJH
HQWU\ORRNXSWDEOHGLUHFWPDSSLQJPRGH
4R6S9/$1WDJ'LII6HUY726ILHOGLQ7&3,3KHDGHU,3EDVHGSULRULW\

Fig. 91 LAN switch on the mainboard

7. 4. 6 Digital and IP system phones

Tab. 123 Digital and IP system phones
MiVoice 5360 / 5360 IP, MiVoice 5361 / 5361 IP, MiVoice 5370 /
5370 IP, MiVoice 5380 / 5380 IP, Office 10, Office 25, Office 35,
Office 45/45pro
Ambient temperature in operation 0 °C to 40 °C
Relative humidity in operation 30 % to 80 %
Admissible storage temperature -25 °C to 45 °C
Power consumption, digital system phones see table "Average power requirements of terminals", page 79 and
table "Maximum power requirements of the system phones on the
DSI bus", page 116
Power consumption, IP system phones see System Manual for "Mitel Advanced Intelligent Network (AIN)
and IP system phones"

Tab. 124 Dimensions and weights, digital and IP system phones

Height (Type of Depth (Type of
Terminals Width Weight
mounting) mounting)
115 mm (desktop 25 °)
198 mm (desktop 25 °)
MiVoice 5360, MiVoice 5360 IP, 151 mm (desktop approx.
262 mm 166 mm (desktop 45 °)
MiVoice 5361, MiVoice 5361 IP 45 °) 850g
90 mm (wall)
199 mm (wall)
115 mm (desktop 25 °)
198 mm (desktop 25 °)
151 mm (desktop approx.
MiVoice 5370, MiVoice 5370 IP 262 mm 166 mm (desktop 45 °)
45 °) 875 g
90 mm (wall)
199 mm (wall)
115 mm (desktop 25 °)
198 mm (desktop 25 °)
151 mm (desktop approx.
MiVoice 5380, MiVoice 5380 IP 262 mm 166 mm (desktop 45 °)
45 °) 935 g
90 mm (wall)
199 mm (wall)
Expansion key module 115 mm (desktop 25 °) 95 mm 198 mm (desktop 25 °) approx.
MiVoice M530 151 mm (desktop 166 mm (desktop 45 °) 180 g
45 °) 90 mm (wall)
199 mm (wall)

Mitel 415/430 as of R4.1 251

syd-0580/1.2 – R4.1 – 08.2016
Annex

Height (Type of Depth (Type of

Terminals Width Weight
mounting) mounting)
Expansion key module 115 mm (desktop 25 °) 128 mm 198 mm (desktop 25 °) approx.
MiVoice M535 151 mm (desktop 166 mm (desktop 45 °) 325g
45 °) 90 mm (wall)
199 mm (wall)
Office 10 55 mm 82 mm 200 mm approx.
360 g
Office 25 56 mm 224 mm 203 mm approx.
500 g
Office 35 75 mm 254 mm 203 mm approx.
680 g
Office 45/45pro 97 mm 336 mm 203 mm approx.
960 g
Expansion key module EKP 44 mm 82 mm 133 mm approx.
115 g
Alpha keyboard AKB 21 mm 190 mm 82 mm approx.
150 g

7. 4. 7 Mitel DECT radio units

GAP functionality
The following table contains the network features as defined in the GAP standard. For
each feature a separate column indicates whether it is supported by communication
servers of the MiVoice Office 400 family or Mitel DECT cordless phones.

252 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Annex

Tab. 125 Features supported as per GAP standard

In Mitel DECT
In MiVoice
No. Feature PP cordless FP
Office 400
phones
1 Outgoing call M ✓ M ✓
2 Off hook M ✓ M ✓
3 On hook (full release) M ✓ M ✓
4 Dialled digits (basic) M ✓ M ✓
5 Register recall M ✓ O ✓
6 Go to DTMF signalling (defined tone length) M ✓ O ✓
7 Pause (dialling pause) M ✓ O —
8 Incoming call M ✓ M ✓
9 Authentication of PP M ✓ O ✓
10 Authentication of user M ✓ O —
11 Location registration M ✓ O ✓
12 On air key allocation M ✓ O ✓
13 Identification of PP M ✓ O —
14 Service class indication / assignment M ✓ O —
15 Alerting M ✓ M ✓
16 ZAP M ✓ O —
17 Encryption activation FP initiated M ✓ O —
18 Subscription registration procedure on-air M ✓ M ✓
19 Link control M ✓ M ✓
20 Terminate access rights FP initiated M ✓ O ✓
21 Partial release O ✓ O ✓
22 Go to DTMF (infinite tone length) O — O —
23 Go to Pulse O — O —
24 Signalling of display characters O ✓ O —
25 Display control characters O — O —
26 Authentication of FP O ✓ O ✓
27 Encryption activation PP initiated O — O —
28 Encryption deactivation FP initiated O — O —
29 Encryption deactivation PP initiated O — O —
30 Calling Line Identification Presentation (CLIP) O ✓ O ✓
31 Internal Call O ✓ O —
32 Service Call O — O —

PP: Portable Part

FP: Fixed Part
M: Mandatory (this feature must be supported by GAP compliant equipment)
O: optional
—: The Mitel DECT cordless phones and MiVoice Office 400 communication servers do not support the feature.

Mitel 415/430 as of R4.1 253

syd-0580/1.2 – R4.1 – 08.2016
Annex

Technical data
Tab. 126 Mitel DECT radio units
Duplex method Time-division multiplex, 10 ms frame length
Frequency range 1880 MHz to 1900 MHz
Frequency bands (carrier) 10
Channel spacing (carrier distance) 1,728 MHz
Transmission rate 1152 kbit/s
Duplex channels per carrier SB-4+ / SB-8 6 / 12
Number of channels (duplex channels) SB-4+ / SB-8 60 / 120
Modulation GFSK
Data transfer rate 32 kbit/s
Voice encoding ADPCM
Transmit power 250 mW peak value
10 mW, average power per channel
Range 30 to 250 m
Max. line length to radio unit
- power supply via DSI bus (0.5mm) 1200 m
- with power supply unit (9–15 VDC, 400 mA) 1200 m
Ambient temperature, radio unit in operation -10 °C to 55 °C
Admissible storage temperature -25 °C to 55 °C
Relative humidity in operation 30 % to 80 %
IP class of protection IP 30
Dimensions: Radio unit W x H x D: 165 x 170 x 70 mm
Weight: Radio unit 320 g
Local power supply to radio unit (optional) Plug-in power supply unit

254 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Annex

7. 5 Operation of digital system phones

7. 5. 1 Digit key assignment of system phones

Digit key assignment depends on the system phones series and the language set for
the communication server.
The following Latin script assignment for the digit keys applies to the system phones /
MiVoice 5360 / 5360 IP, MiVoice 5361 / 5361 IP, MiVoice 5370 / 5370 IP, Office 35,
Office 45/45pro, Office 135/135pro and all models of Office 160 for all communication
server languages with the exception of Greek:

Tab. 127 Latin-script digit key assignment

-.?1!,:;’"¿¡ ABC2ÄÆÅÇ
-.?1!,:;’"¿¡ abc2äæåàç

DEF3É GHI4
def3éèê ghi4ì

JKL5 MNO6ÑÖØ
jkl5 mno6ñöøò

PQRS7 TUV8Ü
pqrs7ß tuv8üù

WXYZ9 +0
wxyz9 +0

*/()<=>%£$¤¥¤@&§ Space #
*/()<=>%£$¤¥¤@&§ Space #

Notes:
– The MiVoice 5360 and Office 25 phones do not have a graphics-compatible display and
therefore cannot display all the characters featured (see also the corresponding user guide).
– On the Office 160 cordless system phone the space character is stored under digit 0 and the
special characters are stored under the #-key instead of the *-key.

Mitel 415/430 as of R4.1 255

syd-0580/1.2 – R4.1 – 08.2016
Annex

7. 5. 2 Alpha keyboardMiVoice 5380 / 5380 IP

The integrated alphanumerical keyboard on the MiVoice 5380 / 5380 IP is available in
a QWERTY and AZERTY version. The special characters can be called up using the
"Ctrl" key and the "Shift" key.

Tab. 128 Integrated alphanumerical keyboard MiVoice 5380 / 5380 IP

Key <Key> Shift + <key> Ctrl + <key> Ctrl + Shift + <key>
A a A äáàâãåæ ÄáàâÃÅÆ
B b B
C c C ç Ç
D d D
E e E éèêë ÉèêË
F f F
G g G
H h H
I i I ïíìî ïíìî
j j j
K k K
L l L
M m M
N n N ñ Ñ
O o O öóòôõø ÖóòôÕØ
P p P
Q q Q
R r R
S s S ß
T t T
U u U üúùû Üúùû
V v V
W w W
X x X
Y y Y ÿ
Z z Z
@ @ @
+ + + -.?!,:;."/\()=<>%
£$õ¥ª&§¿¡

256 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Annex

7. 5. 3 Function commands (macros)

Function commands are used mainly for automatically activating/ deactivating features
using the function keys of the system phones. The following function commands are
available:

Tab. 129 Function commands for system phones

Function command Meaning
"A" Seize line with maximum priority1)
"I" Seize line
"H" Seize line in hands-free mode2)
"X" Disconnect
"P" Pause 1 second before next action
"Lxx" Seize line xx (line keys)1)
"N" Enter call number keyed in during call preparation
"." Control keys function
"Z" Activate / deactivate DTMF mode (tone dialling)
"R" Use call number last dialled
"Y" End call and reseize line3)
1) Available only with the key telephones.
2) Available for Mitel 600 DECT only.
3) Not available for Office 10.

The function commands can be stored directly on the system phones via Self Service
Portal or on the function keys via WebAdmin.

Note:
As the Office 10 does not have a text mode, only 3 function commands can be stored on func-
tion keys on this phone. The 3 function commands are entered using the following keys:

Tab. 130 Function commands on function keys Office 10

Pause 1 second before next action

Control keys function

Activate / deactivate DTMF mode (tone dialling)

Mitel 415/430 as of R4.1 257

syd-0580/1.2 – R4.1 – 08.2016
Annex

7. 6 Functions and terminals no longer supported

The MiVoice Office 400 series continues to support the terminals and functions of the
Aastra IntelliGate series. Exceptions include the following terminals and functions:

• Digital system phones Office 20, Office 30, Office 40

• IP system phones Office 35IP, Office 70IP-b
• Cordless system phones Office 100, Office 130/130pro, Office 150, Office 150EEx,
Office 155pro/155ATEX
• The Aastra 6751i phone is no longer supported as an Mitel SIP phone.
• IP system softphone Office 1600/1600IP
• DECT radio unit SB-4
• Pocket Adapter V.24
• LAN switch SM-LAN8
• X.25 in the D channel
• Ascotel® Mobility Interface (AMI) and DCT terminals
• Universal Terminal Interface (UTI)
• AMS Hotel manager and Hospitality Mode V1.0 (hotel functions)
• Operator application Office 1560/1560IP
• Aastra Management Suite (AMS) is replaced by the web-based configuration tool
WebAdmin, the remote management SRM (Secure IP Remote Management) and
the application System Search.
• The external remote control (ERC) cannot be set up with WebAdmin. ERC is re-
placed by the possibility, to integrate mobile phones and other external phones into
the system (Mobile or External Phone Extension).
• Only language package downloading is available for Virtual Appliance in System
Search, Emergency Upload and the display of Virtual Appliance communication
servers is not available.
• Mitel BluStar 8000i is not supported by the Virtual Appliance communication server.
• The CPU2 application card is no longer supported (only CPU2-S).
• The Telephony Web Portal (TWP) application is replaced with Mitel MiCollab Audio,
Web and Video Conferencing.

258 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Annex

7. 7 Licensing information of third-party software products

7KH9RYLGD6RIWZDUH/LFHQVH9HUVLRQ
&RS\ULJKWF9RYLGD1HWZRUNV,QF$OOULJKWVUHVHUYHG
5HGLVWULEXWLRQDQGXVHLQVRXUFHDQGELQDU\IRUPVZLWKRUZLWKRXWPRGLILFDWLRQDUH
SHUPLWWHGSURYLGHGWKDWWKHIROORZLQJFRQGLWLRQVDUHPHW
5HGLVWULEXWLRQVRIVRXUFHFRGHPXVWUHWDLQWKHDERYHFRS\ULJKWQRWLFHWKLVOLVWRI
FRQGLWLRQVDQGWKHIROORZLQJGLVFODLPHU
5HGLVWULEXWLRQVLQELQDU\IRUPPXVWUHSURGXFHWKHDERYHFRS\ULJKWQRWLFHWKLVOLVW
RIFRQGLWLRQVDQGWKHIROORZLQJGLVFODLPHULQWKHGRFXPHQWDWLRQDQGRURWKHUPDWHUL
DOVSURYLGHGZLWKWKHGLVWULEXWLRQ
7KHQDPHV92&$/9RYLGD2SHQ&RPPXQLFDWLRQ$SSOLFDWLRQ/LEUDU\DQG
9RYLGD2SHQ&RPPXQLFDWLRQ$SSOLFDWLRQ/LEUDU\92&$/PXVWQRWEHXVHGWR
HQGRUVHRUSURPRWHSURGXFWVGHULYHGIURPWKLVVRIWZDUHZLWKRXWSULRUZULWWHQ
SHUPLVVLRQ)RUZULWWHQSHUPLVVLRQSOHDVHFRQWDFWYRFDO#YRYLGDRUJ
3URGXFWVGHULYHGIURPWKLVVRIWZDUHPD\QRWEHFDOOHG92&$/QRUPD\
92&$/DSSHDULQWKHLUQDPHZLWKRXWSULRUZULWWHQSHUPLVVLRQ
7+,662)7:$5(,63529,'('$6,6$1'$1<(;35(66('25,03/,('
:$55$17,(6,1&/8',1*%87127/,0,7('727+(,03/,(':$55$1
7,(62)0(5&+$17$%,/,7<),71(66)25$3$57,&8/$5385326(7,7/(
$1'121,1)5,1*(0(17$5(',6&/$,0(',112(9(176+$//929,'$
1(7:25.6,1&25,76&2175,%87256%(/,$%/()25$1<'$0$*(6,1
(;&(662)125)25$1<,1',5(&7,1&,'(17$/63(&,$/(;(0
3/$5<25&216(48(17,$/'$0$*(6,1&/8',1*%87127/,0,7('72
352&85(0(172)68%67,787(*22'6256(59,&(6/2662)86(
'$7$25352),7625%86,1(66,17(55837,21+2:(9(5&$86('
$1'21$1<7+(25<2)/,$%,/,7<:+(7+(5,1&2175$&7675,&7
/,$%,/,7<257257,1&/8',1*1(*/,*(1&(2527+(5:,6($5,6,1*,1
$1<:$<2872)7+(86(2)7+,662)7:$5((9(1,)$'9,6('2)7+(
3266,%,/,7<2)68&+'$0$*(

63,5,7*)D[LV&RS\ULJKWF

0RGHPDQG96RIWZDUHLV&RS\ULJKWF63,5,7

(FKR&DQFHOODWLRQ6RIWZDUHLV&RS\ULJKWF63,5,7

Mitel 415/430 as of R4.1 259

syd-0580/1.2 – R4.1 – 08.2016
Annex

<RUN7HFKQRORJLHV/LPLWHG
&RS\ULJKWDQG/LFHQVH,QIRUPDWLRQ

<RXDJUHHWKDWDOORZQHUVKLSDQGFRS\ULJKWRIOLFHQVHGLFRQVUHPDLQWKHSURSHUW\RI<RUN
7HFKQRORJLHV/LPLWHG<RXZLOOEHJUDQWHGDQRQH[FOXVLYHOLFHQVHWRGLVSOD\WKHJUDSKLFDO
PHGLDUR\DOW\IUHHLQDQ\SHUVRQDORUFRPPHUFLDOVRIWZDUHDSSOLFDWLRQVZHEGHVLJQSUHVHQ
WDWLRQVDQGPXOWLPHGLDSURMHFWVWKDW\RXFUHDWHDQGRUGLVWULEXWH<RXPD\PRGLI\WKHLFRQV
DQGGLVSOD\WKHUHVXOWLQJGHULYHGDUWZRUNVXEMHFWWRWKHWHUPVRIWKLVDJUHHPHQW:KHUHDQ
DSSOLFDWLRQLVWREHGLVWULEXWHGWKHJUDSKLFDOPHGLDPXVWEHFRPSLOHGLQWRWKHDSSOLFDWLRQ
ELQDU\ILOHRULWVDVVRFLDWHGGDWDILOHVGRFXPHQWDWLRQILOHVRUFRPSRQHQWV,I\RXDUHFUHDWLQJ
VRIWZDUHDSSOLFDWLRQVRUZHEVLWHVRQEHKDOIRIDFOLHQWWKH\PXVWHLWKHUSXUFKDVHDQDGGLWLRQDO
OLFHQVHIRUWKHLFRQVIURP<RUN7HFKQRORJLHV/LPLWHGRU\RXPD\VXUUHQGHUDQGIXOO\WUDQVIHU
\RXUOLFHQVHWR\RXUFOLHQWDQGQRWLI\XVWKDW\RXKDYHGRQHVR([FHSWZKHUHVWDWHGDERYH
\RXPD\QRWOLFHQVHVXEOLFHQVHJUDQWDQ\ULJKWVRURWKHUZLVHPDNHDYDLODEOHIRUXVHWKH
LFRQVHLWKHULQWKHLURULJLQDORUPRGLILHGVWDWHWRDQ\RWKHUSDUW\<RXPD\QRWLQFOXGHWKH
LFRQVLQDQ\IRUPRIHOHFWURQLFWHPSODWHWKDWDOORZVRWKHUSDUWLHVWRGLVWULEXWHPXOWLSOHFRSLHV
RIFXVWRPLVHGDSSOLFDWLRQV<RXPD\QRWLQFOXGHWKHLFRQVLQIRUPRIREVFHQHSRUQRJUDSKLF
GHIDPDWRU\LPPRUDORULOOHJDOPDWHULDO

727+((;7(173(50,77('%<$33/,&$%/(/$:,&216$1'27+(5*5$3+,&$/
0(',$$5(3529,'('$6,6:,7+287:$55$17<2)$1<.,1'(,7+(5(;35(66
25,03/,(',1&/8',1*%87127/,0,7('72$1<,03/,(':$55$17<2)0(5
&+$17$%,/,7<25),71(66)25$3$57,&8/$5385326(25121,1)5,1*(0(17
7+((17,5(5,6.$5,6,1*2872)86(253(5)250$1&(2)7+(,&216$1'
27+(5*5$3+,&$/0(',$5(0$,16:,7+<28

,112(9(17:,//<25.7(&+12/2*,(6/,0,7('%(/,$%/()25$1<'$0$*(6
,1&/8',1*/2662)'$7$/26723325781,7<25352),76&2672)&29(525
$1<63(&,$/,1&,'(17$/&216(48(17,$/',5(&725,1',5(&7'$0$*(6
$5,6,1*)520255(/$7,1*727+(86(2)7+(,&216$1'27+(5*5$3+,&$/
0(',$+2:(9(5&$86('21$1<7+(25<2)/,$%,/,7<7+,6/,0,7$7,21:,//
$33/<(9(1<25.7(&+12/2*,(6/,0,7('+$6%((1$'9,6('25*,9(1127,&(
2)7+(3266,%,/,7<2)68&+'$0$*(,1$1<&$6(<25.7(&+12/2*,(6
/,0,7('
6(17,5(/,$%,/,7<81'(5$1<3529,6,212)7+,6$*5((0(176+$//%(
/,0,7('727+(*5($7(52)7+(/,&(16(385&+$6()((3$,'%<<28)257+(
,&21625…127+,1*,17+(6(7(506$1'&21',7,2166+$//(;&/8'(25
/,0,7<25.7(&+12/2*,(6/,0,7('¶6/,$%,/,7<)25'($7+253(5621$/,1-85<
&$86('%<,761(*/,*(1&(25)5$8'25$1<27+(5/,$%,/,7<:+,&+&$1127
%((;&/8'('25/,0,7('81'(5$33/,&$%/(/$:

7KLV$JUHHPHQWVKDOOEHVXEMHFWWRDQGFRQVWUXHGDQGLQWHUSUHWHGLQDFFRUGDQFHZLWK(QJOLVK
/DZDQGVKDOOEHVXEMHFWWRWKHMXULVGLFWLRQRIWKH&RXUWVRI(QJODQG$Q\HQTXLULHVUHJDUGLQJ
WKLV$JUHHPHQWVKRXOGEHGLUHFWHGWR<RUN7HFKQRORJLHV/LPLWHG6W0DU\¶V&RWWDJH6W
%XU\DQ3HQ]DQFH8.75'-

$XJXVW

*O\SK/DELVDWUDGLQJQDPHRI<RUN7HFKQRORJLHV/LPLWHGUHJLVWHUHGLQ(QJODQGDQG:DOHV
1R5HJLVWHUHGRIILFH6W0DU\V&RWWDJH6W%XU\DQ3HQ]DQFH75'-8.
*O\SK/DELVDWUDGHPDUNRI<RUN7HFKQRORJLHV/LPLWHG

260 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Annex

7. 8 Documents and online help systems with further infor-

mation
Product Document
Products of the MiVoice Office 400 fam- System Manual Mitel 470
ily
System Manual Virtual Appliance
User Guide Getting Started with Mitel 470
System Manual System Functions and Features
SIP Access User’s Guide (English)
MiVoice Office 400 feature overview
Application Notes, technical information, FAQs and compatibility lists are
all available on the internet/extranet support page at:
https://pbxweb.aastra.com
Applications System Manual Mitel Alarm Server
Mitel Alarm Server User's Guide
Installation Instructions Mitel OpenCount for MiVoice Office 400
Configuration Guide Mitel OpenCount for MiVoice Office 400
Installation and Administration Guide "Mitel Standard Linux"
Solutions Guide "Virtual Appliance Deployment"
WebAdmin Online Help
Configuration assistant
Setup wizard
Self Service Portal (SSP) Online Help
Project planning application Mitel CPQ Online Help
DECT Planning DECT systems User’s Guide
Mitel SIP-DECT User’s Guide for Mitel 600 SIP-DECT on MiVoice Office 400
Basic/Enterprise voice mail system User's Guide for MiVoice Office 400 voice mail system
System Manual System Functions and Features
OIP System Manual Mitel Open Interfaces Platform
Online Help
User's Guide Mitel OfficeSuite
User's Guide for First Party TAPI Service Provider
Networking System Manual for Mitel Advanced Intelligent Network (AIN) and IP sys-
tem phones
Private networking system manual
Mitel SIP phones on MiVoice Office 400 Mitel 6730/31/53 SIP, Mitel 6735/37/55/57 SIP, Mitel 6739 SIP,
Mitel 6863/65 SIP, Mitel 6867/69 SIP user's guide
Mitel SIP phones (platform-independ- User's guide, short user's guide, installation instructions, administration
ent) instructions
IP system phones Quick User's Guide MiVoice 5360 IP / MiVoice 5361 IP / MiVoice 5370 IP
/MiVoice 5380 IP

Mitel 415/430 as of R4.1 261

syd-0580/1.2 – R4.1 – 08.2016
Annex

Product Document
Operating Instructions for MiVoice 5360 IP / MiVoice 5361 IP /
MiVoice 5370 IP / MiVoice 5380 IP / MiVoice 2380 IP
Digital system phones Quick User's Guide Office 10 / Office 25 / Office 35 / Office 45/45pro /
Office 135/135pro / Office 160pro/Safeguard/ATEX / MiVoice 5360 /
MiVoice 5361 / MiVoice 5370 / MiVoice 5380 / Mitel 610 DECT /
Mitel 612 DECT / Mitel 620 DECT / Mitel 622 DECT / Mitel 630 DECT /
Mitel 632 DECT / Mitel 650 DECT
User's Guide Office 10 / Office 25 / Office 35 / Office 45/45pro /
Office 135/135pro / Office 160pro/Safeguard/ATEX / MiVoice 5360 /
MiVoice 5361/ MiVoice 5370/ MiVoice 5380 / MiVoice 5380 /
Mitel 610 DECT / Mitel 612 DECT / Mitel 620 DECT / Mitel 622 DECT /
Mitel 630 DECT / Mitel 632 DECT / Mitel 650 DECT
Analogue phones Mitel 6710 Analogue / Mitel 6730 Analogue
user's guide
PC operator console User's Guide MiVoice 1560 PC Operator
Online Help

Most of the documents are accessible at http://www.mitel.com/docfinder. Many docu-

ments in the above table are summarised per language and software release in docu-
mentation sets, and can be downloaded as a .zip file. Note: Documentation sets are
very large (~500 MB). The download can take some time, depending on the connec-
tion.
More documents are available on the internet:

• Environmental information for communication server and system phones

• Declarations of conformity for communication server and system phones
• Labels for system phones and expansion key modules
• Safety instructions for system phones
• Application Notes
• Product information
• Leaflets
• Brochures
• Data sheets

262 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016
Index

A Error display 236

Error Mode 207
Aastra 5300ip series
Event messages 213
Integrated switch 147
Event table 230
Power supply 147
Exclusion of Liability 11
About this document 14
Access control 169 F
Access log 172
File browser 243
Access types 168
File system state 242
Application interfaces 31
Authorization profile 169 First start 178, 211
First-party CTI 35
Auxiliary applications 164
FTP distribution service 180
B H
Boot Mode 206
Hardware update 189
C Hazard alert messages 14
Carrying out functions 209 I
Change the DSP module 193
Installation (overview) 19
Charging bay 240
Configuration 162 Interfaces (overview) 38
Configuration data 184
Conformity 10
L
Connection possibilities (overview) 38 LED display 200
CTI - Computer Telephony Integration 35 LED on the radio unit 237
CTRL key 201 Licences 190
Limited Warranty (Australia only) 15
D Log data 172
Data backup 179 Longclicks on cordless phones 241
Data Maintenance 182
Data memory 182
M
Data protection 13 Maintenance 182
DECT 187 Media resources 42
DECT error 239 Message and alarm systems 34
Default user account 169 Message destinations 231
Dial-up connection to the AIN 210 MiContact Center Business 30
Display and control panel 200 Mitel 9
Display priorities 202 Mitel 400 Call Center 33
Distribution service 180 Mitel 400 CCS 29, 33
Downgrade 186 Mitel 400 Hospitality Manager 31
Mitel 600 DECT 26
E Mitel 6710a, Mitel 6730a 27
Mitel 6730 SIP 23
E-mail distribution service 180
Emergency Upload via LAN 212 Mitel 6750 SIP 23
Mitel 6800 SIP 22
Environment 11

Mitel 415/430 as of R4.1 263

syd-0580/1.2 – R4.1 – 08.2016
Mitel Alarm Server 30 RAM test 212
Mitel applications (overview) 29 Remote access 173
Mitel BluStar 8000i 24 Replacing system terminals 195
Mitel BluStar for PC 24 Replacing the EIM card 194
Mitel Border Gateway (MBG) 30 Replacing the interface card 191
Mitel Business CTI 30 Replacing the Mainboard 195
Mitel Dialer 29 Resetting the IP address 212
Mitel Hospitality Manager 164 Restart 178
Mitel MiCollab 29 Restart with database backup 209
Mitel Mobile Client (MMC) 25 Restart without database backup 210
Mitel Office Suite 25
Mitel Open Interfaces Platform (OIP) 29, 31 S
Mitel OpenCount 30 Safety Information 12
Mitel phones and clients (overview) 22 SB-4+ 239
Mitel Plan 30 SB-8 239
Mitel WAV Converter 167 SB-8ANT 239
MiVoice 1560 PC Operator 24 Secure IP Remote Management (SRM) 31
MiVoice 2380 Softphone 24 Self Service Portal 165
MiVoice 5300 Digital 26 Self Service Portal (SSP) 31
MiVoice 5300 IP 25 Software assurance 62
Modes of operation 202 Status display 236
Symbols 15
N System logs 242
Networking Possibilities 20 System overview 18
System Search 166
O
Operating state display 236 T
Operations supervision 213 Third-party CTI 36
Overload code display 242
Overview U
applications 29 Update Software 185
communication systems 18 User access control 169
Connection possibilities 38 User accounts 169
Installation version 19 User information 10
Mitel system phones and clients 22
Networking possibilities 20 W
Positioning 20 WebAdmin 30, 162
WebAdmin auxiliary applications 164
P WebAdmin configuration tool 162
Password syntax 171
Password-free access 172, 210
Pilot key 201
PoE 147
Positioning (overview) 20
Power over Ethernet 147
Product information 9

R
Radio unit 237

264 Mitel 415/430 as of R4.1

syd-0580/1.2 – R4.1 – 08.2016