Develop Bugs

{Troubleshooting} Solving the Vonage VoIP/SIP WM6 client Issues

The goal of this thread is to get Vonage softphone accounts working with WM6 Internet Calling again. I'm going to use my cosmic moderation powers to delete without notice all posts that don't actually contribute to this effort. I don't want any "how do I set up provisioning..." posts cluttering up this thread. If you are having this issue, please respond to the poll so Vonage can get an idea of the affected XDA posters. If you answer no, then please post here! TMK all Vonage softphone users are affected, so you would be one of a kind.
To aid with troubleshooting, I'm also willing to (temporarily) share my Vonage softphone provisioning information with trusted SIP gurus who wish to participate. Post here if you're interested.
Ok, Here's what we know:
Sometime during the week of June 18th, Vonage softphone accounts stopped working on all WM6 builds that had Internet calling activated
SJPhone however, continues to function normally.
WM6 Internet calling still functions normally with other SIP service providers.
Given this information, I installed the Airscanner packet sniffer on my Tytn. The 30 day free trial for this sniffer can be found here. This nifty little utility creates packet captures that can be read by Ethereal. The current version of Ethereal is located here.
I next attached Airscanner to the IEEE 802.11b/g Compatible WiFi adaptor on my TyTN, connected to my home AP and turned my TyTN's phone radio off. Then I proceeded to capture the sip initiation sessions with SJPhone (worked fine) and WM6 Internet Calling (showed "No Service" after long "Searching" delay). Everybody who wants to participate in this exercise should connect this way btw. Let's not cloud the troubleshooting effort with the ideosyncracies of 3G connectivity.
Here are the relevant packet captures (click images for full size versions in new browser windows)
Internet Calling Registration Packet
SJPhone Registration Packet
Initial Analysis
As it turns out, the SIP register packet sent by Internet calling is being ignored by Vonage's SIP servers at sphone.vopr.vonage.net:5061. WM6 Internet Calling retrys the original Registration request 11 times then gives up. However, the registration packet is immediately accepted when sent by SJPhone. This points to a formatting issue with Internet calling's SIP Registration packet.
SJPhone is also sending a binding request to the SoftJoys STUN server but you can clearly see that the response from Vonage is occuring directly directly after the STUN bind request and is in response to the original UDP packet and not the STUN bind packet (response from softjoys is not shown but is further down in the conversation). Conclusion: STUN isn't the reason why SJPhone is succeeding here.
So it would appear to be something in the REGISTER request itself. Here are the differences I've noticed:
the REGISTER sip URI contains the :5061 port suffix in SJPhone and not in WM6. However, both programs are sending the request to port 5061 at sphone.vopr.vonage.net. This probably isn't the issue
the source port for SJPhone is 5060 and for WM6 its 1153. This may be the issue IMO. Perhaps Vonage added firewall rules that restrict outbound connections to known SIP ports. I'm working on coming up with a way to test this currently.
the contact binding information is completely different between WM6 and SJPhone. Could this be an issue? Any SIP gurus out there, feel free to comment!
Is anybody seeing anything else here?
Next steps:
Once we've identified the likely causes for the failure, I will get on the phone with Vonage technical and go over our findings. I may even link them to this thread. Hopefully the outcome will be a quick change to Vonage's firewalls or SIP servers. Also, it would be nice to find out more about WM provisioning/registry settings to handle these:
How to provision STUN servers
How to force the source port from a random 1000-2000 to 5060. BTW: setting the enableport5060 value to a 1 doesn't change this. It merely causes Internet Calling to start listening on port 5060.
Let's get this issue solved so Vonage Softphone accounts can once again work with Windows Mobile!
... or we Vonage users could just close our accounts and just install asterisk or use a different service that works I guess...

One of our posters has already engaged Vonage Customer care & told them to use this thread as a reference. Hopefully we'll get an answer on this ITNF.

I've added a poll to determine affected users. If you have a Vonage Softphone account, please respond!

