SIP INVITE via LoadBalaner with Require Incoming Auth Enabled

Yeti-Switch
1

Hi,

Do we need to setup header filtering or X-Yeti-Auth for the SIP INVITE via LoadBalancer that has Require Incoming Auth enabled in customer_athentication?

Apparently, SIP INVITE via LoadBalancer, it returns 401 Unauthorized and when I send the SIP Invite directly to SEMS(bypassing lb), it works. Although, authorization details are passed from Lb to Sems but the internal reason states: no match found.
401 Unauthorized Response NOT matched
401 Unauthorized no Authorization header

Interestingly, I am able to successfully SIP register via LB using the same credentials

Is this the expected behavior?

2

X-Yeti-Auth is not related to user/password auth mechanism

3

It depends on your configuration. In general authorization via load balancer should work. Have you added your balancer addresses to System->Load balancers?

4

Yes, loadbalancers IPs are already added in System → Load Balancer. in fact, I can successfully register a SIP device with SIP REGISTER request via LoadBalancer. It is just impacting SIP INVITE requests via lb to sems… any other suggestion?

My configuration is:
1.1.1.1 - PC IP
2.2.2.2 - LB node IP
2.2.2.3 - SEMS node IP

Find below, the SIP INVITE trace

SIP INVITE FROM UA to LB
2020/01/17 22:35:44.926498 1.1.1.1:5060 → 2.2.2.2:5060
INVITE sip:61411111111@2.2.2.2;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK-d8754z-820541289e32a3df-1—d8754z-
Max-Forwards: 70
Contact: sip:61811111111@1.1.1.1:5060;transport=UDP
To: sip:61411111111@2.2.2.2;transport=UDP
From: “61811111111"sip:61811111111@2.2.2.2;transport=UDP;tag=26255268
Call-ID: NzMzYzc4ZjkzODgwN2I2MzQzZDUxOTI1OTg0Y2FiYTE.
CSeq: 2 INVITE
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
Content-Type: application/sdp
Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri
User-Agent: Z 3.6.25251 r25476
Authorization: Digest username=“61811111111”,realm=“s.sems.com”,nonce=“C10542c771227e286239a2e202bbfca13a9”,uri="sip:61411111111@2.2.2.2;transport=UDP”,response=“b9a30e3e87d50a727f10b580a”,cnonce=“d6a6188238170743c03297d1632c”,nc=00000001,qop=auth-int,algorithm=MD5
Allow-Events: presence, kpml
Content-Length: 239

v=0
o=Z 0 0 IN IP4 1.1.1.1
s=Z
c=IN IP4 1.1.1.1
t=0 0
m=audio 8000 RTP/AVP 3 110 8 0 98 101
a=rtpmap:110 speex/8000
a=rtpmap:98 iLBC/8000
a=fmtp:98 mode=20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv

SIP INVITE FROM LB to SEMS
2020/01/17 22:35:44.928250 2.2.2.2:5060 → 2.2.2.3:7000
INVITE sip:61411111111@2.2.2.2;transport=UDP SIP/2.0
Record-Route: sip:2.2.2.2;lr;ftag=26255268
Via: SIP/2.0/UDP 2.2.2.2;branch=z9hG4bK7a01.05b8f4c6a6cd7b3c084cfc0386f9c3b9.0
Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK-d8754z-820541289e32a3df-1—d8754z-
Max-Forwards: 69
Contact: sip:61811111111@1.1.1.1:5060;transport=UDP
To: sip:61411111111@2.2.2.2;transport=UDP
From: “61811111111"sip:61811111111@2.2.2.2;transport=UDP;tag=26255268
Call-ID: NzMzYzc4ZjkzODgwN2I2MzQzZDUxOTI1OTg0Y2FiYTE.
CSeq: 2 INVITE
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
Content-Type: application/sdp
Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri
User-Agent: Z 3.6.25251 r25476
Authorization: Digest username=“61811111111”,realm=“s.sems.com”,nonce=“C10542c771227e286239a2e202bbfca13a9”,uri="sip:61411111111@2.2.2.2;transport=UDP”,response=“b9a30e3e87d50a727f10b580a”,cnonce=“d6a6188238170743c03297d1632c”,nc=00000001,qop=auth-int,algorithm=MD5
Allow-Events: presence, kpml
Content-Length: 239
X-ORIG-IP: 1.1.1.1
X-ORIG-PORT: 5060
X-ORIG-PROTO: 1

