AASTRA SIP-DECT (Release 3.0)- OM System Manual - Installation, Administration and Maintenance EN - Manual (Page 18)

SIP–DECT OM System Manual Release 3.0 2 Getting Started
Aastra depl-1624/1.0 Page: 18 (241)
2 Getting Started
This chapter describes how to set up a small SIP–DECT system using two RFP devices,
useable as a small stand-alone DECT telephony system or for evaluation purposes.
Note: The DHCP/TFTP configuration described here can be used to operate current RFPs
(RFP (L) 35/36/37 IP, RFP (L) 43 WLAN) together with older RFPs
(RFP (L) 32/34 IP, RFP (L) 42 WLAN). However, a more straightforward setup using
the Java-based OpenMobility Configurator tool is described in the SIP–DECT:
Installation & Administration Compendium document (see /24/).
Prerequisites
Some hardware and software prerequisites are to be met to follow this quick start guide:
•
a licensed RFP device (e.g. RFP L35 IP),
•
a PC to run a browser or start Java programs,
•
two or more DECT handsets (preferably two Aastra 600d / 650c),
•
OMM-SIP installation medium with software, such as the “iprfp3G.dnld” file,
•
a Linux PC server for setting up DHCP/TFTP, HTTP and SNTP services required e.g. to
update the RFP software,
•
optional: a VoIP communications system that provides SIP accounts.
You can use any operating system for the PC-based server system that provides a DHCP
and TFTP server. However, the following description details on a Linux x86 server.
Tip: For testing and evaluation, you may download and install virtualization software for
your workstation, such as “VmWare Player” or “VirtualBox”. Within a virtual machine,
you are able to operate a Linux system, for example the CentOS, Debian or Ubuntu
“LiveCD” ISO files that are downloadable for free on the respective Linux vendor web
sites.
IMPORTANT : The PC-OMM (OMM in host mode, see also chapter 9.11) is not
supported on virtual machines due to specific real-time requirements.
2.1 Setting up DHCP / TFTP
An RFP in the factory default configuration will request the address configuration via DHCP.
While it is possible to configure a fixed (non-DHCP) address for the RFPs (see chapter 9.6),
this description starts with setting up a DHCP server that will answer the DHCP requests.
The DHCP server will be limited to answer only DHCP requests from Aastra RFPs (sorted
out by MAC address), so the new DHCP server will not disturb the operation of possibly
other DHCP servers in your LAN.
Also you need a TFTP server that offers the software file for the RFPs. For current RFPs
(RFP (L) 35/36/37 IP and RFP (L) 43 WLAN), the TFTP server provides the software file for
updates (“iprfp3G.dnld”). For older RFPs(RFP (L) 32/34 IP and RFP (L) 42 WLAN), the TFTP
server provides the software file loaded during RFP startup (“iprfp2G.tftp”). The IP address
and the software file download location is part of the DHCP answer, the RFP receives during
start-up. By using this DHCP-provided configuration, the RFP downloads the software file
and starts the program that is included in the software file.