I recently upgraded my tytn to WM6 and was about to get Vonage for my phone, and i found your post saying it wont work so i set out on a long search of the internet for a possible solution. Below is a link to a blog entry at MSDN which talks about making voip work with vonage on wm6. Can you try it and let me know if it works?
http://blogs.msdn.com/cenet/archive...-rtc-voip-functionality-work-with-vonage.aspx

Interesting link. I wonder how one sets the RTC initialization flags in the ipphonecanvas client ?

Well, I set up a Trixbox ([email protected]) PBX using the nerdvittles virtual appliance & then trunked it to my Vonage softphone account. Then I set up a remote extension and provisioned my TyTN to attach to my PBX. After an afternoon tuning NAT, everything now works just swimmingly. Even 3G works, and I hnow ave audio in both directions too! Based on this, I believe that the issue lies in the way Internet Calling sets up the contact portion of the register packet that is causing the Vonage SIP servers to error out. This is why I never get a response, not even an error response, to my REGISTER packets
I've got three bugs to eliminate in my asterisk configuration and once they are fixed I'm thinking that I have a workaround.

Final response from Vonage:
We understand from your email that you are experience problems using the SoftPhone with Windows Mobile 6.
The SoftPhone application was designed to be used with a PC and not a Pocket PC running Windows mobile. I have pasted the link below that will provide the PC requirements needed to use the SoftPhone.
http://vonage.com/help.php?category=153&nav=5
If you have any questions, your Vonage team is available to assist you 24 hours a day, 7 days a week. Contact us whenever and however it suits you!
Click to expand...
Click to collapse
Based on this, it is clear Vonage doesn't want to deal with the root cause of this issue. Too bad, IMO because there's a vast plethora of WM6 devices now out there which could connect to Vonage services if this was resolved. Business lost for Vonage it would seem.
Based on their response, my advice for Vonage users would be to close your softphone accounts & find a more suitable provider such as sipphone.com. FTTB the asterisk solution is a (very usable) workaround but there's no guarantee that Vonage won't shut that down in the same manner.

Any new update which u can share with us ?
the problem i have now is i can make calls , but i can't receive any incoming since vonage did something .
I used it on my pda and worked ok .
if u find any please update this thread

glad i found this thread, i was racking my brain as to why this wasnt working... i only just got a TyTn to replace my POS HP 6915, so naturally I got a WM6 rom for it mainly for using my Vonage Softphone through the voip feature.... great
i guess if vonage are wiping their hands off it the only thing to do is see what somes in the way of updates from M$ ?
or someone to do a bit of reverse engineering?

Just found this thread...
... after struggling all weekend. I am presuming that there's been no progress on solving the problem with the WM6 client. Damn shame Vonage doesn't want to play nicely.
I see uninstallation in my future.
Dan

On another related note, in order to used the WM6VoIP.cab files, does the device need to be application unlocked?
Thanks!
Dan

I just cant resist let me in
HELLO GOVERNOR LONG TIME NO MIND TO BUG
BRING ME UP TO SPEED IT WORKED AND THEN STOPPED SO LETS GO OUTSIDE THE BOX. IT WORKS IT JUST NEEDS TO BE REMINDED THAT IT IS WORKING NOT TWEAKED TOLD TO NOT REGISTER. IT WORKS CAUSE IT WORKED ONCE SO FIND WHERE IT IS STOPPING IT SELF.
ANY WAYS IF ITS OK IM IN JUST NEED SOFT PHONE APP WHAT DEVICE I SHOULD USE (GOT THE\M ALL) AND LETS SEE IF WE CANT BEAT A PREVENTION TACTIC FROM 2 GUYS THAT COPIED A FOREIGN SOLUTION.
IM BACK ONLY FOR U CHIEF

Hope I'm not committing a faux pas by bumping this, but I haven't been able to find any up-to-date information on this anywhere. Has anyone solved this problem? Or did everyone give up?
I just switched to Vonage, and added Softphone without realizing that no one has a current method of connecting to it with WinMo (via apps or native VOIP support), so I'd really like to get it working

