hello About this error in my SuSE box, I have installed Ser, Radiusclient and Freeradius in other PC with Red Hat 9 and now radius accounting is working very well so I think there is a problem with some module or library in SuSE Linux 9...
Now I have some questions about this accounting logs:
1. I have 3 states for each call: 2 starts and 1 stop, please see the log below and tell me how can I solve this problem.
2. I need account non successful calls, i.e. 0 second calls, is this possible with this module?
thanks Rafael
----- Radius Log for 1 completed call ---------->
Fri Jul 23 18:04:45 2004 Acct-Status-Type = Start Service-Type = IAPP-Register Sip-Response-Code = 200 Sip-Method = Invite User-Name = "6603000@200.110.2.131" Calling-Station-Id = "sip:6603000@200.110.2.131" Called-Station-Id = "sip:6604000@200.110.2.131" Sip-Translated-Request-URI = "sip:6604000@200.110.6.58" Acct-Session-Id = "f1367900-7340-4684-802a-0002a40055b2@10.0.0.236" Sip-To-Tag = "bb405f25a4" Sip-From-Tag = "f100462aa4" Sip-CSeq = "15" NAS-IP-Address = 127.0.0.1 NAS-Port = 5060 Acct-Delay-Time = 0 Client-IP-Address = 127.0.0.1 Acct-Unique-Session-Id = "71f539047855d0e4" Timestamp = 1090623885
Fri Jul 23 18:04:45 2004 Acct-Status-Type = Start Service-Type = IAPP-Register Sip-Response-Code = 200 Sip-Method = Bye User-Name = "6603000@200.110.2.131" Calling-Station-Id = "sip:6603000@200.110.2.131" Called-Station-Id = "sip:6604000@200.110.2.131" Sip-Translated-Request-URI = "sip:6604000@200.110.6.58" Acct-Session-Id = "f1367900-7340-4684-802a-0002a40055b2@10.0.0.236" Sip-To-Tag = "bb405f25a4" Sip-From-Tag = "f100462aa4" Sip-CSeq = "15" NAS-IP-Address = 127.0.0.1 NAS-Port = 5060 Acct-Delay-Time = 0 Client-IP-Address = 127.0.0.1 Acct-Unique-Session-Id = "71f539047855d0e4" Timestamp = 1090623885
Fri Jul 23 18:05:06 2004 Acct-Status-Type = Stop Service-Type = IAPP-Register Sip-Response-Code = 200 Sip-Method = 8 User-Name = "6604000@200.110.2.131" Calling-Station-Id = "sip:6604000@200.110.2.131" Called-Station-Id = "sip:6603000@200.110.2.131" Sip-Translated-Request-URI = "sip:6603000@10.0.0.236" Acct-Session-Id = "f1367900-7340-4684-802a-0002a40055b2@10.0.0.236" Sip-To-Tag = "f100462aa4" Sip-From-Tag = "bb405f25a4" Sip-CSeq = "9" NAS-IP-Address = 127.0.0.1 NAS-Port = 5060 Acct-Delay-Time = 0 Client-IP-Address = 127.0.0.1 Acct-Unique-Session-Id = "8b35f17e9ba92270" Timestamp = 1090623906 -------------------------
Jan Janak jan@iptel.org wrote: On 21-07 11:07, Rafael J. Risco G.V. wrote:
Hi Jan I did not see any other error in Ser or Radiusd Debuging, I?ve tested radiusclient with "radclient" and I think its working as I can see in the logs below:
sipser:/usr/local/etc/raddb# radclient -f digest localhost auth hola123 Received response ID 138, code 2, length = 45 Reply-Message = "Hello, test with digest"
This tests just authentication, not accounting.
on the other hand, freeradius in debug mode just show me authentication process from Ser and it is doing "accounting" for other NAS like gnugk and cisco as5350 (please look the radius log below)... About "radius-ing failed" message, I found this parameter in acc.c (line 674,2-16):
if (rc_acct(SIP_PORT, send)!=OK_RC) { LOG(L_ERR, "ERROR: acc_rad_request: radius-ing failed\n"); goto error; } rc_avpair_free(send); return 1;
Yes, but the error comes from the radiusclient library because rc_acct does not return OK_RC, as you can see in the code snippet above.
I really do not know what the problem is, since it is working in other setups, I suppose your radiusclient library is not configured properly, maybe there is an error in the dictionary files. It is also possible to enable debugging in radiusclient, but you need to recompile the library to make it work.
Jan.
_______________________________________________ Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
--------------------------------- Do You Yahoo!? Todo lo que quieres saber de Estados Unidos, América Latina y el resto del Mundo. Visíta Yahoo! Noticias.