v=0
o=Z 0 0 IN IP4 1.1.1.1
s=Z
c=IN IP4 1.1.1.1
t=0 0
m=audio 8000 RTP/AVP 3 110 8 0 98 101
a=rtpmap:110 speex/8000
a=rtpmap:98 iLBC/8000
a=fmtp:98 mode=20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv

image
image855×851 29.7 KB

5

Could you provide full trace? your trace doesn’t contain 401 response.

401 Unauthorized Response NOT matched means - there is no credentials for request saved in aurth database. You could check output yeti.show.auth.credentials.all command at yeti-cli

6

Dmitry,

If credentials are not saved in the auth database, then how can it successfully register (SIP REGISTER) via loadBalancer and successfully send SIP INVITE requests directly to SEMS? it shouldn’t right?

The issue here seems to be very specific to SIP INVITE requests only via LoadBalancer.

Here is the full trace:

  • 1.1.1.1:1046 - PC IP
  • 2.2.2.2:5060 - LB IP
  • 2.2.2.3:7000 - SEMS IP

From SIP Client to LoadBalacer (I have masked few sensitive information)

2020/01/21 09:23:11.319909 1.1.1.1:1046 -> 2.2.2.2:5060
INVITE sip:6141111111@2.2.2.2;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 1.1.1.1:1046;branch=z9hG4bK-d8754z-18cad64f26ce0543-1—d8754z-
Max-Forwards: 70
Contact: sip:61811111111@1.1.1.1:1046;transport=UDP
To: sip:61411111111@2.2.2.2;transport=UDP
From: "61811111111"sip:61811111111@2.2.2.2;transport=UDP;tag=32062478
Call-ID: OTEzYTU5YTBkYTI3YWFhYTU0OGUzNGFlZWZjYTk5M2E.
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
Content-Type: application/sdp
Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri
User-Agent: Z 3.6.25251 r25476
Allow-Events: presence, kpml
Content-Length: 237

v=0
o=Z 0 0 IN IP4 1.1.1.1
s=Z
c=IN IP4 1.1.1.1
t=0 0
m=audio 8000 RTP/AVP 3 110 8 0 98 101
a=rtpmap:110 speex/8000
a=rtpmap:98 iLBC/8000
a=fmtp:98 mode=20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv

2020/01/21 09:23:11.320490 2.2.2.2:5060 -> 1.1.1.1:1046
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 1.1.1.1:1046;branch=z9hG4bK-d8754z-18cad64f26ce0543-1—d8754z-
To: sip:61411111111@2.2.2.2;transport=UDP
From: "61811111111"sip:61811111111@2.2.2.2;transport=UDP;tag=32062478
Call-ID: OTEzYTU5YTBkYTI3YWFhYTU0OGUzNGFlZWZjYTk5M2E.
CSeq: 1 INVITE
Content-Length: 0

2020/01/21 09:23:11.320574 2.2.2.2:5060 -> 2.2.2.3:7000
INVITE sip:61411111111@2.2.2.2;transport=UDP SIP/2.0
Record-Route: sip:2.2.2.2;lr;ftag=32062478
Via: SIP/2.0/UDP 2.2.2.2;branch=z9hG4bKc7cd.9e96c57612b68c34e6ac9941be03fb48.0
Via: SIP/2.0/UDP 1.1.1.1:1046;branch=z9hG4bK-d8754z-18cad64f26ce0543-1—d8754z-
Max-Forwards: 69
Contact: sip:61811111111@1.1.1.1:1046;transport=UDP
To: sip:61411111111@2.2.2.2;transport=UDP
From: "61811111111"sip:61811111111@2.2.2.2;transport=UDP;tag=32062478
Call-ID: OTEzYTU5YTBkYTI3YWFhYTU0OGUzNGFlZWZjYTk5M2E.
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
Content-Type: application/sdp
Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri
User-Agent: Z 3.6.25251 r25476
Allow-Events: presence, kpml
Content-Length: 237
X-ORIG-IP: 1.1.1.1
X-ORIG-PORT: 1046
X-ORIG-PROTO: 1

v=0
o=Z 0 0 IN IP4 1.1.1.1
s=Z
c=IN IP4 1.1.1.1
t=0 0
m=audio 8000 RTP/AVP 3 110 8 0 98 101
a=rtpmap:110 speex/8000
a=rtpmap:98 iLBC/8000
a=fmtp:98 mode=20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv

