Abstract: A vulnerability-solution resolution (VSR) system is disclosed that is designed to create and maintain associations between vulnerabilities identified by third-party scanners (TPSs) and solutions, such as software patches received from third-party vendors. The VSR system includes a data scheme that enables information regarding vulnerabilities and solutions to be stored, and enables certain relationships to be automatically created between these vulnerabilities and solutions. In particular, the VSR system is designed to automatically form certain relationships between particular vulnerabilities and solutions based on solution supersedence and inheritance. Additionally, the VSR system includes a graphical user interface (GUI) that enables a user to exclude particular relationships from consideration when recommending solutions to resolve a vulnerability or when calculating metrics regarding the vulnerability.

Abstract: A vulnerability-solution resolution (VSR) system is disclosed that is designed to create and maintain associations between vulnerabilities identified by third-party scanners (TPSs) and solutions, such as software patches received from third-party vendors. The VSR system includes a data scheme that enables information regarding vulnerabilities and solutions to be stored, and enables certain relationships to be automatically created between these vulnerabilities and solutions. In particular, the VSR system is designed to automatically form certain relationships between particular vulnerabilities and solutions based on solution supersedence and inheritance. Additionally, the VSR system includes a graphical user interface (GUI) that enables a user to exclude particular relationships from consideration when recommending solutions to resolve a vulnerability or when calculating metrics regarding the vulnerability.

Abstract: A vulnerability-solution resolution (VSR) system is disclosed that is designed to create and maintain associations between vulnerabilities identified by third-party scanners (TPSs) and solutions, such as software patches received from third-party vendors. The VSR system includes a data scheme that enables information regarding vulnerabilities and solutions to be stored, and enables certain relationships to be automatically created between these vulnerabilities and solutions. In particular, the VSR system is designed to automatically form certain relationships between particular vulnerabilities and solutions based on solution supersedence and inheritance. Additionally, the VSR system includes a graphical user interface (GUI) that enables a user to exclude particular relationships from consideration when recommending solutions to resolve a vulnerability or when calculating metrics regarding the vulnerability.

Abstract: A vulnerability-solution resolution (VSR) system is disclosed that is designed to create and maintain associations between vulnerabilities identified by third-party scanners (TPSs) and solutions, such as software patches received from third-party vendors. The VSR system includes a data scheme that enables information regarding vulnerabilities and solutions to be stored, and enables certain relationships to be automatically created between these vulnerabilities and solutions. In particular, the VSR system is designed to automatically form certain relationships between particular vulnerabilities and solutions based on solution supersedence and inheritance. Additionally, the VSR system includes a graphical user interface (GUI) that enables a user to exclude particular relationships from consideration when recommending solutions to resolve a vulnerability or when calculating metrics regarding the vulnerability.

Abstract: Communication systems and methods are described that include call notification with rich caller identification. Components of the communication systems are configured to receive a call for a user via an enterprise voice channel. A call request is automatically generated in response to event data of the received call. The call request includes caller data from enterprise databases or directories. The caller data provides identifying information of the caller to the user via the call request. The call request can include response options by which the user can participate in the call. The call request is routed to a target device of the user via a data channel of the host enterprise. The target device provides the user with multiple action or response options via the call request. The response options include for example accepting the call, delaying the call, forwarding the call, ignoring the call, and ignoring the caller.

Abstract: Communication systems and methods are described that include call notification with rich caller identification. Components of the communication systems are configured to receive a call for a user via an enterprise voice channel. A call request is automatically generated in response to event data of the received call. The call request includes caller data from enterprise databases or directories. The caller data provides identifying information of the caller to the user via the call request. The call request can include response options by which the user can participate in the call. The call request is routed to a target device of the user via a data channel of the host enterprise. The target device provides the user with multiple action or response options via the call request. The response options include for example accepting the call, delaying the call, forwarding the call, ignoring the call, and ignoring the caller.

Abstract: Communication systems and methods are described that include call notification with rich caller identification. Components of the communication systems are configured to receive a call for a user via an enterprise voice channel. A call request is automatically generated in response to event data of the received call. The call request includes caller data from enterprise databases or directories. The caller data provides identifying information of the caller to the user via the call request. The call request can include response options by which the user can participate in the call. The call request is routed to a target device of the user via a data channel of the host enterprise. The target device provides the user with multiple action or response options via the call request. The response options include for example accepting the call, delaying the call, forwarding the call, ignoring the call, and ignoring the caller.

Abstract: An integrated voicemail system is described that provides “visual voicemail” that overcomes the shortcomings associated with a user having to dial into a voicemail system and navigate through a menu of options using conventional voice and/or standard DTMF signaling-based browsing capabilities. The visual voicemail instead provides, via a client device of the user's choice, a visual presentation of a user's voicemails along with state information of the voicemails. The visual presentation of the voicemails includes a user interface that allows a user to control or manipulate voicemails from the client device, where the manipulation includes playing, pausing, rewinding, fast-forwarding, deleting, and changing a state of each voicemail. The visual voicemail also eliminates the need for a user to periodically call-in to the enterprise voicemail system in order to check for voicemail messages as the messages can be automatically delivered to the user's client device.

Abstract: Provisioning is described for use in communications systems. The provisioning includes receiving a message at an inbox of a device. The message includes information of an electronic location of a source device from which to download the appropriate application and device and user-specific information used for configuration of the application. An application is automatically transferred to the device in response to selection of the received message by a user of the device. The application is automatically installed on the device. The application is auto-started, at which time it self-configures using the original message.