A little question..Voip over 3g--it's possible or not?????

As in the subject...i wanto to make voip calls over 3g networks, not wifi..!!!
It's possible or not??

with Skype 2.2beta works nicely

diektronics said:
with Skype 2.2beta works nicely
Click to expand...
Click to collapse
Oh..i didn't say this..!! Skype is perfectly functionally...but..i wish use integrated voip of wm6..!

I use Internet Calling with my TyTN over 3G on AT&T (PDA connect plan) to my local asterisk server. My server sits behind NAT and my TyTN is on extension 500. My Asterisk server has a trunk connection to my Vonage softphone account for outbound calling. Overall, it works very nicely. There's a bit of breakup, but its quite usable. I'm working on a GSM610 codec now that will improve things even further.
My main issue is power. VoIP over the 3G data connection dramatically reduces battery life. It's like constant surfing with PIE.

I use it over T-Mobile's EDGE. Because this is not real 3G, regular calls can't be received while there is a data stream, but my VoIP provider allows me to forward to my regular phone numbers when the VoIP number is off line.
Bottom line, it works perfectly fine with the included software in WM6.

listening sockets and ping issue over WIFI on some devices

Hi,
I'm the developer of this application:
http://forum.xda-developers.com/showthread.php?t=586654
Two people are claiming that my app doesn't work over WIFI on their device.
In fact they can't even ping their device's Wifi interface IP address, although internet works.
So, outbound connections works, inbound connections doesn't.
And they have no firewall installed. How it that possible? Is there a rom/driver issue on some HTC devices? (one user has a touch pro, the other a touch cruise)
The weird thing is that the incoming connection works over USB (with the virtual network connection created by activesync/WMDC), pings succeed and my app works.
Has someone ever had the same issue?
I know it's not very common to use applications that need to handle incoming connections on a WM device...
It would be great if someone had an idea about the root of the problem!
Julien

[Q] VPN on Rhod 100 TP2

I have the latest Froyo6 build on my Froyo TP2 Rhod_100 UK
I have been trying to set up the VPN, but I can not get it working. Does anyone know why and how I can sort this out please?
PS. I also tried to run a VoIP (SIP) client (3CX) on the machine, but that too does not work.
My airtime provider is Vodafone UK and they have assured me that both are enabled on my account at a princely sum of £15 per month! Needless to say at that cost I am dead keen to make this work.

jonners59 said:
I have the latest Froyo6 build on my Froyo TP2 Rhod_100 UK
I have been trying to set up the VPN, but I can not get it working. Does anyone know why and how I can sort this out please?
PS. I also tried to run a VoIP (SIP) client (3CX) on the machine, but that too does not work.
My airtime provider is Vodafone UK and they have assured me that both are enabled on my account at a princely sum of £15 per month! Needless to say at that cost I am dead keen to make this work.
Click to expand...
Click to collapse
Can you get either to work on wifi?

I know there were some Chinese users trying to get the VPN to work, and couldn't.
I haven't tried, as I have no use for a VPN on my phone lol.
Also, I have known people to get SIP working, but it wasn't so great from what I heard...

Sorry I was not getting alerts and the thread was not showing up in my subs....
If I use WiFi then I am at home and do not need the VPN, but the SIP Phone DOES work and very well.
If I use the WM as a gateway for my laptop, then the laptop can run a VPN and SIP Phone via the phone. If that makes sense to you. Thus the Router running the VPN is working and the config works, and the mobile operator has set up the service. So this is just the phone settings - I believe.

jonners59 said:
Sorry I was not getting alerts and the thread was not showing up in my subs....
If I use WiFi then I am at home and do not need the VPN, but the SIP Phone DOES work and very well.
If I use the WM as a gateway for my laptop, then the laptop can run a VPN and SIP Phone via the phone. If that makes sense to you. Thus the Router running the VPN is working and the config works, and the mobile operator has set up the service. So this is just the phone settings - I believe.
Click to expand...
Click to collapse
If I had a VPN I could connect to I would test it out...
Maybe its a misconfiguration in Android? broken driver or config?

