VoIP Mailing List Archives

[ahmedmunir007 at gmail...]

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

[asterisk at Offermans....]

Hello Ahmed,

On Fri, Sep 23, 2016 at 04:12:42PM -0400, Ahmed Munir wrote:

[ahmedmunir007 at gmail...]

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.

[andrew at ivins.id.au]

Hi Ahmed,

I ran into similar problems. freeradius-client returns the same error code for numerous failure cases, so Asterisk doesn't get an opportunity to log anything useful. If you look here:


https://github.com/FreeRADIUS/freeradius-client/blob/master/lib/buildreq.c



You'll see many instances where it returns ERROR_RC. You are almost certainly running into one of these. I ended up putting in print debug into that file and recompiling. I think in my case it was as simple as a hostname not resolving. Once you're not working blind, you'll find what is happening pretty quickly.


Andrew


On 28 September 2016 at 03:32, Ahmed Munir <ahmedmunir007@gmail.com (ahmedmunir007@gmail.com)> wrote:

[asterisk at Offermans....]

Hello Ahmed, Andrew, and asterisk friends,

Some time ago, I ran into similar problems as well I can confirm the
statement of Andrew: Turn on the logging facilities and you will find your
issue most likely. However, you need also a strategy. ``Radius client
testing'' as you mentioned, can mean anything. The point is, can asterisk
talk to the freeradius server via the client settings? To my opinion, this
is easy to test. Maybe the message: ``cdr_radius.c:208 radius_log: Unable
to create RADIUS record. CDR not recorded'' already implies that this is
not possible. I cannot judge it. You can by turning on radiusd -X and have
a close look to the output.

On Wed, Sep 28, 2016 at 07:59:13AM +0800, Andrew Ivins wrote:

[ahmedmunir007 at gmail...]

Hi Andrew and Willy,


Thanks for sharing the info.


As for enabling radius server debugging 'radiusd -X', made some test calls don't see the radiusclient sending data to radius server. However, using radtest or radiusclient testing, able to send data to radius server (after enabling debug).


For further testing, on my other server  using OpenSIPs, setup the radiusclient  and data was able to send over to radius server without any issue i.e. using same radiusclient config that I'm using for Asterisk radiusclient.


Btw, will try to work on Andrew advise and will update you if I make any progress.

[asterisk at Offermans....]

Hi Ahmed and asterisk friends,

So asterisk cannot contact the radius server.

The radiusclient __can__ contact the radius server.

Check in the asterisk log files why asterisk cannot contact the radius
server! Be also aware of the user, who is running the daemons. This user
might need read access to certain configuration files.

On Wed, Sep 28, 2016 at 01:24:58PM -0400, Ahmed Munir wrote:

[andrew at ivins.id.au]

You don't get anything in the Asterisk logs because freeradius-client (formerly radiusclient-ng) returns a single failure code for any failure when building a radius request.

Andrew


On 29 September 2016 at 15:55, Willy Offermans <asterisk@offermans.rompen.nl (asterisk@offermans.rompen.nl)> wrote:

[andrew at ivins.id.au]

You won't see anything in the Asterisk logs because there's nothing to log. The error happens in the freeradius-client library and returns an integer. On 29 Sep 2016 17:44, "Willem Offermans" <Willem@offermans.rompen.nl (Willem@offermans.rompen.nl)> wrote:

[ahmedmunir007 at gmail...]

Hi Willy & Andrew,


After doing alot of hits and tries, the issue found at the dictionary.digium at radius client end. For the solution, I used the dictionary.digium that comes with asterisk source file, restarted asterisk services and able to send CDR data over to radius server.


Thanks guys for your help.

On Thu, Sep 29, 2016 at 12:18 PM, Ahmed Munir <ahmedmunir007@gmail.com (ahmedmunir007@gmail.com)> wrote: