Arrangement for retrieving recorded audio announcements from a messaging system for identification of a calling party

• US 6,940,954 B1
• Filed: 09/06/2002
• Issued: 09/06/2005
• Est. Priority Date: 09/06/2002
• Status: Expired due to Fees

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Toebes, John Albert
• Primary Examiner(s): Tsang, Fan
• Assistant Examiner(s): Sing, Simon P.
• Application Number:
  US10/235,724
• Time in Patent Office: 1,096 Days
• Field of Search: 379/88.11, 379/88.12, 379/88.17, 379/88.19, 379/142.06, 379/207.15, 379/373.04, 379/88.21, 379/88.2, 379/142.01, 379/142.04, 379/373.01, 455/415, 709/219
• US Class Current: 379/88.17
• CPC Class Codes: H04M 3/42051 where the notification is included in the ringing tone
• CPC Class Codes: H04M 3/42068 where the identifier is used to access a profile
• CPC Class Codes: H04M 3/4931 Directory assistance systems
• CPC Class Codes: H04M 7/006 Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP) , including next generation networks with a packet-switched transport layer H04L65/00 takes precedence; aspects not specific to the type of network H04M3/00; special services in those networks H04M3/42

Abstract

An IP-based subscriber endpoint, for example a VoIP telephony device or an IP telephony user agent, is configured for retrieving recorded audio caller information in response to receiving an incoming call that includes a calling party identifier. The IP-based subscriber endpoint, in response to receiving the calling party identifier, generates an IP-based query via an IP network to an identifiable server for identification of a source of the recorded audio caller information corresponding to the calling party identifier. The IP-based subscriber endpoint outputs a request to the source of the recorded audio caller information, and plays the recorded audio caller information in response to reception via the IP-based network. Hence, the IP-based subscriber endpoint is able to retrieve existing recorded audio caller information from servers configured for storing recorded names, eliminating the necessity for text to speech resources.

Claims

1. A method in an Internet Protocol (IP) based subscriber endpoint configured for receiving a telephony call for a called party and that includes a calling party identifier for identifying a corresponding calling party, the method including:

outputting an IP-based query, that includes the calling party identifier, to a directory server for subscriber information that identifies the calling party;

determining a stored location of a recorded audio announcement that audibly identifies the calling party based on the subscriber information;

retrieving via an IP connection the recorded audio announcement from the stored location; and

outputting the recorded audio announcement as an announcement of the telephony call for the called party.

2. The method of claim 1, wherein the IP-based query outputting step includes outputting the IP-based query, having the calling party identifier, to the directory server according to Lightweight Directory Access Protocol (LDAP).

3. The method of claim 2, wherein the determining step includes:

determining an IP address for a server configured for storing the recorded audio announcement, and an identifier recognizable by the server for retrieval of the recorded audio announcement;

sending a request, specifying the identifier, to the server at the corresponding IP address for the recorded audio announcement, according to a protocol executable by tide server; and

receiving the recorded audio announcement from the server.

4. The method of claim 3, wherein the sending step includes generating a prescribed command according to an Application Programming Interface (API) utilized by the server.

5. The method of claim 3, wherein the sending step includes specifying a calling party name as the identifier, the server being a subscriber directory.

6. The method of claim 2, wherein the determining step includes:

determining an IP address for a remote tangible medium configured for storing the recorded audio announcement, and a directory path that specifies the corresponding stored location;

generating a string that specifies an identity of the recorded audio announcement at the stored location on the remote tangible medium; and

outputting a request, that includes the IP address and the string, for retrieval of the recorded audio announcement from the remote tangible medium.

7. The method of claim 2, further comprising:

receiving from the directory server a redirect response that specifies a second directory server for retrieval of the subscriber information;

sending the IP-based query, that includes the calling party identifier, to the second directory server based on the redirect response; and

receiving the subscriber information from the second directory server.

8. The method of claim 7, wherein:

the receiving the subscriber information includes receiving the subscriber information via a wide area, packet switched IP-based network; and

the retrieving step includes retrieving the recorded audio announcement via the wide area, packet switched IP-based network.

9. The method of claim 2, wherein the subscriber endpoint is an IP telephony device, the outputting step including:

transcoding the recorded audio announcement to a native format announcement executable by a player within the IP telephony device, and

