Considerations For Ip Phones Supported By A Local Survivable Processor; Transition Of Control From Primary Controller To Lsp - Avaya G700 Installation And Upgrades

Hide thumbs Also See for G700:
Table of Contents

Advertisement

3 Configuring a New G700 with an S8300 (Primary Controller or Local Survivable Processor):
Considerations for IP Phones Supported by a
Local Survivable Processor
A DHCP server assigns IP addresses to IP endpoints dynamically. Avaya IP phones perform a DHCP
discover request to receive an IP address, as well as receive parameters necessary to function
correctly. These parameters include the location of the call control server, the location of the TFTP
server, as well as the directory on the TFTP server from where the phone receives its upgrades.
When preparing a DHCP server to work with Avaya IP phones, there is an option that must be
administered to allow the Avaya phone to receive the DHCP offer. This option is "site-specific-
option-number" (sson) 176. Different DHCP servers allow for this administration in different ways,
but the sson option must be mapped to 176. Then the option can be set up to send the information
desired to the Avaya phones for the intended activity.
The sson option should send a string. This string will include "MCIPADD=www.xxx.yyy.zzz".
MCIPADD defines the Avaya Call Controller with which the phone will register. In an S8700
system, this address should be a CLAN address, and in an S8300 system, this address will be the IP
address of the S8300. Multiple addresses can be administered at this point to allow for LSP failover.
The second address in the MCIPADD list may be an address for a second S8700 CLAN board or an
LSP IP address. If a second CLAN board is used, then the third address must be the LSP, and any
subsequent addresses should be alternate LSPs. Local LSPs should appear first in the list, with remote
LSPs later in the list as possible back ups.
Also included in the sson option string is the "MCPORT=1719". This is the port the phone will listen
on for signalling traffic to the call controller. Next is the tftp server field. This field indicates to the
phone where it is to receive firmware updates, along with the tftp directory field.
All phones for which the DHCP server has an LSP as the second address in the MCIPADD list should
either be administered to be part of the same network region, or the network regions involved should
be interconnected. On the primary controller in the ip-network-map form, a range of IP addresses can
be specified to be part of the specified network region. This is where the phones of a specific subnet
or range should be placed into the same network region. If it is not desired for all the phones receiving
a controller list with the LSP to be in the same network region, the form "ip-network-region #" should
interconnect all the network regions that contain those phones.

Transition of Control from Primary Controller to LSP

When the network connection between the G700 and the S8700 goes down, control of endpoints
connected to the G700 goes to the next point in the primary controller list, which will be either a
second CLAN board or the LSP. At this point, the S8700 alarms to notify the customer and services
personnel that the network connection between the S8700 and G700 has problems. If control passes
to the LSP, the LSP's license allows it to support the G700 endpoints for up to 6 days, within which
the network problems should be resolved.
The customer must pass control back to the S8700 manually, by selecting Shutdown this server
from the S8300 web page (includes selecting the option to restart after shutdown), or a technician
must run reset system 4 from the Linux command line. When the system reboots, the G700 and its
endpoints reregister with the primary controller, in this case the S8700.
Installation and Upgrades for the G700 with an S8300/S8700
555-234-100 — Issue 2 — October 2002
139

Advertisement

Table of Contents
loading

Table of Contents