Abstract: In general, the disclosure describes techniques for evaluating application quality of experience metrics over a software-defined wide area network. For instance, a network device may receive an application data packet of a data flow for an application and send a first set of probe packets, configured according to an initial probing profile, over each of one or more links, The network device may monitor the data flow to determine one or more characteristics of the data flow and generate an updated probing profile based on the one or more characteristics of the data flow. The network device may then send a second set of one or more probe packets, configured according to the updated probing profile, over each of the one or more links.

Abstract: Techniques are described for selecting, with an intermediate device, a preferred remote endpoint from a plurality of remote endpoints accessible to a client computing device via a network and indicating the preferred remote endpoint to the client computing device. For example, an intermediate device may intercept a DNS response from a DNS load balancer that load balances service requests across multiple remote endpoints that provide the requested service. Based on values for one or more network performance metrics for network traffic from each of the multiple endpoints to the intermediate device, the intermediate device may modify the priority of IP addresses included in the DNS response. The intermediate device may, for instance, replace an original primary IP address in the DNS response with an IP address for another one of the remote endpoints for which the intermediate device measured better network performance metrics.

Abstract: The present disclosure relates to enabling clients to identify qualified developers for software development projects. An example method of operating a developer exchange server includes updating stored progress of developers for mission-related activities, wherein the mission-related activities correspond to features of a software platform, and determining, based on the stored progress of each of the developers, a confidence score for each of the developers for each of the features. The method includes receiving a search request that indicates a subset of the features and corresponding confidence thresholds for each of the subset of features, and in response, determining a ranked listing of qualified developers based on the subset of the features, the corresponding confidence thresholds, and the respective confidence score of each of the developers for each of the subset of features. The method further includes providing the ranked listing of qualified developers in response to the search request.

Abstract: The present disclosure relates techniques for coordinating and synchronizing client-facing support services with the activities and responses from one or more technical teams assigned to address a client issue. In certain implementations, this may allow an agent or customer approach to use a single reference identifier (such as a case or matter number) to access information or updates from technical teams that do not typically employ such a number for their own tracking purposes. In this manner, relevant information to a client issue may be accessed from all involved technical teams at the agent level as well as allowing the technical teams themselves to readily see activity by other teams.

Abstract: A visual task management board may include multiple task records that includes information associated with the respective task records. The task records may include an action status field that displays if the task is actionable or is blocked. Further, if the task is blocked, the visual task management board may display why the action is blocked. Additionally, information associated with blocking of the task may be stored. If a task is not blocked, the visual task management board may display if the task needs attention, indicative that acting upon the task is urgent. The action status of a task may be based at least in part on action taken by a user of the visual task management board, such as via an action performed on the visual task management board.

Abstract: Techniques are described for performing subscriber aware two-way active measurement protocol (TWAMP) data session provisioning between two endpoints in a computer network. For example, the disclosed techniques include extending TWAMP control messaging to include a communication mode for negotiating subscriber-aware TWAMP data monitoring. If the communication mode is supported by both endpoints, a subscriber identifier is specified when a TWAMP data session is provisioned (negotiated) over the control session. The disclosed techniques further include extending TWAMP data messaging to include the subscriber identifier in each test packet for the data session. In this way, each of the endpoints may identify a subscriber corresponding to one or more received TWAMP test packets based on the subscriber identifier included in the received TWAMP test packets.

Abstract: Embodiments of the present disclosure are directed to providing, via a client instance hosted by an enterprise management data-center, an interactive map configured to provide contextual actions on a user interface. Using interaction points of the interactive map, a user may assign tasks, communicate with other users, and search for various elements.

Abstract: Embodiments of the present disclosure are directed to providing, via a client instance hosted by an enterprise management data-center, an optimized travel route, including task assignment and scheduling, based at least on user configured criteria. Particularly, the client instance may execute an algorithm, trained via machine learning, to determine the optimized travel route in view of the user configured criteria.

Abstract: The present disclosure relates to enabling clients to identify qualified developers for software development projects. An example method of operating a developer exchange server includes updating stored progress of developers for mission-related activities, wherein the mission-related activities correspond to features of a software platform, and determining, based on the stored progress of each of the developers, a confidence score for each of the developers for each of the features. The method includes receiving a search request that indicates a subset of the features and corresponding confidence thresholds for each of the subset of features, and in response, determining a ranked listing of qualified developers based on the subset of the features, the corresponding confidence thresholds, and the respective confidence score of each of the developers for each of the subset of features. The method further includes providing the ranked listing of qualified developers in response to the search request.

