Re: incoming packet message processed, error 401: Unauthorized

2020-10-19 Thread Ali Alhaidary
I had the same case, however, after some tweeks and mainly replacing realm with the static IP and removing user:password parameter, I can hardly see 401 in turn log and the request gets authenticated directly, but I can still find just few in hundreds of lines of turn log. On 10/20/20 5:00 AM,

Re: incoming packet message processed, error 401: Unauthorized

2020-10-19 Thread Maxim Solodovnik
Correction: just have double checked and there are some 401 This might be the part of SDP Initial response is 401, then goes authentication part, and then communication this can be checked with Wireshark On Tue, 20 Oct 2020 at 08:54, Maxim Solodovnik wrote: > > > On Tue, 20 Oct 2020 at 08:39,

Re: incoming packet message processed, error 401: Unauthorized

2020-10-19 Thread seba.wag...@gmail.com
Which logs? we especially mean CoTurn Server log. It looks like this: 1528379: session 001335: realm user <>: incoming packet message processed, error 401: Unauthorized Thanks Seb Sebastian Wagner Director Arrakeen Solutions http://arrakeen-solutions.co.nz/

Re: incoming packet message processed, error 401: Unauthorized

2020-10-19 Thread Maxim Solodovnik
On Tue, 20 Oct 2020 at 08:39, seba.wag...@gmail.com wrote: > I had the same question recently. > > I can see the same behaviour in Turn Logs. The first request fails with > 401, and subsequent requests get handled and authenticated. > > The connection works, on turn side as well as the media Serv

Re: incoming packet message processed, error 401: Unauthorized

2020-10-19 Thread seba.wag...@gmail.com
I had the same question recently. I can see the same behaviour in Turn Logs. The first request fails with 401, and subsequent requests get handled and authenticated. The connection works, on turn side as well as the media Server connection works fine. But every connection attempt logs one 401. Ev

Re: incoming packet message processed, error 401: Unauthorized

2020-10-19 Thread Ali Alhaidary
Thank you, I was looking into https://mail-archives.apache.org/mod_mbox/openmeetings-user/202010.mbox/browser that did not have search :-) I will try them and return to you. On 10/19/20 5:13 PM, Maxim Solodovnik wrote: I would use search in ML archives directly: https://openmeetings.markmail

Re: incoming packet message processed, error 401: Unauthorized

2020-10-19 Thread Maxim Solodovnik
I would use search in ML archives directly: https://openmeetings.markmail.org/ this I was able to find this https://markmail.org/message/d6ifllraemj6dz6v post :)) On Mon, 19 Oct 2020 at 17:23, Ali Alhaidary wrote: > when googling it, ideas were conflicting, some say that this is a > legitimate e

Re: incoming packet message processed, error 401: Unauthorized

2020-10-19 Thread Ali Alhaidary
when googling it, ideas were conflicting, some say that this is a legitimate error, even in the ML, the issue was raided many times, but could not find a conclusive solution. Would you please send me your .conf file. On 10/19/20 11:04 AM, Maxim Solodovnik wrote: 401 means your TURN parameters

Re: incoming packet message processed, error 401: Unauthorized

2020-10-19 Thread Maxim Solodovnik
401 means your TURN parameters most probably are incorrect were you able to find and check my config? (should be searchable at ML archives) On Sun, 18 Oct 2020 at 23:52, Ali Alhaidary wrote: > as the above message is so much frequent in turn log, could the bellow > be the remedy: > > https://git

incoming packet message processed, error 401: Unauthorized

2020-10-18 Thread Ali Alhaidary
as the above message is so much frequent in turn log, could the bellow be the remedy: https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/-/issues/1226