Mitel Networks RFP4445, RFP47DRC User Manual

SIP-DECT OM System Manual

ADMINISTRATION GUIDE

Release 8.0

NOTICE

The information contained in this document is believed to be accurate in all respects but is not warranted by Mitel Networks™ Corporation (MITEL®). The information is subject to change without notice and should not be construed in any way as a commitment by Mitel or any of its affiliates or subsidiaries. Mitel and its affiliates and subsidiaries assume no responsibility for any errors or omissions in this document. Revisions of this document or new editions of it may be issued to incorporate such changes.

No part of this document can be reproduced or transmitted in any form or by any means - electronic or mechanical

- for any purpose without written permission from Mitel Networks Corporation.

TRADEMARKS

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

Mitel’s Power Over Ethernet (PoE) Powered Device (PD) products are covered by one or more of the U.S. patents (and any foreign patent counterparts thereto) identified at Mitel’s website: www.mitel.com/patents.

For more information on the PD patents that are licensed, please refer to www.cmspatents.com.

SIP-DECT OM System Manual

Administration Guide

Release 8.0 - September 2018

®,™ Trademark of Mitel Networks Corporation

CONTENTS

1 Overview..........................................................................................................................................................10

1.1 The SIP-DECT Solution 10

1.2 About DECT Base Stations 11

1.2.1 DECT Base Station Families 11

1.2.2 OpenMobility Manager (OMM) Mode 16

1.3 About the OpenMobility Manager 16

1.3.1 OMM Tasks 16

1.3.2 SIP-DECT Special Features and Capabilities 17

1.3.3 OMM Capacities and Features 18

1.3.4 OMM Capacities and RFP Support 18

1.4 About DECT Phones 19

1.5 File naming conventions 19

1.6 Login and passwords 20

2 Enhanced Feature Overview .........................................................................................................................21

2.1 PC-based OMM installation 21

2.2 DECT XQ 21

2.3 Wideband (CAT-iq 1.0 / Mitel Hi-Q™ audio technology) 22

2.4 DECT enhanced security 22

2.5 VoIP encryption 23

2.6 Mixed DECT base station installations 23

2.7 Wireless LAN (WLAN) 23

2.7.1 802.11i: WPA2-Enterprise Pre-Authentication for fast Roaming 23

2.7.2 Channel Configuration Feedback for HT40 and tx Power 24

2.7.3 Channel Configuration Feedback for HT80 24

2.8 DECT base station synchronization 24

2.8.1 Clustering and paging areas 24

2.9 DECT base station Reset to Factory Settings 25

2.9.1 RFP4G reset to factory defaults 25

2.10 System redundancy 26

2.10.1 OMM standby 26

2.10.2 Backup SIP proxy/registrar 26

2.10.3 Configurable User Account for Standby Check 26

2.10.4 User data synchronization (MiVoice 5000 dual homing support) 26

2.10.5 Multi-OMM Manager for OMM-centralized management 27

2.11 Simplified licensing 27

2.12 Extended regulatory domain support 27

2.13 DECT phone functionality 28

2.13.1 DECT Phone Download over Air 28

2.13.2 Central DECT Phone Configuration Over Air (CoA) 29

2.13.3 OMM DECT phone provisioning 30

2.13.4 Mitel 600 DECT Phone Dial Editor Mode 30

2.13.5 Mitel 602 DECT Phone Customizable Boot Texts 30

2.13.6 OMM-Centralized call logs 30

2.13.7 User individual DECT Phone PIN Key Lock 30

2.14 Hot Desking 31

2.15 Conferencing 31

2.15.1 Conferencing audio notification 32

2.15.2 Centralized conferencing with MiVoice Business 32

2.15.3 N-WAY CONFERENCING 32

2.16 SIP over UDP/TCP/TLS 33

2.17 SIP multiport 33

2.18 UTF-8 encoding 34

2.19 Alphanumeric dialing 34

2.20 Voice mail number 35

2.21 Call handling 35

2.21.1 Diversion indication 35

2.21.2 Call completed elsewhere 36

iii

2.21.3 Semi-Attended Transfer 36

2.21.4 Third Line Handling for Mitel 142d and 600 DECT Phones 36

2.21.5 Call Transfer Enhancements for Mitel 142d DECT phones 37

2.22 Truncating SIP User Name in SIP URI 38

2.23 OM Locating application 38

2.24 Extended messaging 38

2.25 Video support 38

2.25.1 USB Video Devices 39

2.25.2 Terminal Video 39

2.26 User monitoring 40

2.27 Corporate directory integration 41

2.28 Integration into external management systems 41

2.29 System configuration tools 41

2.30 SIP enhancements 42

2.30.1 Globally Routable User-Agent URIs (GRUUs) 42

2.30.2 Session timer 42

2.30.3 SIP Contact matching 42

2.30.4 Configurable Call reject state codes 43

2.30.5 Call release timers 43

2.30.6 Incoming call timeout 43

2.30.7 Call reject on silent charging 43

2.30.8 route header 43

2.30.9 MWI SUBSCRIPTION period 43

2.31 Auto answer, intercom calls and audio settings 44

2.31.1 Intercom Calls 44

2.31.2 Auto answer audio settings 45

2.32 SIP-DECT XML terminal interface 45

2.32.1 Feature Access Codes Translation 45

2.32.2 Ring Tone Selection for (Alarm) Messages 46

2.33 Software Update Dispersion 46

3 Licensing .........................................................................................................................................................47

3.1 Licensing Model 47

3.1.1 System Licenses 47

3.1.2 About G.729 Channels 48

3.1.3 PARK Service 48

3.1.4 Upgrade License 49

3.1.5 Grace Period 49

3.1.6 License Violations and Restrictions 50

3.2 Uploading a License File 50

3.3 License Models 51

3.3.1 Small System (Unlicensed) 51

3.3.2 Medium or Large System 51

4 Getting Started................................................................................................................................................53

4.1 Base Station Startup Configuration 53

4.2 System Configuration 53

4.3 System Settings 54

4.4 Base Stations 54

4.5 SIP settings 55

4.6 DECT Phones 56

4.6.1 DECT Phone and SIP state verification 57

5 OMM Web Service...........................................................................................................................................59

5.1 Login 59

5.2 Logout 60

5.3 “Status” Menu 60

5.4 “System” Menu 61

5.4.1 “System Settings” Menu 61

5.4.2 ”Provisioning” Menu 68

5.4.3 ”SIP” Menu 71

5.4.4 “User administration” Menu 79

5.4.5 “Time zones” Menu 81

5.4.6 “SNMP” Menu 82

5.4.7 “DB management” Menu 83

5.4.8 “Event log” Menu 85

5.5 “Sites” Menu 86

5.5.1 Creating a New Site 86

5.5.2 Editing a Site 87

5.5.3 Deleting a Site 87

5.6 “Base Stations” Menu 87

5.6.1 Base Station States 89

5.6.2 OMM / RFP Software Version Check 90

5.6.3 Creating and Changing Base Stations 90

5.6.4 Capturing DECT Base Stations 92

5.6.5 Deleting DECT Base Stations 92

5.6.6 Find my SIP-DECT Base Station 92

5.7 “DECT Phones” Menu 94

5.7.1 Creating and Changing DECT Phones 95

5.7.2 Importing DECT phone Configuration Files 96

5.7.3 Subscribing DECT Phones 97

5.7.4 Deleting DECT phones 98

5.7.5 Searching the DECT phone List 99

5.7.6 Displaying User and DECT Phone Data 99

5.8 “WLAN” Menu 103

5.8.1 “WLAN profiles” Menu 103

5.8.2 “WLAN clients” Menu 108