playing the native format announcement for the called party by the player.

10. The method of claim 2, wherein the subscriber endpoint is a proxy device in communication with a telephony device for the called party, the outputting step including:

transcoding the recorded audio announcement to a native format data stream executable by the telephony device; and

supplying the native format data stream to the telephony device according to a prescribed interface protocol used between the proxy device and the telephony device.

11. An Internet Protocol (IP) based subscriber endpoint device comprising:

an IP based interface configured for receiving a telephony call for a called party and that includes a calling party identifier for identifying a corresponding calling party;

a query resource configured for outputting an IP-based query, that includes the calling party identifier, to a directory server for subscriber information that identifies a calling party;

a file transfer resource configured for retrieving via an IP connection a recorded audio announcement, that audibly identifies the calling party, from a stored location determined based on the subscriber information; and

an output resource configured for outputting the recorded audio, announcement as an announcement of the telephony call for the called party.

12. The device of claim 11, wherein the query resource is configured for outputting the IP-based query, having the calling party identifier, to the directory server according to Lightweight Directory Access Protocol (LDAP).

13. The device of claim 12, wherein:

the IP based interface is configured for determining a server configured for storing the recorded audio announcement; and

the file transfer resource is configured for sending to the server a request, specifying at least a portion of the subscriber information, for the recorded audio announcement, according to a protocol executable by the server, and receiving the recorded audio announcement from the server.

14. The device of claim 13, wherein the file transfer resource is configured for sending the request by generating a prescribed command according to an Application Programming Interface (API) utilized by the server.

15. The device of claim 13, wherein the file transfer resource is configured for specifying a calling party name as the identifier, the server being a subscriber directory.

16. The device of claim 12, wherein:

the IP based interface is configured for determining a remote tangible medium configured for storing the recorded audio announcement; and

the file transfer resource is configured for generating a string that specifies an identity of the recorded audio announcement at the stored location on the remote tangible medium, and outputting to the remote tangible medium a request, that includes the string, for retrieval of the recorded audio announcement from the remote tangible medium.

17. The device of claim 12, wherein the query resource, in response to receiving from the directory server a redirect response that specifies a second directory server for retrieval of a locator, sends the IP-based query, that includes the calling party identifier, to the second directory server based on the redirect response, for reception of the locator from the second directory server.

18. The device of claim 17, wherein the query resource and the file transfer resource are configured for receiving the locator and the recorded audio announcement, respectively, via a wide area, packet switched IP-based network.

19. The device of claim 12, further comprising a player configured for playing an audio file according to a native format, the subscriber endpoint being implemented in an IP telephony device and the output resource configured for transcoding the recorded audio announcement to a native format announcement executable by the player within the IP telephony device.

20. The device of claim 12, wherein the subscriber endpoint is a proxy device in communication with a telephony device for the called party, the output resource configured for:

transcoding the recorded audio announcement to a native format data stream executable by the telephony device; and

supplying the native format data stream to the telephony device according to a prescribed interface protocol used between the proxy device and the telephony device.

21. A computer readable medium having stored thereon sequences of instructions for receiving an IP based telephony call for a called party and that includes a calling party identifier for identifying a corresponding calling party, the sequences of instructions including instructions for performing the steps of:

outputting an IP-based query, that includes the calling party identifier, to a directory server for subscriber information that identifies the calling party;

determining a stored location of a recorded audio announcement that audibly identifies the calling party based on the subscriber information;

retrieving via an IP connection the recorded audio announcement from the stored location; and

outputting the recorded audio announcement as an announcement of the telephony call for the called party.

22. The medium of claim 21, wherein the IP-based query outputting step includes outputting the IP-based query, having the calling party identifier, to the directory server according to Lightweight Directory Access Protocol (LDAP).

23. The medium of claim 22, wherein the determining step includes:

determining an IP address for a server configured for storing the recorded audio announcement, and an identifier recognizable by the server for retrieval of the recorded audio announcement;

sending a request, specifying the identifier, to the server at the corresponding IP address for the recorded audio announcement, according to a protocol executable by the server; and

receiving the recorded audio announcement from the server.

24. The medium of claim 23, wherein the sending step includes generating a prescribed command according to an Application Programming Interface (API) utilized by the server.

