Re: [Freeswitch-users] [ERR] sofia_reg.c:2110 "some gateway" Registration Failed with status Unauthorized [401]. failure #37 (Snabel Kaabiya)
Hi, I've googled about this parameter "stale=true" and looked again at the SIP trace. I've noticed that in the problematic servers this header: Authorization: Digest username="username", realm="sip.de.didlogic.net", nonce="U0DtvVNA7JFDwqn/iKN2y0i7jjJF/xDpK+45ZYA=", cnonce="tZUwATUmEjKDKHBU0sVf8A", algorithm=MD5, uri="sip:sip.de.didlogic.net;transport=udp", response="8aaadef8769d2234def69a699c53f95c", qop=auth, nc=0000018e is sent in the first REGISTER request, could this cause the issue? any ideas? Thanks, Snabel On Mon, Apr 7, 2014 at 5:36 PM, Snabel Kabiya <snabel@lexifone.com> wrote:
Hi,
can you please elaborate on that? what do you mean by: "stale=true"? what's the meaning of this header? also as you can see on the server with old freeswitch version where we don't have this issue, we don't have this header in the response. is this header requested in the freeswitch upgraded version?
where should this header be added? can you please change the SIP trace for the problematic server bellow? so i can see what a valid flow should look like?
Thanks, Snabel
---------- Forwarded message ---------- From: Brian West <brian@freeswitch.org> To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org> Cc: Date: Mon, 7 Apr 2014 08:12:38 -0500 Subject: Re: [Freeswitch-users] [ERR] sofia_reg.c:2110 "some gateway" Registration Failed with status Unauthorized [401]. failure #37 (Snabel Kaabiya) Your provider is broken, They should be sending a stale=true and they aren't, Since they aren't resetting the nonce count with stale=true in the challenge we come back thinking our current nonce count of 18f is fine.
-- Brian West brian@freeswitch.org FreeSWITCH Solutions, LLC PO BOX 2531 Brookfield, WI 53008-2531 Twitter: @FreeSWITCH , @briankwest http://www.freeswitchbook.com http://www.freeswitchcookbook.com
T: +1.918.420.9001 | F: +1.918.420.9002 | M: +1.918.424.WEST iNUM: +883 5100 1420 9001 ISN: 410*543 Skype:briankwest PGP Key: http://www.bkw.org/key.txt (AB93356707C76CED)
On Apr 7, 2014, at 1:55 AM, Snabel Kabiya <snabel@lexifone.com> wrote:
Hi,
Are they using the same account? That could conceivable cause issues, you'd need to check with DIDLogic if they support that. [SNABEL] yes it's the same account.
Since you have a working and non-working servers you could compare the requests to see what differs between them. [SNABEL] i did that, you can see inline both requests. the only difference i saw, is this header: Supported: precondition, path, replaces highlighted in the requests:
/**************************************************************************************************************
Working server
***************************************************************************************************************/
2014-04-06 18:00:20.896614 [NOTICE] sofia_reg.c:418 Registering DIDLogic send 618 bytes to udp/[46.165.252.40]:5060 at 15:00:20.898875:
------------------------------------------------------------------------
REGISTER sip:sip.de.didlogic.net;transport=udp SIP/2.0 Via: SIP/2.0/UDP 5.9.23.171:5080;rport;branch=z9hG4bKXrH2QjNrt081K Max-Forwards: 70 From: <sip:95299@sip.de.didlogic.net>;tag=4eaeaXtSSUc3a To: <sip:95299@sip.de.didlogic.net> Call-ID: 2c4ba5f8-bd9c-11e3-8545-0d578f78ffdf CSeq: 58062146 REGISTER Contact: <sip:gw+DIDLogic@5.9.23.171:5080;transport=udp;gw=DIDLogic> Expires: 3600 User-Agent: FreeSWITCH-mod_sofia/1.2.12+git~20130806T202138Z~22ab34c507 Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY Supported: precondition, path, replaces Content-Length: 0
------------------------------------------------------------------------
recv 444 bytes from udp/[46.165.252.40]:5060 at 15:00:20.912841:
------------------------------------------------------------------------
SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 5.9.23.171:5080 ;rport=5080;branch=z9hG4bKXrH2QjNrt081K From: <sip:95299@sip.de.didlogic.net>;tag=4eaeaXtSSUc3a To: <sip:95299@sip.de.didlogic.net ;tag=b27e1a1d33761e85846fc98f5f3a7e58.c173 Call-ID: 2c4ba5f8-bd9c-11e3-8545-0d578f78ffdf CSeq: 58062146 REGISTER WWW-Authenticate: Digest realm="sip.de.didlogic.net", nonce=" U0FtMFNBbARsF99U0eRscR/9s7cQ6Y2ULDJAKIA=", qop="auth" Content-Length: 0
------------------------------------------------------------------------
send 898 bytes to udp/[46.165.252.40]:5060 at 15:00:20.913382:
------------------------------------------------------------------------
REGISTER sip:sip.de.didlogic.net;transport=udp SIP/2.0 Via: SIP/2.0/UDP 5.9.23.171:5080;rport;branch=z9hG4bKy1aUSD6UQ9ymF Max-Forwards: 70 From: <sip:95299@sip.de.didlogic.net>;tag=4eaeaXtSSUc3a To: <sip:95299@sip.de.didlogic.net> Call-ID: 2c4ba5f8-bd9c-11e3-8545-0d578f78ffdf CSeq: 58062147 REGISTER Contact: <sip:gw+DIDLogic@5.9.23.171:5080;transport=udp;gw=DIDLogic> Expires: 3600 User-Agent: FreeSWITCH-mod_sofia/1.2.12+git~20130806T202138Z~22ab34c507 Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY Supported: precondition, path, replaces Authorization: Digest username="username", realm=" sip.de.didlogic.net", nonce="U0FtMFNBbARsF99U0eRscR/9s7cQ6Y2ULDJAKIA=", cnonce="A8sptzg/EjKkSwAejPT25g", algorithm=MD5, uri="sip: sip.de.didlogic.net;transport=udp", response="42c896b44b2ed46127099aa90adf5c01", qop=auth, nc=00000001 Content-Length: 0
------------------------------------------------------------------------
recv 780 bytes from udp/[46.165.252.40]:5060 at 15:00:20.927553:
------------------------------------------------------------------------
SIP/2.0 200 OK Via: SIP/2.0/UDP 5.9.23.171:5080 ;rport=5080;branch=z9hG4bKy1aUSD6UQ9ymF From: <sip:95299@sip.de.didlogic.net>;tag=4eaeaXtSSUc3a To: <sip:95299@sip.de.didlogic.net ;tag=b27e1a1d33761e85846fc98f5f3a7e58.dbc6 Call-ID: 2c4ba5f8-bd9c-11e3-8545-0d578f78ffdf CSeq: 58062147 REGISTER Contact: <sip:gw+DIDLogic@5.9.23.171:5080;transport=udp;gw=DIDLogic>;expires=3600, <sip:gw+DIDLogic@144.76.109.73:5080;transport=udp;gw=DIDLogic>;expires=3150, <sip:gw+DIDLogic@144.76.98.11:5080;transport=udp;gw=DIDLogic>;expires=3010, <sip:gw+DIDLogic@5.9.201.120:5080;transport=udp;gw=DIDLogic>;expires=2869, <sip:gw+DIDLogic@144.76.98.12:5080;transport=udp;gw=DIDLogic>;expires=1281, <sip:gw+DIDLogic@5.9.201.121:5080;transport=udp;gw=DIDLogic>;expires=2545 Content-Length: 0
/**************************************************************************************************************
problematic server
***************************************************************************************************************/
2014-04-06 09:32:05.472850 [NOTICE] sofia_reg.c:423 Registering DIDLogic send 894 bytes to udp/[46.165.252.40]:5060 at 06:32:05.492557:
------------------------------------------------------------------------
REGISTER sip:sip.de.didlogic.net;transport=udp SIP/2.0 Via: SIP/2.0/UDP 144.76.98.11:5080;rport;branch=z9hG4bKUZ0p2Fjget1KN Max-Forwards: 70 From: <sip:95299@sip.de.didlogic.net>;tag=XK0KSD17jemDN To: <sip:95299@sip.de.didlogic.net> Call-ID: de332712-ba83-11e3-b33f-0dc96adc5bb0 CSeq: 57892398 REGISTER Contact: <sip:gw+DIDLogic@144.76.98.11:5080 ;transport=udp;gw=DIDLogic> Expires: 3600 User-Agent: FreeSWITCH-mod_sofia/1.2.23+git~20140317T213443Z~769a03a629~64bit Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY Supported: path, replaces Authorization: Digest username="username", realm=" sip.de.didlogic.net", nonce="U0DtvVNA7JFDwqn/iKN2y0i7jjJF/xDpK+45ZYA=", cnonce="tZUwATUmEjKDKHBU0sVf8A", algorithm=MD5, uri="sip: sip.de.didlogic.net;transport=udp", response="8aaadef8769d2234def69a699c53f95c", qop=auth, nc=0000018e Content-Length: 0
------------------------------------------------------------------------
recv 446 bytes from udp/[46.165.252.40]:5060 at 06:32:05.520506:
------------------------------------------------------------------------
SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 144.76.98.11:5080 ;rport=5080;branch=z9hG4bKUZ0p2Fjget1KN From: <sip:95299@sip.de.didlogic.net>;tag=XK0KSD17jemDN To: <sip:95299@sip.de.didlogic.net ;tag=b27e1a1d33761e85846fc98f5f3a7e58.437e Call-ID: de332712-ba83-11e3-b33f-0dc96adc5bb0 CSeq: 57892398 REGISTER WWW-Authenticate: Digest realm="sip.de.didlogic.net", nonce=" U0D2EVNA9OVIqS6bUrch5649kHnuK6PXK/Fii4A=", qop="auth" Content-Length: 0
------------------------------------------------------------------------
send 894 bytes to udp/[46.165.252.40]:5060 at 06:32:05.520845:
------------------------------------------------------------------------
REGISTER sip:sip.de.didlogic.net;transport=udp SIP/2.0 Via: SIP/2.0/UDP 144.76.98.11:5080;rport;branch=z9hG4bKv8SF4a3KB3Q6g Max-Forwards: 70 From: <sip:95299@sip.de.didlogic.net>;tag=XK0KSD17jemDN To: <sip:95299@sip.de.didlogic.net> Call-ID: de332712-ba83-11e3-b33f-0dc96adc5bb0 CSeq: 57892399 REGISTER Contact: <sip:gw+DIDLogic@144.76.98.11:5080 ;transport=udp;gw=DIDLogic> Expires: 3600 User-Agent: FreeSWITCH-mod_sofia/1.2.23+git~20140317T213443Z~769a03a629~64bit Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY Supported: path, replaces Authorization: Digest username="username", realm=" sip.de.didlogic.net", nonce="U0D2EVNA9OVIqS6bUrch5649kHnuK6PXK/Fii4A=", cnonce="tZUwATUmEjKDKHBU0sVf8A", algorithm=MD5, uri="sip: sip.de.didlogic.net;transport=udp", response="3dc99375cf925ad9af145899dcf83b1a", qop=auth, nc=0000018f Content-Length: 0
------------------------------------------------------------------------
recv 446 bytes from udp/[46.165.252.40]:5060 at 06:32:05.536657:
------------------------------------------------------------------------
SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 144.76.98.11:5080 ;rport=5080;branch=z9hG4bKv8SF4a3KB3Q6g From: <sip:95299@sip.de.didlogic.net>;tag=XK0KSD17jemDN To: <sip:95299@sip.de.didlogic.net ;tag=b27e1a1d33761e85846fc98f5f3a7e58.b648 Call-ID: de332712-ba83-11e3-b33f-0dc96adc5bb0 CSeq: 57892399 REGISTER WWW-Authenticate: Digest realm="sip.de.didlogic.net", nonce=" U0D2EVNA9OUTYGscaPkV4MvAB1IDDtpQK/FjjIA=", qop="auth" Content-Length: 0
------------------------------------------------------------------------
2014-04-06 09:32:05.532842 [ERR] sofia_reg.c:2110 DIDLogic Registration Failed with status Unauthorized [401]. failure #72 2014-04-06 09:32:06.472844 [WARNING] sofia_reg.c:478 DIDLogic Failed Registration [904], setting retry to 2160 seconds.
On Sun, Apr 6, 2014 at 10:27 PM, < freeswitch-users-request@lists.freeswitch.org> wrote: Send FreeSWITCH-users mailing list submissions to freeswitch-users@lists.freeswitch.org
To subscribe or unsubscribe via the World Wide Web, visit http://lists.freeswitch.org/mailman/listinfo/freeswitch-users or, via email, send a message with subject or body 'help' to freeswitch-users-request@lists.freeswitch.org
You can reach the person managing the list at freeswitch-users-owner@lists.freeswitch.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of FreeSWITCH-users digest..."
Today's Topics:
1. Re: [ERR] sofia_reg.c:2110 "some gateway" Registration Failed with status Unauthorized [401]. failure #37 (Snabel Kaabiya) (Snabel Kabiya) 2. Re: [ERR] sofia_reg.c:2110 "some gateway" Registration Failed with status Unauthorized [401]. failure #37 (Snabel Kaabiya) (Steven Ayre)
---------- Forwarded message ---------- From: Snabel Kabiya <snabel@lexifone.com> To: freeswitch-users@lists.freeswitch.org Cc: Date: Sun, 6 Apr 2014 17:29:43 +0300 Subject: Re: [Freeswitch-users] [ERR] sofia_reg.c:2110 "some gateway" Registration Failed with status Unauthorized [401]. failure #37 (Snabel Kaabiya) Hi,
please see my answers inline:
Thanks, Snabel
---------- Forwarded message ---------- From: Steven Ayre <steveayre@gmail.com> To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org> Cc: Date: Sun, 6 Apr 2014 09:59:43 -0400 Subject: Re: [Freeswitch-users] [ERR] sofia_reg.c:2110 "some gateway" Registration Failed with status Unauthorized [401]. failure #37 (Snabel Kaabiya) According to https://wiki.freeswitch.org/wiki/Provider_Configuration:_DIDLogicnothing particularly special is required. What you have should work.
Does this gateway ever register successfully - does it register fine then start getting the 401 later, or does it never register at all. If the latter perhaps the username/password is incorrect? If it works at first then starts to fail then it might be an error at DIDLogic's end and I suggest you contact them to find out what is causing the 401. [SNABEL] the gateway registers fine then start getting the 401 later, it works at first then starts to fail. i'm not sure it's an error at DIDLogic's end. because we have another server with freeswitch verion: FreeSWITCH Version 1.2.12+git~20130806T202138Z~22ab34c507 (git 22ab34c 2013-08-06 20:21:38Z) which works fine, we don't get this error there...
Also any modifications to the gateway (eg changing password) take more than reloadxml to take effect. You need to run 'sofia profile <profilename> killgw <gateway>', wait for the gateway to be removed (gives a log message or check via 'sofia status gateway') then 'sofia profile <name> rescan' to add the gateway with the new settings. Or restart FreeSWITCH. [SNABEL] i did restarted freeswitch.
By the way sip_cid_type is a variable not a parameter. See http://wiki.freeswitch.org/wiki/Sofia_Configuration_Files#Variables - but unknown parameters are ignored so it should make no difference to registration; ping, ping-max and caller-id-in-from should also have no effect on registration. [SNABEL] i see, so i could just remove them...
-Steve
On 6 April 2014 03:37, Snabel Kabiya <snabel@lexifone.com> wrote: Hi All,
I'm still getting this error:
[ERR] sofia_reg.c:2110 DIDLogic Registration Failed with status Unauthorized [401]. failure #72
I've looked at SIP trace and freeswitch logs but i can't figure out what's causing the registration failure.
here is more info on the issue, i would really appreciate your help guys.
Server: Linux Ubuntu-1204-precise-64-minimal 3.5.0-34-generic #55~precise1-Ubuntu SMP Fri Jun 7 16:25:50 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
freeswitch version: FreeSWITCH Version 1.2.23+git~20140317T213443Z~769a03a629~64bit (git 769a03a 2014-03-17 21:34:43Z 64bit)
Gateway configuration: <gateway name="DIDLogic"> <param name="username" value="username"/> <param name="realm" value="sip.de.didlogic.net"/> <param name="password" value="password"/> <param name="register" value="true"/> <param name="context" value="public"/> <param name="caller-id-in-from" value="true"/> <param name="sip_cid_type" value="none"/> <param name="ping" value="30"/> <param name="ping-max" value="3"/> </gateway>
SIP trace:
2014-04-06 09:32:05.472850 [NOTICE] sofia_reg.c:423 Registering DIDLogic send 894 bytes to udp/[46.165.252.40]:5060 at 06:32:05.492557:
------------------------------------------------------------------------
REGISTER sip:sip.de.didlogic.net;transport=udp SIP/2.0 Via: SIP/2.0/UDP 144.76.98.11:5080;rport;branch=z9hG4bKUZ0p2Fjget1KN Max-Forwards: 70 From: <sip:95299@sip.de.didlogic.net>;tag=XK0KSD17jemDN To: <sip:95299@sip.de.didlogic.net> Call-ID: de332712-ba83-11e3-b33f-0dc96adc5bb0 CSeq: 57892398 REGISTER Contact: <sip:gw+DIDLogic@144.76.98.11:5080 ;transport=udp;gw=DIDLogic> Expires: 3600 User-Agent: FreeSWITCH-mod_sofia/1.2.23+git~20140317T213443Z~769a03a629~64bit Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY Supported: path, replaces Authorization: Digest username="username", realm=" sip.de.didlogic.net", nonce="U0DtvVNA7JFDwqn/iKN2y0i7jjJF/xDpK+45ZYA=", cnonce="tZUwATUmEjKDKHBU0sVf8A", algorithm=MD5, uri="sip: sip.de.didlogic.net;transport=udp", response="8aaadef8769d2234def69a699c53f95c", qop=auth, nc=0000018e Content-Length: 0
------------------------------------------------------------------------
recv 446 bytes from udp/[46.165.252.40]:5060 at 06:32:05.520506:
------------------------------------------------------------------------
SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 144.76.98.11:5080 ;rport=5080;branch=z9hG4bKUZ0p2Fjget1KN From: <sip:95299@sip.de.didlogic.net>;tag=XK0KSD17jemDN To: <sip:95299@sip.de.didlogic.net ;tag=b27e1a1d33761e85846fc98f5f3a7e58.437e Call-ID: de332712-ba83-11e3-b33f-0dc96adc5bb0 CSeq: 57892398 REGISTER WWW-Authenticate: Digest realm="sip.de.didlogic.net", nonce="U0D2EVNA9OVIqS6bUrch5649kHnuK6PXK/Fii4A=", qop="auth" Content-Length: 0
------------------------------------------------------------------------
send 894 bytes to udp/[46.165.252.40]:5060 at 06:32:05.520845:
------------------------------------------------------------------------
REGISTER sip:sip.de.didlogic.net;transport=udp SIP/2.0 Via: SIP/2.0/UDP 144.76.98.11:5080;rport;branch=z9hG4bKv8SF4a3KB3Q6g Max-Forwards: 70 From: <sip:95299@sip.de.didlogic.net>;tag=XK0KSD17jemDN To: <sip:95299@sip.de.didlogic.net> Call-ID: de332712-ba83-11e3-b33f-0dc96adc5bb0 CSeq: 57892399 REGISTER Contact: <sip:gw+DIDLogic@144.76.98.11:5080 ;transport=udp;gw=DIDLogic> Expires: 3600 User-Agent: FreeSWITCH-mod_sofia/1.2.23+git~20140317T213443Z~769a03a629~64bit Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY Supported: path, replaces Authorization: Digest username="username", realm=" sip.de.didlogic.net", nonce="U0D2EVNA9OVIqS6bUrch5649kHnuK6PXK/Fii4A=", cnonce="tZUwATUmEjKDKHBU0sVf8A", algorithm=MD5, uri="sip: sip.de.didlogic.net;transport=udp", response="3dc99375cf925ad9af145899dcf83b1a", qop=auth, nc=0000018f Content-Length: 0
------------------------------------------------------------------------
recv 446 bytes from udp/[46.165.252.40]:5060 at 06:32:05.536657:
------------------------------------------------------------------------
SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 144.76.98.11:5080 ;rport=5080;branch=z9hG4bKv8SF4a3KB3Q6g From: <sip:95299@sip.de.didlogic.net>;tag=XK0KSD17jemDN To: <sip:95299@sip.de.didlogic.net ;tag=b27e1a1d33761e85846fc98f5f3a7e58.b648 Call-ID: de332712-ba83-11e3-b33f-0dc96adc5bb0 CSeq: 57892399 REGISTER WWW-Authenticate: Digest realm="sip.de.didlogic.net", nonce="U0D2EVNA9OUTYGscaPkV4MvAB1IDDtpQK/FjjIA=", qop="auth" Content-Length: 0
------------------------------------------------------------------------
2014-04-06 09:32:05.532842 [ERR] sofia_reg.c:2110 DIDLogic Registration Failed with status Unauthorized [401]. failure #72 2014-04-06 09:32:06.472844 [WARNING] sofia_reg.c:478 DIDLogic Failed Registration [904], setting retry to 2160 seconds.
---------- Forwarded message ---------- From: Steven Ayre <steveayre@gmail.com> To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org> Cc: Date: Sun, 6 Apr 2014 15:26:28 -0400 Subject: Re: [Freeswitch-users] [ERR] sofia_reg.c:2110 "some gateway" Registration Failed with status Unauthorized [401]. failure #37 (Snabel Kaabiya) i'm not sure it's an error at DIDLogic's end. because we have another server with freeswitch verion: FreeSWITCH Version 1.2.12+git~20130806T202138Z~22ab34c507 (git 22ab34c 2013-08-06 20:21:38Z) which works fine, we don't get this error there...
Are they using the same account? That could conceivable cause issues, you'd need to check with DIDLogic if they support that.
Since you have a working and non-working servers you could compare the requests to see what differs between them.
-Steve
On 6 April 2014 10:29, Snabel Kabiya <snabel@lexifone.com> wrote: Hi,
please see my answers inline:
Thanks, Snabel
---------- Forwarded message ---------- From: Steven Ayre <steveayre@gmail.com> To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org> Cc: Date: Sun, 6 Apr 2014 09:59:43 -0400 Subject: Re: [Freeswitch-users] [ERR] sofia_reg.c:2110 "some gateway" Registration Failed with status Unauthorized [401]. failure #37 (Snabel Kaabiya) According to https://wiki.freeswitch.org/wiki/Provider_Configuration:_DIDLogicnothing particularly special is required. What you have should work.
Does this gateway ever register successfully - does it register fine then start getting the 401 later, or does it never register at all. If the latter perhaps the username/password is incorrect? If it works at first then starts to fail then it might be an error at DIDLogic's end and I suggest you contact them to find out what is causing the 401. [SNABEL] the gateway registers fine then start getting the 401 later, it works at first then starts to fail. i'm not sure it's an error at DIDLogic's end. because we have another server with freeswitch verion: FreeSWITCH Version 1.2.12+git~20130806T202138Z~22ab34c507 (git 22ab34c 2013-08-06 20:21:38Z) which works fine, we don't get this error there...
Also any modifications to the gateway (eg changing password) take more than reloadxml to take effect. You need to run 'sofia profile <profilename> killgw <gateway>', wait for the gateway to be removed (gives a log message or check via 'sofia status gateway') then 'sofia profile <name> rescan' to add the gateway with the new settings. Or restart FreeSWITCH. [SNABEL] i did restarted freeswitch.
By the way sip_cid_type is a variable not a parameter. See http://wiki.freeswitch.org/wiki/Sofia_Configuration_Files#Variables - but unknown parameters are ignored so it should make no difference to registration; ping, ping-max and caller-id-in-from should also have no effect on registration. [SNABEL] i see, so i could just remove them...
-Steve
On 6 April 2014 03:37, Snabel Kabiya <snabel@lexifone.com> wrote: Hi All,
I'm still getting this error:
[ERR] sofia_reg.c:2110 DIDLogic Registration Failed with status Unauthorized [401]. failure #72
I've looked at SIP trace and freeswitch logs but i can't figure out what's causing the registration failure.
here is more info on the issue, i would really appreciate your help guys.
Server: Linux Ubuntu-1204-precise-64-minimal 3.5.0-34-generic #55~precise1-Ubuntu SMP Fri Jun 7 16:25:50 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
freeswitch version: FreeSWITCH Version 1.2.23+git~20140317T213443Z~769a03a629~64bit (git 769a03a 2014-03-17 21:34:43Z 64bit)
Gateway configuration: <gateway name="DIDLogic"> <param name="username" value="username"/> <param name="realm" value="sip.de.didlogic.net"/> <param name="password" value="password"/> <param name="register" value="true"/> <param name="context" value="public"/> <param name="caller-id-in-from" value="true"/> <param name="sip_cid_type" value="none"/> <param name="ping" value="30"/> <param name="ping-max" value="3"/> </gateway>
SIP trace:
2014-04-06 09:32:05.472850 [NOTICE] sofia_reg.c:423 Registering DIDLogic send 894 bytes to udp/[46.165.252.40]:5060 at 06:32:05.492557:
------------------------------------------------------------------------
REGISTER sip:sip.de.didlogic.net;transport=udp SIP/2.0 Via: SIP/2.0/UDP 144.76.98.11:5080;rport;branch=z9hG4bKUZ0p2Fjget1KN Max-Forwards: 70 From: <sip:95299@sip.de.didlogic.net>;tag=XK0KSD17jemDN To: <sip:95299@sip.de.didlogic.net> Call-ID: de332712-ba83-11e3-b33f-0dc96adc5bb0 CSeq: 57892398 REGISTER Contact: <sip:gw+DIDLogic@144.76.98.11:5080 ;transport=udp;gw=DIDLogic> Expires: 3600 User-Agent: FreeSWITCH-mod_sofia/1.2.23+git~20140317T213443Z~769a03a629~64bit Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY Supported: path, replaces Authorization: Digest username="username", realm=" sip.de.didlogic.net", nonce="U0DtvVNA7JFDwqn/iKN2y0i7jjJF/xDpK+45ZYA=", cnonce="tZUwATUmEjKDKHBU0sVf8A", algorithm=MD5, uri="sip: sip.de.didlogic.net;transport=udp", response="8aaadef8769d2234def69a699c53f95c", qop=auth, nc=0000018e Content-Length: 0
------------------------------------------------------------------------
recv 446 bytes from udp/[46.165.252.40]:5060 at 06:32:05.520506:
------------------------------------------------------------------------
SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 144.76.98.11:5080 ;rport=5080;branch=z9hG4bKUZ0p2Fjget1KN From: <sip:95299@sip.de.didlogic.net>;tag=XK0KSD17jemDN To: <sip:95299@sip.de.didlogic.net ;tag=b27e1a1d33761e85846fc98f5f3a7e58.437e Call-ID: de332712-ba83-11e3-b33f-0dc96adc5bb0 CSeq: 57892398 REGISTER WWW-Authenticate: Digest realm="sip.de.didlogic.net", nonce="U0D2EVNA9OVIqS6bUrch5649kHnuK6PXK/Fii4A=", qop="auth" Content-Length: 0
------------------------------------------------------------------------
send 894 bytes to udp/[46.165.252.40]:5060 at 06:32:05.520845:
------------------------------------------------------------------------
REGISTER sip:sip.de.didlogic.net;transport=udp SIP/2.0 Via: SIP/2.0/UDP 144.76.98.11:5080;rport;branch=z9hG4bKv8SF4a3KB3Q6g Max-Forwards: 70 From: <sip:95299@sip.de.didlogic.net>;tag=XK0KSD17jemDN To: <sip:95299@sip.de.didlogic.net> Call-ID: de332712-ba83-11e3-b33f-0dc96adc5bb0 CSeq: 57892399 REGISTER Contact: <sip:gw+DIDLogic@144.76.98.11:5080 ;transport=udp;gw=DIDLogic> Expires: 3600 User-Agent: FreeSWITCH-mod_sofia/1.2.23+git~20140317T213443Z~769a03a629~64bit Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY Supported: path, replaces Authorization: Digest username="username", realm=" sip.de.didlogic.net", nonce="U0D2EVNA9OVIqS6bUrch5649kHnuK6PXK/Fii4A=", cnonce="tZUwATUmEjKDKHBU0sVf8A", algorithm=MD5, uri="sip: sip.de.didlogic.net;transport=udp", response="3dc99375cf925ad9af145899dcf83b1a", qop=auth, nc=0000018f Content-Length: 0
------------------------------------------------------------------------
recv 446 bytes from udp/[46.165.252.40]:5060 at 06:32:05.536657:
------------------------------------------------------------------------
SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 144.76.98.11:5080 ;rport=5080;branch=z9hG4bKv8SF4a3KB3Q6g From: <sip:95299@sip.de.didlogic.net>;tag=XK0KSD17jemDN To: <sip:95299@sip.de.didlogic.net ;tag=b27e1a1d33761e85846fc98f5f3a7e58.b648 Call-ID: de332712-ba83-11e3-b33f-0dc96adc5bb0 CSeq: 57892399 REGISTER WWW-Authenticate: Digest realm="sip.de.didlogic.net", nonce="U0D2EVNA9OUTYGscaPkV4MvAB1IDDtpQK/FjjIA=", qop="auth" Content-Length: 0
------------------------------------------------------------------------
2014-04-06 09:32:05.532842 [ERR] sofia_reg.c:2110 DIDLogic Registration Failed with status Unauthorized [401]. failure #72 2014-04-06 09:32:06.472844 [WARNING] sofia_reg.c:478 DIDLogic Failed Registration [904], setting retry to 2160 seconds.
_________________________________________________________________________
Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE: http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE: http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_________________________________________________________________________
Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE: http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
participants (1)
-
Snabel Kabiya