Aastra SIP-DECT User's Guide download pdf (Page 13)

Large SIP-DECT System Compendium: OM SIP – DECT Solution

1. Open the System menu and select the Administration: Firewall command.

Disable the firewall function.

2. Copy the necessary “SIP-DECT_4.0.bin” file to the Linux server, either via the

SIP-DECT 4.0 product installation medium or via download.

3. Open the Applications menu and select the System Tools: Term inal

command. Enter the “su” command to elevate your system access rights.

>OM System Manual:

Installing the OMM Software

4. Enter “sh SIP-DECT_4.0.bin” to extract the installation files and to start the

installation automatically.

>OM System Manual:

Configuring the Start

Parameters

5. Enter “nano /etc/sysconfig/SIP-DECT” to adapt the OMM configuration file.

Remove the hash character and change the “OMM_RESILIENCY=” setting to

the IP addresses of the primary and secondary OMM instances. If the OMM

should bind to a specific Ethernet interface, remove the hash character and

change the “OMM_IF=” setting accordingly. Leave the editor with the [Ctrl-X]

keyboard combination and save your changes. Start the OMM with “/etc/init.d/

sip-dect-omm start” or reboot the PC.

>OM System Manual:

Initial Setup

6. Start a browser and navigate to the IP address of the server that runs the OMM.

license text. Change the password for the “Full access” and the “Root/SSH”

accounts. Import the license file. Navigate to the System: System settings

page. Change the DECT: Regulatory domain setting.

Set up RFPs

>OM System Manual:

DHCP Client

For a larger number of RFPs, a DHCP service that automatically configures RFPs is

important. The DHCP service sends the IP configuration, where to download the

software files (“iprfp3G.dnld” and “iprfp2G.tftp”) via TFTP and the IP addresses of

the OMMs to the starting RFPs.

The TFTP and DHCP services are not part of the SIP-DECT 4.0 solution, hence you

need to set up your own.

Tip: The “OM System Manual” provides an example in the “Setting up DHCP /

TFTP” chapter.

Your DHCP server configuration should include at least:

■ a static MAC/IP address mapping for the RFPs / PC system running the OMM;

■ an IP address range large enough to assign a separate IP address to all RFPs;

■ a rule to separate DHCP queries by vendor ID “OpenMobility3G” for current

RFPs (see About RFP Types starting on page 3);

■ a rule to separate DHCP queries by vendor ID “OpenMobility” for older RFPs;

■ DHCP answers containing IP, net mask, gateway, TFTP server IP, and boot file

name;

■ option 224 with “OpenMobility” or “OpenMobilitySIP-DECT” in DHCP answers;

■ option 43 with vendor option 10 (OMM IP) and – if using a backup server –

vendor option 19 (2nd OMM IP).

>OM System Manual:

Creating and Changing RFPs

After setting up the DHCP and TFTP service, connect at least all RFPs referenced in

the license file to power and LAN. Navigate to the Radio Fixed Parts page of the

OMM Web service. Verify the RFPs Connected status.

>OM System Manual:

RFP LED Status

Tip: For a first test, click on the configuration icon of a connected RFP. Activate

the DECT settings option. Accept the default DECT cluster number “1”.

Confirm with OK to activate the RFP. Watch the RFP’s LEDs for a status

indication.

>OM System Manual:

RFP Synchronization

The DECT cluster number groups RFPs that can be synchronized over the air. With

synchronization, seamless handover of DECT handsets is possible. Use a different

1 2 ... 8 9 10 11 12 13 14 15 16 17 18 ... 22 23

Comments to this Manuals

No comments

Aastra SIP-DECT User's Guide Page 13

Comments to this Manuals

Related products and manuals for Telephones Aastra SIP-DECT