From Release 2.0 onwards, the Avaya Flare Experience product has been rebranded as Avaya Communicator. All Avaya Flare Experience for iPad users will be prompted by iTunes to update Avaya Communicator for iPad.
As of 11th August 2014 Avaya Flare Experience for iPad is no longer be available for installation from the App Store. Users will not be able to roll back from Avaya Communicator for iPad 2.0 to Avaya Flare® Experience 1.2 after the upgrade.
The update is designed to be seamless and the existing configuration will be retained across the upgrade. All features of Avaya Flare Experience 1.2 that are supported with IP Office 8.1 FP1+ and 9.0 carry forward with this new Avaya Communicator 2.0 update.
Support for 3rd Party Server Certificates: Avaya Communicator has improved security through new certificate handling procedures. For more information, see Updating server certificates to improve end-user security and client user experience on the Avaya support site:( )
For changing existing settings: Tap the Settings button at the top left of the Avaya Communicator for iPad client, For Fresh Installation: When you are prompted "how you like to auto-configure the client setting?", choose the following option for IP Office: "I will manually configure my services".
Phone Server Address: Enter your server address for make and receive phone calls on the Avaya Communicator client. You can also enter a fully-qualified domain name (FQDN) of the IP Office server., Phone Server Port: Enter your port number. If you do not specify a port number, the system uses the default port number, Phone Service Domain: Enter your enterprise's SIP domain (domain of your company's Avaya IP Office network for example, a domain could be example.com)
Note: When you enable TLS on Avaya Communicator client, the SIP signalling between Avaya Session Border Controller for Enterprise (ASBCE) and Avaya Communicator client is encrypted and authenticated. Users may report that they can successfully login with Avaya Flare Experience for iPad but fail to login Avaya Communicator even though they enter the same User Name and Password(s). For a comprehensive review of how Avaya Communicator uses certificates and recommendations for updating server certificates to comply with new requirements, please refer to "Updating server certificates to improve end-user security and client user experience", available from support.avaya.com:
My work has an Avaya one-x communicator. I have set up the phone in the past to call my cell phone instead of my desk phone. I was in the office one day and used my desk phone. Since that time the desk phone will not transfer to cell. I have had all tech people in company look - they say the Avaya is set up correctly. I had changed some settings on my phone, but can't seem to find what I may have done. PLEASE HELP!!
Yeah, I had a feeling you might say that, except I did that first and we verified that the application is forwarding calls to any other numbers and phones and as previously stated, all settings on the application are correct.
The phone automatically goes to voice mail when forwarded to the Verizon cell number. A user calls the number using Avaya One X to forward to Verizon cell, the Call is forwarded to the cell and the user gets voice mail after a single ring.
This is starting to get extremely frustrating. What I actually said was that I have been successful in forwarding calls from the Avaya One-X to OTHER PHONES / NUMBERS. What has been UNSUCCESSFUL is forwarding any calls to the Verizon cell phone from Avaya One-X. And no, my settings on my cell phone have not changed in the past few months to prevent the calls from being forwarded. I beg of you to please stop trying to make this about a third party issue, it is not. This is an issue with Verizon accepting calls from Avaya One-X, as represented by the other user(s) who have raised this issue. Clearly the support staff is not interesting in seriously looking into and resolving this problem. Perhaps it is time to take my business elsewhere. Thank you for your time.
We know that it is imporant to have your desk phone working properly. Thanks for all your hard work in an effort to resolve this issue and we want to help. Are you able to setup the call forwarding to a different number? To confirm, you changed settings on your cellphone or desk phone before the issue started?
PamelaF_VZW
Follow us on Twitter @VZWSupport
If my response answered your question please click the "Correct Answer" button under my response. This ensures others can benefit from our conversation. Thanks in advance for your help with this!!
I doubt anybody has put any development effort into h.323 softclients in a long time, especially third party open source clients. The industry has moved onto SIP and now WebRTC (which may or may not use SIP as its signaling protocol).
It sounds like your company policy has mandated h.323 in a windows environment and thats OK, but you'll likely see Avaya retire one-x communicator in preference of Equinox clients in the not so distant future and then you'll be in a SIP environment or WebRTC if you use the clientless web version.
7fc3f7cf58