[Windows Mobile Development and Hacking General] Sleuth255:
I can translate aboutthemind:

He's stating that the WM6 VoIP client is full of bugs but the allure of "free" calling over VoIP has appeal to both hackers and businesses alike so we keep banging away at it. So far, he feels that Schaps is the closest to having a "functioning" native WM6 client (mine works better IMHO ;) ).

He also stated that M$ "supposedly" released this but the WM6 platform has seen no "official" Internet calling application since none of the Operators have decided to pick up on it (due to apparent revenue issues). m$ (Gates) has been silent on the availability since the initial betas. So his point is this:

Is Internet calling even a release level feature of the WM6 ROM? Perhaps not. Perhaps we should instead be devoting our energies to other more proven technologies and building them in to our ROMs.

aboutthemind is far from an idiot; he merely communicates differently.

edit (I have to read posts many times to extract all intellectual content):

abouthtemind also states that the Internet calling app was designed for INTRANET only and believes its IP address/NAT related that causes the issues we experience trying to use it over 3G.

I personally disagree with this because my TyTN works fine with my asterisk server over 3G. What's different about my connection? Very high speed (Business class RoadRunner) server access along with very high speed phone access (AT&T pda connect plan). I use DHCP at my 3G connection and my asterisk server is configured for NAT at both ends. Using G.711, I experience millisecond drops (audio is occasionally choppy) but have both-way audio. I'm also not getting ring-back (can't hear ringing tone on my TyTN while the remote end is ringing) but I believe this is an asterisk configuration problem.

I therefore believe Internet Calling audio issues are codec related and that the one way issue is caused by congestion at our phone's virtual network card. G.711 is all that is support out of the box and, as such, does no compression. This is one of the reasons why INTRANET connections work: more bandwidth at the phone. G.729 is held out as the "holy grail" solution here, but my research indicates that current phone processors my not have enough power to use G.729. I could be wrong here in that a native processor version could exist, but I'm concentrating on GSM610 instead because there is a good compression ratio, and the codec is already optimized for the ARM V4I instruction set (which itself is pseudo-code of course).

@aboutthemind: I remain committed to solving the codec issue for the reasons above. I too want to produce an out-of-the-box solution & will release a new ROM with my fixes if I do. I say "if" not "when" because understanding codec code itself is rocket science... in the examples they actually invoke assembler to do some math processes because the C compiler optimizations aren't quite fast enough :eek:. Besides this, I'm not fully convinced that the WM6 RTC layer is fully ACM codec compliant. There may be an issue at compress/decompress time which only works with G.711 because G.711 does no compression.

Finally, why spend all this energy on WM6 Internet Calling instead of simply cooking in a more proven solution? Here:

Solution must have tight phone integration: press the green button and call or receive call

Solution must have tight contact integration

Solution must use phone earpiece not speaker and have good volume

Solution must transfer over bluetooth to car handsfree

Right now, Internet Calling, while not there for sure, actually comes closest and therefore holds the promise of working with all of the above. I believe that fixing the codec will solve points one and two. Hardware itself causes issue 3 and may only be solvable by changing phone hardware. IMO, a quick tweak should solve issue 4 and I will start working on that when I get a reliable GSM610 codec working.