Dialer traffic...is there anyway to handle this?

Wow. That is an awesome question. These days dialer traffic seems like the only portion of the voice business that is showing signs of healthy growth and thanks to the U.S. presidential elections, it grows ten fold during the election years. So, of course there is a way to handle dialer traffic - let me be clear, carriers don’t want dialer traffic, but they take it. They take it because they have this network asset that is only partially utilized, and if they can improve the utility of that asset by taking dialer traffic, they will. But they will only do so if they can control it and of course, they can’t control it proactively. They can only control it after they discover it. But, by then, they may have interfered with their normal operations and then that may be too late.

How do I suggest handling dialer traffic? It’s not rocket science, but it isn’t the easiest thing to do. The solution to the dialer traffic management problem is intelligent blending. Intelligent blending is the ability for the interconnect voice management platform to blend in conversational traffic with dialer traffic, so that it doesn’t exceed the thresholds that the terminating networks place on it . Remember, carriers don’t want dialer traffic on their network, but if they can’t get anything, they’ll take some dialer traffic so long as it doesn’t disrupt their normal conversational business. The way to do that is to take calls of conversational traffic and blend them with dialer originated traffic in a mix such as 80/20 conversational to dialer, or something like that, so that the carrier can take a portion of the dialer traffic without disrupting their conversational operations. This blending requires a sophisticated routing engine (can’t be done with static file Least Cost Routing), and must include a feedback loop to ensure that the thresholds are being managed actively and performance is tracked in real-time. So, if you can blend, you can handle dialer traffic.

Adios Amigo — Ani