Calls are not working Android

ℹ️ Support 💬 Talk (spreed)
1

[no app in context] Error: RedisException: Connection lost at <>

  1. /var/www/html/lib/private/Memcache/Redis.php line 72
    Redis->get(“eb32eeafbe31a11 … w”)
  2. /var/www/html/custom_apps/spreed/lib/Chat/ChatManager.php line 669
    OC\Memcache\Redis->get(“zq5o8htw”)
  3. /var/www/html/custom_apps/spreed/lib/Chat/ChatManager.php line 653
    OCA\Talk\Chat\ChatManager->checkCacheOrDatabase([“OCA\Talk\Room”], 885, 100, false)
  4. /var/www/html/custom_apps/spreed/lib/Chat/ChatManager.php line 630
    OCA\Talk\Chat\ChatManager->waitForNewMessagesWithCache([“OCA\Talk\Room”], 885, 100, 30, false)
  5. /var/www/html/custom_apps/spreed/lib/Controller/ChatController.php line 461
    OCA\Talk\Chat\ChatManager->waitForNewMessages([“OCA\Talk\Room”], 885, 100, 30, [“OC\User\User”], false, true)
  6. /var/www/html/lib/private/AppFramework/Http/Dispatcher.php line 230
    OCA\Talk\Controller\ChatController->receiveMessages(1, 100, 885, 0, 30, 0, 0, 0, 1)
  7. /var/www/html/lib/private/AppFramework/Http/Dispatcher.php line 137
    OC\AppFramework\Http\Dispatcher->executeController([“OCA\Talk\Controller\ChatController”], “receiveMessages”)
  8. /var/www/html/lib/private/AppFramework/App.php line 183
    OC\AppFramework\Http\Dispatcher->dispatch([“OCA\Talk\Controller\ChatController”], “receiveMessages”)
  9. /var/www/html/lib/private/Route/Router.php line 315
    OC\AppFramework\App::main(“OCA\Talk\Controller\ChatController”, “receiveMessages”, ["OC\AppFramewo … "], [“v1”,“zq5o8htw” … "])
  10. /var/www/html/ocs/v1.php line 64
    OC\Route\Router->match(“/ocsapp/apps/sp … w”)
  11. /var/www/html/ocs/v2.php line 23
    require_once(“/var/www/html/ocs/v1.php”)

GET /ocs/v2.php/apps/spreed/api/v1/chat/zq5o8htw?setReadMarker=0&lookIntoFuture=1&lastKnownMessageId=885&includeLastKnown=0
from x.x.x.x by admin at 2023-09-11T18:54:43+00:00

2

Hi, do you run into a specific issue or why are you posting this here?

3

Hi. My calls are not working.
Here are the problems that are in the logs

  1. |Error|no app in context|RedisException: Connection lost|
  2. |Error|PHP|Redis::get(): php_network_getaddresses: getaddrinfo for nextcloud-aio-redis failed: Name does not resolve at /var/www/html/lib/private/Memcache/Redis.php#72|
4

Can you follow How to debug problems with Collabora and/or Talk · nextcloud/all-in-one · Discussion #1358 · GitHub?

The redis error is likely unrelated and caused by Random connectivity issues when enabling ipv6 for the internal network · nextcloud/all-in-one · Discussion #2557 · GitHub

5

/etc/hosts
127.0.0.1 localhost
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
— BEGIN PVE —
127.0.1.1 talk
— END PVE —

Nextcloud Talk

  • processing: x/standalone-signaling/api/v1/welcome
  • Trying x:443…
  • Connected to x port 443
  • ALPN: offers h2,http/1.1
  • TLSv1.3 (OUT), TLS handshake, Client hello (1):
  • CAfile: /etc/ssl/certs/ca-certificates.crt
  • CApath: none
  • TLSv1.3 (IN), TLS handshake, Server hello (2):
  • TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
  • TLSv1.3 (IN), TLS handshake, Certificate (11):
  • TLSv1.3 (IN), TLS handshake, CERT verify (15):
  • TLSv1.3 (IN), TLS handshake, Finished (20):
  • TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
  • TLSv1.3 (OUT), TLS handshake, Finished (20):
  • SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
  • ALPN: server accepted h2
  • Server certificate:
  • subject: CN=x
  • start date: Sep 8 19:06:30 2023 GMT
  • expire date: Dec 7 19:06:29 2023 GMT
  • subjectAltName: host “x” matched cert’s “x”
  • issuer: C=US; O=Let’s Encrypt; CN=R3
  • SSL certificate verify ok.
  • TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
  • using HTTP/2
  • h2 [:method: GET]
  • h2 [:scheme: https]
  • h2 [:authority: x]
  • h2 [:path: /standalone-signaling/api/v1/welcome]
  • h2 [user-agent: curl/8.2.1]
  • h2 [accept: /]
  • Using Stream ID: 1

GET /standalone-signaling/api/v1/welcome HTTP/2
Host: x
User-Agent: curl/8.2.1
Accept: /

< HTTP/2 200
< alt-svc: h3=“:443”; ma=2592000
< content-type: application/json; charset=utf-8
< date: Tue, 12 Sep 2023 13:41:55 GMT
< server: Caddy
< server: nextcloud-spreed-signaling/12de5a9b71afef06eaf171099712ef0a5f6ca0c4
< x-spreed-signaling-features: audio-video-permissions, hello-v2, incall-all, mcu, simulcast, switchto, transient-data, update-sdp, welcome
< content-length: 94
<
{“nextcloud-spreed-signaling”:“Welcome”,“version”:“12de5a9b71afef06eaf171099712ef0a5f6ca0c4”}

  • Connection #0 to host x left intact
    exit
6

Looks good. If you visit the talk admin settings, and check turn server for example, do you get a connection error? https://yourncdomain.com/settings/admin/talk

7

all ok

Знімок екрана 2023-09-12 165241
Знімок екрана 2023-09-12 1652411611×785 33.1 KB

8

Is it only a specific device from which calls do not work? Can you also try from a different network for testing?

9

Not working on all my android devices: Pixel 4xl, Samsung A02s, Infinix note 12 2023 and some xiaomi. tried from different networks

10

Does it work via browser?

11

yes, it works via browser

12

Then it is most likely an issue of the android talk app Issues · nextcloud/talk-android · GitHub

13

There is one more clarification: calls in group chats work fine.

update:
On a Samsung smartphone, the talk application has requested screen overlay permission. I gave him this permission - 1 on 1 calls worked.
Google and Infinix phones have such an option in the settings, but there is no Nexcloud Talk item in the list of applications

update 2:
i think it’s a problem with the app Nextcloud Talk.
itself doesn’t ask for overlay permission and also doesn’t show up in the overlay app settings list.
My devices are running Android 13

1 Like
14

I think that I have found a problem why notifications on smart phones do not work in nextcloud-talk.
In the browser - user - personal settings - language - set the Ukrainian language - then call notifications do not work. If you turn English back on, everything seems to be fine.
This is a program bug