2020/01/21 09:23:11.321875 2.2.2.3:7000 -> 2.2.2.2:5060
SIP/2.0 100 Connecting
Record-Route: sip:2.2.2.2;lr;ftag=32062478
Via: SIP/2.0/UDP 2.2.2.2;branch=z9hG4bKc7cd.9e96c57612b68c34e6ac9941be03fb48.0
Via: SIP/2.0/UDP 1.1.1.1:1046;branch=z9hG4bK-d8754z-18cad64f26ce0543-1—d8754z-
To: sip:61411111111@2.2.2.2;transport=UDP
From: "61811111111"sip:61811111111@2.2.2.2;transport=UDP;tag=32062478
Call-ID: OTEzYTU5YTBkYTI3YWFhYTU0OGUzNGFlZWZjYTk5M2E.
CSeq: 1 INVITE
Server: SBC 1.8.34-5
Content-Length: 0

2020/01/21 09:23:11.331693 2.2.2.3:7000 -> 2.2.2.2:5060
SIP/2.0 401 Unauthorized
Record-Route: sip:2.2.2.2;lr;ftag=32062478
Via: SIP/2.0/UDP 2.2.2.2;branch=z9hG4bKc7cd.9e96c57612b68c34e6ac9941be03fb48.0
Via: SIP/2.0/UDP 1.1.1.1:1046;branch=z9hG4bK-d8754z-18cad64f26ce0543-1—d8754z-
To: sip:61411111111@2.2.2.2;transport=UDP;tag=8-4BC525CA-5E26284F0005100F-C5489700
From: "61811111111"sip:61811111111@2.2.2.2;transport=UDP;tag=32062478
Call-ID: OTEzYTU5YTBkYTI3YWFhYTU0OGUzNGFlZWZjYTk5M2E.
CSeq: 1 INVITE
WWW-Authenticate: Digest realm=“sems1.s.com”, qop=“auth,auth-int”, nonce=“Fa392da870f96fc863a1290587c5fd5f3”
Server: SBC 1.8.34-5
Content-Length: 0

2020/01/21 09:23:11.331800 2.2.2.2:5060 -> 2.2.2.3:7000
ACK sip:61411111111@2.2.2.2;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 2.2.2.2;branch=z9hG4bKc7cd.9e96c57612b68c34e6ac9941be03fb48.0
Max-Forwards: 69
To: sip:61411111111@2.2.2.2;transport=UDP;tag=8-4BC525CA-5E26284F0005100F-C5489700
From: "61811111111"sip:61811111111@2.2.2.2;transport=UDP;tag=32062478
Call-ID: OTEzYTU5YTBkYTI3YWFhYTU0OGUzNGFlZWZjYTk5M2E.
CSeq: 1 ACK
Content-Length: 0

2020/01/21 09:23:11.331909 2.2.2.2:5060 -> 1.1.1.1:1046
SIP/2.0 401 Unauthorized
Record-Route: sip:2.2.2.2;lr;ftag=32062478
Via: SIP/2.0/UDP 1.1.1.1:1046;branch=z9hG4bK-d8754z-18cad64f26ce0543-1—d8754z-
To: sip:61411111111@2.2.2.2;transport=UDP;tag=8-4BC525CA-5E26284F0005100F-C5489700
From: "61811111111"sip:61811111111@2.2.2.2;transport=UDP;tag=32062478
Call-ID: OTEzYTU5YTBkYTI3YWFhYTU0OGUzNGFlZWZjYTk5M2E.
CSeq: 1 INVITE
WWW-Authenticate: Digest realm=“sems1.s.com”, qop=“auth,auth-int”, nonce=“Fa392da870f96fc863a1290587c5fd5f3”
Server: SBC 1.8.34-5
Content-Length: 0

2020/01/21 09:23:11.353927 1.1.1.1:1046 -> 2.2.2.2:5060
ACK sip:61411111111@2.2.2.2;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 1.1.1.1:1046;branch=z9hG4bK-d8754z-18cad64f26ce0543-1—d8754z-
Max-Forwards: 70
To: sip:61411111111@2.2.2.2;transport=UDP;tag=8-4BC525CA-5E26284F0005100F-C5489700
From: "61811111111"sip:61811111111@2.2.2.2;transport=UDP;tag=32062478
Call-ID: OTEzYTU5YTBkYTI3YWFhYTU0OGUzNGFlZWZjYTk5M2E.
CSeq: 1 ACK
Content-Length: 0

