The end key does not operate correctly on softconsole running V2.1(24) it will disconect all callers not just the active one, this was an intermitant problem with V2.1(15) as well.
Avaya do have a private Build that resolves this issuebut do not plan to put t on general release (yet).
I would recomend you get your distributor to put preasure on Avaya for this build.
Many thanks, how the hell do avaya expect us to keep up with the firmware releases when they seem to have to update them every week or so to fix the fix that the fix was supposed to fix.
I would NOT stick with 2.1.15 the buglist for it is HUGE. Either go to 2.1.24 if you don't use softconsole, or downgrade the units to 2.0.18 (which is relatively stable).
I have tested today the latest SC with IPO406 2.1.24. I had DT phones and analoque phones. Using the analoque phone (with headset so off-hook mode) with SC worked fine.....using the DT phone (without headset so normnal handset), did not work. Unfortenalety couldn't finalise testing. My first idea at this moment was the off-hook mode) Will continue testing tommorrow. Keep yoú posted!
Great news for those of us in North America! I just tried softconsole with 2.1.24, and this is NOT an issue when using DS phones. Tried it with and without a headset
This issue with the del key and DT Phones it seems.....does pressing the hang up button on SC work fine? Or is it in general hanging up will disconnect both parties?
Finally tested the SC with DT phones. It's a problem with DT phones only as far as I can tell.
Avaya's answer (via Crane) is "sorry, we know, wait for V3.0....."
The only thing that's really stable lately is the poor quality of Avaya testing. I still can't believe that they force us poor resellers to be Avaya certified. For what??? We must spend 1000's of euros to get no support, bugfull software and lot's of non-documented features.
There is a reason why we only build one tunnel to that island....And yes we know, we shouldn't even have done that.
(what...do I sound frustrated??....no...after 5 years one couldn't expect a different behaviour).
If any Avaya employee is in fact reading this forum and is seriously involved in making the product better and stable: Please stop working on this V3 thing and resolve all those small issues we have to explain over and over again to the customers.......
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.