Hi guys,
Indeed this week we have updated flexisip to be able to handle
SHA-256 algorithm but it seems to break the register in the old
desktop client.
Until we have a fix for this we disabled SHA-256, it should be
working again now.
Cheers,
Le 30/08/2019 à 20:58, Echedey a
écrit :
Are you using the last
version of FlexiSIP server and 4.1.1 version of the desktop
client?
Could you test that client with an account on the Linphone SIP
service?
I attached my log trying registration on the main service.
30 de agosto de 2019 19:52, "Russell Treleaven" < address@hidden>
escribió:
Latest client on osx is working fine with
my own sip server.
On Fri, Aug 30, 2019, 2:45 PM Echedey
López Romero < address@hidden>
wrote:
It is strange, this
issues only happen on desktop client for some people
here. No problem on mobile client.
If its related with the FlexiSIP server from Linphone
free SIP service I would prefer wait on a report in
the desktop client repo for devs confirmation if its
is an issue from server side or client side. It is
true that maybe they changed something in the server
but that could be a "good change" that mobile clients
from them already supported and they must update the
desktop client now.
Regards,
Echedey, López RomeroEl 30 ago. 2019 19:25, El Pato
<address@hidden>
escribió:
>
> I have 2 PJSIP clients that worked fine for
months. They both started failing auth on August 28
around 1:30 in the morning Pacific Daylight Time.
>
> My logs captured the event:
>
> 2019-08-28:2019-08-29,01:34:02.457 WARNING
MainThread account.onRegState 0 171100 401 sip:address@hidden
Unauthorized
>
> 2019-08-28:2019-08-29,01:25:57.602 WARNING
MainThread onRegState 0 171100 Unauthorized 401
>
> After this event, every subsequent registration
fails with "server rejected with stale=false". This
has been going on for over 2 days now.
>
> PJSIP Status 171100 = PJSIP_EFAILEDCREDENTIAL.
>
> The docs for PJSIP_EFAILEDCREDENTIAL say
> "Credential failed to authenticate. For this
failure, right credential for the realm has been found
and used to authenticate against the challenge, but
the server has rejected the authorization request with
401/407 response (either with no stale parameter or
with "stale=false" parameter). In most cases, this
indicates that the username/password combination is
incorrect. "
>
> Something is broken with the linphone sip server,
it is rejecting valid username/password combinations.
>
_______________________________________________
Linphone-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/linphone-users
--
Regards,
Echedey, López Romero
_______________________________________________
Linphone-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/linphone-users
|