2020/01/21 09:23:11.362695 1.1.1.1:1046 -> 2.2.2.2:5060
INVITE sip:61411111111@2.2.2.2;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 1.1.1.1:1046;branch=z9hG4bK-d8754z-fe048f983d100ce3-1—d8754z-
Max-Forwards: 70
Contact: sip:61811111111@1.1.1.1:1046;transport=UDP
To: sip:61411111111@2.2.2.2;transport=UDP
From: “61811111111"sip:61811111111@2.2.2.2;transport=UDP;tag=32062478
Call-ID: OTEzYTU5YTBkYTI3YWFhYTU0OGUzNGFlZWZjYTk5M2E.
CSeq: 2 INVITE
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
Content-Type: application/sdp
Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri
User-Agent: Z 3.6.25251 r25476
Authorization: Digest username=“61811111111”,realm=“sems1.s.com”,nonce=“Fa392da870f96fc863a1290587c5fd5f3”,uri="sip:61411111111@2.2.2.2;transport=UDP”,response=“3a59a1d7793
e62e19904bf9a6de240”,cnonce=“8ff1431f884a02c11b642024665”,nc=00000001,qop=auth-int,algorithm=MD5
Allow-Events: presence, kpml
Content-Length: 237

v=0
o=Z 0 0 IN IP4 1.1.1.1
s=Z
c=IN IP4 1.1.1.1
t=0 0
m=audio 8000 RTP/AVP 3 110 8 0 98 101
a=rtpmap:110 speex/8000
a=rtpmap:98 iLBC/8000
a=fmtp:98 mode=20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv

2020/01/21 09:23:11.362959 2.2.2.2:5060 -> 1.1.1.1:1046
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 1.1.1.1:1046;branch=z9hG4bK-d8754z-fe048f983d100ce3-1—d8754z-
To: sip:61411111111@2.2.2.2;transport=UDP
From: "61811111111"sip:61811111111@2.2.2.2;transport=UDP;tag=32062478
Call-ID: OTEzYTU5YTBkYTI3YWFhYTU0OGUzNGFlZWZjYTk5M2E.
CSeq: 2 INVITE
Content-Length: 0

2020/01/21 09:23:11.363021 2.2.2.2:5060 -> 2.2.2.3:7000
INVITE sip:61411111111@2.2.2.2;transport=UDP SIP/2.0
Record-Route: sip:2.2.2.2;lr;ftag=32062478
Via: SIP/2.0/UDP 2.2.2.2;branch=z9hG4bK97cd.a6298049075e61665740bfd02e633007.0
Via: SIP/2.0/UDP 1.1.1.1:1046;branch=z9hG4bK-d8754z-fe048f983d100ce3-1—d8754z-
Max-Forwards: 69
Contact: sip:61811111111@1.1.1.1:1046;transport=UDP
To: sip:61411111111@2.2.2.2;transport=UDP
From: “61811111111"sip:61811111111@2.2.2.2;transport=UDP;tag=32062478
Call-ID: OTEzYTU5YTBkYTI3YWFhYTU0OGUzNGFlZWZjYTk5M2E.
CSeq: 2 INVITE
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
Content-Type: application/sdp
Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri
User-Agent: Z 3.6.25251 r25476
Authorization: Digest username=“61811111111”,realm=“sems1.s.com”,nonce=“Fa392da870f96fc863a1290587c5fd5f3”,uri="sip:61411111111@2.2.2.2;transport=UDP”,response=“3a59a1d7793
e62e19904bf9a6de240”,cnonce=“8ff1431f884a02c11b642024665”,nc=00000001,qop=auth-int,algorithm=MD5
Allow-Events: presence, kpml
Content-Length: 237
X-ORIG-IP: 1.1.1.1
X-ORIG-PORT: 1046
X-ORIG-PROTO: 1

v=0
o=Z 0 0 IN IP4 1.1.1.1
s=Z
c=IN IP4 1.1.1.1
t=0 0
m=audio 8000 RTP/AVP 3 110 8 0 98 101
a=rtpmap:110 speex/8000
a=rtpmap:98 iLBC/8000
a=fmtp:98 mode=20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv

