Project

General

Profile

Actions

Support #2185

closed

Timeouts and calls not received - User case 19403

Added by Vahnish Itamar 4 months ago. Updated 4 months ago.

Status:
Closed
Priority:
High
Assignee:
Target version:
Start date:
2024-07-21
Due date:
% Done:

0%

Estimated time:
Session tokens:
3a62173453344e00bb9fef01f2b640f0, fce10ab6b83e4d11bb44f37ab1b375a5, ac22d68ae3ff4ccfb7457cbc319be65b, 8ea70df5a32242e88685313ccd9b8259

Description

We have a user reporting that she cannot make calls incoming or outgoing to the watch.

She get's a timeout or the watch doesn't receive the messages at all.

I attached some sessions for you to look at:

3a62173453344e00bb9fef01f2b640f0
fce10ab6b83e4d11bb44f37ab1b375a5
ac22d68ae3ff4ccfb7457cbc319be65b
8ea70df5a32242e88685313ccd9b8259

Logs are attached from the watch side. I will attach the phone side once she sends it to me. Let me know what you think. I did not see anything other than early TIMEOUTS.

Actions #1

Updated by Oded Arbel 4 months ago

  • Status changed from New to Closed

There were no watch logs attached to the ticket.

From looking at the session data, in all cases the call was cancelled after the watch callee did not connect, and only the first session it was an actual ring timeout - in all other cases the caller disconnected the call after waiting less than 20 seconds. The session logs also show that all RegistrationFree incoming call notifications were delivered correctly and received a 200 OK from Trackimo's servers.

If the watch logs show that the watch did not receive the call notification, then it is out of Cloudonix hands - neither the Cloudonix Platform nor the Mobile SDK seem to be involved in this issue.

Feel free to reopen the issue if you have more information.

Actions

Also available in: Atom PDF