Chris Parker wrote:

>
> What attributes are these?

Example from a detail file:

Mon Dec 10 17:42:59 2001
 NAS-IP-Address = <edited to protect the innocent>
 Vendor-Specific = 0x000019da02093020302f322f31
 NAS-Port-Type = Async
 User-Name = "567"
 Called-Station-Id = "<edited to protect the innocent>"
 Calling-Station-Id = ""
 Acct-Status-Type = Stop
 Acct-Delay-Time = 0
 Acct-Input-Octets = 0
 Acct-Output-Octets = 0
 Acct-Session-Id = "31AE6B8400000036"
 Acct-Session-Time = 10
 Acct-Input-Packets = 0
 Acct-Output-Packets = 0
 Service-Type = 0
 Vendor-Specific =
0x000019da1830683332332d636f6e662d69643d333336323636363320333233313339363520363130303330333120333533333030

 Vendor-Specific =
0x000019da013b683332332d696e636f6d696e672d636f6e662d69643d3030303030303030203030303030303030203030303030303030203030303030303336

 Vendor-Specific = 0x000019da210d683332332d67772d69643d
 Vendor-Specific =
0x000019da1a1c683332332d63616c6c2d6f726967696e3d6f726967696e617465
 Vendor-Specific = 0x000019da1b15683332332d63616c6c2d747970653d566f4950
 Vendor-Specific =
0x000019da1932683332332d73657475702d74696d653d30323a35303a32322e3139302055544320546875204e6f762032322032303031

 Vendor-Specific =
0x000019da1c34683332332d636f6e6e6563742d74696d653d30323a35303a33372e3136302055544320546875204e6f762032322032303031

 Vendor-Specific =
0x000019da1d37683332332d646973636f6e6e6563742d74696d653d30323a35303a34372e3530302055544320546875204e6f762032322032303031

 Vendor-Specific = 0x000019da1716683332332d72656d6f74652d616464726573733d
 Vendor-Specific = 0x000019da1e1a683332332d646973636f6e6e6563742d63617573653d3136
 Vendor-Specific = 0x000019da1f16683332332d766f6963652d7175616c6974793d30
 Client-IP-Address = <edited to protect the innocent>
Timestamp = 1008024179
 Request-Authenticator = None

All of those Vendor-Specific Attributes are comming from a Cisco As5300 doing VoIP



>
> >Is this just something that someone hasn't gotten around to decoding the
> >VSAs or is this a bug or do I need to use an undocumented switch or
> >something?
>
> You may want to change the dictionary entries from octet to string for the
> attributes if you know they are being sent as human readable strings.
>

All of the Cisco VoIP Attributes are already set as string.

I'm not sure how they are being sent.. I just know all of the cisco documentation
shows everything in a human readable form

like:   h323-gw-id=<ip>  h323-conf-id=<conf id> h323-remote-address=<remote
address>   (and so on)

Thank you

Jeremy McNamara


- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Reply via email to