2020/01/21 09:23:11.363673 2.2.2.3:7000 -> 2.2.2.2:5060
SIP/2.0 100 Connecting
Record-Route: sip:2.2.2.2;lr;ftag=32062478
Via: SIP/2.0/UDP 2.2.2.2;branch=z9hG4bK97cd.a6298049075e61665740bfd02e633007.0
Via: SIP/2.0/UDP 1.1.1.1:1046;branch=z9hG4bK-d8754z-fe048f983d100ce3-1—d8754z-
To: sip:61411111111@2.2.2.2;transport=UDP
From: "61811111111"sip:61811111111@2.2.2.2;transport=UDP;tag=32062478
Call-ID: OTEzYTU5YTBkYTI3YWFhYTU0OGUzNGFlZWZjYTk5M2E.
CSeq: 2 INVITE
Server: SBC 1.8.34-5
Content-Length: 0

2020/01/21 09:23:11.364025 2.2.2.3:7000 -> 2.2.2.2:5060
SIP/2.0 401 Unauthorized
Record-Route: sip:2.2.2.2;lr;ftag=32062478
Via: SIP/2.0/UDP 2.2.2.2;branch=z9hG4bK97cd.a6298049075e61665740bfd02e633007.0
Via: SIP/2.0/UDP 1.1.1.1:1046;branch=z9hG4bK-d8754z-fe048f983d100ce3-1—d8754z-
To: sip:61411111111@2.2.2.2;transport=UDP;tag=8-186F88FB-5E26284F00058E5E-C5489700
From: "61811111111"sip:61811111111@2.2.2.2;transport=UDP;tag=32062478
Call-ID: OTEzYTU5YTBkYTI3YWFhYTU0OGUzNGFlZWZjYTk5M2E.
CSeq: 2 INVITE
WWW-Authenticate: Digest realm=“sems1.s.com”, qop=“auth,auth-int”, nonce=“Fa392da870f96fc863a1290587c5fd5f3”
Server: SBC 1.8.34-5
Content-Length: 0

2020/01/21 09:23:11.364143 2.2.2.2:5060 -> 2.2.2.3:7000
ACK sip:61411111111@2.2.2.2;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 2.2.2.2;branch=z9hG4bK97cd.a6298049075e61665740bfd02e633007.0
Max-Forwards: 69
To: sip:61411111111@2.2.2.2;transport=UDP;tag=8-186F88FB-5E26284F00058E5E-C5489700
From: "61811111111"sip:61811111111@2.2.2.2;transport=UDP;tag=32062478
Call-ID: OTEzYTU5YTBkYTI3YWFhYTU0OGUzNGFlZWZjYTk5M2E.
CSeq: 2 ACK
Content-Length: 0

2020/01/21 09:23:11.364247 2.2.2.2:5060 -> 1.1.1.1:1046
SIP/2.0 401 Unauthorized
Record-Route: sip:2.2.2.2;lr;ftag=32062478
Via: SIP/2.0/UDP 1.1.1.1:1046;branch=z9hG4bK-d8754z-fe048f983d100ce3-1—d8754z-
To: sip:61411111111@2.2.2.2;transport=UDP;tag=8-186F88FB-5E26284F00058E5E-C5489700
From: "61811111111"sip:61811111111@2.2.2.2;transport=UDP;tag=32062478
Call-ID: OTEzYTU5YTBkYTI3YWFhYTU0OGUzNGFlZWZjYTk5M2E.
CSeq: 2 INVITE
WWW-Authenticate: Digest realm=“sems1.s.com”, qop=“auth,auth-int”, nonce=“Fa392da870f96fc863a1290587c5fd5f3”
Server: SBC 1.8.34-5
Content-Length: 0

From LoadBalancer to SEMS

