Call routing using domain name service and electronic number mapping

1. Non-transitory computer-readable media having computer-executable instructions embodied thereon that, when executed, enable a computing device to perform a method of routing mobile device calls based on a converted telephone number of a mobile device, location information of the mobile device, and trunk group identifiers, the method comprising:

generating a query requesting one or more routes for a mobile device call, the query comprises the converted telephone number of the mobile device and location information of the mobile device;

receiving one or more responses from a centralized routing function identifying, based at least in part on the location information in the query, the one or more routes for the mobile device call, the one or more responses each comprising an originating trunk group identifier, wherein the originating trunk group identifier includes an egress trunk group; and

upon receiving the one or more responses, routing the mobile device call using an egress trunk group of a response from the centralized routing function, wherein routing the mobile device call comprises:

accessing a table of a plurality of trunk groups, wherein the table contains references to a corresponding egress trunk group identifier for each of the plurality of trunk groups; and

identifying within the table of the plurality of trunk groups a matching trunk group, between a trunk group in the table and a trunk group in the response, for routing the mobile device call.

2. The media of claim 1 , wherein the converted telephone number is an Electronic Number Mapping ENUM Domain Name Service DNS telephone number which is converted to DNS Fully Qualified Domain Name FQDN from E.164 format.

3. The media of claim 1 , wherein the query is an ENUM DNS Name Authority Pointer NAPTR Resource Record (RR) query comprising an OPT RR, the OPT RR comprising location information selected from at least one of the following: a CallingPartyNumber, a Mobile Switching Center Identification (MSCID), a cell location, or a sector location.

4. The media of claim 1 , wherein each of the one or more responses further comprises a terminating trunk group identifier, wherein the terminating trunk group identifier comprises an egress trunk group for a next hop tandem switch.

5. The media of claim 4 , further comprising:

sending the terminating trunk group identifier to the next hop tandem switch, wherein the terminating trunk group identifier comprises an egress trunk group from the next hop tandem switch.

6. The media of claim 1 , wherein the one or more routes comprise SIP and legacy TDM routes.

7. The media of claim 6 , wherein the one or more routes are encoded in a URI generated by a Regular Expression replacement as virtual trunk group identifiers.

8. The media of claim 7 , wherein SIP based routes are presented using SIP URI and TDM based routes are presented using the SIP URI.

9. The media of claim 1 , wherein routing the mobile device call using an egress trunk group of a response from the centralized routing function further comprises:

issuing an alarm and processing another response when no matching trunk group exists between the trunk group in the table and the trunk group in the response; and

forwarding the mobile device call out of the matching trunk group based on NAPTR order and preference identified in the response, when the matching trunk group exists.

10. The media of claim 9 , wherein identifying within the table of the plurality of trunk groups the matching trunk group between the trunk group in the table and the trunk group in the response comprises comparing a locally configured trunk-context data object and a trunk-context of an egress trunk group in the response.

11. The media of claim 9 , wherein each of the plurality of trunk groups comprises a flag, wherein the flag signals whether to include trunk group information for a next hop switch.

12. The media of claim 11 , wherein the trunk group information for the next hop switch comprises user parameters in a SIP “CONTACT:” header.

13. Non-transitory computer-readable media having computer-executable instructions embodied thereon that, when executed, enable a computing device to perform a method of routing mobile device calls based on a converted telephone number of a mobile device, location information of the mobile device, and trunk group identifiers, the method comprising:

receiving a query requesting one or more routes for a mobile device call, the query comprises the converted telephone number of the mobile device and location information of the mobile device;

in response to the query, generating one or more responses identifying, the one or more routes for the mobile device call, the one or more responses each comprising an originating trunk group identifier, wherein the originating trunk group identifier includes an egress trunk group; and

communicating the one or more responses to an originating switch for routing the mobile device call, wherein routing the mobile device call comprises:

accessing a table of a plurality of trunk groups, wherein the table contains references to a corresponding egress trunk group identifier for each of the plurality of trunk groups; and

identifying within the table of the plurality of trunk groups a matching trunk group, between a trunk group in the table and a trunk group in a response, for routing the mobile device call.

14. The media of claim 13 , wherein each of the one or more routes in the one or more responses is based on location information of the mobile device.

15. The media of claim 13 , wherein each of the one or more routes in the one or more responses is further based on a least cost routing models of a wireless communication network associated with the mobile device.

16. The media of claim 14 , wherein the least cost routing models are based at least in part on network trunk audits and rates.

17. The media of claim 13 , wherein the one or more routes in the one or more responses further comprise routing from the originating switch to a next hop switch only, or routing from the originating switch to a tandem switch, and a terminal switch.

18. A system for routing mobile device calls based on a converted telephone number of a mobile device, location information of the mobile device, and trunk group identifiers, the system comprising:

an originating switch configured for:

generating a query requesting one or more routes for a mobile device call, the query comprises the converted telephone number of the mobile device and location information of the mobile device;

receiving one or more responses identifying, based at least in part on the location information in the query, the one or more routes for the mobile device call, the one or more responses each comprising an originating trunk group identifier, wherein the originating trunk group identifier includes an egress trunk group; and

upon receiving the one or more responses, routing the mobile device call using an egress trunk group of a response, wherein routing the mobile device call comprises:

accessing a table of a plurality of trunk groups, wherein the table contains references to a corresponding egress trunk group identifier for each of the plurality of trunk groups; and

identifying within the table of the plurality of trunk groups a matching trunk group, between a trunk group in the table and a trunk group in the response, for routing the mobile device call;

a centralized routing function configured for:

receiving the query requesting one or more routes for a mobile device call, the query comprises the converted telephone number of the mobile device and location information of the mobile device;

in response to the query, generating one or more responses identifying, based at least in part on the location information in the query, the one or more routes for the mobile device call, the one or more responses each comprising an originating trunk group identifier, wherein the originating trunk group identifier includes an egress trunk group;

communicating the one or more responses to the originating switch for routing the mobile device call.

19. The system of claim 18 , wherein the originating switch is further configured for:

issuing an originating switch alarm and processing another response when no matching trunk group for the originating switch exists between the trunk group in the table and the trunk group in the response; and

forwarding the mobile device call out of the matching trunk group based on NAPTR order and preference identified in the response, when the matching trunk group exists.

20. The system of claim 19 , further comprising a tandem switch, wherein the tandem switch is configured for:

receiving a request URI with a terminating trunk group from the originating switch, wherein the terminating trunk group identifier comprises an egress trunk group

accessing a tandem switch table of a plurality of trunk groups associated with a trunk group in the one or more responses, wherein the table contains references to the tandem switch corresponding egress trunk group identifier for each of the plurality of trunk groups;

identifying within the tandem switch table of the plurality of trunk groups a matching trunk group for the tandem switch between a trunk group in the table and a trunk group in a response;

issuing a tandem switch alarm and using a default process when no matching trunk group for the tandem switch exists between the trunk group in the table and the trunk group in a response; and

forwarding the mobile device call out of the matching trunk group based on NAPTR order and preference identified in the response, when the matching trunk group exists.