Jump to: navigation, search
Line 1: Line 1:
 
= Reporting Operational Data=
 
= Reporting Operational Data=
 +
 +
This page describes SIP Endpoint SDK capabilities to report problems with audio stream and other operational data to the application code, intended to provide real-time indication to the user of something not working as expected because of environmental problems (audio device malfunction, network data path broken etc).
 +
 +
== Detection and reporting of missing audio ==
 +
The purpose of this feature is to detect a case when no audio data comes in either direction, caused by:
 +
 +
microphone device malfunction, or microphone being inadvertently muted by user
 +
audio stream coming from remote side consists of complete silence, because of data path broken somewhere
 +
Voice Activity Detection is performed at the voice engine level, using Real-time Access to Audio Stream feature internally, with the results of the analysis attributed to currently active session. Detection results for each 10 msec audio frame are processed as following (separately in both directions):
 +
 +
15 frames (150 msec of audio) are aggregated into one data point for histogram, printed to the log at each 10th voe:checkpoint (about each 10 sec)
 +
total number of "active" frames and timestamp of last such frame are saved in audio statistics structure
 +
Application access to the raw detection results (or histogram data) is not planned at this moment.
 +
 +
SIP Endpoint Core (C++) API
 +
  
 
[[Category:V:SESDK:9.0.0OSXDRAFT]]
 
[[Category:V:SESDK:9.0.0OSXDRAFT]]

Revision as of 07:21, May 20, 2020

Reporting Operational Data

This page describes SIP Endpoint SDK capabilities to report problems with audio stream and other operational data to the application code, intended to provide real-time indication to the user of something not working as expected because of environmental problems (audio device malfunction, network data path broken etc).

Detection and reporting of missing audio

The purpose of this feature is to detect a case when no audio data comes in either direction, caused by:

microphone device malfunction, or microphone being inadvertently muted by user audio stream coming from remote side consists of complete silence, because of data path broken somewhere Voice Activity Detection is performed at the voice engine level, using Real-time Access to Audio Stream feature internally, with the results of the analysis attributed to currently active session. Detection results for each 10 msec audio frame are processed as following (separately in both directions):

15 frames (150 msec of audio) are aggregated into one data point for histogram, printed to the log at each 10th voe:checkpoint (about each 10 sec) total number of "active" frames and timestamp of last such frame are saved in audio statistics structure Application access to the raw detection results (or histogram data) is not planned at this moment.

SIP Endpoint Core (C++) API

Comments or questions about this documentation? Contact us for support!