I have a problem here where some equipment reports the h323id in 4 �0� padded hex words, and other equipment doesn't �0� pad it.
EG: One nas does something like: printf(�%08x %08x %08x %08x�,a,b,c,d), and another does something like: printf(�%x %x %x %x�,a,b,c,d), What I want to do is force all h323-conf-id Cisco VSA attributes to the second form when inserting into my accounting database. I see a few different ways of doing this: 1. Hack the cisco sa attribute fixup code to also fix up this format for the h323-conf-id attribute. 2. Write a C extension function for postgresql to do this in the insert statement. 3. Make a new type in postgresql which stores internally in 4 4byte words with as �%x %x %x %x� external form I suspect '1' would be the most efficient place to do this, and I wonder if this modification would be acceptable back upstream. I am sure someone else must have come across this problem before, and I am interested in seeing how this was dealt with. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
