[VoiceOps] BW RADIUS CDR interface

[Aled Treharne]

On 22 February 2010 22:41, Mark Lindsey <lindsey at e-c-group.com> wrote:
> On 2/22/10 5:32 PM, Aled Treharne wrote:
>>
>> On 22 February 2010 22:23, Mark Lindsey<lindsey at e-c-group.com>  wrote:
>>
>>>
>>> Speaking of Dave's point about fraud analysis -- an advantage of watching
>>> the traffic in real-time is that you can do something about a suspicious
>>> call.  If the fraud analyzer is clever enough, it could accept the RADIUS
>>> accounting-start records and record the status of all active calls. Then
>>> if
>>> the call looks suspicious (a two-hour call to Jamaica from a customer who
>>> never places other International calls) then do an IDS-style teardown by
>>> killing the call with a spoofed BYE.
>>>
>>
>> No need to do it the dirty way - you can tear the call down with a
>> CAP/OCI-P call to the AS. Nice and clean. I've seen a pre-pay call
>> control application use this method to tear down the call when a user
>> reached their credit limit. Real-time rating.
>>
>
> That's true -- it's cleaner. But this means the system has to authenticate
> with the credentials of the BroadWorks user, right? If so, that's still
> possible, but I believe there are limitations on multiple concurrent CAP
> sessions.
>
> I know the BW AS has another interface for tearing down calls from an
> administrator level, but I don't think it's exposed through CAP.

It's been a while since I've looked at the call control interface in
any detail, but I think the application itself maintained a single
connection and communicated over that connection.

Cheers,
Aled.