Today we implemented the Avaya IP Office into a clients site.
Once I started to ask the engineer about anything outside of the “usual install” things got, well let’s say…. complicated. 🙂
Something that amazed me is that the implementation company wanted to assign static IP’s to 30 phones, and even if not we would still have to go to all 30 phones and tell the phone where the TFTP server was for the system. I was certain that this must be incorrect and that there must be some way to get the DHCP server to tell the phones where everything was on the network and save a load of time.
I have done a bit of research, and this is possible using Microsofts DHCP, but the method is hidden away and not clear in the documentation on the Ayaya website. Below is the method for those also looking via Google 🙂 (Click on the images to get the full versions)
First, you need to create a predefined Scope. Right click on the DHCP Server and select “Set Predefined Scopes”
Next, click the Add Button…..
Setup a new option with the information below. The important thing is to use a String Value and the Code 176…
After clicking ok, you need to set the String value. The picture below does not show the whole string, but you add based on this information:
MCIPADD=xxx.xxx.xxx.xxx,MCPORT=1719,TFTPSRVR=yyy.yyy.yyy.yyy,TFTPDIR=z
• xxx.xxx.xxx.xxx is the H323 Gatekeeper address. Normally this is the IP Office Control Unit’s address.
• yyy.yyy.yyy.yyy is the TFTP Server IP Address. Normally this is the IP address of the PC running Manager.
• z is the directory on the TFTP Server where the 4600 Series IP telephone software files are located. This information is not required if those files are in the TFTP server’s default directory. Personally I will not use this option so my string will be:
MCIPADD=192.168.16.10,MCPORT=1719,TFTPSRVR=192.168.16.1
The last thing to do is to add the newly added option to your scope, then the phones should boot correctly!
We looked at IP Office where I work when we replaced our Nortel System a few years ago. I personally thought it was the way to go, but management could not come to grips with Avaya’s support costs, which were close to $8000 per year.
We ended up going with a Mitel system, and pretty much everybody agrees now that we should have gone with the Avaya! Why listen to your IT guy right? What does he know?
hmmm -from my experience there isn’t any useful documentation on the awful avaya web site.
Anthony, I think going with the IP Office a few years ago, would have been a bad idea. still too young, and too many bugs. Now it is a great option, but then you would have been beta testing it for Avaya. As for the maintenance costs, thats why you go through an avaya dealer, and not avaya themselves. Trust me, I am an IP office programmer for an Avaya Dealer. Much more cost effective way to go.
Man.. you just saved my life!!!
I got hit with a request for a 176 config and was already freaking and expecting to loose a few hours figuring how to do it when I googled into your blog…
Many many thanks
Alex