Jeremy McNamara <[EMAIL PROTECTED]> wrote: > $INCLUDE dictionary.cisco IS in the raddb/dictionary file and it looks like > FreeRadius is using the dictionary.cisco file because we can authenticate VoIP > calls but for some reason in the detail file those same VSAs are not getting > decoded when they come from the 5300.
Authenticating VoIP calls is not the issue. If you do not have anything in the servers configuration which uses the VoIP attributes for authentication, then those attributes will be ignored. i.e. A packet with a username && password can be authenticated fine, even if it contains 100 other unknown attributes. The fact that the VoIP attributes are not decoded when logged to the detail file, means they're probably not decoded at *all* in the server. See the FAQ for running the server in debugging mode. I'm willing to bet that when doing authentication, the VoIP attrib utes are printed out in hex. > A test....If we remove $INCLUDE dictionary.cisco from raddb/dictionary we cannot > authenticate calls.. so FreeRadius must be using it, but then why isn't it > decoding them for accounting? That's exceedingly weird. One of the VSA's you posted said: > Vendor-Specific = >0x000019da1830683332332d636f6e662d69643d333336323636363320333233313339363520363130303330333120333533333030 To me, that syas the NAS is generating VSA's for vendor code 0x19da, or 6618. That isn't Cisco, and I don't know what it is. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
