> ODBC: SQLExecDirect Error:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY KEY
> constra
> int 'pk_Calls': Attempt to insert duplicate key in object 'Calls'.
> Sending Accounting Ack of id 192 to ce9ce303 (usr1.linkup.net)
>
> Response Time: 60
> This started happening after I reset my NAS. It was acting up. I am
> talking with my vendor but am not sure I am being fed the correct
> infrmation. Can someone tell me exactly how the AcctSessionID is
> generated? Is it entirely by the NAS at the point the call is started or
> how? I assume this is the duplicate key right?
The key is the above four fields. They must be unique for the duration
of the
accouting packet in the calls table. Typically the first byte is the
"start cycle", and the last three bytes are the accounting cycles. This
would
be 99 reboots of 2^24 calls (which call roll to the next start cycle
is need be. The above looks like the third reboot, 12th accounting
record.
-- Dale E. Reed Jr. (daler@iea.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.emerald.iea.com