Outbound ringback tone is through speaker rather than actual network ringback in earpiece.

[GoogleCodeExporter]

NOTE: This form is only for reporting bugs. For problems, questions, or
comments, please visit:  http://groups.google.com/group/sipdroid-users

*************************************************
* Read the FAQ                                  *
*    Check if the bug has already been reported *
*        No doubles please                      *
*************************************************

Did you carefully read above and decide this means of communication is the
right for your notice? Don't just list an incompatible SIP server or
device, please. Try to look behind the scenes if you like to
contribute here. Thanks!

--
What steps will reproduce the problem?
1. Dial a call using Sipdroid 1.1.8 beta on Moto Droid Android 2.0
2. I am connected to an Asterisk server running Asterisk 1.4.26.1
3.

What is the expected output? What do you see instead?
I expect to hear network delivered ringback tone in the phone earpiece
rather than a local tone through the speaker.

What version of the product are you using? On what operating system?
Version 1.1.8 Beta, Android 2.0 on Motorola Droid

Which SIP server are you using? What happens with PBXes?
I am using Asterisk 1.4.26.1.  I do not have a PBXes account.

Please provide any additional information below.
The way this functions, if you call a number which would give a "non
working number" recoding, the audio is not cut through so you can hear it.
 The voice path does not cut through to the earpiece of the phone until the
other end actually answers.  I would like to see this client provide
cut-through of the audio from initial call set up.

Original issue reported on code.google.com by jwmcconn...@gmail.com on 13 Nov 2009 at 1:26

[GoogleCodeExporter]

Issue 253 has been merged into this issue.

Original comment by pmerl...@googlemail.com on 26 Dec 2009 at 10:05

[GoogleCodeExporter]

Original comment by pmerl...@googlemail.com on 18 Jan 2010 at 2:56

• Changed state: FutureRelease

[GoogleCodeExporter]

Original comment by pmerl...@googlemail.com on 18 Jan 2010 at 3:23

• Changed state: Fixed