Do you know the actual location of where you are calling?
Approximately 35% of the active telephone numbers in North America have been ported. For those routing calls based on dialed digits, this means one-third of your calls are likely being misrouted. And that can be very costly — especially for businesses with high call volumes.
There’s a better way to optimize call routing for NANPA numbers. With thinQ LRN, you have an easy-to-access service for simple, accurate, and cost-effective routing:
Simple: Use SIP or REST API to send us a NANPA number, and we will give you the corresponding LRN to route the call. Whether the number is ported or not, you always pay the correct rate based on the true location of the number.
Accurate: Query extended LRN to view all available geographic information on the number, including state, residential code, and company name.
Cost-Effective: Reduce expenses with streamlined routing and no minimum commitments—you pay for what you need, not what the big carriers charge.
Take a Closer Look at Calls with thinQ LRN
thinQ LRN is everything you expect from an LRN solution, but more. It can be bundled with our other offerings or fit easily into your existing calling solution.
Our LRN includes:
- Standard or extended LRN results
- US and Canada coverage
- REST API
- SIP 302 Redirect
- TXT, JSON, XML formatting available
What is a Location Routing Number (LRN)?
A unique number that uses the format of a telephone number, but actually represents an entire telephone switch through which multiple telephone numbers are routed. The assignment of a location routing number to telephone numbers allows for local number portability. For example, when a number is dialed, the TO number is queried against the database to return the LRN, which allows for proper routing to the correct carrier. A number that has never been ported will not have an LRN and will be routed based on its NPA-NXX. If it has been ported, the database will return the LRN.