2 registration requests from WSS users

Hi guys, each user on sip sends 2 requests for register (each 120seconds). After 1 one i get Unauthorized, and only after this user send a string with Authorization and only after it he sends OK. Why such thing happend?

server*CLI> pjsip show history entry 356
<— History Entry 356 Received from AAA.AAA.AAA.AAA:49355 at 1594191642 —>
REGISTER sip:ip.somedomain.com SIP/2.0
Via: SIP/2.0/WSS 0cjap9104qvk.invalid;received=AAA.AAA.AAA.AAA;branch=z9hG4bK6031126
Max-Forwards: 69
To: sip:someid@ip.somedomain.com
From: “User 33” sip:someid@ip.somedomain.com;tag=s2tlqvfvtv
Call-ID: tb607u21fa71vup6fphvt8
CSeq: 17 REGISTER
Contact: sip:87mnjdri@0cjap9104qvk.invalid;transport=ws;expires=600;+sip.ice;reg-id=1;+sip.instance=“urn:uuid:a97c9ac0-bbd2-4457-9b5d-3af24329bf38
Expires: 600
Allow: INVITE, ACK, CANCEL, BYE, UPDATE, MESSAGE, OPTIONS, REFER, INFO, NOTIFY
Supported: path, gruu, outbound
User-Agent: JsSIP 3.4.2
Content-Length: 0
Content-Length: 0

server*CLI>pjsip show history entry 357
<— History Entry 357 Sent to AAA.AAA.AAA.AAA:49355 at 1594191642 —>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/WSS 0cjap9104qvk.invalid;rport=49355;received=AAA.AAA.AAA.AAA;branch=z9hG4bK6031126
Call-ID: tb607u21fa71vup6fphvt8
From: “User 33” sip:someid@ip.somedomain.com;tag=s2tlqvfvtv
To: sip:someid@ip.somedomain.com;tag=z9hG4bK6031126
CSeq: 17 REGISTER
WWW-Authenticate: Digest realm=“asterisk”,nonce=“1594191642/df0d58d9807b5ca916d55ae4aaabaec3”,opaque=“138b01cf618d4a2a”,algorithm=md5,qop=“auth”
Server: Asterisk PBX 17.5.1
Content-Length: 0

server*CLI> pjsip show history entry 358
<— History Entry 358 Received from AAA.AAA.AAA.AAA:49355 at 1594191643 —>
REGISTER sip:ip.somedomain.com SIP/2.0
Via: SIP/2.0/WSS 0cjap9104qvk.invalid;received=AAA.AAA.AAA.AAA;branch=z9hG4bK93510
Max-Forwards: 69
To: sip:someid@ip.somedomain.com
From: “User 33” sip:someid@ip.somedomain.com;tag=s2tlqvfvtv
Call-ID: tb607u21fa71vup6fphvt8
CSeq: 18 REGISTER
Authorization: Digest username=“someid”, realm=“asterisk”, nonce=“1594191642/df0d58d9807b5ca916d55ae4aaabaec3”, uri=“sip:ip.somedomain.com”, response=“ee0d5134a66438c1cf8b323ff436473d”, algorithm=MD5, cnonce=“kpmlhcr2q7ht”, opaque=“138b01cf618d4a2a”, qop=auth, nc=00000001
Contact: sip:87mnjdri@0cjap9104qvk.invalid;transport=ws;expires=600;+sip.ice;reg-id=1;+sip.instance=“urn:uuid:a97c9ac0-bbd2-4457-9b5d-3af24329bf38
Expires: 600
Allow: INVITE, ACK, CANCEL, BYE, UPDATE, MESSAGE, OPTIONS, REFER, INFO, NOTIFY
Supported: path, gruu, outbound
User-Agent: JsSIP 3.4.2
Content-Length: 0
Content-Length: 0

Because that is the standard SIP authentication handshake.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.