<< S710/VOX VoIP Earphone vs Speaker Problem >>

---

Has anyone come up with a solution to route **INCOMING** VoIP audio to the internal speaker on the S710/VOX?

The vanilla S710/Vox VoIP install (at below link) works great out of the box, except I can find no way to redirect incoming audio to the earpiece. The conversation always plays through the speakerphone.

http://forum.xda-developers.com/show...highlight=voip

There’s lots of talk about this problem on the Development and Hacking board—but I cant find a published solution—For **ANY** wifi enabled handset—even with cooked ROMs.

Any suggestions-- ??

THANKS.

Same Problem

---

Please, Help !!!
This problem is only with this phone, urgent VoIP Services please...
TAL

OK-
Ive found two solutions-- unfortunately, both for **PPC**.

Glofiish X500—WM5 non cooked:
http://eten-users.eu/index.php?showtopic=9556&hl=

SPV M3100—WM6 cooked:
http://forum.xda-developers.com/show...&postcount=783

Several posts on different boards indicate this is an **OS** problem. Seems to me if this is true we are out of luck until an official ROM update (because there are no S710/Vox SP ROM Hacks out there).

On the otherhand—

The implementation may lie in the VoIP .dll’s which may be worth looking at since there are some floating around for SP's and PPC's.

Can anyone **CONCEPTUALLY** confirm the above?

Of course—

There may be an temporary workaround like the Glofiish solution.

Thanks.

From a posting on Modaco: would the headset solve the noise/privacy issue? I have not yet tested (I use Skype) but it seems like a reasonable workaround.

RE: << S710/VOX VoIP Earphone vs Speaker Problem >>

---

This issue is NOT SPECIFICALLY related to the S710/VOX!

THIS IS A CROSS POST-- TO CLOSE THE ISSUE IN THIS THREAD--

I EXPECT A NEW ISSUE-RELATED THREAD IN THE "DEVELOPMENT AND HACKING BOARD" SOMETIME SOON. THOSE GUYS KNOW WHAT THEY ARE DOING-- SO I THINK THATS WHERE THE ISSUE BELONGS.

And I Quote from Windows CE Networking Team WebLog:

http://blogs.msdn.com/cenet/archive/...ws-mobile.aspx

“… On some Windows Mobile 6 SKUs, VOIP (Voice over IP) is supported. This functionality is based on RTC. So, RTCDll.dll (RTC binary) will be available on some of the WM 6 SKUs. However, on these SKUs, RTC is not released as an SDK, but solely to provide the VOIP functionality. So if an application wishes to use RTC on these SKUs, it is free to do so, but that scenario won’t be supported by Microsoft. …” (May 23, 2007)

My reading of this is simply:

In order to “correct” the speakerphone problem, you gotta “correct” the rtcdll.dll.

And since all we have is a Microsoft binary release of the .dll (there’s no source out there, correct?) the only solution would be to write a new handset-aware (hardware-integrated, lets say, native) sip-client. And that’s not trivial without rtcdll.dll source.

That’s basically why the ROM-chefs havent come up with a solution… yet.

Or:

Is it as simple as getting the correct registry-settings?

I think not. I can think of several reasons why there’s likely no easy/simple registry fix.