Using Audio Proxy Server (APS) in PJSIP

Table of Contents

1. Requirements
2. Building Steps
3. Installation
4. Developing Application with APS Support
5. Limitations
6. Issues

Audio Proxy Server (APS) is a wrapper to the Nokia S60 sound device. Its main purpose is to bypass the Vendor ID (VID) related restrictions on S60 3rd Edition and S60 3rd Edition, FP1 platforms, when streaming audio data in 3rd party applications. The component is most suitable for VoIP developers who need to set the appropriate audio priority and preference values in order to utilize full duplex audio (quoted from ​Nokia wiki page on APS).

APS has some benefits over Audio Streaming API:

• Much lower latency. The Audio Streaming API has few hundreds milliseconds of latency at best, while using APS it is possible to bring down the latency to only about 30ms!
• Ability to switch audio-routing (to earpiece or loudspeaker). Routing to earpiece can also avoid echo.

Requirements

To build PJSIP with APS support, we need:

1. Successfully build non-APS pjsip as described Getting Started for Symbian
2. APS release 2.4.3 that is packaged in ​SDK API Plug-in, e.g:
   • ​APS for MR
   • ​APS for FP1
   • we're not sure how APS should work for FP2
3. MMF DevSound API (i.e.: to get sounddevice.h):
   • for S60 3rd edition MR, it can be found in ​Extensions plug-in for S60 3rd Edition SDK for Symbian OS for C++ MR. Note that the page may say that this extension has been superseded by the plugin above, but you still need to install this one.
   • for S60 3rd edition FP1 & FP2, it is bundled in the SDK API Plug-in above.
4. You need a Symbian Developer Certificate of type Open Signed Offline and with valid Publisher ID to install the application that uses APS on the device. APS requires MultimediaDD capability and this capability is among the restricted capabilities so the application needs to be signed with a valid developer certificate to use the capability. The signing options for applications that need these restricted capabilities are Open Signed Offline or Certified Signed. Please see ​Symbian Signed website for more detail.

Building Steps

Here are a few steps to build PJSIP with APS support:

1. 1.0.x: Specify that sound device implementation is using APS, i.e in config_site.h:

   #if defined(PJ_SYMBIAN) || PJ_SYMBIAN==1
   #   define PJMEDIA_SOUND_IMPLEMENTATION PJMEDIA_SOUND_SYMB_APS_SOUND
   #endif
   

   1.1 and above: macro PJMEDIA_SOUND_IMPLEMENTATION is deprecated, so it should be defined as:

   #if defined(PJ_SYMBIAN) || PJ_SYMBIAN==1
   #   define PJMEDIA_AUDIO_DEV_HAS_SYMB_APS	1
   #endif
   

2. 1.0.x: Edit bld.inf and application's .mmp files (e.g: symbian_ua.mmp, symbian_ua_gui.mmp, symsndtest.mmp), and activate SND_USE_APS macro:

   #define SND_USE_NULL	0
   #define SND_USE_APS	1
   #define SND_USE_VAS	0
   

   1.1 and above: bld.inf doesn't need to be edited, and the macro should be defined is SND_HAS_APS:

   #define SND_HAS_APS	1
   

3. Refresh the makefiles:
   • 1.0.x: If you are using Carbide, please refresh the project first (right click bld.inf from the Symbian Project Navigator pane, and select Refresh). symbian_audio_aps.mmp should be there after the refresh done.
     • If you are building from command line, use bldmake clean then bldmake bldfiles.
   • 1.1 and above: symbian_audio_aps.mmp is no longer used, all symbian audio implementations are bundled in pjmedia_audiodev.mmp.
4. Clean and rebuild the whole project. Please note that WINSCW target doesn't seem to support APS.
5. Make the installer (.sis file) for the application.

Installation

1. Install APS Server apsserver2.sisx to device, the installer comes with the APS SDK package i.e in folder InstallToDevice/AudioProxyServer243. You will need to do this only once for each device.
2. Sign the application installer with APS support with Developer Certificate using Open Signed Offline/with Publisher ID.
3. Install the application to the device.

Developing Application with APS Support

1. Specify application UID in a global variable named APP_UID whose base type TPtrC, e.g:

   TPtrC APP_UID = _L("2000521C");
   

2. Link the application to APS library, i.e:

   LIBRARY		APSSession2.lib
   

3. Add MultimediaDD capability to your application, i.e. in application MMP:

   CAPABILITY	MultimediaDD ...
   

There are some notes for developing application with APS support:

• There seems binary compatibility issue among Symbian OS versions, you will have to use appropriate SDK API Plug-in and apsserver2.sisx for each OS version.

Limitations

• Currently, this APS wrapper can only work in S60 3rd edition device that supports G.711, which perhaps means all S60 3rd edition devices.

Issues

We found some issues with APS, such as noisy audio or no audio at all, please go to Symbian Section in our FAQ for more information.