Manual Mitel A415
Manual Mitel A415
MITEL 415/430
AS OF VERSION R6.0
SYSTEM MANUAL
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:
legal@mitel.com.
For a list of the worldwide Mitel Networks Corporation registered trademarks, please
refer to the website: http://www.mitel.com/trademarks.
Mitel 415/430
syd-0580/2.0 – 09.2018
®, ™ Trademark of Mitel Networks Corporation
© Copyright 2018 Mitel Networks Corporation
All rights reserved
2
Content
3 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
3. 2. 2 Power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
3. 2. 3 Media resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
3. 3 Expansion with cards and modules . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
3. 3. 1 System modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
3. 3. 1. 1 DSP modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
3. 3. 2 Interface cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
3. 3. 2. 1 Trunk cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
3. 3. 2. 2 Terminal cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
3. 3. 2. 3 Options card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
3. 3. 3 Wiring adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
3. 4 System capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
3. 4. 1 Media resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
3. 4. 2 General system capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
3. 4. 3 Terminals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
3. 4. 4 Terminal and network interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
3. 4. 5 Software assurance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
3. 4. 6 Licences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
3. 4. 6. 1 Description of available licences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
3. 4. 7 Restricted operating mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
3. 4. 8 Temporary offline licences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
3. 4. 9 Trial licences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
3. 4. 10 Power supply capacity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
3. 4. 10. 1 Supply power available for terminals. . . . . . . . . . . . . . . . . . . . . . . . . . 84
3. 4. 10. 2 Power supply per terminal interface . . . . . . . . . . . . . . . . . . . . . . . . . . 85
4 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
4. 1 System components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
4. 2 Fitting the communication server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
4. 2. 1 Equipment supplied . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
4. 2. 2 Mounting options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
4. 2. 2. 1 Cable cover set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
4. 2. 2. 2 Mitel 415 rack-mounting set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
4. 2. 2. 3 Mitel 430 rack-mounting set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
4. 2. 3 Location requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
4. 2. 4 Safety regulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
4. 2. 5 Wall mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
4. 2. 5. 1 Minimum distances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
4. 2. 5. 2 Drilling plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
4. 2. 5. 3 Drilling template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4. 2. 5. 4 Wall-mounting procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
4. 2. 6 Desktop installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
4. 2. 7 Rack-mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
4. 2. 7. 1 Rack-mounting procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
4. 2. 7. 2 Installing the fan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
4. 2. 7. 3 Installing the cable cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
4 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
4. 3 Earthing and protecting the communication server . . . . . . . . . . . . . . . 97
4. 3. 1 Connecting the earthing wire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
4. 3. 2 Connecting the cable screening . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
4. 4 Powering the communication server . . . . . . . . . . . . . . . . . . . . . . . . . . 99
4. 4. 1 115/230 V power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
4. 4. 2 Uninterruptible power supply (UPS) . . . . . . . . . . . . . . . . . . . . . . . . . 100
4. 5 Equipping the Basic System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
4. 5. 1 Fitting an interface card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
4. 5. 2 Fitting a wiring adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
4. 5. 3 Fitting DSP modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
4. 5. 4 Component mounting rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
4. 6 Connecting the communication server . . . . . . . . . . . . . . . . . . . . . . . 105
4. 6. 1 Direct connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
4. 6. 2 Indirect connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
4. 6. 2. 1 Connection via main distribution board . . . . . . . . . . . . . . . . . . . . . . . 106
4. 6. 2. 2 Connection to a universal building cable installation (UBC) . . . . . . . 108
4. 7 Cabling interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
4. 7. 1 Port addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
4. 7. 2 Network interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
4. 7. 2. 1 Basic rate interface BRI-T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
4. 7. 2. 2 Primary rate interface PRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
4. 7. 2. 3 FXO network interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
4. 7. 3 Terminal interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
4. 7. 3. 1 DSI terminal interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
4. 7. 3. 2 BRI-S terminal interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
4. 7. 3. 3 FXS terminal interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
4. 7. 4 Equipment on the ODAB options card. . . . . . . . . . . . . . . . . . . . . . . . 135
4. 7. 4. 1 Connection of a door intercom (TFE) . . . . . . . . . . . . . . . . . . . . . . . . 136
4. 7. 4. 2 Control outputs and control inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . 139
4. 7. 5 Audio interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
4. 7. 6 Ethernet interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
4. 8 Installing, powering, connecting and registering terminals . . . . . . . . 144
4. 8. 1 IP system phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
4. 8. 2 Mitel 6800/6900 SIP phone series. . . . . . . . . . . . . . . . . . . . . . . . . . . 146
4. 8. 3 Standard SIP phones and standard SIP terminals . . . . . . . . . . . . . . 146
4. 8. 4 Mobile/external phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
4. 8. 5 OIP and other applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
4. 8. 6 Digital system phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
4. 8. 6. 1 General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
4. 8. 6. 2 MiVoice 5361 / 5370 / 5380. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
4. 8. 7 DECT radio units and cordless phones . . . . . . . . . . . . . . . . . . . . . . . 150
4. 8. 7. 1 Installing the radio units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
4. 8. 8 Analogue phones Mitel 6710 Analogue, Mitel 6730 Analogue . . . . . 154
Mitel 415/430 5
syd-0580/2.0 – R6.0 – 09.2018
5 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
5. 1 WebAdmin Configuration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
5. 1. 1 Integrated and auxiliary applications . . . . . . . . . . . . . . . . . . . . . . . . . 160
5. 2 Access types with WebAdmin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
5. 3 User access control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
5. 3. 1 WebAdmin User accounts and authorization profiles . . . . . . . . . . . . 165
5. 3. 1. 1 User accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
5. 3. 1. 2 Authorization profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
5. 3. 1. 3 Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
5. 3. 2 Password-free access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
5. 3. 3 Automatic exit from the configuration . . . . . . . . . . . . . . . . . . . . . . . . 168
5. 3. 4 WebAdmin access log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
5. 4 WebAdmin remote access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
5. 4. 1 Access enabled by local users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
5. 4. 2 Function code for remote maintenance access. . . . . . . . . . . . . . . . . 169
5. 4. 3 Function keys for remote maintenance access . . . . . . . . . . . . . . . . . 170
5. 5 Configuring with WebAdmin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
5. 6 WebAdmin Configuration Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
5. 6. 1 Licences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
5. 6. 2 File management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
5. 6. 3 System reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
5. 6. 3. 1 Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
5. 6. 3. 2 First start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
5. 6. 4 Data backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
5. 6. 4. 1 Auto backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
5. 6. 4. 2 Distribution service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
5. 6. 4. 3 Manual backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
5. 6. 4. 4 Restore backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
5. 6. 5 Importing and exporting configuration data . . . . . . . . . . . . . . . . . . . . 176
5. 6. 6 Mitel 6800/6900 SIP phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
6 Operation and Maintenance . . . . . . . . . . . . . . . . . 178
6. 1 Data Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
6. 1. 1 What data is stored where. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
6. 1. 1. 1 System software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
6. 1. 1. 2 File system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
6. 1. 1. 3 Boot software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
6. 1. 1. 4 System-specific data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
6. 1. 2 Updating configuration data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
6. 2 Update Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
6. 2. 1 System software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
6. 2. 2 Firmware for corded system phones . . . . . . . . . . . . . . . . . . . . . . . . . 183
6. 2. 3 Firmware System MiVoice Office 400 DECT. . . . . . . . . . . . . . . . . . . 183
6. 2. 4 Firmware System Mitel SIP-DECT . . . . . . . . . . . . . . . . . . . . . . . . . . 184
6. 3 Hardware update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
6 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
6. 3. 1 Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
6. 3. 2 System information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
6. 3. 2. 1 Licences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
6. 3. 2. 2 EIM card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
6. 3. 3 Interface cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
6. 3. 3. 1 Replacing a defective interface card . . . . . . . . . . . . . . . . . . . . . . . . . 187
6. 3. 3. 2 New card with fewer ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
6. 3. 3. 3 New card with more ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
6. 3. 3. 4 Change slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
6. 3. 4 System modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
6. 3. 4. 1 Changing the DSP module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
6. 3. 5 System cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
6. 3. 5. 1 Replacing the EIM card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
6. 3. 6 Mainboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
6. 3. 7 Replacing system terminals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
6. 3. 7. 1 DSI system phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
6. 3. 7. 2 DECT terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
6. 4 Display and control panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
6. 4. 1 LED display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
6. 4. 2 Pilot key (CTRL key) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
6. 4. 3 Operating modes and display priorities . . . . . . . . . . . . . . . . . . . . . . . 198
6. 4. 3. 1 Startup Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
6. 4. 3. 2 Normal Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
6. 4. 3. 3 Feature Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
6. 4. 3. 4 Application Command Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
6. 4. 3. 5 Boot Command Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
6. 4. 3. 6 Wiring Adapter Malfunction Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
6. 4. 3. 7 Warning Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
6. 4. 3. 8 Boot Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
6. 4. 3. 9 Shut-down Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
6. 4. 3. 10 Error Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
6. 4. 4 Carrying out functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
6. 4. 4. 1 Shutting down the communication server . . . . . . . . . . . . . . . . . . . . . 204
6. 4. 4. 2 Normal restart with database backup . . . . . . . . . . . . . . . . . . . . . . . . 205
6. 4. 4. 3 Forced restart without database backup . . . . . . . . . . . . . . . . . . . . . . 205
6. 4. 4. 4 Enabling / disabling password-free access . . . . . . . . . . . . . . . . . . . . 205
6. 4. 4. 5 Enabling / disabling the dial-up connection to the AIN . . . . . . . . . . . 206
6. 4. 4. 6 Carrying out a first start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
6. 4. 4. 7 Resetting the IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
6. 4. 4. 8 Thorough RAM test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
6. 4. 4. 9 Emergency Upload via LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
6. 5 Operations supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
6. 5. 1 Event message concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
6. 5. 1. 1 Event types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
6. 5. 1. 2 Event tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Mitel 415/430 7
syd-0580/2.0 – R6.0 – 09.2018
6. 5. 1. 3 Signal destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
6. 5. 2 Operating state and error displays . . . . . . . . . . . . . . . . . . . . . . . . . . 234
6. 5. 2. 1 System operating state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
6. 5. 2. 2 System error displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
6. 5. 2. 3 Terminals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
6. 5. 2. 4 Operating state of the Mitel DECT radio units . . . . . . . . . . . . . . . . . . 235
6. 5. 2. 5 Malfunction of the Mitel DECT radio unit . . . . . . . . . . . . . . . . . . . . . . 237
6. 5. 2. 6 Malfunctions of Mitel DECT cordless phones . . . . . . . . . . . . . . . . . . 237
6. 5. 2. 7 Malfunctions of the DECT charging bays . . . . . . . . . . . . . . . . . . . . . 238
6. 5. 2. 8 Longclicks on Mitel DECT cordless phones . . . . . . . . . . . . . . . . . . . 239
6. 5. 2. 9 Overload code displays Office 135 / Office 160 . . . . . . . . . . . . . . . . 240
6. 5. 3 Other aids . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
6. 5. 3. 1 System logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
6. 5. 3. 2 File system state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
6. 5. 3. 3 File browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
6. 5. 3. 4 Measuring equipment for cordless systems . . . . . . . . . . . . . . . . . . . 241
7 Annex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
7. 1 Systematic designation system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
7. 2 Rating Plate and Designation Stickers . . . . . . . . . . . . . . . . . . . . . . . 243
7. 3 Equipment Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
7. 4 Technical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
7. 4. 1 Network interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
7. 4. 2 Terminal interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
7. 4. 3 Communication server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
7. 4. 4 Design of interface cards, modules and wiring adapters. . . . . . . . . . 247
7. 4. 5 LAN switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
7. 4. 6 Digital and IP system phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
7. 4. 7 Mitel DECT radio units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
7. 5 Operation of digital system phones . . . . . . . . . . . . . . . . . . . . . . . . . . 252
7. 5. 1 Digit key assignment of system phones . . . . . . . . . . . . . . . . . . . . . . 252
7. 5. 2 Alpha keyboardMiVoice 5380 / 5380 IP . . . . . . . . . . . . . . . . . . . . . . 253
7. 5. 3 Function commands (macros) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
7. 6 Functions and terminals no longer supported . . . . . . . . . . . . . . . . . . 256
7. 7 Licensing information of third-party software products . . . . . . . . . . . 257
7. 8 Documents and online help systems with further information . . . . . . 259
8 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
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.
User groups
The design of the phones, softphones and PC applications of the MiVoice Office 400
communication solution is particularly user-friendly, which means they can be operated
by all end users without specific product training.
The phones and PC applications for professional applications, such as the operator
console or call centre applications require training of the personnel.
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 the necessary safety/legal information
and user documents. All user documents such as user guides and system manuals are
available for download from the MiVoice Office 400 document portal as individual doc-
uments or as documentation sets. Some user documents are accessible only via a
partner login.
Mitel 415/430 9
syd-0580/2.0 – R6.0 – 09.2018
Product and Safety Information
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 a MiVoice Office 400 communication system and to operate it efficiently
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 a MiVoice
Office 400 communication system into operation.
• Ensure that all end users have access to the user guides.
1. 2 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.
DANGER!
Danger indicates an imminently hazardous situation which, if not avoided, will result in death or serious
injury.
WARNING!
Warning indicates a potentially hazardous situation which, if not avoided, could result in death or serious
injury.
CAUTION!
Caution indicates a potentially hazardous situation which, if not avoided, may result in minor or moderate
injury and/or damage to the equipment or property.
10 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
Product and Safety Information
The lightning flash with arrowhead symbol, within an equilateral triangle, is intended to alert the user to the
presence of uninsulated dangerous voltage within the product’s enclosure that may be of sufficient magni-
tude to constitute a risk of electric shock.
The exclamation point within an equilateral triangle is intended to alert the user to the presence of important
operating and maintenance (servicing) instructions in the literature accompanying the product
Indicates ESD components. Failure to observe information identified in this way can lead to damage caused
by electrostatic discharge.
The ground symbol within a circle identifies the product to be connected to an external conductor. Connect
this product to earth ground before you make any other connections to the equipment.
Operating safety
MiVoice Office 400 communication servers are operated on 115/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 source. 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.
• 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
defective.
• Check that you have all the relevant user documents at your disposal.
• Configure this product with only the assemblies specified and in the locations stated
in the user documentation.
• During the installation follow the installation instructions for your MiVoice Office 400
product in the sequence that is given and observe to the safety warnings they con-
tain.
Mitel 415/430 11
syd-0580/2.0 – R6.0 – 09.2018
Product and Safety Information
CAUTION!
Failure to follow all instructions may result in improper equipment operation and/or risk of electrical shock.
• Install all wiring according to local, state, and federal electrical code requirements.
• Do not connect telecommunications cabling to the system, service the system, or
operate the system with the grounding conductor disconnected.
• Ensure the AC receptacle is installed near the equipment and easily accessible.
• Use only Mitel approved power adapters.
Any servicing, expansion or repair work is to be carried out only by trained technical
personnel with the appropriate qualifications.
1. 3 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.
12 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
Product and Safety Information
Note
In this document, it is presumed, that the Mitel SMB Controller is loaded with a MiVoice
Office 400 application software. This assumption is always valid, even the expression
Mitel SMB Controller, SMBC or communication server is used.
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: 2.0
• Valid as of / based on: R6.0 / R6.0
• © 09.2018 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
General Considerations
Special symbols for additional information and document references.
Mitel 415/430 13
syd-0580/2.0 – R6.0 – 09.2018
Product and Safety Information
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.
14 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
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. If you are setting up an
communication system for the first time, it may be useful to set up a test system
step by step on site. At the end of the chapter you find a useful getting started guide
for this purpose.
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.
Mitel 415/430 15
syd-0580/2.0 – R6.0 – 09.2018
System Overview
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
16 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
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 users with SIP/IP phones and TDM extensions (FXS, DSI, BRI-S).
Fig. 3 Max. expansion capacity for users with SIP/IP phones and TDM extensions (FXS, DSI, BRI-S)
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 415/430 17
syd-0580/2.0 – R6.0 – 09.2018
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.
18 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
System Overview
Mitel 415/430 19
syd-0580/2.0 – R6.0 – 09.2018
System Overview
20 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
System Overview
Mitel 415/430 21
syd-0580/2.0 – R6.0 – 09.2018
System Overview
22 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
System Overview
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
Mitel 415/430 23
syd-0580/2.0 – R6.0 – 09.2018
System Overview
• 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
24 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
System Overview
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 Mitel 6940 SIP, Mitel 6873 SIP, MiVoice 5380 / 5380 IP
reception phone or the web-based Mitel 400 Hospitality Manager application. Re-
duced hospitality functionality are also available on Mitel 6920 SIP, Mitel 6930 SIP,
Mitel 6867 SIP and Mitel 6869 SIP phones. Connection to a Property Management
System (PMS) via the communication server's Ethernet interface is also possible.
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.
Mitel 415/430 25
syd-0580/2.0 – R6.0 – 09.2018
System Overview
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
communication server via standardised interfaces (see "Application interfaces",
page 28).
Auxiliary applications for planning and the configuration and park management are
available as a web application.
2. 7. 1 Mitel Applications
Tab. 9 Mitel applications
Application Main features
• Simple first party CTI application
• Dial, answer, hang up
• Integration in Outlook, Lync 2013 and Office 365
• Search in directories
Mitel Dialer
• Compatibility with MiVoice 5300, MiVoice 5300 IP, Mitel 6800/6900 SIP,
Mitel 600 DECT series phones
• Installation via SSP or WebAdmin
• Click to call support (e.g. for Hospitality Manager)
• Application interface for deep integration of applications by Mitel or other
manufacturers (see "Application interfaces", page 28)
• 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
26 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
System Overview
Mitel 415/430 27
syd-0580/2.0 – R6.0 – 09.2018
System Overview
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.
28 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
System Overview
OIP connectors
Automation and
Communication systems External directories
alarming systems
Fig. 4 OIP as middleware between communications system, external data sources and applications
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 415/430 29
syd-0580/2.0 – R6.0 – 09.2018
System Overview
30 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
System Overview
With the graphical interface (tree structure) events and the relevant actions are easily
linked with one another.
See also:
More information can be found in the Mitel Open Interfaces Platform system manual and in the
OIP WebAdminOnline help.
Mitel 415/430 31
syd-0580/2.0 – R6.0 – 09.2018
System Overview
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.
• 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-
32 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
System Overview
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 some applications (e.g. Office eDial) the First-Party TAPI Service Provider
(AIF-TSP) is required. Other applications (e.g. Mitel Dialer) use the CSTA protocol.
Application example
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.1) 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).
1) for USA and Canada on Mitel 470 other protocols are supported.
Mitel 415/430 33
syd-0580/2.0 – R6.0 – 09.2018
System Overview
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.
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 done through WebAdmin. The Mitel 6940 SIP, Mitel 6873 SIP,
MiVoice 5380 / 5380 IP reception phone or the web-based Mitel 400 Hospitality Man-
ager application is available to operate the functions. Reduced hospitality functionality
are also available on Mitel 6920 SIP, Mitel 6930 SIP, Mitel 6867 SIP and
Mitel 6869 SIP phones. A connection to a Property Management System (PMS) via the
communication server's Ethernet interface is also possible. The commercially available
FIAS protocol 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.
34 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
System Overview
2. 8 Connection options
Digital terminals
WE 23
Aug 16:58
Week
Office 34
Menu 80IP
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
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
OMM RFP
network PISN (QSIG /
BRI-Sextern
Private telephony
SIP-DECT with
Mitel 415/430
Ethernet OpenMobilityManager
BRI-T
PSS1)
Ethernet
FXS Door intercoms with DTMF
control functions
FXS
Control outputs
VGA
Door intercom system CTI /call centre workstations
Door opener
Controller
Fixed Mobile Convergence
USB
Bell input Ethernet Mitel Mobile Client
Mitel 415/430 35
syd-0580/2.0 – R6.0 – 09.2018
System Overview
2. 9 Getting started
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.
After working through the following chapters you can make internal calls between the
different types of phones connected to the server. Furthermore you will have a perfect
configuration platform to learn more about the system, its features and expansion pos-
sibilities.
2. 9. 1 General requirements
You need a Windows OS computer with internet access, the System Search applica-
tion and access to Mitel Connect.
If you plan to address the communication server with a static IP address (recom-
mended) you may obtain it from your IT administrator.
In order to allocate your IP and SIP phones to the communication server, DHCP ser-
vice should be available in your subnet. (Your communication server has an integrated
DHCP server as well, however it is switched off as per default.)
If you plan to set up a SIP trunk, you need a SIP account by a SIP provider of your
choice.
Required accesses
The URL’s listed below refer to proprietary Mitel sites. You need a partner login to ac-
cess them. If you do not have a Mitel partner login, ask your sales partner for more in-
formation.
Required tools
36 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
System Overview
Mitel CPQ is designed to support you with the different activities in the sales and order-
ing process. It is a web-based application for online usage. You can access the appli-
cation through the Mitel Connect Portal [2].
Save the component list either as Microsoft Excel or Word file and place an order with
your Mitel reseller.
1. Download the Documentation set from the Mitel document portal [1], double-click
the file and follow the installation wizard steps.
2. Choose My Documents or another suitable target directory and install the Documen-
tation set. A folder named Mitel is created automatically.
3. Download the latest system software from [2] into the same folder and double click
the file. The software (zip) and the release notes (pdf) will also be extracted to the
folder named Mitel.
4. Download the latest System Search application from [2] into the folder named Mitel.
The application needs no installation and can be executed by a double click.
CAUTION!
• Before you begin, read the product information and safety instructions carefully (see the PDF included in
the Documentation set or the printed sheet included in the delivery package).
• To prevent ESD damage to the components, always touch the earthed metal case of the communication
server before carrying out work inside the housing. This also applies to handling interface cards, proces-
sor cards, and system modules that are not packed inside the ESD protective wrapping.
Mitel 415/430 37
syd-0580/2.0 – R6.0 – 09.2018
System Overview
1. Connect your computer to the IP network ensuring that your computer is in the
same subnet as the communication server.
2. Double-click System Search to start the application.
3. In System Search, click Search.
All communication servers in the same subnet are listed.
Tip
If your communication server is not listed, your computer is in another subnet. If it is not pos-
sible to connect the IP network in the same subnet, connect your computer to the communi-
cation server either directly or through a switch. Click Search again.
38 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
System Overview
1. In System Search, select your communication server from the list and click the IP
settings tab.
2. Set DHCP to Off, enter the static IP address of the communication server and the
corresponding Subnet mask. Click Save.
The password window opens.
Note
Although you can use DHCP, we recommend that you address the communication server
using a static IP address.
3. Enter the default user name and password (admin / password) of the communica-
tion server and click OK.
A message appears that the IP address has been successfully changed.
Note
You must select the correct Sales channel as it is mapped to the licence code.
4. Click Next.
The Software update view is displayed. We recommend that you update the com-
munication server to the latest software release.
5. Choose the Manual software upload entry and upload the system software that you
have already saved to your hard disc (see chapter "Download documents, system
software and tools", page 37”). During the software update (or if you chose not to
update the software, after you click Next in step 6) a first start is executed to set the
sales channel and the country specific settings.
6. Click Next.
The Upload audio guides view is displayed. The communications server uses spo-
ken text for several purposes like voice mail, presence information or auto atten-
dant. These texts are stored in audio files. You can download audio guide lan-
guages through the menu Localize in System Search and then upload them to the
communication server in this view.
Mitel 415/430 39
syd-0580/2.0 – R6.0 – 09.2018
System Overview
Note
If your communication server has Internet access, you can choose to skip this step, because
you can download the audio guide languages later from a Mitel FTP server through the
Localization ( =e6) view in WebAdmin.
7. Click Next.
The First access view displays, prompting you to change the default password of
the administrator account, to choose the System language, and to enter a Site
name.
8. Click Next.
The first page of the WebAdmin Setup wizard opens.
Tip
If you need help while going through the steps of the wizard, click Help in the upper right of the
Setup wizard.
A new help window appears. You can leave the help window open, while going through the
steps.
1. On the first page of the Setup wizard, you register or activate the communication
server by uploading a valid Licence file.
– Copy the Equipment ID (EID) to the clipboard.
– In a new browser window, log in to the Mitel Connect portal [2] and open the Li-
cences & Services section.
– Option 1: If you have a voucher, enter the voucher number in the Voucher edit
field, click Register Voucher and follow the instructions. You need to enter the
Equipment ID (EID) during the procedure. On completing the procedure, you will
obtain a Licence file.
– Option 2: If you have no voucher, enter the Equipment ID (EID) in the Activate
product edit field, click Activate product and follow the instructions. On complet-
ing the procedure, you will obtain a Licence file.
– Upload the Licence file in the WebAdmin Setup wizard.
Your communication system is now registered and activated.
The new licences are enabled. You can see them on the licence overview page.
Note
If you do not activate the communication server, it will switch to a restricted operating mode
after four hours.
2. Click Apply and Next.
The second page, Setting up the IP addressing, opens.
Set the Gateway address and a Primary DNS server.
40 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
System Overview
Note
If you do not set these parameters, you cannot load audio guides or update Mitel SIP phone
strings from the Mitel download server.
3. Click Apply and Next.
The third page, Configuring media resources, opens.
On this page, the system proposes to configure the DSP resources automatically.
You can use this configuration to begin with. You can always change the DSP set-
tings under Configuration - System - Media resources ( =ym). Check the options
for FoIP and DECT resources, if applicable.
4. Click Apply and Next.
The fourth page, Setting up the numbering plan, opens.
This page displays the predefined call numbers of the internal numbering plan. You
can edit or delete these numbers.
5. Click Apply and Next.
The fifth page, Setting up SIP providers, opens.
This page allows you to set up a SIP provider profile or import a predefined SIP pro-
vider profile from an XML file. If your communication system will not be connected to
the public network through a SIP provider, skip this step.
6. Click Apply and Next.
The sixth page, Setting up users, terminals and DDIs(DIDs), opens.
On this page, you set up users, terminals and DDIs(DIDs).
7. Click Apply and Next.
The seventh page, Setting up the auto attendant, opens.
This page allows you to set up an auto attendant, if needed. The auto attendant en-
ables you to specify, what options are offered to a caller while greeting the caller.
The caller can select any of the options by dialing a single digit.
8. Click Apply and Next.
This completes the setup. Click Restart for the configurations to take effect.
As you allocated phones to users in step 6 of the Setup wizard, the data instances for
the phones have been automatically created. In this part of the procedure, for regis-
tering the phones, you pair the data instances with the physical phones.
Note
Mitel SIP phones get their time and date from an NTP server. To ensure this, enable the NTP
service in System / General ( =ty) and enter the IP address of the NTP server.
Mitel 415/430 41
syd-0580/2.0 – R6.0 – 09.2018
System Overview
1. Go to Terminals / Standard terminals ( =qd) in WebAdmin and click the phone you
want to register with the communication server.
The automatically generated SIP credentials and registration credentials (Registra-
tion user name and Registration password) of the phone are displayed. You will
need to provide the registration credentials later to register the phone.
2. Add one or more expansion key modules to the phone, if available.
3. Connect the phone to the IP network and to the power supply by using the optional
power adapter. If your IP network supports PoE, no power adapter is required.
4. Restart the phone.
The phone searches for the communication server. If more than one communication
server is available, the phone lists them in the format <XXX–MAC address>.
Tip
You will find the MAC address of your communication server in IP network / IP addressing
( =9g) of WebAdmin.
5. Choose your communication server from the list, and when prompted, enter the
Registration user name and the Registration password.
The phone registers with the communication server. If a new phone software is
available, the phone automatically updates and restarts.
42 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
System Overview
2. Connect the phones to the DSI interfaces on the front panel. Connect the phones in
the same order as you have set them up in the previous chapter and start with the
lowest port number.
3. The phones are registered and allocated to their phone data instance in the commu-
nication server. If you keep the suggested order, the phone type matches with the
configured terminal type. You can fix a terminal mismatch in the WebAdmin terminal
view.
Mitel 415/430 43
syd-0580/2.0 – R6.0 – 09.2018
Expansion Stages and System Capacity
The basic system 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 86.
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
44 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
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
Tab. 12 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:
The diagram below shows the position of all the interfaces and slots on the mainboard
display and control elements and on the front panel.
Mitel 415/430 45
syd-0580/2.0 – R6.0 – 09.2018
Expansion Stages and System Capacity
Mainboard EIM
Cardholder for
EIM card
SM1
Connector
for fan
FAN
SM2 (Mitel430)
(Mitel430)
Internal interfaces
Ethernet FXS DSI
LED display
(Mitel430)
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
46 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
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 communication server is powered with 19V DC from the power sup-
ply. All other voltages are generated directly on the mainboard. To ensure that its oper-
ation is maintained even in the event of a mains outage, an external uninterruptible
power supply (UPS) must be used. For more details about the power supply see "Pow-
ering the communication server", page 99.
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. 14). Another part is allocated to selectable functions, according to re-
quirements. These functions are partly subject to licence (see Tab. 15).
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. 21 and Tab. 22).
Mitel 415/430 47
syd-0580/2.0 – R6.0 – 09.2018
Expansion Stages and System Capacity
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.
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. 14).
– 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.
48 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
Expansion Stages and System Capacity
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.
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.
Mitel 415/430 49
syd-0580/2.0 – R6.0 – 09.2018
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 67).
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 51 for an overview).
The number of configurable VoIP channels depends on both the type of DSP chip
(see "Configuration of DSP chips", page 54) and the configured mode (see "Stand-
ard Media Switch modes of operation", page 53).
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
50 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
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 53). 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 54) and the type of DSP chip
(see "Configuration of DSP chips", page 54).
• 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-E1 network in-
terfaces used in certain countries (e.g. Brazil). This setting provides the tone sender
and receiver for transmitting signalling information.
Mitel 415/430 51
syd-0580/2.0 – R6.0 – 09.2018
Expansion Stages and System Capacity
Master
1 VoIP channel
Non-IP endpoint IP endpoint
Satellite
Non-IP endpoint
No VoIP channel
Non-IP endpoint
52 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
Expansion Stages and System Capacity
Mitel 415/430 53
syd-0580/2.0 – R6.0 – 09.2018
Expansion Stages and System Capacity
No audio channels are reserved after a first start and they can be used for voice mail,
auto attendant, call recording or announcement.
54 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
Expansion Stages and System Capacity
the following table. All the possible combinations are listed, with the maximum number
of channels.
Mitel 415/430 55
syd-0580/2.0 – R6.0 – 09.2018
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. 14).
– 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 59).
The length varies depending on the type of interface card. For precise dimensions see
the Chapter "Technical data", page 244.
56 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
Expansion Stages and System Capacity
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 "Fitting a wiring adapter",
page 102).
Note
On the ESST terminal card the jumper must always be fitted in position T (see Fig. 24).
Mitel 415/430 57
syd-0580/2.0 – R6.0 – 09.2018
Expansion Stages and System Capacity
3. 3. 2. 2 Terminal cards
Terminal cards are used for connecting digital and analogue voice and data terminals.
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 131).
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 "Fitting a wiring adapter", page 102).
Note
On the ESST terminal card the jumper must always be fitted in position T (see Fig. 24).
58 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
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).
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).
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.
Mitel 415/430 59
syd-0580/2.0 – R6.0 – 09.2018
Expansion Stages and System Capacity
There are different types of wiring adapters, of which two (WA-TS0 and WA-TS1) have
different plug-in orientations. This determines the ratio of BRI-S interfaces to BRI-T in-
terfaces.
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).
The assignment to the RJ45 sockets depending on the wiring adapters is shown in
Tab. 35.
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.
60 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
Expansion Stages and System Capacity
3. 4. 1 Media resources
Mitel 415/430 61
syd-0580/2.0 – R6.0 – 09.2018
Expansion Stages and System Capacity
AIN with
Max. number... Mitel 415 Mitel 430 Mitel 430 as
Master
SmartDDI conversion rules overall 200 200 200
Call distribution elements 500 500 500
Queue with announcement 8 8 8
User groups 21 21 21
Members per user group "normal" 811)/16 811)/16 811)/16
Members per user group "large" 20 100 100
Abbreviated dialling numbers + PISN users 1500 1500 1500
Operator keys per phone on Mitel 6800/6900 SIP 1012) 1012) 1012)
Room keys on Mitel 6873 SIP (inclusive expansion keypad) 10 50 50
Line keys per key telephone (except Mitel 6800/6900 SIP) 39 39 39
Line keys per key telephone on Mitel 6800/6900 SIP 2...1213) 2...1213) 2...1213)
Line keys per CDE on Mitel 6800/6900 SIP 814) 814) 814)
Total line keys on Mitel 6800/6900 SIP see 15) see 15) see 15)
Switch groups 50 50 50
Positions per switch group 3 3 3
Hotline destinations 20 20 20
Emergency destinations 50 50 50
Internal emergency numbers 10 10 10
Internal emergency response teams 5 5 5
Members of internal emergency response teams 20 20 20
Public emergency numbers 20 20 20
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
62 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
Expansion Stages and System Capacity
AIN with
Max. number... Mitel 415 Mitel 430 Mitel 430 as
Master
Profiles per mailbox for auto attendant 3 3 3
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)16) 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 on Mitel 6800/6900 SIP phones 304) 60 100
Alpha keyboard Mitel 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,
2 DECT-cordless phones and 1 MiCollab client (3 MiCollab clients with MiCollab version 8.1) 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 in the DSP settings:
Mitel 415: Secure G.711: 1 × 7 = 7 channels, Secure G.711/G.729: 1 × 5 = 5 channels.
Mitel 430: Secure G.711: 2 × 7 = 14 channels, Secure G.711/G.729: 3 × 5 = 15 channels.
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)In USA/Canada the abbreviation DID (Direct Inward Dial) is used instead of DDI (Direct Dialling In)
11)With global call distribution
12)Only 6 on Mitel 6940 SIP/Mitel 6873 SIP if phone is also used as reception phone.
13)Depending on the phone type: Aastra 6730i/31i: 6 keys; Mitel 6735/37/39/53/55/57 SIP: 9 keys;
Mitel 6863 SIP: 2 keys; Mitel 6865/67 SIP: 9 keys; Mitel 6869/73 SIP: 12 keys; Mitel 6900 SIP: 12 keys
14)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.
Mitel 415/430 63
syd-0580/2.0 – R6.0 – 09.2018
Expansion Stages and System Capacity
15)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).
Example: The following line keys are configured on different Mitel SIP phones: 4 keys for line 1, 7 keys for
line 2, 5 keys for line 3, 5 keys for line 4.
→ Highest number of keys per line: 7
→ Total 24 line keys are allowed
→ Configured line keys: 4 + 7 + 5 + 5 = 21 → OK
16)The call data memory is only used if the output destination is blocked (e.g. printer jam).
3. 4. 3 Terminals
Tab. 28 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)
Miscella- Free seating pools 20 100 100
neous
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
DSI Operator consoles / operator applica- MiVoice 5380 4 8 16 2
tions MiVoice 1560
DSI Cordless system SB-4+ radio unit 10 20 32 1
DSI Cordless system SB-8 / SB-8ANT radio 5 10 32 2)
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
64 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
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 Mitel 6930 SIP 1 1 1
applications Mitel 6940 SIP
Mitel 6869 SIP
Mitel 6873 SIP
MiVoice 5380 IP 4 8 16
MiVoice 1560
LAN Reception/Front desk Mitel 6940 SIP 1 1 1
Mitel 6873 SIP
LAN Mitel SIP terminals Mitel 6920 SIP 10 50 50
Mitel 6930 SIP
Mitel 6940 SIP
Mitel 6863 SIP
Mitel 6865 SIP
Mitel 6867 SIP
Mitel 6869 SIP
Mitel 6873 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 BRI-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
Mitel 415/430 65
syd-0580/2.0 – R6.0 – 09.2018
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.
66 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
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 requiring
SWA 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.
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
file.
The licence file contains all the enabled licences. When you purchase a new licence
from your authorised dealer, you obtain a new licence file in return. Upload this file in
WebAdmin in the Licences ( =q9) view.
Notes:
– A licence file is not transferable to another communication server.
– If you receive a voucher instead of a licence file, log on with your partner login at
Mitel Connect https://connect.mitel.comand generate the licence file yourself using the EID
number. Detailed instructions about this can be found in the WebAdmin help on the
Licences ( =q9) view.
• Software Release
Updating to a new software release requires a licence. A valid software assurance
Mitel 415/430 67
syd-0580/2.0 – R6.0 – 09.2018
Expansion Stages and System Capacity
(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 76). The communication
server will switch back to normal operation as soon as you upload a licence file 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 file using the EID number and the voucher. The licence file 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 file.
Detailed instructions about this can be found in the WebAdmin help on the Licences
( =q9) view.
Users
68 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
Expansion Stages and System Capacity
Terminals
Mitel 415/430 69
syd-0580/2.0 – R6.0 – 09.2018
Expansion Stages and System Capacity
need to also purchase a Mitel 8000i Video Options licence. The two licences are
needed to register the terminals on the system. Use is not possible if Video Termi-
nals licences are missing.
• 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.
• 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 6800/6900 SIP series can automatically register on a backup communication
server. On the backup communication server one licence is required per phone.
The licences are needed to register the clients on the system.
• 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.
• 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.
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
70 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
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.
• 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.
• 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.
• 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 2 audio channels for recording or play-
ing 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.
Features
• 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 415/430 71
syd-0580/2.0 – R6.0 – 09.2018
Expansion Stages and System Capacity
Resources
Note:
This licence is required for Mitel 415/430, Mitel SMBC and Mitel 470 only. For Virtual Appli-
ance, 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.
72 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
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.
Networking
Private networking
Mitel 415/430 73
syd-0580/2.0 – R6.0 – 09.2018
Expansion Stages and System Capacity
Applications
• 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 61). It cannot be combined with CTI third-party licences.
• Dialers
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 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.
74 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
Expansion Stages and System Capacity
Note:
Either the OpenCount application or a third party application can use the Open Application
Interface.
Interfaces
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.
• 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
Mitel 415/430 75
syd-0580/2.0 – R6.0 – 09.2018
Expansion Stages and System Capacity
one or both protocols for third-party applications. Only one licence is needed for a
user with several SIP phones.
• Basic User
This licence allows third-party applications to use the Open Application Interface.
Note:
Either the OpenCount application or a third party application can use the Open Application
Interface.
• 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.
76 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
Expansion Stages and System Capacity
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 Licences ( =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. 30) shows which
trial licences are available.
Overview of licences
Tab. 30 Overview of licences
Offlin
With- Licences Trial
e
Licence Licensed attributes out With licence for net- licenc
licenc
licence working e
e
Software
Software Release Allows a particular soft- Restrict Unrestricted In the AIN, – –
ware release to be oper- ed1) only on the
ated Master;
otherwise
per node.
Users
Basic User Licence bundle: 0 1 additional user per In the AIN, ✓ –
1 additional user licence. only on the
1 phone licence (any one) Master;
1 phone per user only otherwise
per node.
Entry UCC User Licence bundle: 0 1 additional user per In the AIN, ✓ –
• 1 additional user licence. only on the
• 8 phone licences (any Master;
one) otherwise
• 8 phones per user per node.
• Video licence for all
licensed phones.
• MiCollab role UCC
Entry
Standard UCC User Licence bundle: 0 1 additional user per In the AIN, ✓ –
• 1 additional user licence. only on the
• 8 phone licences (any Master;
one) otherwise
• 8 phones per user per node.
• Video licence for all
licensed phones.
• MiCollab role UCC
Standard
Mitel 415/430 77
syd-0580/2.0 – R6.0 – 09.2018
Expansion Stages and System Capacity
Offlin
With- Licences Trial
e
Licence Licensed attributes out With licence for net- licenc
licenc
licence working e
e
Premium UCC User Licence bundle: 0 1 additional user per In the AIN, ✓ –
• 1 additional user licence. only on the
• 8 phone licences (any Master;
one) otherwise
• 8 phones per user per node.
• Video licence for all
licensed phones.
• MiCollab role UCC Pre-
mium
Terminals
MiVoice 2380 IP Number of registered 0 Per licence 1 addi- In the AIN, ✓ ✓
Softphones MiVoice 2380 IP IP soft- tional IP softphone only on the
phones Master;
otherwise
per node.
MiVoice 5300 IP Number of registered , 0 1, 20 or 50 additional In the AIN, ✓ ✓
Phones2) MiVoice 5360 IP, IP system phones per only on the
MiVoice 5361 IP, licence Master;
MiVoice 5370 IP and otherwise
MiVoice 5380 IP IP sys- per node.
tem phones
Mitel SIP Terminals Number of registered 0 1, 20 or 50 additional In the AIN, ✓ ✓
phones of the Mitel SIP phone per only on the
Mitel 6800/6900 SIP licence Master;
series otherwise
per node.
Mitel 8000i Video Use of the video function- 0 Additional licence for In the AIN, ✓ ✓
Options ality of an Mitel SIP termi- Mitel SIP Terminals. 1, only on the
nal 20 or 50 additional Master;
Mitel SIP terminals otherwise
with video functionality per node.
per licence.
MMC Extensions Number of mobile phones 0 Per licence 1 addi- In the AIN, – –
that can be registered tional mobile phone only on the
with Mitel Mobile Client (with Mitel Mobile Cli- Master;
for operation with an Mitel ent) otherwise
Mobile Client Controller per node.
(MMCC)
Dual Homing Number of registered 0 Per licence 1, 20 or 50 Always on – ✓
Mitel 6800/6900 SIP additional phones the backup
phones on a backup com- communi-
munication server cation
server
78 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
Expansion Stages and System Capacity
Offlin
With- Licences Trial
e
Licence Licensed attributes out With licence for net- licenc
licenc
licence working e
e
Mobile or External Number of mobile/exter- 0 One additional In the AIN, ✓ ✓
Phone Extensions nal phones that can be mobile/external phone only on the
registered (without Mitel per licence (without Master;
Mobile Client) Mitel Mobile Client) otherwise
per node.
SIP Terminals Number of registered 0 1 additional standard In the AIN, ✓ ✓
standard SIP terminals SIP terminal per only on the
licence Master;
otherwise
per node.
Video Terminals Use of the video function- 0 Additional licence for In the AIN, ✓ ✓
ality of a standard SIP ter- SIP Terminals. 1 addi- only on the
minal tional standard SIP ter- Master;
minal with video func- otherwise
tionality per licence. per node.
BluStar
BluStar Softphones Number of registered 0 1, 20 or 50 additional In the AIN, ✓ ✓
BluStar softphones BluStar softphones per only on the
licence Master;
otherwise
per node.
BluStar Softphone Use of the video function- 0 Additional licence for In the AIN, ✓ ✓
Video Options ality of a BluStar soft- BluStar softphone. 1, only on the
phone 20 or 50 additional Master;
BluStar softphones otherwise
with video functionality per node.
per licence.
Audio services
Conference Bridge Use of conference bridge Locked Enabled In the AIN, – ✓
(Dial-In Conference) only on the
Master;
otherwise
per node.
Number in Queue Use of the function 'queue Locked Enabled In the AIN, ✓ ✓
with announcement ' only on the
Master;
otherwise
per node.
Auto Attendant Use of the auto attendant Locked Enabled In the AIN, ✓ ✓
function only on the
Master;
otherwise
per node.
Mitel 415/430 79
syd-0580/2.0 – R6.0 – 09.2018
Expansion Stages and System Capacity
Offlin
With- Licences Trial
e
Licence Licensed attributes out With licence for net- licenc
licenc
licence working e
e
Enterprise Voice Voice compression, Locked Enabled (including 2 In the AIN, ✓ ✓
Mail expanded voice memory audio channels for only on the
capacity, and e-mail noti- voice mail, Auto Atten- Master;
fication whenever new dant or call recording) otherwise
voice messages are per node.
received, forwarding of
voice messages, call
recording.
Audio Record & Audio channels for Locked Per licence 1 addi- In the AIN, – –
Play Channels recording or playing back tional audio channel only on the
audio data. for voice mail, Auto Master;
Attendant or call otherwise
recording per node.
Features
Analogue Modem Use of the modem func- Locked Enabled In the AIN, ✓ ✓
tionality on an only on the
Mitel 415/430. Master;
otherwise
per node.
Secure VoIP Encrypted VoIP connec- Non- Encrypted transmis- Per node – –
tions using SRTP and encrypte sion
TLS. d trans-
mission
Silent Intrusion Use of the Silent intrusion Locked Enabled In the AIN, – –
feature only on the
Master;
otherwise
per node.
Resources
VoIP Channels for VoIP functionality 0 / 2 4) Per licence 1 addi- In the AIN, ✓ ✓
Standard Media tional VoIP channel only on the
Switch3) Master;
otherwise
per node.
Network
B-Channels on PRI B channels that can be 10 Per licence 1 addi- In the AIN, – –
Cards used simultaneously on tional B- channel only on the
the PRI interface Master;
otherwise
per node.
SIP Access Chan- Simultaneously usable 0 Per licence 1 addi- In the AIN, ✓ ✓
nels channels to an SIP pro- tional SIP access only on the
vider channel Master;
otherwise
per node.
80 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
Expansion Stages and System Capacity
Offlin
With- Licences Trial
e
Licence Licensed attributes out With licence for net- licenc
licenc
licence working e
e
Private networking
QSIG Networking QSIG channels 0 Per licence 4 or n Per node ✓ ✓
Channels5) QSIG channels (n lim-
ited by the system
capacity)
Base Mitel AIN Operation of an AIN Locked AIN with master and Only on the – –
one satellite Master
Mitel AIN Satellites Additional satellite in an 0 Additional licence for Only on the – –
AIN Base Mitel AIN. 1 addi- Master
tional satellite per
licence
Applications
Advanced Messag- SMPP protocol for inte- Locked Enabled In the AIN, – –
ing gration of an SMS server only on the
and registration of 9d Master;
cordless phones as sys- otherwise
tem phones. (Includes per node.
licence SMPP)
CTI First Party via First-party CTI clients 0 Enabled for a specific In the AIN, – ✓
LAN with basic functions on number of users (see only on the
Ethernet interface "General system Master;
capacity", page 61) otherwise
per node.
Dialers Number of simultane- 0 1, 20 or 50 additional In the AIN, – ✓
ously active, user-linked instances per licence only on the
Mitel Dialer applications. Master;
otherwise
per node.
Hospitality Manager Use of Mitel 400 Hospital- Locked Enabled In the AIN, – ✓
ity Manager only on the
Master;
otherwise
per node.
Hospitality PMS Use of the PMS interface Locked Enabled In the AIN, – ✓
Interface and therefore the FIAS only on the
protocol. Master;
otherwise
per node.
Hospitality PMS Number of rooms when 0 1, 20, 50 or 100 rooms In the AIN, – ✓
Rooms using the PMS interface. per licence only on the
Master;
otherwise
per node.
Mitel 415/430 81
syd-0580/2.0 – R6.0 – 09.2018
Expansion Stages and System Capacity
Offlin
With- Licences Trial
e
Licence Licensed attributes out With licence for net- licenc
licenc
licence working e
e
Mitel OpenCount Basic licence: Prerequi- Locked Enabled In the AIN, ✓ ✓
Basic Package site for all other only on the
OpenCount licences. Master;
Enables connection to the otherwise
MiVoice Office 400 and per node.
the use of basic functions.
Mitel OpenCount Additional licence: Offers Locked Enabled In the AIN, ✓ ✓
Healthcare Branch extra functions for care only on the
Package homes and retirement Master;
homes. otherwise
per node.
Mitel OpenCount Additional licence: Offers Locked Enabled In the AIN, ✓ ✓
Public Authorities extra functions for munic- only on the
Branch Package ipalities, communities and Master;
ministries. otherwise
per node.
Mitel OpenCount Additional licence: Offers Locked Enabled In the AIN, ✓ ✓
Functional Upgrade extra functions such as only on the
to Comfort PIN telephony. Master;
otherwise
per node.
Mitel OpenCount Additional licence: Offers Locked Enabled In the AIN, ✓ ✓
Functional Upgrade extra functions such as only on the
to Premium intermediate statements, Master;
invoicing etc. otherwise
per node.
Mitel OpenCount Additional licence: Ena- 0 1, 20 or 50 additional In the AIN, ✓ ✓
Users bles a defined number of users per licence only on the
users to be monitored via Master;
OpenCount. otherwise
per node.
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, – ✓
face only on the
Master;
otherwise
per node.
82 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
Expansion Stages and System Capacity
Offlin
With- Licences Trial
e
Licence Licensed attributes out With licence for net- licenc
licenc
licence working e
e
BSS Licence Right to connect a BluStar unavail- enabled In the AIN, – –
server able only on the
Master;
otherwise
per node.
BSS-Lync Interface Right to use the BluStar unavail- enabled In the AIN, – –
Lync interface able only on the
Master;
otherwise
per node.
CSTA Sessions Number of monitored ter- 0 1, 20, 50 or 100 CSTA In the AIN, ✓ ✓
minals via the CSTA pro- sessions per licence only on the
tocol. Master;
otherwise
per node.
Presence Sync. via Number of users who can 0 1, 20 or 50 additional In the AIN, ✓ ✓
SIMPLE and MSRP use one (or both) proto- users per licence who only on the
cols for the third-party may use both proto- Master;
applications. cols. otherwise
per node.
OAI Interface Use of the Open Applica- Locked Enabled In the AIN, – ✓
tion Interface only on the
Master;
otherwise
per node.
1) 4 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 76).
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.
All the licences are offered in separate licence packages. Depending on the sales
channels the packages may differ from the licences in Tab. 30. 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.
Mitel 415/430 83
syd-0580/2.0 – R6.0 – 09.2018
Expansion Stages and System Capacity
The number of permissible terminals per system depends on the power requirements
of the individual terminals. To check the power requirements refer to Tab. 32 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.
84 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
Expansion Stages and System Capacity
Tip
With the planning application Mitel CPQ the power supply available for terminals is checked
automatically.
Overload shut-down
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).
Mitel 415/430 85
syd-0580/2.0 – R6.0 – 09.2018
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.
Fan
Power cord
Left-hand bracket
for cable cover Cable cover
86 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
Installation
4. 2. 1 Equipment supplied
The equipment supplied with the communication server includes:
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.
• Cable cover
• Left-hand bracket for cable cover
• Right-hand bracket for cable cover
• Screw set
Mitel 415/430 87
syd-0580/2.0 – R6.0 – 09.2018
Installation
• Screw set
• Fan
4. 2. 3 Location requirements
The following location requirements must be observed when positioning the communi-
cation server.
WARNING!
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 clearances or lowering the ambi-
ent temperature.
For Mitel 430 install the fan from the rack-mounting set.
4. 2. 4 Safety regulations
Be sure to observe the following safety regulations before carrying out work inside a
communication server:
CAUTION!
Components, interface cards or system modules can be damaged by electrical voltage.
Always shut down and disconnect the communication server from the power supply before removing the
housing cover.
CAUTION!
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 hous-
ing. This also applies to interface cards and system modules that are no longer packed inside the ESD pro-
tective wrapping.
88 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
Installation
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.
CAUTION!
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.
t
t
Fig. 12 Minimum distances for wall mounting (front panel facing to the right)
Mitel 415/430 89
syd-0580/2.0 – R6.0 – 09.2018
Installation
t
t
All dimensions in mm
Fig. 13 Minimum distances for wall mounting (front panel facing downwards)
4. 2. 5. 2 Drilling plan
The communication server is suspended into two pre-mounted 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).
90 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
Installation
"
#
$
" #
All dimensions in mm
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.
Mitel 415/430 91
syd-0580/2.0 – R6.0 – 09.2018
Installation
"
$
4. 2. 5. 4 Wall-mounting procedure
Materials required:
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.
92 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
Installation
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 "Shut-down Mode", page 202) and dis-
connect it from the power supply.
CAUTION!
Be sure to observe the "Safety regulations", page 88.
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 92).
CAUTION!
To ensure adequate heat dissipation make sure that no objects are placed on top of the communication
server (see also "Location requirements", page 88). Minimum distances must also be observed as shown
in Fig. 12.
4. 2. 7 Rack-mounting
The rack-mounting set allows the communication server to be installed 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).
Mitel 415/430 93
syd-0580/2.0 – R6.0 – 09.2018
Installation
• 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
6OJUT
6OJU
6OJU
6OJUNN
Fig. 16 Placing two communication servers above each other inside a 19” rack
4. 2. 7. 1 Rack-mounting procedure
Materials required:
• Rack-mounting kit
• Screw set for wall/desktop installation
• Screwdriver
1. Pull off the screw covers on the left and right of the front panel.
94 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
Installation
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 "Shut-down Mode", page 202) and dis-
connect it from the power supply.
CAUTION!
Be sure to observe the "Safety regulations", page 88.
1. Shut down the communication server (see "Shut-down Mode", page 202) and dis-
connect it from the power supply.
CAUTION!
Be sure to observe the "Safety regulations", page 88.
Mitel 415/430 95
syd-0580/2.0 – R6.0 – 09.2018
Installation
Note
The fan only turns if required by the equipment temperature.
!
N
A
F
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 ones in Fig. 18.
3. Fit the cable cover over the brackets from above until they are felt to engage.
96 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
Installation
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.
CAUTION!
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.
CAUTION!
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.
Mitel 415/430 97
syd-0580/2.0 – R6.0 – 09.2018
Installation
Communication Communication
Server Server
Fig. 20 Earthing of the communication server in the case of an indirect cabling and direct cabling
98 Mitel 415/430
syd-0580/2.0 – R6.0 – 09.2018
Installation
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.
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
Mitel 415/430 99
syd-0580/2.0 – R6.0 – 09.2018
Installation
WARNING!
Hazard due to heat generation in the event of short-circuits. The mains power supply connection 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).
• 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
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.
See also
For more technical details see "Technical data", page 244.
CAUTION!
Be sure to observe the "Safety regulations", page 88.
1. Shut down the communication server (see "Shut-down Mode", page 202) 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 "Fitting a wiring adapter", page 102) into
the appropriate wiring adapter slot WA1…WA4.
6. Fit the housing cover.
7. Reconnect the communication server to the power supply.
Interface card
1
Metal clamp 50 - 60°
Slot 25°
Mainboard
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 135).
– The interface cards EAD4V and EAD4C cannot be fitted to slot IC4 of an Mitel 430 due to
their mechanical dimensions.
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.
Note
– The arrows on the wiring adapters specify the plug-in orientation of the required port assign-
ment.
– 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 201).
– 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.
RIGHT WRONG
CAUTION!
Be sure to observe the "Safety regulations", page 88.
1. Shut down the communication server (see "Shut-down Mode", page 202) and dis-
connect it from the power supply.
2. Remove the housing cover.
3. Remove the fastening screw from the DSP module slot.
4. Instead of the fastening screw, screw in the spacer sleeve enclosed with the mod-
ule.
5. Place the module on the DSP slot (or onto a module already 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.
• In principle the interface cards can be used in all the card slots.
Exceptions:
– 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 not supported.
• 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 60). 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.
• 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
On the front panel all the connections are made using RJ45 connectors.
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 110.
4. 6. 2 Indirect connection
There are two possibilities for connecting the communication server indirectly to the
telephone network and terminal-side cabling:
Communica-
tion server
NT1
NT1
(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 243).
Notes:
– This cable cannot be used to connect PRI and Ethernet interfaces (see also "Connection of
PRI primary rate interface", page 114 and "Connection of Ethernet interfaces", page 143).
– It is not possible to connect an ODAB door intercom interface with only one cable (see also
"Connection of a door intercom (TFE)", page 136).
Tip
Use standard commercial connecting cables not just for the PRI and Ethernet interfaces but
also for connecting the BRI-T interfaces.
A B
View A View B
Fig. 27 Pin numbering, RJ45 connector
Phone
User
User
(Main) distri-
bution frame
Communica-
tion server User Patch panel
EDV
NT1
Public
NT1 exchange
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.
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.
Notes
– The interfaces can be configured on BRI-S using the wiring adapters (see "Fitting a wiring
adapter", page 102).
– The maximum number of interfaces per communication server has to be taken into account
(see Tab. 29).
– 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. 38 Cable requirements for basic rate interface BRI-T
Core pairs × cores 1×4o2×2
Stranded yes
Wire diameter, core 0.4…0.6 mm
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)
[1] Communica-
NT1 tion server
U BRI-T BRI-T
c c
a d d
Exchange b e e
[2] f f
The assignment of the RJ45 connector is identical on the NT-side and on the side of
the communication server.
Fig. 33 BRI-S basic rate interface external, networked with copper line
Tab. 40 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 125).
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. 41 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.
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.
NT1
RXA
Exchange RXB Communication
U PRI TXA server
TXB
4-wire
PRI Copper line PRI
PINX 1 PINX 2
max. 200 m
Tab. 44 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
Tab. 45 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
3 — — 3
6 — — 6
7 — — 7
8 — — 8
Leased-line
PRI PRI
PINX 1 NT1 or dial-up NT1 PINX 2
connection
Fig. 39 Primary rate access PRI, networked with leased-line or dial-up connection
Tab. 46 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
3 — — 3
6 — — 6
7 — — 7
8 — — 8
See also:
System Manual “PISN / QSIG Networking”
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:
Cable Requirements
Tab. 48 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.
Note
Circuit type as per EN/IEC 60950: SELV
Connection
Tab. 49 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
1. Connection
point
Communica-
tion server
1. Connection 2. Connection
point point
Communica-
tion server
C
B
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. 51 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
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
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.
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:
Power available case A:
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]
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]
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]
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]
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.
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. 51: 1220 mW
Fig. 43 indicates:
Example 2:
An MiVoice 5380 with 2 MiVoice M530 expansion key modules
Power requirements as per Tab. 51: 1340 + 300 + 300 = 1940 mW.
Fig. 43 indicates:
Example 3:
Evaluation of an existing line installation
Line diameter: 0.5 mm
Loop resistance: 120 Ω
Fig. 43 indicates:
Cable Requirements
Tab. 52 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:
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.
Notes
– Some of the interfaces can be configured on BRI-T using the wiring adapters (see "Fitting a
wiring adapter", page 102).
– The maximum number of interfaces per communication server has to be taken into account
(see Tab. 29).
Connection
Tab. 53 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:
Tab. 54 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 128).
8. Connection
1. 2. 3. point
Communica-
2 x 100 Ω
tion server
max. 150 m
Communication
server
(Main)
max. 3 m
distribution 8. Connec-
1. 2. 3. frame tion point
2 x 100 Ω 2 x 100 Ω
4. Connection
1. 2. point
Communica-
tion server 2 x 100 Ω
max. 20 m
max. 500 m
Connection
point
Communi-
cation 2 x 100 Ω
server
max. 1000 m
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:
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
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
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. 56 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)
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.
Connection
Tab. 57 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
After a first start all the FXS interfaces are configured on Phone / Fax.
CAUTION!
Terminals connected to FXS interfaces can be damaged if the configuration of the FXS interface mode is
unsuitable.
Note
Circuit type as per EN/IEC 60950: TNV-2
• Analogue phones with DTMF or pulse dialling (earth key is not supported)
FXS interface
The no-load voltage at the ports is approx. 53 VDC. The loop current is limited to 25
mA.
1) Transmission with the T.38 protocol is recommended for Fax over IP. The corresponding media re-
sources need to be allocated.
FXS interface
CAUTION!
Control outputs must have a floating connection.
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.
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 135).
CAUTION!
Control inputs must have a floating connection.
a 25mA
24 VDC
b
FXS interface
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.
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 135).
48 VAC
b
48 VAC
FXS interface
See also
"General bell on FXS interface" in the "System Functions and Features" System Manual.
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.
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.
Port 3 TO
Port 1 KT
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. 59.
Connection
Tab. 62 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 –
A Ta
TS1 Speech path
power supply
TS2
TO1
Door
TO2
115/230 VAC
KT1
Bell key switch must
KT2 be floating
ODAB
CAUTION!
• The bell key switch does not require an external power supply, but must have a floating connection.
• 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".
Jumper Configuration
The jumper configuration is shown in the following diagram.
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. 61.
Tab. 65 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 –
CAUTION!
The control inputs do not require an external power supply but they must have a floating connection.
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. 5 Audio interface
The audio interface can be used for the following purposes:
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.
4. 7. 6 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.
Note
Circuit type as per EN/IEC 60950: SELV
Socket
Tab. 70 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.
First-start response
The IP addressing after a first start depends on whether a static IP addressing is al-
ready stored from a previous configuration. A static IP addressing (IP address, subnet
mask, gateway) entered manually is stored and remains 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 (e.g. after initial delivery), the communication 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 log on 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. 71) with a direct connection.
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 196).
Cable Requirements
Use commercial Cat. 5 cable, or choose a cable type with the following characteristics:
4. 8. 1 IP system phones
Accesses
Tab. 73 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
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.
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.
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. 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".
MiVoice 1560 PC Operator and Mitel OfficeSuite are described in the "Mitel Open In-
terfaces Platform" System Manual.
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.
Note:
The total length of the cables from the communication server to the system phone must not be
less than 10 m.
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. In this situation, although the system phone can be used for basic telephone oper-
ations, 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 configuration.
Carrying out a logon on the system phone: Long keypress (long click) on a function key. Set
new phone type appears next. Confirm with Foxkey Yes.
Note:
To prevent any damage to the phone, always disconnect the phone from the power supply
first before connecting a headset to DHSG standard.
CAUTION!
The system's reliability can be adversely affected by electrostatic discharges caused by touching 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 ➃).
• Long line
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 118 ff.
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. 66).
• 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
Note:
If these requirements cannot be met (e.g.outdoor installation), use the appropriate protective
housing.
160
37 100
84
ø screw : 4 mm
168
Mounting bracket
All dimensions in mm
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
115/230 VAC
(optional)
DSI interface
Socket 1
Socket 2
For further display variants, see "Operating state of the Mitel DECT radio units",
page 235
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.
switch is set correctly. If the MWI LED is on when a message is available and blinking
when no message is available 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.
– The notification type Low voltage is also supported (used for other analogue phones, espe-
cially in USA and Canada).
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.
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.
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.
5 Configuration
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 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.
The standard PIN "0000" is accepted, but must be changed during first login. You can
choose any 2 to 10-digit number combination.
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 communi-
cation 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).
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 and SMB Controller, System Search is only available for downloading lan-
guage 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.
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.
Note:
External access (ISDN/analogue) with a dial-up connection is only recommended on some con-
ditions, for performance reasons.
See also:
If you are setting up an MiVoice Office 400 communication system for the first time, read the
chapter "Getting started", page 36).
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).
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:
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 167.
You can see the predefined user accounts in the User account ( =a7) view.
Note:
The predefined user accounts cannot be deleted.
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).
Note:
Authorization profiles can only be viewed or created by Administrators in Expert mode.
5. 3. 1. 3 Passwords
To ensure that the communication server can only be configured by authorized person-
nel, access to the configuration is password-protected.
Password syntax
The following rules apply to password selection and spelling:
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.
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.
If the passwords of all administrators are lost, access can still be gained locally without
a password (see "Password-free access", page 168).
5. 3. 2 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 205.
There is no password-free access for remote maintenance.
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.
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.
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 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, read the
chapter "Getting started", page 36.
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:
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. 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 (Licences =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. 30) shows which
trial licences are available.
All licences are stored in a licence file, which you can obtain from your authorised
dealer. Each licence file can only be used for one communication server. To licence
several communication servers, you will obtain separate licence files 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
file is required on the Master.
1) In USA/Canada the abbreviation DID (Direct Inward Dial) is used instead of DDI (Direct Dialling In).
See also:
"Licences", page 67
5. 6. 2 File management
The file management of the MiVoice Office 400 application is done via 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 6800/6900 SIP phones via FTP server. Moreover, you can manually
or automatically load the languages for the WebAdmin, Hospitality Manager 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.
5. 6. 3 System reset
5. 6. 3. 1 Restart
Restart via WebAdmin
A restart via WebAdmin is triggered in the maintenance settings with the Restart button
in the System reset( =4e) view.
A restart via WebAdmin reboots the MiVoice Office 400 communication server. The
configuration data is preserved.
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.
5. 6. 3. 2 First start
A first start has the effect of resetting the MiVoice Office 400 communication server
from scratch. The system-specific data such as the system ID, system type, sales
channel, licence file, software generation and IP address of the system are preserved.
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.
Note:
This function is only accessible for Administrators in Expert mode.
5. 6. 4 Data backup
With a configuration data backup all the MiVoice Office 400 configuration data of the
communication server is stored in a compressed file in ZIP format. You can let the con-
figuration 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.
The configuration backup and the audio data backup are always stored in a encrypted
format.
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 MiVoice Office 400 config-
uration data at regular intervals and saves the backup files on the communication
server’s file management 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.
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 MiVoice Office 400 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.
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 spreadsheets.
You can find the export function in the following views:
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.
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
• 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, generation, DECT identification numbers,
IP address of the configuration server). The contents of the memory are retained
even when there is no power supply.
Mainboard
Range of the RAM chips
EIM card
Range of
the Flash
chips
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 com-
munication server starts up, the software on the Flash memory is decompressed,
loaded into the main memory and started.
6. 1. 1. 2 File system
MiVoice Office 400 file system
The file system of the MiVoice Office 400 communication server comprises the MiVoice
Office 400 application software, the software for system phones, the system and termi-
nal configuration data, the audio data, system logs, data for WebAdmin, etc. With
WebAdmin you have access to the file system via the menu item File management.
You can see the file system memory load and you can load audio data, languages for
the user interface and online help, language files for Mitel 6800/6900 SIP-series
phones as well as an external numbering plan for SIP connection. Moreover, with the
file browser you have the possibility to view, upload, replace or delete folders and files
in the file system. (see also "File management", page 173).
Functions for backing up and restoring MiVoice Office 400 configuration data and au-
dio data are available in the WebAdminMaintenance / Data backup ( =um) view (see
also "Data backup", page 175).
Usually there is no need to access the MiVoice Office 400 file system directly as all
needed functions are available in WebAdmin. For special cases you can access the
MiVoice Office 400 file system with a FTP session.
Note:
Modifying or deleting files on the file system 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 MiVoice Office 400
application software.
6. 1. 1. 4 System-specific data
The system-specific data (system ID, system type, sales channel, generation, 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 communication server,
and remains available. It can be ported to a different communication server by replac-
ing the EIM card.
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 165.
6. 2 Update Software
6. 2. 1 System software
MiVoice Office 400 application software
The MiVoice Office 400 application software is normally updated with WebAdmin. In
exceptional cases (e.g. during downgrade), an Emergency Upload via System Search
is required (see also page 182).
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 6800/6900 SIP phones as well as on Mitel 600 DECT
DECT phones via the menu.
Depending on the phone, additional information is displayed.
Providing the MiVoice Office 400 system software and licence file
The new MiVoice Office 400 system software and the relevant licence file 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 gen-
erate the new licence file through the Mitel Connect internet portal https://connect.mi-
tel.com and upload it to your communication system. You need a login to access
Mitel Connect (user name and password).
In newly delivered systems it is possible to directly load new system software after
choosing the sales channel.
Notes:
– Most times a new licence file is also required for new MiVoice Office 400 system software.
You can also install and start up the new software without specifying the licence file. How-
ever, once you have started to use the software you will need to upload the licence file 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.
– 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.
– Please read the chapter “Important hints and restrictions” in the release notes to the soft-
ware to be loaded.
See also:
A detailed description of the software upload procedure with WebAdmin is available in the
online help.
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 202).
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. 89). This is normal since it takes a while to
decompress the system software..
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.
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.
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 all concerned users if the system has to be put out of operation during work-
ing time.
2. Shut down the communication server (see "Shut-down Mode", page 202) and dis-
connect it from the power supply.
6. 3. 2 System information
Some system information are stored on the EIM (Equipment Identification Module)
card. The information includes:
The data is not deleted by a first start of the MiVoice Office 400 communication server,
and remains available.
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 file can be obtained either from your authorized dealer or via
Mitel Connect https://connect.mitel.com using the EID (partner login required).
3. Upload the licence file in the Licences ( =q9) view. The licence file is stored in the
file system of the communication server in the sub directory ...\data\lic.
4. The newly licensed features are enabled. It is not necessary to restart the communi-
cation server (exception: AIN licences).
See also:
"Licences", page 67
6. 3. 2. 2 EIM card
The EIM card must be replaced in the following cases:
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 104.
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.
CAUTION!
Be sure to observe the "Safety regulations", page 88.
• 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.
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.
1. Change the card and put the system into operation again. Similar procedure as de-
scribed in "Replacing a defective interface card", page 187.
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).
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 187.
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 201).
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 104).
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.
CAUTION!
Be sure to observe the "Safety regulations", page 88.
Note:
If there are several modules fitted and the module 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.
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.
CAUTION!
Be sure to observe the "Safety regulations", page 88.
&*.
Notes:
– The EIM card must be fitted before the system is put into operation. The communication
server will not start without the EIM card.
– 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:
CAUTION!
Be sure to observe the "Safety regulations", page 88.
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.
6. 3. 7. 2 DECT terminals
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.
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.
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.
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 195).
1)Supported as of R2.1
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.
CAUTION!
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. 75 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.
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.
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.
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:
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.
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.
The following display patterns and symbols have been defined for displaying the status
of the communication server:
$53-
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:
Display pri-
Operating mode Remarks
ority
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.
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.
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:
Mutual combinations of patterns [12] and [13] are possible as are combinations with
patterns [14], [15] and [16].
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:
Mutual combinations of patterns [14], [15] and [16] are possible as are combinations
with patterns [12] and [13].
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. 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).
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 (pattern [1], Tab. 89). 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.
The boot mode remains active until the Emergency Upload is completed or the system
is restarted manually.
6. 4. 3. 9 Shut-down 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 204). It then remains in Shut-down 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 shut-down mode.
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).
Requirement:
The system is in "Application Command Mode", page 200.
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.
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.
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.
Requirement:
The system is in "Application Command Mode", page 200.
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.
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.
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.
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, software genera-
tion and IP address of the system are preserved.
Requirement:
The system is in "Boot Command Mode", page 201.
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.
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.
• IP address: 192.168.104.13
• Subnet mask: 255.255.255.0
• Gateway: 0.0.0.0
6. 5 Operations supervision
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
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, positive or negative impact (if any) and the information, if there is
a match or not, 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 233).
Tab. 101 Meaning of the parameter values for the event message Send e-mail failed
Parameter 1 (XXYY) Parameter 2: Parameter 3:
Additional info
1) depending on the
Value Reason (XX) Action (YY) E-mail client
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
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.
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.
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.
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.
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
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
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.
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
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).
You will find the interface description and the different MIB versions on Mitel InfoChan-
nel – Mitel Solution Alliance - API and Interface Information - MiVoice Office 400 - Mi-
Voice Office 400 Network Management.
To access these documents, you have to be a member in Mitel Solution Alliance
(MSA). If you are not a member yet, go to Mitel website and search for “Mitel Solution
Alliance” where you can join. A membership on level MSA partner (MP) is sufficient.
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.
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:
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. 100 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).
→ 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.
• System is running but a problem has been detected on one or more wiring adapter
slots. (See "Wiring Adapter Malfunction Mode", page 201.)
• Warning. System is still capable of running but the system function may be impaired
(see "Warning Mode", page 201).
• Serious error. System is no longer able to run (see "Error Mode", page 203).
In the event of sporadic errors check the installation for earth loops.
6. 5. 2. 3 Terminals
Tab. 103 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
Tab. 104 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
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 – – – – 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.
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. 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.
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
ID
Power
specification
System
PCB designation Type
approval
Material no.
Production date Serial number
7. 3 Equipment Overview
Tab. 112 Equipment Overview
Description
Mitel 415 basic system with power supply unit and power cable
Mitel 430 basic system with power supply unit and power cable
DSP module SM-DSPX1
DSP module SM-DSPX2
Description
TIC-2AB trunk card (2 x FXO)
TIC-4AB trunk card (4 x FXO)
TIC-1PRI ISDN primary trunk card
TIC-2TS ISDN basic trunk card/terminal interface card
TIC-4TS ISDN basic trunk card/terminal interface card
Terminal card EADP4 (4 x DSI-AD2)
Terminal card ETAB4 (4 x FXS)
Options card ODAB
Wiring adapter 2W
Wiring adapter TS0
Wiring adapter TS1
Wiring adapter 1PRI
Prefabricated system cable 12 x RJ45, 6 m
RJ45 patch cable, blue, screened, 1 m
RJ45 patch cable, blue, screened, 2 m
Mitel 415 rack-mounting set
Mitel 430 rack-mounting kit incl. fan
Cable cover set for Mitel 415/430
7. 4 Technical data
7. 4. 1 Network interfaces
The following technical data applies to the network interfaces:
• E1 ISDN PRI
– 30 B channels, 1 D channel, Bitrate 2.048 Mbit/s
– Protocol DSS1 (public), QSIG/PSS1 (private) – used mainly in Europe
– Protocol CAS MFC R2 – used in Brazil
– Only on TIC-1PRI card
• 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:
7. 4. 3 Communication server
Tab. 114 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)
Card/module Design
WA-TS0 F2
WA-TS1 F2
WA-2W1) F1
WA-1PRI F1
1) Must not be used in USA/Canada.
"NN
#NN
$NN
NN
NN
NN
NN NN
7. 4. 5 LAN switch
%DVH7%DVH7;VZLWFK
)XOO\FRPSOLDQWZLWK,(((X
$XWR0',;$XWRSRODULW\$XWRQHJRWLDWLRQ
)ORZFRQWUROIXOO\VXSSRUWHG KDOIGXSOH[EDFNSUHVVXUHIORZFRQWUROIXOOGXSOH[,((([IORZFRQWURO
(PEHGGHG65$0IRUSDFNHWVWRUDJH
HQWU\ORRNXSWDEOHGLUHFWPDSSLQJPRGH
4R6S9/$1WDJ'LII6HUY726ILHOGLQ7&3,3KHDGHU,3EDVHGSULRULW\
Technical data
Tab. 123 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
DEF3É GHI4
def3éèê ghi4ì
JKL5 MNO6ÑÖØ
jkl5 mno6ñöøò
PQRS7 TUV8Ü
pqrs7ß tuv8üù
WXYZ9 +0
wxyz9 +0
*/()<=>%£$¤¥¤@&§ Space #
*/()<=>%£$¤¥¤@&§ Space #
Notes:
– The MiVoice 5360 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.
The function commands can be stored directly on the system phones via Self Service
Portal or on the function keys via WebAdmin.
•
• 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.
7KH9RYLGD6RIWZDUH/LFHQVH9HUVLRQ
&RS\ULJKW F 9RYLGD1HWZRUNV,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\ULJKW F
0RGHPDQG96RIWZDUHLV&RS\ULJKW F 63,5,7
(FKR&DQFHOODWLRQ6RIWZDUHLV&RS\ULJKW F 63,5,7
<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
Product Document
IP system phones Quick User's Guide MiVoice 5360 IP / MiVoice 5361 IP / MiVoice 5370 IP
/MiVoice 5380 IP
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 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 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
R
Radio unit 235
RAM test 208
Replacing system terminals 191
Replacing the EIM card 190
Replacing the interface card 187
Replacing the Mainboard 191
Resetting the IP address 207
Restart 173, 174
Restart with database backup 205
Restart without database backup 205