sound is audible only on one device

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

Please follow the inline comment..

On Wed, Dec 16, 2009 at 9:07 PM, sangram desai <desaisang at gmail.com> wrote:
> Hi All,
> We were able to establish a call between two Windows Mobile handsets. But
> sound is audible only on one device.
> The scenario is as follows:
> If there are two devices D1 and D2, and a call is made from D1 to D2, it is
> audible only on D2. Even if call is made from D2 to D1, the sound is still
> audible on D2 side with very poor quality over wifi/GPRS.

AFAIK, GPRS is usually not suitable for VoIP.

> We have tried to set the following parameters also, but it has only
> increased the sound intensity keeping the choppiness of sound and packet
> loss intact on D2.
> PJMEDIA_SND_DEFAULT_REC_LATENCY? set to 140
> PJMEDIA_SND_DEFAULT_PLAY_LATENCY? set to 140

FYI, we increased default play latency to 160, as the value seems to
give acceptable performance on most WM devices. We used to recommend
to use pjsystest tool to find the optimum latency setting.

> We have found that both the handsets were using differnt codecs as displayed
> by wireshark in RTP packets. Those were G711 PCMU and GSM codecs.
> 1) Is it necessary to have same codec between two communicating devices?

Well, unfortunately pjsip requires both sides to use same codec,
otherwise one way audio or no audio may be occurred. Ticket #476 may
be related to this issue.

As the call was relayed and media might be transcoded (from the log),
the simplest workaround could be by enabling only a codec in pjsip.

> 2) What is the ideal configuration settings for WM devices?

Ideal? if there was one, everybody must be happy :) It should depend
on many factors, usually about purpose and environment. For general
use, config_site_sample.h should be optimal. Moreover, some settings
may depend on the device, e.g: audio device latency settings.

> 3)How can we determine CPU usage while our application is running as it can
> be one of the reasons behind packet loss.

Right, for optimizations, please check:
 - http://trac.pjsip.org/repos/wiki/FAQ#cpu
 - http://trac.pjsip.org/repos/wiki/audio-check-cpu
There should be third-party tools out there to monitor CPU usage.

BR,
nanang

> Please note that we are using PJSIP version 1.5
> The handsets we are using are HTC Touch(D1) and HTC innovation(D2).
> We?have attached the PJSIP.log file with this mail.
> Thanks,
> Sangram



[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux