Optimistic caching for address translations

1. A method to manage a call connection, comprising:

receiving a first identifier for a call;

retrieving a second identifier associated with said first identifier;

initiating a first call connection using said second identifier from a call terminal;

determining whether said second identifier is valid by requesting, by said call terminal, a third identifier from an Authoritative Directory (AD) server and comparing said second and third identifiers;

converting said first identifier into a fourth identifier;

sending said fourth identifier to said AD server; and

completing said call connection in accordance with said determination.

2. The method of claim 1 , wherein said first identifier comprises an E.164 number.

3. The method of claim 1 , wherein said second identifier comprises one of a telephone number, a network address, an Internet Protocol (IP) address, an electronic mail address, a facsimile number, a pager number, and a mobile telephone number.

4. The method of claim 1 , further comprising determining that said second identifier is valid if said second and third identifiers match.

5. The method of claim 4 , wherein said third identifier comprises one of a telephone number, a network address, an Internet Protocol (IP) address, an electronic mail address, a facsimile number, a pager number, and a mobile telephone number.

6. The method of claim 5 , wherein said fourth identifier is an ENUM Uniform Resource Identifier (URI).

7. The mcthod of claim 1 , wherein said completing comprises:

determining that said second identifier is invalid;

terminating said first call connection; and

initiating a second call connection using thc third identifier.

8. The method of claim 1 , wherein said retrieving comprises:

searching a cache using said first identifier; and

retrieving said second identifier from said cache.

9. The method of claim 1 , wherein said second identifier comprises an identifier from a Naming Authority Pointer (NAPTR) Domain Name System (DNS) resource record.

10. An article comprising:

a storage medium;

said storage medium including stored instructions that, when executed by a processor, result in managing a call connection by receiving a first identifier for a call, retrieving a second identifier associated with said first identifier, initiating a first call connection using said second identifier from a call terminal, determining whether said second identifier is valid by requesting, by said call terminal, a third identifier from an Authoritative Directory (AD) server and comparing said second and third identifiers, converting said first identifier into a fourth identifier, and sending said fourth identifier to said AD server, and completing said call connection in accordance with said determination.

11. The article of claim 10 , wherein the stored instructions, when executed by a processor, further result in determining that said second identifier is valid if said second and third identifiers match.

12. The article of claim 10 , wherein the stored instructions, when executed by a processor, further result in said completing by determining that said second identifier is invalid, terminating said first call connection, and initiating a second call connection using the third identifier.

13. The article of claim 10 , wherein the stored instructions, when executed by a processor, further result in said retrieving by searching a cache using said first identifier, and retrieving said second identifier from said cache.

14. A system, comprising:

a computing platform adapted to manage a call connection;

said platform being further adapted to receiving a first identifier for a call, retrieving a second identifier associated with said first identifier, initiating a first call connection using said second identifier from a call terminal, determining whether said second identifier is valid by requesting, by said call terminal, a third identifier from an Authoritative Directory (AD) server and comparing said second and third identifiers, converting said first identifier into a fourth identifier, and sending said fourth identifier to said AD server, and completing said call connection in accordance with said determination.

15. The system of claim 14 , wherein said platform is further adapted to determine that said second identifier is valid if said second and third identifiers match.

16. The system of claim 14 , wherein said platform is further adapted to perform said completing by determining that said second identifier is invalid, terminating said first call connection, and initiating a second call connection using the third identifier.

17. The system of claim 14 , wherein said platform is further adapted to perform said retrieving by searching a cache using said first identifier, and retrieving said second identifier from said cache.

18. A system to manage a call connection, comprising:

a call terminal to receive an E.164 number;

a Call Management Module (CMM) to retrieve an identifier associated with said E.1 64 number, initiate a first call connection using said identifier, convert the identifier, and send a request to validate said identifier;

an AD server to receive said request to validate said identifier, said AD server to compare said identifier with another identifier and send a message to said CMM to indicate whether said identifier is valid, with said CMM terminating said first call connection if said identifier is invalid.

19. The system of claim 18 , wherein said CMM initiates a second call connection if said identifier is invalid.

20. The system of claim 18 , wherein said CMM convcrts said identifier to an ENUM URI prior to validation by said AD server.