EasyManua.ls Logo

Aastra NeXspan 500 - 4 Implementing the Ip Dect Service; Principle

Aastra NeXspan 500
87 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Page 41 01/2007 AMT/PTD/PBX/0062/1/2EN
4 IMPLEMENTING THE IP DECT SERVICE
4.1 PRINCIPLE
To implement an IP DECT installation, a network infrastructure is required, which comprises at
least the following items:
Note :
The radio fixed parts (RFPs)
The portable handsets (PP)
The NeXspan iPBX associated with a GSI gateway
A Red Hat Linux PC server, if you do not wish to use the OMM (OpenMobility Manager)
application from an RFP.
Note: the number of RFPs was defined through a previous radio study (deployment).
The different services required to operate the IP DECT service from the OMM interface are:
TFTP server for loading the RFP software (ip_rfp.cnt) on each RFP.
DHCP server for providing the IP address of each RFP and the IP address of the
equipment (RFP or Linux server PC) hosting the OMM application which manages the
SIP DECT STIMULI signalling interface
Debug tool (Syslog daemon).
the DHCP and TFTP servers can be installed on different PCs.
IMPORTANT : RFP power supply: if power is remotely supplied to the RFPs, contact the
administrator (need for a remote power switch).
To main IP DECT service implementation phases are:
Configuring the DHCP server
Configuring the TFTP server
Installing and configuring the OMM (licences)
Declaring the PPs in the OMM
Declaring the SIP subscriptions for the portable handsets in the iPBX
Registering the DECT handsets.

Table of Contents

Other manuals for Aastra NeXspan 500

Related product manuals