Like this:
Accounts:
bonjour@local:
display_name = Adrian
enabled = true
rtp:
video_codec_list = VP9, H264, VP8
video_codec_order = VP9, H264, VP8
encryption:
enabled = true
sip:
auto_answer =
That section must be added to your account settings, in the same section,
inside Accounts.
You edited the wrong section, BlinkSettings.
Adrian
> On 17 Aug 2021, at 09:25, g4-l...@tonarchiv.ch wrote:
>
> Sadly this didn't work.
>
> On Ubuntu I found the .blink/config file with this part:
>
Thanks again!
I will forward this note to the SIP provider.
Cheers
Till
On 17.08.21 14:09, Adrian Georgescu wrote:
> The server must send 401 in order to challenge the client, then the client
> replies with another Publish with Auth headers.
>
> Adrian
>
>
>> On 17 Aug 2021, at 09:01,
The server is miss-behaving.
Adrian
> On 17 Aug 2021, at 09:09, Adrian Georgescu wrote:
>
> The server must send 401 in order to challenge the client, then the client
> replies with another Publish with Auth headers.
>
> Adrian
>
>
>> On 17 Aug 2021, at 09:01, g4-l...@tonarchiv.ch wrote:
The server must send 401 in order to challenge the client, then the client
replies with another Publish with Auth headers.
Adrian
> On 17 Aug 2021, at 09:01, g4-l...@tonarchiv.ch wrote:
>
> Ah I understand. Thanks for the explanation.
>
> Why don't the PUBLISH messages have an auth header?
Ah I understand. Thanks for the explanation.
Why don't the PUBLISH messages have an auth header? Is this not in the
RFC? The missing auth header is the reason why the server rejects the
PUBLISH messages...
Cheers
Till
On 17.08.21 13:57, Adrian Georgescu wrote:
> The Publish interval is used to
Perfect! Thanks for your reply. I will check this.
Regards,
Till
On 17.08.21 13:41, Adrian Georgescu wrote:
> To disable sending PUBLISH you can edit the configuration file ~/.blink and
> add this section:
>
>+-- enabled = False
> presence --|
>+
>
> Indentation is
The Publish interval is used to refresh a Publish that was successful. If the
Publish fails, like in your case, the client will retransmit it based on other
internal timers depending on the reason of the failure.
Adrian
> On 16 Aug 2021, at 10:46, g4-l...@tonarchiv.ch wrote:
>
> Anyone there?
To disable sending PUBLISH you can edit the configuration file ~/.blink and add
this section:
+-- enabled = False
presence --|
+
Indentation is critical make a backup of the file in case something goes wrong
during or with the editing.
Alternatively you can install
For me the biggest problem with Blink is the lack of support.
I have no idea why there are so many PUBLISH sip messages issued by
Blink. I think the Publish Interval is the expiration tome set for each
PUBLISH message, not the time between PUBLISH messages. My (limited)
understanding is the
Anyone there?
This seems to be a bug: I set SIP Publish Interval to 3600 seconds. But
in the log I see that Blink sends the PUBLISH message at least once a
minute...
Cheers
T. Wimmer
On 12.08.21 21:39, g4-l...@tonarchiv.ch wrote:
> Hi there,
>
> My SIP provider asked me to disable SIP PUBLISH
Hi there,
My SIP provider asked me to disable SIP PUBLISH on my Blink client.
Their system answers with "400 Invalid auth header", and as far as I
understand, their server will eventually drop the connection for DoS
reasons. (DoS with one request every 10 minutes??)
Now I wonder if auth headers
12 matches
Mail list logo
