Mike Chamberlain <[EMAIL PROTECTED]> wrote: > I am using various Quintum boxes to communicate with our FreeRadius > server. My question concerns the attributes: > > Quintum-AVPair = "xxxx=yyyy" > > What we need to know is... what's the deal with that?
Ask Quintum. It's annoying. > What is the > difference between an AVPair attribute and the other standard > name-value attributes such as: > > Quintum-h323-gw-id = "h323-gw-id=au-syd-wentworth" Not much. Quintum just copied what Cisco did, which was a very bad idea. > It seems that there are multiple values that could be passed as the > AVPair, but FreeRadius only seems to be able to access. For instance, > reading the FreeRadius log, during authentication, the AVPair contains > "h323-ivr-out=ACCESSCODE:xxxx", but then later during authorization it > contains "h323-ivr-out=FOLLOW_ON_FLAG:0". Then, on the stop call > message, it contains "h323-incoming-conf-id=33383732 61306336 38390064 > 393862B3". Why can the AVPair values not all be sent through in the > latter format? Ask the NAS. FreeRADIUS doesn't get to choose the format the NAS sends. > Why could these attributes not be passed on their own, > rather than lumped into this AVPair affair? If I want to access the > h323-incoming-conf-id when it is not presented as its own attribute, > is it accessible through the AVPair? Maybe. > Basically, if anyone can point me to some documentation that explains > this whole AVPair ridiculousness then that would be great. It's a Quintum attribute. Try asking them. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
