Then I don't know what to say. You can remove the key from the calls
table and pray for the best. Other than that, tell CompuTone to make
thier RADIUS accounting usefull. If you can't prevent duplicate
accounting, how are you going to bill based on it?
> >The calls table and the callsonline view is related, but NOT the same.
> >If callsonline isn't working, you either don't have the trigger
> >installed to upkeep the callsonline table (actually the server ports table)
> >or you don't have entries in the server ports table for the NAS.
>
> I've checked both the trigger (present) and the ports list and both are
> present. Any other ideas?
Is the trigger the one from the insttrig.sql script? I have seen some
installations with 6.5 where people used the HTML wizard to get a report
from the calls table each morning and it busted the calls trigger.
> Perhaps you can DETAIL what I'm looking for in the trigger area? Based on
> what someone ELSE said, I believe the trigger to be correct, but I may be
> mistaken.
Compare it to the one in insttrig.sql for delete it and re-run
insttrig.sql.
-- Dale E. Reed Jr. (daler@iea.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.emerald.iea.com