Got Dynamic Routing?
Okay, so, if you’ve visited our website, read any of our literature, received any of our emails, or spoken to any of our sales teams or our customers, you probably know that we are the “Dynamic Routing” guys. It’s a description that fits us well. See, we believe that, without exception, in today’s voice marketplace carriers must have dynamic routing at the core of their voice networks. Next Gen routing capabilities that leverages all the software benefits of SDN networks, SIP networks and current best practice big data architecture is no longer a nice to have, it is a must have. We’ve been doing it since 2009 when we first launched our Dynamic Route Management Solution (dROM), and it flipped traditional Least Cost Routing (LCR) methods on its head.
Dynamic Routing is the technological evolution for voice routing that was bound to happen once VoIP was introduced in the late 1990s. If you are a voice services provider then you MUST employ a Dynamic Routing Solution. Let’s state that again…YOU MUST employ a Dynamic Routing Engine for your voice traffic. Dynamic Voice Routing Engines allow service providers to take into account an unlimited amount of information and determine the “right” way to route a call uniquely on every call. Think of the information as attributes of the call, items such as:
1) Cost for terminating the call
2) Price charged to the originator of the call
3) Time of Day of the call
4) Quality Requirements of the call
5) Type of Call (International, Domestic, Jurisdiction)
6) Does it need to be LNP/MNP dipped?
7) Do you have to check for Credit Risk?
8) Do you have to route it to a specific terminating supplier because of Revenue Assurance requirements?
9) Is it part of a Bi-Lateral?
10) Performance of Suppliers in route for the call. Are they performing up to the requirements?
11) Dialer Traffic?
12) Toll-Free Traffic?
13) Did you want to distribute the call to a different supplier?
14) Did you want to block a specific supplier?
15) Is there a Minimum Margin requirement for the call? What is it? Which suppliers meet it?
16) Is this a repeat call that just came in less than X seconds ago?
17) Is it to a destination you don’t want to terminate the call to?
18) Is it a retail call?
There are many attributes that you want to consider when determining how to route a call. These are just a few. But, what is clear about these attributes is that traditional Least Cost Routing methods can’t do any of this analysis on a call-by-call basis. They are static, stale rules that are applied generically to every call. That’s not how it should work in 2016. In 2016 you should be able to uniquely construct a routing plan for every call on a call-by-call basis that takes into account all attributes and all available network related data in real-time. That’s what Dynamic Routing is. That’s what GCS dROM does. That’s why you need it.
So…Got Dynamic Routing?