Avaya Inc.

Tibor Lukac

Harsh V Mendiratta

Stephen Andrew Baker

Gordon Richards Brunson

Puneet Kumar

Joel M Ezell

Chandra Mouli Ravipati

Srinivasan Narayanan

Eric Cooper

Sreekanth Subrahmanya Nemani

Mohan Vinayak Phadnis

Sanjog Kotnis

Anand Padhye

Chandra Ravipati

In an attempt to establish a communication session between a first communication entity and a second communication entity, a first message is received. For example, the first message may be a SIP INVITE message. A determination is made, based on a registration message from the first communication entity and/or the second communication entity, that at least one of the first communication entity or the second communication entity is Internet Protocol (IP) version intolerant. In response to determining that the at least one of the first communication entity or the second communication entity is IP version intolerant, one or more IP addresses are adapted in messages (e.g., the SIP INVITE message) for establishing the communication session. The adaption changes/removes the one or more IP addresses to a different IP version to ensure proper IP compatibility.

IP tolerance and signaling interworking

A request to establish a communication session with a second communication device is received. The request to establish the communication session comprises one or more routing attributes for routing the communication session. The one or more routing attributes for routing the communication session are looked up in a dynamic routing framework. The communication session is routed to a third communication device or destination instead of the second communication device based on the one or more routing attributes and one or more rules defined in the dynamic routing framework. For example, the communication session is routed to a specific contact center queue based on the routing attribute instead of initially being routed to an Interactive Voice Response (IVR) system.

System and method for flexible routing

A communication session is established between a first communication device and a second communication device. The communication session comprises a first dialog between an application server and the first communication device. The first communication device uses a first network address in the first dialog. In response to an event, such as a first network interface failing, a SIP INVITE with replaces header message is received by the application server with a second address of the first communication device. In response to receiving the SIP INVITE with replaces header message from the first communication device with a second address of the first communication device, the first dialog between the application server and the first device is reestablished using the second network address.

Reestablishment of session initiation protocol (SIP) dialogs

To deal with ANAT/IP version incompatibility, a communication endpoint registers with a communication system using a SIP REGISTER message. For example, the communication endpoint registers when it boots up. The SIP REGISTER message indicates that the communication endpoint: does not support the Alternative Network Address Type (ANAT) protocol or is one of IPV4 intolerant or IPV6 intolerant. When a SIP INVITE message is received with a Session Description Protocol (SDP) offer that comprises the ANAT protocol or an IP address that is opposite of the IP version intolerance of the communication endpoint, a 4XX SIP response message is sent to the sender of the SIP INVITE to indicate the incompatibility. In response, to receiving the 4XX SIP response message, the SIP INVITE is modified to be compatible with the capabilities of the communication endpoint.

Alternative network address type (ANAT) encoding and media interworking

In response to a failure of a SIP dialog between a first communication endpoint and a first communication application (i.e., when a session manager fails), a first Session Initiation Protocol (SIP) INVITE with replaces header message received from the first communication endpoint. The first SIP INVITE with replaces header message comprises a Session Description Protocol (SDP) offer and a first request Universal Resource Identifier (URI) that identifies the first communication application. In response to receiving the first SIP INVITE with replaces header message, a second SIP INVITE with replaces header message is sent to a second communication application. The second SIP INVITE with replaces header message is used to reestablish all the SIP failed dialogs in order to reestablish the original communication session and reestablish the original media stream.

Call preservation for multiple legs of a call when a primary session manager fails

To reestablish a media stream, first and second SIP INVITE with replaces header messages are received by an application from a first and second communication endpoint respectively. The SIP INVITE with replaces header messages comprises a first Session Description Protocol (SDP) offer that are each based a change of a network address used by the respective communication endpoint. In response to receiving one or both of the SIP INVITE with replaces header messages, the application, depending on implementation, sends one of a first SIP 200 OK message with a fabricated SDP answer or sends a SIP 480 temporarily unavailable message that does not comprise a SDP offer. This initiates the process of reestablishing the media stream on new network without dropping the communication session.

Session initiation protocol call preservation based on a network failure

A request for a communication session is received by a system. For example, a request to establish a voice communication session is received by the system. The system determines whether the request for the communication session is to be forked to a plurality of communication endpoints. If the communication session is to be forked, a highest bandwidth requirement for the forked communication session is determined. The determined highest bandwidth requirement for the forked communication session is based on a highest bandwidth requirement of one or more codecs that are defined in the received request for the communication session. The determined highest bandwidth requirement for the forked communication session is allocated so that the forked communication session can be established.

System and method for efficient bandwidth allocation for forked communication sessions

A communication processor receives a call request to establish a communication session from a first communication endpoint to a second communication endpoint. The communication processor changes the intent of the call request. For example, the call request can be changed by automatically forwarding the call request, automatically forking the call request, automatically rejecting the call request based on the second communication endpoint being busy, and/or changing a first type of medium of the communication session to a second type of medium of the communication session. A call log manager conveys status information regarding the changed intent of the call to a call log of the second communication endpoint based on changing the intent of the call request.

Communication endpoint call log notification

Methods, devices, and systems for smart load balancing are provided. SIP Requests destined for a particular AOR are delivered to one of several registered contact addresses according to associated availability score stored in routing element's contact resolution table. The availability score is periodically updated by the contact entity itself using the SIP PUBLISH mechanism to push the score to the routing element.

Smart load balancing for call center applications

Methods, devices, and systems are provided for taking a pluggable extension and applying it to a unique set of a user population to handle their preferred and user-centric alerting relationships. More particularly, the pluggable extension allows a user to have their personalized contact resolution algorithm applied by a server to calls initiated by them or directed toward. The contact resolution algorithm is pluggable to any server and does not need to be built into the server itself. Moreover, multiple users can refer to and use the same pluggable contact resolution algorithm.

Pluggable contact resolution

A method, apparatus and computer program product for performing distributed conferencing is presented. A Public Branch Exchange (PBX) receives a plurality of calls intended for a conference bridge from a plurality of conference participants. The plurality of conference participants is conferenced together at the PBX. The plurality of conference participants is connected to the conference bridge by way of a single connection from the PBX to the conference bridge.

Growing community of inventors

Superior, CO, United States of America

Tibor Lukac