Hello,
We have a bit of a problem with some Cisco Vendor Specific Attributes for
the voice enabled AS5300. When accounting for voice Cisco has implemented a
VSA scheme for voice specific accounting attributes. Eg: h323-connect-time,
h323-voice-quality, h323-call-type, etc. I have added the necessary
definitions in the dictionary and receive the VSAs. The problem is this:
Cisco sends the VSAs with the Attribute name appended to the value. So
radiator receives and logs the following CDR information:
h323-connect-time = "h323-connect-time=22:08:12.830 UTC Thu Dec 16 1999"
or
h323-voice-quality = "h323-voice-quality=0"
All other Cisco VSAs (Cisco-NAS-Port, other non-h323) work fine.
I have confirmed with Cisco that this is a known problem/issue which is not
going to be remedied. They will be relying on the Radius server to parse out
the extraneous information. I believe their reasons are for flexibility for
Radius servers without dictionary capability (?). They say that the Merit
radius server encounters the same problems and manual parsing is necessary.
Cisco secure parses automatically.
My question is what is the most efficient way to do this with Radiator? I'm
thinking probably a pre-auth/handler-hook function would do. I'm not too
familiar with the Radiator code and am only fairly proficient in Perl so any
help will be greatly appreciated. If you have a more elegant solution or
something built in that I may not know about, please advise.
Thanks for the help and happy new year.
Vincent Torres
[EMAIL PROTECTED]
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