5.9 “System features” Menu 108

5.9.1 “Digit treatment” Menu 109

5.9.2 “Directory” Menu 110

5.9.3 “Directory (comp. mode)” menu 112

5.9.4 “Feature Access Codes” Menu 113

5.9.5 ”XML Applications” Menu 115

5.10 “Licenses” Menu 117

5.11 “Info” Menu 117

6 OM Management Portal (OMP) ......................................................................................................................118

6.1 Login 118

6.2 Logout 119

6.3 OMP Main Window 119

6.4 “Status” Menu 120

6.4.1 Overview 121

6.4.2 DECT base stations 122

6.4.3 Users 123

6.4.4 Devices 124

6.4.5 Sites 125

6.4.6 Conference 126

6.4.7 Video Devices 126

6.5 “System” Menu 127

6.5.1 “Basic settings” Menu 127

6.5.2 “Advanced settings” Menu 130

6.5.3 “Statistics” Menu (Monitoring Mode Only) 138

6.5.4 “SIP” Menu 139

6.5.5 ”Provisioning” Menu 143

6.5.6 “User administration” Menu 145

6.5.7 “Data management” Menu 149

6.5.8 “Event Log” Menu 151

6.6 “Sites” Menu 153

6.7 “DECT Base Stations” Menu 154

6.7.1 “Device list” Menu 154

6.7.2 “Paging areas” Menu 160

6.7.3 “Capturing” Menu 161

6.7.4 “Enrolment” Menu 162

6.7.5 “Export” Menu 162

6.7.6 “Sync view” Menu 163

6.7.7 “Statistics” Menu 164

6.7.8 “Quality” Menu 166

6.8 “WLAN” Menu 168

6.8.1 Profiles 168

6.9 “Video devices” Menu 172

6.9.1 Changing Video Devices 172

6.9.2 Viewing Video Device Details 173

6.9.3 Deleting Video Devices 173

6.9.4 Filtering Video Device Table 173

6.10 “DECT Phones” Menu 173

6.10.1 ”Overview” Menu 174

6.10.2 “Users” Menu 176

6.10.3 “Devices” Menu 176

6.10.4 Device Detail Panel 177

6.10.5 Creating DECT phone Datasets 184

6.10.6 Configuring DECT phone Datasets 185

6.10.7 Subscribing DECT phone Datasets 185

6.10.8 Deleting DECT phone Datasets 185

6.10.9 Selecting Columns 186

6.10.10 Filtering DECT phone Table 186

6.10.11 Changing the Relation Type 186

6.10.12 Enabling / Disabling DECT phone Event Log 187

6.10.13 User Monitoring 187

6.11 “Conference rooms” Menu 188

6.11.1 Creating Conference Rooms 188

6.11.2 Configuring Conference Rooms 189

6.11.3 Deleting Conference Rooms 189

6.11.4 Viewing Conference Room Details 190

6.12 “ALARM TRIGGERS” MENU “System features” Menu 190

6.12.1 “General settings” Menu 190

6.12.2 “Feature access codes” Menu 191

6.12.3 “Alarm triggers” Menu 191

6.12.4 “Digit treatment” Menu 193

6.12.5 “Directory” Menu 194

6.12.6 Easy migration from corporate Directory (comp. mode) to new corporate Directory structure 196

6.12.7 “Directory (comp. mode)” Menu 197

6.12.8 “XML applications” Menu 199

6.12.9 “CoA Profiles” Menu 203

6.13 “Licenses” Menu 204

6.14 “General” Menu 205

6.15 “Help” Menu 206

7 DECT Phone ....................................................................................................................................................208

7.1 Key lock with PIN 208

7.1.1 Maintain the PIN 208

7.1.2 Unlock a locked Mitel 600 DECT phone 208

7.1.3 Setup automatic key lock with PIN 210

8 Configuration and Administration ................................................................................................................211

8.1 IP Signaling and Media Stream 211

8.2 DECT Base Station Synchronization 213

8.2.1 Initial Synchronization Procedure 214

8.2.2 Checking the Synchronization of a Network 215

8.3 DECT Base Station Channel Capacity 215

8.4 Network Infrastructure Prerequisites 216

8.5 SIP-DECT Startup 216

8.5.1 TFTP and DHCP Server Requirements 217

8.5.2 Booting Steps 217

8.5.3 Booter Startup 218

8.5.4 Application Startup 220

8.5.5 RFP LEDs 224

8.6 State Graph of the Start-up Phases 228

8.7 Local DECT Base Station Configuration (OM Configurator) 231

8.7.1 Selecting the Network Interface 232

8.7.2 Adding DECT Base Stations for configuration 232

8.7.3 Scanning for DECT Base Stations 232

8.7.4 Adding DECT Base Stations manually 233

8.7.5 Loading DECT Base Station data from File 233

8.7.6 Editing DECT Base Station configuration data 233

8.7.7 Applying Configuration Changes 236

8.7.8 Factory Reset 236

8.7.9 Saving and Loading a DECT Base Station List 236

8.7.10 Removing DECT Base Station Entries 237

8.7.11 Compatibility with Older SIP-DECT Releases 237

8.8 OMM Configuration and Resource Files 237

8.8.1 Configuration File URL 238

8.8.2 Specific Configuration URLs 240

8.8.3 ReLoad of Configuration and Resource files 240

8.8.4 AXI Commands in Configuration Files 241

8.8.5 User Configuration Files 243

8.8.6 Digest Authentication and Certificate Validation 245

8.8.7 DECT base station software Image from RFP OMM 246

8.8.8 Redirection and Configuration Service (RCS) 246

8.8.9 Customer Logo on OMM Web Service 247

8.9 DECT Base Station Configuration Files 247

8.9.2 Standard IP settings 248

8.9.3 Configuration file source 248

8.9.4 Parameter settings priority 249

8.9.5 Software update settings for 3rdgeneration DECT base stations 249

8.9.6 SOFTWARE UPDATE SETTINGS FOR 4th GENERATION DECT BASE STATIONS 249

8.9.7 Times when RFP configuration times are read 249

8.9.8 RFP configuration file update check 250

8.9.9 Handling of parameter changes 251

8.9.10 Configuration file syntax 251

8.10 Consolidated Certificate management 253

8.10.1 SIP over TLS certificates 253

8.10.2 OMM Certificate (Web service / AXI) 253

8.10.3 Provisioning certificates 253

8.10.4 Certificate validation 254

8.11 3rdand 4thGeneration RFP Software Update 254

8.12 802.1Q Support 254

8.12.1 Boot Phase of IP RFPs (DHCP) 255

8.12.2 Boot Phase of IP RFPs (Local Configuration) 256

8.13 Installing OMM in Host Mode 256

8.13.1 System Requirements 256

8.13.2 Installing the OMM Software 256

8.13.3 Configuring the Start Parameters 257

8.13.4 Specific Commands – Troubleshooting 258

8.14 Updating the OMM 258

8.14.1 Updating a Single OMM Installation 259

8.14.2 Updating a Standby OMM Installation 259

8.15 OMM Standby 261

8.15.1 Configuring OMM Standby 261

8.15.2 Fail Over Situations 261

8.15.3 Failover Failure Situations 262

8.15.4 Specific standby situations 263

8.16 User data synchronization (MiVoice 5000 dual homing support) 264

8.16.1 Roaming 265

8.16.2 Setting up user data synchronization 266

vii

8.16.3 User data synchronization modes 267

8.17 Managing Account Data for System Access 269

8.17.1 Account Types 269

8.17.2 Potential Pitfalls 270

8.18 WLAN Configuration 270

8.18.1 WLAN configuration steps (RFP 42 WLAN / RFP 43 WLAN only) 270