2020/01/21 09:23:11.321115 2.2.2.2:5060 -> 2.2.2.3:7000
INVITE sip:61411111111@2.2.2.2;transport=UDP SIP/2.0
Record-Route: sip:2.2.2.2;lr;ftag=32062478
Via: SIP/2.0/UDP 2.2.2.2;branch=z9hG4bKc7cd.9e96c57612b68c34e6ac9941be03fb48.0
Via: SIP/2.0/UDP 1.1.1.1:1046;branch=z9hG4bK-d8754z-18cad64f26ce0543-1—d8754z-
Max-Forwards: 69
Contact: sip:61811111111@1.1.1.1:1046;transport=UDP
To: sip:61411111111@2.2.2.2;transport=UDP
From: "61811111111"sip:61811111111@2.2.2.2;transport=UDP;tag=32062478
Call-ID: OTEzYTU5YTBkYTI3YWFhYTU0OGUzNGFlZWZjYTk5M2E.
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
Content-Type: application/sdp
Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri
User-Agent: Z 3.6.25251 r25476
Allow-Events: presence, kpml
Content-Length: 237
X-ORIG-IP: 1.1.1.1
X-ORIG-PORT: 1046
X-ORIG-PROTO: 1

v=0
o=Z 0 0 IN IP4 1.1.1.1
s=Z
c=IN IP4 1.1.1.1
t=0 0
m=audio 8000 RTP/AVP 3 110 8 0 98 101
a=rtpmap:110 speex/8000
a=rtpmap:98 iLBC/8000
a=fmtp:98 mode=20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv

2020/01/21 09:23:11.322105 2.2.2.3:7000 -> 2.2.2.2:5060
SIP/2.0 100 Connecting
Record-Route: sip:2.2.2.2;lr;ftag=32062478
Via: SIP/2.0/UDP 2.2.2.2;branch=z9hG4bKc7cd.9e96c57612b68c34e6ac9941be03fb48.0
Via: SIP/2.0/UDP 1.1.1.1:1046;branch=z9hG4bK-d8754z-18cad64f26ce0543-1—d8754z-
To: sip:61411111111@2.2.2.2;transport=UDP
From: "61811111111"sip:61811111111@2.2.2.2;transport=UDP;tag=32062478
Call-ID: OTEzYTU5YTBkYTI3YWFhYTU0OGUzNGFlZWZjYTk5M2E.
CSeq: 1 INVITE
Server: SBC 1.8.34-5
Content-Length: 0

2020/01/21 09:23:11.331859 2.2.2.3:7000 -> 2.2.2.2:5060
SIP/2.0 401 Unauthorized
Record-Route: sip:2.2.2.2;lr;ftag=32062478
Via: SIP/2.0/UDP 2.2.2.2;branch=z9hG4bKc7cd.9e96c57612b68c34e6ac9941be03fb48.0
Via: SIP/2.0/UDP 1.1.1.1:1046;branch=z9hG4bK-d8754z-18cad64f26ce0543-1—d8754z-
To: sip:61411111111@2.2.2.2;transport=UDP;tag=8-4BC525CA-5E26284F0005100F-C5489700
From: "61811111111"sip:61811111111@2.2.2.2;transport=UDP;tag=32062478
Call-ID: OTEzYTU5YTBkYTI3YWFhYTU0OGUzNGFlZWZjYTk5M2E.
CSeq: 1 INVITE
WWW-Authenticate: Digest realm=“ytrtp-sems1-syd.sipvoice.com.au”, qop=“auth,auth-int”, nonce=“Fa392da870f96fc863a1290587c5fd5f3”
Server: SBC 1.8.34-5
Content-Length: 0

2020/01/21 09:23:11.332337 2.2.2.2:5060 -> 2.2.2.3:7000
ACK sip:61411111111@2.2.2.2;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 2.2.2.2;branch=z9hG4bKc7cd.9e96c57612b68c34e6ac9941be03fb48.0
Max-Forwards: 69
To: sip:61411111111@2.2.2.2;transport=UDP;tag=8-4BC525CA-5E26284F0005100F-C5489700
From: "61811111111"sip:61811111111@2.2.2.2;transport=UDP;tag=32062478
Call-ID: OTEzYTU5YTBkYTI3YWFhYTU0OGUzNGFlZWZjYTk5M2E.
CSeq: 1 ACK
Content-Length: 0

