Configuring Aastra SIP-DECT Solution with 3CX Phone system
pixel500w-500x1
Zero Admin
With the new Dashboard
pixel500w-500x1
Bulletproof Security
With SSL certs and NGINX
pixel500w-500x1
Install on $100 Appliance
Intel MiniPC architecture
pixel500w-500x1
New, Intuitive Windows Client
More themes, more UC
pixel500w-500x1
More CRM Integrations
Scripting Interface to add your own
pixel500w-500x1
Improved Integrated Web Conferencing
iOS and Android apps included
pixel500w-500x1
Personal Click2Meet URLs

Configuring Aastra SIP-DECT Solution with 3CX Phone system

Please Note: The Aastra series of IP phones are no longer supported for 3CX Phone System. This page is here for documentation purposes only. Check out the 3CX supported IP phones at the bottom of this page or on the 3CX Support page.

IMPORTANT This guide has been tested with the following:

OMM version 1.6.6
Software version 91.24.32.2
Hardware version number 1.11.11
Base Station Aastra RFP L32 IP (indoor)

Be aware that different firmware revisions may have different web interface formats and functionality.

  1. Plug the Aastra Basestation into a POE switch or use the power supply attached. The POE switch must be IEEE 802.af compliant.
  2. Create a DHCP reservation on the DHCP server. Otherwise use the OM Configurator Tool. You will need the following:
    a) TFTP server
    b) Open Mobility Configurator tool
    c) Java Runtime Environment version 1.4 or higher for OM configurator tool
    You can download the OM tool and the tftp image from the following location:
    http://www.aastra.com/cps/rde/xchg/SID-3D8CCB6A-6B487CC0/04/hs.xsl/21410.htm
    or you can use the tool provided – OMM Activation CD.
  3. Assigning an IP address to the RFPThere are 2 ways – the first is creating a DHCP reservation. In the reservation also include the Boot Server Host Name [tftp server ip] and the Bootfile name [omm_ffsip.tftp].The second way is using the OM Configurator tool. The instructions below will explain how to achieve a local configuration of the RFP.Using the OM configurator tool – Once you have installed Java on your machine, open OM_Configurator.jar using Java and the following screen will be displayed.
    Figure 1: OM configuration toolSet Use Local Configuration – Set this to “Yes”. If the Yes checkbox is selected, DHCP will be disabled and the IP Address will be assigned statically to the RFP.
    Enter the IP address you want to assign to the RFP and proceed with the Subnet mask.
    Enter the TFTP server IP address (you can use Pumpkin by Klever) and under TFTP file name insert the application image downloaded with the OM tool – omm_ffsip.tftp.
    Finally insert the OMM IP address. Please read the documentation by Aastra for further information about RFP and OMM. This is important when you have more than one RFP. In this case this single RFP will be assigned as the OMM in your SIP-DECT network.Click on “Send Configuration”. The Configuration will be sent to the RFP.Place the application image in the TFTP directory. Start TFTP server.

    The RFP will request the image from the TFTP server. Once access is granted, the firmware will be loaded. The first LED will blink red.

    In a single RFP scenario, it is important that the RFP is an OMM. An OMM will load extra services like Web configuration default on port 80.

    Optional: You can add additional parameters by clicking on the “Add Parameter” button and the desired parameter can be chosen like NTP server address, DNS addresses, DNS domain and Country.


    Figure 2: Add Parameters

  4. Accessing the OMM web interfaceType http://(RFP assignedIPaddress) in your browser and the OMM web interface logon will be displayed.
    Figure 3: Logging into the OMM – Open Mobility ManagerAccess the OMM – Default credentials are Username omm and Password omm. Only 1 user can connect to the OMM concurrently. So it is important that you click on Logout whenever you need to terminate the session. Failure to do so will keep the session active for 5 minutes. The OMM will log itself out after 5 minutes of user inactivity.
  5. OMM System SettingsClick on “System” to start the OMM configurationClick on “System Settings”
    Figure 4: System Settings Configuration Pagea) Add the System Name – In this case this is named DEPLOYMENT.
    b) Under “DECT SETTINGS” enter the “PARK” number that came with the OMM activation kit. Each DECT network requires a unique PARK key provided in the OMM Activation Kit Product. This is mandatory.
    c) Syslog can be optionally enabled. Enter the IP address of the syslog monitor and default port is 514.
    d) Date and Time – Set the date and time. This is important because it is the RFP that providers the date and time to the PP.
    e) Click on the OK button to save changes.
  6. Session Initiation Protocol ConfigurationClick on SIP to configure Session Initiation protocol settings for the DECT basestation.
    Figure 5: SIP configurationEnter Proxy server, Registrar server, and Outbound proxy server settings.
    Click the OK button at the top of the screen for Open Mobility to restart and apply newly configured settings.
  7. Configuration of Radio Fixed Partsa) Click on Radio Fixed Parts in the OMM menu.
    b) Click on the “NEW” button and the “Configure Radio Fixed Part” popup will show. See Figure 6.
    c) Enter the MAC address of the RFP.
    d) Enter a location Identifier to ID the RFP’s location in your DECT network.
    e) Under “DECT Settings” select the DECT Cluster checkbox and assign to Cluster 1.Click OK to proceed.
    Figure 6: Configure Radio Fixed PartNote: Further information can be found on RFP Clustering by consulting the DECT installation manual section 3.3.3 – RFP configuration especially in a multiple RFP scenario.Once the RFP is added, the Radio Fixed Part should look like this: See Figure 7.
    Figure 7: An RFP which is Active and in SyncThe above screenshot shows that the RFP is active and synchronized. This means that the RFP is up and running. The RFP recognizes and is recognized by other RFP’s in the cluster through its air interface and delivers a synchronous clock signal to the PPs.

    Note: For more RFP state information check the Installation, Administration and Maintenance DECT manual – section 3.3.3.2 – States of a RFP.

  8. Configuration of PP – Portable Partsa) Click on Portable Parts.
    Figure 8a: Main PP config screenb) A new PP can be added to the system by pressing the “New” Button. The following popup window appears allowing the configuration of a new PP.
    Figure 8b: Addition of a new Portable Partc) Enter a Name Parameter. This represents the SIP Display Name Field.
    d) Enter a SIP account number in the Number Field.
    e) The IPEI is the DECT 142 handset IPEI number which can be found in the System Options menu for the DECT 142 handset. Enter IPEI number.
    f) The DECT authentication code is used during the initial DECT subscription as a security option and can be set for each PP separately. In this case this is 1234.
    Note: The authentication code can only be changed if the PP is not subscribed. Changes will take place until the PP is subscribed again.
    g) Under SIP Authentication enter the User name, Password and Password confirmation for the extension available for use in the 3CX Phone System IP PBX.
    h) Click OK and a new PP will be created. See Figure 8c below.
    Figure 8c: A list of PPs created
  9. Enabling the OMM to allow subscriptions from a PPAfter adding a PP configuration to the OMM, the PP must be subscribed. However, the OMM must be first enabled to allow subscriptions to take place from the PP handset.
    To do this press the “Subscribe” button on the PP OMM webpage. The OMM will allow a subscription of configured but not subscribed PPs during the next hour only. The administrator must press the subscribe button again to permit more PP handsets to subscribe to the SIP-DECT system. Therefore the subscription for the listed and unsubscribed PP’s is valid for 1 hour.
    Figure 9: This screenshot shows that Subscriptions for this PP are allowed but the PP has not subscribed to the system yet
  10. Subscribe a PP to the SIP-DECT systemOn the DECT handset, a subscription must be performed to the SIP-DECT system through the System/Subscriptions menu to achieve the above result. At the moment, you will only see “No Subscription” on the SIP DECT handset display.To subscribe do the following:a) Press the Menu softkey
    b) Scroll downwards to “System” – Press the “OK” softkey
    c) Select “Subscriptions” – “No Subscription” will be displayed.
    d) Select the “New” softkey.
    e) Confirm the IPEI number – Press OK.
    f) You will be asked to “Enter PARK”. Enter the PARK code in numeric format. You can see the PARK code in
    i) OMM / System / System Settings page or
    ii) OMM / Portable Parts page in the top right corner
    g) Once PARK is confirmed, you will be asked to enter the DECT Authentication Code. If you did not configure DECT authentication you can skip this step by pressing OK.
    h) You will see a “Success” message on the handset display indicating that the PP has been successfully subscribed to the system. You will then see the SIP DECT system name, the PP display name and Date and time configuration.
    Figure 10: Display on handset after successful subscription
  11. Confirmation

    Figure 11: Subscriptions are allowed and PP is now subscribedFigure 11 shows that the RFP allows subscriptions to be made from the listed Portable Parts (Figure 9). However it also shows that the PP named Aastra 142 DECT, is successfully subscribed to the system. Extension 200 is now registered to the 3CX Phone System and is able to make and receive calls using DECT technology to any other phone registered on the 3CX PBX.

Congratulations – You have successfully configured your SIP-DECT SYSTEM with 3CX.

You might also be interested in:

<