8.18.2 WLAN configuration steps (RFP 48 WLAN) 271

8.18.3 Optimizing the WLAN 273

8.18.4 Securing the WLAN 275

8.19 SNMP Configuration 275

8.20 Backup SIP Proxy/Registrar 276

8.20.1 REGISTER Redirect 276

8.20.2 DNS SRV 277

8.20.3 Backup SIP Servers 278

8.20.4 Keep Alive Mechanism 280

8.20.5 Prioritized Registration 280

8.20.6 Monitoring the SIP Registration Status 281

8.20.7 Configurable User Account for Standby Check 281

8.20.8 OMM Standby Enhancement 281

8.21 Conferencing 282

8.21.1 Centralized Conferencing 283

8.21.2 Integrated Conference Server (ICS) 283

8.21.3 Configure conference rooms 285

8.22 Download Over Air 288

8.22.1 How “Download Over Air” Works 288

8.22.2 How to configure “Download Over Air” 289

8.23 Central DECT Phone Configuration Over Air (CoA) 291

8.23.1 Configuration files 291

8.23.2 Configuration file download to DECT phones 292

8.23.3 CoA Configuration using OMP 293

8.23.4 Configuration using usr_common.cfg/<user>/cfg Files 293

8.23.5 Variable lists 294

8.24 Extended DECT Phone Interface 299

8.25 OMM/DECT Phone Lock with Branding ID 301

8.25.1 Subscribing the DECT Phone 301

8.26 Device Placement 301

8.26.1 “Placement” View 301

8.26.2 “DECT Base Stations” View 302

8.26.3 “Image management” View 303

8.27 Monitoring with USB Video Devices 305

8.27.1 Configuration of a video user account 305

8.27.2 Configuration of USB video devices 306

8.27.3 Monitoring with USB video devices 306

8.28 Terminal Video 306

8.28.1 Technical Details 307

8.28.2 OMP Configuration Steps 307

8.28.3 Camera Selection via DECT phone Menu 307

8.29 User Monitoring 307

8.29.1 Overview 308

8.29.2 Status Attributes and Validation Mechanisms 309

8.29.3 Escalation 312

8.29.4 Alarm Triggers 312

8.29.5 OM Locating Application 313

8.29.6 Licensing and System Capacities 313

8.29.7 Configuration 313

8.29.8 Start and Failover 315

8.29.9 Supported DECT phones 316

8.29.10 Restrictions 317

8.30 SRTP 317

8.31 SIP over TLS 318

8.31.2 Certificates 319

viii

8.31.3 Private Key 320

8.31.4 TLS Transport Mode 320

8.31.5 Verification of Remote Certificates 321

8.31.6 Additional Security Considerations 321

8.32 DECT Enhanced Security 322

8.33 Migration of RFP SL35 IP from SIP-DECT Lite 3.1 to SIP-DECT 6.1 322

8.34 802.1x Certificate Based Authentication 323

8.34.1 802.1x Configuration 324

8.34.2 Prerequisites Referring to 802.1x Topology 325

8.34.3 802.1x Feature Description 325

8.35 802.1x Certificate Server Configuration 330

8.36 Initiate 802.1x by DHCP Options or OM_Configurator 331

8.36.1 DHCP Options 331

8.36.2 OM_Configurator 331

9 Maintenance ....................................................................................................................................................332

9.1 Site Survey Measurement Equipment 332

9.2 Checking the Mitel Handset Firmware Version 332

9.3 Diagnostic 332

9.3.1 Mitel DECT Phone Site Survey Mode 332

9.3.2 Mitel Handset Auto Call Test Mode 333

9.3.3 Mitel Handset Auto Answer Test Mode 333

9.3.4 Syslog 334

9.3.5 SSH user shell 335

9.3.6 Core File Capturing 339

9.3.7 DECT Monitor 340

10 Regulatory Compliance and Safety Information (4th Generation Dect Base Stations) ..........................344

11 Safety Information (3rdGeneration Dect Base Stations) ............................................................................345

11.1 CE Marking 345

11.2 Communications Regulation Information 345

11.2.1 FCC Notices (U.S. Only) 345

11.3 Health and Safety 346

11.3.1 Exposure to Radio Frequency (RF) Signals: 346

11.3.2 Industry Canada (Canada only) 346

11.4 Informations réglementaires en matière de communications 346

11.4.1 Notes FCC (USA uniquement) 347

12 Appendix .........................................................................................................................................................348

12.1 Pre-Configuration File Rules 348

12.2 DECT phone Configuration File (OMM Database) 348

12.2.1 Supported Instructions 348

12.2.2 Data Section Fields 349

12.2.3 Example 350

12.3 RFP Configuration File / Central (OMM Database) 353

12.3.2 RFP Configuration File / Local (OM Configurator) 356

12.4 RFP Export File Format 360

12.5 CoA Configuration Parameters 362

12.5.1 Configuration of Variable Lists 362

12.5.2 Extended COA Examples 363

12.5.3 Example 1 363

12.5.4 Example 2 363

12.5.5 Example 3 367

12.5.6 Example 4 367

12.5.7 Example 5 369

12.5.8 Supported COA Parameters 370

12.6 Protocols and Ports 398

12.7 Abbreviations 400

12.8 Definitions 401

12.9 References 403

SIP-DECT OM System Manual

1 OVERVIEW

This document describes the installation / configuration, administration, and maintenance of the SIPDECT solutions. Please also see the documents listed in the References section (section 12.9) for additional details on different aspects of the SIP-DECT system.

For a list of abbreviations and definitions, see the appropriate sections in the Safety Information.

1.1 THE SIP-DECT SOLUTION

The SIP-DECT solution includes the following main components:

SIP-DECT base stations that are distributed over an IP network and offer DECT, WLAN, and IP interfaces

DECT phones (portable DECT devices) OpenMobility Manager (OMM): Management and signaling software for the SIP-

DECT solution, which runs on one of the DECT base stations or on a dedicated Linux server (for large installations). In addition, a standby OMM can be configured to ensure OMM function in case of failure or loss of network connection.

A SIP Call Manager/IP PBX/Media Server platform (e.g. Asterisk) 001-omm-arch.psd/.

The IP PBX/media server/media gateway, OMM and the RFPs communicate through the IP infrastructure. The RFPs and the DECT phones communicate over the air, where the DECT GAP protocol or DECT GAP with proprietary enhancements is used.

The SIP-DECT solution supports seamless handover between RFPs which are in a group of synchronized RFPs (cluster) and roaming between RFPs on remote sites.

Additional components include:

LDAP server to facilitate a central corporate directory Provisioning server to provide RFP configuration or user data files Data backup server to automatically backup an OMM database from the server OM Locating server and clients to run the SIP-DECT locating solution 3rd party messaging or alarm server to integrate the SIP-DECT text messaging into

a unified messaging or alarm environment Computer for administration and maintenance tools: Web browser, OM

Management Portal (OMP), DECT Monitor

Figure 1 Architectural Overview of the SIP-DECT Infrastructure and Features

1.2 ABOUT DECT BASE STATIONS

Overview

DECT base stations are also referred to as Radio Fixed Parts (RFPs) in this document.

1.2.1 DECT BASE STATION FAMILIES

1.2.1.1RFP 4G DECT Base Station family

As of SIP-DECT 8.0, SIP-DECT supports the 4thbase station generation (RFP 4G). This 4thRFP generation comprises of:

RFP 44 DECT RFP as indoor model with 4 narrow band voice channels and internal antennas.

RFP 45 DECT RFP as indoor model with 8 narrow band voice channels and internal antennas.

