Hi,
 
I succeeded in sending radius start/stop packets to my Radius server.
But I saw a problem when the hanging up party is different from the calling party.
 
In the following radius start/stop pair 200000900568888885 calls 200000900569871112 but 200000900569871112 is hanging up. So the BYE message is sent from 200000900569871112.
 
How can I solve this problem so that calling party is same for both radius start stop messages ?
 
Thu Jun  1 16:29:11 2006
        Acct-Session-Id = "c73bf2494104ba79ZTdhMWJjNTYwYmMyM2E1ZjFmZWZhMDAyYWVjYzNmNjM."
        Gric-Timezone = 1714959921
        Ascend-PRI-Number-Type = 577334379
        Ascend-Route-IP = 1936289850
        Gric-Roaming-Server-Id = "INVITE"
        Ascend-Calling-Subadddress = "sip:200000900569871112@192.168.1.23:16634;rinstance=388dfcffc2868d87;transport=udp"
        Gric-Request-Type = 1664561715
        Ascend-Route-IPX = 577334379
        Ascend-Callback-Delay = 3277318212
        Acct-Status-Type = Start
        Service-Type = 15
        User-Name = "200000900568888885@sip.test.net"
        NAS-Port = 5060
        Acct-Delay-Time = 0
        NAS-IP-Address = 193.243.202.99
        Timestamp = 1149168551
 
Thu Jun  1 16:29:13 2006
        Acct-Session-Id = "c73bf2494104ba79ZTdhMWJjNTYwYmMyM2E1ZjFmZWZhMDAyYWVjYzNmNjM."
        Gric-Timezone = 1664561715
        Ascend-PRI-Number-Type = 577334379
        Ascend-Route-IP = 1936289850
        Gric-Roaming-Server-Id = "BYE"
        Ascend-Calling-Subadddress = "sip:200000900568888885@192.168.1.28:16934"
        Gric-Request-Type = 1714959921
        Ascend-Route-IPX = 577334379
        Ascend-Callback-Delay = 1432970919
        Acct-Status-Type = Stop
        Service-Type = 15
        User-Name = "200000900569871112@sip.test.net"
        NAS-Port = 5060
        Acct-Delay-Time = 0
        NAS-IP-Address = 193.243.202.99
        Timestamp = 1149168553
Regards,
ilker

From: sip [mailto:sip@arcdiv.com]
Sent: Thursday, June 01, 2006 1:10 AM
To: İlker Aktuna (Koç.net); serusers@iptel.org
Subject: RE: [Serusers] Radius accounting howto

The purpose of the module is to take care of that all for you.  I'm afraid I don't use the acc_radius module as I don't honestly see the point in separating out each and every logging function into separate modules (talk about backward thinking).  I still use the older acc module compiled with radius support.

The code block I sent you is all that's necessary for the logging of start/stop requests.

N.


[UTF-8?]On Wed, 31 May 2006 19:47:50 +0300, İlker Aktuna \(Koç.net\) wrote
> 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@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@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@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@lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of sip
> > Sent: Tuesday, May 30, 2006 8:28 PM
> > To: serusers@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
> > >
> > > 
> > >
> > >
>
>

_____________________________________________________________________________________________________________________________________________
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.
_____________________________________________________________________________________________________________________________________________