<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Times New Roman; font-size: 12pt; color: #000000'>I think it depends what you're planning on using it for. In my case, I wanted to use it for call traffic analysis (ex. calls volumes to NPAs, gateways, etc) and troubleshooting tools for our repair departments. I had developed a perl module for FreeRadius that would store the CDRs into a reporting and troubleshooting database which worked out fairly well. However, the licensing model that Broadsoft uses for the Radius interface isn't very "efficient" and has been a major problem for our deployment. It seems Broadsoft only anticipates customers using the Radius interface for enhanced call logging and billing and prices it around that which makes it an expensive feature to use solely for network analysis.<span><br><br>Other than the licensing issues, the interface works fairly well. It could use some better documentation on what the VSAs are, but most of that can be reverse engineered from the CSV accounting files since the column sequences line up with the VSA numbers.<br><br><div><div><div>-- <br>Jason Nesheim<br><div><div></div></div></div></div></div><br></span><br>----- Original Message -----<br>From: "David Hiers" <hiersd@gmail.com><br>To: VoiceOps@voiceops.org<br>Sent: Monday, February 22, 2010 6:30:04 AM<br>Subject: [VoiceOps] BW RADIUS CDR interface<br><br>All,<br>A quick question for the brain trust:<br><br>If you use the BW RADIUS CDR interface, are you happy with it?<br><br>Thanks,<br><br>David<br>_______________________________________________<br>VoiceOps mailing list<br>VoiceOps@voiceops.org<br>https://puck.nether.net/mailman/listinfo/voiceops<br></div></body></html>