AASTRA SIP-DECT User Manual

SIP–DECT OM System Manual Release 3.0

SIP–DECT

OM System Manual

Installation, Administration, and

Maintenance

Release 3.0

Document ID: depl-1624

Version: 1.0

Aastra Deutschland GmbH	Zeughofstr. 1	2012 - All Rights Reserved
	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-1624/1.0

Page: 1 (241)

SIP–DECT OM System Manual Release 3.0 Table of Contents

Table of Contents

1 OVERVIEW		...........................................................................................................................................	7
1.1	THE SIP–DECT SOLUTION............................................................................................................		7
1.2	ABOUT THE RADIO FIXED PARTS (RFPS)........................................................................................		9
	1.2.1 ..................................................................................................................	RFP Families	9
	.......................................................	1.2.1.1 Former RFP Types (Till SIP–DECT Release 2.1)	9
	.....................................................	1.2.1.2 New RFP Types (Since SIP–DECT Release 3.0)	10
	1.2.2 .............................................................................................................	RFP only Mode	12
	1.2.3 ...........................................................................OpenMobility Manager (OMM) Mode		12
1.3	ABOUT ..........................................................................................THE OPENMOBILITY MANAGER		12
	1.3.1 ..................................................................................................................	OMM Tasks	13
	1.3.2 ...............................................................SIP–DECT Special Features and Capacities		14
	1.3.3 .....................................................................................OMM Capacities and Features		15
1.4	ABOUT ......................................................................................................THE PORTABLE PARTS		16

2	GETTING STARTED...........................................................................................................................				18
	2.1	SETTING UP DHCP / TFTP ..........................................................................................................			18
	2.2	INITIAL SETUP..............................................................................................................................			22
3	ENHANCED FEATURE OVERVIEW..................................................................................................				27
4	NAMING CONVENTION .....................................................................................................................				33
5	LOGIN AND PASSWORDS................................................................................................................				34
6	LICENSING .........................................................................................................................................				35
	6.1	LICENSING MODEL .......................................................................................................................			35
		6.1.1	Grace Period.................................................................................................................		37
		6.1.2 License Violations and Restrictions..............................................................................			38
		6.1.3 G. 729 License Violations.............................................................................................			38
	6.2	UPLOADING AN ACTIVATION OR LICENSE FILE ...............................................................................			39
	6.3	DEMONSTRATION MODE...............................................................................................................			39
	6.4	LICENSE MODES..........................................................................................................................			40
		6.4.1	Small System................................................................................................................		40
		6.4.2	Medium System............................................................................................................		40
		6.4.3	Large System................................................................................................................		41
7	OMM WEB SERVICE..........................................................................................................................				43
	7.1	LOGIN .........................................................................................................................................			43
	7.2	LOGOUT	......................................................................................................................................		44
	7.3	“STATUS” MENU ..........................................................................................................................			45
	7.4	“SYSTEM” MENU ..........................................................................................................................			45
		7.4.1	“System settings” Menu................................................................................................		45
			7.4.1.1	Restarting the OMM ..................................................................................................	49
			7.4.1.2	Updating the OMM ....................................................................................................	49
		7.4.2	“SIP” Menu....................................................................................................................		50
		7.4.3	“User administration” Menu ..........................................................................................		54
		7.4.4	“Time zones” Menu.......................................................................................................		55
			7.4.4.1	Changing Time Zones ...............................................................................................	56
			7.4.4.2	Resetting Time Zones ...............................................................................................	56
		7.4.5	“SNMP” Menu...............................................................................................................		56
		7.4.6	“DB management” Menu ..............................................................................................		58
			7.4.6.1	Manual Database Import ...........................................................................................	58
			7.4.6.2	Automatic Database Import.......................................................................................	59
			7.4.6.3	Manual Database Export...........................................................................................	61
			7.4.6.4	Automatic Database Export.......................................................................................	61
		7.4.7	“Event log” Menu ..........................................................................................................		62
	7.5	“SITES” MENU..............................................................................................................................			62
		7.5.1 Creating a New Site......................................................................................................			63
		7.5.2	Editing a Site.................................................................................................................		64
		7.5.3	Deleting a Site ..............................................................................................................		64
	7.6	“RADIO FIXED PARTS” MENU.........................................................................................................			64
		7.6.1 States of an RFP ..........................................................................................................			65

Aastra

depl-1624/1.0

Page: 2 (241)

SIP–DECT OM System Manual Release 3.0				Table of Contents
	7.6.2 OMM / RFP SW Version Check ...................................................................................			66
	7.6.3 Creating and Changing RFPs.......................................................................................			67
	7.6.4 Importing RFP Configuration Files ...............................................................................			69
	7.6.5	Capturing RFPs ............................................................................................................		71
	7.6.6	Deleting RFPs...............................................................................................................		72
7.7	“PORTABLE PARTS” MENU ............................................................................................................			72
	7.7.1 Creating and Changing PPs .........................................................................................			73
	7.7.2 Importing PP Configuration Files..................................................................................			75
	7.7.3	Subscribing PPs ...........................................................................................................		76
		7.7.3.1 Subscription with Configured IPEI.............................................................................		77
		7.7.3.2	Wildcard Subscription................................................................................................	78
	7.7.4	Deleting PPs.................................................................................................................		78
	7.7.5 Searching within the PP List.........................................................................................			78
7.8	“WLAN” MENU............................................................................................................................			80
	7.8.1	“WLAN profiles” Menu ..................................................................................................		80
		7.8.1.1 Creating and Changing WLAN Profiles .....................................................................		81
		7.8.1.2	Deleting WLAN Profiles.............................................................................................	87
		7.8.1.3	Exporting WLAN Profiles...........................................................................................	88
	7.8.2	“WLAN clients” Menu....................................................................................................		88
