Product and Software: This article applies to the Aruba 5000, 6000, 3000, 2400, 800, and 200 Mobility Controllers and to ArubaOS 3.3.1.x and later.
To troubleshoot the Avaya 4600 series phones, you first need to understand how the Avaya phones learn their key variables: address of gatekeeper and address of the file server and registration port number (UDP 1719). The phones can learn these key variables from DHCP option 176 or they can also be hard-coded on the wired set. This article highlights only a subset of the listed options:
- MCIPADD: the IP address of the Avaya gatekeeper. (The requirement is only one gatekeeper.)
- MCPORT: UDP port 1719 is the default registration port.
- TFTPSRVR: the IP TFTP server where the images are downloaded from.
Sample string for the requested option 176:
To program the phone manually, you must press the"*" button to break into the program mode, when you are presented with this option.
When entering a period for the IP address, use the "*" button.
To move to the next variable, press "#".
The variable names are: Phone, CallSV, CallSvPort, Router, Mask, FileSV, 802.1Q, and VLAN ID.
The mapping between the DHCP options and phone variables are as follows:
- MCIPADD = CallSV
- MCPORT = CallSvPort
- TFTPSRVR = FileSV
To troubleshoot the Avaya 4600 series phones, follow these steps:
1) Verify that there are no drops on the datapath by issuing the following command:
show datapath session table [IP of the phone]
2) The Avaya 4600 series phones can run on either a SIP or H323 image. When the phone is booting, write down the firmware string. If the image is incorrect, download the correct image from the Avaya site to a TFTP server. The administrator should know the correct image for the phone. You can instruct the phone to pick up the new image by coding "FileSV" on the phone. This will override the TFTP server that was defined by option 176.
3) For the registration port, always use UDP port 1719. There are no exceptions to this rule.
4) Note that the gatekeeper address will be different for the H323 and SIP phones. If the phone is running a SIP image, the gatekeeper IP address should be the Avaya SIP proxy server. If the phone is running a H323 image, the gatekeper IP address should be an interface on the call server. If the phones are pointing to incorrect gatekeeper, code "CallSV" on the set to override the DHCP option. Consult the administrator for the correct gatekeeper IP address.