User Manual

OpenMobility SIP Installation, Administration and Maintenance
Aastra DeTeWe Doc-ID: pm-0504 28.11.2006 Page: 19 (52)
3 Installation and configuration
To establish and maintain an IP DECT installation, a network infrastructure is
assumed, which comprises at least the following components:
• RFPs
• PPs
• media server (e.g. Asterisk)
The following services should be provided:
• TFTP
• DHCP
• Syslog daemon
3.1 OpenMobility start up
3.1.1 Start up of the RFPs
For booting a RFP there must at least a TFTP server on the attached
network to load the application software.
The essential network settings can be alternatively
• given by a DHCP server at startup time.
• configured on the RFP with the tool OM Configurator. The settings made
by the OM Configurator will be saved permanently in the internal flash
memory.
The RFP gets the boot image file from a TFTP server. The used TFTP server
needs to support /1/. A used DHCP server needs to support /4/.
The TFTP and DHCP server need not to reside on the same host.
3.1.1.1 Booting overview
Booting is performed in two steps:
1. Starting the boot process.
2. Starting the application.
Booter
The RFP has only a little standalone application built into the flash. This
software realizes the so called net boot process.
On startup each IP DECT Base Station tries to determine its own IP address
and other settings of the IP interface from the configuration settings in the
internal flash memory. If no settings are available or these settings are
disabled, the IP DECT Base Station tries to determine these settings via
DHCP.
The RFP gets the application image file from the TFTP server.
Application
After starting the application image the IP DECT Base Station checks the
local network settings in its internal flash memory once again. If no settings