Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Wanet Telecoms Ltd on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Two issues with H.323 6.8.202 update 1

Status
Not open for further replies.

romero830

Systems Engineer
May 21, 2019
7
US
Good afternoon all, I have a bit of an issue with the newest release(6.8.202) of h.323 firmware for the 9608 devices, and hoping that you may have some insight or ideas as to what the issue may be.

1. The update has been applied to all but about 143 of our call center phones. Of these 143 that were not updated, they are sitting on releases 6.6401 (2 phones), 6.6506 (7 phones) and 6.6604 (134 phones). After a restart of the phone, the update appears that it is applying to the phone, but after the Kernel update reaches 100% complete, there is a 1-2 second delay, and then the phone contacts the call server and then connects the phone after verifying that it is registered. Upon checking the firmware on the phone, it shows the old release instead of the new 6.8202 version. Of the phones that are able to successfully update to the new version, there is a delay after the kernel reaches 100%,around 2-3 minutes at times.

I have tried performing reboots; clearing/resetting values on the phone; attempted to downgrade to 6.6229 in order to attempt to update back to the newest; All result in a failed update and the phone staying on the current installed release.

2. The update has successfully updated to 2000+ phones, but a very small percentage (less than 100) of these phones no longer pass audio to/from the Handset. Picking up the receiver is registered and the line opens, but there is no audio when the handset is used. Speaker and Headset devices work flawlessly. Downgrading back to the previous version (6.6604) resolves the issue.

I have searched and scoured through the forum and Google with no luck so far of anyone else having either of these issues after this specific update. And due to the security nature of the release, management is not willing to roll back to the previous release. Any input or suggestions are welcomed and will be greatly appreciated!

Thank you,

Christopher Romero, ACIS Telecom Engineer.
 
Watching this thread closely as I'm putting 6.8.202 in the lab today.
 
Can you check if the phones are of different hardware vintage and manufacturing dates? 9608D01A-1009, Serial 11XX.. (circa 2011), for example. Perhaps a pattern will develop.
 
@ZeroZeroOne

I was able to get the details on a few phones from one of the locations where Audio was not passing the the handset.

Model: 9608G 101
Product ID: 700505424/9608D03B-1009
SN: All start with "16WZ53300-"

As for the devices that will not update, Here is one example that I have on hand in office.

Model: 9608 R45
Product ID: 700504844/9608D02B-1009
SN: Starts with "15N515-"


I have another 5 in a remote location in the following model:

Model: 9608G 110
Product ID: 700505424/9608D03B-1009
SN: All Start with 19WZ11-

Thank you,

Christopher Romero, ACIS Telecom Engineer.
 
Do you use vpn phones at all? I am facing an issue with the 6.8.x firmware where if you log in a J169 phone in at the office and then log in using a 9620 vpn phone at home. The J169 would be logged out showing extension in use. The J169 phone eventually locks up completely and is unresponsive. The solution is to reboot.
 
Did 20 phones yesterday. A few production but mostly lab. Mix of B189 and 9611/9641. As of now, no issues to report.
 
Are you using wired plantronic headsets? A patch is being developed to fix audio issues with headsets. If you do I would suggest opening a ticket with avaya to get the patch. They are only releasing the patch for 6.8.2 until it is available in 6.8.3.
 
Update:
We have resolved the issue where we some devices were not receiving the update. Turns out that one of our System Administrator's had made a change to the DHCP scopes for the live environment, instead of to the test one that we requested. After correcting the DHCP scope for the 242 option, we were able to successfully update all remaining phones in the system to the newest firmware release.

We do however still have an issue with no audio in the handset of about 105 devices. They are the newer 9608G model so we are trying to determine if all affected phones are from the same batches, or if there is anything else that identifies as the cause.


Thank you,

Christopher Romero, ACIS Telecom Engineer.
 
FINAL UPDATE:

Avaya Tier 4 support was finally able to find the cause of the issue, and came back with a work-around solution for the time being, will be patched on the 6.8.3 release that is slated for mid/late November.

**Current Workaround involved changing ADMIN_HSEQUAL setting from ‘2’ to ‘1’. 1 is the default setting for wide-band frequency for voice. We had it set to ‘2’ to provide Hearing Aid Compatibility. This change resolved the issue on all 9608G phones



Thank you,

Christopher Romero, ACIS Telecom Engineer.
 
Did tier4 confirm the problem is only with 9608G phones? What hardware version?
 
Not sure about being specific to just the 9608G model, as we were the only group to have reported the issue at the time. So far, Avaya has not received any other reports of the issue. As for the specific model, it was the 9608D03B version that the issue occurred with.

Thank you,

Christopher Romero, ACIS Telecom Engineer.
 
thanks for the update. Non issue for me as I haven't changed ADMIN_HSEQUAL from default.
 
I got more information from Avaya:
This issue came in as a customer found defect (CFD) from one customer and got to R&D on 17 September. We found that it applies to 9608GD03B/9611GD02C/J169/J179 running 6.8.0/6.8.1/6.8.2 software. It happens if the phone is configured for Hearing Aid Compatibility (either via SET ADMIN_HSEQUAL 2 or Options -> Advanced Options -> Handset Equalization -> HAC Option). It is fixed in the next service pack scheduled for the end of November. As noted in the external posting, the workaround is to not enable Hearing Aid Compatibility.”
 
Update from avaya: they were able to reproduce the issue of the phone locking up and they think they have identified the cause. Stay tuned for what caused it and the updated firmware.
 
Thanks for the update! We are reviewing the release notes now.

Thank you,

Christopher Romero, ACIS Telecom Engineer.
 
Just wanted to let you know Avaya has come up with a potential patch for the J169 screen freezing up. Open up a ticket with Avaya to gain access: 96x1-IPT-H323-R6_8_2_1T_rb984775-112919.zip
 
This is the developers explanation of the phone locking up: “The application processes(tasks) work simultaneously with synchronization.
In the case one process was stopped without releasing resources and other process was waiting for that resources at the same time
(infinitely, because the first one cannot be recovered in that state)“
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top