[asterisk-users] Asterisk Radius CDR
Ahmed Munir
ahmedmunir007 at gmail.com
Tue Sep 27 14:32:37 CDT 2016
I did radius client status testing with radius server, able to access the
radius server. However, still getting radius CDR issue after setting debug
level 8 even granting 666 access to radiusclient-ng config files.
message: cdr_radius.c:208 radius_log: Unable to create RADIUS record. CDR
not recorded!
Please advise if I missed out anything.
Date: Mon, 26 Sep 2016 12:09:34 +0200
> From: Willy Offermans <asterisk at Offermans.Rompen.nl>
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> <asterisk-users at lists.digium.com>
> Subject: Re: [asterisk-users] Asterisk Radius CDR
> Message-ID: <20160926100934.GB4895 at vpn.offrom.nl>
> Content-Type: text/plain; charset=us-ascii
>
> Hello Ahmed,
>
> On Fri, Sep 23, 2016 at 04:12:42PM -0400, Ahmed Munir wrote:
> > Hi,
> >
> > I've recently setup Asterisk with Radius CDR by following the document:
> > https://wiki.asterisk.org/wiki/display/AST/RADIUS+CDR+Backend.
> >
> > The issue currently I'm facing is after turning on the debug getting
> > message: cdr_radius.c:208 radius_log: Unable to create RADIUS record. CDR
> > not recorded!
> >
> > I've checked and grant access 666 to radiusclient config files: servers &
> > dictionary.digium and 777 to '/var/run/radius.seq'. I've noticed that
> > /var/run/radius.seq is not getting updated.
> >
> >
> > Further added, in asterisk CLI while running command: cdr show status
> > getting results below;
> >
> > Call Detail Record (CDR) settings
> > ----------------------------------
> > Logging: Enabled
> > Mode: Simple
> > Log unanswered calls: No
> > Log congestion: No
> >
> > * Registered Backends
> > -------------------
> > cdr-syslog
> > Adaptive ODBC
> > cdr-custom
> > csv
> > radius
> >
> >
> > Please advise if I may missed any steps.
> >
> > --
> > Regards,
> >
> > Ahmed Munir Chohan
>
> I cannot advice you about steps you might have missed, probably none. To my
> experience, the documentation is not sufficient.
>
> I can tell you that freeradius can be run in debug mode: radiusd -X Do this
> and have a close look to the output.
>
> If you cannot find any attempt to connect to the freeradius server you need
> to have a close look to the asterisk log files as well. Figure out what is
> going wrong. There should be some clue.
>
> I don't understand the grant access settings. Figure out the user which is
> running asterisk and set the setting appropriately! I remember that I
> needed the following access setting:
>
> -rw-r----- 1 root asterisk /usr/local/etc/radiusclient-ng/servers
>
> So read access for asterisk to the servers file. This was not documented at
> all, but somehow logical, if you figured it out.
>
> --
> Met vriendelijke groeten,
> With kind regards,
> Mit freundlichen Gruessen,
> De jrus wah,
>
> Wiel
>
> *************************************
> W.K. Offermans
>
> Powered by ....
>
> (__)
> \\\'',)
> \/ \ ^
> .\._/_)
>
> www.FreeBSD.org
>
>
>
--
Regards,
Ahmed Munir Chohan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20160927/56316c72/attachment.html>
More information about the asterisk-users
mailing list