Abstract: An integrated voicemail system is described that provides “visual voicemail” that overcomes the shortcomings associated with a user having to dial into a voicemail system and navigate through a menu of options using conventional voice and/or standard DTMF signaling-based browsing capabilities. The visual voicemail instead provides, via a client device of the user's choice, a visual presentation of a user's voicemails along with state information of the voicemails. The visual presentation of the voicemails includes a user interface that allows a user to control or manipulate voicemails from the client device, where the manipulation includes playing, pausing, rewinding, fast-forwarding, deleting, and changing a state of each voicemail. The visual voicemail also eliminates the need for a user to periodically call-in to the enterprise voicemail system in order to check for voicemail messages as the messages can be automatically delivered to the user's client device.

Abstract: Communication systems and methods are described that include call notification with rich caller identification. Components of the communication systems are configured to receive a call for a user via an enterprise voice channel. A call request is automatically generated in response to event data of the received call. The call request includes caller data from enterprise databases or directories. The caller data provides identifying information of the caller to the user via the call request. The call request can include response options by which the user can participate in the call. The call request is routed to a target device of the user via a data channel of the host enterprise. The target device provides the user with multiple action or response options via the call request. The response options include for example accepting the call, delaying the call, forwarding the call, ignoring the call, and ignoring the caller.

Abstract: In one embodiment, a method comprises a mobile node receiving an incoming wireless call; the mobile node determining whether enhanced services are available for the incoming wireless call based on outputting a DTMF tone on a voice channel associated with the incoming wireless call and determining whether a notify message, indicating a server providing the enhanced services has received the DTMF tone, is received on a data channel during the incoming wireless call; and the mobile node selectively initiating the enhanced services for the incoming wireless call with the server in response to determining the enhanced services are available for the incoming wireless call.

Abstract: Embodiments for generating a sorted integrated directory are described. The sorted integrated directory integrates contacts from disparate directories into a common directory. The formation of the integrated directory includes receiving contacts from multiple directories. The contacts represent or are formed under multiple data structures, with one data structure corresponding to one of the directories. The received contacts are converted into contact objects. The contact objects, each of which represents a contact, all include or are formed under a common data structure. An integrated directory is generated or formed from the contact objects. The integrated directory thus includes a set of contacts of the disparate source directories.

Abstract: Communication systems and methods are described that enable mobile devices to route telephone calls via an enterprise telephone system. The communication system is configured to receive via a data channel a request from the mobile device. The mobile device corresponds to a user making a call. The server receiving the request includes a private branch exchange (PBX) and one or more other servers hosted by or coupled to the enterprise. A first call leg is initiated over a first voice channel in response to the request. The first call leg is coupled to the server and mobile device. Numerous second call legs are initiated over a second voice channel, and the second call legs are coupled to the server and numerous client devices corresponding to an intended call recipients. A voice conference call is formed between the mobile device and client device by joining the first and second call legs.

Abstract: Communication systems and methods are described that enable mobile devices to route telephone calls via an enterprise telephone system. The communication system is configured to receive via a data channel a request from the mobile device. The mobile device corresponds to a user making a call. The server receiving the request includes a private branch exchange (PBX) and one or more other servers hosted by or coupled to the enterprise. A first call leg is initiated over a first voice channel in response to the request. The first call leg is coupled to the server and mobile device. A second call leg is initiated over a second voice channel, and the second call leg is coupled to the server and a client device corresponding to an intended call recipient. A voice conference call is formed between the mobile device and client device by joining the first and second call legs.

Abstract: Embodiments for searching multiple directories are described. The searching includes remote searching and local searching. Local searching is performed against the local integrated phonebook on a client device. In contrast, remote searching is performed against one or more directories or directory types of an enterprise server (e.g. corporate directory, etc.). The local directory on the client device therefore effectively functions like a cache of information of one or more of the directories of the enterprise server, where the cache is stored locally on the client device.

Abstract: Communication systems and methods are described that enable mobile devices to route telephone calls via an enterprise telephone system. The communication system is configured to receive via a data channel a request from the mobile device. The mobile device corresponds to a user making a call. The server receiving the request includes a private branch exchange (PBX) and one or more other servers hosted by or coupled to the enterprise. A first call leg is initiated over a first voice channel in response to the request. The first call leg is coupled to the server and mobile device. A second call leg is initiated over a second voice channel, and the second call leg is coupled to the server and a client device corresponding to an intended call recipient. A voice conference call is formed between the mobile device and client device by joining the first and second call legs.

Abstract: Melting information of a client device is described. The device melting includes receiving a melt message at an inbox of a client device. A source of the melt message is authenticated using identification information of the melt message. The client device automatically deletes client state information of the client device in response to authenticating the source of the melt message.

Abstract: Communication systems and methods are described that enable mobile devices to route telephone calls via an enterprise telephone system. The communication system is configured to receive via a data channel a request from the mobile device. The mobile device corresponds to a user making a call. The server receiving the request includes a private branch exchange (PBX) and one or more other servers hosted by or coupled to the enterprise. A first call leg is initiated over a first voice channel in response to the request. The first call leg is coupled to the server and mobile device. A second call leg is initiated over a second voice channel, and the second call leg is coupled to the server and a client device corresponding to an intended call recipient. A voice conference call is formed between the mobile device and client device by joining the first and second call legs.

Abstract: Communications rate control is described. The rate control includes receiving a message addressed to a client device of a user. A determination is made as to a category of the message. Data of the message is synchronized between a server and the mobile device in response to one or more of the category and one or more user actions at the client device.