vaibhav3002 / sipdroid

Automatically exported from code.google.com/p/sipdroid
GNU General Public License v3.0
0 stars 0 forks source link

in-call DTMF dialing fails intermittently with PCMU but works with PCMA #771

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Dialing additional digits via sipdroid during a call never worked
reliably for me until i disabled the PCMU codec and started using PCMA.
If i try dialing additional digits during a call when using the PCMU
codec i hear tones for each digit i dial, but the other end of the call
only received a random subset of the digits i dial.  It didn't seem to
matter how quickly or slowly i entered the digits, some were always
lost.

I'm using the following version of sipdroid:
- sipdroid 2.0.1 beta
- Nexus One /w Android 2.2.1 b FRG83D /w T-Mobile USA

I've seen this problem using the following two configurations:

- sipdroid connected to pbxes.com and pbxes.com routing the calls out
  via a google voice trunk.  The call is initiated from sipdroid to a
  DID.

- sipdroid connected to gizmo5.  The call is initiated from sipdroid to
  a DID.

Using PCMA instead of PCMU fixes the issue in both configurations above.
In all cases I've been using a WIFI connection.  I tried adjusting the
"dtmfmode" setting on my extension at pbxes.com, but this did not make
any difference.  I also tried testing some other codecs with pbxes.com
(these codecs don't seem to be supported by gizmo5) and discovered that:
- speex fails the same way that PCMU does.
- GSM works fine.

To reproduce the problem:
- configure sipdroid to register to a sip provider.
- establish an outbound connection via sipdroid to a DID.
- ensure that sipdroid is using the PCMU or speex codec.
- try to dial additional digits during the call, the other end should
  fail to receive them all.
- repeat this process using the PCMA or GSM codec and things should
  succeed.

This issue may be related to the following existing bugs:

100 DTMF not working while connected to WLAN
329 DTMF problem starting with 1.3.8

But neither of those bugs mentions talks specifically about DTMF
problems being related to a specific codec.  If this issue is a dup of
those i apologize.

Original issue reported on code.google.com by e...@drymartini.org on 1 Dec 2010 at 8:23