AASTRA SIP-DECT User Manual
SIP – DECT OM System Manual Release 2.1
SIP – DECT
OM System Manual
Installation, Administration, and
Maintenance
Release 2.1
Document ID: depl-1230
Version: 1.3
Aastra Deutschland GmbH Zeughofstr. 1
10997 Berlin, Germany
No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including
photocopying, recording, or information storage and retrieval system, for any purpose without the express written permission of
Aastra.
Aastra depl-1230/1.3 Page: 1 (196)
2010 - All Rights Reserved
SIP – DECT OM System Manual Release 2.1 Table of Contents
Table of Contents
1 OVERVIEW ...........................................................................................................................................6
1.1 THE SIP – DECT SOLUTION..........................................................................................................6
1.2 ABOUT THE RADIO FIXED PARTS (RFPS) ........................................................................................ 7
1.2.1 RFP only Mode...............................................................................................................8
1.2.2 OpenMobility Manager (OMM) Mode .............................................................................9
1.3 ABOUT THE OPENMOBILITY MANAGER............................................................................................9
1.3.1 OMM Tasks ....................................................................................................................9
1.3.2 OMM Capacities and Features.....................................................................................10
1.4 ABOUT THE PORTABLE PARTS ......................................................................................................11
2 GETTING STARTED...........................................................................................................................13
2.1 SETTING UP DHCP / TFTP.......................................................................................................... 13
2.2 INITIAL SETUP..............................................................................................................................17
3 ENHANCED FEATURE OVERVIEW.................................................................................................. 21
4 LICENSING ......................................................................................................................................... 24
4.1 LICENSING MODEL .......................................................................................................................24
4.1.1 Latency Timer...............................................................................................................24
4.1.2 License Violations and Restrictions..............................................................................25
4.2 UPLOADING AN ACTIVATION OR LICENSE FILE ...............................................................................26
4.3 DEMONSTRATION MODE...............................................................................................................26
4.4 LICENSE MODES ..........................................................................................................................26
4.4.1 Built-in License (Small System).................................................................................... 26
4.4.2 Activated Built-in License (Medium System) ................................................................27
4.4.3 Standard License (Large System)................................................................................28
5 OMM WEB SERVICE..........................................................................................................................30
5.1 LOGIN .........................................................................................................................................30
5.2 LOGOUT ......................................................................................................................................31
5.3 “STATUS” MENU ..........................................................................................................................31
5.4 “SYSTEM” MENU ..........................................................................................................................32
5.4.1 “System settings” Menu................................................................................................32
5.4.1.1 Restarting the OMM ..................................................................................................35
5.4.1.2 Updating the OMM ....................................................................................................35
5.4.2 “SIP” Menu....................................................................................................................36
5.4.3 “User account” Menu ....................................................................................................40
5.4.4 “Time zones” Menu.......................................................................................................41
5.4.4.1 Changing Time Zones............................................................................................... 41
5.4.4.2 Resetting Time Zones ...............................................................................................42
5.4.5 “SNMP” Menu...............................................................................................................42
5.4.6 “DB management” Menu ..............................................................................................43
5.4.6.1 Manual Database Import ........................................................................................... 44
5.4.6.2 Automatic Database Import .......................................................................................44
5.4.6.3 Manual Database Export ........................................................................................... 46
5.4.6.4 Automatic Database Export....................................................................................... 47
5.4.7 “Event log” Menu ..........................................................................................................48
5.5 “SITES” MENU .............................................................................................................................48
5.5.1 Creating a New Site......................................................................................................49
5.5.2 Editing a Site.................................................................................................................49
5.5.3 Deleting a Site ..............................................................................................................49
5.6 “RADIO FIXED PARTS” MENU.........................................................................................................49
5.6.1 States of an RFP ..........................................................................................................51
5.6.2 OMM / RFP SW Version Check ...................................................................................52
5.6.3 Creating and Changing RFPs.......................................................................................52
5.6.4 Importing RFP Configuration Files ...............................................................................54
5.6.5 Capturing RFPs ............................................................................................................56
5.6.6 Deleting RFPs ..............................................................................................................56
5.7 “PORTABLE PARTS” MENU............................................................................................................ 56
5.7.1 Creating and Changing PPs.........................................................................................57
5.7.2 Importing PP Configuration Files.................................................................................. 59
depl-1230/1.3 Page: 2 (196)
SIP – DECT OM System Manual Release 2.1 Table of Contents
5.7.3 Subscribing PPs ...........................................................................................................61
5.7.3.1 Subscription with Configured IPEI ............................................................................. 62
5.7.3.2 Wildcard Subscription................................................................................................62
5.7.4 Deleting PPs.................................................................................................................63
5.7.5 Searching within the PP List.........................................................................................63
5.8 “WLAN” MENU............................................................................................................................65
5.8.1 “WLAN profiles” Menu .................................................................................................. 65
5.8.1.1 Creating and Changing WLAN Profiles .....................................................................65
5.8.1.2 Deleting WLAN Profiles ............................................................................................. 70
5.8.2 “WLAN clients” Menu....................................................................................................70
5.9 “SYSTEM FEATURES” MENU..........................................................................................................70
5.9.1 “Digit treatment” Menu..................................................................................................70
5.9.1.1 Creating and Changing “Digit treatment” Entries....................................................... 71
5.9.1.2 Deleting “Digit treatment” Entries .............................................................................. 72
5.9.2 “Directory” Menu...........................................................................................................72
5.9.2.1 Creating and Changing LDAP Servers ...................................................................... 73
5.9.2.2 Deleting LDAP Entries...............................................................................................74
5.9.3 “Feature access codes” Menu ...................................................................................... 74
5.10 “LICENSES” MENU .......................................................................................................................75
5.11 “INFO” MENU ...............................................................................................................................76
6 OM MANAGEMENT PORTAL (OMP) ................................................................................................ 77
6.1 LOGIN .........................................................................................................................................77
6.2 LOGOUT ......................................................................................................................................78
6.3 OMP MAIN WINDOW ...................................................................................................................78
6.4 “STATUS” MENU ..........................................................................................................................79
6.5 “SYSTEM” MENU ..........................................................................................................................80
6.5.1 “System settings” Menu................................................................................................81
6.5.2 “Statistics” Menu...........................................................................................................82
6.5.3 “SIP” Menu....................................................................................................................83
6.5.4 “Data management” Menu............................................................................................84
6.5.4.1 “Automatic DB import” Tab ........................................................................................ 84
6.5.4.2 “Automatic DB export” Tab ........................................................................................ 86
6.5.4.3 “User data import” Tab ..............................................................................................87
6.5.4.4 “Miscellaneous” Tab.................................................................................................. 88
6.6 “SITES” MENU .............................................................................................................................89
6.7 “RADIO FIXED PARTS” MENU.........................................................................................................90
6.7.1 “Device list” Menu.........................................................................................................90
6.7.1.1 RFP Detail Panel....................................................................................................... 92
6.7.1.2 Adding New RFPs..................................................................................................... 94
6.7.1.3 Changing RFPs ......................................................................................................... 95
6.7.1.4 Viewing RFP Details.................................................................................................. 95
6.7.1.5 Deleting RFPs ...........................................................................................................95
6.7.1.6 Showing Synchronization Relations ..........................................................................96
6.7.1.7 Selecting Columns ....................................................................................................96
6.7.1.8 Filtering RFP Table ...................................................................................................96
6.7.2 “Paging areas” Menu ....................................................................................................97
6.7.3 “Enrolment” Menu.........................................................................................................98
6.7.4 “Export” Menu...............................................................................................................99
6.7.5 “Sync view” Menu .........................................................................................................99
6.7.6 “Statistics” Menu.........................................................................................................101
6.7.6.1 RFP Statistics Overview .......................................................................................... 101
6.7.6.2 RFP Statistics Group Panels ................................................................................... 102
6.8 “PORTABLE PARTS” MENU.......................................................................................................... 103
6.8.1 Overview” Menu .........................................................................................................103
6.8.2 “Users” Menu..............................................................................................................105
6.8.3 “Devices” Menu ..........................................................................................................106
6.8.4 PP Detail Panel ..........................................................................................................107
6.8.5 Creating PP Datasets .................................................................................................110
6.8.6 Configuring PP Datasets ............................................................................................111
6.8.7 Subscribing PP Datasets............................................................................................111
6.8.8 Deleting PP Datasets .................................................................................................111
6.8.9 Selecting Columns......................................................................................................112
6.8.10 Filtering PP Table .......................................................................................................112
depl-1230/1.3 Page: 3 (196)
SIP – DECT OM System Manual Release 2.1 Table of Contents
6.8.11 Enabling / Disabling PP Event Log.............................................................................113
6.9 “SYSTEM FEATURES” MENU........................................................................................................113
6.9.1 “General settings” Menu .............................................................................................113
6.9.2 “Feature access codes” Menu .................................................................................... 114
6.9.3 “Alarm triggers” Menu.................................................................................................114
6.9.3.1 Creating “Alarm triggers” .........................................................................................115
6.9.3.2 Configuring “Alarm triggers” ....................................................................................115
6.9.3.3 Deleting “Alarm triggers” ......................................................................................... 116
6.9.3.4 View “Alarm trigger” Details..................................................................................... 116
6.9.4 “Digit Treatment” Menu...............................................................................................116
6.9.5 “Directory” Menu.........................................................................................................117
6.10 “LICENSE” MENU .......................................................................................................................118
6.11 “GENERAL” MENU...................................................................................................................... 118
6.12 “HELP” MENU ............................................................................................................................119
7 CONFIGURATION UND ADMINISTRATION ASPECTS.................................................................121
7.1 IP SIGNALING AND MEDIA STREAM .............................................................................................121
7.2 RFP SYNCHRONIZATION ............................................................................................................ 123
7.2.1 Initial Synchronization Procedure...............................................................................124
7.2.2 Checking the Synchronization of a Network...............................................................125
7.3 RFP CHANNEL CAPACITY ..........................................................................................................125
7.4 NETWORK INFRASTRUCTURE PREREQUISITES .............................................................................126
7.5 SIP – DECT STARTUP .............................................................................................................. 126
7.5.1 TFTP and DHCP Server Requirements ..................................................................... 126
7.5.2 Booting Steps .............................................................................................................127
7.5.3 Booter Startup ............................................................................................................128
7.5.3.1 DHCP Client ............................................................................................................ 128
7.5.3.1.1 DHCP Request........................................................................................................ 128
7.5.3.1.2 DHCP Offer ............................................................................................................. 129
7.5.3.1.3 Retries.....................................................................................................................129
7.5.3.2 TFTP Client .............................................................................................................129
7.5.3.3 Booter Update .........................................................................................................129
7.5.4 Application Startup .....................................................................................................130
7.5.4.1 DHCP Client ............................................................................................................ 130
7.5.4.2 Selecting the Right DHCP Server............................................................................132
7.5.5 RFP LED Status ......................................................................................................... 132
7.5.5.1 Booter LED Status...................................................................................................133
7.5.5.2 Application LED Status............................................................................................ 133
7.6 STATIC LOCAL CONFIGURATION OF AN RFP (OM CONFIGURATOR)..............................................135
7.7 RFP CONFIGURATION FILES ......................................................................................................140
7.8 802.1Q SUPPORT .....................................................................................................................144
7.8.1 Boot Phase of IP RFPs (DHCP).................................................................................145
7.8.2 Boot Phase of IP RFPs (Local Configuration) ............................................................ 145
7.9 INSTALLING OMM IN HOST MODE...............................................................................................146
7.9.1 System Requirements ................................................................................................146
7.9.2 Installing the OMM Software ......................................................................................146
7.9.3 Configuring the Start Parameters...............................................................................147
7.9.4 Specific Commands – Troubleshooting......................................................................148
7.10 UPDATING THE OMM.................................................................................................................148
7.10.1 Updating a Single OMM Installation ...........................................................................149
7.10.2 Updating a Standby OMM Installation........................................................................149
7.11 OMM STANDBY.........................................................................................................................150
7.11.1 Configuring OMM Standby .........................................................................................151
7.11.2 Fail Over Situations .................................................................................................... 151
7.11.3 Fail Over Failure Situations ........................................................................................151
7.11.4 Specific Standby Situations........................................................................................152
7.11.4.1 How A Standby OMM Becomes Active ................................................................... 152
7.11.4.2 Handling When Both OMMs Are Not Synchronized ................................................ 152
7.11.4.3 Two DECT Air Interfaces......................................................................................... 153
7.12 MANAGING ACCOUNT DATA FOR SYSTEM ACCESS ......................................................................153
7.12.1 Account Types............................................................................................................154
7.12.2 Potential Pitfalls ..........................................................................................................155
7.13 WLAN CONFIGURATION (RFP 42 / L42 ONLY) ...........................................................................155
depl-1230/1.3 Page: 4 (196)
SIP – DECT OM System Manual Release 2.1 Table of Contents
7.13.1 WLAN configuration steps .......................................................................................... 155
7.13.2 Optimizing the WLAN .................................................................................................156
7.13.3 Securing the WLAN .................................................................................................... 157
7.14 SNMP CONFIGURATION ............................................................................................................158
7.15 DOWNLOAD OVER AIR ...............................................................................................................158
7.15.1 How “Download Over Air” Works ...............................................................................159
7.15.2 How to configure “Download Over Air”.......................................................................159
8 MAINTENANCE ................................................................................................................................163
8.1 SITE SURVEY MEASUREMENT EQUIPMENT ..................................................................................163
8.2 CHECKING THE AASTRA DECT 142 / AASTRA 142D HANDSET FIRMWARE VERSION ..................... 163
8.3 DIAGNOSTIC ..............................................................................................................................163
8.3.1 Aastra DECT 142 / Aastra 142d Site Survey Mode ...................................................163
8.3.2 Aastra DECT 142 / Aastra 142d Auto Call Test Mode ...............................................164
8.3.3 Aastra DECT 142 / Aastra 142d Auto Answer Test Mode .........................................164
8.3.4 Syslog .........................................................................................................................165
8.3.5 ssh user shell..............................................................................................................166
8.3.5.1 Login .......................................................................................................................166
8.3.5.2 Command Overview................................................................................................ 167
8.3.5.3 OMM Console On Linux Server............................................................................... 167
8.3.5.4 RFP Console Commands........................................................................................ 168
8.3.5.5 OMM Console Commands ...................................................................................... 168
8.3.6 Core File Capturing ....................................................................................................170
8.3.7 DECT Monitor.............................................................................................................170
9 APPENDIX ........................................................................................................................................174
9.1 DECLARATION OF CONFORMITY .................................................................................................. 174
9.2 COMMUNICATIONS REGULATION INFORMATION FOR AASTRA DECT 142 US................................174
9.2.1 FCC Notices (U.S. Only) ............................................................................................174
9.2.2 Industry Canada (Canada only) .................................................................................175
9.3 COMMUNICATIONS REGULATION INFORMATION FOR RFP 32 OR RFP 34 (NA).............................175
9.3.1 FCC Notices (U.S. Only) ............................................................................................175
9.3.2 Industry Canada (Canada only) .................................................................................176
9.4 ABBREVIATIONS .........................................................................................................................177
9.5 DEFINITIONS..............................................................................................................................177
9.6 REFERENCES ............................................................................................................................179
9.7 PRE-CONFIGURATION FILE RULES ..............................................................................................180
9.7.1 PP Configuration File (OMM Database).....................................................................181
9.7.1.1 Supported Instructions ............................................................................................ 181
9.7.1.2 Data Section Fields ................................................................................................. 181
9.7.1.3 Example ..................................................................................................................182
9.7.2 RFP Configuration File / Central (OMM Database).................................................... 183
9.7.2.1 Supported Instructions ............................................................................................ 183
9.7.2.2 Data Section Fields ................................................................................................. 184
9.7.2.3 Example ..................................................................................................................184
9.7.3 RFP Configuration File / Local (OM Configurator) .....................................................186
9.7.3.1 Supported Instructions ............................................................................................ 186
9.7.3.2 Data Section Fields ................................................................................................. 187
9.7.3.3 Example ..................................................................................................................188
9.8 RFP EXPORT FILE FORMAT .......................................................................................................190
9.9 PROTOCOLS AND PORTS............................................................................................................191
10 INDEX................................................................................................................................................193
depl-1230/1.3 Page: 5 (196)
SIP – DECT OM System Manual Release 2.1 1 Overview
1 Overview
This document describes the installation / configuration, administration, and maintenance of
the SIP – DECT solution.
Other valid documentation
Please observe also the information to other parts of your SIP – DECT installation given in
the documents listed in the section entitled References starting on page 179.
Reference
For a list of abbreviations and definitions valid for this manual please refer to the appropriate
chapters in the Appendix starting on page 174.
1.1 The SIP – DECT Solution
The SIP – DECT solution comprises the following main components:
• Aastra SIP – DECT base stations or Radio Fixed Parts (RFPs) being distributed over an
IP network and offering DECT and IP interfaces.
• Portable DECT devices known as handsets, Portable Parts (PP) or just device e.g. Aastra
620d.
• OpenMobility Manager (OMM) : Management and signaling SW for the SIP – DECT
solution, which runs on one of the Radio Fixed Parts or on a dedicated Linux PC (for large
installations).
• A SIP Call Manager/IP PBX/Media Server platform e.g. Asterisk.
The following figure gives a graphical overview of the architecture of the SIP – DECT
wireless solution:
depl-1230/1.3 Page: 6 (196)
SIP – DECT OM System Manual Release 2.1 1 Overview
The IP PBX/media server/media gateway, OMM and the RFPs communicate through the IP
infrastructure. The RFPs and the Portable Parts 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 are:
• 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 on the server or to
automatically import an OMM database into the OMM;
• OM Locating server and clients to run the Aastra 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.
1.2 About the Radio Fixed Parts (RFPs)
Aastra provides 3 types of RFPs for the SIP – DECT solution:
• RFP 32 IP / RFP L32 IP
DECT RFP as indoor model
• RFP 34 IP / RFP L34 IP
DECT RFP as outdoor model
• RFP 42 WLAN / RFP L42 WLAN
DECT RFP + WLAN Access Point as indoor model
In general the RFP 32 and RFP 34 have the same hardware and software capabilities.
Please be aware of the regulatory differences between North America and all 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
depl-1230/1.3 Page: 7 (196)
SIP – DECT OM System Manual Release 2.1 1 Overview
- 5 carrier frequencies
- Transmit Power 20 dBm
• RFP L32 IP or RFP L34 IP (EMEA)
- - Frequency Band 1880 to 1900 MHz
- - 10 carrier frequencies
- - Transmit Power 24 dBm
The RFP L42 WLAN is only available for the EMEA region.
RFP 32 IP / RFP L32 IP / RFP 32 NA RFP L42 WLAN / RFP 42 WLAN
1 Power jack (120 V/230 V AC adapter)
2 Ethernet jack; Power supply in line with Power over Ethernet standard IEEE 802.3af
The difference between L-RFPs (L32 IP / L34 IP / L42 WLAN) and non-L-RFPs (32 IP /
34 IP / 42 WLAN) is that the “L” variants have a build-in license, please see chapter
Licensing for details.
1.2.1 RFP only Mode
Within this mode the RFP converts IP protocol to DECT protocol and then transmits the
traffic to and from the handsets over a DECT time slot. On air the RFP has 12 available time
slots, 8 can have associated DSP resources for media streams. All DECT time slots are used
for control signaling, SW download over air, messaging and bearer handover independent of
associated DSP resources.
2 control signaling channels are also used to carry bearer signals that signal the handset to
start the handover process. If the radio signal of another RFP is stronger than that of the
current RFP, then the handset starts the handover process to the RFP that has the stronger
signal as the user moves around the site.
depl-1230/1.3 Page: 8 (196)
SIP – DECT OM System Manual Release 2.1 1 Overview
Clusters
Groups of RFPs can be built which are named clusters. Within a cluster RFPs are
synchronized to enable a seamless handover when an user crosses from one RFP’s area of
coverage to another. For synchronization it is not necessary for an RFP to see directly all
other RFPs in the system. Each RFP only needs to be able to see the next RFP in the chain.
But it is preferable for an RFP to see more than one RFP to guarantee synchronization in the
event that one of the RFPs fails.
1.2.2 OpenMobility Manager (OMM) Mode
If the OMM shall not run on a dedicated Linux PC then 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 as well if it is included into 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/media 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 chapter 7.5) or by setting
the data via the OM Configurator (see 7.6). 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 from a TFTP server but only one RFP
activates the OMM services.
Note: It is possible to deactivate the DECT part of an RFP. If the DECT interface is
deactivated then all resources (CPU and memory) are available for the OMM.
1.3 About the OpenMobility Manager
The OpenMobility Manager (OMM) runs on one of the RFPs or on a dedicated Linux PC.
There is only one active OpenMobility Manager (OMM) in the system.
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 e.g.
- 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
depl-1230/1.3 Page: 9 (196)
SIP – DECT OM System Manual Release 2.1 1 Overview
rd
party
3
Alarm
Server
LDAP Server
Provisioning/
Database
Backup Server
WEB
service
Call Manager
SIP
OM Integrated
Messaging &
Alerting Service
OMM
3rd party
Message
Server
OM
Locating
Server
OMM Application XML Interface
(OM AXI) for OAM&P* and
other applications
(XML, TCP/TLS)
*OAM&P – Operation, Administration,
aintenance &
M
rovisioning
P
OM Management
Portal
OM Locating Client
...
Additional information on the following topics are available with separate documents.
• Locating: please see the SIP – DECT; OM Locating Application; Installation,
Administration & User Guide /23/.
• Integrated Messaging and Alerting Service: please see the SIP – DECT; OM Integrated
Messaging & Alerting Application; Installation, Administration & User Guide /24/ and the
SIP – DECT; Aastra 610d, 620d, 630d; Messaging & Alerting Applications; User Guide
/25/.
• Integration of SIP – DECT in unified messaging and alarm environments: please see /25/
and the OM Application XML Interface (OM AXI) specification /27/.
• User data provisioning: please see the SIP – DECT; OM Handset Sharing & Provisioning;
User Guide /26/.
• Administration and Monitoring by 3rd party applications: please see the OM Application
XML Interface (OM AXI) specification /27/.
1.3.2 OMM Capacities and Features
The OMM capacities are:
Release 1.8 Release 2.1 or later
RFP OMM Linux PC
OMM
RFP OMM Linux PC
OMM
2
L-RFP
RFP L3x IP and RFP L42 WLAN
Standard RFP
RFP 3x IP and RFP 42 WLAN
256 n.a. 20 n.a.
n.a. n.a. 256
3
2048
3
Handset / user 512 n.a. 512 4500
Message / Alarm receive
n.a. n.a.
depl-1230/1.3 Page: 10 (196)
Yes 2 /
3
Yes
Yes 3 /
3
Yes
SIP – DECT OM System Manual Release 2.1 1 Overview
Release 1.8 Release 2.1 or later
Message send n.a. n.a. Yes
Locating n.a. n.a. Yes
1
available for field trial on request
2
build in license for L-RFP installation; requires a license for standard RFP installations
3
requires a license; not available for L-RFP installations
1.4 About the Portable Parts
Portable Part (PP) is DECT standard terminology and in the context of the SIP – DECT
solution is interchangeable with handset. Aastra provides the following handsets:
Aastra 142d, Aastra 610d / Aastra 620d / Aastra 630d.
Aastra 142d Aastra 610d Aastra 620d Aastra 630d
RFP OMM Linux PC
OMM
RFP OMM Linux PC
2
3
OMM
Yes
Yes
2
3
3
Please be aware of differences in regulatory requirements between North America and all
other areas of the world. These differences lead to different Aastra 142d variants which use
specific frequency bands and field strengths:
• Aastra DECT 142 (NA)
- Frequency Band 1920 to 1930 MHz
- 60 duplex channels
- 100 mW (maximum output per active channel)
- 5 mW (average output per active channel)
• Aastra 142d (EMEA)
- Frequency Band 1880 to 1900 MHz
- 120 duplex channels
- 250 mW (maximum output per active channel)
- 10 mW (average output per active channel)
The Aastra 610d / 620d / 630d supports both the NA and EMEA regulatory requirements.
depl-1230/1.3 Page: 11 (196)
SIP – DECT OM System Manual Release 2.1 1 Overview
In addition to the Aastra DECT 142 / Aastra 142d, standard 3rd party DECT GAP phones
may operate on the SIP – DECT solution. But the functionality may be limited by the
characteristics of the 3rd party DECT phone.
depl-1230/1.3 Page: 12 (196)
SIP – DECT OM System Manual Release 2.1 2 Getting Started
2 Getting Started
This chapter describes how to set up a small SIP – DECT system using two RFP devices,
useable as a small stand-alone DECT telephony system or for evaluation purposes.
Prerequisites
Some hardware and software prerequisites are to be met to follow this quick start guide:
• two licensed RFP devices (RFP L32 IP),
• a PC to run a browser or start java programs,
• a PC-based server for setting up DHCP/TFTP,
• two or more DECT handsets (preferably two Aastra 610d/620d/630d),
• OMM-SIP installation medium with software, such as the “omm_ffsip.tftp” file,
• optional: a VoIP communications system that provides SIP accounts.
You can use any operating system for the PC-based server system that provides a DHCP
and TFTP server. However, the following description details on a Linux system. For testing
and evaluation, you may download and install virtualization software for your workstation,
such as “VmWare Player” or “VirtualBox”. Within a virtual machine, you are able to operate a
Linux system, for example the CentOS, Debian or Ubuntu “Live-CD” ISO files that are
downloadable for free on the respective Linux vendor web sites.
2.1 Setting up DHCP / TFTP
An RFP in the factory default configuration will request the address configuration via DHCP.
While it is possible to configure a fixed (non-DHCP) address for the RFPs (see chapter 7.6),
this description starts with setting up a DHCP server that will answer the DHCP requests.
The DHCP server will be limited to answer only DHCP requests from Aastra RFPs (sorted
out by MAC address), so the new DHCP server will not disturb the operation of possibly
other DHCP servers in your LAN:
Also you need at least a TFTP server that offers the firmware file for the RFP. The IP
address and the firmware file download location is part of the DHCP answer, the RFP
receives during start-up. By using this DHCP-provided configuration, the RFP downloads the
firmware file and starts the software program that is included in the firmware file.
As stated earlier, the PC server system described here is operated by a Linux system. If you
run Linux in a virtual machine, the virtual machine’s network adapter should be configured for
the “Bridged Mode” which allows the virtual machine to receive/answer DHCP broadcasts on
the physical Ethernet adapter.
Activating bridge mode with VirtualBox
depl-1230/1.3 Page: 13 (196)
SIP – DECT OM System Manual Release 2.1 2 Getting Started
Also, you need the firmware file for the RFP inside the virtual machine. You can copy via
network e.g. by using SCP, FTP, SMB etc. To keep things simple, the virtual machine used
in this example has a second CD-ROM that points to the hardware CD-ROM drive that in
turn has the OMM-SIP installation medium inserted.
Second CD-ROM with VirtualBox
The following steps will start the virtual machine where you can configure and run the
DHCP/TFP server program.
1 Start the virtual machine. The Linux desktop should be displayed after start-up. The
following screenshot depicts the situation if you start VirtualBox with a Live CD Linux
(CentOS 5.5 to be precise).
CentOS LiveCD, copy files, calling up a terminal
2 On the virtual machine’s desktop, double click the OMM-SIP CD-ROM. Use drag & drop
to copy the “omm_ffsip.tftp” and “aafon6xdd.dnls” files to the Linux desktop.
depl-1230/1.3 Page: 14 (196)
SIP – DECT OM System Manual Release 2.1 2 Getting Started
3 Start a terminal program. With Gnome desktop, select the Applications: Accessories:
Terminal menu command.
4 In the terminal program, you need to enter the following commands to switch off the
firewall and to start the SSH service:
su -l
ip -4 a
Starts a super user (“root”) shell.
Shows the current network configuration.
The “eth0” adapter should show an IP
address allocated by a DHCP server in your
LAN.
ip a add 192.168.1.1/24 dev eth0
ip l set dev eth0 up
Optional: if the “eth0” adapter has no IP
address, you can assign the address
manually.
/etc/init.d/sshd start
passwd centos
Starts the SSH service.
Set a (simple) password for the “centos”
user.
iptables -F INPUT
Flush (clear) the INPUT firewall.
5 Leave the virtual machine. With VirtualBox press and release the right [Ctrl] key. With
VmWare Player press and release both the left [Ctrl] key and the left [Alt] key. You may
iconize the virtual machines window now.
6 From your home desktop, start a remote terminal via SSH. Use your favorite SSH
program (e.g. the PuTTY program for Windows) and connect to the IP address of the
virtual machine. Log in as “centos” user with the password entered previously. Note, that it
is now possible to use the clipboard to enter new commands and configuration file
statements.
7 Enter the following commands to configure and start the DHCP/TFTP service:
su -l
mkdir /var/lib/tftpboot
cd /var/lib/tftpboot
cp -v /home/centos/Desktop/* .
Starts a super user (“root”) shell.
Creates the standard TFTP directory.
Change the current directory.
Copy files here. (“omm_ffsip.tftp” and
“aafon6xdd.dnls” from the CD ROM). Mind
the trailing dot.
:> /etc/dnsmasq.conf
nano /etc/dnsmasq.conf
Create a new and empty configuration file.
Start the “nano” text editor to change the
“/etc/dnsmasq.conf” file. Adapt and paste the
example configuration from below. Press
[Ctrl-X] to end the text editor and confirm
saving the file with the [Y] and [Return] keys.
dnsmasq -d -q
Start the DHCP/TFTP service in debug
mode.
8 Connect the desired RFPs to your LAN. Establish their power supply, either by PoE or by
plugging in the external power adapters. During the RFP start-up, the SSH console
windows should display debug output as displayed in the following screen shot.
depl-1230/1.3 Page: 15 (196)
SIP – DECT OM System Manual Release 2.1 2 Getting Started
SSH console (PuTTY) with DHCP/TFTP output
DnsMasq Configuration File (/etc/dnsmasq.conf)
The following configuration example needs to be adapted to your network and RFPs.
Change all lines with “192.168.112.” to match your LAN. Use a calculator (e.g. Windows
“Calc”) to convert the hex values in the “openmob,43” line: 192=0xc0, 168=0xa8, 112=0x70,
and 52=0x34. Also change the MAC address (here: 00:30:42:0d:10:2e) to the value printed
on the backside label of the RFP that is designated as OMM.
# Disable DNS service for this dnsmasq instance
port = 0
# The OMM (specific MAC used) needs a fixed IP
dhcp-host = 00:30:42:0d:10:2e,net:openmob,192.168.112.52
# Set net:openmob for clients that send Vendor=='OpenMobility'
dhcp-vendorclass=openmob,OpenMobility
# Ignore queries that does not send Vendor=='OpenMobility'
dhcp-ignore=#openmob
# Set the firmware file name for bootp requests
dhcp-boot = net:openmob,omm_ffsip.tftp
# Specify options to be send to all RFPs
dhcp-option = openmob,224,"OpenMobility" # Let RFP accept our config
dhcp-option = openmob,43,0a:04:c0:a8:70:34 # Hex: 192.168.112.52 is OMM
dhcp-option = openmob,option:router,192.168.112.1
dhcp-option = openmob,option:dns-server,192.168.112.1
dhcp-option = openmob,option:domain-name,"mycompany.de"
dhcp-option = openmob,option:ntp-server,0.0.0.0
# The 'dhcp-range' is required otherwise DNSmask does not serve DHCP
dhcp-range = net:openmob,192.168.112.52,192.168.112.55,,,1h
# This dnsmasq also acts as TFTP server
enable-tftp
tftp-root=/var/lib/tftpboot
The “dhcp-range” statement may overwrite the default netmask and broadcast settings.
Adapt “,,,1h”, e.g. to “255.255.255.0,192.168.112.255,1h” for this.
OMM selection
One RFP of a set needs to function as OpenMobility Manager (OMM). The configuration
suggested above will select a specific RFP for this role with the “DHCP option 43”. The OMM
is generally selected
depl-1230/1.3 Page: 16 (196)
SIP – DECT OM System Manual Release 2.1 2 Getting Started
• via the DHCP request (see chapter 7.5.3.1),
• within the static local configuration of an RFP (see chapter 7.6),
• within the RFP configuration file of a PC-based OMM (see chapter 7.7).
The RFP which has the same IP address as the dedicated OMM IP address will be the RFP
which the OMM application runs on.If two OMM IP adresses are configured, the OMM
application is started on both dedicated RFPs. One OMM becomes the active OMM and the
other the standby OMM. For more details about the standby feature, see chapter 7.11.
2.2 Initial Setup
After bringing up the DHCP/TFTP server and starting the RFPs, you can start a web browser
and call up the web-based user interface of the OMM. Alternatively, the Java-based
OpenMobility Manager (“omp.jar”) may be used. The following step-by-step description
emphasizes on the OMM’s web console.
1 Start a web browser and navigate to the IP address that you have configured for the OMM
in the DHCP option 43. This will display the OMM’s login page.
Note: The browser’s communication with the OMM’s web console is secured by the
HTTPS protocol. However, since you cannot validate a numeric intranet address
with a certifacte chain, you need to ignore / overwrite the web browser’s warning
about invalid certificates.
2 Enter “omm” in the User name input field. Also enter “omm” in the Password input field.
Click the OK button to log in. In the factory default configuration, the OMM now displays
the Info: End-user license agreement page. Read the agreement and confirm by
clicking the Accept button.
OMM web console, login with “omm” / “omm”
3 On the next two pages that are displayed automatically, you need to enter new passwords
for two administrative user accounts. The first account is the “omm” user that can change
the configuration. The second account can be used to call up the OMM’s command line
shell via SSH. Enter passwords that contain at least lower case letters, capital letters, and
digits. After changing the passwords, the web console shows the Status page.
4 Navigate to the System: System settings page. Change the PARK setting to the PARK
code that is printed on the installation CD-ROM. Also change the Regulatory domain to
match your region. Confirm with OK.
depl-1230/1.3 Page: 17 (196)
SIP – DECT OM System Manual Release 2.1 2 Getting Started
System: System settings, change PARK and DECT regulatory domain
Note: The RFP L32 IP / RFP L34 IP / RFP L42 WLAN devices provide a build in license as
described here. If you have purchased another license type and e.g. RFP L32 IP /
RFP L34 IP / RFP L42 WLAN devices, you need to upload the license file on the
Licenses page now (see chapter 4).
5 Navigate to the Radio fixed parts page. Click the Start button to start capturing. Wait 10
seconds. Click the Radio fixed parts menu entry to refresh the display. If all expected
RFPs are listed, click Stop to end capturing.
Radio fixed parts, capture and add new RFPs
6 Click the icon next to the desired entry to add a new RFP to the OMM. The New radio
fixed part dialog opens. Enter a Name. Enable the DECT settings checkbox that assigns
the RFP to DECT cluster “1”. Confirm with OK. Repeat this step for the second RFP.
7 Navigate to the Portable parts page. Click on the New button. The New portable part
dialog opens. Enter a Name, a Number and a DECT authentication code. Confirm with
OK. Repeat this step for a second DECT portable part with a different DECT
authentication code.
depl-1230/1.3 Page: 18 (196)
SIP – DECT OM System Manual Release 2.1 2 Getting Started
Portable parts, add new portable part
8 Click on the Start button below the Wildcard subscription heading. This will activate
subscription without known handset IPEIs for the next two minutes. During this period,
subscribe two of your DECT handsets. Enter the configured DECT authentication code on
the DECT handset during the subscription procedure (see chapter 7). After subscribing
two DECT handsets make a test call from one DECT handset to the other.
9 Navigate to the System: SIP page to connect the OMM to your PBX. Enter the IP address
of your PBX in the Proxy server and Registrar server fields. In the following screen shot,
an Aastra OpenCom 100 PBX with address 192.168.112.91 is used to provide the SIP
PBX functions.
depl-1230/1.3 Page: 19 (196)
SIP – DECT OM System Manual Release 2.1 2 Getting Started
SIP: System, connect to PBX & change portable part SIP configuration
10 Navigate back to the Portable parts page. Click the icon next to the desired portable
part entry to open the respective Configure portable parts dialog. Change to User name
and Password fields under the SIP authentication heading to the SIP account
credentials configured on the PBX (see chapter 5.4.2 and chapter 5.7.1). Note, that the
entered User name is sent to the PBX as “authorization username” within the SIP
“REGISTER” message.
Verify the SIP registration, for example on a status display of your PBX as shown above.
Place a test call from the DECT portable part to another phone attached to the PBX.
The next steps depend on your requirements and would typically include setting up a
standby OMM (see chapter 7.11) or setting up the Download over Air software-update for
Aastra 610d/620d/630d portable parts (see chapter 7.15).
depl-1230/1.3 Page: 20 (196)
SIP – DECT OM System Manual Release 2.1 3 Enhanced Feature Overview
3 Enhanced Feature Overview
An SIP – DECT system scale from a single licensed RFP up to a larger SIP – DECT system
that may include hundreds of RFPs. 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 chapters.
Download over Air
The Aastra 610d / 620d / 630d devices are able to download and upgrade their firmware via
DECT. The firmware file that has to be provided by a TFTP server is automatically distributed
to all subscribed DECT portable parts by the OMM (see chapter 7.15).
OMM standby
The OMM is the central management entity in a SIP – DECT system and forms thereby
single point of failure. It is possible to automatically transfer the OMM function to a second
RFP device in case of failure or loss of network connection (see chapter 7.11).
DECT XQ
The DECT radio communication generally suffers from attenuation and radio wave reflection.
Especially 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 an RFP and an Aastra 610d/620d/630d portable parts at the expense of DECT
channel capacity (see 7.3). Enable this feature for some or all of your RFPs (see chapter
5.6.3, “DECT settings” or chapter 6.7.1.2, “DECT tab”).
RFP synchronization / radio coverage planning
To ensure a seamless communication experience, the SIP – DECT system switches an
ongoing DECT phone call from one RFP to another if the radio communication quality drops
below a certain threshold. The seamless handover is possible only if the participating RFPs
are synchronized. RFP synchronization is performed via radio communication between
RFPs, which in turn requires a decent radio coverage planning (see chapter 7.2).
Clustering / 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 need to split your network into clusters (or “synchronization domains”). Assign RFPs to
cluster numbers for this (see chapter 5.6.3, “DECT settings” or chapter 6.7.1.2, “DECT tab”).
If your SIP – DECT system consists of a very large number of RFPs, you should configure
the paging area size to optimize the signaling necessary for paging a DECT portable part in
throughout the SIP – DECT system (see 6.7.2).
Isolated sites
A separate cluster number is also required, e.g. for a single RFP servicing an office abroad.
Also, if the VPN network connection to the isolated site’s RFP cannot transport DHCP, you
may use static IP address configuration for the single RFP (see chapter 7.6).
depl-1230/1.3 Page: 21 (196)
SIP – DECT OM System Manual Release 2.1 3 Enhanced Feature Overview
Wireless LAN (WLAN)
If you purchased a number of WLAN RFPs (RFP L42 WLAN or RFP 42 WLAN), the SIP –
DECT system also provides access to your company LAN via Wireless LAN. The WLAN
configuration of a group of WLAN RFPs is managed by WLAN profiles (see chapter 5.8).
Locating application
You can set up a system to locate and track DECT portable parts in your DECT system. This
includes a separate Web user interface, which for example can be operated by service
personnel to locate a DECT portable part that has triggered an alarm. Refer to the
“OpenMobility Location Application” user guide for details, see /23/.
Extended messaging
You can set up an extended messaging and alarms system, e.g. to provide automated
reactions on alarms triggered by DECT portable parts or on alert messages. The extended
messaging system may also provide message confirmations, message based services, and
may also be integrated with external computer systems. Refer to the “OpenMobility
Integrated Messaging & Alerting” user guide for details, see /24/.
OpenMobility provisioning
While some users in the SIP – DECT system will use their “personal handset”, it is also
possible to operate shared handsets. The OpenMobility SIP – DECT solution provides an
enhanced DECT Handset Sharing and Provisioning concept that enables to comfortably
manage a large amount of DECT handsets and which provides a flexible subscribing model.
With this, the SIP – DECT system supports new features such as logging in and out with a
personalized user account on different DECT handsets, import of user data from an external
provisioning server, automatically subscribe new DECT handsets or control subscription
specific system functions from DECT handsets. Refer also to the “OpenMobility Provisioning”
user guide for details see /26/.
SNMP integration / External configuration files
To integrate the SIP – DECT system into external management systems, each RFP runs an
SNMP agent that can be queried by SNMP management software (see 7.14). To integrate to
external configuration management systems, the DECT system’s configuration is available
my means of ASCII-based configuration files. For example, you can configure automatic
import or export of configuration files from/to an external server (refer also to the
“OpenMobility Provisioning” user guide for details see /26/).
PC-based OMM installation
A very large number of RFPs or a large number of DECT portable parts may exceed the
storage capacity or processing power of the embedded RFP device. For this reason, it is also
possible to operate the OMM on a standard PC under the Linux operating system (see
chapter 7.8).
System configuration tools
You can configure and maintain the SIP – DECT system with two different
applications:
• a web-based service (OMM Web service, see chapter 5) and
• a java-based tool (OM Management Portal, OMP, see chapter 6).
depl-1230/1.3 Page: 22 (196)
SIP – DECT OM System Manual Release 2.1 3 Enhanced Feature Overview
Both applications support the essential configuration and administration settings required for
smaller SIP – DECT systems. However, for larger SIP – DECT systems using enhanced
features, some settings are not available in both applications. To help you to decide which
application to use, the following table lists the features and settings that are available in one
of the applications:
Feature Web OMP
OMM update & restart Yes No
Time zone settings Yes No
SNMP configuration Yes No
WLAN configuration Yes No
Dynamic PP subscriptions (OpenMobility provisioning) No Yes
Locating settings for PP No Yes
Paging areas No Yes
Alarm Triggers No Yes
RFP sync. View No Yes
RFP statistics No Yes
depl-1230/1.3 Page: 23 (196)
SIP – DECT OM System Manual Release 2.1 4 Licensing
4 Licensing
4.1 Licensing Model
Starting with version 2.1 several features of the Open Mobility system are licensed:
• the system size concerning the number of configured RFPs,
• the software version running the OMM,
• the messaging application, and
• the locating application.
For information on the messaging and locating application please refer to the appropriate
documents listed in the section 9.6 References.
There are three different license modes available for the user depending on the desired
system size:
• Built-in license
for small systems consisting of at most 2 RFPs,
• Activated built-in license
for medium systems consisting of at most 20 L-RFPs and
• Standard license
for large systems with variable system size up to 2048 RFPs (the actual number is part of
the license).
Additionally the OMM can operate in a demonstration mode.
4.1.1 Latency Timer
The OMM identifies medium and large systems using the unique PARK as well as the MAC
addresses of up to three RFPs (called validation RFPs here).
The number of three RFPs guarantees a redundancy when a hardware or network error
occurs. On the other hand, an odd number does not allow system duplication with splitting
the system into two separate parts.
OM Web service: Licenses page
When the 1st validation RFP is disconnected the OMM generates just a warning. This
warning will be displayed on the Status page of the OM Web service, see also chapter 5.3.
depl-1230/1.3 Page: 24 (196)
SIP – DECT OM System Manual Release 2.1 4 Licensing
OM Web service: Status page
But when the 2nd validation RFPs is disconnected, the OMM considers a license violation. In
this case a latency timer of up to 72 hours starts to decrement. When the timer expires, the
OMM restricts all licensed features.
When the validation RFPs are reconnected to the OMM, the latency timer is incremented
until it reaches its maximum of 72 hours. In other words the latency timer must be recharged
the same time as the violation last to gain the full redundancy time.
4.1.2 License Violations and Restrictions
A license can be violated in three ways:
• The number of configured items exceeds the number of licensed items. In this case the
associated feature is restricted:
- the audio stream of calls is dropped after 30 seconds when the number of connected
RFPs exceeds the licensed number,
- the messaging application limits the type of messages to “info”,
- the locating feature is stopped.
• The software version coded into the activation or license file does not cover the software
version running on the OMM.
All of the restrictions above will be activated until either the OMM is restarted with the
correct version or the license is replaced covering the correct software version.
• The OMM has no connection to at least 2 of the validation RFPs and the latency timer has
expired.
All of the restrictions above will be activated until at least 2 validation RFPs are
reconnected to the OMM.
depl-1230/1.3 Page: 25 (196)
SIP – DECT OM System Manual Release 2.1 4 Licensing
4.2 Uploading an Activation or License File
An activation or a license file must be purchased from the Aastra license server. The license
confirmation you received contains detailed information how to generate an activation /
license file. The file can be uploaded into the OMM either via Web service (see chapter 5.10)
or via the OMP (see chapter 6.10).
An activation file as well as a license file contain a PARK for system identification. If the
newly imported PARK differs from the current PARK, the OMM will perform a reset.
Note: The file can be opened with a text editor to view the license or activation parameter.
4.3 Demonstration Mode
When an OMM comes up for the first time, it considers itself as working in demonstration
mode. In this mode all of the OMM features can be evaluated without any license for 72
hours starting with the 1
st
RFP being connected to the OMM.
Display of demonstration mode in the OM Web service
After 72 hours the OMM restricts all features as described in section 4.1.2.
The OMM stays in demonstration mode as long as the default built-in PARK is not changed.
The PARK can be changed either on the System settings page as described in section
5.4.1. This leads to a small system using the built-in license. Another way to change the
PARK is to upload an activation or license file purchased from the Aastra license server (see
chapter 4.1.1). This leads to a medium system or large system respectively.
Note: Multiple OMMs running the Demo license at the same location can influence each
other because of the same PARK!
4.4 License Modes
4.4.1 Built-in License (Small System)
When changing the PARK on the System settings page of the OM Web service, the OMM
uses the built-in license. The built-in license features:
• up to two L-RFPs
depl-1230/1.3 Page: 26 (196)
SIP – DECT OM System Manual Release 2.1 4 Licensing
- messaging restricted to type “Info”, “Low”, “Normal” and “High” for all user (no
“Emergency” and “Locating Alert”), and
- no locating.
• up to two “normal” RFPs
- ◦ no messaging (except prio Info) and
- ◦ no locating.
On a small system it is prohibited to exceed the limits of license due configuration. Since
there is no activation or license file present, the software version is not checked. As the
system is not validated via RFPs and hence the latency timer does not play any role there
are no license violations possible at all.
When there are more than 2 RFPs configured while the PARK is changed only the first two
RFPs will stay in the configuration database. All other RFPs will be dropped silently.
4.4.2 Activated Built-in License (Medium System)
When the PARK is changed via the upload of an activation file, the OMM enters the activated
system state. In this state the OMM uses the following license features:
• up to 20 L-RFPs,
• messaging restricted to type “Info”, “Low”, “Normal” and “High” for all user (no
“Emergency” and “Locating Alert”), and
• no locating.
The OMM extracts the software version from the activation file and checks this against its
own software version. A lower software version within the activation file leads to a license
violation.
The OMM prevents a license violation due misconfiguration e.g. it is not possible to configure
st
RFP in the system.
a 21
To obtain an activation file from the Aastra license server the MAC address of 3 RFPs must
be entered. These 3 validation RFPs are used to validate the activation.
depl-1230/1.3 Page: 27 (196)
SIP – DECT OM System Manual Release 2.1 4 Licensing
While obtaining an activation file from the Aastra license server it is possible to enter the
PARK used for a small system installation. This prevents the need to re-subscribe all
handsets.
When there are more than 20 RFPs configured (in demonstration mode) while an activation
file is uploaded, only the first 20 RFPs will stay in the configuration database. All other RFPs
will be dropped silently.
Note: Note: When once changed via activation file upload, the PARK cannot be changed
any more on the System settings page of the OM Web service.
4.4.3 Standard License (Large System)
When the PARK is changed via the upload of a license file, the OMM enters the large system
state. In this state the OMM uses the following license features coded into the license file.
• System license:
- number of RFPs (L-RFPs or normal RFPs),
- software version of the OMM allowed to be executed.
• Messaging license:
- number of messaging clients allowed to send messages,
- whether clients are allowed to receive messages.
• Locating license:
- number of locatable handsets,
- whether the locating application is allowed to execute.
During purchase of a license file from the Aastra license server, the MAC address of 3 RFPs
must be entered. These 3 validation RFPs are used to operate the latency timer as described
in section 4.1.1.
depl-1230/1.3 Page: 28 (196)
SIP – DECT OM System Manual Release 2.1 4 Licensing
When obtaining the license file from the Aastra license server, it is possible to use the PARK
used for a small or medium system installation. This prevents the need to re-subscribe all
handsets.
Note: Note: When once changed via activation file upload, the PARK cannot be changed
any more on the System settings page of the OM Web service.
depl-1230/1.3 Page: 29 (196)
SIP – DECT OM System Manual Release 2.1 5 OMM Web Service
5 OMM Web Service
The OMM acts as an HTTP/HTTPS server. The HTTP server binds to port 80 and HTTPS
binds to port 443 by default. A HTTP request on port 80 will be redirected to HTTPS on
port 443. The service access is restricted to one active session at a time and is password
protected.
The browser used for service access has to be at least Microsoft Internet Explorer 6.0 or
Mozilla Firefox 1.5 and must have frame support, JavaScript and cookies enabled.
Note: The service access is restricted to one active session at a time and is password
protected.
5.1 Login
The OMM allows only one user at a time to configure the system. A user must authenticate
with a user name and a password. Both strings are checked case sensitive.
With initial installation or after discarding all settings, the OMM Web service is accessible via
a default build-in user account with user “omm” and password “omm”.
With the first login into a new SIP – DECT SW version the user has to accept the End User
License Agreement (EULA), see chapter 5.11.
If the default build-in user account is active, the administrator has to change the default
account data (passwords) of the “Full access” and “root” account. Refer Initial Setup (see
chapter 2.2). The meaning of the different account types is described in section 7.12.1.
Please note: The OMM will force to alter the default account data. As long as the
passwords are unchanged, the OMM will not allow any other configuration.
After login in, the following menus are available:
• Status menu:
displays the system status, see chapter 5.3;
• System menu:
allows configuration of general SIP – DECT system parameters, see chapter 5.4;
depl-1230/1.3 Page: 30 (196)
Loading...