7.9 “SYSTEM FEATURES” MENU..........................................................................................................				88
	7.9.1	“Digit treatment” Menu..................................................................................................		89
		7.9.1.1 Creating and Changing “Digit treatment” Entries.......................................................		90
		7.9.1.2 Deleting “Digit treatment” Entries ..............................................................................		91
	7.9.2	“Directory” Menu...........................................................................................................		91
		7.9.2.1 Creating and Changing LDAP Servers......................................................................		92
		7.9.2.2	Deleting LDAP Entries...............................................................................................	93
	7.9.3 “Feature access codes” Menu......................................................................................			93
7.10	“LICENSES” MENU........................................................................................................................			94
7.11	“INFO” MENU ...............................................................................................................................			95
8 OM MANAGEMENT PORTAL (OMP) ................................................................................................				96
8.1	LOGIN .........................................................................................................................................			96
8.2	LOGOUT	......................................................................................................................................		97
8.3	OMP MAIN WINDOW....................................................................................................................			97
8.4	“STATUS” MENU ..........................................................................................................................			99
8.5	“SYSTEM” MENU ........................................................................................................................			100
	8.5.1	“System settings” Menu..............................................................................................		100
	8.5.2	“Statistics” Menu.........................................................................................................		101
	8.5.3	“SIP” Menu..................................................................................................................		103
	8.5.4	“User administration” Menu ........................................................................................		104
		8.5.4.1 Creating New User Accounts ..................................................................................		105
		8.5.4.2 Changing a User Account .......................................................................................		106
		8.5.4.3 Viewing User Account Details .................................................................................		107
		8.5.4.4	Deleting User Accounts...........................................................................................	107
	8.5.5	“Data management” Menu..........................................................................................		107
		8.5.5.1 “Automatic DB import” Tab......................................................................................		107
		8.5.5.2 “Automatic DB export” Tab......................................................................................		109
		8.5.5.3 “User data import” Tab ............................................................................................		110
		8.5.5.4 “Manual DB import” Tab ..........................................................................................		111
		8.5.5.5 “Manual DB export” Tab ..........................................................................................		112
		8.5.5.6	“Maintenance” Tab ..................................................................................................	113
8.6	“SITES” MENU............................................................................................................................			114
8.7 “RADIO FIXED PARTS” MENU.......................................................................................................				115
	8.7.1	“Device list” Menu.......................................................................................................		115
		8.7.1.1	RFP Detail Panel.....................................................................................................	117
		8.7.1.2	Adding New RFPs...................................................................................................	119
		8.7.1.3	Changing RFPs.......................................................................................................	121
		8.7.1.4	Viewing RFP Details................................................................................................	121
		8.7.1.5	Deleting RFPs .........................................................................................................	121
		8.7.1.6	Showing Synchronization Relations ........................................................................	121
		8.7.1.7	Selecting Columns ..................................................................................................	122
		8.7.1.8	Filtering RFP Table .................................................................................................	122
	8.7.2	“Paging areas” Menu ..................................................................................................		123
	8.7.3	“Enrolment” Menu.......................................................................................................		124

Aastra

depl-1624/1.0

Page: 3 (241)

SIP–DECT OM System Manual Release 3.0				Table of Contents
	8.7.4	“Export” Menu.............................................................................................................		125
	8.7.5	“Sync view” Menu .......................................................................................................		126
	8.7.6	“Statistics” Menu.........................................................................................................		128
		8.7.6.1	RFP Statistics Overview..........................................................................................	128
		8.7.6.2 RFP Statistics Group Panels...................................................................................		130
8.8	“PORTABLE PARTS” MENU ..........................................................................................................			130
	8.8.1	Overview” Menu .........................................................................................................		131
	8.8.2	“Users” Menu..............................................................................................................		133
	8.8.3	“Devices” Menu ..........................................................................................................		134
	8.8.4	PP Detail Panel ..........................................................................................................		135
	8.8.5	Creating PP Datasets .................................................................................................		139
	8.8.6	Configuring PP Datasets ............................................................................................		139
	8.8.7	Subscribing PP Datasets............................................................................................		140
	8.8.8	Deleting PP Datasets .................................................................................................		140
	8.8.9	Selecting Columns......................................................................................................		140
	8.8.10	Filtering PP Table .......................................................................................................		141
	8.8.11	Enabling / Disabling PP Event Log.............................................................................		142
8.9 “SYSTEM FEATURES” MENU........................................................................................................				142
	8.9.1	“General settings” Menu .............................................................................................		143
	8.9.2	“Feature access codes” Menu....................................................................................		144
	8.9.3	“Alarm triggers” Menu.................................................................................................		145
		8.9.3.1	Creating “Alarm triggers” .........................................................................................	146
		8.9.3.2	Configuring “Alarm triggers” ....................................................................................	146
		8.9.3.3	Deleting “Alarm triggers” .........................................................................................	146
		8.9.3.4	View “Alarm trigger” Details.....................................................................................	147
	8.9.4	“Digit treatment” Menu................................................................................................		147
	8.9.5	“Directory” Menu.........................................................................................................		148
	8.9.6	“XML applications” Menu............................................................................................		148
		8.9.6.1 Creating a New XML Hook......................................................................................		150
		8.9.6.2 Changing an XML Hook ..........................................................................................		150
		8.9.6.3 Viewing XML Hook Details ......................................................................................		151
		8.9.6.4	Deleting XML Hooks................................................................................................	151
8.10	“LICENSE” MENU........................................................................................................................			152
8.11	“GENERAL” MENU ......................................................................................................................			152
8.12	“HELP” MENU ............................................................................................................................			154
9 CONFIGURATION UND ADMINISTRATION ASPECTS .................................................................				155
9.1 IP SIGNALING AND MEDIA STREAM .............................................................................................				155
9.2	RFP SYNCHRONIZATION ............................................................................................................			157
	9.2.1	Initial Synchronization Procedure...............................................................................		159
	9.2.2	Checking the Synchronization of a Network...............................................................		159
