9610 won't communicate with system

[argent3993]

Hi! I have a 9610 phone that is acting strange. It's been working fine for 18 months. But now when it boots, it hangs on 'Discovering 10.1.0.26' - which is our IP office server. We're running IPO Server Edition v10.1.0.1.0 build 3.

I have 60 other phones on the network - all working fine - but they are all model 9611G. This is the only 9610 - it's a courtesy phone in our lobby. On boot, it gives an error HTTP: -905, says 'No File Server Address' and then hangs on the 'Discovering' screen. I have the appropriate options listed in DHCP - both on 176 and 242. Specifically...

176-> MCIPADD=10.1.0.26,MCPORT=1719,TFTPSRVR=10.1.0.26
242-> MCIPADD=10.1.0.26,MCPORT=1719,HTTPSRVR=10.1.0.26

Prior to today, I just had option 242 and did not have option 176. I added it to see if it would resolve the issue - which it hasn't. I've also reset the phone back to factory defaults via the CLEAR option. Not sure what else to try.

Any ideas? Thanks!

 

[Nutritional_Info]

Have you tried manually setting the values, ie a static address, call / file servers, etc?

 

[argent3993]

Not yet. The admin in me *hates* to statically address anything, but I will try that 1st thing in the morning.

 

[janni78]

I'm assuming this is a 5610 and not 9610 ?

You should change option 176 to MCIPADD=10.1.0.26,MCPORT=1719,TFTPSRVR=10.1.0.26,HTTPSRVR=10.1.0.26 since never firmware of 56xx uses HTTP instead of TFTP.

For testing purposes using static values is good.

Are the phones and IP Office on the same subnet?
If not something might changed in a firewall just affecting the 5610 phone.

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

 

[Pepp77]

Janni - nope it is a 9610 - a very basic 96 series designed for lobby type areas. It should use the same options as the other 96 series phones. I would place the phone where a working one is to see if it is the network connection or the phone.

| ACSS SME |

 

[argent3993]

Yes - it's a 9610, not a 5610. I took the phone from the lobby back to IT and plugged it in to a working drop to do initial troubleshooting. Got the same results. I haven't specifically tested the original drop it was plugged into - but will do that today as well.

This phone is actually on a different subnet than the IPO server. IPO is located at 10.1.0.26 - on the 10.1.0.0/20 subnet. This particular phone is on the 10.2.0.0/20 subnet.

I actually have phones on the 10.1.0.0/20, 10.2.0.0/20, and 10.3.0.0/20 subnets. All phones except this one are working normally. There haven't been any router changes (no firewall between subnets - just the router). Not sure what would affect just the 9610 and not the 9611G. To the best of my knowledge, the 9610 is an H323 phone just like the 9611G.

Will be headed to the office in just a bit. Will try to statically assign the phone to see what happens.

 

[Pepp77]

Could well be the phone is just borked, especially if it is having the same symptoms where another phone works. It does happen.

| ACSS SME |

 

[janni78]

So there is a 9610 ! Never seen that one =)

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

 

[derfloh]

Probably 9601? It is only supported on CM.

IP Office remote service

https://www.fwilke.com/home

Fixed price SIP trunk configuration:

https://www.fwilke.com/en/ip-office-sip-trunk-en/

CLI based cale blocking:

https://blog.fwilke.com/ip-office-block-calls-from-specific-cli/

SCN fallback over PSTN:

https://blog.fwilke.com/ip-office-scn-fallback/

 

[Pepp77]

Now I am confused. If it is a 9610 how has it ever worked on an IPO,considering it does appear to be CM only. (My original google just found an Avaya 9610 and I went no further )

| ACSS SME |

 

[tlpeter]

The 9610 never worked and not supported either.

BAZINGA!

I'm not insane, my mother had me tested!

 

[sizbut]

Indeed.

9610 - never ever supported on IP Office.

9001 - never ever supported on IP Office.

If it ever worked with an IP Office then it was by luck or accident.

Stuck in a never ending cycle of file copying.

 

[argent3993]

No joy on statically addressing the phone. Actually almost behaved as if it wasn't statically IP addressed. I went in and set all the appropriate values, rebooted the phone - and still got the HTTP -905 error and the 'No File Server Address' message, even though I had manually entered it on the config screen. Phone wouldn't respond to a ping, either (not sure if it would at this point, but anyway..)

Just very odd. I'm going to temporarily replace it with a 9611G that's been locked down as much as possible. Will get my hands on another 9610 and go from there.

Thanks for the all the suggestions...

 

[argent3993]

Hmm - just saw the other comments about the 9610 not working with IPO. Maybe it was just dumb luck that it had been working???

Any other suggestions for a basic IP handset for IPO? Intended use is as a courtesy/lobby-type phone.

 

[Nutritional_Info]

If you upgrade to R11, I'd recommend the J129.

I you have digital ports on your system, a 1408 would do you justice, or 9504.