#Lync Question 24: How can I setup CDR for @Sonusnet SBC 1000/2000 for @MSFTLync

On of the licenses included with a Sonus SBC 1000/2000 is for CDR, which you can see in System / Licencing / Current Licenses

Firstly in order to get CDR working you need a RADIUS accounting server.

Originally this post was going show you how to install and configure RADIUS accounting using Windows Network Policy Server (NPS) in Windows Server 2012 however it would seem it is not compatible as I hit the following error.

A RADIUS message with the Code field set to 12, which is not valid, was received on port 1813 from RADIUS client <FQDN>. Valid values of the RADIUS Code field are documented in RFC 2865.

So I went back to the drawing board and when looking for a Free RADIUS server, enter FreeRADIUS which you can get here http://sourceforge.net/projects/freeradius/

So If we run through the installing

After installing you should download NOTEPAD2 which is more compatible than Windows NotePad for Unix formatted files with linefeeds.

Next you will need to download the RADIUS dictionary file from the Sonus website, then add the dictionary.net file to C:\FreeRADIUS\etc\raddb\dictionaries folder

Then edit the dictionary file in the C:\FreeRADIUS\etc\raddb\dictionaries folder with NOTEPAD2 and add a line to include dictionary.net  this is required to translate the vendor-177 attributes and binary values, otherwise you won’t know what is what.

Next you need to add/authorise a RADIUS client for each Sonus SBC.

Edit the C:\FreeRADIUS\etc\raddb\clients.conf file with NOTEPAD2 and at the bottom we need to define Sonus SBC, using the following example

client SONUSSBC01 {
  ipaddr = 10.2.10.131
  secret = radiussecret
}

After that you can start the FreeRADIUS Server, from the start menu.

Then in the Sonus WebUI, within Auth and Directory Services / RADIUS / RADIUS Servers click on the green plus in the middle

If we define the IP/FQDN of the RADIUS server, do note that RADIUS Accounting is on port 1813 and our defined RADIUS secret from before.

Then in Auth and Directory Services / RADIUS / Configuration under RADIUS Accounting Server to use our defined RADIUS server

If all is good on the Sonus in Auth and Directory Services / RADIUS / RADIUS Servers then server connectivity should show as Up.  To test make a call via your SONUS.

Within the C:\FreeRADIUS\var\log\radius\radacct folder you should see a folder for the IP address of your SONUS SBC and within that folder is a logfile (one created each day)

And if I look at a call report, here is a snippet.

Not very pretty….but as a wise Exchange man says to me “Lync is just numbers”

REFERENCES:

Radius Code 12 Unsupported
http://windowsarchitecture.wordpress.com/2010/11/02/radius-code-12-unsupported/

NOTEPAD2
http://www.flos-freeware.ch/notepad2.html