VOIP Phones Not Auto Booting 1

[AvatharV]

We have an Avaya phone system. We have 20 sites and all the site phones boot up, find DHCP addresses and the File & Call server just fine. Yesterday, we discovered that the main corporate site is not working correctly.

As long as the Avaya 1608 & 1616 phones stay connected, they seem to work just fine. If you unplug or reboot them, they seem to pull an IP address, but can't find the File or Call server. If you manually give the phones an IP address and put the File & Call server IP addresses in, it seems to work.

There have been Juniper switch & firewall updates recently, but not on this corporate segment. The File/Call server are on the same local network as the phones having problems. We had moved DHCP to a new server, and even rolled that back to the old server to see if that was the problem (since the old server had not been modified, we just turned off DHCP), no luck.

We restarted the MAS, but haven't restarted the CM server yet. Do you think that will help? If we do restart the CM, do all the existing calls drop? Any other tips?

Thanks.

 

[mattKnight]

>We had moved DHCP to a new server, and even rolled that back to the old server to see if that was the problem (since the old server had not been modified, we just turned off DHCP), no luck.


You have a problem with your DHCP. Quite what its difficult to say, probably the scope options are wrong. Possibly you have the DHCP server port on the switch configured wrong

Sadly vague questions generate vague answers


Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

 

[janni78]

If they get an IP address but you need to enter CallSv and FileSv manually to get them to work your DHCP server aren't sending out Option 242, or at least not the right parameters.
Rebooting CM won't fix that.

"Trying is the first step to failure..." - Homer

 

[mojoputter]

The other 2 gents are correct on saying you have an issue with your DHCP settings or perhaps the phones are not seeing the DHCP server.
Below is a example of Option 242 DHCP settings

OPTION:242:MCIPADD=10.123.10.42,MCPORT=1719,HTTPSRVR=10.114.24.235,L2Q=1,L2QVLAN=342

MCIPADD = C-lan or procr
MCPORT= always 1719
HTTPSRVR= customer's HTTP server address
L2Q=1 turns on layer 2 priority to end point based on network region defined in PBX

 

[Mlck]

If your PC's are connected tru the phones and you two Vlan / ports , be sure you keep the option 242 in your DATA DHCP scope: L2Q=1,L2Qvlan=(VOIP VLAN) to tell the phones to boot in the VOIP VLAN in tagged mode, then, option 242 in your VOIP scope will be : MCIPADD=10.123.10.42,MCPORT=1719,HTTPSRVR=10.114.24.235

Good try, put your switch port Untag on the voip VLAN and try with a PC.

CM has nothing to do with this issue.

Don't follow the cows

 

[AvatharV]

That is what is thoroughly confusing us..

Our old DHCP server had options 176 & 242 set. These same options were put in the new DHCP server.. and seemed to work. We haven't made any other changes in quite a while, neither network or server wise.

We have VLAN 3 as data & VLAN 5 as voice.

Our 10.5.5.x (voice) DHCP options for voice are:

176 MCIPADD=10.5.5.10,MCPORT=1719,TLSSRVR=10.5.2.28,L2Q=1,L2QVLAN=5,VLANTEST=0
242 MCIPADD=10.5.5.10,MCPORT=1719,TLSSRVR=10.5.2.28,L2Q=1,L2QVLAN=5,VLANTEST=0

Our 10.5.3.x (data) DHCP options for data are:

176 L2QVLAN=5
242 L2QVLAN=5

The phones seem to boot up in VLAN 3 and find that they need to be on VLAN 5, reboots and pulls a 10.5.5.x address like it should, but it doesn't seem to pull the string info for 242. Does the order matter? Should there be spaces after the commas?

Thanks.

Thanks.

 

[mojoputter]

Do you have the option set on the data side as well to point to VLAN 5..?

 

[AvatharV]

Yes,

We have the data side set to:

176 L2QVLAN=5
242 L2QVLAN=5

 

[prflash]

We just had this same issue and you need to add the ip address of the file server that has the 46xx file.

 

[AvatharV]

Thanks to everyone for your input. It really helped.

The problem was indeed DHCP related. We had all the correct server options strings put in DHCP, but the server admin put the options as MICROSOFT and not STANDARD. That is why the critical strings were not being passed to our phones.

 

[mojoputter]

Thanks for telling all the resolution, star for you