Failed to authenticate device message

Hi all,

I keep on getting this message:

My sip.conf file looks like this

[code][general]
allowguest=no
udpbindaddr=0.0.0.0
port=5060
qualify=yes
srvlookup=yes
canreinvite=no
disallow=all
allow=g726
allow=gsm
allow=alaw
allow=ulaw

[mijo]
type=friend
callerid=“User Mijo” <101>
secret=test_pass_mijo
nat=yes
host=dynamic
context=testing

[test]
type=friend
callerid=“Test User” <102>
secret=test_pass_test
nat=yes
host=dynamic
context=testing[/code]

My extensions.conf file looks like this:

[code][general]
autofallthrough=yes
writeprotect=no

[global]

[testing]
exten => 101,1,Dial(SIP/mijo)
exten => 102,1,Dial(SIP/test)
exten => 103,1,Dial(hello-world)
[/code]

SIP debug log

[code]<— SIP read from UDP:192.168.5.79:46450 —>
INVITE sip:103@192.168.5.87;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 192.168.5.79:46450;branch=z9hG4bK-524287-1—e6bf0f29fc7f921c;rport
Max-Forwards: 70
Contact: sip:mijo@192.168.5.79:46450;transport=UDP
To: sip:103@192.168.5.87;transport=UDP
From: sip:mijo@192.168.5.87;transport=UDP;tag=ec42124b
Call-ID: bYk_wl87KR1-Bonmg1w0wQ…
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
Content-Type: application/sdp
Supported: replaces, norefersub, extended-refer, timer, outbound, path, X-cisco-serviceuri
User-Agent: Zoiper r30798
Allow-Events: presence, kpml
Content-Length: 241

v=0
o=Zoiper 0 0 IN IP4 192.168.5.79
s=Zoiper
c=IN IP4 192.168.5.79
t=0 0
m=audio 33190 RTP/AVP 3 0 8 101
a=rtpmap:3 GSM/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=sendrecv
<------------->
— (14 headers 12 lines) —
Sending to 192.168.5.79:46450 (no NAT)
Sending to 192.168.5.79:46450 (no NAT)
Using INVITE request as basis request - bYk_wl87KR1-Bonmg1w0wQ…
Found peer ‘mijo’ for ‘mijo’ from 192.168.5.79:46450

<— Reliably Transmitting (NAT) to 192.168.5.79:46450 —>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.5.79:46450;branch=z9hG4bK-524287-1—e6bf0f29fc7f921c;received=192.168.5.79;rport=46450
From: sip:mijo@192.168.5.87;transport=UDP;tag=ec42124b
To: sip:103@192.168.5.87;transport=UDP;tag=as1326a623
Call-ID: bYk_wl87KR1-Bonmg1w0wQ…
CSeq: 1 INVITE
Server: Asterisk PBX 13.4.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm=“asterisk”, nonce="596d9e32"
Content-Length: 0

<------------>
Scheduling destruction of SIP dialog ‘bYk_wl87KR1-Bonmg1w0wQ…’ in 6400 ms (Method: INVITE)

<— SIP read from UDP:192.168.5.79:46450 —>
ACK sip:103@192.168.5.87;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 192.168.5.79:46450;branch=z9hG4bK-524287-1—e6bf0f29fc7f921c;rport
Max-Forwards: 70
To: sip:103@192.168.5.87;transport=UDP;tag=as1326a623
From: sip:mijo@192.168.5.87;transport=UDP;tag=ec42124b
Call-ID: bYk_wl87KR1-Bonmg1w0wQ…
CSeq: 1 ACK
Content-Length: 0

<------------->
— (8 headers 0 lines) —

<— SIP read from UDP:192.168.5.79:46450 —>
INVITE sip:103@192.168.5.87;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 192.168.5.79:46450;branch=z9hG4bK-524287-1—9fc7271c65ca5c5d;rport
Max-Forwards: 70
Contact: sip:mijo@192.168.5.79:46450;transport=UDP
To: sip:103@192.168.5.87;transport=UDP
From: sip:mijo@192.168.5.87;transport=UDP;tag=ec42124b
Call-ID: bYk_wl87KR1-Bonmg1w0wQ…
CSeq: 2 INVITE
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
Content-Type: application/sdp
Supported: replaces, norefersub, extended-refer, timer, outbound, path, X-cisco-serviceuri
User-Agent: Zoiper r30798
Authorization: Digest username=“mijo”,realm=“asterisk”,nonce=“596d9e32”,uri="sip:103@192.168.5.87;transport=UDP",response=“1265c877bed5d7b3cf98ce882fb697a3”,algorithm=MD5
Allow-Events: presence, kpml
Content-Length: 241

