The octets doesn't work either (get same result with integer) to decode this field.
I get this: IMSI = 0x24076301002058f6
where I should read: 247036100020856
Do you think I should add a new type definition in the code?
Thanks,
Arnaud G
Alan DeKok wrote:
Arnaud G <[EMAIL PROTECTED]> wrote:
Hello here is a little dictionary for the nokia ggsn (GPRS equipement):...
#Not provided by nokia ggsn
#VENDOR Nokia
#
# Vendor-specific attributes
#
ATTRIBUTE IMSI 224 integer
Are they crazy? They're using non-VSA's?
But I have a little problem wirh the IMSI field. It is discribed by nokia as:
IMSI -> String : Its format is binary coded decimal with extra four bits set to 1 for an odd number of digits, e.g 123 equals hexadecimal bytes 21 F3
I didn't find a type between string/abinary that give me the right number. I set it to integer where it seems to be more correct. Any idea??
'octets'
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
