as the descriptin in RFC 2865 continues to say...
The actual format of the information is site or application
specific. UTF-8 encoded 10646 [7] characters are recommended, but
a robust implementation SHOULD support the field as
undistinguished octets.
The codification of the range of allowed usage of this field is
outside the scope of this specification.
I think you're seeing a Mac address, probably from a Wireless Access point
See RFC 3580
though the originator didn't follow that format either, which calls for
dashes between hex bytes.
Dave.
- Original Message -
From: zack musa [EMAIL PROTECTED]
To: freeradius-users@lists.freeradius.org
Subject: MAC address in Radacct
Date: Wed, 23 Feb 2005 17:56:39 -0800 (PST)
Hi
In my radacct table, under the calling station ID
attribute field, I get this value.
|CallingStationID |
|00:04:75:FC:09:5A|
From what i get in the RFC 2865,this Attribute allows
the NAS to send in the Access-Request packet the phone
number that the call came from, using Automatic Number
Identification (ANI) or similar technology.Is it
suppose to be the phone number? Since what appear in
my dialup admin accounting table, the attribute field
are named callerID, and containing the same value
(|00:04:75:FC:09:5A|).Can someone help to clarify me
what is the difference between CallerID (in dialup
admin) and CallingStationID (in the radacct table of
mysql DB)?
Another thing is there any ERD or any type of diagram
that explain the operation of dialupadmin that I can
refer?
Thanks to all.
__
Do you Yahoo!?
Yahoo! Mail - Find what you need with new enhanced search.
http://info.mail.yahoo.com/mail_250
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
