(RADIATOR) Accounting Cisco Attributes

Richard Grantham Richard.Grantham at bactel.com
Wed May 14 08:20:20 CDT 2003


Hi all,

We know that Cisco, in all their wisdom, decided that their VSA would
take the form 

	cisco-h323-WHATEVER = "h323-WHATEVER=something"

I'm trying to log just the 'somthing' part of that attribute in our
Oracle database and was wondering on the best way to do it.  At the
moment I'm using an ugly klude using the AcctSQLStatement parameter:

    AcctSQLStatement \
      update raw_accounting_log set \
        h323_gw_id = substr('%{cisco-h323-gw-id}', 12), \
        h323_call_origin = substr('%{cisco-h323-call-origin}', 18), \
        h323_call_type = substr('%{cisco-h323-call-type}', 16), \
        h323_conf_id = substr('%{cisco-h323-conf-id}', 14), \
        h323_disconnect_cause = substr('%{cisco-h323-disconnect-cause}',
23), \
        h323_remote_address = substr('%{cisco-h323-remote-address}', 21)
\
      where log_id = %{Timestamp}
 
The other question was how can I specify the primary key of the
accounting record using AcctColumnDef?  As is shown in the example above
I'm using the Timestamp integer - which is not ideal!  I'd like to use
an Oracle sequence which, to those of you who don't know the syntax,
would allow me to specify the PK as log_id.nextval.

TIA,

Richard
-- 
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.


More information about the radiator mailing list