The present disclosure describes a monitoring environment that monitors an activity for activity that may be indicative of being prohibited by the local, the state, and/or the national governing authorities, namely suspicious activity, or activity that is prohibited by the local, the state, and/or the national governing authorities, namely prohibited activity. The monitoring environment verifies the activity is actually being monitored within the monitoring environment. The verification can require one or more monitoring persons monitoring the activity to perform one or more tasks to verify their attentiveness in monitoring the activity. The one or more tasks can be as simple as activating a checkbox or providing a code or an electronic signature to provide some examples, although more complicated tasks, such as a biometric verification such as a retinal, a facial, and/or a voice verification to provide some examples, are possible as will be recognized by those skilled in the relevant art(s) without departing from the spirit and scope of the present disclosure.

The present disclosure relates generally to network diagnostics, and more specifically to techniques for determining the health of customer premises equipment (CPE) devices. In certain examples, a scoring system can determine a health score for a CPE device, the health score indicating the health of the CPE device. The health score is determined by receiving, analyzing, and integrating information from different sources, including sources in addition to CPE diagnostic data for the CPE device at the current time. Such sources can include CPE diagnostic data for the CPE device at other times, CPE diagnostic data for other CPE devices related to the CPE device (e.g., in the same household or surrounding area as the CPE device), technical specifications of the CPE device (e.g., make, model and firmware of the CPE device), or per-equalization parameters obtained by the CPE device.

A test instrument connectable to a network to provide copper impairment testing and remediation in a digital subscriber line (DSL) service is provided. The test instrument may comprise a port connectable to a test point in a network. The test instrument may also comprise a processing circuit to perform tests in the following categories: (i) shorts, grounds, and opens, (ii) true length, (iii) balance, and (iv) series fault, wherein the combination of these tests may determine copper impairment. Once tests are conducted, one or more remediation recommendations may be provided based at least in part on failure in one of the test categories. The test results and remediation recommendations may then be presented at an output, such as a display at a test instrument or user device.

A fault in a telecommunication line can be identified and located using line test data for that telecommunication line. A series of line tests can be performed on a selected telecommunication line experiencing problems. The results from the series of line tests can be analyzed to identify differences in the results between the line tests. The identified differences can then be used to determine if a fluctuation is present in the telecommunication line. If a fluctuation is determined to be present in the telecommunication line, the identified differences can also be used to determine a location of the fluctuation relative to reference location such as the distribution point where the telecommunication line originates.

Automatic testing/analysis of local loops of telecommunications networks includes obtaining bits-per-tone data for a local loop of a telecommunications network and generating a bit value string from the bits-per-tone data. The bit value string is then analyzed to determine whether it includes a bit pattern indicative of an impairment of the local loop. Further approaches for automatically testing local loops of telecommunications networks include obtaining attenuation data for multiple tones carried by the local loop and determining whether the attenuation data falls below thresholds for providing a service using the local loop.

Example implementations relate to conferencing environment monitoring. An example monitoring device can include a processor to monitor a physical aspect and an audio aspect of a conferencing environment in which a conferencing device is located, wherein the conferencing device is communicatively coupled to the monitoring device. The monitoring device can detect, based on the monitoring, an issue impacting a conferencing session associated with the conferencing device and the conferencing environment. In response to the detection, the monitoring device can determine a correction for the issue and perform the correction.

Embodiments provide systems and methods for reconstructing a communication session upon a failure of a session manager by monitoring a communication session associated with a Universal Call IDentifier (UCID) and detecting a failure of the session manager. In some cases, A timer can be set in response to detecting the failure of the session manager. In response to the timer expiring before detecting the recovery of the session manager, the application server can end monitoring of the communication session. In response to detecting a subsequent recovery of the session manager, a re-invitation message associated with the communication session and including the UCID can be sent. Communications components of the contact center can receive and accept the re-invitation message, re-map a session initiated by the re-invitation message to the communication session based on the UCID from the re-invitation message, and reconstruct the communication session.

Decreasing the time to resolution of trouble tickets and preemptively resolving potential network issues using a predictive customer care support framework communicatively coupled to a telecommunications service provider via a network is described. Techniques described herein include preprocessing ticket data associated with a trouble ticket corresponding to a subscriber using a decision engine that can implement a decision tree scheme to automatically identify appropriate data sources from which relevant data can be routed to the decision engine in a bundled format. The techniques further include detecting potential network issues not yet reported by subscribers using an analytical engine to identify a root cause for the potential network issues and implementing recommended solutions to reduce an influx of trouble tickets at a customer support terminal.

The present disclosure relates to methods and devices for communication systems comprising an electrically conductive line. The disclosure proposes a method in a line estimation device for determining termination characteristics of an electrically conductive line in a communication system. The method comprises outputting a test signal to the line, wherein the test signal is a wideband test signal with a bandwidth arranged to provide an adequate measurement time-resolution. The method further comprises receiving reflections from impedance discontinuities of the line in response to the test signal. The method also comprises forming a trace of the reflections. The method additionally comprises identifying at least one anomaly in the trace of reflections. The method yet further comprises determining termination characteristics of the line based on characteristics of the trace before and after the identified at least one anomaly. The disclosure also relates to corresponding line estimation devices and computer programs.

Decreasing the time to resolution of trouble tickets and preemptively resolving potential network issues using a predictive customer care support framework communicatively coupled to a telecommunications service provider via a network is described. Techniques described herein include preprocessing ticket data associated with a trouble ticket corresponding to a subscriber using a decision engine that can implement a decision tree scheme to automatically identify appropriate data sources from which relevant data can be routed to the decision engine in a bundled format. The techniques further include detecting potential network issues not yet reported by subscribers using an analytical engine to identify a root cause for the potential network issues and implementing recommended solutions to reduce an influx of trouble tickets at a customer support terminal.