[VoiceOps] BW RADIUS CDR interface
hiersd at gmail.com
Mon Feb 22 15:17:44 EST 2010
Thanks for the info....
On Mon, Feb 22, 2010 at 11:27 AM, Jason L. Nesheim <jnesheim at cytek.biz> wrote:
> 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.
> 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.
> Jason Nesheim
> ----- Original Message -----
> From: "David Hiers" <hiersd at gmail.com>
> To: VoiceOps at voiceops.org
> Sent: Monday, February 22, 2010 6:30:04 AM
> Subject: [VoiceOps] BW RADIUS CDR interface
> A quick question for the brain trust:
> If you use the BW RADIUS CDR interface, are you happy with it?
> VoiceOps mailing list
> VoiceOps at voiceops.org
More information about the VoiceOps