October 27, 2016

GCS uses the word “Dynamic” to describe their routing engine. What exactly do you mean by dynamic and how is it beneficial in the use of your product?

We define Dynamic Routing as follows: The ability to uniquely provide a suggested route list to the switch, on a call-by-call basis, that considers a wide variety of attributes including...

Destination phone number
Time of Call
Origination phone number
Cost to destination
Price to the originating party
Quality Requirements  (ALOC, ABR, ASR, PDD, NER, etc.)
Supplier Performance
Margin Requirements
Product Requirements
Routing Policy Rules (Percentage Based, Service Level Based, Product Based, Overrides, No Looping, No Arbitrage allowed, etc.)
Revenue Assurance Requirements (Credit, Pre-Pay, Off-set); Bi-Laterals coming soon
NP, MNP (3rd party database dipped calls)
Jurisdictional Requirements (Local, Intrastate, Interstate, International, Non-conforming); EU/NON-EU coming soon
Exception based rules & policy overrides
Personal Route Advance
Rate Changes from suppliers
Rate Changes to originators

All of this is done in real-time, at the time of each call, and considers all information available to the routing engine, (including the previous call(s), and any rate changes that may have taken place prior to the next call being processed).
  
So, that is our long winded definition of Dynamic Routing. A shorter way of describing it is Dynamic Routing is a policy engine that considers business and network policies and, on a call-by-call basis, provides a call route list that is unique for every call based on all available information at the time the call was received by the switch.
 

See ya, Ani