Hi,
I've installed SER and UA is
xlite2.0.
While I changed the ser.cfg to use "digest
authentication" I found that Xlite cannot make any response back to
SER.
My Xlite can register to Brekeke server without problem
and the challenge sequent order is different than
SER's.
Challenge order using the Brekeke is something like
1.UA sends register without digest
credentials
2.Brekeke reply with 401 and include digest
challenge.
3.Phone asks for
username/password
4.Phone sends another
Register
5.Brekeke sends 200 ok
But from the captured packets I found my SER challenge
order is:
1.UA sends register without digest
credentials
2.SER sends 200 ok
3.SER sends 401unauthorized packet with digest
challenge
4.Xlite does not make any response to digest
challenge
Does anyone have same problem? Please give me some
suggestion. Thanks.
Ted
Followings are my settings and log file from
Xlite
---------------------------------------------------------------------------------------------------------------------------------------------------
My Xlite
settings:
SIP Proxy
Enabled: yes
User Name: aaaa
Authorization user: aaaa
Password: aaaa
Domain/Realm: siptest2.com
SIP Proxy: 192.168.13.195
Out Bound Proxy:
Proxy Mode: Normal
Send Internal IP: Always
---------------------------------------------------------------------------------------------------------------------------------------------
Ser.cfg
file:
if (uri==myself)
{
# if (uri==~"siptest2.com")
{
lookup("aliases");
save("aliases");
if (method=="REGISTER") {
# Uncomment this if you want to use digest
authentication
if (!www_authorize("siptest2.com", "subscriber"))
{
www_challenge("siptest2.com",
"0");
break;
};
save("location");
break;
};
# native SIP destinations are handled using our USRLOC
DB
if (!lookup("location"))
{
sl_send_reply("404", "Not
Found");
break;
};
-------------------------------------------------------------------------------------------------------------------------------
XLite Log:
c 2004 Xten Networks, Inc. All
rights reserved.
X-Lite release 1103m build stamp 14262
License key:
F6775B3A009F49A6A8731A9FF47F4925
Established SIP protocol listen
on: 192.168.13.45:5060
SIP: 192.168.13.45:5060
RTP:
192.168.13.45:8000
NAT: 203.70.51.158
Firewall Discovery
Skipped
PROXY#0:
192.168.13.195:5060
SEND TIME: 71179320
SEND >> 192.168.13.195:5060
REGISTER
sip:siptest2.com SIP/2.0
Via: SIP/2.0/UDP
203.70.51.158:5060;rport;branch=z9hG4bKB2835C30DFBD445CBCE7A0EF7102666C
From:
7788 <sip:aaaa@siptest2.com>;tag=4229923641
To: 7788
<sip:aaaa@siptest2.com>
Contact: "7788"
<sip:aaaa@203.70.51.158:5060>
Call-ID:
E9D219D38ED74352BE61793371C150A0@siptest2.comCSeq:
4425 REGISTER
Expires: 1800
Max-Forwards: 70
User-Agent: X-Lite release
1103m
Content-Length: 0
RECEIVE TIME: 71179330
RECEIVE <<
192.168.13.195:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP
203.70.51.158:5060;rport=5060;branch=z9hG4bKB2835C30DFBD445CBCE7A0EF7102666C;received=192.168.13.45
From:
7788 <sip:aaaa@siptest2.com>;tag=4229923641
To: 7788
<sip:aaaa@siptest2.com>;tag=b27e1a1d33761e85846fc98f5f3a7e58.4cd2
Call-ID:
E9D219D38ED74352BE61793371C150A0@siptest2.comCSeq:
4425 REGISTER
Contact:
<sip:aaaa@203.70.51.158:5060>;q=0.00;expires=1800
Server: Sip EXpress
router (0.8.12 (i386/linux))
Content-Length: 0
Warning: 392
192.168.13.195:5060 "Noisy feedback tells: pid=3854
req_src_ip=192.168.13.45 req_src_port=5060 in_uri=sip:siptest2.com
out_uri=sip:siptest2.com via_cnt==1"
RECEIVE TIME: 71179330
RECEIVE <<
192.168.13.195:5060
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP
203.70.51.158:5060;rport=5060;branch=z9hG4bKB2835C30DFBD445CBCE7A0EF7102666C;received=192.168.13.45
From:
7788 <sip:aaaa@siptest2.com>;tag=4229923641
To: 7788
<sip:aaaa@siptest2.com>;tag=b27e1a1d33761e85846fc98f5f3a7e58.4cd2
Call-ID:
E9D219D38ED74352BE61793371C150A0@siptest2.comCSeq:
4425 REGISTER
Contact:
<sip:aaaa@203.70.51.158:5060>;q=0.00;expires=1800
WWW-Authenticate:
Digest realm="siptest2.com",
nonce="41aa11fb6be5ff8f82db0c5b411b09bec6326874"
Server: Sip EXpress router
(0.8.12 (i386/linux))
Content-Length: 0
Warning: 392 192.168.13.195:5060
"Noisy feedback tells: pid=3854 req_src_ip=192.168.13.45 req_src_port=5060
in_uri=sip:siptest2.com out_uri=sip:siptest2.com via_cnt==1"
SEND TIME: 72969444
SEND >> 192.168.13.195:5060
REGISTER
sip:siptest2.com SIP/2.0
Via: SIP/2.0/UDP
203.70.51.158:5060;rport;branch=z9hG4bKB05B820332FD41F3996EE88B69B15047
From:
7788 <sip:aaaa@siptest2.com>;tag=4229923641
To: 7788
<sip:aaaa@siptest2.com>
Contact: "7788"
<sip:aaaa@203.70.51.158:5060>
Call-ID:
E9D219D38ED74352BE61793371C150A0@siptest2.comCSeq:
4426 REGISTER
Expires: 1800
Max-Forwards: 70
User-Agent: X-Lite release
1103m
Content-Length: 0
RECEIVE TIME: 72969624
RECEIVE <<
192.168.13.195:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP
203.70.51.158:5060;rport=5060;branch=z9hG4bKB05B820332FD41F3996EE88B69B15047;received=192.168.13.45
From:
7788 <sip:aaaa@siptest2.com>;tag=4229923641
To: 7788
<sip:aaaa@siptest2.com>;tag=b27e1a1d33761e85846fc98f5f3a7e58.4d70
Call-ID:
E9D219D38ED74352BE61793371C150A0@siptest2.comCSeq:
4426 REGISTER
Contact:
<sip:aaaa@203.70.51.158:5060>;q=0.00;expires=1800
Server: Sip EXpress
router (0.8.12 (i386/linux))
Content-Length: 0
Warning: 392
192.168.13.195:5060 "Noisy feedback tells: pid=3850
req_src_ip=192.168.13.45 req_src_port=5060 in_uri=sip:siptest2.com
out_uri=sip:siptest2.com via_cnt==1"
RECEIVE TIME: 72969624
RECEIVE <<
192.168.13.195:5060
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP
203.70.51.158:5060;rport=5060;branch=z9hG4bKB05B820332FD41F3996EE88B69B15047;received=192.168.13.45
From:
7788 <sip:aaaa@siptest2.com>;tag=4229923641
To: 7788
<sip:aaaa@siptest2.com>;tag=b27e1a1d33761e85846fc98f5f3a7e58.4d70
Call-ID:
E9D219D38ED74352BE61793371C150A0@siptest2.comCSeq:
4426 REGISTER
Contact:
<sip:aaaa@203.70.51.158:5060>;q=0.00;expires=1800
WWW-Authenticate:
Digest realm="siptest2.com",
nonce="41aa18f9a539df7f1af6e0547175a252a158aa4d"
Server: Sip EXpress router
(0.8.12 (i386/linux))
Content-Length: 0
Warning: 392 192.168.13.195:5060
"Noisy feedback tells: pid=3850 req_src_ip=192.168.13.45 req_src_port=5060
in_uri=sip:siptest2.com out_uri=sip:siptest2.com via_cnt==1"