RFP 47 (Indoor Unit) DECT RFP as indoor model with 8 narrow band voice channels and 2 SMA connectors for external directional antennas.

RFP 47 DRC (Outdoor Unit) RFP 47 pre-installed with directional antennas and 3m cable in an outdoor enclosure.

RFP 48 DECT RFP with 8 narrow band voice channels + WLAN Access Point as indoor model with internal antennas for DECT and WLAN.

The hardware of all the RFPs complies with the different regulatory domains. There are no specific hardware variants required to use specific frequency bands and field strengths. Transmit Power, frequency band and carrier frequencies are controlled by software.

SIP-DECT OM System Manual

Configuration

Button

1 RFP 44/45/47/48 (1 LED)

2 Configuration Button

3 100Mbit/s Ethernet Interface, PoE (RFP 44, 45, 47)

4 1Gbit/s Ethernet Interface, PoE (RFP 48)

RJ45 Ethernet Interface

(PoE)

Overview

Differences compared to the previous 3rdRFP family (RFP 35, 36, 37 IP and RFP 43 WLAN) are:

RFP 48 supports 5GHz WLAN according to 802.11ac and 3x3 MIMO Configuration button

- switch to SIP-DECT with Cloud-ID mode

- reset RFP to factory defaults Separate outdoor enclosure available for outdoor usage No external power supply (PoE only) No USB interface RFP 44/45/ support 100MBit/s Ethernet only, The RFP 48 supports 1 GBit/s Boots from internal flash memory instead of net-boot (SIP-DECT software is already

on board) Software update via TFTP, FTP(S), HTTP(S), SFTP supported Hardware can support Secure SIP and SRTP (with SIP-DECT 5.0 or later) Supports CAT-iq 1.0 level high definition voice for the Mitel 650 DECT phone

There are no differences regarding the SW update process compared with the 3rd RFP generation, except a SW update through USB is not possible; because, the RFP 4G does not come with a USB interface.

The RFP 47 RF output is provided through 50 ohm SMA–type connectors. These are electrically compliant with old external antennas, although might not fit mechanically to some antenna cabling.

It is the responsibility of installers to propose connecting solutions according to the installations. For that, a 50 ohm / 3Ghz coaxial adapter is required, which will link the RF output connectors of RFP47 to the existing DECT antenna infrastructure.

1.2.1.2 RFP 3G DECT Base Station Types

Mitel offers four types of RFP 3G DECT base stations for the SIP-DECT solution:

RFP 35 IP DECT RFP as indoor model

RFP 36 IP DECT RFP as outdoor model with built-in dipole antennas

RFP 37 IP DECT RFP as outdoor model with connectors for external directional antennas

RFP 37 DRC (Set) DECT RFP, preinstalled with directional antennas and 3m cable in an outdoor enclosure

RFP 43 WLAN

DECT RFP + WLAN Access Point as indoor model with internal antennas for DECT and WLAN

As of SIP-DECT 6.0, there is no distinction between DECT base station soft brands (that is, L-RFPs and non-L-RFPs). See section 3.3.2 for more information.

SIP-DECT OM System Manual

In general the RFP 35 / 36 / 37 IP have the same hardware platform and software capabilities. RFP 43 supports WLAN in addition to DECT.

1 Power 48V DC (optional)

2 1GBit/s Ethernet (PoE)

3 USB

4 DECT antenna connector (RFP 37 IP)

5 Antennas (RFP 37 IP)

The hardware of all the new RFPs complies with the different regulatory domains. There are no specific hardware variants required to use specific frequency bands and field strengths. Transmit Power, frequency band and carrier frequencies are controlled by software.

Other differences compared to the previous RFP family (RFP 32/34 IP and RFP 42 WLAN):

Boots from internal flash memory instead of net-boot (SIP-DECT software is already on board)

Supports software update through TFTP, FTP(S), HTTP(S), SFTP Supports 1GBit/s Ethernet Supports CAT-iq 1.0 level high definition voice for the Mitel 650 DECT phone Hardware can support Secure SIP and SRTP (with SIP-DECT 5.0 or later) Uses an external 48V DC Power Supply (if no PoE available) which meets the latest

environmental requirements (RFP 37: PoE only) RFP 43 WLAN supports the 802.11a/b/g/n standards Indoor RFPs have a USB 2.0 interface to connect external hardware for future

applications (for example, Video Camera)

1.2.1.3Older RFP Types

Older RFP models supported by the SIP-DECT solution include:

RFP 32 IP DECT RFP as indoor model

RFP 34 IP DECT RFP as outdoor model

Overview

RFP 42 WLAN DECT RFP + WLAN Access Point as indoor model

The RFP 32 and RFP 34 have the same hardware and software capabilities. Please note the regulatory differences between North America and other areas of the world. These differences lead to different RFP 32/34 variants which use specific frequency bands and field strengths:

RFP 32 NA or RFP 34 NA (NA)

– Frequency Band 1920 to 1930 MHz – 5 carrier frequencies – Transmit Power 20 dBm

RFP 32 IP or RFP 34 IP (EMEA)

– Frequency Band 1880 to 1900 MHz – 10 carrier frequencies – Transmit Power 24 dBm

The RFP 42 WLAN is only available for the EMEA region.

RFP 32 IP / RFP 32 NA

RFP 34 IP / RFP 34 NA

1 Power jack (120 V/230 V AC adapter)

2 Ethernet jack; Power supply in line with Power over Ethernet standard IEEE 802.3af

RFP 42 WLAN

As of SIP-DECT 6.0, there is no distinction between RFP soft brands (i.e., L-RFPs and non-L-RFPs). With SIP-DECT 5.0 and older releases, the “L” variants have built-in licenses. See section 3.3.2 (Licensing) for more information.

Note: The software package for previous RFPs has a tftp extension

e.g. “iprfp2G.tftp. With SIP-DECT 3.0 or higher, you need a 3G RFP to run the Open Mobility Manager.

SIP-DECT OM System Manual

1.2.2 OPENMOBILITY MANAGER (OMM) MODE

If the OMM is not running on a dedicated Linux server, one RFP within a SIP-DECT installation must be declared to operate as the OpenMobility Manager (OMM). The RFP acting as the OMM may also act as a regular RFP if it is part of a DECT cluster.

In OMM mode, an RFP functions as a regular RFP. Additionally, it is responsible for SIP signaling between the SIP-DECT system and the IP PBX/SIP server. Further on, it takes over the management part of the SIP-DECT solution. You designate an RFP as the OMM by assigning an IP address to the RFP within the DHCP scope (see section 8.5) or by setting the data via the OM Configurator (see section 8.7). After an RFP is designated as the OMM, it starts the extra services on board (for example, the web service that supports the management interface). All RFPs download the same firmware (for their RFP type), but only one RFP (or two, in standby implementations) activates the OMM services.

Note: It is possible to deactivate the DECT part of an RFP. If the DECT

interface is deactivated, all resources (CPU and memory) are available for the OMM. This might be necessary, for example, in configurations where a mix of OpenMobility Manager, G.729/Conferencing and WLAN is provided by the same RFP.

1.3 ABOUT THE OPENMOBILITY MANAGER

The OpenMobility Manager (OMM) requires an RFP 35/36/37 IP resp. RFP 43 WLAN, or a dedicated Linux server.

There is only one OpenMobility Manager (OMM) active in the system at a given time.

If the OMM runs on a DECT base station, a 100 Mbit/s network link is required. If the OMM runs on a dedicated Linux server, a 1 GBit/s network link is required

(see also section 8.13.1).

In addition, a standby OMM can be configured to ensure the OMM function in case of failure or loss of network connection. For more information on the standby OMM see section 8.15.

1.3.1 OMM TASKS

