Sounds weird that the incoming requests log on the radius server doesn't show anything. A digest problem should generate a log entry as digest is implemented as a set of av pairs as part of the request and where User-Password is not present. The radius server needs to understand the headers and calculate the required hashes etc to determine match. BTW, providing a RADIUS server for SIP auth without DIGEST support is a fraud, as DIGEST is part of the RFC. So, I do believe Quintum supports DIGEST and that the problem lies elsewhere.
g-)
----- Original Message -----
From: Ashutosh kumar
To: serusers@lists.iptel.org
Sent: Wednesday, November 23, 2005 11:59 AM
Subject: [Serusers] Quintum and radius_aith

Hi all,

          I am using Quintum tenor platform (radius + pstn gw) to send my calls outwards to pstn. I am using radius authorization. The radius server is provided by Quintum itself as a packaged billing+gw solution.

          The radius auth packets seem to go from my ser and they even land on the radius server, but they are not visible in the “incoming requests” monitor of the radius server or its log, although they are visible in the Ethereal on the radius machine. What I doubt is whether the Quintum radius is supports digest requests or not, because my radius packets are working very fine with freeradius, although on a different machine.

 

          Correct me or ask for clarification when and where needed.

 

          Any help will be highly appreciated.

 

PS:      - As evident, I am not having any problem in my radiusclient.conf.

           - The radius server is running on standard ports.

 -There is no firewall policy on the Quintum radius server that blocks/denies/rejects any packets from ser.

 

Regards,

Ashutosh Kumar

_______________________________________________
Serusers mailing list
serusers@lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers