As you can see in the network trace, the SIP server challenges the
REGISTER for authentication, but it seems that the client is not
able/configured to perform digest authentication. After the 401, the
client must send back a REGISTER with an "Authorization" header.
Cheers,
Daniel
On 06/19/06 16:31, Hamid Ali Asgari wrote:
The client can't register, still it doesn't allow registration.
Attached is the ngrep output you mentioned.
Thanks,
Hamid
Ngrep Output:
#
U 85.15.7.17:3166 -> 85.15.7.18:5060
REGISTER sip:shatel.ir SIP/2.0..From: sip:[EMAIL PROTECTED];tag=5fa04040..To:
sip:[EMAIL PROTECTED]: 9401fb256987b29da88b308b1
1ce64ed..Cseq: 1 REGISTER..Contact:
<sip:[EMAIL PROTECTED];LINEID=6f5beb97d08670a1c8328ce1526ae928>..Expires:
300..Date: Mon, 19 J
un 2006 11:02:02 GMT..Max-Forwards: 20..User-Agent: sipX/2.5.2
(WinNT)..Accept-Language: en..Via: SIP/2.0/UDP 85.15.7.17;branch
=z9hG4bK-a4ba80ab4920a96042a782f74c40944d..Content-Length: 0....
#
U 85.15.7.17:3166 -> 85.15.7.18:5060
REGISTER sip:shatel.ir SIP/2.0..From: sip:[EMAIL PROTECTED];tag=5fa04040..To:
sip:[EMAIL PROTECTED]: 9401fb256987b29da88b308b1
1ce64ed..Cseq: 1 REGISTER..Contact:
<sip:[EMAIL PROTECTED];LINEID=6f5beb97d08670a1c8328ce1526ae928>..Expires:
300..Date: Mon, 19 J
un 2006 11:02:02 GMT..Max-Forwards: 20..User-Agent: sipX/2.5.2
(WinNT)..Accept-Language: en..Via: SIP/2.0/UDP 85.15.7.17;branch
=z9hG4bK-a4ba80ab4920a96042a782f74c40944d..Content-Length: 0....
#
U 85.15.7.17:3166 -> 85.15.7.18:5060
REGISTER sip:shatel.ir SIP/2.0..From: sip:[EMAIL PROTECTED];tag=5fa04040..To:
sip:[EMAIL PROTECTED]: 9401fb256987b29da88b308b1
1ce64ed..Cseq: 1 REGISTER..Contact:
<sip:[EMAIL PROTECTED];LINEID=6f5beb97d08670a1c8328ce1526ae928>..Expires:
300..Date: Mon, 19 J
un 2006 11:02:02 GMT..Max-Forwards: 20..User-Agent: sipX/2.5.2
(WinNT)..Accept-Language: en..Via: SIP/2.0/UDP 85.15.7.17;branch
=z9hG4bK-a4ba80ab4920a96042a782f74c40944d..Content-Length: 0....
#
U 85.15.7.18:5060 -> 85.15.7.17:5060
SIP/2.0 401 Unauthorized..From: sip:[EMAIL PROTECTED];tag=5fa04040..To:
sip:[EMAIL PROTECTED];tag=a2c1e7c3808498f2cb2d193cd520e0fc.60d6
..Call-Id: 9401fb256987b29da88b308b11ce64ed..Cseq: 1 REGISTER..Via:
SIP/2.0/UDP 85.15.7.17;branch=z9hG4bK-a4ba80ab4920a96042a78
2f74c40944d..WWW-Authenticate: Digest realm="shatel.ir",
nonce="449677461ef22770698d74f5dde4b0c2f00cf44f"..Server: OpenSer (1.0
.1 (i386/linux))..Content-Length: 0..Warning: 392 85.15.7.18:5060 "Noisy
feedback tells: pid=13352 req_src_ip=85.15.7.17 req_s
rc_port=3166 in_uri=sip:shatel.ir out_uri=sip:shatel.ir via_cnt==1"....
#
U 85.15.7.18:5060 -> 85.15.7.17:5060
SIP/2.0 401 Unauthorized..From: sip:[EMAIL PROTECTED];tag=5fa04040..To:
sip:[EMAIL PROTECTED];tag=a2c1e7c3808498f2cb2d193cd520e0fc.60d6
..Call-Id: 9401fb256987b29da88b308b11ce64ed..Cseq: 1 REGISTER..Via:
SIP/2.0/UDP 85.15.7.17;branch=z9hG4bK-a4ba80ab4920a96042a78
2f74c40944d..WWW-Authenticate: Digest realm="shatel.ir",
nonce="4496774acfd59b6e20c1968fc0bff804d526ce03"..Server: OpenSer (1.0
.1 (i386/linux))..Content-Length: 0..Warning: 392 85.15.7.18:5060 "Noisy
feedback tells: pid=13352 req_src_ip=85.15.7.17 req_s
rc_port=3166 in_uri=sip:shatel.ir out_uri=sip:shatel.ir via_cnt==1"....
-----Original Message-----
From: Daniel-Constantin Mierla [mailto:[EMAIL PROTECTED]
Sent: Monday, June 19, 2006 4:32 PM
To: Hamid Ali Asgari
Cc: [email protected]
Subject: Re: [Users] SIP Clients Can't REGISTER
Hello,
On 06/19/06 14:38, Hamid Ali Asgari wrote:
Hi,
Thanks for the reply.
I commented out the entry you mentioned:
[EMAIL PROTECTED] Auth-Type := Accept, Sip-Group == "suspended",
#Service-Type == "Group-Check"
What happens now is that the radius will check for a group named SUSPENDED
and will reject because it won't match the 101 user:
>From RADIUS debug:
users: Matched entry DEFAULT at line 152
users: Matched entry DEFAULT at line 255
-----------------------------------------------------------
Users:152: DEFAULT Auth-Type = System
Fall-Through = 1
Users:255: DEFAULT Auth-Type := Reject, Service-Type == "Group-Check"
Any thoughts?
this is ok, it is the response that the user is not in the suspended
group. The processing should go further in openser configuration script.
Do you encounter other issues with calls/registrations?
Cheers,
Daniel
Hamid
-----Original Message-----
From: Daniel-Constantin Mierla [mailto:[EMAIL PROTECTED]
Sent: Monday, June 19, 2006 12:54 PM
To: Hamid Ali Asgari
Cc: 'Edson'; [email protected]
Subject: Re: [Users] SIP Clients Can't REGISTER
If look carefully in the configuration file of the tutorial, it checks
for users belonging to "suspended" group. As you have in 'users' file:
[EMAIL PROTECTED] Auth-Type := Accept, Sip-Group == "suspended",
Service-Type == "Group-Check"
Reply-Message = "Authorized"
means that user 101 is in suspended group and it is not allowed to
register or initiate calls. So remove this line for your 'users' file.
Also, when you test, just watch the network traffic on you sip server,
it will reveal the reply code so you can spot easily which statement was
hit in the config file: ngrep -d any port 5060
Cheers,
Daniel
_______________________________________________
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users
