Webex calls drop when answering from locked iPad in HexnodeSolved

Participant
Discussion
12 hours ago Nov 13, 2026
We manage a group of iPads with Hexnode and use the Webex app for calls. Incoming Webex calls still ring on the iPad lock screen, but when users swipe right to answer, the call immediately drops. If the iPad is already unlocked, the call connects normally.
This used to work, so I first wondered if APNs, notifications, or an MDM restriction could be causing it. The devices are not in kiosk mode. Lock screen notifications, Today View, and Control Center on the lock screen are allowed in the iOS restrictions policy. There is also a lock screen message/wallpaper policy applied, but nothing that should affect calls.
Has anyone seen Webex calls drop only when answering from the locked iPad screen?

Replies (1)

Marked SolutionPending Review
Hexnode Expert
34 minutes ago Nov 13, 2026
Marked SolutionPending Review

This behavior is unlikely to be caused by APNs if the incoming Webex call is already appearing on the lock screen. APNs is responsible for waking the device and presenting the incoming VoIP notification/call UI. Since that part is working, the drop is more likely happening during the iOS CallKit handoff after the swipe-to-answer action.

There is no Hexnode iOS restriction specifically designed to block the swipe gesture for answering calls from the lock screen.

A few useful checks:

  1. Confirm Webex notifications are allowed on the device under Settings > Notifications > Webex.
  2. Confirm Webex has the required iOS permissions under Settings > Webex.
  3. In the Hexnode iOS restrictions policy, make sure lock screen notifications are not disabled.
  4. If kiosk mode is configured, test outside kiosk mode. Kiosk restrictions can affect app behavior, but if these iPads are not in kiosk, this is less likely.
  5. Test the same Webex account and call flow on an unmanaged iPad or iPhone, preferably on the same network and then on another network.

If the issue happens only on managed devices, the next step would be to isolate the applied policies by temporarily testing with restrictions removed from one device. If the same behavior occurs on an unmanaged device, it points away from Hexnode and toward a Webex/iPadOS lock-screen call handling issue.

Regards,

Mary Romero

Save