Toll Fraud Detection/Alerting.

Unanswered Question
Hythim Ali El Hadad Tue, 11/10/2009 - 12:05


It is solved completely in cucm 7.1 by logical partitioning

it prevent it at all

you can check it for more details

Jonathan Schulenberg Tue, 11/10/2009 - 16:56

Do you have documentation on how Geolocation and Logical Partition would solve this? Those features were originally intended to address country-specific laws, such as India, which require all off-net calls to cross the PSTN locally and not use TEHO. There are certainly other uses but nothing that I have seen which documents this particular scenario.

For toll fraud prevention: The current line/device combined CSS approach (see the UC Manager SRND) suggests that the line-level CSS include block patterns which prevent the user from dialing undesired destinations.

Within the context of CCX, Unity, or other UC applications, the CTI Port-level CSS should include these block partitions first to prevent it from being able to dial incorrect locations. Unity has additional methods for preventing this within the application. CCX does not provide a method for a user to get CCX to make an outbound call by default. The only way would be if you wrote a script that allowed a caller to specify the call transfer destination.

Depending on your deployment, you can also set UCM service parameters to prevent offnet-to-offnet transfers. That way an on-net user must remain involved in the call or UCM will drop it.

For toll fraud detection: Assuming that you have configured the CSS correctly for users/devices/applications, this should be largely preventable; however, your best method for seeing it is with call accounting software that parses UCM CDR records. Many of these products can show where calls are being made to. Just search the forum for suggestions. There are many threads that cover it.


This Discussion