Avaya Support Forums  

Go Back   Avaya Support Forums > Telephones, Adjuncts, and Adapters

Thread Tools Search this Thread Display Modes
Old 02-07-2020, 09:02 AM
chayco chayco is offline
Aspiring Member
Join Date: Dec 2019
Location: UK
Posts: 1
chayco has 10 reputation points
Default 1616-i handset failing to register after network failure.

My customer has a mixed environment of IP handsets 1616-I (h323) and 9611G (h323), on the same VLAN.

Comm Mgr V6.3.1, duplicated servers with media gateways. No IPSIs or CLANs.
H.323 handsets
1616-I firmware 1.312 (latest)

In normal service the phones work as expected, I can unplug a phone and plug it back in again and the phone will boot, download settings and register as normal.

There have recently been some issues with the LAN which has caused the phones to loose layer 3 connectivity to the core CM (handset power still retained). In this situation the phone loses registration (as expected) the 1616-I phones then display a message alternating between "no filesv" and "no callsv" with the phone restarting every few minutes and coming back to the same message. Once the LAN is restored the 9611G phones happily reconnect and register automatically. However the 1616-I phones are now stuck in this state and the only way to fix the issue is to go through the craft clear process to clear all the values, which allows it to boot and register. This means going to every phone to clear them and then logging the phone back in again,

I can replicate the problem by removing the voice VLAN from the network LAN port. After the VLAN is added back the phone still can't recover without manual intervention.

Can anyone suggest anything to try that will avoid manually resetting the phones every time or whether this is a known issue with 1616-I handsets?

Upgrading to 96xx phones is not an option and obviously the network team need to stop the issue with the LAN, but the phones should be able to recover from this type of problem.



Reply With Quote
Old 02-11-2020, 09:43 AM
mlombardi1's Avatar
mlombardi1 mlombardi1 is offline
Join Date: Sep 2010
Location: New York
Posts: 510
mlombardi1 has 25 to 49 reputation pointsmlombardi1 has 25 to 49 reputation pointsmlombardi1 has 25 to 49 reputation points

Strange. When the phones are in limbo, do they still have an IP on the voice VLAN that is pingable from CM?
Reply With Quote

1616-i, no callsv, no filesv

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

All times are GMT -7. The time now is 12:42 AM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.