- Joined
- Feb 24, 2019
- Messages
- 9
- Reaction score
- 0
Hello,
I have tested 3cx during many hours and configured it deeply before writing this post.
I still have a quite big issue, the click to call feature from webclient only rely on uaCTSA compatibility, so it cannot work with basic phones or DECT, only way to make it works is to register all extensions on Android client but then the status is alway connected even if extension is not registered.
I saw on forum that it was not the case on previous version. Why relying only on uaCTSA and not allow all registered phone to a extension to ring basically (as seen in phone section of management console).... Really a shame for users.
I want to migrate from my custom provider asterisk web interface (with click to call fonction and enterprise directory) which are greatly appreciated by users and I choose 3cx alternative due to it webclient. But this limit around the exclusive use of uaCTSA is all locking down...
Really bad to not allow parameter in extension or a global setting to do not rely only on uaCSTA but rely basically on SIP registering status...
Hope there is a workaround or I hope 3cx will understand that this choice is greatly locking down feature of their webclient.
I have tested 3cx during many hours and configured it deeply before writing this post.
I still have a quite big issue, the click to call feature from webclient only rely on uaCTSA compatibility, so it cannot work with basic phones or DECT, only way to make it works is to register all extensions on Android client but then the status is alway connected even if extension is not registered.
I saw on forum that it was not the case on previous version. Why relying only on uaCTSA and not allow all registered phone to a extension to ring basically (as seen in phone section of management console).... Really a shame for users.
I want to migrate from my custom provider asterisk web interface (with click to call fonction and enterprise directory) which are greatly appreciated by users and I choose 3cx alternative due to it webclient. But this limit around the exclusive use of uaCTSA is all locking down...
Really bad to not allow parameter in extension or a global setting to do not rely only on uaCSTA but rely basically on SIP registering status...
Hope there is a workaround or I hope 3cx will understand that this choice is greatly locking down feature of their webclient.
Last edited:
