SIP–DECT OM System Manual Release 3.0 SIP–DECT OM System Manual Installation, Administration, and Maintenance Release 3.0 Document ID: depl-1230 Version: 0.2 Aastra Deutschland GmbH Zeughofstr. 1 10997 Berlin, Germany ¤ 2012 - All Rights Reserved 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.
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) ........................................................................................8 1.2.
SIP–DECT OM System Manual Release 3.0 7.7 7.6.2 OMM / RFP SW Version Check ...................................................................................64 7.6.3 Creating and Changing RFPs.......................................................................................64 7.6.4 Importing RFP Configuration Files ...............................................................................67 7.6.5 Capturing RFPs ....................................................................................
SIP–DECT OM System Manual Release 3.0 8.7.4 8.7.5 8.7.6 “Export” Menu .............................................................................................................124 “Sync view” Menu .......................................................................................................125 “Statistics” Menu.........................................................................................................127 8.7.6.1 8.7.6.2 8.8 8.9 Table of Contents RFP Statistics Overview.........
SIP–DECT OM System Manual Release 3.0 Table of Contents 9.10 802.1Q SUPPORT .....................................................................................................................182 9.10.1 Boot Phase of IP RFPs (DHCP) .................................................................................183 9.10.2 Boot Phase of IP RFPs (Local Configuration) ............................................................183 9.11 INSTALLING OMM IN HOST MODE.............................................
SIP–DECT OM System Manual Release 3.0 11.7.1.2 11.7.1.3 Table of Contents Data Section Fields ................................................................................................. 221 Example .................................................................................................................. 222 11.7.2 RFP Configuration File / Central (OMM Database)....................................................223 11.7.2.1 11.7.2.2 11.7.2.3 Supported Instructions .........................
SIP–DECT OM System Manual Release 3.0 1 1 Overview 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 219.
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.
SIP–DECT OM System Manual Release 3.0 1 Overview 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.
SIP–DECT OM System Manual Release 3.0 1 Overview 1.2.1.2 New RFP Types (Since SIP–DECT Release 3.0) With SIP–DECT release 3.
SIP–DECT OM System Manual Release 3.0 1 Overview x supports 1GBit Ethernet x supports CAT-iq 1.0 level high definition voice for the new Aastra 650c handset family x hardware is ready to support Secure SIP and SRTP with a SIP–DECT 3.0 follow-up release x uses an external 48V DC Power Supply (if no PoE available) which fulfils the latest environmental requirements, i.e. EOP step 2 level 5 x The RFP 43 WLAN supports the 802.11n standard. x The RFP 43 WLAN can house the OMM.
SIP–DECT OM System Manual Release 3.0 Note: 1 Overview 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. When you decide to run an RFP-based OMM, you should be sure that the maximum number concurrent calls will not exceed <= 100 in your DECT network. 1.3 About the OpenMobility Manager With SIP–DECT 3.
SIP–DECT OM System Manual Release 3.0 1 Overview 3rd party Alarm Server Call Manager SIP LDAP Server OM Management Portal 3rd party Message Server OM Integrated Messaging & Alerting Service WEB service OM Locating Server OMM OM Locating Client ...
SIP–DECT OM System Manual Release 3.0 1.3.3 1 Overview Feature/Handset GAP 142d 600d 1 650c Locating yes yes yes enhanced locating features yes enhanced locating features DECT XQ no no yes yes UTF-8 and alphanumeric dialing support 2 no no yes yes SIP–DECT XML terminal API 2 no no yes yes CAT-iq 1.0 / Aastra Hi-Q™ audio technology 2 no no yes no 1 requires Aastra 600d firmware release 4.00 or higher 2 new with SIP–DECT 3.
SIP–DECT OM System Manual Release 3.0 Feature/SW Release 1 Overview Release 1.8 RFP OMM Linux x86 Release 2.1 RFP OMM server OMM CAT-iq 1.0 / Aastra Hi-Q™ audio technology - - Linux x86 Release 3.0 or later RFP OMM server OMM - - Linux x86 server OMM yes yes 1 There must be at least one RFP L35/36/37 IP or RFP L43 WLAN to host the OMM (2nd RFP for OMM standby). 2 The feature requires a license and is not available for L-RFP installations which are using built-in licenses.
SIP–DECT OM System Manual Release 3.0 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. 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 firmware release 4.
SIP–DECT OM System Manual Release 3.0 2 2 Getting Started 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 35/36/37/43 together with older RFPs 32/34/42.
SIP–DECT OM System Manual Release 3.0 2 Getting Started the “Bridged Mode” which allows the virtual machine to receive/answer DHCP broadcasts on the physical Ethernet adapter. Activating bridge mode with VirtualBox 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.
SIP–DECT OM System Manual Release 3.0 2 Getting Started 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 “iprfp3g.dnld”, “iprfp2g.tftp”, and “aafon6xdd.dnld” files to the Linux desktop. 3 Start a terminal program. With Gnome desktop, select the Applications: Accessories: Terminal menu command.
SIP–DECT OM System Manual Release 3.0 2 Getting Started 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 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.
SIP–DECT OM System Manual Release 3.0 2 Getting Started option SIPDECT.importurl code 24 = text; option magic_str option tftp-list option vlanid code 224 = text; code 150 = array of ip-address; 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.
SIP–DECT OM System Manual Release 3.0 2 Getting Started 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 “DHCP option 43”. The OMM is generally selected x via the DHCP request (see chapter 9.5.3.1), x within the static local configuration of an RFP (see chapter 9.
SIP–DECT OM System Manual Release 3.0 2 Getting Started 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.
SIP–DECT OM System Manual Release 3.0 2 Getting Started 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.
SIP–DECT OM System Manual Release 3.0 2 Getting Started 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 800 PBX with address 192.168.112.91 is used to provide the SIP PBX functions.
SIP–DECT OM System Manual Release 3.0 3 3 Enhanced Feature Overview 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.
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.
SIP–DECT OM System Manual Release 3.0 3 Enhanced Feature Overview For 3-party GAP handsets, 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 600d/650c e.g. “↪” are replaced by “ ”. User configuration files must be encoded in UTF-8.
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”).
SIP–DECT OM System Manual Release 3.0 3 Enhanced Feature Overview 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 /27/. SIP–DECT XML terminal interface The SIP–DECT XML terminal interface allows external applications to provide content for the user on the DECT handsets display and much more. The list of potential applications is endless.
SIP–DECT OM System Manual Release 3.0 3 Enhanced Feature Overview x a web-based service (OMM Web service, see chapter 7) and x a java-based tool (OM Management Portal, OMP, see chapter 8). 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.
SIP–DECT OM System Manual Release 3.0 4 4 Naming Convention Naming Convention The naming convention used with SIP–DECT 2.1 or earlier for software deliverable is unified with SIP–DECT 3.0. This applies for the software packaged for the RFPs as well as for the Red Hat© Linux x86 server packages. SW package Old New Recommended standard name in SIP–DECT installations SW image for RFP (L) 32/34 IP / RFP (L) 42 WLAN omm_ffsip.tftp SIPDECT_.tftp iprfp2g.
SIP–DECT OM System Manual Release 3.0 5 5 Login and Passwords Login and Passwords Interface/Tool OMM RFP (L) 32/34 IP / RFP (L) 42 WLAN RFP (L) 35/36/37 IP / RFP (L) 43 WLAN Initial configuration via OM Configurator login / password n.a. No login required “omm” / “omm” “omm” / “omm” Initial OMM configuration via Web or OMP standard fullaccess account login / password n.a. n.a. OMM access via Web Read-only or fullor OMP access accounts as configured (after initial OMM n.a. n.a.
SIP–DECT OM System Manual Release 3.0 6 Licensing 6.1 Licensing Model 6 Licensing Starting with SIP–DECT release 2.1 several features of the Open Mobility system are licensed: x the system size concerning the number of configured RFPs, x the software version running the OMM, x the messaging application, and x the locating application. For information on the messaging and locating application please refer to the appropriate documents listed in the section 11.6 References.
SIP–DECT OM System Manual Release 3.0 6 Licensing Additionally the OMM can operate in a demonstration mode. Update License Updates from release 2.1 to 3.0 need an update license. A free update license can be received up to one year after the initial SIP–DECT 2.1 license activation. After this time an update license is required. 6.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).
SIP–DECT OM System Manual Release 3.0 6.1.2 6 Licensing License Violations and Restrictions A license can be violated in three ways: x 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.
SIP–DECT OM System Manual Release 3.0 6 Licensing resources are temporarily free (condition: number of G.729 licenses >0 (built-in or license file). 6.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 7.10) or via the OMP (see chapter 8.9.6).
SIP–DECT OM System Manual Release 3.0 6.4 License Modes 6.4.1 Small System 6 Licensing When changing the PARK on the System settings page of the OM Web service, the OMM uses the built-in license resp. the standard license for a small system. The built-in license for a small system features: x up to two L-RFPs - messaging restricted to type “Info”, “Low”, “Normal” and “High” for all user (no “Emergency” and “Locating Alert”), and - no locating.
SIP–DECT OM System Manual Release 3.0 6 Licensing The OMM prevents a license violation due misconfiguration e.g. it is not possible to configure a 21st RFP in the system. 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. While obtaining an activation file from the Aastra license server it is possible to enter the PARK used for a small system installation.
SIP–DECT OM System Manual Release 3.0 6 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: depl-1230/0.2 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.
SIP–DECT OM System Manual Release 3.0 7 7 OMM Web Service 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.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service x Sites menu: allows to group RFPs into different sites, see chapter 7.5; x Radio fixed parts menu: allows configuration and administration of the attached RFPs, see chapter 7.6; x Portable parts menu: allows administration of the PPs, see chapter 7.7; x WLAN menu: allows configuration of WLAN parameters, see chapter 7.8; x System features menu: allows administration of system features like digit treatment and directory, see chapter 7.
SIP–DECT OM System Manual Release 3.0 7.4 7 OMM Web Service “System” Menu The System menu comprises general parameters to configure and administrate the system parameters of the SIP–DECT solution. 7.4.1 “System settings” Menu The system settings cover global settings for the OpenMobility Manager. The following tasks can be performed: x configuring the global settings (see the following description in this section), x updating the OMM (see chapter 7.4.1.2), x restarting the OMM (see chapter 7.4.1.1).
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service The following parameters can be set: General settings x System Name: Enter the system name. x Remote Access: Switches on/off the SSH access to all RFPs of the DECT system. For more information on the SSH access see chapter 10.3.5. Net parameters To allow the prioritization of Voice Packets and/or Signaling Packets (SIP) inside the used network the IP parameter ToS (Type of Service) should be configured. depl-1230/0.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service x ToS for voice packets: Determines the type of service (ToS resp. DiffServ) byte of the IP packet header for all packets that transport RTP voice streams. x ToS for signalling packets: Determines the type of service (ToS resp. DiffServ) byte of the IP packet header for all packets related to VoIP signaling. x TTL (Time to live): Determines the maximum hop count for all IP packets.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service Voice mail Voice mail number: You can configure a system wide voice mail number. This number is used by the Aastra 600d / Aastra 650c handset family if the voice box is called. OM Integrated Messaging and Alerting Service The OpenMobility Manager provides a integrated message and alarm server, which could be activated/deactivated and configured here. For a detailed description see /26/.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service A reset web page is loaded then displaying a progress bar and the login web page is loaded automatically if the OMM is reachable again. 7.4.1.2 Updating the OMM If the OMM is running on an RFP, the Update button is available on the System settings web page. After pressing the Update button, the RFP residing the OMM checks whether a new boot image file is available on the TFTP server or not. For more details about updating the OMM see the section 9.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service The following parameters can be set: Basic settings x Proxy server: IP address or name of the SIP proxy server. If a host name and domain are used for the proxy server parameter, ensure that a DNS server and a domain are specified for your SIP–DECT system via DHCP or the OM Configurator tool. x Proxy port: SIP proxy server’s port number. Default is 5060. To enable DNS SRV support for proxy lookups, use a value of “0” for the proxy port.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service x Registrar server: IP address or name of the SIP registrar. Enables the PPs to be registered with a Registrar. If a host name and domain are used for the proxy server parameter, ensure that a DNS server and a domain are specified for your SIP–DECT system via DHCP or the OM Configurator tool. x Registrar port: SIP Registrar’s port number. Default is 5060. To enable DNS SRV support for registrar lookups, use a value of 0 for the registrar port.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service RTP settings x RTP port base: Each RFP needs a continuous port area of 68 UDP ports for RTP voice streaming. The RTP port base is the start port number of that area. Default is 16320. x Preferred codec 1 – 4: Specifies a customized codec preference list which allows you to use the preferred codecs. The Codec 1 has the highest and Codec 4 the lowest priority. Note: With SIP–DECT Release 3.0 the voice codecs G.722 (wideband), G.711 u-law, G.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service Registration traffic shaping Allows to limit the number of simultaneous SIP registrations at startup/fail over of the OMM. If activated, it prevents bursts of SIP registration during startup/fail over of the OMM. x Active: The registration traffic shaping mechanism can be switched off/on herewith. x Simultaneous Registrations: The maximum number of simultaneously started registrations.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service These settings which are case sensitive can be changed on the User administration web page. 1 Account type: Select the account type you wish to change. 2 Active: This setting applies to the Read-only access account. Using this account, a user is not allowed to configure any item of the OMM installation. The account can be deactivated. 3 User name: If desired, enter a new user name.
SIP–DECT OM System Manual Release 3.0 7.4.4 7 OMM Web Service “Time zones” Menu On the Time zones page, the OMM provides all available time zones. They are set with their known daylight savings time rules adjusted to the Universal Coordinated Time (UTC) per default. The difference to the UTC time is shown in the UTC difference column. In case of a configured daylight savings time rule (DST column) this is also marked for each time zone.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service 7.4.4.2 Resetting Time Zones To reset individual time zone settings, press the Default button on the Time zone web page. This sets all time zones back to the default values and deletes the changed time zone rules in the configuration file. 7.4.5 “SNMP” Menu To manage a larger RFP network, an SNMP agent is provided for each RFP. This will give alarm information and allow an SNMP management system (such as “HP Open View”) to manage this network.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service The following parameters can be configured using the OMM web service: General settings x Read-only community: The SNMP community strings forms a password that is sent by the SNMP management system when querying devices. The query is answered only if the SNMP community string matches. You may use “public” as a default keyword for readonly access. x System contact: Enter a descriptive text that typically is displayed in the SNMP management software.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service 7.4.6.1 Manual Database Import Please note: A manual import of a database leads to a reset of the OMM to take effect. In the Manual import section of the DB management page enter the following: 1 Protocol: – To import a database from the Web browser’s file system the protocol FILE has to be selected. – To import a database from an external server select the preferred protocol (e.g. HTTP).
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service In the Automatic import section of the DB management page enter the following: 1 Startup only: Activate this option if the import should be started for an initial configuration. 2 Startup and periodically: If this option is activated, the OMM tries to import the configured database file during startup and at the configured time of day. 3 Time: Enter the time, the import should be started.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service The automatic OMM database import allows to change all configuration settings but not the account settings and the PARK. There is only one exception: changing the default user account and the PARK for an initial configuration is possible. After the initial configuration, the user account settings and PARK can only be changed via the Web service on the target OMM itself. 7.4.6.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service change, then no backup will be done. A backup file will be overwritten during a day if there is more than one modification. A new file will be created when this first change occurs at the day. Please note: For an automatic database export a time synchronization with an NTP server is mandatory. For NTP server configuration see chapter 9.5.4 and chapter 9.6.
SIP–DECT OM System Manual Release 3.0 7.4.7 7 OMM Web Service “Event log” Menu The Event log page displays important event information on OMM system functions, e.g. security aspects. A more detailed system log can be obtained by configuring the Syslog function in the System settings menu, see chapter 7.4.1. To clear the display, press the Clear button. 7.5 “Sites” Menu RFPs can be grouped into different sites. A site consists of the following parameters: x ID: Identification number of the site.
SIP–DECT OM System Manual Release 3.0 7.5.1 7 OMM Web Service Creating a New Site 1 On the Sites page press the New button. The Configure site dialog opens. 2 ID: Enter the identification number of the site. A value between 1 and 250 is possible. If no value is given, the OMM selects the next free ID. 3 Name: Enter the name of the site. 4 Hi-Q Technology: The capability Hi-Q ¥ audio technology must be enabled or disabled for each site specifically.
SIP–DECT OM System Manual Release 3.0 7.6 7 OMM Web Service “Radio fixed parts” Menu On the Radio fixed parts page, all configured RFPs are listed in tables. The RFPs are sorted by their Ethernet (MAC) addresses. You can select a sorting criterion for the RFP table. In the Sorted by field, select the criterion: x DECT clusters: The RFPs are sorted by clusters. All used clusters are displayed in the navigation bar on the left side. The OMM RFP of each cluster is marked with a bold font.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service x importing RFP configuration files (see chapter 7.6.4), x capturing RFPs (see chapter 7.6.5), x deleting RFPs (see chapter 7.6.6). 7.6.1 States of an RFP For each RFP the state of the DECT subsystem is displayed. These states are: Synchronous The RFP is up and running. The RFP recognizes and is recognized by other RFPs in its cluster through its air interface and delivers a synchronous clock signal to the PPs.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service The RFP was configured but has not connected to the OMM yet. Therefore the IP address column is empty. SW Update available The RFP is connected to the OMM. On the TFTP server has found a new software. The RFP is waiting that the OMM initiates a reboot. In the meantime is the RFP full operational. 7.6.2 OMM / RFP SW Version Check When the RFPs are connecting the OMM they submit their SW version.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service RFP 42 configuration RFP 43 configuration 2 Configure the RFP, see parameter description below. 3 Press the OK button. The following parameters can be set in the New radio fixed part resp. the Configure radio fixed part dialog: General settings x MAC address: Each RFP is identified by its unique MAC address (6 bytes hex format, colon separated). Enter the MAC address, it can be found on the back of the chassis.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service DECT settings The DECT functionality for each RFP can be switched on/off. x DECT cluster: If DECT is active the RFP can be assigned to a cluster. x Preferred synchronization source: Activate this checkbox if the RFP should be used as synchronization source for the other RFPs in the cluster. For background information on RFP synchronization please refer to chapter 9.2. x Reflective environment: Within areas containing lot of reflective surfaces (e.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service x Output power level (default: “Full”): Determines the signal power level used by the RFP to send WLAN data. You may limit the power level to minimize interferences with other WLAN devices. The actual power level is also capped by the WLAN Regulatory domain setting on the System settings page. x HT40 (RFP 43 WLAN only): High throughput mode with 40 MHz bandwidth increases data rate up to 300 Mbit/s. 7.6.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service 4 Select the RFPs you want to add to the OMM database by selecting the appropriate checkboxes. 5 Press Add. All successfully stored records are marked green in the Added column. Failed records are marked with a red star. 6 To read error hints in the referring log file, press the Log file button. Error hints can also be read in a syslog trace (see chapter 7.4.1). 7 To remove imported data entries, activate the check box next to the desired entries.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service 1 On the Radio fixed parts page press the Start button. After a while the list page is filled by the MAC addresses of those RFPs which tried to register to the OMM (unregistered RFPs). Note: Please note that these entries are not really stored (they are lost after reset). 2 By pressing the customize icon of the appropriate RFP, you can add further data and store the RFP (see chapter 7.6.3). 7.6.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service x IPEI: Indicates the PP' IPEI. x Subscribed: Indicates if the PP subscribed to the system. x Download: This column is only presented if the “Download over Air” feature is started successfully and gives information about the download status of the handset SW (see chapter 9.17).
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service 2 Configure the PP, see parameter description below. 3 Press the OK button. The following parameters can be set in the New portable part resp. the Configure portable part dialog: General settings x Name: The name parameter represents the SIP Display Name field. This parameter is optional but recommended. x Number: The number is the SIP account number or extension for the PP. x IPEI: The IPEI is the DECT handset IPEI number.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service x SOS number, ManDown number: SOS and ManDown are calling numbers which will be automatically called as soon as an SOS or ManDown event happens. If no individual SOS or ManDown number is configured for a handset the number of the appropriate alarm trigger will be used as calling number in case of a SOS or ManDown event. Please see chapter 8.9.3 and /28/ for details.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service 4 Select the PPs you want to add to the OMM database by selecting the appropriate checkboxes. 5 Press Add. depl-1230/0.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service All successfully stored records are marked green in the Added column. Failed records are marked with a red star. 6 To read error hints in the referring log file, press the Log file button. Error hints can also be read in a syslog trace (see chapter 7.4.1). 7 To remove imported data entries, activate the check box next to the desired entries. Press Delete to remove the selected entries. 7.7.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service Note: To ease the first installation of a DECT system, the subscription is enabled permanently while at least one PP (with IPEI) is set up within the database and no PP is subscribed. After successful subscription of the first PP the subscription will still be enabled for 24 hours. Note: To allow an unbound device subscription, the Auto-create on subscription flag must be set with the help of the OM Management Portal (OMP). Please see chapter 8.5.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service 7.7.3.1 Subscription with Configured IPEI The PP data to be assigned to the subscribing PP are identified by the IPEI. Furthermore the IPEI leads to a further guarantee not to receive none authorized subscriptions even if AC is not set as a mean to achieve security. To enable subscriptions, press the Start button of the section Subscription with configured IPEIs on the Portable parts page.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service 1 On the Portable parts page click on the Search button. The Search portable parts dialog opens. 2 Enter the handset’s number or IPEI. At least one parameter has to be set. The entered number or IPEI has to match exactly with a handset’s number or IPEI. If number and IPEI are given then a handset has to exist in the OMM’s database whose number and IPEI match both otherwise the search fails.
SIP–DECT OM System Manual Release 3.0 7.8 7 OMM Web Service “WLAN” Menu The WLAN menu allows you to manage the wireless LAN function of all WLAN capable RFPs that are connected to the OMM. You can view and change wireless parameters and security settings to adapt the WLAN configuration to suit your needs. You can also check how many and which wireless clients are currently connected. Nevertheless, the WLAN function is only available for devices of the type RFP L42 WLAN and RFP L43 WLAN.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service 7.8.1.1 Creating and Changing WLAN Profiles You need at least one active WLAN profile in order to operate the WLAN function for an RFP (L)42 WLAN or RFP (L)43 WLAN device. 1 Navigate to the WLAN profiles page. This page shows the number of existing WLAN profiles and a list of available WLAN profiles. 2 If you create a new WLAN profile, configure the RFP type first to get the correct input fields.