9.3 RFP CHANNEL CAPACITY ..........................................................................................................				160
9.4 NETWORK INFRASTRUCTURE PREREQUISITES .............................................................................				160
9.5	SIP–DECT STARTUP ................................................................................................................			161
	9.5.1	TFTP and DHCP Server Requirements .....................................................................		161
	9.5.2	Booting Steps .............................................................................................................		162
	9.5.3	Booter Startup.............................................................................................................		163
		9.5.3.1	DHCP Client............................................................................................................	164
		9.5.3.1.1	DHCP Request ......................................................................................................	164
		9.5.3.1.2	DHCP Offer............................................................................................................	164
		9.5.3.1.3	Retries ...................................................................................................................	165
		9.5.3.2	TFTP Client .............................................................................................................	165
		9.5.3.3	Booter Update .........................................................................................................	165
	9.5.4	Application Startup .....................................................................................................		165
		9.5.4.1	DHCP Client............................................................................................................	165
		9.5.4.2	Configuration using DHCP ......................................................................................	167
		9.5.4.3 Selecting the Right DHCP Server............................................................................		168
	9.5.5	RFP LED Status .........................................................................................................		169
		9.5.5.1	Booter LED Status...................................................................................................	169
		9.5.5.2	Application LED Status............................................................................................	170
9.6 STATE GRAPH OF THE START-UP PHASES...................................................................................				173
9.7 STATIC LOCAL CONFIGURATION OF AN RFP (OM CONFIGURATOR)..............................................				174
9.8	RFP CONFIGURATION FILES.......................................................................................................			181
9.9 RFP (L) 35/36/37 IP / RFP (L) 43 WLAN SOFTWARE UPDATE..................................................				185

Aastra

depl-1624/1.0

Page: 4 (241)

SIP–DECT OM System Manual Release 3.0					Table of Contents
	9.10	802.1Q SUPPORT		......................................................................................................................	186
		9.10.1 Boot Phase of IP RFPs (DHCP).................................................................................			186
		9.10.2 Boot Phase of IP RFPs (Local Configuration) ............................................................			187
	9.11	INSTALLING OMM ...............................................................................................IN HOST MODE			187
		9.11.1	System Requirements ................................................................................................		188
		9.11.2 Installing ......................................................................................the OMM Software			188
		9.11.3 Configuring ...............................................................................the Start Parameters			189
		9.11.4 Specific Commands ......................................................................– Troubleshooting			190
		9.11.5 Upgrade ................................................from OMM Version 2.x to 3.x in Host Mode			190
	9.12	UPDATING THE OMM.................................................................................................................			190
		9.12.1 Updating ...........................................................................a Single OMM Installation			191
		9.12.2 Updating ........................................................................a Standby OMM Installation			191
	9.13	OMM STANDBY.........................................................................................................................			192
		9.13.1	Configuring .........................................................................................OMM Standby		193
		9.13.2	Fail Over ....................................................................................................Situations		193
		9.13.3 Fail Over ........................................................................................Failure Situations			193
		9.13.4	Specific Standby ........................................................................................Situations		195
			9.13.4.1 ...................................................................How A Standby OMM Becomes Active		195
			9.13.4.2 ................................................Handling When Both OMMs Are Not Synchronized		195
			9.13.4.3 .........................................................................................Two DECT Air Interfaces		195
	9.14	MANAGING ACCOUNT ......................................................................DATA FOR SYSTEM ACCESS			196
		9.14.1	Account Types............................................................................................................		196
		9.14.2	Potential ..........................................................................................................Pitfalls		197
	9.15	WLAN CONFIGURATION ....................................(RFP (L) 42 WLAN / RFP (L) 43 WLAN ONLY)			197
		9.15.1	WLAN configuration ..........................................................................................steps		197
		9.15.2	Optimizing .................................................................................................the WLAN		198
		9.15.3	Securing ....................................................................................................the WLAN		200
	9.16	SNMP CONFIGURATION.............................................................................................................			200
	9.17	DOWNLOAD OVER ...............................................................................................................AIR			201
		9.17.1 How “Download ................................................................................Over Air” Works			201
		9.17.2 How to configure .......................................................................“Download Over Air”			202
10	MAINTENANCE ................................................................................................................................				205
	10.1	SITE SURVEY MEASUREMENT ..................................................................................EQUIPMENT			205
	10.2	CHECKING THE AASTRA ...............................................................HANDSET FIRMWARE VERSION			205
	10.3	DIAGNOSTIC ..............................................................................................................................			205
		10.3.1 Aastra Handset .............................................................................Site Survey Mode			205
		10.3.2 Aastra Handset .........................................................................Auto Call Test Mode			206
		10.3.3 Aastra Handset ...................................................................Auto Answer Test Mode			206
		10.3.4	Syslog	207
		10.3.5	SSH user ............................................................................................................shell		208
			10.3.5.1 .......................................................................................................................	Login	208
			10.3.5.2 ................................................................................................	Command Overview	209
			10.3.5.3 ........................................................................OMM Console On Linux x86 Server		210
			10.3.5.4 ........................................................................................	RFP Console Commands	210
			10.3.5.5 ......................................................................................	OMM Console Commands	211
		10.3.6	Core File ....................................................................................................Capturing		212
		10.3.7	DECT Monitor.............................................................................................................		213
