Editorial

Expensive Fraud Calls

Published on:

October 20, 2014

We have talked about it before, but reading the article I think it is important to point out some points that were not so clear before. The first one is that some carriers really seem to go after the money, even if they have to go to court. In contrast to the credit card industry, fraud is the responsibility of the customer, not the provider.

It happened again, and it would not be the last time: http://finance.yahoo.com/news/phone-hackers-dial-redial-steal-012343295.html another victim about phone call fraud, caused by a hacked PBX that was somehow accessible for the bad guys.

We have talked about it before, but reading the article I think it is important to point out some points that were not so clear before. The first one is that some carriers really seem to go after the money, even if they have to go to court. In contrast to the credit card industry, fraud is the responsibility of the customer, not the provider.

Then the next point is that it is obviously not necessary that the PBX actually received voice traffic from the public internet. Typically fraud uses the victims PBX as a kind of “least cost router” for terminating traffic into expensive countries. But when calling expensive 900 numbers like mentioned in the article, there is no need to have any traffic with the outside world. All it takes is that the PBX is using its route into the PSTN world.

In theory, a bot on a computer in the LAN can use the click to dial feature of the PBX to keep on dialing expensive numbers. The voice would end up somewhere either on the local PC or smart phone, or just on the phone on the office table. On the weekend when nobody is in the office it would take some time to figure out what is going on.

This is new. If a bot can access the local TAPI on the computer and initiate a call, you are in trouble. There is no extra password check between the TAPI client and the TAPI server. All it takes is a program running on the local PC that is starting to dial numbers.

So what are we learning from all of this?

Apart from the usual recommendations to check for viruses on your computer and make sure that users are choosing good passwords and PIN codes, you should check if your service provider has a fraud detection feature. This will limit the damage in case you should get hacked for whatever reason, despite all the precautions that you did on the system. If you are using prepaid accounts, the damage will be limited to the money that you have put into the meter.

By default, version 5 does not come with a CSTA license which is required for TAPI calls. If you have the license and are using TAPI, you can do a few measures that reduce the exposure to the risk. You can double check what numbers can be called from your PBX in the dial plan. In many cases it is not necessary that PBX users are dialing expensive hotlines, and if they do, you can set the flag in the dial plan that they have to enter their PIN code. And you can make sure that PCs are turned off when users are not in the office. This does not only make sure that you don’t have any surprises on your phone bill on Monday morning. It also saves power.

Derniers articles

Voir tous

Unlock the Power of OpenAI’s Realtime API with Vodia PBX: Join Our Exclusive Webinar!

Join our exclusive webinar to explore how Vodia PBX seamlessly integrates with OpenAI’s Realtime API, unlocking powerful new capabilities for your communication systems. This session will showcase how AI-driven features can streamline workflows, improve operational efficiency and elevate the PBX experience for both general users and those on Microsoft Teams. Whether you’re looking to stay ahead of the competition or leverage the latest AI trends, this webinar offers practical knowledge and actionable strategies. Register now to secure your spot and take the first step toward transforming your telecom infrastructure with AI innovation!

December 4, 2024

Connecting to OpenAI Realtime API

This document details the beta version of the Vodia PBX that connects to the OpenAI realtime API, enabling users to interact with a chatbot via telephone. The backend JavaScript code facilitates the connection, handling audio input and output, and the WebSocket connection to the OpenAI API. The setup requires a Vodia PBX version 69.5.3 or higher, an API key, and a license with an IVR node. The demo can be accessed by editing the ivrnode.js template and creating an IVR node in the tenant. The system supports various VoIP devices and offers good voice quality. Future improvements include voice activity detection and the ability to take actions based on OpenAI responses.

November 26, 2024

How Vodia Helps Hotels Not Disturb Their Guests

Vodia’s cloud PBX system enhances the Do-Not-Disturb (DND) function for hotels, allowing guests to manage their privacy through buttons in the room or on the phone. The system syncs with PMS for seamless functionality, enabling hotel operators to manually override DND when guests struggle to disable it. For critical situations, like room service follow-ups, the system allows specific extensions to bypass DND, ensuring guests are reachable when needed. VIP guest management features, guest-to-guest call restrictions and automatic resets upon checkout ensure privacy, security, and convenience, improving the guest experience while maintaining operational efficiency.

October 22, 2024