IP Phone Resets

[Vmail]

Couple of questions. I have IP403 with 10 4612's. I have had issues with the pbx reseting for no reason. So I upgraded to 2.1.24, so far so good. My question is when the ip office reboots some of the ip phones request you key in a new extn number and p/w. Now I have set each extension in the ip office with a static ip? Why do some come up fine and not others.

Secondly, How is the association with booting up via Ip addresses set if the ip phone is used along with a computer in the 2nd RJ45 port.

Third an final, how do you guys set the extension in the ip office via g711 or uncompressed etc. What is a standard that we should use. I have it set as g711 64 clear for Lan connections.

Thanks for all the help.

vmail

 

[Morrack]

Not sure on the first question.

Second: it's just a simple 2 port switch built into the back of the IP hardphone. Your PC and the phone both maintain seperate IP addresses. It may help to visualize it as your network drop going to a 5 port switch, and the IP phone and the PC both going to that same switch.

3rd: depends on your network setup and if you are making VoIP connections outside the building. If only using internal g.711 mulaw is usually a suitable choice (assuming 100M switched QoS capable connections everywhere). However, if you have external connections, unless you have bandwidth to spare you are usually going to want to set those links to g.729a. The basic rule of thumb with voip is to keep ALL your codecs the SAME - so if you have h.323 trunks between sites (for example) set to g.729, then set all your phones to g.729 also.

Peter

 

[Raffles666]

Question 1: Have you also upgraded the firmware in the 4612's? I had a similar situation with early 2.1's.

2.1(24) - or even 2.1(27) - also has updated IP phone code. That's probably your problem.

cheers



Old school Alchemy engineer - trying to keep up with the times

 

[Vmail]

How can I check the firmware of the phones from phone?

 

[sizbut]

If you want to check the firmware in the phones; press HOLD, dial V I E W # and then use * to go through the phone details which will include the phones software.


However I would simply recommend running Manager, send a reboot to the system (File | Advanced | Reboot) and leave Manager running. The IP phones should also reboot and whilst restarting will check via TFTP with the Manager app for the appropriate software and upgrade if necessary.

Get the t-shirt, buy the mug and throw the stress ball hard.

 

[Vmail]

Thanks sizbut,

These phones were from a definity we took out they are running the def24r1_8_2.bin? Is this correct? Doesn't seem so.

 

[sizbut]

Unfortunately the only system near me at the moment is a 3.0. The 1.8.2 bin file would be correct for that but I don't won't know about for an IP Office 2.1(24) until I go back into the office tommorrow.

That's partially why I recommended restarting the phone with Manager running - that way the phone gets whatever software level bin files have been supplied with the IP Office admin suite and thus also tested with that level of IP Office core software.

Get the t-shirt, buy the mug and throw the stress ball hard.

 

[VOiDDude]

You should use 2.1(27) to make sure all ip phones come up correctly after a reboot. All previous firmware versions contain a bug in the password algorithm used on the IPO to register the IP Phone.

If possible don't use the manager as TFTP because the TFTP implementation is not that great. Certainly not if you will have high volumes of TFTP traffic. Better use a 3th party TFTP server you can run as a service.