The release notes for 2.5 mention that if you have and problems with
RadiusNT 2.5.200, we recommend that you fall back to 2.5.124. I would
recommend using RadiusNT 2.5.124 unless you have a specific reason
to use the RadiusNT 2.5.200.
RadGetConfigs gets the RADIUS attributes for a specific user (the
accountid is the number following it). There is also a RadGetATConfigs
for the Account Type defaults.
Most likely the problem is that the trigger on your calls table did not
get re-added correctly during the database update. Using Enterprise
manager, check to see if you have a calls_insert trigger on your
-- Dale E. Reed Jr. (firstname.lastname@example.org)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com