The OMM performs the following tasks:

Signaling gateway (SIP <-> DECT) Media stream management Managing sync-over-air functions between RFPs Provides a Web service for system configuration Provides additional services such as

– LDAP based central corporate directory – OM Application XML interface (OM AXI) for OAM&P,

messaging, alerting service and locating – Integrated Messaging and Alerting Service (OM IMA) – Data backup and provisioning services

– SIP-DECT XML terminal interface. This interface adapts the “XML API

for SIP Phones“ to SIP–DECT phones. The Mitel 600 DECT phone family is

supported.

Overview

Additional information on the following functionality is available in separate documents.

Locating: See the SIP-DECT OM Locating Application Administration Guide. Integrated Messaging and Alerting Service: See the SIP-DECT OM Integrated

Messaging and Alerting Application Guide and the SIP-DECT Mitel 600 Messaging and Alerting Applications Guide.

User data provisioning: See the SIP-DECT OM Handset Sharing and Provisioning Guide.

Administration and monitoring by third party applications: See the OM Application XML Interface Specification.

SIP-DECT XML terminal interface: See the SIP-DECT XML Terminal Interface Specification.

1.3.2 SIP-DECT SPECIAL FEATURES AND CAPABILITIES

Feature GAP 142d 600

Large DECT Systems (XXL) No connection handover

beyond 256 RFPs

Messaging & Alerting no no yes

Initiate Alarm Trigger *, # feature access code

procedure, no sensor alarm

yes yes

*, # feature access code procedure, no sensor alarm

yes

Locating yes yes yes

DECT XQ no no yes

SIP-DECT OM System Manual

Feature GAP 142d 600

UTF-8 and alphanumeric dialing

no no yes

support

SIP-DECT XML terminal API no no yes

CAT-iq 1.0 / Hi-Q™ audio

no no yes (650 only)

technology

1.3.3 OMM CAPACITIES AND FEATURES

The following table summarizes OMM capabilities:

Feature Release 3.0 or later Release 6.0 or later

RFP OMM Linux server

OMM

RFP 32/34/35/36/37/44/45/47 IP and

256

2048

RFP 42/43/48 WLAN

Handsets / users 512 4500 512/1024

Message / Alarm receive yes / yes

yes / yes

Message send yes yes yes yes

Locating yes

yes

DECT XQ yes yes yes yes

RFP OMM Linux server

256

yes / yes

yes

OMM

4096

10000

yes / yes

yes

UTF-8 and alphanumeric dialing support yes yes yes yes

SIP-DECT XML terminal API yes yes yes yes

CAT-iq 1.0 / Hi-Q™ audio technology yes

The feature requires a license.

The feature is available with the RFP 35/36/37/44/45/47 IP and RFP 43/48 WLAN and the Mitel 650

yes

DECT phone (or other CAT-iq-capable devices). The feature is enabled per site and requires that the RFPs are configured in the same site and cluster.

Release 8.0 or later: If RFP 4G runs as OMM, 1024 users/handsets are supported.

1.3.4 OMM CAPACITIES AND RFP SUPPORT

The following table summarizes OMM and RFP support capabilities:

Feature As of SIP-DECT 6.0 As of SIP-DECT 8.0

RFP 32/34 IP and RFP 42 WLAN

RFP 35/36/37 IP and RFP 43 WLAN

RFP OMM Linux server

OMM

256 4096 256 4096

RFP OMM Linux server

OMM

RFP 44/45/47 IP and RFP 48 WLAN

Not applicable

256 4096

Feature As of SIP-DECT 6.0 As of SIP-DECT 8.0

Overview

RFP OMM Linux server

OMM

DECT phones / users 512 10000 1024 (RFP 4G

RFP OMM Linux server

OMM

10000

OMM) 512 (RFP 3G

OMM)

1.4 ABOUT DECT PHONES

DECT Phones (formerly referred to as Portable Parts) are an integral part of the SIP-DECT solution. Mitel provides the following DECT phones:

Mitel 142 DECT Phone Mitel 600 DECT Phone series

– Mitel 612 DECT Phone – Mitel 622 DECT Phone – Mitel 632 DECT Phone – Mitel 650 DECT Phone

Notes on the Mitel 600 DECT Phones

The Mitel 600 DECT phones support both the NA and EMEA regulatory requirements. The latest Mitel 600 firmware release has the following characteristics:

New user interface e.g. new dial editor with alphanumerical and always en-bloc dialing

Support of UTF-8 in over the air signaling with the OMM Digit and alphanumeric dialing Support of SIP-DECT XML terminal interface Support of microSD card to save subscription data and the most important local

device data (not supported by Mitel 600 DECT phones) Additional subscription options Additional alarm melodies

Profile indication in idle display For more details please see /31/and /32/. In addition to the existing Mitel 600 DECT phone set, the new Mitel 650 DECT phone supports CAT-iq

1.0 and thus supports G.722 (wideband) voice connections. For the full experience of wideband audio, the DECT phone hardware (e.g., speakers, microphone, and processor) has been improved.

The Mitel 600 DECT phone also supports DECT enhanced security.

1.5 FILE NAMING CONVENTIONS

The following table lists the file names for SIP-DECT software deliverables.

SIP-DECT OM System Manual

Software package As of SIP-DECT 7.1 As of SIP-DECT 8.0

Software image for RFP 32/34 IP / RFP 42 WLAN omm_ffsip.tftp iprfp2G.tftp

Software image for RFP 35/36/37 IP / RFP 43 WLAN iprfp3G.dnld iprfp3G.dnld

Software image for RFP 44/45/47 IP / RFP 48 WLAN Not applicable Iprfp4G.dnld

OMM software for Linux Red Hat server (selfextracting executable)

OMM software rpm

DECT phone software rpm SIP-DECT-HANDSET-

SIP-DECT OMM/MOM OVA SIP-DECT-<version>.ova SIP-DECT-<version>.ova

SIP-DECT_<version>.bin SIP-DECT_<version>.bin

SIP-DECT-OMM<version>.i686.rpm

<version>.i686.rpm

SIP-DECT-OMM<version>.i686.rpm

SIP-DECT-HANDSET<version>.i686.rpm

1.6 LOGIN AND PASSWORDS

The following table summarizes the default login and passwords for SIP-DECT system components.

Interface/Tool SIP-DECT OMM

SDC OMM

Initial configuration through OM Configurator login / password (no previous connection with the OMM)

Initial OMM configuration through Web or OMP standard full-access account login / password

n/a No login required “omm” / “omm”

“omm” / “omm” “omm” / “omm”

RFP 32/34 IP / RFP 42 WLAN

n/a n/a

RFP 35/36/37 IP / RFP 43 WLAN RFP 44/45/47 IP / RFP 48 WLAN

OMM access through Web or OMP (after initial OMM configuration)

Configuration through OM Configurator after connection with OMM login / password (system-wide set by OMM)

ssh (no previous connection with the OMM)

ssh (with previous connection with the OMM) (system-wide set by OMM)

Read-only or fullaccess accounts as configured

n/a OMM standard full-

n/a User shell:

n/a n/a

access account login / password

“omm” / “omm” Root shell:

“root” / “22222”

OMM standard fullaccess account login / password

Root shell: as configured

OMM standard full-access account login / password

User shell: “omm” / “omm”

Root shell: “root” / “22222”

User shell: OMM standard full-access account login / password

Root shell: as configured

Enhanced Feature Overview

2 ENHANCED FEATURE OVERVIEW

A SIP-DECT system can scale from a small system of five or less DECT base stations to a larger SIPDECT system that may include hundreds of DECT base stations. Some of the more advanced features target larger DECT systems. You may browse the following list of features in order to get an overview and to decide if it’s relevant for your requirements. You find in-depth explanations in the referenced sections.

Please note: Be aware that the majority of the new enhanced features require the current

DECT phone firmware release. It is assumed that SIP-DECT installations are configured to perform an automatic firmware update over the air.

2.1 PC-BASED OMM INSTALLATION

A very large number of DECT base stations or a large number of DECT phones may exceed the storage capacity or processing power of the embedded DECT base station. For this reason, it is also possible to operate the OMM on a standard PC under the Linux operating system (see section 8.13).

As of SIP-DECT 5.0, CentOS 6 and virtualized environments (VMware vSphere ESXI 5 and 6) are also supported. SIP-DECT 6.1 is tested with CentOS 6.x.

As of SIP-DECT 7.1, CentOS 7 is required. An OVA-File is distributed together with the software for usage within virtualized environments (VMware vSphere 6.5). The verification is executed with VMware vSphere 6.0 and 6.5. For further information, see document /47/ SIP-DECT_LinuxServerInstallation.

2.2 DECT XQ

The DECT radio communication generally suffers from attenuation and radio wave reflection. In particular, if a building’s walls and ceilings contain a higher portion of metal-based material or if larger metal surfaces are present, the DECT XQ improves the radio communication between a DECT base station and a Mitel 600 DECT phone at the expense of DECT channel capacity (see 8.3). Enable this feature for some or all of your DECT base stations (see section 5.6.3, “DECT settings” or section 6.7.1.2, “DECT tab”).

DECT XQ audio cannot be combined with Hi-Q audio within the same connection. There are three operating modes related to audio quality available on the Mitel 650 DECT phone:

standard audio, Hi-Q audio and automatic.

In Hi-Q audio mode, a Mitel 650 DECT phone exclusively establishes wideband

connections and does not switch to narrowband later. A Mitel 650 in this mode

ignores the XQ capability of the RFP.

In standard audio mode, a Mitel 650 DECT phone exclusively establishes

narrowband connections and does not switch to wideband later. A Mitel 650 in this

mode will switch to DECT XQ and back as necessary.

In automatic mode, the connection establishment depends on whether the current

base provides DECT XQ or not. If DECT XQ is available, a narrowband connection

will be established. Otherwise, a wideband connection will be established.

SIP-DECT OM System Manual

2.3 WIDEBAND (CAT-IQ 1.0 / MITEL HI-Q™ AUDIO TECHNOLOGY)

In conjunction with the RFP 35/36/37/44/45/47 IP and RFP 43/48 WLAN, the Mitel 650 DECT phone can act as a Mitel Hi-Q audio terminal. This feature is realized using wideband speech according to CAT-iq.

Each Hi-Q connection uses twice the capacity on the DECT air interface, as compared to conventional narrowband. Therefore, four Hi-Q connections can be established via one RFP, instead of eight narrowband calls.

Mitel Hi-Q audio technology must be enabled or disabled per site (see section 5.5). This functionality must be homogeneously available among synchronous RFPs (members of the same cluster). Each site with enabled Hi-Q audio must exclusively contain new RFP 35/36/37/44/45/47 IP or RFP 43/48 WLAN.

Typically one site is identical with one cluster, i.e. all RFPs belonging to a specific site belong to a specific cluster. However a site can have more than one cluster. The OMM allows configuration of a cluster that contains multiple sites. Such configuration could annul the rule that Hi-Q audio must be homogeneously available among synchronous RFPs.

Please note: It is strongly recommended not to setup systems with multiple sites within one

cluster.

2.4 DECT ENHANCED SECURITY

In response to market concerns, the DECT standard has introduced improvements to security. Many security features, which were specified in the DECT standard (respectively GAP) were left optional for the DECT phones. These mechanisms became mandatory with CAT-iq. Almost all of this functionality was present and used within SIP-DECT right from the start.

Furthermore, some new features have been added to GAP:

Encryption of all calls (not only voice calls)

Re-keying during a call

Early encryption Each feature provides an additional security guarantee and is therefore an integral part of the SIP-DECT

solution. The feature set can be enabled or disabled per site, because enhanced security is available with 3rdor

4thgeneration RFPs. Roaming between sites where enhanced security is enabled and disabled respectively should be avoided.

With SIP-DECT 5.0 and later, when DECT enhanced security is enabled, every connection is encrypted – not only voice calls, but also service calls (e.g. list access) or messaging.

Additionally, the cipher key used for encryption during an ongoing call is changed every 60 seconds. Finally, every connection is encrypted immediately upon establishment to protect the early stages of the

signaling such as dialing or CLIP information. DECT enhanced security is only supported with Mitel 602 DECT phones. Older terminals (e.g. 6x0d or

142d) or GAP phones still operate as normal, but do not support the new security mechanisms.

Enhanced Feature Overview

2.5 VOIP ENCRYPTION

To allow secured call connections over unsecured IP infrastructures (e.g. internet), SIP-DECT supports SRTP to encrypt the RTP voice streams and TLS to encrypt the SIP signaling.

These security mechanisms, together with a secured iPBX infrastructure, allow protected call services and ensure:

Authentication

Integrity

Confidentiality

Privacy When a Mitel 600 DECT phone user is involved in a SRTP call, a key icon in the call display indicates

that the media path to the next hop is ciphered. The key icon is only displayed when the connection uses SIP over TLS, SRTP (for 3G RFPs only) and

DECT encryption together for a secure key exchange and a secure media transport.

2.6 MIXED DECT BASE STATION INSTALLATIONS

In sites (or whole systems) with Hi-Q audio disabled, any combination of RFP 32/34 IP / RFP 42 WLAN and RFP 35/36/37 IP / RFP 43/48 WLAN is allowed. Note, however, that some security features are not supported for all DECT base stations (that is, SRTP and enhanced security are supported on 3 generation RFPs only).

RFP SL35 IP support

SIP-DECT supports the RFP SL35 IP after applying the unlock file and the standard SIP-DECT software to the DECT base station.

Before the standard SIP-DECT software can be installed on the RFP SL35 IP, the unlock.xml file must be available for the DECT base station on the USB. After applying the unlock.xml file the DECT base station accepts the standard SIP-DECT software.

In terms of licensing, the OMM manages the RFP SL35 IP with the unlock file and the standard SIPDECT software like an RFP 35 IP.

For a detailed description see section 8.30.

and 4

2.7 WIRELESS LAN (WLAN)

If you have a number of WLAN DECT base stations (RFP 42/43/48 WLAN), the SIP-DECT system also provides access to your company LAN through Wireless LAN. The RFP 43/48 WLAN support 802.11n. The RFP 48 WLAN also supports 802.11ac. The WLAN configuration of a group of WLAN RFPs is managed by WLAN profiles (see section 5.8).

2.7.1 802.11I: WPA2-ENTERPRISE PRE-AUTHENTICATION FOR FAST ROAMING

WLAN stations (e.g. laptop) which decide to roam to another WLAN access point (AP) must perform the full authentication process with the new AP. In 802.1x (RADIUS) networks this can take a long time resulting in network dropouts during the roam.

SIP-DECT OM System Manual

The AP share authentication information with other APs, so the station can authenticate faster (pre-auth) when roaming to a new AP. This method reduces network dropouts significantly.

The RFP 43 and RFP 48 automatically enables pre-authentication for WPA-Enterprise enabled WLANs. The RFP 42 does not support this feature.

2.7.2 CHANNEL CONFIGURATION FEEDBACK FOR HT40 AND TX POWER

The HT40 channel configuration in 802.11n enabled networks may not always become active because of other access points that use channels that would overlap. In this case, the RFP 43 and RFP 48 fall back to HT20.

