Phone Type: NoPhone on R10 after it was working OK 1

[trinetintl]

Several weeks ago we successfully upgraded an IP Office to R10, about a week ago, the SonicWALL on a remote site was rebooted and all of a sudden the two phones there started to continually reboot. It seems the phone are registering and un-registering continually. We asked the IT guy to take the one of the "bad" phones to another remote site, site with working phones because we kept insisting that the router was blocking something. The IT guy unplugged a perfectly working phone, plugged the one that came from the "bad" site and the phone continue to reboot and un-registering itself, basically experiencing the same behavior, the problem reached critical mass when the IT guy then put the original phone back, phone that was working OK prior to the test and now that phone is rebooting and un-registering, it is behaving the same way as the "bad" phone. That put a big smile on the IT guys voice to say the least because now he can wash his hands off the problem and he can safely blame the PBX. When we take the phone to the same subnet of the IP Office, or connect the phone to the switch where the IP Office is located, phone registers without any problems. I can see it is an issue with the keep-alive any ideas?

13:48:53 2049919236mS H323Evt: Recv: RegistrationRequest 192.168.253.118; Extn(1551), time since last RRQ-KA 55023, Endpoints registered: 32; Endpoints in registration: 1
13:48:54 2049920414mS H323Evt: Recv: RegistrationRequest 192.168.254.144; Extn(1506), time since last RRQ-KA 55010, Endpoints registered: 32; Endpoints in registration: 1
13:48:54 2049920604mS H323Evt: Keep-alive time-out on 1557 (keep_alive_count 0)
13:48:54 2049920604mS H323Evt: GK: Unregister endpoint BHA_58fbc83352b15d3b for extension 1557 reason 2 urq_reason 3

13:48:55 2049921955mS H323Evt: Removing inactive H323 socket from 192.168.254.254:38121

RE

http://www.trinet-intl.com

APSS, AIPS

 

[amriddle01]

Well it's a network issue for sure, so switches or routers/firewalls or an addressing issue,.....but definitely network I'd say

 

[trinetintl]

Just found out something I did not know, it is bit concerning, it seems 5600 series IP phones are no longer supported on R10, could these phones be causing all the networking/registration issues? I would assume that if the 5610 phones are no longer supported it simply will not register or operate normally but will be isolated to that phone and not affect the rest of the phones plus we have several 5610 operating correctly on R10, kind of confusing.

RE

http://www.trinet-intl.com

APSS, AIPS

 

[amriddle01]

I doubt it vey much, I'd still focus on the network....

 

[TomMills]

Is the issue just with the 56xx or are the 96xx rebooting too?

APSS/ACIS/ACSS-SME
not arrogant, just succinct.

 

[trinetintl]

amriddle01, I tend to agree with you, but the way this mess came about has managed to plant a seed of uncertainty on the IT guy about the IP Office that I cannot manage to shake out. I checked the dates, the system was upgraded on April 7 of last month and only about a week ago things started to go haywire with the remote sites and just yesterday on the main site. We never had an IP Office fully established and in full production for days, let alone over a month go belly up like this, and not having full control of the network infrastructure to test and manage is a bit frustrating.

RE

http://www.trinet-intl.com

APSS, AIPS

 

[amriddle01]

Just put some phones on their own switch that you loan them and use the second LAN port, again avoid his/their sh1t altogether, I'll bet they never drop off then