Decoding complex CableLabs-Event-Message

[Laurent Debacker]

Hi,

We would like to use FreeRadius to decode Cablelabs accounting messages, as
specified in
http://www.cablelabs.com/packetcable/downloads/specs/PKT-SP-EM-I12-05812.pdf
.

FreeRadius has a CableLabs dictionary, which works fine, but...
The value of one of the AVP, CableLabs-Event-Message, is actually an HEX
value containing additional fields.
For example:
        CableLabs-Event-Message =
0x0001d2d2026d30310000000000003030313030303000
0e812333000100033031000000000000303031303030300000000006323031323031333130363032
32312e3633390000000081000500

The FreeRadius does not decode that value to get all details.
For example, bytes 4 to 28
(d2d2026d303100000000000030303130303030000e812333) is actually the BCID
(Billing Correlation ID) field.
The BCID itself contains 4 "sub" fields: NTP time reference (4 first
bytes), Element ID (next 8 bytes), Time Zone (next 8 bytes), and Event
counter (ast 4 bytes).
See the packet cable specifications for more details.

I understood the only way would be to write a perl module to decode those
values.

Before I start writing, does anyone know of any implementation of such a
perl module? I would not like spending my time rewriting something that
already exists.

Thanks in advance for any help anyone could provide on this topic.

Laurent.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeradius.org/pipermail/freeradius-users/attachments/20120131/d94815c4/attachment.html>