Hello!
The question is a pretty similar to this one
https://www.3cx.com/community/threads/third-party-app-doesnt-call-through-3cx-android-app.70619/
We have an app that suppose to invoke a default dialer that places a call directly. For example, we have a "Call" button in our app and we expect a default dialer is launched that places a call to the given extension immediately without user interaction. It works fine with android system dialer and a bunch of other 3rd party apps, but not with 3CX. Accordingly to the logcat traces, OS seems to recognize 3CX app as the default dialer but it invokes a system dialed app instead.
Just to clarify: there are 2 ways to invoke a dialer from android app:
1. Using ACTION_DIAL intent action. In this case a dialer screen is being opened and the requested extension is displayed in the input field. The user can make any changes or just initiate a call. This scenario works fine with 3CX.
2. Using ACTION_CALL intent action. In this case a dialer screen is being opened, that immediately initiates a call to the requested extension without any user input. This scenario is failed by 3CX app.
In short, our questions are:
1. Is it even possible for 3CX app to handle ACTION_CALL intents?
2. If so, what are the success conditions? Currently 3cx app does not provide any feedback neither in UI or in logcat. Thus it's impossible to investigate a possible failure reason. Could it be client app settings / server-side configurarion / uri schema issues or so?
Thanks in advance!
The question is a pretty similar to this one
https://www.3cx.com/community/threads/third-party-app-doesnt-call-through-3cx-android-app.70619/
We have an app that suppose to invoke a default dialer that places a call directly. For example, we have a "Call" button in our app and we expect a default dialer is launched that places a call to the given extension immediately without user interaction. It works fine with android system dialer and a bunch of other 3rd party apps, but not with 3CX. Accordingly to the logcat traces, OS seems to recognize 3CX app as the default dialer but it invokes a system dialed app instead.
Just to clarify: there are 2 ways to invoke a dialer from android app:
1. Using ACTION_DIAL intent action. In this case a dialer screen is being opened and the requested extension is displayed in the input field. The user can make any changes or just initiate a call. This scenario works fine with 3CX.
2. Using ACTION_CALL intent action. In this case a dialer screen is being opened, that immediately initiates a call to the requested extension without any user input. This scenario is failed by 3CX app.
In short, our questions are:
1. Is it even possible for 3CX app to handle ACTION_CALL intents?
2. If so, what are the success conditions? Currently 3cx app does not provide any feedback neither in UI or in logcat. Thus it's impossible to investigate a possible failure reason. Could it be client app settings / server-side configurarion / uri schema issues or so?
Thanks in advance!