From SIP-DECT 5.0 on, the effective channel configuration and the transmit power are reported to the OpenMobility Manager.

You can view these parameters in the OMM Web service and the OMP (DECT base stations > Device

list -> Show details – WLAN tab) and change the channel to a frequency without overlapping APs.

2.7.3 CHANNEL CONFIGURATION FEEDBACK FOR HT80

HT80 includes the HT40/HT20 bandwidth setting. A channel with a bandwidth of 80 MHz occupies 4 WLAN channels with a bandwidth of 20 MHz. If the WLAN profile options HT80/ HT40 MHz have been activated, the necessary center channel will be automatically selected in the corresponding areas by configuration itself.

HT80 is independent from 256 QAM / 3x3 MIMO. The ac standard is the first WLAN standard with 256 QAM modulation and the bandwidth HT80. The n standard supports 3x3 MIMO too, but the RFP43 has only 2 antennas (for 2x2 MIMO) and the RFP48 has 3 antennas.

2.8 DECT BASE STATION SYNCHRONIZATION

To ensure a seamless communication experience, the SIP-DECT system switches an ongoing DECT phone call from one DECT base station to another if the radio communication quality drops below a certain threshold. The seamless handover is possible only if the participating DECT base stations are synchronized. DECT base station synchronization is performed via radio communication between DECT base stations, which in turn requires a decent radio coverage planning (see section 8.2).

2.8.1 CLUSTERING AND PAGING AREAS

Your SIP-DECT system may include different locations, where the distances between the locations prevent the RFPs from performing the over-the-air synchronization. In this case, you must split your network into clusters (or “synchronization domains”). You assign DECT base stations to cluster numbers for this purpose (see section 5.6.3 “DECT settings” or section 6.7.1.2, “DECT tab”). Note that overlap between different clusters on one campus or site must be avoided.

If your SIP-DECT system consists of a very large number of DECT base stations, you should configure the paging area size to optimize the signaling necessary for paging a DECT phone in throughout the SIP-DECT system (see 6.7.2).

A separate cluster number is also required for a remote site (e.g., for a single DECT base station servicing an office abroad). Also, if the VPN network connection to the isolated site’s DECT base station cannot transport DHCP, you may use static IP address configuration for the single DECT base station (see section 8.7.6).

Enhanced Feature Overview

2.9 DECT BASE STATION RESET TO FACTORY SETTINGS

A DECT base station can be reset to factory settings using a USB flash drive with a file on it named “factoryReset”. When the USB flash drive is plugged into the DECT base station, the DECT base station is reset to factory settings automatically. The file is automatically removed from the USB flash drive during this process.

You can also reset the base station to default settings using the OM Configurator or the OMM Web service (see section 8.7.8).

2.9.1 RFP4G RESET TO FACTORY DEFAULTS

To reset to factory defaults, do the following:

1. Use the configuration button to reset the RFP to factory defaults. After the reset to factory defaults, the RFP operates in the standard SIP-DECT mode.

2. Press the Configuration button to start the configuration process. The LED starts flashing green which indicates that the button is pressed.

3. Keep the button pressed until it starts flashing red (10 sec < t < 15 sec).

4. Release the button while the LED is flashing red to reset the RFP to factory defaults.

5. The RFP performs a reset to factory defaults and reboots. After reboot the RFP is started in the standard SIP-DECT mode.

Note: If the button is pressed until it is flashing green, then the button has no effect.

SIP-DECT OM System Manual

2.10 SYSTEM REDUNDANCY

The SIP-DECT solution offers a number of features to support system robustness and redundancy.

2.10.1 OMM STANDBY

The OMM is the central management entity in a SIP-DECT system and therefore constitutes a single point of failure. It is possible to automatically transfer the OMM function to a second DECT base station in case of failure or loss of network connection (see section 8.15).

In an OMM standby implementation, it could happen in rare cases that both OMMs become temporarily active. In such a situation, all SIP-DECT users are SIP registered from to the configured PBX both OMMs. This can cause problems if the PBX accepts only one registration per user (non-forking proxy).

To prevent this scenario, SIP-DECT has a mechanism to detect situations with two active OMMs. When such a situation is detected, the remaining active OMM will SIP re-register all users to the PBX.

This mechanism can be enabled/disabled through the “SIP reRegister after 2 active OMM failover” parameter in the OMP System -> SIP-> Supplementary Services menu (see section 5.4.3.6)

2.10.2 BACKUP SIP PROXY/REGISTRAR

To increase the operational availability of the system in critical environments like hospitals, the OMM offers a new failover mechanism for the SIP server. Therefore, in addition to the primary proxy, outbound proxy and registrar server, it is possible to configure two additional levels of backup servers named “secondary” and “tertiary” servers (see section 8.20.3).

In addition, a keep-alive mechanism implemented in the OMM allows the automatic failover to secondary/tertiary servers or automatic coming back to primary servers (see section 8.20.4).

2.10.3 CONFIGURABLE USER ACCOUNT FOR STANDBY CHECK

The “Standby OMM” feature of SIP-DECT allows configuration of the user account to be used to check the availability of the iPBX. An availability check starts automatically in fail over situations.

The OMM starts a SIP registration for a specific DECT phone user and sends an OPTIONS request to the configured SIP proxy. If there is an answer, the SIP proxy/registrar is considered reachable and the standby OMM becomes active.

With previous SIP-DECT releases, the OMM used the user account with the lowest phone number for the check procedure. To select a specific user account for this purpose, enable the “Used for visibility checks” flag in the user settings (see section 6.10.4.2).

Please note: The “Used for visibility checks” flag can only be set for one user. The number

for visibility checks is shown under OMP Status -> Users -> Number menu. If the flag is not set for a specific user, the OMM uses the user account with the lowest phone number.

2.10.4 USER DATA SYNCHRONIZATION (MIVOICE 5000 DUAL HOMING SUPPORT)

With SIP-DECT 6.1 and later, SIP-DECT supports MiVoice 5000 dual homing, to ensure that SIP-DECT telephony services survive if the network connection to the OMM goes down. Dual homing is achieved through user data synchronization across all OMMs in the system. Every peripheral OMM propagates changes in user, device, Configuration over Air (CoA) profiles or SARI configuration to a central OMM.

Enhanced Feature Overview

Every OMM in the installation (including the central OMM) can use a standby OMM. AXI is used to distribute configuration changes between the central and peripheral OMMs.

For more information on this feature, see section 8.16.

2.10.5 MULTI-OMM MANAGER FOR OMM-CENTRALIZED MANAGEMENT

With SIP-DECT 7.0 and later, SIP-DECT supports centralized management through the Multi-OMM Manager (MOM).

The Multi-OMM Manager (MOM) is a server application that provides centralized provisioning and user/device data synchronization across multiple SIP-DECT sites within a SIP-DECT system. Additionally, the MOM supports system-wide messaging.

Instead of deploying one OMM with DECT base stations installed at different sites, or deploying DECT base stations and a dedicated OMM at each site, you can create a multi-site SIP-DECT system with local survivability and centralized management capabilities. You deploy OMMs and DECT base stations as a standalone system at each site, but manage the entire SIP-DECT system through the MOM interface.

For more information on this feature, see the Multi-OMM Manager Configuration and Administration Guide.

2.11 SIMPLIFIED LICENSING

With SIP-DECT 6.0 or later, the licensing model is simplified. The system no longer distinguishes between different DECT base station “soft-brands”, and some licenses are deprecated. See section

3.3.2 for more information.

Please note: New license files are not compatible with SIP-DECT 4.0 (or older) systems.

2.12 EXTENDED REGULATORY DOMAIN SUPPORT

