Custom Query (2195 matches)

BDSound IMproved Audio Device (bdIMAD) is a multiplatform audio interface created to integrate in PJSIP library with no effort.

Features

• Echo cancellation (Full Duplex)
• Noise reduction
• Automatic Gain Control
• Audio Enhancement

Supported operating systems

• Windows
• Android
• MacOS X
• iOS
• Linux / Alsa

Supported platforms

• x86
• x64
• ARM Cortex-A8/A9/A15 with NEON

Using Pjsip with bdIMAD

• Request bdIMAD library from ​bdsound
• Enable bdIMAD by defining this on config_site.h

  #define PJMEDIA_AUDIO_DEV_HAS_BDIMAD	1
  

• Make sure you disable other sound device backends, by defining these on config_site.h

  #define PJMEDIA_AUDIO_DEV_HAS_PORTAUDIO 0
  #define PJMEDIA_AUDIO_DEV_HAS_WMME 0
  #define PJMEDIA_AUDIO_DEV_HAS_COREAUDIO 0 
  

• Since the bdIMAD library provide itself the echo cancellation and the latency management, is necessary to disable these features in the PJSIP librariy applications. For example in PJSUA sample application there is the need to provide the following commands:

  --ec-tail=0
  --no-vad
  --capture-lat=0
  --playback-lat=0
  

A CLI framework features an interface for defining command specification, parsing, and executing a command.

Features

• Portable across desktop (windows, macosx, linux, etc) and mobile platforms (symbian, windows mobile, iphone, android, etc.)
• User may access the UI by telneting to the app, and be able to operate the app as if it's a desktop app

Enhancements to existing console UI

• Command (auto)completion, e.g. one can specify "makecall" or "make" or "m". The system will detect if a fraction of a word makes up unique command
• arguments completion, i.e. user may specify the arguments together with the command, or if not, he will be asked to provide them.
• command history (the use of up and down arrow)

Telnet interface

• will provide interface exactly the same as console interface on desktop
• may provide different logging level for each client

Command specification

The command specification includes:

• Definition in an xml file
• Command/argument name
• Command/argument id
• Argument data type (int, string, choice)
• Argument mandatory type (optional/mandatory)
• Text description (to show in help screen)
• Each command could contain argument list or other command
• Callback handler

XML example of a command specification:

<CMD name='vid' id='0' desc="">
       <CMD name='help' id='0' desc='' />
       <CMD name='enable' id='0' desc='' />
       <CMD name='disable' id='0' desc='' />
       <CMD name='call' id='0' desc='' >
                <CMD name='add' id='101' desc='...' />
                <CMD name='cap' id='102' desc='...' >
                   <ARG name='streamno' type='int' desc='...' id='1'/>
                   <ARG name='devid' type='int' optional='1' id='2'/>
                </CMD>
       </CMD>
</CMD>
<CMD name='disable_codec' id=0 desc="">
	<ARG name='codec_list' type='choice' id='3'>
	    <CHOICE value='g711'/>
	    <CHOICE value='g722'/>
	</ARG>
</CMD>