search

jsxc / xmpp-cloud-auth

:key: Authentication hub for Nextcloud+JSXC→Prosody, ejabberd, saslauthd, Postfix
https://www.jsxc.org
MIT License
60 stars 18 forks source link

Problem with audio-video calls (STUN USER) #91

Open susobaco opened 1 year ago

susobaco commented 1 year ago

Hello, I have been testing audio or video calls and I have observed that they are performed well from the browser:

_76: : session 001000000000000004: peer 192.168.*.* lifetime updated: 300 76: : session 001000000000000004: realm <***.org> user <1686138035>: incoming packet CREATE_PERMISSION processed, success 76: : session 001000000000000004: peer 192.168.*.* lifetime updated: 300 76: : session 001000000000000004: realm <***.org> user <1686138035>: incoming packet CREATE_PERMISSION processed, success 76: : session 001000000000000004: peer 192.168.*.* lifetime updated: 300 76: : session 001000000000000004: realm <***.org> user <1686138035>: incoming packet CREATE_PERMISSION processed, success 76: : session 001000000000000004: peer 192.168.*.* lifetime updated: 300 76: : session 001000000000000004: realm <***.org> user <1686138035>: incoming packet CREATE_PERMISSION processed, success 76: : session 001000000000000004: peer 192.168.*.* lifetime updated: 300 76: : session 001000000000000004: realm <***.org> user <1686138035>: incoming packet CREATE_PERMISSION processed, success 76: : session 001000000000000004: peer 192.168.*.* lifetime updated: 300 76: : session 001000000000000004: realm <***.org> user <1686138035>: incoming packet CREATE_PERMISSION processed, success 76: : session 001000000000000001: peer *.*.. lifetime updated: 300 76: : session 001000000000000001: realm <**.org> user <1686136213:.org>: incoming packet CREATE_PERMISSION processed, success 76: : session 001000000000000002: peer *.*.. lifetime updated: 300 76: : session 001000000000000002: realm <**.org> user <1686136213:.org>: incoming packet CREATE_PERMISSION processed, success 76: : session 001000000000000004: peer 192.168.*.* lifetime updated: 600 76: : session 001000000000000004: realm <***.org> user <1686138035>: incoming packet CHANNELBIND processed, success 78: : session 001000000000000004: refreshed, realm=<.org>, username=<1686138035>, lifetime=0 78: : session 001000000000000004: realm <.org> user <1686138035>: incoming packet REFRESH processed, success 78: : session 001000000000000001: refreshed, realm=<.org>, username=<1686136213:.org>, lifetime=0 78: : session 000000000000000002: refreshed, realm=<.org>, username=<1686136213:.org>, lifetime=0 78: : session 001000000000000001: realm <.org> user <1686136213:.org>: incoming packet REFRESH processed, success 78: : session 000000000000000002: realm <.org> user <1686136213:.org>: incoming packet REFRESH processed, success 78: : session 001000000000000002: refreshed, realm=<.org>, username=<1686136213:.org>, lifetime=0 78: : session 001000000000000002: realm <.org> user <1686136213:.org>: incoming packet REFRESH processed, success 78: : session 001000000000000003: refreshed, realm=<.org>, username=<1686136213:.org>, lifetime=0 78: : session 001000000000000003: realm <.org> user <1686136213:.org>: incoming packet REFRESH processed, success 79: : session 001000000000000004: usage: realm=<.org>, username=<1686138035>, rp=92, rb=15624, sp=117, sb=13365 79: : session 001000000000000004: peer usage: realm=<.org>, username=<1686138035>, rp=106, rb=11697, sp=81, sb=14013 79: : session 001000000000000004: closed (2nd stage), user <1686138035> realm <***.org> origin <>, local 0.0.0.0:3478, remote ..*.*:43259, reason: allocation timeout 79: : session 001000000000000004: delete: realm=<***.org>, username=<1686138035>

But, when making them from an external client, (Dino or Conversations) there is an error at the time of authentication on the STUN server, the user is missing.

turnserver[578]: 257: : session 000000000000000016: realm <*****.org> user <>: incoming packet message processed, error 401: Unauthorized

Could this be due to a registration problem of this program?