SIP-DECT 6.1 enables operation of the SIP-DECT solution in more countries. The SIP-DECT system can be operated in all countries that allow operation of DECT devices with frequency bands and transmit power settings supported by the current SIP DECT phones and base stations. In most cases, this requires different frequency channel and transmit power settings.

This feature is intended mainly for installations on cruise liners, where the SIP-DECT system requires a switch of regulatory domain depending on the actual location of the ship. Such systems are planned and installed based on a site survey with 100mW transmit power. The lower transmit power value is used at all times, independent from the regulatory domain.

A new regulatory domain, 1910-1927MHz_250mW, has been added for South America. You can configure this regulatory domain via the OMP (System -> Basic settings -> DECT tab); see section

6.5.1.2 for configuration details. In addition, a new parameter is introduced to limit the DECT base station transmit power to 100mW,

independent of the active regulatory domain. The active transmit power is sent to the DECT phone when it registers its location with the OMM. The DECT phone adjusts its transmit power to the value received from the OMM.

SIP-DECT OM System Manual

2.13 DECT PHONE FUNCTIONALITY

2.13.1 DECT PHONE DOWNLOAD OVER AIR

The Mitel 600 series DECT Phones can download and upgrade their firmware via DECT over the air. As of SIP-DECT 6.0, the DECT base station software images (iprfp3G.dnld and iprfp4G.dnld) contains

the Mitel 600 DECT phone software. The 3rd generation RFPs can house the SIP-DECT 8.0 OMM as in previous releases. The OMM supports the 2nd, 3rd and 4th generation RFPs. If the DECT base station houses the OMM, the OMM uses this software to update the DECT phones. The DECT base station OMM no longer automatically attempts to load a DECT phone software image from a DECT base station software URL when provided via DHCP or local configuration.

For specific maintenance purposes only, SIP-DECT allows configuration of a URL via the OMM Web service or OMP to use an alternative DECT phone software image (see section 5.4.1.8). The Mitel 600 DECT phone firmware packages are delivered in the “600.dnld” file for the OMM running on a DECT base station.

For large installations using a Linux Server-hosted OMM, a DECT base station software images (iprfp3G.dnld and iprfp4G.dnld) without Mitel 600 DECT phone software is available to reduce network traffic in update scenarios.

The DECT phone firmware packages are included in the OMM installation package for Red Hat Enterprise Linux (RHEL) and CentOS for the Linux server version of the OMM.

Please note: An DECT base station upgrade from SIP-DECT 3.0 to 6.0 or later is not

supported due to the extended DECT base station software image. The 3.0 software does not accept the extended software image.

For large installations using a Linux Server OMM, the DECT base station software images (iprfp3G.dnld and iprfp4G.dnld) without Mitel 600 DECT phone software can be used. This software image supports a direct RFP upgrade from SIP-DECT 3.0 to 6.1.

2.13.1.1 4

Generation RFP houses the OMM

The 4th generation RFPs come with more hardware resources in terms of CPU speed and memory. It is recommended to operate the OMM on a 4G RFP.

Please note: If you move the OMM and you want to keep the existing dynamic user phone

relation which is stored in the OMM DB backup file, then activate the option Preserve user device relation at DB restore in the new OMM. The new OMM restores the relation

between the user and the DECT phone during DB import.

If this option is not set, then all dynamic user gets logged out from their DECT phones when importing the OMM DB into the new OMM.

Enhanced Feature Overview

If the OMM is operated on 4G RFP, then 1024 DECT users and phones are supported. (512 DECT users and phones if the OMM is operated on a 3G RFP).

The 4G RFP comes with the configuration button, which allows to switch to the SIP-DECT with Cloud-ID (SDC) mode. As of SIP-DECT 8.0, a 4G RFP is required to run an SDC OMM.

2.13.2 CENTRAL DECT PHONE CONFIGURATION OVER AIR (COA)

SIP-DECT 6.0 and later supports centralized DECT phone configuration over the air (CoA) for Mitel 602 DECT phones. DECT phone CoA is useful for deployment of special configuration to a single DECT phone or a large number of DECT phones. No local access to the DECT phone is required.

DECT phone CoA is implemented by providing additional configuration information to the well-known configuration files or providing profiles via OMP. Configuration can be changed at the device level (DECT subscription) or the user level (based on login).

Configuration of all DECT phones with a predefined default profile is also supported. Up to 20 possible DECT phone profiles make it easy to adapt to different usage scenarios for heterogeneous user groups (e.g., nurses and doctors in hospital environments). See section 8.23 for more information on this feature.

2.13.2.1 CoA enhancements

The Mitel 602 DECT phone 6.1 firmware (bundled with SIP-DECT release 6.1) includes new features which are configurable via Configuration over Air (CoA).

New configuration commands allow you to overwrite local key programming on the Mitel 602 DECT phones. SIP-DECT 6.1 also supports configuration of the new XML application hooks introduced for the XML terminal interface via CoA (see section 2.32).

In addition, the Mitel 602 DECT phone 6.1 firmware introduces variable lists. A variable list includes a number of items, each of which corresponds to an action to be performed on the DECT phone. For more information, see section 8.23.5.

SIP-DECT OM System Manual

2.13.3 OMM DECT PHONE PROVISIONING

While some users in the SIP-DECT system use a dedicated DECT phone, it is also possible to operate shared DECT phones. The SIP-DECT solution provides an enhanced DECT phone sharing and provisioning concept that enables the management of a large number of DECT phones and provides a flexible subscription model.

The SIP-DECT system allows logging into and out of different DECT phones with a personalized user account, import of user data from an external provisioning server, automatic subscription of new DECT phones, and control of subscription-specific system functions from DECT phones.

See the SIP-DECT DECT Phone Sharing and Provisioning Guide for details on this feature.

2.13.4 MITEL 600 DECT PHONE DIAL EDITOR MODE

It is assumed that most customers use digits only in their dialing plan, and that it is more convenient if dial editors support only the digits 0 to 9, * and #. The Dial editor supports digits only flag (on the OMP (System -> Advanced settings -> DECT Phones tab) enables this mode. In this mode, the * has the meaning of a digit to be merely dialed, even if it short-pressed.

If the mode is not set to digits only, the short pressed * will change the editor mode to alphanumeric.

2.13.5 MITEL 602 DECT PHONE CUSTOMIZABLE BOOT TEXTS

By default, the text shown on the Mitel 600 DECT phone at start up is Mitel-specific (branded in the firmware). Customers can also define their own text (on the OMP (System -> Advanced settings ->

DECT Phones tab).

2.13.6 OMM-CENTRALIZED CALL LOGS

SIP-DECT 7.0 introduces support for OMM-centralized call logs for SIP-DECT systems using the Mitel MX-ONE call server.

The OMM-centralized call log features the OMM manager caller and redial list entries pushed by the MXONE call server for all DECT phones in the system. When this feature is enabled, DECT phone users can access the OMM-centralized call log on their DECT phones using the existing XML hooks for caller list and redial list.

The OMM also handles the “missed call” notifications for the DECT phone. If the number of missed calls changes, the OMM sends the information to the DECT phone.

The OMM sorts the call log entries according to the most recent entry. Call log entries from the same day are listed with the time stamp and older entries are listed with the date stamp.

For information on how to enable OMM-centralized call logs, see section 5.9.5.2 (Modifying an XML Hook via the OMM web service) or section 6.12.8.2 (Modifying an XML Hook via the OMP).

2.13.7 USER INDIVIDUAL DECT PHONE PIN KEY LOCK

2.13.7.1 OMM Key Lock with PIN Management

+ 170 hidden pages

Mitel Networks RFP4445, RFP47DRC User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual