After standby the app cant establish a call / WINDOWS 11

[Giorgio-Germani]

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

---

Steps to reproduce

1. Have Talk running, stop using it and close it to its minimized in the Taskbar
2. Go in Standby and let 1 day pass
3. Next day open Talk and try to resume a call.

Expected behaviour

Establish the call

Actual behaviour

After opening Talk i see my last used chat. I click start call. The call rings, the other party answers, the calls drops and reconnects. Reconnection repeats, no call can be established.

CTRL Shift L didn't provide any logs. Shortcut seems to not function.

Only after a closing the app completely (clearing from ram) and opening it it would work as expected. I think there might be a session issue after a longer break. If the app would simply force refresh if sessions timed out it might be solved. The server side works fine.

[ShGKme]

Please provide the diagnosis report as the bug report template.

[Giorgio-Germani]

Diagnosis report

Nextcloud Talk Desktop
Version	v1.2.5
Built-in Talk version	v21.1.2
Release channel	stable
Operating system	Windows_NT 10.0.26100 (Windows 11 Pro)
Executable Path	C:\Users\Admin\AppData\Local\NextcloudTalk\app-1.2.5\Nextcloud Talk.exe
Connected to	-
Nextcloud version	31.0.7
Nextcloud Talk version	21.1.2
notifications app enabled	✅ yes
notify_push app enabled	✅ yes

Application config

{
  "launchAtStartup": false,
  "theme": "default",
  "systemTitleBar": false,
  "monochromeTrayIcon": false,
  "zoomFactor": 1,
  "playSoundChat": "respect-dnd",
  "playSoundCall": "respect-dnd",
  "enableCallbox": "respect-dnd",
  "secondarySpeaker": false,
  "secondarySpeakerDevice": null,
  "trustedFingerprints": []
}

[Antreesy]

Hi @Giorgio-Germani

Session recovery should be handled equally on client and webpage. There's an experimental feature to attempt reconnecting you may try, if you have access to webserver terminal commands: occ config:app:set spreed experiments_users --value=2 After that, try to log out / log in to update capabilities and see the effect

[Giorgio-Germani]

Here is a video that shows the Problem. Once you reload the App things work fine.

[ShGKme]

Could you run the client from the terminal and show the output if there are any errors?

In legacy PowerShell or new pwsh:

& 'C:\Users\Admin\AppData\Local\NextcloudTalk\app-1.2.5\Nextcloud Talk.exe'

In CMD:

"C:\Users\Admin\AppData\Local\NextcloudTalk\app-1.2.5\Nextcloud Talk.exe"

[Giorgio-Germani]

Yes there is the following:

Vue Devtools extension is installed [14208:0730/160333.820:ERROR:services\network\p2p\socket_manager.cc:137] Failed to resolve address for cloud.reventor.eu., errorcode: -105 [14208:0730/160333.821:ERROR:services\network\p2p\socket_manager.cc:137] Failed to resolve address for cloud.reventor.eu., errorcode: -105 [14208:0730/160333.821:ERROR:services\network\p2p\socket_manager.cc:137] Failed to resolve address for cloud.reventor.eu., errorcode: -105 [14208:0730/160333.821:ERROR:services\network\p2p\socket_manager.cc:137] Failed to resolve address for cloud.reventor.eu., errorcode: -105 [14208:0730/160333.823:ERROR:services\network\p2p\socket_manager.cc:137] Failed to resolve address for cloud.reventor.eu., errorcode: -105 [14208:0730/160333.823:ERROR:services\network\p2p\socket_manager.cc:137] Failed to resolve address for cloud.reventor.eu., errorcode: -105 [14208:0730/160333.871:ERROR:services\network\p2p\socket_manager.cc:137] Failed to resolve address for cloud.reventor.eu., errorcode: -105 [14208:0730/160333.871:ERROR:services\network\p2p\socket_manager.cc:137] Failed to resolve address for cloud.reventor.eu., errorcode: -105 [14208:0730/160333.873:ERROR:services\network\p2p\socket_manager.cc:137] Failed to resolve address for cloud.reventor.eu., errorcode: -105 [14208:0730/160333.873:ERROR:services\network\p2p\socket_manager.cc:137] Failed to resolve address for cloud.reventor.eu., errorcode: -105 [14208:0730/160413.147:ERROR:services\network\p2p\socket_manager.cc:137] Failed to resolve address for cloud.reventor.eu., errorcode: -105 [14208:0730/160413.147:ERROR:services\network\p2p\socket_manager.cc:137] Failed to resolve address for cloud.reventor.eu., errorcode: -105 [14208:0730/160413.216:ERROR:services\network\p2p\socket_manager.cc:137] Failed to resolve address for cloud.reventor.eu., errorcode: -105 [14208:0730/160413.216:ERROR:services\network\p2p\socket_manager.cc:137] Failed to resolve address for cloud.reventor.eu., errorcode: -105 [14208:0730/160413.217:ERROR:services\network\p2p\socket_manager.cc:137] Failed to resolve address for cloud.reventor.eu., errorcode: -105 [14208:0730/160413.217:ERROR:services\network\p2p\socket_manager.cc:137] Failed to resolve address for cloud.reventor.eu., errorcode: -105

I also recorded a video of this test.