11	APPENDIX ........................................................................................................................................				217
	11.1	DECLARATION OF C ..................................................................................................ONFORMITY			217
	11.2	COMMUNICATIONS ........................REGULATION INFORMATION FOR AASTRA 142D, AASTRA 600D			217
		11.2.1 FCC Notices ............................................................................................(U.S. Only)			217
		11.2.2 Industry Canada .................................................(Canada only, not for Aastra 600d)			218
	11.3	COMMUNICATIONS ......................REGULATION INFORMATION FOR RFP 32, RFP 34 AND RFP 35			218
		11.3.1 FCC Notices ............................................................................................(U.S. Only)			218
		11.3.2	Industry Canada .................................................................................(Canada only)		219
	11.4	ABBREVIATIONS.........................................................................................................................			220
	11.5	DEFINITIONS..............................................................................................................................			220
	11.6	REFERENCES ............................................................................................................................			222
	11.7	PRE-CONFIGURATION ..............................................................................................FILE RULES			223
		11.7.1 PP Configuration .....................................................................File (OMM Database)			224
			11.7.1.1 ............................................................................................	Supported Instructions	224

Aastra

depl-1624/1.0

Page: 5 (241)

SIP–DECT OM System Manual Release 3.0		Table of Contents
11.7.1.2	Data Section Fields .................................................................................................	225
11.7.1.3	Example ..................................................................................................................	225
11.7.2 RFP Configuration File / Central (OMM Database)....................................................		227
11.7.2.1	Supported Instructions ............................................................................................	227
11.7.2.2	Data Section Fields .................................................................................................	228
11.7.2.3	Example ..................................................................................................................	228
11.7.3 RFP Configuration File / Local (OM Configurator) .....................................................		230
11.7.3.1	Supported Instructions ............................................................................................	230
11.7.3.2	Data Section Fields .................................................................................................	231
11.7.3.3	Example ..................................................................................................................	232
11.8 RFP EXPORT FILE FORMAT .......................................................................................................		233
11.9 PROTOCOLS AND PORTS............................................................................................................		235
12 INDEX................................................................................................................................................		237

Aastra

depl-1624/1.0

Page: 6 (241)

SIP–DECT OM System Manual Release 3.0	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 222.

Reference

For a list of abbreviations and definitions valid for this manual please refer to the appropriate chapters in the Appendix starting on page 217.

Trademarks

Linux® is a registered trademark of Linus Torvalds. Red Hat® is a registered trademark of Red Hat, Inc.

Apache Tomcat™ is a trademark of the Apache Software Foundation. Oracle™ and Java™ are a registered trademarks of Oracle Corporation. Windows® and Excel® are a registered trademarks of Microsoft Corporation .

All other product and brand names are trademarks, registered trademarks, or service marks of their respective holders.

1.1The 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 x86 server (for large installations). In addition, a standby OMM can be configured to ensure the OMM function in case of failure or loss of network connection.

•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:

Aastra

depl-1624/1.0

Page: 7 (241)

SIP–DECT OM System Manual Release 3.0		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.

Aastra

depl-1624/1.0

Page: 8 (241)

SIP–DECT OM System Manual Release 3.0	1 Overview

1.2About the Radio Fixed Parts (RFPs)

1.2.1RFP Families

1.2.1.1Former RFP Types (Till SIP–DECT Release 2.1)

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

-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.

Aastra

depl-1624/1.0

Page: 9 (241)

SIP–DECT OM System Manual Release 3.0	1 Overview

RFP 32 IP / RFP L32 IP / RFP 32 NA	RFP L42 WLAN / RFP 42 WLAN
RFP 34 IP / RFP L34 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

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 built-in license, please see chapter Licensing for details.

Note: Since SIP–DECT 3.0, the previous RFP family (RFP (L) 32/34 IP and

RFP (L) 42 WLAN) cannot longer run the Open Mobility Manager (see also chapter 1.3). The SW package for previous RFPs has a tftp extension e.g. “iprfp2G.tftp”.

1.2.1.2 New RFP Types (Since SIP–DECT Release 3.0)

With SIP–DECT release 3.0 Aastra provides 3 new types of RFPs for the SIP–DECT solution:

•RFP 35 IP / RFP L35 IP DECT RFP as indoor model

•RFP 36 IP / RFP L36 IP

DECT RFP as outdoor model with built-in dipole antennas

•RFP 37 IP / RFP L37 IP

DECT RFP as outdoor model with connectors for external directional antennas

•RFP 43 WLAN / RFP L43 WLAN

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

Aastra

depl-1624/1.0

Page: 10 (241)

SIP–DECT OM System Manual Release 3.0	1 Overview

The difference between L-RFPs (L35 IP / L36 IP / L37 IP / L43 WLAN) and non-L-RFPs (35 IP / 36 IP / 37 IP / 43 WLAN) is that the “L” variants have built-in licenses, please see chapter Licensing for details.

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 Ethernet (PoE)

3USB

4DECT antenna connector (RFP (L) 37 IP)

5Antennas (RFP (L) 37 IP)

The hardware of all the new RFPs complies with the different regulatory areas of the world. 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 (L) 32/34 IP and RFP (L) 42 WLAN) are:

•Boot from internal flash memory instead of net-boot; there is already a SIP–DECT software on board

•software update via TFTP, FTP(S), HTTP(S) supported

•supports 1GBit Ethernet

•supports CAT-iq 1.0 level high definition voice for the new Aastra 650c handset family

•hardware is ready to support Secure SIP and SRTP with a SIP–DECT 3.0 follow-up release

•uses an external 48V DC Power Supply (if no PoE available) which fulfils the latest environmental requirements

•The RFP 43 WLAN supports the 802.11abg and 802.11n standards.

•The RFP 43 WLAN can house the OMM.

•The indoor RFPs have a USB 2.0 interface to connect external hardware for future applications e.g. video camera.

Aastra

depl-1624/1.0

Page: 11 (241)

SIP–DECT OM System Manual Release 3.0	1 Overview