I do not know. It tells me nothing. The settings are as per the router config. How do I find out what is incorrect/broken etc...?

Can you give as many details as possible on the type of VPN I'm trying to connect to?
It's probably not working because none of the devs use that function - and can't debug it without trying to reproduce your setup.
I might play with it a little as it would potentially let me remotely schedule MythTV recordings safely, but it would be pretty low-pri for me.

I am using at this stage a simple PPTP setup for now. The Android settings are minimal - username and PW, and that is it.
But my laptop, which works has more settings o configure. I.e. MSCHAP and MSCHAPv2
Point to point MPPE
Security 128b and/or 40b
Allow BSD
Allow Deflate data comp
Allow TCP header comp
Does this help

OK, sometime in the next week or two I'll try to get PPTP up and running using similar parameters. I've been meaning to do it in general (not phone-related) for other reasons anyway - but it's been a low priority for a long time.

Entropy512 said:
OK, sometime in the next week or two I'll try to get PPTP up and running using similar parameters. I've been meaning to do it in general (not phone-related) for other reasons anyway - but it's been a low priority for a long time.
Click to expand...
Click to collapse
Why not OpenVPN? Seems like it would be easier/more standards-compliant that a craptacular PPTP VPN .

arrrghhh said:
Why not OpenVPN? Seems like it would be easier/more standards-compliant that a craptacular PPTP VPN .
Click to expand...
Click to collapse
I'll look into what VPN options Android supports - although for the OP, he may have specific reasons forcing PPTP.

arrrghhh said:
Why not OpenVPN? Seems like it would be easier/more standards-compliant that a craptacular PPTP VPN .
Click to expand...
Click to collapse
Because I am working with Draytek, my router. Vendor to set up the VPN and this was the. First config as it was the simplest. Seems everything else works, just. Not the. Phone. The phone too has PPTP as a standard setting.

Eh, I prefer to avoid PPTP like the plague if I have any choice. Most companies don't provide a choice, so I figured that's why you were locked in.
If you do have a choice, I would try something different. That's just me tho, I'd prefer open to closed any day if I had the choice .

Just a side note - the built-in Android VPN support uses pppd. The ril currently uses "killall pppd" to disable mobile data. If you're using both at once, then this will kill the VPN too. This is a stupid flaw in the current ril code, which is fixed in the "initpppd" branch of my ril repo. (But the initpppd branch depends on a number of rootfs fixes before it is usable, and stinebd has not merged any of it yet.)

highlandsun said:
Just a side note - the built-in Android VPN support uses pppd. The ril currently uses "killall pppd" to disable mobile data. If you're using both at once, then this will kill the VPN too. This is a stupid flaw in the current ril code, which is fixed in the "initpppd" branch of my ril repo. (But the initpppd branch depends on a number of rootfs fixes before it is usable, and stinebd has not merged any of it yet.)
Click to expand...
Click to collapse
Thanks for the reminder of that, I remember the discussions on the dev list.
I'm going to shelve poking at the VPN stuff until the RIL overhaul stabilizes and gets mainlined in this case.

Entropy512 said:
I'll look into what VPN options Android supports - although for the OP, he may have specific reasons forcing PPTP.
Click to expand...
Click to collapse
OK, please excuse slowness of response. As arrghh knows from another thread I am in transit across Europe. I reached my destination, Italy and have spent the past few days getting internet access *broadband virtually does not exist here unless you are in a City, so I have to use a very slow mobile broadband).
I am not a techie, but I am a willing player with some knowledge - dangerous, I know. I have been assisted by the manufacturer of my Router, a Draytek 2820 to set up a VPN. We may make it a more sophisticated VPN later, but pptp is the easiest. I have it working on all laptops and PCs, including this old banger here in Italy. What I can NOT do, is get it working on the phone. I think it is communicating with the router, but it is not getting through.
PS the PCs and Laptops are all Linux - Ubuntu 10.10
Hope this helps

