John,
If you aren't tied to the name 'Ascend-Disconnect-Cause' just do
what I did:
sed s/Ascend-Disconnect-Cause/Acct-Terminate-Cause/g dictionary >
dictionary.test
Then move your dictionary.test file into place as 'dictionary'. Now the
Ascend codes sent will be turned into Acct-Terminate-Cause in your sql db.
I had the same issue when working with Ciscos and Ascends. Now my db has
all the terminate reasons in it regardless of nas and I'm only inserting
%{Acct-Terminate-Cause} into my db.
--------------------------------------------------------------------------
Aaron Holtz
ComNet Inc.
UNIX Systems Administration/Network Operations
"It's not broken, it just lacks duct tape."
--------------------------------------------------------------------------
On Nov 12, John Coy molded the electrons to say....
>My network is comprised mostly of Ascend MAX terminal servers.
>I have one USR Total Control chassis, however, and I'm trying
>to log some radius accounting information that is normally
>available through the Ascend units.
>
>There is one attribute - Ascend-Disconnect-Cause - which
>shows the reason why a connection was disconnected. The
>equivalent USR attribute is Acct-Terminate-Cause.
>
>Since I use SQL accounting, I'm stuck for a way to set the
>attribute in my insert string. I was wondering if there was
>a way to set an accounting attribute such that:
>
>(using a ?: constructor)
>
>Acct-Terminate-Cause = Acct-Terminate-Cause ? Acct-Terminate-Cause :
>Ascend-Disconnect-Cause;
>
>Is there a clever way to do this in the Radiator server?
>
>Thanks in advance.
>
>John
>
>
>===
>Archive at http://www.thesite.com.au/~radiator/
>To unsubscribe, email '[EMAIL PROTECTED]' with
>'unsubscribe radiator' in the body of the message.
>
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
