Hello,
If you are using the acc module for CDR generation then only the Stop
message should be received by the Radius server. This message should
contain all the information you need like duration, startup time,
creation time and others.
Regards,
Razvan
On 05/20/2011 02:46 AM, Cindy Leung wrote:
I am also not receiving a Start packet on my radius server for some reason.
I'm new to this so please bear with me. :-)
modparam("acc", "early_media", 1)
modparam("acc", "report_ack", 1)
modparam("acc", "report_cancels", 1)
modparam("acc", "detect_direction", 0)
modparam("acc", "failed_transaction_flag", 3)
modparam("acc", "aaa_flag", 1)
modparam("acc", "service_type", 15)
modparam("acc", "aaa_url", "radius:/etc/radiusclient-ng/radiusclient.conf")
modparam("acc", "cdr_flag", 6)
I am seeing all the "Intrim-Update" and "Stop" packets.
Any suggestions as to what to look for please? Thanks.
Cindy
On Apr 29, 2011, at 10:42 AM, Maciej Bylica wrote:
Hi Vlad,
Thanks for info.
I am about to work on this.
Thanks,
Maciej
2011/4/21 Vlad Paiu<[email protected]>:
Hello,
The new CDRs type of accounting in OpenSIPS 1.6.4 only produces one entry
per call for every type of backend, whether it's a DB, Radius or Syslog. So
it's natural to only have a single STOP entry per call, and not two, a start
and stop entry as in the old type of accounting.
The STOP packet should also contain the Sip-Call-Duration and
Sip-Call-Duration attributes, defined in the 'etc/dictionary.opensips'
dictionary that comes with the OpenSIPS sources. Are you using that provided
dictionary ?
Regards,
Vlad
On 04/17/2011 11:38 PM, Maciej Bylica wrote:
Dear OS Fans,
I've just managed to configure new acc with dialog cdr generation
feature with Mysql.etc/dictionary.opensipset
It looks fine and realy help to do accouting for some of us.
In my scenario there is a need to use Radius.
As stated in acc module description, there is a need to use cdr_flag
and setflag in initial invite.
Once it is set there i do receive only STOP radius acc packet.
In case i do not have setflag set anywere in my script Opensips
produce START and STOP packet properly.
Does anyone knows where to look for the problem?
Last question does standard STOP packet incorporate call duration attr
anyhow or should i use aaa_extra in my config.
My STOP packet is as follows:
Sun Apr 17 21:08:38 2011
Acct-Status-Type = Stop
Service-Type = IAPP-Register
Sip-Response-Code = 200
Sip-Method = Bye
Event-Timestamp = "\266:\253M\374\212\256"
Sip-From-Tag = "eb759c18"
Sip-To-Tag = "00-07350-027f5afd-492940963"
Acct-Session-Id =
"b0790b4443102642ZTMzOWZlNGU0Njg4MDMwM2EzZjI1NTY5NTllNWFiYjk."
User-Name = "[email protected]"
Calling-Station-Id = "sip:[email protected]"
Called-Station-Id = "sip:[email protected]"
Sip-Translated-Request-URI = "sip:77.77.77.77:5060"
User-Agent = "X-Lite release 1003l stamp 30942"
Contact = "<sip:[email protected]:15950>"
NAS-Port-Id = 5060
Acct-Delay-Time = 0
NAS-IP-Address = 127.0.0.1
Client-IP-Address = 127.0.0.1
Acct-Unique-Session-Id = "7e6e2ace14ff4970"
Timestamp = 1303067318
I do have the latest OS 1.6.4-2-notls revision 7872.
Thx in advance for help,
Maciej.
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
--
Razvan Crainea
OpenSIPS Developer
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