1.2.2RFP 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/media resources for media streams. All DECT time slots are used for control signaling, software download over air, messaging and bearer handover independent of associated DSP/media 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.

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.3OpenMobility Manager (OMM) Mode

If the OMM shall not run on a dedicated Linux x86 server 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 9.5) or by setting the data via the OM Configurator (see 9.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, 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.3About the OpenMobility Manager

With SIP–DECT 3.0 the OpenMobility Manager (OMM) requires to run on one of the new RFP types (RFP (L) 35/36/37 IP resp. RFP (L) 43 WLAN) or on a dedicated Linux x86 server.

Aastra

depl-1624/1.0

Page: 12 (241)

SIP–DECT OM System Manual Release 3.0	1 Overview

There is only one active OpenMobility Manager (OMM) in the system.

•If the OMM runs on an RFP, a 100 Mbit network link is required.

•If the OMM runs on a dedicated Linux x86 server, a 1 Gbit network link is required (see also chapter 9.11.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 chapter 9.13.

1.3.1OMM 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

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

Aastra SIP Phones“ for SIP–DECT handsets. The Aastra 600d handset family (firmware release 4.00 required) and the Aastra 650c handset are supported.

Aastra

depl-1624/1.0

Page: 13 (241)

SIP–DECT OM System Manual Release 3.0	1 Overview

Additional information on the following topics are available with separate documents.

•Locating: please see the SIP–DECT; OM Locating Application; Installation, Administration & User Guide /25/.

•Integrated Messaging and Alerting Service: please see the SIP–DECT; OM Integrated Messaging & Alerting Application; Installation, Administration & User Guide /26/ and the SIP–DECT; Aastra 610d, 620d, 630d; Messaging & Alerting Applications; User Guide /28/.

•Integration of SIP–DECT in unified messaging and alarm environments: please see /28/ and the OM Application XML Interface (OM AXI) specification /28/.

•User data provisioning: please see the SIP–DECT; OM Handset Sharing & Provisioning; User Guide /27/.

•Administration and Monitoring by 3rd party applications: please see the OM Application XML Interface (OM AXI) specification /28/.

•SIP–DECT XML terminal interface: please see the SIP–DECT XML terminal interface specification /34/.

1.3.2SIP–DECT Special Features and Capacities

Special features and capacities of the SIP–DECT 3.0 solution are:

Feature/Handset	GAP	142d	600d 1	650c
Large DECT Systems (XXL)	No connection	yes	yes	yes
	handover
	beyond
	256 RFPs
Messaging & Alerting	no	no	yes	yes
Initiate Alarm Trigger	*, # feature	*, # feature	yes	yes
	access code	access code
	procedure,	procedure,
	no sensor	no sensor
	alarm	alarm
Locating	yes	yes	yes	yes
			enhanced	enhanced
			locating	locating
			features	features
DECT XQ	no	no	yes	yes
UTF-8 and alphanumeric	no	no	yes	yes
dialing support 2
SIP–DECT XML terminal API 2	no	no	yes	yes
CAT-iq 1.0 / Aastra Hi-Q™	no	no	no	yes
audio technology 2

1requires Aastra 600d firmware release 4.00 or higher

2new with SIP–DECT 3.0

Aastra

depl-1624/1.0

Page: 14 (241)

SIP–DECT OM System Manual Release 3.0	1 Overview

1.3.3OMM Capacities and Features

The OMM capacities are:

Feature/SW Release	Release 1.8		Release 2.1		Release 3.0 or later
	RFP OMM	Linux x86	RFP OMM	Linux x86	RFP OMM	Linux x86
		server OMM		server OMM		server OMM
L-RFP:	256	-	20	-	20 1	-
RFP L32/34 IP and
RFP L42 WLAN
Standard RFP:	-	-	256 2	2048 2	256 1, 2	2048 2
RFP 32/34 IP and
RFP 42 WLAN
L-RFP:	-	-	-	-	20	-
RFP L35/36/37 IP
and RFP L43 WLAN
Standard RFP:	-	-	-	-	256 2	2048 2
RFP 35/36/37 IP and
RFP 43 WLAN
Handsets / users	512	-	512	4500	512	4500
Message / Alarm	-	-	yes / yes 2	yes / yes 2	yes / yes 2	yes / yes 2
receive
Message send	-	-	yes 3	yes 3	yes 3	yes 3
Locating	-	-	yes 2	yes 2	yes 2	yes 2
DECT XQ	-	-	yes	yes	yes	yes
UTF-8 and	-	-	-	-	yes	yes
alphanumeric dialing
support
SIP–DECT XML	-	-	-	-	yes	yes
terminal API
CAT-iq 1.0 / Aastra	-	-	-	-	yes 4	yes 4
Hi-Q™ audio
technology

1There must be at least one RFP L35/36/37 IP or RFP L43 WLAN to host the OMM (2nd RFP for OMM standby).

2The feature requires a license and is not available for L-RFP installations which are using built-in licenses.

3This feature requires a license for standard RFP installations. There is a built-in license for L-RFP installation.

4The feature is available with the new RFP (L) 35/36/37 IP and RFP (L) 43 WLAN and the Aastra 650c handset (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.

Aastra

depl-1624/1.0

Page: 15 (241)

SIP–DECT OM System Manual Release 3.0	1 Overview

1.4About 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, and (since SIP–DECT 3.0) Aastra 650c.

Aastra 142d

Aastra 610d

Aastra 620d

Aastra 630d

Aastra 650c

Notes on the Aastra 142d handset

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)	Aastra 142d (global, all other countries)
Frequency Band 1920 to 1930 MHz (UPCS)	Frequency Band 1880 to 1900 MHz
60 duplex channels	120 duplex channels
100 mW (maximum output per active	250 mW (maximum output per active
channel)	channel)
5 mW (average output per active channel)	10 mW (average output per active channel)

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.

Notes on the Aastra 600d and Aastra 650c handsets

The Aastra 610d / 620d / 630d supports both the NA and EMEA regulatory requirements.

The new Aastra 600d handset firmware release 4.0 should to be used with Aastra 610d / Aastra 620d / Aastra 630d to support all SIP–DECT release 3.0 features. Note that SIP– DECT release 3.0 still supports the previous Aastra 600d handset firmware release 3.03 but with limitation; for example this handset firmware is incompatible with some of the new SIP– DECT release 3.0 features such as UTF-8.

The Aastra 600d firmware release 4.0 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

Aastra

depl-1624/1.0

Page: 16 (241)

SIP–DECT OM System Manual Release 3.0	1 Overview

•Support of SIP–DECT XML terminal interface

•Support of microSD card to save subscription data and the most important local device data (Aastra 620d / Aastra 630d)

•Additional subscription options

•Additional alarm melodies

•Profile indication in idle display

For more details please see /28/and /29/.

The Aastra 650c handset has the same feature set as the current Aastra 600d handsets. In addition to the Aastra 600d firmware release 4.0x feature set, the new Aastra 650c handset supports CAT-iq 1.0 and is thus capable to run G.722 (wideband) voice connections. For the full experience of wideband audio the handset hardware e.g. speakers, microphone, processor, have been improved.

Aastra

depl-1624/1.0

Page: 17 (241)

SIP–DECT OM System Manual Release 3.0	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.

Note: The DHCP/TFTP configuration described here can be used to operate current RFPs (RFP (L) 35/36/37 IP, RFP (L) 43 WLAN) together with older RFPs

(RFP (L) 32/34 IP, RFP (L) 42 WLAN). However, a more straightforward setup using the Java-based OpenMobility Configurator tool is described in the SIP–DECT: Installation & Administration Compendium document (see /24/).

Prerequisites

Some hardware and software prerequisites are to be met to follow this quick start guide:

•a licensed RFP device (e.g. RFP L35 IP),

•a PC to run a browser or start Java programs,

•two or more DECT handsets (preferably two Aastra 600d / 650c),

•OMM-SIP installation medium with software, such as the “iprfp3G.dnld” file,

•a Linux PC server for setting up DHCP/TFTP, HTTP and SNTP services required e.g. to update the RFP software,

•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 x86 server.

Tip: 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 “LiveCD” ISO files that are downloadable for free on the respective Linux vendor web sites.

IMPORTANT : The PC-OMM (OMM in host mode, see also chapter 9.11) is not supported on virtual machines due to specific real-time requirements.

2.1Setting 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 9.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 a TFTP server that offers the software file for the RFPs. For current RFPs (RFP (L) 35/36/37 IP and RFP (L) 43 WLAN), the TFTP server provides the software file for updates (“iprfp3G.dnld”). For older RFPs(RFP (L) 32/34 IP and RFP (L) 42 WLAN), the TFTP server provides the software file loaded during RFP startup (“iprfp2G.tftp”). The IP address and the software 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 software file and starts the program that is included in the software file.

Aastra

depl-1624/1.0

Page: 18 (241)

SIP–DECT OM System Manual Release 3.0	2 Getting Started

The following steps will start a Linux x86 server system where you can configure and run the DHCP/TFP server program.

1Start the Linux x86 server system. The Linux desktop should be displayed after start-up. The following screenshot depicts the situation if you start with a Live CD Linux (CentOS 6.2 to be precise).

CentOS LiveCD, copy files, calling up a terminal

2On the Linux x86 server system’s desktop, double click the OMM-SIP CD-ROM. Use drag & drop to copy the “iprfp3G.dnld”, “iprfp2G.tftp”, and “aafon6xxd.dnld” files to the Linux desktop.

3Start a terminal program. With Gnome desktop, select the Applications: Accessories: Terminal menu command.

4In the terminal program, you need to enter the following commands to switch off the firewall and to start the SSH service:

su –l	Starts a super user (“root”) shell.
ip -4 a	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	Optional: if the “eth0” adapter has no IP
ip l set dev eth0 up	address, you can assign the address
	manually.
/etc/init.d/sshd start	Starts the SSH service.
passwd centoslive	Set a (simple) password for the “centoslive”
	user.
iptables -F INPUT	Flush (clear) the INPUT firewall. Disable
echo 0 > /selinux/enforce	SELINUX that prevents TFTP downloads.

5From your working PC’s 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 Linux x86 server system. Log in as “centos” user with the password entered previously.

Aastra

depl-1624/1.0

Page: 19 (241)

SIP–DECT OM System Manual Release 3.0	2 Getting Started

Note, that it is now possible to use the clipboard to enter new commands and configuration file statements.

6 Enter the following commands to configure and start the DHCP/TFTP service:

su –l	Starts a super user (“root”) shell.
yum install dhcp tftp-server	Installs a DHCP and a TFTP server.
yum install nano	Installs the “nano” text editor.
cd /var/lib/tftpboot	Change the current directory.
cp -v /home/centoslive/Desktop/* .	Copy files here. (“iprfp3G.dnld”,
	“iprfp2G.tftp”, and “aafon6xxd.dnld” from the
	CD ROM). Mind the trailing dot in the
	command.
nano /etc/dhcp/dhcpd.conf	Start the “nano” text editor to change the
	“/etc/dhcp/dhcpd.conf” configuration file for
	the ISC DHCP daemon. 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.
/etc/init.d/dhcpd restart	Start the DHCP server.
chkconfig tftp on	Enable the TFTP server that is started from
/etc/init.d/xinetd restart	xinetd. Start the xinetd daemon after this.
tail -f /var/log/messages	View the system log for DHCP messages.

7Connect 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 DHCP messages that indicate the RFP DHCP queries.

DHCP Configuration File (/etc/dhcp/dhcpd.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. 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.

################################################

# dhcpd.conf sample configuration for SIP-DECT #

################################################

ddns-update-style interim; ignore client-updates; default-lease-time 86400; max-lease-time 86400;

### Define SIP-DECT options (incl. structure of option 43) ###

option space SIPDECT;
option SIPDECT.omm-ip	code	10	= ip-address;
option SIPDECT.omm-syslog	code	14	= ip-address;
option SIPDECT.omm-syslog-port code		15	= unsigned integer 16;
option SIPDECT.country	code	17	= unsigned integer 16;
option SIPDECT.ntpsrvname	code	18	= text;

Aastra

depl-1624/1.0

Page: 20 (241)

SIP–DECT OM System Manual Release 3.0			2 Getting Started
option SIPDECT.omm-ip2	code 19	= ip-address;
option SIPDECT.importurl	code 24	= text;
option magic_str	code 224		= text;
option tftp-list	code 150		= array of ip-address;
option vlanid	code 132		= unsigned integer 16;

### class definition ###

#RFP (L) 31,32,33,34,41,42 class "SIP-DECT2G" {

match if option vendor-class-identifier = "OpenMobility";

}

#RFP (L) 35,36,37,43, since firmware 3.0RC3

class "SIP-DECT3G" {

match if option vendor-class-identifier = "OpenMobility3G";

}

### subnet definition ###

shared-network SIP-DECT

{

subnet 192.168.112.0 netmask 255.255.255.0

{

pool {

range 192.168.112.52 192.168.112.55; allow members of "SIP-DECT2G";

allow members of "SIP-DECT3G";

option routers 192.168.112.1; option subnet-mask 255.255.255.0; option ntp-servers 192.168.112.109;

option domain-name-servers 192.168.112.1,8.8.8.8;

next-server 192.168.112.183; vendor-option-space SIPDECT;

option magic_str = "OpenMobilitySIP-DECT"; option SIPDECT.omm-ip 192.168.112.43;

#option SIPDECT.omm-ip2 192.168.112.52;

#option SIPDECT.country 1;

#option SIPDECT.omm-syslog 192.168.112.1;

if option vendor-class-identifier = "OpenMobility" { filename "/iprfp2G.tftp";

}

if option vendor-class-identifier = "OpenMobility3G" { filename "/iprfp3G.dnld";

}

# option tftp-server-name "tftp://192.168.112.183/subdir";

Aastra

depl-1624/1.0

Page: 21 (241)

SIP–DECT OM System Manual Release 3.0		2 Getting Started
	host OMM {
	hardware ethernet 00:30:42:12:6E:3B;
	fixed-address 192.168.112.43;
	}
}	# end of pool
} #	end of subnet
}

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 code 10 option of the DHCP vendor option 43. The OMM is generally selected

•via the DHCP request (see chapter 9.5.3.1),

•within the static local configuration of an RFP (see chapter 9.6),

•within the RFP configuration file of (see chapter 9.8).

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 9.13.

2.2Initial Setup

After starting 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.

1Start a web browser and navigate to the IP address that you have configured for the OMM in the code 10 option of the DHCP vendor 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.

2Enter “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.

Aastra

depl-1624/1.0

Page: 22 (241)

SIP–DECT OM System Manual Release 3.0	2 Getting Started

OMM web console, login with “omm” / “omm”

3On 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.

4Navigate to the System: System settings page. For a small, un-activated installation as it’s depicted here for evaluation purposes, change the PARK setting to the PARK code that is printed on the installation CD-ROM. If you upload a license/activation file instead, the PARK is changed to the value included with the uploaded file. Also change the Regulatory domain to match your region. Confirm with OK.

System: System settings, change PARK and DECT regulatory domain

WARNING: Please note that selecting the incorrect regulatory domain may result in a violation of applicable law in your country! If you install the system in North America for example, choose “US (FCC/IC)”.

Aastra

depl-1624/1.0

Page: 23 (241)

SIP–DECT OM System Manual Release 3.0 2 Getting Started

Note: The RFP L35 IP / RFP L36 IP / RFP L37 IP / RFP L43 WLAN and RFP L32 IP / RFP L34 IP / RFP L42 WLAN devices provide a built-in license as described here. If you have purchased another license type, you need to upload the license file on the Licenses page now (see chapter6).

5Navigate 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

6Click 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.

7Navigate 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.

Aastra

depl-1624/1.0

Page: 24 (241)

SIP–DECT OM System Manual Release 3.0	2 Getting Started

Portable parts, add new portable part

8Click 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.

9Navigate 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 Asterisk FreePBX with address 192.168.112.91 is used to provide the SIP PBX functions.

Aastra

depl-1624/1.0

Page: 25 (241)

SIP–DECT OM System Manual Release 3.0	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 part dialog. Change to User name and Password fields under the SIP authentication heading to the SIP account credentials configured on the PBX (see chapter 7.4.2 and chapter 7.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 9.13) or setting up the Download over Air software-update for Aastra 600d / 650c portable parts (see chapter 9.17).

Aastra

depl-1624/1.0

Page: 26 (241)

SIP–DECT OM System Manual Release 3.0	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.

Please note: Be aware that the majority of the new enhanced features require at least the following handset firmware releases

–600d: firmware release 4.00

–650c: firmware release 1.00

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

Download over Air

The Aastra 600d handset family and the Aastra 650c handset are able to download and upgrade its firmware via DECT over the air.

For the OMM running on an RFP the handset firmware packages are delivered in the package file “aafon6xxd.dnld” for the Aastra 600d handset family and the Aastra 650c handset. This package file must be put on the same server and path where the RFP gets a software image file for update purposes (e.g. iprfp3G.dnld).

The handset firmware packages are included in the OMM installation package for Red Hat© Linux for the Linux x86 server version of the OMM (e.g. SIP-DECT_3.0.bin).

Wideband (CAT-iq 1.0 / Aastra Hi-Q™ audio technology)

Together with the new RFP (L)35/36/37 IP and RFP (L) 43 WLAN, the Aastra 650c offers the possibility to act as Aastra Hi-Q audio terminal. This feature is realized using wideband speech according to CAT-iq.

Each Hi-Q connection uses, compared to conventional narrowband, the double capacity on the DECT air interface. Due to this fact, 4 Hi-Q connections (instead of 8) can be established via one RFP.

Aastra Hi-Q audio technology must be enabled or disabled per site (see chapters 7.5 and 8.6). 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 (L)35/36/37 IP or RFP (L) 43 WLAN.

Typically one site is identical with one cluster, i.e. all RFPs belonging to a specific site belonging to a specific cluster. However a site can have more than one cluster. The OMM does not refuse to configure one cluster which 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.

Aastra

depl-1624/1.0

Page: 27 (241)

SIP–DECT OM System Manual Release 3.0	3 Enhanced Feature Overview

RFP mixed installations

In sites (or whole systems) with disabled Hi-Q audio, an arbitrary mixture of

RFP (L) 32/34 IP / RFP (L) 42 WLAN and RFP (L) 35/36/37 IP / RFP (L) 43 WLAN is allowed. No further restrictions appear for mixed installations.

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 600d / Aastra 650c portable part at the expense of DECT channel capacity (see 9.3). Enable this feature for some or all of your RFPs (see chapter 7.6.3, “DECT settings” or chapter 8.7.1.2, “DECT tab”).

It is not possible to have DECT XQ audio combined with Hi-Q audio within the same connection.

Three operating modes regarding audio quality are selectable at the Aastra 650c handset: standard audio, Hi-Q audio and automatic.

•In case that an Aastra 650c operates in Hi-Q audio mode, it will exclusively establish wideband connections and not switch to narrowband later on. An Aastra 650c in this mode will ignore the XQ capability of the RFP.

•In case that an Aastra 650c operates in standard audio mode, it will exclusively establish narrowband connections and not switch to wideband later on. An Aastra 650c in this mode will switch to DECT XQ and back as necessary.

•In case that an Aastra 650c operates 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.

UTF-8

The UTF-8 support allows the presentation of a wider range of language specific characters e.g. umlauts and eases the internationalization/localization. Since SIP–DECT 2.1 the OMM and the Aastra 600d handset family support UTF-8 for text messaging.

With the SIP–DECT 3.0 the OMM and the Aastra 600d / 650c handsets support an extended character set for

•User parameter (configurable via WEB, OMP or external user configuration files)

–System name

–User name

–Number

•SIP “display names” und SIP “user id’s” of incoming and outgoing calls

•Call logs

•LDAP directory access

•XML terminal interface objects

Be aware that this feature needs at least following handset firmware releases:

•Aastra 600d: firmware release 4.00 or later

•Aastra 650c: firmware release 1.00 or later

Aastra

depl-1624/1.0

Page: 28 (241)

SIP–DECT OM System Manual Release 3.0	3 Enhanced Feature Overview

For 3-party GAP handsets, Aastra DECT 142 / Aastra 142d or Aastra 600d / 650c with older firmware releases, the UTF-8 character set is not supported. If possible, the OMM maps UTF-8 character to LATIN-1.

Please note: The actually available set of characters is defined by the handset. Please see /29/. Characters not supported by the Aastra 600d / 650c e.g. “ ” are replaced by “ ”.

User configuration files must be encoded in UTF-8.

Alphanumeric dialing

The SIP–DECT release 3.0 supports together with the new handset firmware releases Aastra 600d 4.00 and Aastra 650c 1.00 the dialing of alphanumeric characters. This allows in advance to the classical dialing of digits the dialing of names (e.g. “Heinrich.Mueller”).

If SIP URI dialing like “name@domain” shall be used please use an (outbound) proxy which supports the interpretation of SIP user names including domain names.

Digit treatment and UTF-8/alphanumeric dialing

The feature “Digit treatment” is designated to handle dialed digit strings only. It cannot be applied with SIP–DECT release 3.0 to UTF-8/alphanumeric dialing.

Voice mail number

A system-wide voice mail number can be configured within the system setting section. This number is used by the Aastra 600d / 650c handset family if a voice box call is initiated.

The system-wide voice mail number can be overruled by a user specific voice mail number.

If there is no voice mail number configured or another type of handset is used; then the voice mail number must be configured locally in the handset.

Please note: The voice mail number is supported by the external user data configuration files. The parameter UD_VoiceMailNumber can be set in the user_common.cfg and/or “user.cfg” or “LoginID.cfg” e.g. “UD_VoiceMailNumber=222”. For details please refer to: SIP–DECT; OM Handset Sharing & Provisioning; User Guide.

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 9.13).

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 9.2).

Aastra

depl-1624/1.0

Page: 29 (241)

SIP–DECT OM System Manual Release 3.0	3 Enhanced Feature Overview

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 7.6.3, “DECT settings” or chapter 8.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 8.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 9.6).

Wireless LAN (WLAN)

If you purchased a number of WLAN RFPs (RFP (L) 42 WLAN or RFP (L) 43 WLAN), the SIP–DECT system also provides access to your company LAN via Wireless LAN. The

RFP (L) 43 WLAN supports additionally 802.11n and 802.11a. The WLAN configuration of a group of WLAN RFPs is managed by WLAN profiles (see chapter 7.8).

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 9.10).

SIP–DECT release 3.0 is tested and released for Red Hat© Enterprise Linux 6 for x86 server.

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 /25/.

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 /26/.

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

Aastra

depl-1624/1.0

Page: 30 (241)