56XX series phone setup

[Vmail]

I have 40 new 4610's going in on an IPO 406. We are using DHCP. How can I change the text file to allow DHCP to give the phones ip address's and point to the call server and tftp server. I am trying to stay away from manually programming each phones ip address, call server, tftp server, gateway etc.

I have looked the the lan admin guide but don't see where to add the IPO address, tftp address???

Thanks.

 

[sizbut]

It is in the LAN administrator guide, you need to confiure the DHCP to issue the IP address and TFTP server adress. They (Avaya) give examples for IIS and RedHat Linux. Do a search on Scope 176.

 

[Vmail]

Thanks Sizbut, but can it hand out the call server (ip office) too? Looking for a way to not have to manually plug ip's into the phones since we have 40 going in at once.

 

[sizbut]

Yes, yes and yes. The DHCP 176 option is used to tell the IP phones their own IP address IP address of their gatekeeper (ie. the IP Office) and the address of the TFTP server that they should use. The phones will then ask for a copy of the 46xxsettings.txt file on the TFTP which can be set with a range of other information.

This is all in the LAN Administrators Guide and also in the IP Office IP Telephone Installation Manual.

 

[avayaconsultant]

The option 176 can be added a custom option is Windows DHCP services as well.

 

[Morrack]

Has anyone ever gotten this to work when using a PIX as the dhcp server? I always seem to end up with a phone with a blank screen.



Peter Sherwood

Morrack Consulting

http://www.morrack.com

 

[Morrack]

Never mind, just got it working. Here is what I added (in addition to the standard address range, enable inside, etc.)

dhcpd option 176 ascii MCIPADD=192.168.15.250
dhcpd option 3 ascii 192.168.15.1
dhcpd option 66 ascii 192.168.15.2

The first line is the IPO (as everyone knows I'm sure), the second is the gateway to be used, the third is the TFTP server.



Peter Sherwood

Morrack Consulting

http://www.morrack.com

 

[NuggiFirst]

Just a little feature:

If you are in v3.0, it's not necessary to give the phone a FileSv address. If you leave this field blank, the phone will use the TFTP address from System/System.

So if you can't get your DHCP-server to handle the CallSv address anyway, it's actually only neccesary to program the CallSv manually. This is quite neat in an multisite installation ;-)

 

[IPOUK]

What about telling the phone what VLAN to go in? Does that work with VLANTEST=x ? Option 176 works fine, but seems a little more tricky with the VLAN info - or is all this part of the 46xxsettings.txt file?

 

[Morrack]

VLANTEST is to tell the phone how long to attempt a non-zero VLAN before defaulting to zero. L2QVLAN defines your voice VLAN. You can set these variables through either method, DHCP Option 176 or the 46xxsettings file.



Peter Sherwood

Morrack Consulting

http://www.morrack.com

 

[IPOUK]

shame the IP Office IP Phone setup pdf (

http://support.avaya.com/elmodocs2/ip_office/R3.0/ip_phone_installation.pdf)

doesn't mention the L2QVLAN within the 176 scope - all it says is the below:

6. In the string value field enter the following:
MCIPADD=xxx.xxx.xxx.xxx,MCPORT=1719,TFTPSRVR=yyy.yyy.yyy.yyy,TFTPDIR=z,VLANTEST=w

So do we just add L2QVLAN to the 176 scope at the end so....

6. In the string value field enter the following:
MCIPADD=xxx.xxx.xxx.xxx,MCPORT=1719,TFTPSRVR=yyy.yyy.yyy.yyy,TFTPDIR=z,VLANTEST=w, L2QVLAN=x ???

 

[Morrack]

I wouldn't bother with MCPORT or TFTPDIR if they are going to be the default values, but yes.



Peter Sherwood

Morrack Consulting

http://www.morrack.com

 

[hoffdog]

Right, if you are just dumping your files into the tftp servers root folder you don't need to bother with the dir entry.

ED