v=0
o=Zoiper 0 0 IN IP4 192.168.5.79
s=Zoiper
c=IN IP4 192.168.5.79
t=0 0
m=audio 33190 RTP/AVP 3 0 8 101
a=rtpmap:3 GSM/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=sendrecv
<------------->
— (15 headers 12 lines) —
Sending to 192.168.5.79:46450 (NAT)
Using INVITE request as basis request - bYk_wl87KR1-Bonmg1w0wQ…
Found peer ‘mijo’ for ‘mijo’ from 192.168.5.79:46450
[Jun 16 22:14:08] NOTICE[12509][C-00000001]: chan_sip.c:25526 handle_request_invite: Failed to authenticate device sip:mijo@192.168.5.87;transport=UDP;tag=ec42124b

<— Reliably Transmitting (NAT) to 192.168.5.79:46450 —>
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 192.168.5.79:46450;branch=z9hG4bK-524287-1—9fc7271c65ca5c5d;received=192.168.5.79;rport=46450
From: sip:mijo@192.168.5.87;transport=UDP;tag=ec42124b
To: sip:103@192.168.5.87;transport=UDP;tag=as1326a623
Call-ID: bYk_wl87KR1-Bonmg1w0wQ…
CSeq: 2 INVITE
Server: Asterisk PBX 13.4.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0

<------------>
Scheduling destruction of SIP dialog ‘bYk_wl87KR1-Bonmg1w0wQ…’ in 6400 ms (Method: INVITE)

<— SIP read from UDP:192.168.5.79:46450 —>
ACK sip:103@192.168.5.87;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 192.168.5.79:46450;branch=z9hG4bK-524287-1—9fc7271c65ca5c5d;rport
Max-Forwards: 70
To: sip:103@192.168.5.87;transport=UDP;tag=as1326a623
From: sip:mijo@192.168.5.87;transport=UDP;tag=ec42124b
Call-ID: bYk_wl87KR1-Bonmg1w0wQ…
CSeq: 2 ACK
Content-Length: 0

<------------->
— (8 headers 0 lines) —

<— SIP read from UDP:192.168.122.1:5060 —>
PUBLISH sip:test@192.168.122.136 SIP/2.0
CSeq: 245 PUBLISH
Via: SIP/2.0/UDP 192.168.122.1:5060;branch=z9hG4bK385288ea-d112-e511-81c1-605718bb7295;rport
User-Agent: Ekiga/4.0.1
From: sip:test@192.168.122.136
Call-ID: 68c7cba6-c812-e511-81c1-605718bb7295@Mijo
To: sip:test@192.168.122.136
Expires: 300
Event: presence
Content-Length: 492
Content-Type: application/pidf+xml
Max-Forwards: 70

<?xml version="1.0" encoding="UTF-8"?>

open sip:test@192.168.122.136 I’m available using Ekiga 2015-06-16T21:40:26+02:00

<------------->
— (12 headers 3 lines) —

<— SIP read from UDP:192.168.5.87:5060 —>
PUBLISH sip:test@192.168.122.136 SIP/2.0
CSeq: 245 PUBLISH
Via: SIP/2.0/UDP 192.168.5.87:5060;branch=z9hG4bK6e6788ea-d112-e511-81c1-605718bb7295;rport
User-Agent: Ekiga/4.0.1
From: sip:test@192.168.122.136
Call-ID: 68c7cba6-c812-e511-81c1-605718bb7295@Mijo
To: sip:test@192.168.122.136
Expires: 300
Event: presence
Content-Length: 492
Content-Type: application/pidf+xml
Max-Forwards: 70

<?xml version="1.0" encoding="UTF-8"?>

open sip:test@192.168.122.136 I’m available using Ekiga 2015-06-16T21:40:26+02:00

<------------->
— (12 headers 3 lines) —

<— SIP read from UDP:192.168.122.1:5060 —>
PUBLISH sip:test@192.168.122.136 SIP/2.0
CSeq: 245 PUBLISH
Via: SIP/2.0/UDP 192.168.122.1:5060;branch=z9hG4bK385288ea-d112-e511-81c1-605718bb7295;rport
User-Agent: Ekiga/4.0.1
From: sip:test@192.168.122.136
Call-ID: 68c7cba6-c812-e511-81c1-605718bb7295@Mijo
To: sip:test@192.168.122.136
Expires: 300
Event: presence
Content-Length: 492
Content-Type: application/pidf+xml
Max-Forwards: 70

<?xml version="1.0" encoding="UTF-8"?>

open sip:test@192.168.122.136 I’m available using Ekiga 2015-06-16T21:40:26+02:00

<------------->
— (12 headers 3 lines) —

