Run RadiusNT in -x15 debug mode and see what going on with your
If the Cisco is re-using AcctSessionIDs, I would call and complaing to
Cisco about it. Sure, we can work around the problem, but that doesn't
solve the actual problem itself. Several people had to do this with
USR, before they issued a patch similiar to this a while ago.
> Do we need to modify any parameter in our configuration in order to make
> it work ???
> In case we modify the key of the calls table to include :
> 1- acctsessionid
> 2- Nasidentifier
> 3- acctseessiontype
> And 4- Username
> Will it affect anything ?
> will it solve the problem ?
Adding username will probably make it less likely to be a duplicate,
but doesn't solve the actual problem.
> The cisco access server seem to send duplicate sessionids to Radius Nt
> even though it was NOT the case while using another radius.
RadiusNT has nothing to do with what Cisco sends. Its possible that
other RADIUS server was not as adament about tracking the duplicates.
Dale E. Reed Jr. Emerald and RadiusNT__________________________________________IEA Software, Inc. www.iea-software.com