#750 Cannot hear anything after the call is connected

[Anonymous]

Originally created by: venu.r...@gmail.com

What steps will reproduce the problem?
1. Google voice call back via sipgate
2. Answer the call in cSipsimple
3. Nothing heard either in speaker or bluetooth mode

What is the expected output? What do you see instead?
To be able to hear the recorded voice from the other side.

Nothing is heard

What version of the product are you using? On what operating system?
CyanogenMod 7 on galaxy Tab

V 0.01-01

Please provide any additional information below.

Nimbuzz works with the same config.

[Anonymous]

Originally posted by: r3gis...@gmail.com

As for Bluetooth, before the commit I did 5 minutes ago, you should ensure that frequency is 8kHz (BT SCO only support 8kHz and previously CSipSimple did not that automatically on BT).

As for speaker that's maybe something with routing. Samsung audio driver has strange routing rules. However there is some workarounds you could try.
Check in the FAQ the last entry about audio troubleshooting it may help to solve the problem. Specially the "Use mode API" option.

If it helps please send a report log so that I can automatically set the correct setting for galaxy tab.

Status: Need-Details

[Anonymous]

Originally posted by: venu.r...@gmail.com

I enabled ICE (STUN was already enabled). Now I can hear the other side through the speaker.

I changed the clock rate to 8KHz under Audio Quality.

Bluetooth is still a problem. It just makes an intermittent noise like one of those radios used to make when no station is selected - not continuous noise.

[Anonymous]

Originally posted by: r3gis...@gmail.com

Ok.

As for Bluetooth, follow issue 51. I've recently ([r671] on nightly build server) improved things to be automatically activated and to use 8kHz. However I'm not sure it will works fine on all devices. It is working fine on Nexus One and a AD2P/SCO jabra bt headset.

However as I know that Samsung's android driver are very badly developed (supporting each of their device is a perpetual fight...). As consequence my first thought about the fact it does not work properly on your galaxy tab is that it's cause of Samsung audio driver.
Did you try the "Use mode API" option?

Status: WrongConfig