Is there a way to use the VOIP hack to enable service on the new @home t-mobile network? I know the VOIP works with standard SIP services but is there a way to make it work on this new network?
nope, tmo uses a different protocol that basically tunnels GSM through the WIFI connection.
I use http://www.tivi.com/ for making VOIP calls, its free and i can call any SIP number, it workes perfectly with T-mobile Dash... you just need a WIFI connection...
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
is there a way to enable the provisioning xml file to enable outgoing voip only?
I have a router with all of my settings and every time i go to use the hermes, it de-registers my router ??
I have a softphone on my pc and it works great without messing with my settings on my main router.
any ideas?
Hey all,
I was wondering how many guys here have voip enabled (SIP account) on their mobile. And are you leaving your pda on the whole day/night or not? Because when voip over wifi is enabled, when you power off your device you don't have any wifi anymore so it don't make sense to have voip (excpet for calling out).
I have my voip also for incomming calls.
Grtz,
Hi,
I had the native VOIP support enabled (separate cab) on my previous rom (Black Satin WM6.0), but now I installed the italian "Parabola" rom and I didn't install the voip yet.
I remember that there is an utility like "advanced configuration" that enables you to chose to mantain wifi on also when the screen is switched off in standby mode. I used that because on outcoming call after XX second the system went in standby, the wifi disconnected and I lost the call.. very annoying. After the trick everything was ok!
But I never used the phone as incoming VOIP call.. just for test one time because I use a softphone on my notebook.
Ciao ;-)
Just a quick question, has anyone gotten the inbuilt "Internet Calling" WM SIP client working on the TP2?
I've been reading all of the threads that I can find on this site to do with SIP, VoIP etc... and trying to get the InternetCalling app working on my TP2. I'm currently running Sergio's Cell Pro V11 ROM, but I've also tried it on the NRG Phoenix ROMs.
It seems that no matter what VoIP setup cab I use to install the client and it's constituent parts, no matter what registry settings I alter, and no matter what SIP provider I try, it always ends up at "No Service" after "Searching".
I just wondered if anyone had experience of getting it to work, either over Wifi, or over 3G?
I've also investigated whether the problem is that Vodafone UK block SIP traffic on their network, but I've not come across anything to say if they do conclusively one way or another?
I am getting the same problem, I think I am not using the right SIP server. On one of the tutorials it tells me to use my SIP server. I am with Telus but I don't know what the sip server is.
Same here. I could not get internal SIP working.
And fring is a resource hog. There is another software (talkonaut), but I don't have enough experience on that one.