[Windows Mobile Development and Hacking General] Tadeusz:
Hi Sleuth,

I have to admit that I never had enough patients to read posts of aboutthemind.

However I agree with most of conclusions you have drown here. Both from aboutthemind posts and your own.

1. Idea to have VoIP client inbuilt and closely integrated with the device system is very appreciated.

2. The client, however should work with the system as you have described. It means that it should actually take over the control of the system and use the peripherals of the device together with the native phone application.

It would be great if we could make the RTC client work properly, but I am afraid, it is very difficult if possible at this stage of the RTC development.

That is way maybe starting a new project could be better solution.

This was about generals, now to back to RTC.

I am not exactly sure if the g711 codec is not capable to work properly both in WiFi and 3G/HSDPA environment. Also I believe, G729 implementation in our mobiles can be done.

I am plaing with VoIP for long time already. Talking about mobile devices, I used to have old HP with PCMCIA WiFi card installed and SJPhone working on it. It was pretty good solution for that time. Later I used Asus PDA with WiFi on board, but without phone option. I used there SJPhone and X-Pro from Counterpath. The last one was commercial product with g729 implemented. And it worked. The processor was Intel 520 MHz. This shows that it could be done. Unfortunately Counterpath has withdrawn this product from the market.

Ok. These were early implementation. There was no integration with the system, it was aimed to PPC with WiFi only and so on.

Now We have WM6 on devices with UMTS/HSDPA on board and I am sure, sooner or later VoIP will be integrated with the system.

At the moment I am usually using Ageet phone, which works perfectly, both on WiFi and 3G, specially with HSDPA. It does not have G729, but it uses GSM, G711, ILBC and Speex, I believe. The only problem with this soft is, that it is not integrated with Phone applet in the WM6. This makes impossible to place calls directly from your contact list. It can import the contact list, but then it does not recognize all does phone number formats, so you need to have them in format, which is accepted by your voip provider. There is also obvious problem with audio redirection to bluetooth headset and receiving a call using green button or headset button.

By the way, I have tested Ageet phone as well as some other commercial phones with many different VoIP providers and environments including my own commercial VoIP network based on PortaOne Switch. All those apps work perfectly with all possible networks.

This can not be said about RTC client. It works with some servers (asterix, FWD in eg.) but does not work with others (PortaOne servers in eg.).

So if we decide to work on RTC, then we should take in mind that there is not only a problem with one way audio in some configurations, but also that this client does not fully complies to SIP protocol and because of that it is cut of from servers like PortaOne, while trying to initiate the call. I have described the problem in my post in your (Shaun's) thread: http://xdaforums.com/showpost.php?p=1241766&postcount=561.

On the other hand Age company is also marketing its SDK. It seems to me that this SDK is really very good, both for PC and PPC environment. The footprint of both versions of their applications is very small . You can see it specially in WM6 if you observe how little memory it takes. Unfortunately the SDK is a commercial product, but they can provide it with G729 included. The question is how to deal with such a project if it would be based on this SDK?

This are only my thoughts. If somebody is interested in taking those thoughts further on, I am open for cooperation.