I'm one of those Chinese who tried using VPNs on my Raphael, but failed of course. Actually, neither on WM, nor on Android, neither via pptp, nor via l2tp over ipsec. What I wanna remind is VPN on most Android roms on hd2 works fine, but some roms also cannot support vpn.
If you have enough time, I don't know how to pray for, would you please explore l2tp over ipsec? Because in many cities in China, pptp is also blocked by ISP. And I can provide a test account if anyone needs it.
Btw, I believe vpn is necessary when connecting a public wifi
Sent from my MSM using XDA Premium App

One more report, vpn in pptp could not work..

At this point - I'm going to hold off on poking at this until highlandsun's new RIL settles out and is officially committed. Some of the dev traffic correspondence indicates that the way we currently handle PPP is incompatible with VPNs. His new ril + rootfs combo that changes the pppd control architecture MIGHT solve some of the PPTP issues, I haven't tried them yet.

See it.
May your works come out soon~

[Q] Google Now voice search firewall issue? [SOLVED]

If I try to use Google Now's voice search on the wifi at work, all I get after it listens to me speak is "Recognizing..." for about 5-10 seconds, then it just goes back to "Tap mic to start speaking." If I do this on cellular data, or my wifi at home, Google Now works fine, which makes me think this is a firewall issue at work. Anyone found any information yet for this new service yet about required ports or the like?
Cell reception is spotty in my building at work (that's why I use the wifi there), so I'd love to figure out the issue.

definitely a firewall issue
An update: I just put my GN on a subnet that has all ports open and Google Now's voice search worked fine. Put it back on the DHCP subnet, and were back to failure.
Anyone else seeing this?

more info
FYI: It's getting stuck on "Recognizing..." even though I have offline voice recognition installed. Obviously, searching won't work without internet access.

I ran into this too, on our work network (where we block almost everything). Works fine at home. Did some sniffing on our firewall and found that my phone was trying to connect to 74.125.142.192 (ie-in-f192.1e100.net - which is Google) on port 14259. I added a rule to our firewall to the connection and now Google Now works perfectly. I have nothing to confirm this is the exact IP and port it will always use, though. I'll keep testing it to see if it stops working.
Interestingly enough, when testing I found that if I left the phone on "Recognizing..." long enough, it eventually worked. I wasn't capturing packets at the time so I couldn't see how it did that.
I'll update if I find any new info...

628
Thanks! Opened that port and voila - voice search is fine now. Thanks!

Confirmed for me as well, and it took awhile and I needed to open up a few more ports.
Destination ports are 5228 and 14259, so I just put the whole range in.
5228:14259
Google server IP's are:
74.125.142.192
173.194.74.192

5228 is needed for push notifications from Google services. I think you could get away with only opening the two ports you mentioned. I do and everything seems to work.
Sent from my Galaxy Nexus using xda app-developers app

My firewall is blocking on port TCP 14259 to a slightly different IP address of 74.125.132.192 which resolves to wb-in-f192.1e100.net
I am accessing the service from the UK.

chugger93 said:
Confirmed for me as well, and it took awhile and I needed to open up a few more ports.
Destination ports are 5228 and 14259, so I just put the whole range in.
5228:14259
Google server IP's are:
74.125.142.192
173.194.74.192
Click to expand...
Click to collapse
Never ever create firewall rules for ip address ranges, unless those ranges are on a private network and you can guarantee exactly where they go. Google, like many major corporations, provides hosting services, and due to this, simply because an IP is registered to Google [or any other corporation], it does not mean it's actually Google who's using it.
The best practice is to allow host names only (urls) when creating firewall rules (most often by wildcard variables - i.e. the asterick * - https://*.googleapis.com for example). IP addresses are dynamically assigned, so just because a specific connection at a specific time resolves to 74.125.142.192 does not mean it will resolve to that IP tomorrow, let alone 10 minutes from now.