SIP–DECT OM System Manual Release 3.0 7 OMM Web Service RFP 42 WLAN profile configuration depl-1230/0.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service RFP 43 WLAN profile configuration 4 Change the desired settings of the WLAN profile. You need at last to define the ESSID setting. The different settings are explained in detail in the sections below. 5 Activate the Profile active setting, otherwise the WLAN profile is inactive which deactivates the WLAN function for RFPs that are assigned to this WLAN profile. 6 Press the OK button to apply the settings.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service General settings x Profile active: Activate this checkbox to activate the profile. This in turn activates the WLAN function for all RFPs that are assigned to the WLAN profile. x SSID: Enter a descriptive character string to identify the WLAN network (e.g. “OurCompany”).The service set identifier is broadcasted by the RFP within “WLAN beacons” in a regularly interval. The SSID identifies the WLAN network and is visible by all WLAN clients.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service x Interference avoidance (on / off, default: off): Enables a WLAN procedure to enhance radio interference avoidance. This setting applies to RFP (L)42 WLAN only. Security settings These settings determine the encryption used for the WLAN connection. Select one of the four modes (Open, WEP, WPA, or Radius). This will activate / gray-out the necessary additional input fields that specify further security settings on the WLAN profile page.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service - Value: You can enter a shared key as Text. Use a longer text sequence with alphanumeric characters and special characters to enhance the shared key strength. A text shared key is case sensitive. Alternatively, the shared key can be entered as Hex value (hexadecimal number, 0-9, a-f). Press the Generate button to generate a random shared key that matches the current settings. x 802.1x (Radius): This setting applies to RFP (L)42 WLAN only.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service 3 You can specify different authentication/encryption settings for each SSID section. For example, you can use WPA / Pre-shared key with different passwords. Note, that some configuration combinations are incompatible with multiple SSIDs. For example, the wireless hardware only manages a single WEP encryption key. Also, some features apply to all defined SSIDs, this includes the MAC access filters list.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service 7.8.1.3 Exporting WLAN Profiles To help simplify the configuration of wireless devices, you can export SSID configuration to a XML WLAN profile file. To export the configuration, please click on the icon. On Windows 7 you can use the command “netsh wlan add profile filename=xxx” to import a WLAN configuration. Many other tools to import WLAN configuration files are available for Windows Vista / Windows XP systems (for example wlan.
SIP–DECT OM System Manual Release 3.0 7.9.1 7 OMM Web Service “Digit treatment” Menu A number manipulation is provided by the digit treatment feature for LDAP corporate directories, that handles both incoming and outgoing calls (see chapter 7.9.2). LDAP A chosen number from a LDAP entry is checked against the external prefix pattern and if a pattern matches it is replaced by the configured internal prefix pattern. Only the best matching rule will be applied.
SIP–DECT OM System Manual Release 3.0 Note: 7 OMM Web Service To support digit treatment and overlap sending, it is necessary to have a dial terminator configured. The result of the conversion is not sent to the handset to be displayed or entered in the call log1. The following tasks can be performed on the Digit treatment page: x creating and changing “Digit treatment” entries (see chapter 7.9.1.1), x deleting “Digit treatment” entries(see chapter 7.9.1.2). 7.9.1.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service 6 Sites: Specifies the sites for which a rule shall be applied e.g. “1,2” (see chapter 7.5). If set to “0” the rule applies to all sites i.e. the rule will be applied to all calls or corporate directory requests. 7 Press the OK button. 7.9.1.2 Deleting “Digit treatment” Entries To delete an existing entry: 1 On the Digit treatment page click on the icon left behind the entry.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service The following tasks can be performed on the Directory page: x creating and changing LDAP entries (see chapter 7.9.1.1), x deleting LDAP entries(see chapter 7.9.2.2). 7.9.2.1 Creating and Changing LDAP Servers 1 To configure a new LDAP entry press the New button on the Directory page. To change the configuration of an existing entry click on the icon left behind the entry. The New LDAP entry resp. the Configure LDAP entry dialog opens.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service x Display type: Selection between the following two alternatives is possible: – Surname (sn), first name (given name) (default) – first name (Given name) and Surname (sn) x Server search timeout: The search results will be accepted within the entered search time (value range: 1 - 99 sec). The configuration is valid for all PP handsets which support the LDAP directory feature.
SIP–DECT OM System Manual Release 3.0 7 OMM Web Service 2 Activate the appropriate checkbox(es) to enable the corresponding FAC feature(s). For each enabled FAC feature enter an assigned access code. 3 Press the OK button. Afterwards the appropriate action can be performed by dialing the “FAC number” followed by the “FAC access code” en bloc from any subscribed DECT handset. In the example above a subscribed user can activate the OMM DECT subscription by dialing “9999*4701#” en bloc.
SIP–DECT OM System Manual Release 3.0 7.11 7 OMM Web Service “Info” Menu On the Info page, the End User License Agreement (EULA) is displayed. With the first login into a new SIP–DECT SW version, this page is displayed automatically and the user has to accept the EULA by pressing the Accept button. depl-1230/0.
SIP–DECT OM System Manual Release 3.0 8 8 OM Management Portal (OMP) OM Management Portal (OMP) The OM Management Portal (OMP) is a Java tool to manage the SIP–DECT solution. It can be used to view and configure OMM system data in the same way as the OM Web service. This section lists all parameters which can be configured and viewed using OMP. All parameters which are also accessible by the OM Web service are described in the appropriate OM Web service section (section 7).
SIP–DECT OM System Manual Release 3.0 8.2 8 OM Management Portal (OMP) Logout There is no automatically logout for the OMP. The user has to log out manually. To log out from the system: x click on the closing icon on the upper left in the upper right corner of the OMP window x or select the Exit entry from the General menu. Note: 8.3 If the OMM link is broken, the OMP asks if you want to reconnect to the OMM. In that case you have to enter the login data again.
SIP–DECT OM System Manual Release 3.0 x configuration mode, x monitor mode. 8 OM Management Portal (OMP) 2 – Main menus The OMP provides two main menus which are available in all program situations: x General menu, see chapter 8.11. x Help menu, see chapter 8.12. 3 – Navigation panel Both configuration and monitor mode contain a navigation panel. This panel contains the mode-dependant menu. 4 – Status bar The status bar is located at the bottom of the main window.
SIP–DECT OM System Manual Release 3.0 8.4 8 OM Management Portal (OMP) “Status” Menu The system status is displayed after startup of OMP. The Status panel provides information about the system health state. The following health state items are displayed: x Synchronization state: indicates the current synchronization state for all RFPs (see chapter 8.7.5). x Standby OMM: indicates if the status of the standby OMM (see chapter 9.13).
SIP–DECT OM System Manual Release 3.0 x 8.5 8 OM Management Portal (OMP) – OK; G.729 licenses are available “System” Menu The System menu allows to configure/view the global settings of the OMM. The systems settings are changeable in configuration mode. Change of some parameters can cause the OMM to be reset. In this case a new login is required. The System menu provides the following entries: 8.5.1 Configuration mode Monitor mode See chapter System settings System settings 8.5.
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) General For a description of the parameters which can be set in the General tab, please refer to the description of the System settings page of the OMM Web service (see chapter 7.4.1). The corresponding parameters can be found there in the General settings, Syslog, OM Integrated Messaging and Alerting service and Voice mail page sections.
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) Statistic counters beginning with “+” are counters which are taken over by standby OMM in case of a failover. All other counters will be reset to the defaults in case of a failover. For more details about the standby feature, see section 9.13. The following tasks can be performed: x Refresh all: request OMM update for all statistics counters. x Clear all: reset all statistics counters in OMM.
SIP–DECT OM System Manual Release 3.0 8.5.3 8 OM Management Portal (OMP) “SIP” Menu The SIP menu covers global settings for SIP signaling and RTP voice streams. The menu provides the settings in several tabs: Basic settings For a description of the parameters which can be set in the Basic settings tab, please refer to the description of the SIP page of the OMM Web service (see chapter 7.4.2).
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) DTMF settings For a description of the parameters which can be set in the DTMF settings tab, please refer to the description of the SIP page of the OMM Web service (see chapter 7.4.2). The corresponding parameters can be found there in the DTMF settings page section.
SIP–DECT OM System Manual Release 3.0 8.5.4 8 OM Management Portal (OMP) “User administration” Menu In the User administration menu you configure the OMM user accounts. User administration menu in configuration mode The 3 user accounts “Full access”, “Read-only” and “Root (ssh only)” available via the User administration page of the OMM Web service (see chapter 7.4.3) can also be configured in the OMP. These are 3 predefined user accounts, which cannot be removed or renamed.
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) 8.5.4.1 Creating New User Accounts It is possible to create additional user accounts (login and password) and to assign specific permissions. These accounts are mainly designed to have specific login data and permissions for applications which are using OM AXI to connect with the OMM. Note: Individual user accounts cannot be used for a login to the OMM Web service nor SSH.
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) Permissions The permissions for an individual user account can be set independent from any license status even if some of the permissions can only been used with an appropriate license. If an application connects with the OMM via OM AXI, then the permissions been sent from the OMM to the application is the result of the configured permissions for this account and the actual license status.
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) 8.5.4.4 Deleting User Accounts Deleting user accounts is only possible in configuration mode. To delete one or more existing user accounts proceed as follows: 1 Select the appropriate account(s) in the user account table by activating the corresponding checkbox(es). 2 In the Tasks bar click on the Delete command. 3 Confirm the displayed prompt with OK.
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) In the Automatic DB import panel 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 8 OM Management Portal (OMP) or the OM Configurator, the OMM tries to import a configured database file automatically during the OMM startup. 8 Click OK to confirm the settings for the automatic import. For further information on the automatic database import process please refer to the chapter 7.4.6.2. 8.5.5.2 “Automatic DB export” Tab The automatic database export feature allows an automatic database backup to an external server for each configuration modification.
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) 8.5.5.3 “User data import” Tab The user data import feature allows the import of user data from an external provisioning server. 1 Active: Activate this option to enable the user data import feature. 2 Protocol: Select the preferred protocol. 3 Server: Enter the IP address or the name of the server. 4 User name, Password: If necessary, enter the account data of the server. 5 Path: Enter the path which includes the user data.
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) 8.5.5.4 “Manual DB import” Tab Please note: A manual import of a database leads to a reset of the OMM to take effect. 1 Protocol: – To import a database from the file system the protocol FILE has to be selected. – To import a database from an external server select the preferred protocol (e.g. HTTP). 2 Server: Enter the IP address or the name of the external server.
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) 8.5.5.5 “Manual DB export” Tab 1 Protocol: Select the preferred protocol. If you want to export the database to the file system, select the FILE setting. 2 Server: Enter the IP address or the name of the server. 3 User name, Password, Password confirmation: If necessary, enter the account data of the server. 4 Directory (only if you have selected the FILE protocol): Select a directory by pressing the Directory button.
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) 8.5.5.6 “Maintenance” Tab In the Maintenance panel you can configure and start a system dump. A file “sysdump.txt” is created in the selected directory. Press the Directory button to select the directory. Then press the Download button to start the system dump. depl-1230/0.
SIP–DECT OM System Manual Release 3.0 8.6 8 OM Management Portal (OMP) “Sites” Menu RFPs can be grouped into different sites. The Sites menu allows to configure/view the configured sites. An empty system has one predefined site (ID: 1) named “default”. Minimum one site is required by the system. A site consists of the following parameters: x ID: 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.
SIP–DECT OM System Manual Release 3.0 Note: 8.7 8 OM Management Portal (OMP) Only sites without assigned RFPs can be deleted. “Radio fixed parts” Menu RFPs can be configured and viewed in the Radio fixed parts menu. The Radio fixed parts menu provides the following entries: 8.7.1 Configuration mode Monitor mode See chapter Device list Device list 8.7.1 Paging areas 8.7.2 Enrolment 8.7.3 Export 8.7.4 Sync view 8.7.5 Statistics 8.7.
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) x – DECT is not enabled and/or RFP not connected. x – DECT is enabled and RFP connected, but DECT has not been activated yet. x – DECT is enabled and RFP is connected, but RFP is not synchronized and searches for other synchronized RFPs. x Note: – DECT is enabled and RFP is connected and synchronized. If the Active column is not displayed, you can activate it in the Select columns dialog, see chapter 8.7.1.7.
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) Select columns: select columns/parameters to be shown in RFP table Select columns: select columns/parameters to be shown in RFP table 8.7.1.7 Filter: show only RFP datasets in table which contain a special search string Filter: show only RFP datasets in table which contain a special search string 8.7.1.8 8.7.1.1 RFP Detail Panel The RFP detail panel is used for configuration/showing of RFP settings and creation of new RFP datasets.
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) “DECT” tab This tab contains the RFP's DECT parameters. “WLAN” tab This tab contains the RFP WLAN parameters. Settings in the WLAN tab apply to RFPs of the type “RFP (L) 42 WLAN” and “RFP (L) 43 WLAN” only. “Hardware” tab In monitor mode this tab shows hardware information of the selected RFP. depl-1230/0.
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) RFP Hardware tab in monitor mode In configuration mode, the RFP hardware type can be set. 8.7.1.2 Adding New RFPs Adding new RFPs is only possible in configuration mode. To add an RFP to the list of known RFP proceed as follows: 1 In the task bar on the right of the Radio fixed parts panel click on the Create command. The New radio fixed part panel opens. It provides various tabs where the RFP data has to be entered, see chapter 8.7.1.1.
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) “DECT” tab x DECT activated: 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 Paging area: Enter the paging area, the RFP is assigned to. Note: The Paging area size is set in the DECT tab of the System settings menu (see chapter 8.5.1). The assignment between RFPs and paging areas can be changed in the Paging areas menu (see chapter 8.7.1.8).
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) 8.7.1.3 Changing RFPs Changing RFPs is only possible in configuration mode. To change the configuration of an existing RFP proceed as follows: 1 Select the appropriate RFP in the RFP table. 2 In the task bar on the right of the Radio fixed parts panel click on the Configure command. The RFP detail panel opens, see chapter 8.7.1.1. 3 Change RFP parameters, see parameter description in chapter 8.7.1.2. 4 Press the OK button. 8.7.1.
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) 8.7.1.7 Selecting Columns You can adapt the parameters shown in the RFP table to your needs: 1 In the task bar on the right of the Radio fixed parts panel click on the Select columns command. The Select columns dialog opens. 2 Select the columns that shall be shown by activating the appropriate checkboxes. 3 Click the OK button. The RFP table will be adapted accordingly. 8.7.1.
SIP–DECT OM System Manual Release 3.0 8.7.2 8 OM Management Portal (OMP) “Paging areas” Menu The Paging area menu shows all configured RFPs in a tree structure consisting of two trees: x The left Unassigned RFPs tree contains all RFPs without an assigned paging area. x The right Paging areas tree shows all configured paging areas with RFPs assigned to these paging areas. All RFPs are shown including their site and optional hierarchy (building, floor, and room) settings.
SIP–DECT OM System Manual Release 3.0 8.7.3 8 OM Management Portal (OMP) “Enrolment” Menu The Enrolment menu allows import of RFP datasets using a configuration file. For information about required configuration file format see chapter 11.7.2. 1 Press the File button. A file system dialog opens in which you can select the configuration file. 2 To check the results from reading the configuration file press the Show log file button. In case of file format errors these errors are listed here.
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) Show status: show import status of a selected RFP dataset. If enrolment failed for this RFP, a message describing the enrolment error is shown. 8.7.4 “Export” Menu The Export menu allows export of all RFPs enrolled to the OMM into an file using “*.csv” file format. The created file can be viewed externally with a standard spreadsheet application. All enrolled RFPs are shown in a table.
SIP–DECT OM System Manual Release 3.0 8.7.5 8 OM Management Portal (OMP) “Sync view” Menu The Sync view menu allows to check the synchronization relations between RFPs in a graphical manner. Note: For background information on RFP synchronization please refer to chapter 9.2. To open the task panel for sync view press the arrow icon in the upper right corner of the sync view panel. The task panel is displayed on the right.
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) x Activate RFP mouse menu in sync view: Press the right mouse button while mouse cursor is on an RFP icon and select the Activate Monitoring command from the context menu. The color of the RFP icon indicates synchronization state of that RFP: x Grey: inactive x Red: not synchronized x Yellow: searching x Green: synchronized Sync relations between RFPs are represented by arrows.
SIP–DECT OM System Manual Release 3.0 8.7.6 8 OM Management Portal (OMP) “Statistics” Menu The Radio fixed parts > Statistics menu provides information about RFP statistics counters. It contains: x an overview panel with all statistics counters (see chapter 8.7.6.1) and x several statistics group panels. In these groups statistics counter types which are related are pooled together (see chapter 8.7.6.2). The menu is only available in monitor mode. 8.7.6.
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) The detail panel for selected statistics counter shows values for total occurrence and occurrence in current and last week. You can clear the selected statistics counter on the selected RFP by pressing the Clear button. 8.7.6.2 RFP Statistics Group Panels The RFP statistics group panels divide RFP statistics counters into logical groups. This allows to view all statistics counters of a special group of all RFPs in one table.
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) x Clear RFP: clear all counters of selected RFP.
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) PP overview in configuration mode The Active column shows the following states: x - PP is not subscribed to the system. x - PP is subscribed to the system. Note: depl-1230/0.2 If the Active column is not displayed, you can activate it in the Select columns dialog, see chapter 8.8.9. To view the user-device-relation, ensure that the User ID and Device ID columns are also activated.
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) PP overview in monitor mode The tasks which can be performed are mode-dependant. Configuration mode Monitor mode See chapter Create: create new fixed PP dataset in detail panel 8.8.5 Configure: configure selected PP user and device dataset in detail panel 8.8.6 Show details: show selected PP user and device dataset in detail panel 8.8.
SIP–DECT OM System Manual Release 3.0 table which contain a special search string 8 OM Management Portal (OMP) table which contain a special search string Log events: enable/disable PP event log 8.8.2 8.8.11 “Users” Menu In the Users panel, all PP user data are listed in a table. The Users panel allows to create (unbound) users (which should be able to login and logout at a device). Note: Use the Select columns dialog (see chapter 8.8.9) to display the desired PP user data.
SIP–DECT OM System Manual Release 3.0 8.8.3 8 OM Management Portal (OMP) “Devices” Menu In the Devices panel, all PP device data are listed in a table. The Device panel allows to configure the DECT part of a PP device dataset. Devices can not be created separately. They will be automatically created during subscription (unbound) or they will be created fixed bound to a user when a user is created in the Overview submenu (see chapter 8.8.1). Note: Use the Select columns dialog (see chapter 8.8.
SIP–DECT OM System Manual Release 3.0 8.8.4 8 OM Management Portal (OMP) PP Detail Panel The PP detail panel is used for configuration/showing of PP settings and creation of new PP datasets. To call up the PP detail panel x choose one of the commands in the task bar on the right of the Portable parts panel (Create, Configure, or Show details) or x select the appropriate PP in the PP table and double-click the entry. The PP detail panel contains the different parameter groups sorted in tabs.
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) x User name: The SIP Authentication user name is optional but recommended. It represents the name which will be used during SIP registration and authentication. If no name is given the number will be used by default. x Password, Password confirmation: The password will be used during SIP registration and authentication. Enter the appropriate data in these fields. “DECT” tab This tab enables to configure the DECT part for the PP dataset.
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) x Delete subscription: This option is only available when configuring an existing PP. If this option is activated, the subscription data will be deleted which also requires a resubscription of the handset device. “Messaging” tab This tab enables to configure the OM Integrated Messaging and Alerting service for the PP dataset.
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) x Tracking: If this option is enabled, the operator of the OM Locating application is able to use the constant tracking feature for the portable part. Note, that this feature consumes more of the portable part’s battery power, because it activates an RFP update information if the device roams and is not in communication. You also cannot enable this feature, if the Locatable option is disabled.
SIP–DECT OM System Manual Release 3.0 8.8.5 8 OM Management Portal (OMP) Creating PP Datasets Creating PP datasets is only possible in configuration mode. You can create the fixed PP dataset or only the PP user data. To create a PP dataset proceed as follows: 1 In the task bar on the right of the Portable parts panel click on the Create command. – In the Overview submenu you can now create a fixed PP dataset (with combined user and device data). – In the Users submenu you can create an unbound user.
SIP–DECT OM System Manual Release 3.0 8.8.8 8 OM Management Portal (OMP) Deleting PP Datasets Deleting PP datasets is only possible in configuration mode. You can delete the fixed PP dataset (in case of fixed relation) or only the PP user data resp. the PP device data (in case of dynamic relation). To delete one or more existing PP datasets proceed as follows: 1 Select the appropriate PP dataset(s) in the PP table by activating the corresponding checkbox(es).
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) The Filter dialog opens. 2 Enter the search string that serves as filter criterion. You can enter digits and characters. The search is case sensitive. 3 Click on the Filter button. The Filter dialog is closed and the PP table will be adapted accordingly. 4 To reset the filter, click on the Filter command in the task bar on the right of the Portable parts panel. 5 In the Filter dialog click on the Reset button. 8.8.
SIP–DECT OM System Manual Release 3.0 8.9.1 8 OM Management Portal (OMP) “General settings” Menu The General settings menu allows to configure/view the FAC number prefix used for feature access codes and alarm triggers. 1 FAC number and prefix for alarm triggers: Enter a unique FAC number. 2 Press the OK button. 8.9.2 “Feature access codes” Menu The Feature access codes menu is used to configure/view the feature access codes parameters. depl-1230/0.
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) The FAC number which introduces the feature access code (see also chapter 8.9.1) is displayed. For a description of the parameters which can be set in this menu see chapter 7.9.3. 8.9.3 “Alarm triggers” Menu The Alarm triggers menu allows to configure/view numerous alarm trigger datasets. There are two predefined alarm triggers (‘SOS and ’Man down‘) which can not be deleted. depl-1230/0.
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) The following tasks can be performed: x Create: create alarm trigger (see chapter 8.9.3.1). x Configure: configure a selected alarm trigger (see chapter 8.9.3.2). x Delete: delete selected alarm triggers (see chapter 8.9.3.3). x Show details: shows parameters of a selected alarm trigger (see chapter 8.9.3.4). 8.9.3.1 Creating “Alarm triggers” In configuration mode you can create new alarm triggers. 1 Click Create.
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) 3 Feature access code: Enter the access code which should be assigned to the alarm trigger. 4 Comment: Enter a comment for the new trigger. 5 Prefix: This field displays the FAC number which introduces the feature access code (see also chapter 8.9.1). 6 Number: Enter the number to be called in case of this alarm trigger. 7 Press the OK button. 8.9.3.
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) For a description of tasks and parameters available in this menu, refer to chapter 7.9.1. depl-1230/0.
SIP–DECT OM System Manual Release 3.0 8.9.5 8 OM Management Portal (OMP) “Directory” Menu The Directory menu allows to configure the LDAP corporate directory services. For a description of tasks and parameters available in this menu, refer to chapter 7.9.2. 8.9.6 “XML applications” Menu The SIP–DECT XML terminal interface allows external applications to provide content for the user on the DECT handsets Aastra 600d / Aastra 650c display and much more.
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) to “automatic” or “PBX” on the handset in the settings / list access menu. If the list access is is set to “local”, the local list are used by the handset. An activated hook becomes available on a handset (incl. the cooresponding menu entry) after the next DECT location registration of the handset. This can be foreced by switching the handset off and on. The same applies if a hook shall be deactivated.
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) 8.9.6.1 Creating a New XML Hook Besides the 5 predefined XML hooks you can create up to 10 additional XML hooks. Adding individual XML hooks is only possible in configuration mode. To add an XML hook proceed as follows: 1 In the Tasks bar click on the Create command. The New XML application panel opens. 2 Configure the XML hook, see parameter description below. 3 Press the OK button.
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) Please note: The 5 predefined XML hooks cannot be renamed. 8.9.6.3 Viewing XML Hook Details You can view the configuration of an XML hook in monitor mode. Proceed as follows: 1 Select the appropriate XML hook in the table. 2 In the Tasks bar click on the Show details command. The user account data is displayed in the user account detail panel. 3 To close the XML hook detail panel press the Cancel button. 8.9.6.
SIP–DECT OM System Manual Release 3.0 8.10 8 OM Management Portal (OMP) “License” Menu The License panel provides an overview on the currently used licenses. In configurator mode you can also import an activation or a license file: The license information is displayed in the following tabs: x General: shows general license status. x System: shows system license status. x Messaging: shows Integrated Messaging and Alerting Service (IMA) license status. x Locating: shows Locating license status. x G.
SIP–DECT OM System Manual Release 3.0 8 OM Management Portal (OMP) x Options: Selecting this menu entry opens the Options dialog (see below). “Options” dialog, “General” tab Language: You can select the OMP language. After changing the language, the OMP is automatically closed and has to be started again. The field User directory shows the path where the following files are saved if necessary: x System dump file “sys_dump.txt” x Expert console log file “spy.
SIP–DECT OM System Manual Release 3.0 8.12 8 OM Management Portal (OMP) “Help” Menu The Help menu is available in all program situations. It contains following submenus: x Expert console: Selecting this menu entry enable/disables the expert console. The expert console allows to trace OMP messages and to check the messages sent and received from the OMM. The expert console will be opened in a secondary window. x Info: Selecting this menu entry displays the End User License Agreement (EULA).
SIP–DECT OM System Manual Release 3.0 9 9 Configuration und Administration Aspects Configuration und Administration Aspects This chapter provides detailed information on various configuration and administration aspects regarding the SIP–DECT solution. 9.1 IP Signaling and Media Stream To establish a call between an IP Phone and a PP (e.g. Aastra 620d), the following IP streams must be established: x A signaling channel to and from the SIP phone. x A signaling channel to and from the OMM.
SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects A call from one PP to another that resides on the same RFP will loop back within the RFP if no media gateway is involved. So the call will not pass through to the Local Area Network (LAN). Although the voice packets will not impact LAN traffic, signal packets will. If the PP user is moving, the PP detects that another RFP has a better signal strength and, therefore, it starts the handover process.
SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects As the PP user moves into the next RFP zone of coverage, the PP detects that the RFP has a better signal strength. Again the media stream from the SIP phone cannot move to the secondary RFP, so the primary RFP uses the LAN to direct the voice to the new secondary RFP. 9.
SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects As long as an RFP is not in sync, no calls can be established using this RFP. If an RFP loses the synchronization, the RFP does not accept new calls (“busy bit”). There is a delay of maximum 3 minutes until the active calls on this RFP are finished. Then it tries to get synchronized again.
SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects - If no message was received within the 30 seconds this stage will be terminated and the next stage will be started. - If no preferred RFP was configured, this stage will be ignored. x Synchronization stage 1 - If a preferred RFP was determined in stage 0, this one will be the synchronization source for the next upcoming RFPs.
SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects Whenever the busy state is announced a log entry is made to the system logs. If the announcement of busy raises in a specific area, a further RFP should be installed to double the number of media streams available for calls. Notes on Hi-Q connections Each Hi-Q connection uses, compared to conventional narrowband, the double capacity on the DECT air interface.
SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects RFP (L) 35/36/37 IP or RFP (L) 43 WLAN uses the internal flash to start the boot image. A fileserver is only needed for software update over the network, please see chapter 9.11.5. The essential network settings can be alternatively: x Communicated by a DHCP server at startup time. x Configured on the RFP with the OM Configurator tool (see chapter 9.6).
SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects Application startup After starting the application image the RFP checks the local network settings in its internal flash memory once again. If no settings are available or if they are disabled, it starts a DHCP client to determine the IP address of the OMM and other application startup settings.
SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects x VLAN-ID optional x TFTP server list optional 9.5.3.1.
SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects 9.5.3.3 Booter Update Each application SW comes with the latest released booter SW. The application SW will update the booter automatically. Please note: After an upgrade from an older OpenMobility Release (< 2.0) to an OpenMobility Release 2.x the booter of the RFPs will be updated to Version 3.4.x. The OpenMobility Configurator 2.x is required to configure RFPs with this new booter version.
SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects Vendor specific options The Vendor Specific Options consist of: Vendor Specific Option Meaning Length Mandatory option 10 ommip1: Used to select the IP-RFP who should reside the Open Mobility Manager (OMM). 4 yes option 14 syslogip: IP address of a Syslog Daemon 4 no option 15 syslogport: Port of a Syslog Daemon 2 no option 17 Country: Used to select the country in which the OMM resides.
SIP–DECT OM System Manual Release 3.0 9 Netherlands 10 Czechoslovakia 11 Austria 12 Denmark 13 Slovakia 14 Finland 15 Hungary 16 Poland 17 Belarus 18 Estonia 19 Latvia 20 Lithuania 21 Ukraine 22 Norway 24 Sweden 25 Taiwan 100 North America 101 France 102 Australia 9 Configuration und Administration Aspects 9.5.4.2 Configuration using DHCP The DHCP client of the RFP familiy requests serveral parameters that are used to configure the RFP.
SIP–DECT OM System Manual Release 3.
SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects LED 1 Info / Booter; LED 2 System; LED 1 Info / Booter; LED 2 System LED 3 DECT; LED 4 (unused) LED 3 DECT; LED 4 WLAN The following tables show the LED status of an RFP according to the different states. A red respectively orange colored field in the table means that the LED glows permanently in red or orange. A split field with e.g.
SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects The following table illustrates the different meaning of the LEDs while the booter is active. LED1 (INFO) Booter LED2 (OMM / SYSTEM) LED3 (DECT) LED4 (WLAN) cont. Power connected cont. cont. 1s 1s 1,9s 0,1s 0,25s 0,25s 0,25s 0,25s 0,25s 0,25s 0,25s 0,25s 3,9s 0,1s cont. cont. Wait for OMM Configurator Input DHCP cont. cont. cont.
SIP–DECT OM System Manual Release 3.0 LED1 (INFO) 9 Configuration und Administration Aspects LED2 (OMM / SYSTEM) 1,85s LED3 (DECT) LED4 (WLAN) OMM connection failure (idle loop) 0,15s Up&Running (OMM connected) cont. 1,85s 0,15s Up&Running + OMM warning 1,85s 0,15s Up&Running + OMM failure RFP DECT DECT not configured on this RFP cont. DECT inactive (not synced yet) 1,85s 0,15s cont DECT 'on air' 1,85s 0,15s DECT + call active 1,85s 0,15s DECT + call active +busy bit RFP WLAN cont.
SIP–DECT OM System Manual Release 3.0 LED1 (INFO) 0,9s 9 Configuration und Administration Aspects LED2 (OMM / SYSTEM) LED3 (DECT) LED4 (WLAN) external configuration failure 0,1s cont. 1,9s RFP general Ready Ready + OMM reside on this RFP 0,1s 1s 1s 1,9s 0,1s OMM connect phase OMM connection failure (idle loop) Ready (OMM connected) cont. 1,9s 0,1s Ready + OMM has a warning 1,9s 0,1s Ready + OMM has an error RFP DECT DECT not configured on this RFP cont.
SIP–DECT OM System Manual Release 3.0 9.
SIP–DECT OM System Manual Release 3.
SIP–DECT OM System Manual Release 3.0 Note: 9 Configuration und Administration Aspects An initial configuration of the RFPs (L) 35/36/37 IP / RFP (L) 43 WLAN via the OM Configurator tool requires a login and password. The default login and password is “omm” and “omm”. No login is required for the initial configuration of the previous RFP family (RFPs (L) 32/34 IP / RFP (L) 42 WLAN. With the launch of SIP–DECT 3.
SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects On systems with multiple Ethernet adapters select the interface to use for the configuration of the RFPs. To configure an RFP, at least the MAC address and all mandatory options (see table below) have to be set. The MAC address must be entered in a format such as xx-xx-xxxx-xx-xx. If the RFP has already an IP address, enter this address in the IP address field.
SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects TFTP Server Address Only mandatory for RFP (L) 32/34 IP / RFP (L) 42 WLAN because of the NETBOOT process; Optional for RFP (L) 35/36/37 IP / RFP (L) 42 WLAN SW update IP address of the TFTP server, set to 0.0.0.
SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects chapter 8.5.5.1) Configuration file server optional URL of a server with configuration files (ipdect.cfg|.cfg) alternatively/in addition to OM Configurator settings.
SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects Use the Scan button to search for available RFPs in the local LAN segment or via the proxy mechanism in outside LAN segments. All MAC addresses of the found RFPs will be displayed in the left RFP list. The status LEDs and the update button are disabled after scanning for RFPs. The list of RFPs could be saved by using the Save RFPs button.
SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects The prepared configuration file can be loaded using the Load config. button. Log files with status information about parsing and executing the configuration file and data are stored into the same directory. Use the Run configs button to start the iterative configuration of multiple RFPs using the prepared and loaded configuration file. The LEDs will display whether the configuration has succeeded or failed.
SIP–DECT OM System Manual Release 3.0 9.8 9 Configuration und Administration Aspects RFP Configuration Files RFP (L) 35/36/37 IP / RFP (L) 43 WLAN configuration files A new configuration parameter specifies the location of the software that will be installed into the flash of an RFP (L) 35/36/37 IP / RFP (L) 43 WLAN and activated by the OpenMobility Manager. OM_SwImageUrl=ftp://172.30.207.21/openmobility/SIP-DECT_3.0.
SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects x “.cfg” is mandatory if it is indicated in the “ipdect.cfg” that a “.cfg” exists for the RFP. (There is a key word to indicated that a “.cfg” exists for every RFP.) Mandatory means: if a file can not be loaded then the RFP will not start. This is relevant for the following scenarios: x RFP boot / startup (after power on, SW update, …) , x a change of the URL.
SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects Configuration files are read by the RFP application at the following times: x RFP reboot, x Restart of an application e.g. OMM, x DHCP renew and DHCP bound, x Configuration changes via OM Configurator, x RFP configuration file update check.
SIP–DECT OM System Manual Release 3.
SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects software intact. After successful installation the OMM is informed about the different software. Activation of the software is then managed by the active OMM. RFPs that do not have a connection to the OMM activate and start the software immediately. Locations for SW update are: x Attached USB mass storage device with a software image iprfp3g.dnld in its root.
SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects supports only one VLAN ID in both directions. That means the VLAN ID in receive direction has to be the same as in send direction. 9.10.1 Boot Phase of IP RFPs (DHCP) Because the IP RFP does not know about VLAN during the beginning of the start up, two DHCP scopes are required. This applies regardless of the Ethernet switch being used.
SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects Please note: Check that the versions of the OMM and RFP software on your SIP–DECT installation are the same. Note that the OMM in host mode is not supported on virtual machines. 9.11.1 System Requirements The Linux PC OMM requires the following configuration: x Red Hat© Enterprise Linux 6 for x86 server x Server HW minimum: - Processor : Dual Core Intel® Xeon® 3065, 2.
SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects For an OMM software update (see chapter 9.12) rpm –U SIP-DECT-OMM-.i586.rpm For Aastra 610d/620d/630d and Aastra 650c handset software installation rpm –i SIP-DECT-HANDSET-.i586.
SIP–DECT OM System Manual Release 3.0 9.11.3 9 Configuration und Administration Aspects Configuring the Start Parameters The basic data for initializing OMM is stored in the file “/etc/sysconfig//SIP-DECT”. It can be edited to modify the OMM interface. ############################################## # OMM configuration file ############################################## # if you use a different interface for omm activate/correct parameter below #OMM_IF="eth0" # OMM_CONFIG_FILE=/opt/SIP-DECT/tmp/omm_conf.
SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects To delete the OMM configuration remove the OMM configuration file “/opt/SIPDECT/tmp/omm_conf.txt” (by default). 9.11.5 Upgrade from OMM Version 2.x to 3.x in Host Mode To update a OMM system from version 2.x to 3.x, you must delete the old OMM software package rpm –e omm_ffsip-OMM omm_ffsip-HANDSET and install the SIP-DECT_3.0.bin software. In this case the installation routine copies automaticly the OMM database.
SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects OMM in RFP mode If the OMM is running on an RFP force the update of this RFP by pressing the Update button on the System settings web page (see chapter 7.4.1.2). The RFP checks the boot image file on the TFTP server and reboots if a new one is found. OMM in host mode (on Linux PC) If the OMM is running on a dedicated Linux PC, install the new software as described in section 9.11.2 on that PC with the command “SIP-DECT_3.0.
SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects c) Start the OMM service. d) Wait at least 30 seconds before you go on with updating the active OMM. 3 Manually update the active OMM. a) Stop the OMM service. b) Install the new SW. c) Wait at least 30 seconds. d) Start the OMM service. Please note: A one by one update of RFPs is not possible if the signaling interface between the OMM and the RFP has been changed. Please see the release notes delivered with the software.
SIP–DECT OM System Manual Release 3.0 9.13.1 9 Configuration und Administration Aspects Configuring OMM Standby Each RFP of the DECT system have to be configured with two OMM IP addresses. This both OMM addresses can be either configured via DHCP (see chapter 9.5.1) or with the OM Configurator (see chapter 9.6). 9.13.2 Fail Over Situations Fail over occurs under following circumstances: x An OMM error occurs on the active OMM.
SIP–DECT OM System Manual Release 3.
SIP–DECT OM System Manual Release 3.0 9.13.4 9 Configuration und Administration Aspects Specific Standby Situations Some aspects have to looked at in case of OMM state changes when they are unsynchronized. 9.13.4.1 How A Standby OMM Becomes Active As the above figure shows in case of an unsynchronized OMM state the standby OMM has to decide whether to become active or not. For this purpose the OMM tries to contact the configured SIP proxy and registrar.
SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects x They lose their RFP base station and search the DECT network without finding another one: - active calls are broken; - PPs stay in searching for network until an air interface is available again. Note: Handover between PPs located to RFPs which are controlled by different OMMs is not possible. When the OMMs get in contact again with each other this inconsistent OpenMobility system situation will end. 9.
SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects x Read-only access: As the name suggests this access type is not allowed to configure any item of the OMM installation. This access type can only be used on the OM Web service. The account can be deactivated. The factory setting for this account is Name: 'user' Password: 'user' Active: 'yes x Root (SSH only) access: This access type is only applicable on the SSH interface of an RFP.
SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects 0x31: SPAIN Spain 0x32: FRANCE France 0x40: MKK Japan 0x41: MKK1 Japan (MKK1) This setting depends on the country and is prescribed by the laws of that country. Only the setting prescribed for that country must be used. The third step is to specify the WLAN parameters in a profile (see chapter 7.8.1). The WLAN profile determines the name (SSID) of the WLAN network and other parameters.
SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects throughput, especially in environments where reflection and attenuation cause problems for HF. Fragmentation Threshold In environments where there is lot of interference and poor radio quality, reducing the fragment size below 1500 bytes can improve the effective throughput. However, transmitted data frames have to be fragmented, which means a higher load on the RFP’s processor.
SIP–DECT OM System Manual Release 3.0 9.15.3 9 Configuration und Administration Aspects Securing the WLAN In order to ensure that communication in the WLAN network is secure, several measures need to be taken. Firstly, data packets transmitted via the openly visible radio interface must be encrypted, and secondly, all WLAN components that provide services should have to authenticate themselves. There are different encryption methods available which you configure within the WLAN profile (see chapter 7.8.
SIP–DECT OM System Manual Release 3.0 9.17 9 Configuration und Administration Aspects Download Over Air The “Download Over Air” feature allows updating the handset firmware without any user interaction or interruption of the telephony services over the existing DECT air interface. This features is currently available for the handset types Aastra 600d and Aastra 650c. The PP firmware is part of each OpenMobility software package which is delivered by Aastra.
SIP–DECT OM System Manual Release 3.0 9.17.2 9 Configuration und Administration Aspects How to configure “Download Over Air” In the following, the configuration of the “Download Over Air” feature is described by using the OM Web service. The feature can also be configured using the OM Management Portal (OMP). Therefore, links to the corresponding OMP settings are also given, but without screenshots. The “Download over Air” feature can be activated or deactivated on the System Settings” web page.
SIP–DECT OM System Manual Release 3.0 9 Configuration und Administration Aspects The handset firmware container for handset firmware update over the air includes packages for the Aastra 600d and Aastra 650c handsets. The available versions are also displayed on the Status web page. Please note: The entry of “Loading firmware from” on the OpenMobility Manager Status web page is only updated on restart of the OpenMobility Manager.
SIP–DECT OM System Manual Release 3.0 - 9 Configuration und Administration Aspects Impossible to download the firmware to that handset (e.g. noAastra 610d/620d/630d/650c) The PP is paged to establish a download connection. In case of a successful connection establishment the PP calculates the number of bytes to download. This may last several seconds. xx kbytes left The download is ongoing and xx kbytes are left. The firmware of this PP is up to date.
SIP–DECT OM System Manual Release 3.0 10 Maintenance 10.1 Site Survey Measurement Equipment 10 Maintenance If a SIP–DECT installation has to be planned, a sufficient distribution of the RFPs is necessary which fulfills the requirements for reliable synchronization and connectivity to the Portable Parts. The site survey kit may help you. It comprises: x One measuring RFP with its own power supply. x A tripod and a battery for the RFP. x Two reference PPs with chargers. x Battery chargers.
SIP–DECT OM System Manual Release 3.0 10 Maintenance PARK: 1F-10-FF-F0-21 RFPI RFP ID: 02* 10FFF21 02 Frame error FE PP: FP: Field strength -dBm 50 57 RFP ID RPN 02 01 00 Menu 50 Phonebook RFP ID: 02* *The ID of RFP to which the PP is currently associated to. In this example the PP is currently connected to the RFP with the number 02. The RFPs 01 and 00 are also visible.
SIP–DECT OM System Manual Release 3.0 10 Maintenance 1 Press the Menu soft key. 25 Enter the following key sequence “R***76#”. 26 Select Auto Answer. 27 Press OK. 28 Enter a number of seconds the phone shall ring before it will answer the call. 29 Press OK. 30 Enter a number of seconds a call shall be active. 31 Press OK. The test will be started automatically. 32 To stop the test switch the phone off and on again. 10.3.
SIP–DECT OM System Manual Release 3.0 10.3.5 10 Maintenance SSH user shell Each RFP offers a lot of commands within the SSH shell. Most of them are useful for diagnostic and may help experts to resolve failures. Note: Some commands can harm the system operation. The SSH access of an RFP is open if x the RFP is connected to an OMM and the “Remote Access” is switched on or x the RFP is not connected to an OMM.
SIP–DECT OM System Manual Release 3.0 10 Maintenance 10.3.5.
SIP–DECT OM System Manual Release 3.0 10 Maintenance 10.3.5.4 RFP Console Commands If you type ip_rfpconsole you are able to use the following commands on each RFP: Command Description ? Displays Command Help Table help Displays Command Help Table logger Send a string to the syslog daemon deftrc Resets all trace settings to default dsp Shows channel config dump Creates system state dump file /tmp/sys_dump.txt.
SIP–DECT OM System Manual Release 3.0 10 Maintenance 10.3.5.
SIP–DECT OM System Manual Release 3.
SIP–DECT OM System Manual Release 3.0 10.3.7 10 Maintenance DECT Monitor Please note: The DECT Monitor has been replaced by OMP but the DECT Monitor can still be used without warrenty for SIP–DECT installations with a standard PARK and up to 256 RFPs’ all within paging area 0. For a better error detection in the SIP–DECT system the DECT Monitor can be used. The DECT Monitor is an MS Windows based stand alone program.
SIP–DECT OM System Manual Release 3.0 10 Maintenance The DECT monitor program is used together with the SIP–DECT system. When the program is started, the user is requested to enter the IP address of the IP DECT RFP or the server running the OpenMobility Manager (OMM) software. There can be several reasons for an unsuccessful link establishment: x Operation of DECT monitor is not enabled inside the OMM. Use the OMM web service to enable DECT monitor operation. x IP address is not correct.
SIP–DECT OM System Manual Release 3.0 10 Maintenance x The Location Registration and Detach events are displayed in the tables for approx. 1-2s after their occurrence (light green background), if possible. There is no display in the FP table if there is no column free for display. If the event has already been displayed, it can be overwritten at any time. The events are not displayed if they occur during an on-going transaction.
SIP–DECT OM System Manual Release 3.0 10 Maintenance depl-1230/0.
SIP–DECT OM System Manual Release 3.0 11 Appendix 11.1 Declaration of Conformity 11 Appendix The CE mark on the product certifies its conformity with the technical guidelines for user safety and electromagnetic compatibility, valid from the date of issue of the relevant Declaration of Conformity pursuant to European Directive 99/5/EC. The Declaration of Conformity can be viewed on the Aastra homepage. 11.2 Communications Regulation Information for Aastra 142d, Aastra 600d 11.2.1 FCC Notices (U.S.
SIP–DECT OM System Manual Release 3.0 11 Appendix This device and its antenna must not be co-located or operating in conjunction with any other antenna or transmitter. This EUT has been shown to be capable of compliance for localized specific absorption rate (SAR) for uncontrolled environment/general population exposure limits specified in ANSI/IEEE Std. C95.1-1992 and had been tested in accordance with the measurement procedures specified in FCC/OET Bulletin 65 Supplement C (2001) and IEEE 1528-2003.
SIP–DECT OM System Manual Release 3.0 11 Appendix particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures: x Reorient or relocate the receiving antenna. x Increase the separation between the equipment and receiver.
SIP–DECT OM System Manual Release 3.0 11.4 11.
SIP–DECT OM System Manual Release 3.0 11 Appendix Asterisk Asterisk is a complete Open Source PBX in software. It runs on Linux, BSD and MacOSX and provides many features. Asterisk supports voice over IP in many protocols, and can interoperate with almost all standards-based telephony equipment. Base station Please see: RFP or Radio Fixed Part DECT Digital Enhanced Cordless Telecommunication The standard (ETS 300 175) essentially specifies the air interface, known as the radio interface.
SIP–DECT OM System Manual Release 3.0 IPEI 11 Appendix International Portable Equipment Identity - 13-digit identification code for PPs - Example: 00019 0592015 3 (the final digit is the checksum). - The code is represented in decimal form. - This code is globally unique. PARK Portable Access Rights Key Access code for the Portable Part. This code determines whether a PP can access a particular DECT system.
SIP–DECT OM System Manual Release 3.0 11.
SIP–DECT OM System Manual Release 3.0 11 Appendix x Instruction settings are made like: = . x Data sequence sections starts with the key word “data_sequence”. This key word is always mandatory to proceed the file. All instructions have to be written before this row. x Data sequence record fields are separated by colon “;”. Colons have also to be set for empty fields if at least one follows which is not empty. Otherwise a position mismatch of fields will occur.
SIP–DECT OM System Manual Release 3.0 11 Appendix 4 IPEI 5 Additional ID 6 Sip user name 7 Sip password 8 SOS number 9 Mandown number 10 Locatable (ignored by Web import and always set to “inactive”) 11 Localization (ignored by Web import and always set to “inactive”) 12 Tracking (ignored by Web import and always set to “inactive”) 13 Description1 (ignored by Web import and always set to “”) 14 Description2 (ignored by Web import and always set to “”) 11.7.1.
SIP–DECT OM System Manual Release 3.0 11 Appendix start_number = 5401 no_of_number = 10 ac = 1001 additional_pin = number sip_user = number sip_pw = number sos_number=5002 mandown_number=5002 # # # # # # # # # # # # # # # # # ---------------------# data sequence: ---------------------# 1. number 2. name 3. AC 4. IPEI 5. additionalId 6. SIP user 7. SIP password 8. sos no 9. mandown no 10. locatable (ignored by Web import and always set to inactive) 11.
SIP–DECT OM System Manual Release 3.0 11 Appendix 11.7.2.1 Supported Instructions All instructions are taken as common value which are set to all records of data sequence section of that file if the corresponding field is empty. Instruction Explanation active Activation of DECT: {‘0’ or ‘false ’= inactive, ‘1’ or ‘true’ = active } cluster Cluster, the RFP is referred to - RFP-OMM: {1..256}, PC-OMM: {1..2048} paging_area Paging area, the RFP is referred to: {‘unassigned, ’0’..
SIP–DECT OM System Manual Release 3.0 11 Appendix 11.7.2.3 Example The following screenshot shows an RFP enrolment data import dialog that is shown if the corresponding configuration file is imported.
SIP–DECT OM System Manual Release 3.0 11 Appendix ############################################################################## data_sequence ############################################################################## #MAC address;Name;DECT activated;DECT cluster;Paging area;Preferred sync.; #Reflective env.
SIP–DECT OM System Manual Release 3.0 11.7.3 11 Appendix RFP Configuration File / Local (OM Configurator) 11.7.3.1 Supported Instructions All instructions are taken as common value which are set to all records of data sequence section of that file if the corresponding field is empty.
SIP–DECT OM System Manual Release 3.0 11 Appendix 37 TFTP server 38 TFTP_FILE 39 OMM IP address 40 IP address of backup OMM 41 Default gateway 42 DNS server 43 DNS domain 44 NTP server IP address 45 NTP server name 46 Syslog daemon IP address 47 Syslog listen port 48 Core 49 Use VLAN 50 Server list 51 Broadcast address 52 VLAN Id 53 Country code 54 Preferred TFTP server 55 Import URL 56 Configuration file server 11.7.3.
SIP–DECT OM System Manual Release 3.0 11 Appendix import_url = https://server/importfiles/ommxy_conf.gz config_file_server = https://server/configfiles/ # --------------# # data sequence # # --------------# # 1. MAC_ADDR ! no instruction supported ! # 2. ACTIVE_FLAG # 3. RFPADDR ! no instruction supported ! # 4. NET_MASK # 5. TFTP_SERVER # 6. TFTP_FILE # 7. OMM1 # 8. OMM2 # 9. GATEWAY #10. DNS_SERVER #11. DNS_DOMAIN #12. NTP_ADDR #13. NTP_NAME #14. SYSLOG_ADDR #15. SYSLOG_PORT #16. CORE #17. USE_VLAN #18.
SIP–DECT OM System Manual Release 3.0 11 Appendix […] RFP configuration: […] 11.8 RFP Export File Format General RFP export files are created by OMM Management Portal in ‘csv’-file format which can be easily viewed by a spreadsheet application.
SIP–DECT OM System Manual Release 3.0 11 Appendix # WLAN channel # WLAN power # WLAN activated # ################################################## MAC address;Name;DECT activated;DECT cluster;Paging area;Preferred sync.;Reflective env.
SIP–DECT OM System Manual Release 3.0 11.
SIP–DECT OM System Manual Release 3.
SIP–DECT OM System Manual Release 3.0 12 12 Index Index 802.1Q support .................................... 182 Configuration tools................................. 30 Aastra 142d ........................................... 15 OM Configurator .............................. 171 Auto answer test mode .................... 203 OM Management Portal (OMP) ......... 94 Auto call test mode .......................... 203 OMM Web service ............................. 41 Checking firmware ..................
SIP–DECT OM System Manual Release 3.0 12 Index Fragmentation threshold...................... 196 Alarm triggers .................................. 142 G.729 codec .......................................... 34 Enabling (OMM Web service) ............ 46 GAP phones .......................................... 16 Enabling (OMP) ................................. 99 Hi-Q™ audio technology........................ 26 PP settings (OMP) ........................... 136 Host mode ...............................
SIP–DECT OM System Manual Release 3.0 12 Index Modes ................................................ 95 SIP authentication (OMM Web service) ....................................................... 72 Options ............................................ 151 SIP authentication (OMP) ................ 134 OpenMobility Manager................see OMM SOS number (OMM Web service) ..... 72 Outdoor RFPs.................................... 8, 10 SOS number (OMP) ........................
SIP–DECT OM System Manual Release 3.0 12 Index RFP 36 IP / RFP L36 IP......................... 10 Standby OMM........................................ 28 RFP 37 IP / RFP L37 IP......................... 10 Configuration ................................... 190 RFP 42 WLAN / RFP L42 WLAN............. 8 Installation update............................ 188 RFP 43 WLAN / RFP L43 WLAN........... 10 OMM Console Commands .............. 209 RFP software update ........................... 181 Overview........
SIP–DECT OM System Manual Release 3.0 depl-1230/0.2 12 Index QoS settings ...................................... 84 Security settings ................................ 83 Radius settings .................................. 84 XML applications ...........................