<— SIP read from UDP:192.168.5.87:5060 —>
PUBLISH sip:test@192.168.122.136 SIP/2.0
CSeq: 245 PUBLISH
Via: SIP/2.0/UDP 192.168.5.87:5060;branch=z9hG4bK6e6788ea-d112-e511-81c1-605718bb7295;rport
User-Agent: Ekiga/4.0.1
From: sip:test@192.168.122.136
Call-ID: 68c7cba6-c812-e511-81c1-605718bb7295@Mijo
To: sip:test@192.168.122.136
Expires: 300
Event: presence
Content-Length: 492
Content-Type: application/pidf+xml
Max-Forwards: 70

<?xml version="1.0" encoding="UTF-8"?>

open sip:test@192.168.122.136 I’m available using Ekiga 2015-06-16T21:40:26+02:00

<------------->
— (12 headers 3 lines) —

<— SIP read from UDP:192.168.122.1:5060 —>
PUBLISH sip:test@192.168.122.136 SIP/2.0
CSeq: 245 PUBLISH
Via: SIP/2.0/UDP 192.168.122.1:5060;branch=z9hG4bK385288ea-d112-e511-81c1-605718bb7295;rport
User-Agent: Ekiga/4.0.1
From: sip:test@192.168.122.136
Call-ID: 68c7cba6-c812-e511-81c1-605718bb7295@Mijo
To: sip:test@192.168.122.136
Expires: 300
Event: presence
Content-Length: 492
Content-Type: application/pidf+xml
Max-Forwards: 70

<?xml version="1.0" encoding="UTF-8"?>

open sip:test@192.168.122.136 I’m available using Ekiga 2015-06-16T21:40:26+02:00

<------------->
— (12 headers 3 lines) —

<— SIP read from UDP:192.168.5.87:5060 —>
PUBLISH sip:test@192.168.122.136 SIP/2.0
CSeq: 245 PUBLISH
Via: SIP/2.0/UDP 192.168.5.87:5060;branch=z9hG4bK6e6788ea-d112-e511-81c1-605718bb7295;rport
User-Agent: Ekiga/4.0.1
From: sip:test@192.168.122.136
Call-ID: 68c7cba6-c812-e511-81c1-605718bb7295@Mijo
To: sip:test@192.168.122.136
Expires: 300
Event: presence
Content-Length: 492
Content-Type: application/pidf+xml
Max-Forwards: 70

<?xml version="1.0" encoding="UTF-8"?>

open sip:test@192.168.122.136 I’m available using Ekiga 2015-06-16T21:40:26+02:00

<------------->
— (12 headers 3 lines) —

<— SIP read from UDP:192.168.122.1:5060 —>
PUBLISH sip:test@192.168.122.136 SIP/2.0
CSeq: 245 PUBLISH
Via: SIP/2.0/UDP 192.168.122.1:5060;branch=z9hG4bK385288ea-d112-e511-81c1-605718bb7295;rport
User-Agent: Ekiga/4.0.1
From: sip:test@192.168.122.136
Call-ID: 68c7cba6-c812-e511-81c1-605718bb7295@Mijo
To: sip:test@192.168.122.136
Expires: 300
Event: presence
Content-Length: 492
Content-Type: application/pidf+xml
Max-Forwards: 70

<?xml version="1.0" encoding="UTF-8"?>

open sip:test@192.168.122.136 I’m available using Ekiga 2015-06-16T21:40:26+02:00

<------------->
— (12 headers 3 lines) —

<— SIP read from UDP:192.168.5.87:5060 —>
PUBLISH sip:test@192.168.122.136 SIP/2.0
CSeq: 245 PUBLISH
Via: SIP/2.0/UDP 192.168.5.87:5060;branch=z9hG4bK6e6788ea-d112-e511-81c1-605718bb7295;rport
User-Agent: Ekiga/4.0.1
From: sip:test@192.168.122.136
Call-ID: 68c7cba6-c812-e511-81c1-605718bb7295@Mijo
To: sip:test@192.168.122.136
Expires: 300
Event: presence
Content-Length: 492
Content-Type: application/pidf+xml
Max-Forwards: 70

<?xml version="1.0" encoding="UTF-8"?>

open sip:test@192.168.122.136 I’m available using Ekiga 2015-06-16T21:40:26+02:00

<------------->
— (12 headers 3 lines) —
Really destroying SIP dialog ‘bYk_wl87KR1-Bonmg1w0wQ…’ Method: ACK[/code]

Yesterday when I have initially setup Asterisk everything worked fine, but today I keep on getting those authentication failure messages.

I’m running Asterisk in a KVM machine if it matters.

Thank you for your time,
Best regards.

The password doesn’t match the user name.