9650 Tepehones

[jamckay]

I know this has been covered many times, i just cannot find the forum, so here goes again.
I have a customer with CM 4.0.5 (S8800) and they are using IP telephone sets that are the 96xx series, they are complaining that the sets will just reset and when i check the system logs: under IP Events these reports are blank. Each date and time customer provides the logs under system log IP Events are always blank. It is like the server does not see the event.
does anyone have suggestions? Customer has the latest firmware for the 96xx phones. I believe it is something on the customers network but how would i prove it? Network sniff to the phone that resets the most? Thanks in advance

[sg]

Hi,

This is most likely to be an issue with the customer network. Please capture a sniffer trace (possibly bookend sniffer) and raise a service request with Avaya support team.

[aa1]

9650 Tepehones

- if the phone suddenly reboots, then there is a chance something triggers the firmware on the phone to reboot and it might be worth investigating other areas than the customer network. if customer network goes down, the phone will try the recovery algorithm for sometime (i.e., look for the gatekeeper, then alternative gatekeepers and then reboot after x amount of time) - provided that these parameters are configured properly.

- if the phone is not getting enough power over PoE (or there is power fluctuation), then this might trigger the phone to reboot

- Are there additional modules connected to it? they might drain more power.

- is the data swtich providing the necesary PoE?

- does the phone reboot while being used, or it just reboots when sitting idle?

- Do the phones all reboot at the same time? (or perhaps phones connected to a specific CLAN, or to a specific network region, or a specific data switch)?

- Are these remote phones?

- do only 9650s behave like this? or other IP phones as well?

- A reason why there is no event logs could be that event logging is disabled. Below are some details. "Log IP Registrations and events" on "change logging-levels" page 2.


Avaya one-X™ Deskphone H.323 Installation and Maintenance Guide Release 6.0 for 9608, 9611G, 9621G, and 9641G Deskphones
16-603603 Issue 1 August 2010
Chapter 5: Troubleshooting Guideline
http://support.avaya.com/css/P8/documents/100109255 (Page 59)


change logging-levels Page 2 of 2
LOGGING LEVELS
Log All Submission Failures: y
Log PMS/AD Transactions: y
Log IP Registrations and events: y <====
Log CTA/PSA/TTI Transactions: y


Avaya Aura™ Communication Manager Screen Reference
Release 6.0 03-602878 Issue 2.0 June 2010
http://support.avaya.com/css/P8/documents/100089489 (Page 576)
Log IP Registrations and Events
If enabled, allows the logging of IP registrations in the history log
Maintenance Procedures for Avaya Aura™ Communication Manager, Media Gateways and Servers
03-300432 Issue 7 August 2010
IP events
http://support.avaya.com/css/P8/documents/100089289 (Page 240)


Additional info:
****************
Administering Network Connectivity on Avaya Aura™ Communication Manager
555-233-504 Issue 15 Sept 2010
http://support.avaya.com/css/P8/documents/100110634


Avaya IP Telephony Deployment Technical Configuration Guide
http://support.avaya.com/css/P8/documents/100123695


suggestions:
**************
- it was suggested in the previous post, choose a phone that has been behaving like this for sometime and capture a network trace from both the phone side and the gatekeeper side. that will help you to check if the problem is possibly on customer network or not.


Hope these help.
Arbi