Hello Folks,
I got some strange issue with RadAuth module.
I have a running server which works just great with RadAuth. The problem comes when in the FROM and TO headers are no descriptions. EG:
Following request will be properly processed:
#
INVITE sip:0012345@babble.net SIP/2.0. To: "0012345"sip:0012345@babble.net. From: "Some User"sip:user@babble.net;tag=5a7e9242.
BUT the following one will not:
INVITE sip:00123456@babble.net SIP/2.0. To: sip:0012345@babble.net. From: sip:user@babble.net:10101;tag=1-2963920204.
Here is what I will get WRONG in RADIUS Server:
Packet-Type = Access-Request Thu Nov 30 22:52:31 2006 User-Name = "user@babble.net" Digest-Attributes = "\n\020user@babble.net" Digest-Attributes = "\001\014babble.net" Digest-Attributes = "\002*456f61dc0d715ea80fd0ed0431df75b73a4c4092" Digest-Attributes = "\004\020sip:babble.net" Digest-Attributes = "\003\010INVITE" Digest-Response = "c96792da6dfb093215150ccd250fac34" Service-Type = Sip-Session Sip-Uri-User = "user" NAS-IP-Address = 127.0.0.1 NAS-Port = 5060 Client-IP-Address = 87.102.50.17
The problem is that in the Digest-URI part I will not get the sip:0012345@babble.net, but the sip:babble.net, therefore completly erroneous info.
I have checked with xlog the request on openser server just before passing the info to radius_proxy_authorize function, and all the FROM-URI, TO-URI, R-URI avps were just fine.
Can somebody from the DEVELOPERS help me? I cannot see other solution, since there is nothing to be tuned in the settings of radauth module.
Thank you in advance for your time!
Cheers, Dan
____________________________________________________________________________________ Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com