I tried that configuration. I get no errors but also no radius packet is created/sent.
after setting the flag by "setflag()" command , do I have to enter another
command to send the accounting packet for that marked message ?
Thanks,
ilker
________________________________
From: serusers-bounces(a)lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf
Of İlker Aktuna (
Koç.net)
Sent: Wednesday, May 31, 2006 5:26 PM
To: sip; serusers(a)iptel.org
Subject: RE: [Serusers] Radius accounting howto
Thanks for that information. But, how does Ser know to send start or stop message to
radius ?
Thanks,
ilker
________________________________
From: sip [mailto:sip@arcdiv.com]
Sent: Wednesday, May 31, 2006 2:13 PM
To: İlker Aktuna (
Koç.net); serusers(a)iptel.org
Subject: RE: [Serusers] Radius accounting howto
These are essentially log flags.
In order to log an INVITE or a BYE to the radius server (assuming your log_flag param was
set to 1), you'd do something like:
if((method=="INVITE" && !has_totag()) ||
method=="BYE")
{
setflag(1);
};
I stick that BEFORE the loose_route section of my config, as if I don't, it
doesn't seem to catch things correctly. I've yet to debug why. The reason I put
the extra !has_totag() in there is for my accounting, so I don't end up logging
reINVITES from the remote side.
Basically, the parameter for log_flag determines which flag you set in order to log the
packet to the radius server.
N.
[UTF-8?]On Wed, 31 May 2006 10:48:42 +0300, İlker Aktuna \(Koç.net\) wrote
Hi,
Thanks for your reply. I saw that in the source and changed according to them. But I
still can't see any radius packets created/sent by Ser when a call is made.
What should I add to the configuration to send start/stop packets ?
Regards,
ilker
-----Original Message-----
From: serusers-bounces(a)lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On
Behalf Of sip
Sent: Tuesday, May 30, 2006 8:28 PM
To: serusers(a)iptel.org
Subject: Re: [Serusers] Radius accounting howto
Those params are valid for the old acc module compiled with radius support.
The acc_radius module I think uses log_flag and log_missed_flag (according to the
source).
N.
On Tue, 30 May 2006 17:54:40 +0300, Ýlker Aktuna (
Koç.net) wrote
Hi everyone,
I am trying to use acc_radius module with presence CVS sources.
I compiled the radiusclient library and compiled ser with acc_radius module.
Then I added following lines to the config:
loadmodule "/root/ser/lib/ser/modules/acc_radius.so"
modparam("acc_radius", "radius_config",
"/usr/local/etc/radiusclient-ng/radiusclient.conf")
modparam("acc_radius",
"service_type", 15) modparam("acc_radius",
"radius_flag", 1) modparam("acc_radius",
"radius_missed_flag", 3)
modparam("acc_radius", "report_ack", 0)
But when I try to start ser, it doesn't accept 2 parameters:
modparam("acc_radius", "radius_flag", 1)
modparam("acc_radius",
"radius_missed_flag", 3)
What should be the correct syntax for these parameters ? are they required ?
And what else should I add to the configuration to send radius-start
and
radius-stop messages to the radius server ?
>
> Thanks,
> ilker
>
>
>
>
<http://387555.sigclick.mailinfo.com/sigclick/0B0A0607/040C4D0A/00034D00/28212191.jpg>
_____________________________________________________________________________________________________________________________________________
Bu e-posta mesaji kisiye ozel olup, gizli bilgiler iceriyor olabilir. Eger bu e-posta
mesaji size yanlislikla ulasmissa, icerigini hic bir sekilde kullanmayiniz ve ekli
dosyalari acmayiniz. Bu durumda lutfen e-posta mesajini kullaniciya hemen geri gonderiniz
ve tum kopyalarini mesaj kutunuzdan siliniz. Bu e-posta mesaji, hic bir sekilde, herhangi
bir amac icin cogaltilamaz, yayinlanamaz ve para karsiligi satilamaz. Bu e-posta mesaji
viruslere karsi anti-virus sistemleri tarafindan taranmistir. Ancak yollayici, bu e-posta
mesajinin - virus koruma sistemleri ile kontrol ediliyor olsa bile - virus icermedigini
garanti etmez ve meydana gelebilecek zararlardan dogacak hicbir sorumlulugu kabul etmez.
This message is intended solely for the use of the individual or entity to whom it is
addressed , and may contain confidential information. If you are not the intended
recipient of this message or you receive this mail in error, you should refrain from
making any use of the contents and from opening any attachment. In that case, please
notify the sender immediately and return the message to the sender, then, delete and
destroy all copies. This e-mail message, can not be copied, published or sold for any
reason. This e-mail message has been swept by anti-virus systems for the presence of
computer viruses. In doing so, however, sender cannot warrant that virus or other forms
of data corruption may not be present and do not take any responsibility in any
occurrence.
_____________________________________________________________________________________________________________________________________________