Code:
APP_VERSION:
1505856
PACKAGE_NAME:
com.tcx.sipphone14
PHONE_MODEL:
Pixel 2
ANDROID_VERSION:
9
BRAND:
google
PRODUCT:
walleye
BUILD_CONFIG:
APPLICATION_ID=com.tcx.sipphone14
BUILD_TYPE=release
DEBUG=false
FLAVOR=
VERSION_CODE=1505856
VERSION_NAME=15.5.400
Code:
Server Version: Standard 15.5.15502.6
Server OS: DebianThe above info was generated from "Send Logs". Please let me know if you need any further info.
Problem: Cannot answer calls on Android App on Pixel 2 running Android 9.0.0.
Basically if you press the answer button, it will stop ringing in the app, but the call will still continue ringing on the server. If I change the RTP mode from "Normal" to "Allow Secure/Only Secure" then the app can answer and hang up the call, but the caller will still hear the ringing tone.
Outbound calls from the app works fine. Only answering calls is the issue
This is not a SIP Trunk/Codec issue as indicated in this other thread https://www.3cx.com/community/threads/android-google-pixel-2-not-accepting-calls.60484/ because the mobile app can answer calls when it is on the office WiFi (same LAN as the 3CX server). The problem also occurs if the mobile is on 4G and an internal extension tries to call the mobile extension. (e.g. yealink ext 300 calls mobile extension on 305)
The issue seems to be specific to the Pixel 2 because the app is working fine on Samsung Note 8 (using Android 8) and a Pixel 3 XL (using Android 9). Also I've loaded the account that works fine on these phones onto the Pixel 2 and the problem continues. If you take the account from the Pixel 2 and provision it on the Note 8 or Pixel 3 XL, then it works fine.
I have tried several other things including:
- Uninstall the client, reboot, install the client from the store
- Change RTP mode from normal to "Allow Secure" or "Secure Only" and this allows the app to answer and hang up the call, but the call is not connected
- Set "PBX delivers Audio"
- Changed the order of the codecs - no difference
- Rebooted firewall
- Run firewall checker and passed
- Rebooted 3CX server
- Changed the transport mode to TCP, UDP and TLS
- Disabled/Enabled Push notifications
- Tried with and without the 3CX tunnel (app registers, the issue is only when trying to answer calls)
- Disabled NAT helper on the mobile
- I have made over 50 calls with different permutations of the above
https://www.3cx.com/blog/change-log/3cxphone-android-build-history/ that the Pixel 2 is specifically mentioned but it doesn't say whether this is with Android 8 or 9.
It would be great if anyone else could confirm/check this and hopefully come up with a solution or let us know if it's a "cannot/won't" fix type situation.
Please let me know if you need any other info. Thanks.