Abstract: The present approach is related to incentivizing users of social media to provide feedback for certain products. The embodiments include monitoring relevant social media content that includes feedback associated with the products, where the social media content is created by different users via social media profiles. Evaluation rules are applied to the social media content to allocate a number points to the social media profiles every time relevant social media is created. When a certain threshold of accumulated points has been exceeded by a user, the user is further incentivized to continue to provide feedback to products via social media, where the incentive includes a form of a reward.

Abstract: Techniques are described for performing subscriber aware two-way active measurement protocol (TWAMP) data session provisioning between two endpoints in a computer network. For example, the disclosed techniques include extending TWAMP control messaging to include a communication mode for negotiating subscriber-aware TWAMP data monitoring. If the communication mode is supported by both endpoints, a subscriber identifier is specified when a TWAMP data session is provisioned (negotiated) over the control session. The disclosed techniques further include extending TWAMP data messaging to include the subscriber identifier in each test packet for the data session. In this way, each of the endpoints may identify a subscriber corresponding to one or more received TWAMP test packets based on the subscriber identifier included in the received TWAMP test packets.

Abstract: Techniques are described for performing subscriber aware two-way active measurement protocol (TWAMP) data session provisioning between two endpoints in a computer network. For example, the disclosed techniques include extending TWAMP control messaging to include a communication mode for negotiating subscriber-aware TWAMP data monitoring. If the communication mode is supported by both endpoints, a subscriber identifier is specified when a TWAMP data session is provisioned (negotiated) over the control session. The disclosed techniques further include extending TWAMP data messaging to include the subscriber identifier in each test packet for the data session. In this way, each of the endpoints may identify a subscriber corresponding to one or more received TWAMP test packets based on the subscriber identifier included in the received TWAMP test packets.

Abstract: Techniques are described for performing subscriber aware two-way active measurement protocol (TWAMP) data session provisioning between two endpoints in a computer network. For example, the disclosed techniques include extending TWAMP control messaging to include a communication mode for negotiating subscriber-aware TWAMP data monitoring. If the communication mode is supported by both endpoints, a subscriber identifier is specified when a TWAMP data session is provisioned (negotiated) over the control session. The disclosed techniques further include extending TWAMP data messaging to include the subscriber identifier in each test packet for the data session. In this way, each of the endpoints may identify a subscriber corresponding to one or more received TWAMP test packets based on the subscriber identifier included in the received TWAMP test packets.

Abstract: Methods and Systems for facilitating caching of advertisements are described. The methods include receiving an ad request and generating a serving plan in response to said receiving the ad request. The serving plan includes multiple cache lines that identify corresponding advertisements. Each of the cache lines is associated with a corresponding expiration. Also, each cache line is readable by logic to display one of the advertisements corresponding to the cache line. The cache lines include a first cache line. The first cache line includes ad information, which is associated with a first one of the advertisements. Moreover, the ad information includes one or more parameters for expiration of the first cache line of a client device. The client device is configured to display the plurality of advertisements. The method includes sending the serving plan to the client device to store in the client device.

Abstract: Methods and Systems for facilitating caching of advertisements are described. The methods include receiving an ad request and generating a serving plan in response to said receiving the ad request. The serving plan includes multiple cache lines that identify corresponding advertisements. Each of the cache lines is associated with a corresponding expiration. Also, each cache line is readable by logic to display one of the advertisements corresponding to the cache line. The cache lines include a first cache line. The first cache line includes ad information, which is associated with a first one of the advertisements. Moreover, the ad information includes one or more parameters for expiration of the first cache line of a client device. The client device is configured to display the plurality of advertisements. The method includes sending the serving plan to the client device to store in the client device.

Abstract: Techniques that enable a user to make VOIP phone calls using a traditional telephone by directing a communications module to connect the caller to another user are provided. The caller first dials a DID and identifies a receiver to be reached. Once the caller has identified the receiver, the caller may hang up the phone and wait until the communications module contacts the caller once the receiver has been connected. The communication module hunts the receiver using the receiver's multiple contact information by calling each of the receiver's contact numbers. Once the receiver answers one of the calls, the communications module detects that the receiver has been connected and then contacts the caller. Finally, once the caller answers the telephone, the caller and the receiver are connected and a communication may commence.