Abstract: A system and a method for providing resiliency in a telephony communication system are provided. The method includes: receiving registration information that relates to a requested service, the registration information including a service name, a resource identifier such as a directory number, at least one pool, and status information; and mapping the received registration information to a database that associates the name of the requested service with the resource identifier and each pool and associates each pool with the status information; and transmitting at least two Uniform Resource Locators (URLs), including a primary URL and a backup URL, for providing the requested service.

Abstract: A system and a method for routing a message to an application over a connection oriented session in a Kafka messaging platform environment are provided. The method includes: acquiring a plurality of partitions from the Kafka messaging platform; designating a first partition from among the plurality of partitions as a sticky partition; generating a plurality of routing keys that are configured to route to the sticky partition; receiving a subscription from a service that corresponds to a first application; transmitting, to the first application, a first routing key that identifies the subscription from among the plurality of routing keys; and receiving messages from Kafka services that are routed by the first routing key to the first application. For any particular application or set of applications, a plurality of connection oriented sessions may be used to achieve load balancing and high availability.

Abstract: A system and a method for overcoming a partial failure of an application in a telephony communication system are provided. The method includes: receiving information indicating that a first application has experienced a partial failure; receiving, from each of a plurality of applications, metadata that relates to a corresponding ordered priority of partitions, a corresponding Availability Zone from among a plurality of Availability Zones in which the respective application is located, and a corresponding instance index within the corresponding Availability Zone; sorting the received metadata with respect to the corresponding Availability Zone and with respect to the corresponding instance index; and reassigning, based on a result of the sorting, the first application to an instance index within the Availability Zone in which the first application is located such that a number of the partitions within instance indexes in the corresponding Availability Zone is balanced.

Abstract: A system and a method for servicing user interactions are provided. The method includes: receiving, from each respective user, a respective request for a corresponding interaction; obtaining, for each interaction, request-specific information that relates to the received respective request and user-specific information that relates to the respective user; analyzing the request-specific information to determine at least one corresponding microservice that is usable for handling the interaction; and routing the request-specific information and the user-specific information to a respective destination that relates to the determined microservice. For any particular interaction, several corresponding microservices and several corresponding routes and destinations may be determined, and workload distribution metrics may be used to select optimum routes.

Abstract: A system and a method for managing contact center functionality are provided. The method includes: receiving, from a servicing application, a request for a web application that implements a plurality of contact center functions; integrating the web application into the servicing application; and displaying a ribbon that includes information that relates to each of the plurality of contact center functions. The ribbon may be embeddable in a user interface screen of the servicing application.

Abstract: A registration is received from an application framework. The registration is for the application framework to be notified of an event managed by a service gateway. The event is based on a communication service provided by the service gateway. The service gateway detects the event. The service gateway sends a notification associated with the event to the application framework. The notification associated with the event comprises information associated with the event. For example, the notification may include a caller's name and address. An object is received from the application framework that is associated with the event. The object associated with the event further comprises extension information that is not used by the communication service/service gateway. A message is sent to a communication endpoint and/or an external application that comprises the object. The extension information is used to provide custom services that are not supported by the communication service/service gateway.

Abstract: Negotiation of a future communication through a personal virtual assistant is provided. A trigger command is received. The trigger command identifies a communication received for a recipient from a sender. Schedule information is accessed. The schedule information is related to the recipient of the received communication. A plurality of options is presented to the sender. The plurality of options are for arranging a future communication between the sender and the recipient, and include at least one option determined based on the accessed schedule information. A selection of an option for arranging a future communication is received. The selected option is executed to arrange the future communication.

Abstract: First communication information is received from a first communication session in a first communication medium. The first information has an associated first topic identifier. The first communication information may be a media stream, such as a voice media stream. Second communication information is received from a second communication session in a second communication medium associated with the first topic identifier. The first and second communication mediums are different communication mediums. The second communication session occurs after the first communication session has ended. For example, the second communication medium may be an email that occurs after a voice call has completed. The first information and the second information are stored in a first topic record based on the first topic identifier. A user can then access the topic record to view the first and second communication information for the topic.

Abstract: A device and method temporally correlates communication types. The method performed by a first electronic device includes receiving a first message in a first communication format from a second electronic device, the first message having first metadata associated therewith. The method includes determining respective second metadata associated with existing conversations. The existing conversations each include a plurality of existing messages in at least one second communication format. The existing messages are a thread in a temporal order. The existing conversations are shown in a single, respective user interface. The method includes determining a correlation between the first message and one of the existing conversations based upon the first and second metadata. The method includes inserting the first message in the existing messages of the one of the existing conversations that maintains the temporal order.

Abstract: A registration is received from an application framework. The registration is for the application framework to be notified of an event managed by a service gateway. The event is based on a communication service provided by the service gateway. The service gateway detects the event. The service gateway sends a notification associated with the event to the application framework. The notification associated with the event comprises information associated with the event. For example, the notification may include a caller's name and address. An object is received from the application framework that is associated with the event. The object associated with the event further comprises extension information that is not used by the communication service/service gateway. A message is sent to a communication endpoint and/or an external application that comprises the object. The extension information is used to provide custom services that are not supported by the communication service/service gateway.

