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

SIP – DECT OM System Manual Release 2.1 7 Configuration und Administration Aspects
depl-1230/1.3 Page: 126 (196)
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.
7.4 Network Infrastructure Prerequisites
To establish and maintain an SIP – DECT installation, a network infrastructure is assumed,
which comprises at least the following components:
• RFPs
• PPs
• IP PBX/media server (e.g. Asterisk)
• TFTP server
Depending on the operational modes the following services should be provided:
• DHCP
• TFTP
• SNTP
• DNS
• LDAP
• Syslog daemon
Note: In NA outdoor RFPs may only be installed with the antennas shipped with the units.
No other antennas or cabling are permitted. In EMEA the outdoor RFPs are shipped
without antennas and you may use the units with one of the optional antennas
(separate order no.).
7.5 SIP – DECT Startup
This chapter contains detailed information on the startup (booting) process of the
SIP – DECT solution.
For booting an RFP, there must be at least one TFTP server on the attached network
to load the OMM/RFP application software. The essential network settings can be
alternatively:
• Communicated by a DHCP server at startup time.
• Configured on the RFP with the OM Configurator tool (see chapter 7.6). The settings
made by the OM Configurator will be saved permanently in the internal flash memory of
each OMM/RFP.
7.5.1 TFTP and DHCP Server Requirements
TFTP server requirements
The RFP gets the boot image file from a TFTP server. The requirement list for the used
TFTP server is defined as follows: