Abstract:
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.
Abstract:
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.
Abstract:
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.
Abstract:
A communication system, method, and components are described. Specifically, a communication system having the ability to facilitate a semi-attended transfer in SIP for an IP-Multimedia Subsystem (IMS) environment is disclosed. The semi-attended transfer is possible even though one or more Back-to-Back User Agents are positioned between users engaged in the semi-attended transfer.
Abstract:
Systems and methods are described for creating and managing Global Session Identifiers (GSIDs) for communication sessions. GSIDs provide a way to globally identify communication sessions including those communication sessions that have experienced one or more topology changes. The GSID may be considered a header itself or a value within a header and information contained within a GSID can be used to trace backwards through time to find the session segments that led up to (or exist concurrently to) a currently signaled session.
Abstract:
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.
Abstract:
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.
Abstract:
A communication system, method, and components are described. Specifically, a communication system having the ability to accommodate communication preferences for multiple users sharing a common line appearance is described. An application sequence can be determined and invoked based on communication preferences of the multiple users sharing a common line appearance.
Abstract:
An initial SIP message is sent to establish a first SIP communication session from a first SIP device. The initial SIP message is sent via a first of a plurality of session managers to a second SIP device. After receiving the initial SIP message at the second SIP device and before ending the first SIP communication session, either the first or second SIP device sends a second SIP message. The second SIP message is sent to the first of the plurality of session managers. Either the first or second SIP devices detects that a response SIP message to the sent second SIP message was not received within a defined time period. In response to detecting that the SIP response message was not received within the defined time period, either the first or second SIP device resends the second SIP message to a second one of the plurality of session managers.
Abstract:
Session Manager anti-looping creates a model that is an effective barrier to looping, efficiently identifying a loop condition by maintaining temporary individual call counters for header sets within temporal parameters and terminating the loop condition upon detection. The system provides an administrator with adjustable parameters for loop detection count and loop detection interval, thereby allowing protection against loop conditions, both inadvertent and intentional.