Abstract:
The system generates a change in the SIP INVITE message during a call transfer. Here, a user relation element involved in the call can change the header information in the message to include the endpoint view of the transferring party. Thus, the INVITE message is redirected to the transferring party's user relation element, which can interpret the received message and “unravel” the B2BUAs in the existing call path. The system includes changes in the user relation element to effect the message change and interpret the message once received. Changes to the user relation element forgo the need to change the communication endpoints.
Abstract:
A communication system, method, and components are described. Specifically, a communication system having one or more Back-to-Back User Agents (B2BUAs) therein is described. The communication system also includes an RFC 4579 conference focus. Mechanisms are described which enable User Agents (UAs) to subscribe to conference state events and create ad-hoc conferences even though the conference focus is operating in a B2BUA environment.
Abstract:
A communication system, method, and components are described. Specifically, a communication system having one or more Back-to-Back User Agents (B2BUAs) therein is described. The communication system also includes an RFC 4579 conference focus. Mechanisms are described which enable User Agents (UAs) to subscribe to conference state events and create ad-hoc conferences even though the conference focus is operating in a B2BUA environment.
Abstract:
The call states of all devices in a call are monitored and reported even when the devices belong to networks that use different types of call identifiers. A first device and a second device are different types of devices selected from a group of types comprising: a legacy device type, a SIP basic device type, and a SIP advanced device type. In response to a request from an application to monitor the first device and a request to establish a call between the first device and the second device, a Universal Call Identifier (UCID) is generated for the call and the call is established. A request to monitor the second device is sent using the UCID. When a change in the call state of the second device is detected, the change of the call state is reported to the application based on the UCID.
Abstract:
The call states of all devices in a call are monitored and reported even when the devices belong to networks that use different types of call identifiers. A first device and a second device are different types of devices selected from a group of types comprising: a legacy device type, a SIP basic device type, and a SIP advanced device type. In response to a request-from an application to monitor the first device and a request to establish a call between the first device and the second device, a Universal Call Identifier (UCID) is generated for the call and the call is established. A request to monitor the second device is sent using the UCID. When a change in the call state of the second device is detected, the change of the call state is reported to the application based on the UCID.
Abstract:
The system and method allow enhanced capabilities for Session Initiation Protocol (SIP) dialogs (communication sessions) between SIP devices. The SIP dialogs have applications that are inserted into the SIP dialog such as a Back-to-Back User Agent (B2BUA) or a proxy application. After the initial dialog is established and these applications fail or become unavailable, the system and method allow the applications to be bypassed or have the SIP dialog redirected to an alternative application. This provides a better user experience because the SIP dialog (e.g., a SIP telephone call) will not be dropped if the application fails mid-dialog.
Abstract:
A first message is received at a primary container that is replicated by a secondary container. The first message is an initial message to initiate a first session. The first message is processed by an application in the primary container. At a point in time, the primary container is unavailable and the system and method detect that the primary container is unavailable. A second message is received. The second message is associated with the first session. The second message is modified by moving at least a portion of a header in the second message into a different header in the second message and adding an additional header to the second message in response to the primary container being unavailable.
Abstract:
A first message is received at a primary container that is replicated by a secondary container. The first message is an initial message to initiate a first session. The first message is processed by an application in the primary container. At a point in time, the primary container is unavailable and the system and method detect that the primary container is unavailable. A second message is received. The second message is associated with the first session. The second message is modified by moving at least a portion of a header in the second message into a different header in the second message and adding an additional header to the second message in response to the primary container being unavailable.
Abstract:
In a distributed communications network without a central call-processing controller, such as a SIP-based network, an application server collects and reports call-processing events to a client application by dynamically subscribing to events on devices specified by the client application and other devices that enter into communication sessions with those specified devices, and dynamically unsubscribes to events on devices with which the communications sessions have ended.
Abstract:
The system generates a change in the SIP INVITE message during a call transfer. Here, a user relation element involved in the call can change the header information in the message to include the endpoint view of the transferring party. Thus, the INVITE message is redirected to the transferring party's user relation element, which can interpret the received message and “unravel” the B2BUAs in the existing call path. The system includes changes in the user relation element to effect the message change and interpret the message once received. Changes to the user relation element forgo the need to change the communication endpoints.