Here is debug log from cisco:
16w0d: Attribute 4 6 D53D3A8C 16w0d: Attribute 5 6 00000017 16w0d: Attribute 61 6 00000004 16w0d: Attribute 1 5 7761701E 16w0d: Attribute 30 5 3532311F 16w0d: Attribute 31 10 39393138 16w0d: Attribute 2 18 23CD7701 16w0d: Attribute 6 6 00000002 16w0d: Attribute 7 6 00000001 16w0d: Attribute 8 6 515FA0BF
You can see that attribute 8 (Framed-IP-Address) is transmitted to kannel, but it doesn't makes sense for kannel, and I cannot get mapping.
In answer kannel sends following packet:
16w0d: Attribute 6 6 00000002 16w0d: Attribute 7 6 00000001 16w0d: Attribute 8 6 FFFFFFFE 16w0d: Attribute 9 6 FFFFFFFF 16w0d: Attribute 12 6 000005DC 16w0d: Attribute 13 6 00000001
Stipe Tolj wrote:
Hi David,
ok, know I know why:
the problem is that your NAS does not deliver an 'Framed-IP-Address' attribute within the acct packet, hence the folllowing inside radius/radius_acct.c:update_tables():
... client_ip = dict_get(pdu->attr, octstr_imm("Framed-IP-Address")); ...
will be of course NULLed and hence there is no mapping.
I wasn't aware that the Framed-IP-Address is an optional field. Is it? Seems it's not mandatory inside the acct packets.
Hmmm, how can we register the mapping inside the "client IP <-> MSISDN" mapping without the client IP?????
Can you check your NAS if this is configurable? What NAS device is it?
Stipe
[EMAIL PROTECTED] ------------------------------------------------------------------- Wapme Systems AG
Vogelsanger Weg 80 40470 D�sseldorf
Tel: +49-211-74845-0 Fax: +49-211-74845-299
E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de ------------------------------------------------------------------- wapme.net - wherever you are
-- David Chkhartishvili Tel: 995 99 182418
