4610 IP Phone not registering

[TheCardMan]

I have a phone 4610IPSW that when we plug it in is goes to a screen that states: Discover XX.XXX.XX.16 (IP Address) and will not come up as the extension assigned. The screen IP address keeps changing from .16 to .15 and back and does not fully resister. I took another working phone and plugged it into that same jack and that phone came up fine. I checked the station in the switch and it is assigned correctly and says S00172 as the Port. When I status, of couse it says disconnected. What else can I try to get this phone to work? It was working before we changed the PC out for the user. (We put in a new PC). The PC works fine.

Any assistance would be appreciated.

Thanks

 

[Midstream]

Do you have the ability to statically assign an IP address to the phone and input the rest of the info, eg. file server, call server, subnet... and so on? Or is the phone just plain stuck?

My thought is.. If you can just get it to register once, you may be allright.

 

[G3siv12]

I am having the same problem with my 4610sw's Check Avaya Support for the 2.8 upgrade release. Our problem is was related to number 4.

1. There is a known issue with R2.7 on 4610SW, 4620SW, 4621SW, 4622SW and 4625SW speakerphones. The level of the transmitted voice, or near end user speaking into these IP telephones, will fluctuate. The volume of the speaker’s voice will fluctuate up and down, which may be perceived as the voice cutting in and out.
2. Latency in the start of the audio path, under certain configurations. In a call center environment the issue will be noticed when the zip tone after the VOA will be missing.
3. Topline will flash or flutter, under certain call scenarios and will stabilize thereafter. The incoming Caller ID information may appear to flutter on the 4610's or 4621's topline display during an incoming call.
4. 4610SW will send a zero (00:00:00:00:00) as its client MAC address during a DHCP discovery message, if the DHCP server is on another subnet other than the one the phones are located in.

 

[TheCardMan]

Thanks

I am not sure if I an staticly assign IP addressess.

Thanks G3siv12 - I will look through those items.

We ended up trying other phones in its place, some other didn't work but them one did but did not give us an option to Logout. But after about a 3 minute period the option to log out appeared and we logged out and then logged in with that persons extension and it looks like it works.

I don't understand, besides logging in and out, how to you associate a phone with an extension? There has to be a manual way of doing this...........

Thanks

 

[jffmsly]

WE are having the same problem across our network. I have telecommuter phones, phones on an LSP and phone here locally that are doing this. The one thing they all have in common is that they are all release 2.8. The phones have been sitting on a desk working but onesy twosies here and there go to the registering then discover screen. After rebooting them several times they eventually come up with no changes to programming. Any suggestions?

 

[Zowwie438]

I was actually going to talk about DHCP issues like G3siv12 did!

From a TCP layer... Some DHCP servers act funny! There was a time when linux DHCP servers had some issues answering windows machines, but that was long ago.

The best way to track this down and figure out EXACTLY what is going on is:

1) Go crab yourself a copy of TCPDUMP... Pref for linux, but they have it for windows as well.

2) Issue a command similar to tcpdump -s0 -X port dhcp

3) Plug that bad boy into the same subnet as that phone and you will be able to see all the DHCP requests going across the LAN and the response given. From there you can get a better handle of exactly what is occuring. You will see the initial request to the DHCP server and the response.

4) Some DHCP servers get a little goofy from time to time and they may not properly hand out and address.

5) Sometimes... Your network admin or someone else may accidently block DHCP requests.

6) Another issue that is more common and this may be the source of your issue is... Some yahoo who is on the same subnet has:
a) Plugged in a wireless router with DHCP.
b) Plugged in a personal firewall/bug with DHCP.
c) Has turned on DHCP on a linux machine or a windows server.

What happens is... Your phone powers on and says "HEY, DHCP!!! Give me somethin good to use!" Normally, DHCP will say "Hey MAC 12:12:12:12, you can use 172.122.10.09 until 12/01/2007 @ 11:59PM"

However... When there are TWO DHCP servers on the same subnet... It get's REALLY STRANGE and sometimes it will work and sometimes it will not. It can range from device to device as well!

If the system worked fine for X time and all of a sudden it started actin goofy... The TCPDUMP will show you the request going out and how many responses it gets. If you see more than 1 response being returned from a different source... Then you have to do the foot work and identify every cubical location that is on that switch in your closet. And/or... Keep sending a DHCP request out and watch your responses while you unplug each cable.

Once isolated... You can go to their desk and smash the offending device with a stapler! LOL

Good luck and I hope my long winded explanation helps ya!

Zowwie

 

[Zowwie438]

BTW.. One more thing I forgot to mention.

If you have another DHCP server on the same subnet.. The symptoms will be:

1) Certain devices can't pull an IP sometimes.

2) Other devices may never be able to pull them.. Depends on latency and collisions in responses.

3) You will slowly start to lose more and more devices. One user may work fine at one desk, and the desk right next to it can fail. Then the next day, it may be reversed.

I hope that my info helps and good luck!