⬆️ ⬇️

Beta versions of 3CX clients for Android and iOS, and solving the problem with 3CX activation on Windows 7

This week we have some good news again - we released new 3CX mobile clients for Android and iOS (they are now in beta testing status), and found a solution to the activation problem that chased 3CX users on Windows 7 64 bit.



And now about everything in order!



Beta client version 3CX for Android



Introducing the beta version of the client 3CX for Android. He received an updated unified communications interface, an improved dialer interface, and full Russian localization. The application also reacts noticeably faster to user actions.



image


A major improvement is the built-in voice codec G729 - for free!

')

image




To get the beta version of the 3CX client for Android, register with the 3CX beta tester program on Google Play and install the new client. You may first need to remove an existing client to install a new one.



Beta client version 3CX for iOS



Simultaneously with the release of the beta version of the 3CX client for Android, we also released the beta version of the client for iOS. Please note - the client is designed for iOS v10!



iOS client has the same new features that appeared in the client for Android. In addition, thanks to Apple CallKit support, you are now managing VoIP calls in the same way as regular GSM calls! For example, an incoming GSM call does not put a VoIP call on hold — you decide which call to give preference to.







At the moment, the beta testing program is limited to the first 1000 Apple IDs that users have sent via the registration form. However, try asking for an invite to test in the comments to this news , specifying your Apple ID e-mail.



Solving the problem of activating 3CX on Windows 7 64 bit



Unfortunately, many users who decided to install 3CX on Windows, at the very last stage, had a strange activation error, accompanied by the appearance of a window with a message similar to the following:



license_error.HTTP/1.1 400 Bad Request Cache-Control: private Content-Length: 1647 Content-Type: text/html Server: Date: Fri, 11 Nov 2016 16:24:35 GMT 


image




Usually this error occurs when a firewall or HTTP proxy tries to filter packets. In this case, the correct activation is impossible, and the user is recommended to activate 3CX to bypass the proxy, or to temporarily disable the DPI .



However, in this case, users did not use DPI, and the reason was different - the computer name with Russian letters in Windows 7. By default, it is formed by the user name with the addition of the suffix –PC .







It is Russian characters in the computer name that cause an activation error! At the moment, we recommend simply renaming the computer, removing Cyrillic characters from the name , as shown in the figure. After renaming, reboot the computer. To complete the 3CX installation:





The following service packs will fix this error.

Source: https://habr.com/ru/post/315702/



All Articles