Abstract: Negotiation of a future communication through a personal virtual assistant is provided. A trigger command is received. The trigger command identifies a communication received for a recipient from a sender. Schedule information is accessed. The schedule information is related to the recipient of the received communication. A plurality of options is presented to the sender. The plurality of options are for arranging a future communication between the sender and the recipient, and include at least one option determined based on the accessed schedule information. A selection of an option for arranging a future communication is received. The selected option is executed to arrange the future communication.

Abstract: First communication information is received from a first communication session in a first communication medium. The first information has an associated first topic identifier. The first communication information may be a media stream, such as a voice media stream. Second communication information is received from a second communication session in a second communication medium associated with the first topic identifier. The first and second communication mediums are different communication mediums. The second communication session occurs after the first communication session has ended. For example, the second communication medium may be an email that occurs after a voice call has completed. The first information and the second information are stored in a first topic record based on the first topic identifier. A user can then access the topic record to view the first and second communication information for the topic.

Abstract: Negotiation of a future communication through a personal virtual assistant is provided. A trigger command is received. The trigger command identifies a communication received for a recipient from a sender. Schedule information is accessed. The schedule information is related to the recipient of the received communication. A plurality of options is presented to the sender. The plurality of options are for arranging a future communication between the sender and the recipient, and include at least one option determined based on the accessed schedule information. A selection of an option for arranging a future communication is received. The selected option is executed to arrange the future communication.

Abstract: Disclosed herein are systems, methods, and non-transitory computer-readable storage media for implementing, via a communication device, a set of algorithms to learn about user's usage of the device and provide automated customization to the device's user interface to improve ease of use and productivity of the end-user. This approach does not require the user's involvement by manually customizing the user interface, such as by setting up a speed dial list or a screen layout. The system automates rendering decisions and the content that is rendered based on the usage information. For example, if a user consistently calls a number every Tuesday and Wednesday morning regardless of scheduled calendar information, the communication device can provide a dynamic widget in the user interface for easy access to that number every Tuesday and Wednesday morning. The user can dial the number easily via the widget without the dial pad or a contacts application.

Abstract: A device and method temporally correlates communication types. The method performed by a first electronic device includes receiving a first message in a first communication format from a second electronic device, the first message having first metadata associated therewith. The method includes determining respective second metadata associated with existing conversations. The existing conversations each include a plurality of existing messages in at least one second communication format. The existing messages are a thread in a temporal order. The existing conversations are shown in a single, respective user interface. The method includes determining a correlation between the first message and one of the existing conversations based upon the first and second metadata. The method includes inserting the first message in the existing messages of the one of the existing conversations that maintains the temporal order.

Abstract: Disclosed herein are systems, methods, and non-transitory computer-readable storage media for generating a context-based rich communication log. A system configured to practice the method performs a context-based analysis of a history of communication sessions over at least two communication modalities, wherein the context-based analysis considers semantic meaning, temporal relationship, and user activities. The system generates associations between the communication sessions based on the context-based analysis, and generates the context-based rich communication log based on the associations. The context-based analysis can be based on time, session participant identifications, ongoing events, and/or on-demand queries of the communication sessions. The system can then present the context-based rich communication log to a user.

Abstract: A system and method to influence routing of a call by a sequenced application from among a plurality of sequenced applications is disclosed. The method comprises receiving a header for the call wherein the header comprises at least one directive from each of the plurality of sequenced applications. Further the method comprises arbitrating conflicts from among the one directive in the header in order to determine a set of sequenced application headers to at least partially execute. Finally, the determined set of sequenced application headers is at least partially executed.

Abstract: Disclosed herein are systems, methods, and non-transitory computer-readable storage media for forming communication threads. A system configured to practice the method receives a first log of first communications in a first modality and receives a second log of second communications in a second modality. Then, the system analyzes the first log and the second log to determine relationships between the first communications and the second communications. The system identifies, based on the relationships, sets of communications having a relationship strength above a threshold, and can form communication threads based on the sets of communications. The system can form communication threads by adding a meta-data tag to a communication unit. Example modalities include short message service (SMS), text, instant messages, phone calls, video calls, emails, events, social networking, and voicemail. The system can further rank the importance of communications threads based on user actions, to yield an importance value.

Abstract: Systems and methods are described for selecting applications for incorporation into an application sequence. The selected applications provide one or more features to a communication session and the order of applications selected for the application sequence depends, at least in part, on one or more dynamic parameters. The consideration of dynamic parameters for application sequencing provides a more flexible alternative to traditional application sequencing based on static parameters, like user identities.

Abstract: A call processing system includes a call processing server. The call processing server processes calls for an internal network that employs SIP features and functions. The call processing server can receive calls from or send calls to one or more external communication endpoints that are not part of the internal network. However, the call processing server can associate a floating user agent with the communication from the external communication endpoint and lock the floating user agent to a gateway. After locking onto a gateway and initiating the call, the floating user agent can then publish call event status and receive SIP primitives similar to other SIP-enabled devices.