25. The medium of claim 23, wherein the sending step includes specifying a calling party name as the identifier, the server being a subscriber directory.

26. The medium of claim 22, wherein the determining step includes:

determining an IP address for a remote tangible medium configured for storing the recorded audio announcement, and a directory path that specifies the corresponding stored location;

generating a string that specifies an identity of the recorded audio announcement at the stored location on the remote tangible medium; and

outputting a request, that includes the IP address and the string, for retrieval of the recorded audio announcement from the remote tangible medium.

27. The medium of claim 22, further comprising instructions for performing the steps of:

receiving from the directory server a redirect response that specifies a second directory server for retrieval of the subscriber information;

sending the IP-based query, that includes the calling party identifier, to the second directory server based on the redirect response; and

receiving the subscriber information from the second directory server.

28. The medium of claim 27, wherein:

the receiving the subscriber information includes receiving the subscriber information via a wide area, packet switched IP-based network; and

the retrieving step includes retrieving the recorded audio announcement via the wide area, packet switched IP-based network.

29. The medium of claim 22, wherein the subscriber endpoint is an IP telephony device, the outputting step including:

transcoding the recorded audio announcement to a native format announcement executable by a player within the IP telephony device, and

playing the native format announcement for the called party by the player.

30. The medium of claim 22, wherein the subscriber endpoint is a proxy device in communication with a telephony device for the called party, the outputting step including:

transcoding the recorded audio announcement to a native format data stream executable by the telephony device; and

supplying the native format data stream to the telephony device according to a prescribed interface protocol used between the proxy device and the telephony device.

31. An Internet Protocol (IP) based subscriber endpoint device comprising:

means for outputting an IP-based query, that includes the calling party identifier, to a directory server for subscriber information that identifies the calling party;

means for determining a stored location of a recorded audio announcement that audibly identifies the calling party based on the subscriber information;

means for retrieving via an IP connection the recorded audio announcement from the stored location; and

means for outputting the recorded audio announcement as an announcement of the telephony call for the called party.

32. The device of claim 31, wherein the IP-based query outputting means is configured for outputting the IP-based query, having the calling party identifier, to the directory server according to Lightweight Directory Access Protocol (LDAP).

33. The device of claim 32, wherein the determining means is configured for determining an IP address for a server configured for storing the recorded audio announcement, and an identifier recognizable by the server for retrieval of the recorded audio announcement, the retrieving means configured for sending a request, specifying the identifier, to the server at the corresponding IP address for the recorded audio announcement, according to a protocol executable by the server, the retrieving means configured for receiving the recorded audio announcement from the server.

34. The device of claim 33, wherein the retrieving means is configured for generating a prescribed command according to an Application Programming Interface (API) utilized by the server.

35. The device of claim 33, wherein the retrieving means is configured for specifying a calling party name as the identifier, the server being a subscriber directory.

36. The device of claim 32, wherein:

the determining means is configured for determining an IP address for a remote tangible medium configured for storing the recorded audio announcement, and a directory path that specifies the corresponding stored location;

the retrieving means configured for generating a string that specifies an identity of the recorded audio announcement at the stored location on the remote tangible medium, and outputting a request, that includes the IP address and the string, for retrieval of the recorded audio announcement from the remote tangible medium.

37. The device of claim 32, wherein the IP-based query outputting means is configured for:

receiving from the directory server a redirect response that specifies a second directory server for retrieval of the subscriber information;

sending the IP-based query, that includes the calling party identifier, to the second directory server based on the redirect response; and

receiving the subscriber information from the second directory server.

38. The device of claim 37, wherein:

the IP-based query outputting means is configured for receiving the subscriber information via a wide area, packet switched IP-based network; and

the retrieving means is configured for retrieving the recorded audio announcement via the wide area, packet switched IP-based network.

39. The device of claim 32, wherein the subscriber endpoint is an IP telephony device, the outputting means configured for transcoding the recorded audio announcement to a native format announcement executable by a player within the IP telephony device, playing the native format announcement for the called party by the player.

40. The device of claim 32, wherein the subscriber endpoint is a proxy device in communication with a telephony device for the called party, the outputting step means configured for transcoding the recorded audio announcement to a native format data stream executable by the telephony device, supplying the native format data stream to the telephony device according to a prescribed interface protocol used between the proxy device and the telephony device.