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: Embodiments of the disclosure are directed to a call reconstruction server. This server can act as a signaling anchor for various SIP UAs involved in the session and can be included in the signaling path between UAs. More specifically, the reconstruction server can insert an identifier such as a Uniform Resource Identifier (URI) into the headers of SIP signaling messages exchanged between UAs during initiation of a session such as a call or conference. These identifiers can be used to insert the reconstruction servers into the path of the session in a way that “bookends” the other servers and/or processes in the session between the UAs. When one of these servers and/or processes restarts, the reconstruction servers can initiate a reconstruction process that rebuilds the session without relying on specially adapted UAs.

Abstract: During a Session Initiation Protocol dialog setup, the user agent sends an INVITE message with an SDP offer to the conference controller, and the conference controller provides to a media gateway a unique session identifier, a unique conference identifier, and optionally at least one of feature information and/or policy information. If the conference controller restarts, the media gateway may provide the conference controller the unique session identifier, the unique conference identifier, and the optional feature and/or policy information. The conference controller may then generate an out-of-dialog SIP REFER message that includes the unique session identifier and the unique conference identifier and provide the message to the user agent.

Abstract: Embodiments of the disclosure are directed to a call reconstruction server. This server can act as a signaling anchor for various SIP UAs involved in the session and can be included in the signaling path between UAs. More specifically, the reconstruction server can insert an identifier such as a Uniform Resource Identifier (URI) into the headers of SIP signaling messages exchanged between UAs during initiation of a session such as a call or conference. These identifiers can be used to insert the reconstruction servers into the path of the session in a way that “bookends” the other servers and/or processes in the session between the UAs. When one of these servers and/or processes restarts, the reconstruction servers can initiate a reconstruction process that rebuilds the session without relying on specially adapted UAs.

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: During a Session Initiation Protocol dialog setup, the user agent sends an INVITE message with an SDP offer to the conference controller, and the conference controller provides to a media gateway a unique session identifier, a unique conference identifier, and optionally at least one of feature information and/or policy information. If the conference controller restarts, the media gateway may provide the conference controller the unique session identifier, the unique conference identifier, and the optional feature and/or policy information. The conference controller may then generate an out-of-dialog SIP REFER message that includes the unique session identifier and the unique conference identifier and provide the message to the user agent.

Abstract: A Session Initiation Protocol (SIP) session dialog is established between a first user agent and a second user agent. The SIP server receives an in-dialog message for the SIP session dialog. At this point, the SIP server is no longer aware of the SIP session dialog, for example, because the SIP server was rebooted. In response to receiving the in-dialog message, the SIP server sends a request not found message to the first user agent that comprises a server accessible value. The SIP server receives an out-of-dialog SIP REFER message. The out-of-dialog SIP REFER message comprises call state information for the SIP session dialog and is sent based on the server accessible value. The SIP server sends the out-of-dialog SIP REFER message to the second user agent. The SIP session dialog is reestablished. The SIP server can be a SIP proxy server or a Back-to-Back User Agent.

Abstract: Embodiments provide caller information in multiple languages to multiple receiving communication devices. In one embodiment, the method includes receiving a call request from a sending endpoint communication device connected to a network. Caller identification information associated with the call request is obtained, where the caller identification information includes one or more identifications associated with the sending endpoint communication device. Each identification specifies the same content in a different language. The call request and at least one of the identifications are transmitted over the network to be received by receiving endpoint communication devices connected to the network. Each receiving endpoint communication device can output at least one of the received identifications specified in a language designated for use by that receiving endpoint communication device.

Abstract: A Session Initiation Protocol (SIP) session dialog is established between a first user agent and a second user agent. The SIP server receives an in-dialog message for the SIP session dialog. At this point, the SIP server is no longer aware of the SIP session dialog, for example, because the SIP server was rebooted. In response to receiving the in-dialog message, the SIP server sends a request not found message to the first user agent that comprises a server accessible value. The SIP server receives an out-of-dialog SIP REFER message. The out-of-dialog SIP REFER message comprises call state information for the SIP session dialog and is sent based on the server accessible value. The SIP server sends the out-of-dialog SIP REFER message to the second user agent. The SIP session dialog is reestablished. The SIP server can be a SIP proxy server or a Back-to-Back User Agent.

Abstract: Embodiments provide caller information in multiple languages to multiple receiving communication devices. In one embodiment, the method includes receiving a call request from a sending endpoint communication device connected to a network. Caller identification information associated with the call request is obtained, where the caller identification information includes one or more identifications associated with the sending endpoint communication device. Each identification specifies the same content in a different language. The call request and at least one of the identifications are transmitted over the network to be received by receiving endpoint communication devices connected to the network. Each receiving endpoint communication device can output at least one of the received identifications specified in a language designated for use by that receiving endpoint communication device.