Abstract: Communications over a network, such as electronic conferences, often have a small portion of content that is notable within the entirety of the communications. By automatically identifying and preserving such notable portions, the relevant “nugget” from the communications may be maintained without requiring preserving the entirety of the communications. Preservation may comprise converting the notable portion to a non-fungible token and adding the token to a blockchain wherein it may be exchanged by the owner to an interested party.

Abstract: Office noise is common. However, a particular individual may be unaware of the impact their volume of speech is having on others within the same work environment. A user of a communication device may be conducting a call and speaking with sufficient volume to be problematic for others. Accordingly, sound levels are monitored by dedicated and/or otherwise unused sound meters (e.g., microphones) and when a user is speaking sufficiently loudly, a mitigation action is taken to reduce the noise level to a more acceptable level.

Abstract: Working from home is becoming more and more commonplace. Ensuring that remote workers are following prescribed data protection measures becomes more important, and challenging. Safe and Secure Remote Working Environment (SSRWE) monitors an environment and determines if a non-compliant element is present. For example, a condition of working from home may be that no notetaking or electronic devices, especially ones comprising a camera, be visible to a system camera capturing the field of view in front of a display. If a non-compliant situation is discovered, the display may be redacted and/or other action taken to protect sensitive information.

Abstract: Users of a networked communication device may omit updating their availability state, and that of an associated communication device, if the state change is sudden or believed to be of sufficiently short duration. By quickly changing their state, a routing component may more accurately know whether or not a communication routed to the communication device will or will not be answered. By utilizing a camera and gesture processing logic, a user may naturally and quickly update their state without the need to navigate menus or select options with manual, tactile interactions with the communication device.

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: Methods and systems provided herein ensure that communication sessions such as phone calls over PSTNs can be reconstructed in the event that the session ends unintentionally. Methods and systems include detecting a call ended, analyzing data associated with the call, determining, based on the data, the call ended unintentionally, and reconstructing the call based on the determination the call ended unintentionally.

Abstract: Users of a networked communication device may omit updating their availability state, and that of an associated communication device, if the state change is sudden or believed to be of sufficiently short duration. By quickly changing their state, a routing component may more accurately know whether or not a communication routed to the communication device will or will not be answered. By utilizing a camera and gesture processing logic, a user may naturally and quickly update their state without the need to navigate menus or select options with manual, tactile interactions with the communication device.

Abstract: Working from home is becoming more and more commonplace. Ensuring that remote workers are following prescribed data protection measures becomes more important, and challenging. Safe and Secure Remote Working Environment (SSRWE) monitors an environment and determines if a non-compliant element is present. For example, a condition of working from home may be that no notetaking or electronic devices, especially ones comprising a camera, be visible to a system camera capturing the field of view in front of a display. If a non-compliant situation is discovered, the display may be redacted and/or other action taken to protect sensitive information.

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 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 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: 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: 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.

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 method, server, and communication system are described that, among other things, enable a server in a server cluster to assume control of any “early” Session Initiation Protocol (SIP) dialogs previously handled by another server in the server cluster when that server fails or otherwise becomes unable to continue handling a communication session. The replacement server in the server cluster is able to generate one or more messages that include an identification of the dialog identifiers used by the now failed server as well as new dialog identifiers to replace the dialog identifiers used by the now failed server.

Abstract: A fingerprint is received from a communication endpoint. The fingerprint is based on a hardware identifier of the communication endpoint. For example the fingerprint may be based on a Media Access Control (MAC) address of the communication endpoint. A request for an emergency call from the communication endpoint is received that also includes the fingerprint. For instance, a user may initiate a 911 call from the communication endpoint. The emergency call is established. After the emergency call is disconnected, a request for an emergency call back is received. For example, if the emergency call prematurely disconnected, the emergency call back is initiated. The request for the emergency call back is routed to the communication endpoint based on the fingerprint to ensure that the emergency call is properly completed.

Abstract: A communication system, method, and components are described. Specifically, a communication system having the ability to carry a transitive context and communicate the transitive context to new participant user agents for continuity through all related call dialogs is disclosed. The transitive context communication is possible through the use of a newly created SIP dialog using a REFER message and/or an INVITE message for all call flows and topology change operations.

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: 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.