3CX on Android kiosk tablets shows “telephony service is null” and calls failSolved

Welcome to the Hexnode Community. For 3CX in Android kiosk mode, there are two separate areas to check:

1. Notifications and incoming call visibility: If the status bar is disabled in the kiosk policy’s peripheral settings, incoming call notifications may not be accessible. Enable the status bar if users need to interact with call notifications.
2. App permissions: Make sure the required permissions for 3CX, especially microphone and related device permissions, are granted through the policy. This avoids users having to manually approve permissions on each tablet.

If the error changes to “telephony service is null”, test the app in these states:

• Kiosk mode enabled
• Kiosk mode disabled
• Hexnode policy removed from the device.

If the same error appears even after removing the policy, it usually means Hexnode is not blocking the app. The issue is likely related to how 3CX is interacting with the Android device’s telephony framework.

I tested it with kiosk enabled, kiosk disabled, and then with the policies removed completely. The same “telephony service is null” message still appears. These are Wi-Fi-only Android tablets, not phones. Could that be related?

Yes, that detail is important. The “telephony service is null” error can occur when 3CX tries to use Android’s native Telecom/telephony APIs as if the device has a cellular phone framework. On Wi-Fi-only tablets or hardware without a SIM/cellular module, that framework may not be available, so Android returns a null telephony service. In that case, the fix is usually inside the 3CX app rather than in Hexnode:

1. Open the 3CX app on the Android tablet.
2. Go to Settings > Advanced.
3. Look for the Telecom API / Car API / Bluetooth API Integration option.
4. Toggle that setting to use the alternative API route, or disable native Telecom API integration if that is the available option.

This stops 3CX from trying to route calls through the missing cellular telephony framework. After changing it, test incoming and outgoing calls again.
You can still keep the Hexnode kiosk policy in place. Just ensure the status bar and required app permissions are configured correctly if users need call notifications and microphone access.

That worked. Toggling the Telecom API / Car API / Bluetooth API Integration setting in 3CX fixed the issue and calls are working now. So the kiosk policy was not the root cause, but enabling the status bar and granting the app permissions were still needed for notifications and microphone access.