Start Procedure - Aastra OpenCom 100 Series Mounting And Commissioning User Manual

Voice over IP (VoIP)

Start Procedure

It may sometimes be useful to understand a VoIP system telephone's start procedure.
Examples:
• A complex DHCP address assignment prevents the operation of the
OpenCom 100's DHCP server within the LAN.
• A VoIP system should be operated with a non-broadcast-capable IP connection.
This may be an RAS connection, a VPN connection or another type of routed con-
nection.
An external DHCP server can also control a VoIP system telephone's start procedure. In
this case, system software matching the type of VoIP system telephone must be trans-
ferred via TFTP.
The file name is determined by the telephone type. If a Media Gateway card is
installed, you can also specify the TFTP server on the card which has a higher per-
formance.
Telephone type
OpenPhone 63 IP
OpenPhone 65 IP
Aastra 6773ip
(OpenPhone 73 IP)
Aastra 6775ip
(OpenPhone 75 IP)
RFP 32 / 34 / 42
RFP 35 / 36 / 37 / 43
After the VoIP system telephone has been connected to the mains power supply, the
start procedure is as follows:
1. The boot loader starts and shows the VoIP system telephone's MAC address in the
display. A DHCP request is sent simultaneously via broadcast on the
255.255.255.255 broadcast address.
2. An IP address, network mask and the default gateway for the start procedure are
sent from the DHCP server. Via the "Next server" option, the DHCP server also pro-
vides the TFTP server's IP address and the operations software's file name. The
134
OpenCom 130/131/150
opi63.cnt
opi65.cnt
opi7x.cnt
ip_rfp.cnt or
ng_ip_rfp32.cnt
ng_ip_rfp.cnt
Media Gateway card
/ram/ip_tel/opi63.cnt
/ram/ip_tel/opi65.cnt
/ram/ip_tel/opi7x.cnt
/ram/ip_tel/ip_rfp.cnt or
/ram/ip_tel/ng_ip_rfp32.cnt
/ram/ip_tel/ng_ip_rfp.cnt