Call-Log for 16XX phones with fw 1.3.5b

[Smovk]

After upgrading to 1.3.5 on 16xx phones the Call Log is not displayed correctly, the last call is not displayed but the previous one is.
Is this a bug ?

 

[Avayell]

I have the exact same problem with one of my customers with 1.3.5 . I have opened a ticket just today.

 

[Avayell]

The ticket is now closed because the IP Phones are not covered by the contract. Does anyone know whom should we refer to, perhaps someone from the team that design the firmwares, in order to fix the issue on a newer firmware?

 

[jmbailey]

We too have an issue with the call log button and firmware 1.35b. Our issue, however, is that when the call log button is pressed, the phone will freeze and then reboot. We have worked with Avaya and they have captured Wireshark sniffer traffic and have sent the info to Avaya's Teir 4 for analysis.

 

[Smovk]

Avaya support reproduced this problem with 1.35b firmware in their lab, they told me this is firmware bug and now it is on Avaya Teir4.

 

[jmbailey]

Yes, Teir 4 has it. They had 2 RSEs collect packet sniffs during the event. They updated us on Friday that they indeed find an issue but need additional more detailed logs and will be coming to site Wednesday to grab additional data.

 

[Avayell]

Does anyone know if there are any news on that? Is there going to be a new firmware soon? Customers are dissapointed.

 

[jmbailey]

Tier 4 needs additional/more detailed debug info from the 1616 events during the call-log button issue. We are expecting an RSE onsite in the next day or so to grab the additional logs. He was here last Wednesday, but Avaya sent him the wrong cable for the line tap he was supposed to use for the capture so he couldn't complete the work.

 

[Smovk]

This bug will be fixed in new firmware. It will be avaliable on 26.9. This is info ftom avaya support

 

[jmbailey]

Hearing the same thing but also tempered a bit. Avaya doesn't appear to be 100% confident in the update as they are sending a RSE out to our site again to gather additional debug info. Hopefully this is just to support what they think they need to fix rather than still researching.

 

[jmbailey]

FYI....

Avaya just sent us a pre-release (pre-GA) firmware to try on the phones with the call log issue. They are currently planning to roll out the new version of firmware (tentatively) on 9/29.

We are going to try the new firmware on a couple of trouble phones tomorrow and see what happens. We'll let you know what we find.

 

[jmbailey]

All,

The new firmware that Avaya provided for us to test has worked. In addition, we have determined how the problem occurs (at least in our environment) and how to correct it temporarily. It is actually a setting in the phone relating to the type of Redial.

Here are the directions we have provided to some of our users to correct the issue:

• Press the menu button on your phone (directly to the left of the #1 key on your dialpad)
• Scroll down and select “Call Settings”
• Scroll down till you see “Redial”
• Change the redial setting to “One” instead of “List”
• Select “Done” once the setting has been changed to “One”

 

[gwebster]

1.3.6 is on support portal -

https://support.avaya.com/downloads...?contentId=C201491911244250_3&productId=P0468