Changes between Version 123 and Version 124 of FAQ

Timestamp:

Dec 9, 2016 1:26:53 AM (8 years ago)

Author:

ming

Comment:

--

FAQ

@@ -336 +336 @@
 ==== Use Audio Switchboard ====
 
-If you don't need conferencing, you may want to consider replacing the conference bridge with the [wiki:Nokia_APS_VAS_Direct#switchboard audio switchboard] which does very minimum buffering to the audio. You will loose conferencing feature, but as a bonus this will lower CPU usage too. 
+If you don't need conferencing, you may want to consider replacing the conference bridge with the [wiki:switchboard audio switchboard] which does very minimum buffering to the audio. You will loose conferencing feature, but as a bonus this will lower CPU usage too. 
 
 To use the audio switchboard, declare this in your {{{config_site.h}}}:
@@ -1128 +1128 @@
  1. '''Avoid resampling'''. Resampling is a CPU intensive process, thus it should be avoided if you can, by choosing uniform clock rate for all media components (sound device, conference bridge, codecs, WAV files, etc.).
  1. '''Choose effective sampling rate'''. Make sure that PJSUA-LIB selects the most effective sampling rate/clock rate for your application. For example, if the application only supports narrowband codecs (G.711, GSM, iLBC, G.723, or G.729), then the best sampling rate to choose would be 8KHz. Choosing higher sampling rate will only just waste CPU power since with higher sampling rate, the more processing is needed. With ''pjsua'', sampling rate can be forced with {{{--clock-rate}}} option. In the application, this can be achieved by setting {{{pjsua_media_config.clock_rate}}} field.
- 1. '''Conference bridge vs audio switchboard'''. If you don't need conferencing, you may want to consider replacing the conference bridge with the [wiki:Nokia_APS_VAS_Direct#switchboard audio switchboard] which is lighter. You will loose conferencing feature, but as a bonus the audio latency will improve. To use the audio switchboard, declare {{{PJMEDIA_CONF_USE_SWITCH_BOARD}}} to non-zero in your {{{config_site.h}}}
+ 1. '''Conference bridge vs audio switchboard'''. If you don't need conferencing, you may want to consider replacing the conference bridge with the [wiki:switchboard audio switchboard] which is lighter. You will loose conferencing feature, but as a bonus the audio latency will improve. To use the audio switchboard, declare {{{PJMEDIA_CONF_USE_SWITCH_BOARD}}} to non-zero in your {{{config_site.h}}}
  1. '''Logging'''. The default logging level is 5, which provides verbose information just in case some debugging is needed. When absolute performance is needed, you can decrease the logging verbosity level to 3 so that only vital information is displayed. This can be done by, either at compile time by setting {{{PJ_LOG_MAX_LEVEL}}} macro (in {{{config_site.h}}} as usual), or at run-time by calling {{{pj_log_set_level()}}}.
  1. '''Threads'''. Use the optimum number of SIP worker threads in the application. The optimum number would be equal to the number of processors (or processor cores) in the system.