2020/01/21 09:23:11.363492 2.2.2.2:5060 -> 2.2.2.3:7000
INVITE sip:61411111111@2.2.2.2;transport=UDP SIP/2.0
Record-Route: sip:2.2.2.2;lr;ftag=32062478
Via: SIP/2.0/UDP 2.2.2.2;branch=z9hG4bK97cd.a6298049075e61665740bfd02e633007.0
Via: SIP/2.0/UDP 1.1.1.1:1046;branch=z9hG4bK-d8754z-fe048f983d100ce3-1—d8754z-
Max-Forwards: 69
Contact: sip:61811111111@1.1.1.1:1046;transport=UDP
To: sip:61411111111@2.2.2.2;transport=UDP
From: “61811111111"sip:61811111111@2.2.2.2;transport=UDP;tag=32062478
Call-ID: OTEzYTU5YTBkYTI3YWFhYTU0OGUzNGFlZWZjYTk5M2E.
CSeq: 2 INVITE
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
Content-Type: application/sdp
Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri
User-Agent: Z 3.6.25251 r25476
Authorization: Digest username=“61811111111”,realm=“sems1.s.com”,nonce=“Fa392da870f96fc863a1290587c5fd5f3”,uri="sip:61411111111@2.2.2.2;transport=UDP”,response=“3a59a1d7793
e62e19904bf9a6de240”,cnonce=“8ff1431f884a02c11b642024665”,nc=00000001,qop=auth-int,algorithm=MD5
Allow-Events: presence, kpml
Content-Length: 237
X-ORIG-IP: 1.1.1.1
X-ORIG-PORT: 1046
X-ORIG-PROTO: 1

v=0
o=Z 0 0 IN IP4 1.1.1.1
s=Z
c=IN IP4 1.1.1.1
t=0 0
m=audio 8000 RTP/AVP 3 110 8 0 98 101
a=rtpmap:110 speex/8000
a=rtpmap:98 iLBC/8000
a=fmtp:98 mode=20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv

2020/01/21 09:23:11.363950 2.2.2.3:7000 -> 2.2.2.2:5060
SIP/2.0 100 Connecting
Record-Route: sip:2.2.2.2;lr;ftag=32062478
Via: SIP/2.0/UDP 2.2.2.2;branch=z9hG4bK97cd.a6298049075e61665740bfd02e633007.0
Via: SIP/2.0/UDP 1.1.1.1:1046;branch=z9hG4bK-d8754z-fe048f983d100ce3-1—d8754z-
To: sip:61411111111@2.2.2.2;transport=UDP
From: "61811111111"sip:61811111111@2.2.2.2;transport=UDP;tag=32062478
Call-ID: OTEzYTU5YTBkYTI3YWFhYTU0OGUzNGFlZWZjYTk5M2E.
CSeq: 2 INVITE
Server: SBC 1.8.34-5
Content-Length: 0

2020/01/21 09:23:11.364183 2.2.2.3:7000 -> 2.2.2.2:5060
SIP/2.0 401 Unauthorized
Record-Route: sip:2.2.2.2;lr;ftag=32062478
Via: SIP/2.0/UDP 2.2.2.2;branch=z9hG4bK97cd.a6298049075e61665740bfd02e633007.0
Via: SIP/2.0/UDP 1.1.1.1:1046;branch=z9hG4bK-d8754z-fe048f983d100ce3-1—d8754z-
To: sip:61411111111@2.2.2.2;transport=UDP;tag=8-186F88FB-5E26284F00058E5E-C5489700
From: "61811111111"sip:61811111111@2.2.2.2;transport=UDP;tag=32062478
Call-ID: OTEzYTU5YTBkYTI3YWFhYTU0OGUzNGFlZWZjYTk5M2E.
CSeq: 2 INVITE
WWW-Authenticate: Digest realm=“sems1.s.com”, qop=“auth,auth-int”, nonce=“Fa392da870f96fc863a1290587c5fd5f3”
Server: SBC 1.8.34-5
Content-Length: 0

2020/01/21 09:23:11.364672 2.2.2.2:5060 -> 2.2.2.3:7000
ACK sip:61411111111@2.2.2.2;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 2.2.2.2;branch=z9hG4bK97cd.a6298049075e61665740bfd02e633007.0
Max-Forwards: 69
To: sip:61411111111@2.2.2.2;transport=UDP;tag=8-186F88FB-5E26284F00058E5E-C5489700
From: "61811111111"sip:61811111111@2.2.2.2;transport=UDP;tag=32062478
Call-ID: OTEzYTU5YTBkYTI3YWFhYTU0OGUzNGFlZWZjYTk5M2E.
CSeq: 2 ACK
Content-Length: 0

7

yeti-cli:8> yeti.show.auth.credentials.all

| id | pwd | user |

| 38 | 618XXXXXXXXa | 618XXXXXXXX |

1 record. Took 0.0011 seconds
yeti-cli:8>