4620SW IP Rebooting

[busydisconnect]

S8720 3.1
We have a Media Gateway that has a couple 4620SW IP phone's that keeps rebooting of (couse it's a VP's phone) is anyone familiar with IP Event TCP_DOWN?

The phone looses all power even when on a call.

20090724:065406165:2871729:capro(5397):MED:[ IPEVT IPT_TCP_DOWN board=01E01 ip= 10.64.28.10 net_reg= 7 ext= 6834 ip= 10.64.66.52: 5134 net_reg= 7 reason=00000]

Things I've already done to troubleshoot:
Upgraded the firmware on the CLAN
Updated the firmware on the phones to 2.91
Swapped out the phones/cables

Other info:
Cisco POE
All other ip phones in that Network region are fine.

Thanks!!!

A lack of Planning On Your Part; Does Not Constitute an Emergency On My MINE!

 

[randyb19]

OK, a few things:

Are your MedPro firmware current?
Have you applied the latest patches to your S8720?

After that, go in the Maintenance Web for your S8720, choose Systems Logs on the left side (you will get a bunch of options to check off); try checking only "IP Events" and at the bottom for "Match Pattern" (don't forget to check it), put in IPEVT. Also, choose a date range from which the error occurred. This may give you more insight into what is happening.

 

[busydisconnect]

We’ve finally been able to duplicate our ip-phone reset issue in a test environment for the first time and have isolated the source of the problem to a POE power-recycle issue. (Below are the results)

20090929:142428883:1764826:capro(5309):MED:[ IPEVT IPT_TCP_DOWN board=01E11 ip= 10.64.28.107 net_reg= 7 ext= 6834 ip= 10.64.66.52: 3429 net_reg= 7 reason=00000]
20090929:142428885:1764829:capro(5309):MED:[ IPEVT IPT_REG board=01C01 ip= 10.64.28.8 net_reg= 7 ext= 6834 ip= 10.64.66.52:49300 net_reg= 7 reason=recovery]
20090929:142429023:1764830:capro(5309):MED:[ IPEVT IPT_TCP_UP board=01C01 ip= 10.64.28.8 net_reg= 7 ext= 6834 ip= 10.64.66.52: 6085 net_reg= 7 reason=endpoint_request]
20090929:155725765:1767018:capro(5309):MED:[ IPEVT IPT_TCP_DOWN board=01C01 ip= 10.64.28.8 net_reg= 1 ext= 1131 ip= 10.64.13.35: 5710 net_reg= 1 reason=00000]
20090929:155725766:1767019:capro(5309):MED:[ IPEVT IPT_REG board=01C01 ip= 10.64.28.8 net_reg= 1 ext= 1131 ip= 10.64.13.35:49300 net_reg= 1 reason=recovery]
20090929:155725805:1767020:capro(5309):MED:[ IPEVT IPT_TCP_UP board=01C01 ip= 10.64.28.8 net_reg= 1 ext= 1131 ip= 10.64.13.35: 2097 net_reg= 1 reason=endpoint_request]
20090929:164806721:1767481:capro(5309):MED:[ IPEVT IPT_TCP_DOWN board=01C01 ip= 10.64.28.8 net_reg= 1 ext= 1131 ip= 10.64.13.35: 2097 net_reg= 1 reason=00000]
20090929:164806721:1767482:capro(5309):MED:[ IPEVT IPT_REG board=01C01 ip= 10.64.28.8 net_reg= 1 ext= 1131 ip= 10.64.13.35:49300 net_reg= 1 reason=recovery]
20090929:164806760:1767483:capro(5309):MED:[ IPEVT IPT_TCP_UP board=01C01 ip= 10.64.28.8 net_reg= 1 ext= 1131 ip= 10.64.13.35: 2527 net_reg= 1 reason=endpoint_request]

Our 4620SW get their power from the Cisco 3560 servers and a trouble ticket has been opened up with Cisco to troubleshoot the issue on the routers.
__________________

A lack of Planning On Your Part; Does Not Constitute an Emergency On My MINE!