This is fixed in the next Emerald release.
> But I can't use this feature anyway, because RadiusNT .60 doesn't support
> it (or there's a bug or something), and when I use .90 (which does work
> with this), RadiusNT .90 stops handling accounting records after an acct.
> record pops up trying to insert a "(null)" into the Calls.UserName column.
> So far, the only RadiusNT version that I've used that this occurs with is
> version .90 (never tried .80 or whatever version came out after .60). So,
> needless to say, I'm back to using .60 until that problem is fixed,
> therefor, can't use the Default Extend (Limit).
> I know that (1.19?) is due to be released soon--will this version fix the
> above mentioned problem in .90?
Actually RadiusNT 2.2 will be the next release. The problem with
that it correctly detects errors and doesn't ACK the accounting when
an error. This is so that if RadiusNT lost its connectiont to SQL
couldn't insert, etc, the accounting packet is not lost. Now it DOES
know to ACK A duplicate from the database. We'll add some more smarts
handle bad accounting and ACK it, so that it doesn't stay around for
-- Dale E. Reed Jr. (firstname.lastname@example.org)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.emerald.iea.com