Media application

• US 7,940,793 B2
• Filed: 04/24/2007
• Issued: 05/10/2011
• Est. Priority Date: 04/24/2007
• Status: Active Grant

• Current Assignee: Avaya LLC (Avaya Incorporated), Avaya Management L.P. (Avaya Incorporated)
• Original Assignee: Avaya Incorporated
• Inventors: Zilbershtein, Itai Ephraim, Perry, Zvika, Pdut, Yaron, Brunson, Gordon R.
• Primary Examiner(s): Lim; Krisna
• Application Number:
  US11/739,378
• Publication Number:
  US 20080270457A1
• Time in Patent Office: 1,477 Days
• Field of Search: 709/204, 379/93.08, 379/93.15, 379/100.13, 379/142.14, 370/466
• US Class Current: 370/466
• CPC Class Codes: H04L 65/1063 Application servers providing network services systems providing special services to telephonic subscribers H04M3/42
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/765 intermediate
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/18 Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
• CPC Class Codes: H04L 69/24 Negotiation of communication capabilities
• CPC Class Codes: H04M 3/533 Voice mail systems
• CPC Class Codes: H04M 7/0072 Speech codec negotiation H04L65/1069 takes precedence

Abstract

A media application server, comprising a network interface and a processor adapted to establish voice connections with opposite end devices and to perform on the connections at least one media application task for signals of a plurality of different signal formats, the processor being adapted to establish the connection in a negotiation procedure in which it advertises itself as supporting fewer than the plurality of signal formats.

Claims

1. A method comprising:

establishing a first voice connection between a first calling device and a first called device, wherein a server establishes the first voice connection using a first codec of a first type after identifying itself as supporting (i) only the first type of codec and (ii) no codec translation; and

establishing a second voice connection between a second calling device and a second called device, wherein the server establishes the second voice connection using a second codec of a second type after identifying itself as supporting (i) only the second type of codec and (ii) no codec translation;

wherein the first type of codec is associated with a first signal format, and

wherein the second type of codec is associated with a second signal format that is different than the first signal format, and

wherein, when each of the first voice connection and the second voice connection is to be established, identifying itself as supporting only one type of codec and no codec translation relieves the server of the burden of performing codec translation.

2. The method of claim 1, wherein the second voice connection is established after the first voice connection is terminated.

3. The method of claim 1, wherein the server comprises software that supports the first voice connection and the second voice connection.

4. The method of claim 1, wherein the first signal format is a compressed format and the second signal format is an uncompressed format.

5. The method of claim 1, wherein the first signal format is an encrypted format and the second signal format is an unencrypted format.

6. The method of claim 1, wherein the first voice connection comprises a voice mail application.

7. A method comprising:

receiving by a server a connection message from a first device seeking a first voice connection with a second device that is connected to the server;

responding to the first device with an indication that the server supports only a first type of codec;

establishing the first voice connection between the first device and the second device by using a first codec of the first type of codec;

receiving by the server a connection message from a third device seeking a second voice connection with a fourth device that is connected to the server;

responding to the third device with an indication that the server supports only a second type of codec; and

establishing the second voice connection between the third device and the fourth device by using a second codec of the second type of codec;

wherein the first type of codec is associated with a first signal format, and

wherein the second type of codec is associated with a second signal format that is different than the first signal format,

wherein, when the first voice connection is to be established, responding with the indication that the server supports only the first type of codec relieves the server of the burden of translating between the first signal format and a different signal format that is associated with the first device, and

wherein, when the second voice connection is be established, responding with the indication that the server supports only the second type of codec relieves the server of the burden of translating between the second signal format and a different signal format that is associated with the third device.