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:
“… 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.
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.