yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] codesplice:
Thanks for the excellent information. I have noticed that most clients other than Sipdroid seem to have issues maintaining a connection to PBXes.org. I've set the reconnect interval to 2 minutes as you suggested, I'll see if that helps. Also, I'm unable to connect at all if I set it to use TCP. It just sits endlessly at Registering. Going out of town for the weekend though so I will play with it some more next week.

In the meantime, I think that GrooveIP has (for me) the best combination of quality, reliability, and integration. Sipdroid + PBXes could be a solid contender if it offered integration with the stock dialer.

Well put, thanks for covering for me!

Bingo!

Gimli claimed 43, no matter what that elf says. More like "42" as in the answer to "What do you get when you multiply six by nine."
[Samsung Galaxy Nexus] martonikaj:
Definitely look into getting assigned a new number.

So if you're not in a good data situation you can receive calls over the cell network.
[Samsung Galaxy Nexus] martonikaj:
Well that may be true that T-Mobile could have stepped up its speeds by moving to 84mbps HSPA (or dual-carrier 42mbps), it wouldn't be infinitely scalable. It'd really just be a stopgap to buy themselves time to build their network more.

My understanding is that moving to LTE has the added advantage of better network utilization and scalability to even higher speeds in the future. When they deploy it, they'll be using "LTE Advanced" also, effectively leap-frogging the other carriers who are still on their first release of LTE.

I personally would love if T-Mobile didn't go the LTE route, but they've made their decision. Its probably the best choice in the long run for T-Mobile to start getting with the standards, and deploying LTE Advanced on the same frequencies as other carriers is one way for them to help their market position.

And as far as frequencies go, if I remember properly T-Mobile plans on moving HSPA to 1900mhz, using 1700/2100 (AWS) for LTE. Correct me if I'm wrong.
[Samsung Galaxy Nexus] Nxxx:
Problem with HSPA 84 is that what phones would support it?
[Samsung Galaxy Nexus] noneone:
Original Tolkien book has Gimli's kills at 42. Origional feature length movie is silent on the issue. Exented cut movie has an extra scene with Gimli at 43, Legolas at 42, the elf shoots a fallen orc cause it was "twitching" and claims 43 as a tie.

Book, 42, movie, 43. I'm going with the book, Gimli's kills at 42. :)
[Samsung Galaxy Nexus] martonikaj:
Well, T-Mobile would just continue to get manufacturers to make them specific phones with the higher 84mbps HSPA+ radio. Just as right now where T-Mobile is (kinda) getting the OEM's to make 42mbps devices while they're already making a 21mbps + LTE version for AT&T and a EVDO + LTE version for Verizon and Sprint, all of whom are bigger partners/buyers that take priority over T-Mobile.

As I said on this point before, I think it would help T-Mobile in the long run to make their network look exactly like AT&T's so that they could get the exact same phones, rather than keep asking OEM's to make special phones for them. Any decrease in the barriers for T-Mobile to pick up new customers and new top-end devices is a good thing.
[Samsung Galaxy Nexus] kevin935:
I really wanna know what the sound quality is about under only 3G/4G, but NOT WIFI. It's very important when I go travel.

Thanks
[Samsung Galaxy Nexus] yerda:
I understand that with the tasker profile, when within a stable wifi connection, you will only receive the call once from the google voice VoIP which does not take any minutes. Everything is smooth and awesome.

When you are outside wifi or don't have it on, then, and you are using 4G data and someone calls you, what happens? Do you receive two calls, one from google voice VoIP on the 4g data that doesn't take minutes, and one on the reliable Tmobile service that does take minutes? And you get to choose which one you want to pick up with?

Thanks in clearing this up!
[Samsung Galaxy Nexus] javapop:
I am trying to set up an old droid using grooveip; it is no longer activated. When adding my Google Voice acct info, it automatically uses my current Verizon cell number associated with the acct. How do I bypass that? Do I just need to set up a new GV acct?
[Samsung Galaxy Nexus] martonikaj:
Its just identifying it for purposes of voicemail because that account is connected to another phone too. The numbers are already "connected".

GrooVe IP doesn't need a phone number though, just your Google credentials. It also doesn't need the Google Voice app to be installed.

---------- Post added at 01:18 PM ---------- Previous post was at 01:16 PM ----------

If you're standing still in an area with fantastic HSPA+, the quality will be good. Anything less than that and I wouldn't want to rely on it as my only source of calls, especially for anything over 5 minutes long. I personally had issues with latency/lag/delay (using GrooVe IP).
[Samsung Galaxy Nexus] jgrinst1:
Personally, I have found only Nimbuzz to work (fairly) consistently with T-Mo 3/4G network. And that's with setting the GV PBXes account as the Nimbuzz-out SIP account. (I'll get technical if anyone wants me to)

My wife swears at me is I use anything else, other than straight cellular...

I'd use NB as my Wifi also, except that it doesn't have caller ID/Name translate from Phone book :(

Otherwise, it's really good for NB to NB calls over all media.
[Samsung Galaxy Nexus] codesplice:
I have GrooveIP/Talkatone/CSipSimple/whatever-other-VoIP-client-I-may-be-using set to only place and receive VoIP calls when connected to wifi. This way, I only ever get a single incoming call at any given time. Otherwise, yes, you'd receive two incoming calls and would be sort-of able to select which one to answer. I say "sort-of" since it's not always easy to switch to the other call handler when one is already occupying your screen. It can be done though :)
[Samsung Galaxy Nexus] codesplice:
Okay, I'll give you that. It's been far too long since I've read the books. I should probably shoot through them again shortly to brush up - I've got a LotR-themed wedding in October ;). Just gotta finish getting through Steven King's Dark Tower series first.

Namarie ;)
[Samsung Galaxy Nexus] Headcase_Fargone:
How do you solve the problem of Google Voice ringing both "lines" when someone calls you? If I leave GV set to forward both to GTalk and the Nexus it makes it difficult to answer the call in Sipdroid. When that happened with GrooveIP the two apps (GrooveIP and default dialer) would fight for the call.
[Samsung Galaxy Nexus] codesplice:
The first post explains how I use Tasker to automatically put my phone into Airplane Mode (disabling the cellular radio) when I'm connected to wifi. I also have whatever VoIP app I happen to be using set to only work on Wifi. I leave Google Voice set to forward to both my "lines", but I'm only ever connected to one or the other - either Wifi or Cellular data, never both.
[Samsung Galaxy Nexus] Headcase_Fargone:
Brilliant! There have been times when Tasker hasn't triggered my wifi off profile for whatever reason and I've been left with calls being forward to GTalk instead of cellular and I hear about someone trying to call me the next day. I'll give this a try.

I tried installing the latest CSipSimple build but kept getting unauthorized errors registering with my PBXES.org account. Same password works fine with Sipdroid though. Weird.
[Samsung Galaxy Nexus] codesplice:
Yeah, I haven't had much luck with PBXes + CSipSimple. I get the same unauthorized errors - even after it's successfully connected! It'll connect, I'll put my phone away, and the next time I look at it I'm no longer connected. Bah humbug. Silly PBXes and their non-standard SIP stuffs.

I'm running CSipSimple + SipGate right now with good results. Be sure to check out this post by natesilver for some nice tips on making VoIP work a bit better:
[Samsung Galaxy Nexus] jgrinst1:
Nice find on the tips post about latency! I'll check it out.

One thing with PBXes - it's squirrelly. After you have set it up with Sipdroid, you have to make sure your password on the website is correct. Sipdroid can read it but other Voip apps may have trouble.

Login to PBXes. Click on "Extensions" and then "Sipdroid <200>" extension. Highlight your password, erase it and re-enter it. Click "Submit" at the bottom, then the red "Apply changes" at the top of the screen. This should fix your sign in problems.

Registration, keepalives and TCP/UDP are also good things to play with regarding your sign-in state.
[Samsung Galaxy Nexus] mixersoft:
But I'll still get VM and notification on GVoice (not carrier), when the data picks up again from spotty connection, correct?

I don't need to be accessible all the time, and I suppose I could just forward GVoice to mobile if I travel completely out of coverage.

Is there a battery life implication if I skip all the tasker steps?
[Samsung Galaxy Nexus] Headcase_Fargone:
Yeah I actually had to go through these steps just to get Sipdroid working properly originally. CSipSimple still gives me unauthorized errors.

I've love to give CSipSimple and Sipgate a try per the post above, but at this point I've tried so many solutions and Sipdroid/PBXes.org is working "well enough" that I'm just kind of burnt out with the whole VOIP thing. Glad to know there's an alternative out there though.
[Samsung Galaxy Nexus] codesplice:
Thanks for the tips, I think I've finally got CSipSimple playing nicely with PBXes.org. We'll see if that continues... Any specifics on the "registration, keepalives, and TCP/UDP" that I should perhaps try to adjust?

So you're really talking about doing a VoIP-only set up, only relying upon the carrier network for data access? Yeah, I guess that would work as you describe then. You'd only know about any missed calls (due to lack of data service) when you regained data and the notifications were pushed to the GVoice app.

I'd still recommend using the Tasker steps if you spend a large portion of your time connected to a reliable wifi network - Wifi is much more battery friendly than the cellular connection, so toggling Airplane Mode will still have a positive effect.

The big thing that draws me to CSS over Sipdroid is the integration with the native dialer. I only want one "Phone" shortcut on my homescreen. Any call that I try to make with that should use the appropriate connection - VoIP if it is available, otherwise cellular.
[Samsung Galaxy Nexus] Headcase_Fargone:
Sipdroid does this. The only issue I have is that it doesn't give you the option of "ask every time" like some apps do. If Sipdroid is connected and you dial out using the native dialer it will go through Sipdroid no matter what.
[Samsung Galaxy Nexus] jgrinst1:
If you can change the SIP transport to TCP you'll be doing your battery a big favor. The defaults for regs and keep-alives are fine if you can keep connected. Otherwise, reduce the registration interval until about the 3-5 minute range. I keep connected fine at 300 seconds.

Perhaps I'm too anal about this too... I'd use the native SIP stack with PBXes if it were a bit more friendly/robust, then I could ditch all third party apps.
[Samsung Galaxy Nexus] Luxferro:
I find pbxes.con to be at better then grooveip. I used sipdroid to setup a pbx account w/ gtalk routing ect. Then change the password for the extension and then enter the info name-200 password into the native voip setting in ICS. Remove sipdroid and then your all set.
[Samsung Galaxy Nexus] :
Whoops!
[Samsung Galaxy Nexus] codesplice:
Ah, so it does. Somehow I was overlooking that this was the default behavior. As for prompting, is it perhaps managed by the Settings -> Call Options -> Preferred Call Type setting? I see options there for Sipdroid only; Sipdroid, when available; Phone; and Always ask.

Thanks for the tips. As for the native SIP stack, I really just want the option to only use it on Wifi and then it would be golden!

Agreed, once I went back to using SipDroid (so it keeps a reliable connection to PBXes), this approach does seem to offer better quality than GrooveIP - likely because of proper VoIP codecs between my phone and the pbxes.org servers.

I think I'll update the OP shortly with these findings - thanks for contributing!
[Samsung Galaxy Nexus] Headcase_Fargone:
Would this be possible to automate with Tasker? You could probably execute a script that changes the built-in SIP settings based on wifi connectivity...
[Samsung Galaxy Nexus] HemRoyd:
I'm just curious what everyone's experience has been with successfully entering DTMF tones via WiFi and the various dialer options.

I recall in the old days with my Nokia E65 and voip.ms - it was very codec dependent, but at least Symbian had the options available, LOL.
[Samsung Galaxy Nexus] muyoso:
This has me seriously considering eating an ETF fee from Sprint.

I'd love to get VOIP calls when at home and cell calls while out, but my only concern is how everything integrates with the stock dialer. If I use Voice Actions to say "Call Walmart", will that work correctly using a VOIP solution?
[Samsung Galaxy Nexus] BrianDigital:
Well I know groove IP intergrates with the stock dailer and if you use one of the auto airplane mode when connected to WiFi the call go through
[Samsung Galaxy Nexus] codesplice:
I haven't seen anything for it so far, and I have done a little bit of looking.

As far as I can tell, the DTMF tones work fine with each solution I've tried - GrooveIP, Talkatone, CSipSimple+SipGate, and SipDroid+PBXes.org/GVoice. I've had no problems with any of the in-call menu's I've encountered.

Correct. If the VoIP client is set up to integrate with the stock dialer (essentially intercepting the Dial intent), then it will continue to place the call in the configured manner regardless of how the call is initiated.
[Samsung Galaxy Nexus] codesplice:
I've updated the OP with a wee bit of information on using SipDroid+PBXes.org for free, easy-to-configure VoIP calls made via your Google Voice account.
[Samsung Galaxy Nexus] harveydent:
Nice title change! Hopefully, this'll steer more people away from carrier contracts
[Samsung Galaxy Nexus] codesplice:
Thanks. That's kind of how I've been promoting this thread elsewhere (to the tune of 600+ unique clicks it seems), so I figured making the title match would be a good move. Also, :cowboy: cowboy smiley.
[Samsung Galaxy Nexus] kcshmo:
Hi, the card activation kit, is that just a Tmobile sim card? I have a few of those lying around. they were never used, it came with the previous phone that I upgraded with Tmobile, and the sales guy forgot to remove them. Can I just activate that with the $30 plan?
[Samsung Galaxy Nexus] codesplice:
The activation kit consists of a SIM card and an activation card. You can't (easily) activate a SIM without the activation number on the activation card.
[Samsung Galaxy Nexus] kcshmo:
Thanks, no big deal. The activation kit is 99 cents on the website, don't know how much they will charge me for shipping. It's cheap enough. Thanks again
[Samsung Galaxy Nexus] illwafer:
awesome guide. thank you very much.

i tried SIPdroid today over WIFI, and although it connected using HD/64bit, it was choppy and unusable.

on the other hand, grooveip worked flawlessly although it had the typical tinny VOIP sound...but still very good. no lag, no echoes.

both were easy to set up, so i'll play around with them and see if i get different results.
[Samsung Galaxy Nexus] :
Is any functionality lost if you delete sipdroid as you mention?
[Samsung Galaxy Nexus] martonikaj:
Shipping is free. Arrives in about 5-7 days (standard USPS ground), and the card is pre-loaded with a few $$ on it already.
[Samsung Galaxy Nexus] codesplice:
You only need one VoIP client - either SipDroid or native SIP. Nothing is gained by having both configured - though SipDroid does provide more options.
[Samsung Galaxy Nexus] muyoso:
So here is a question. Using your method of having VOIP at home and cell service while out, if you make a call while out its going to show the Tmobile number on the caller ID of whoever you call right? Is there anyway to have it show the Google Voice number on caller ID so that people I call won't be confused by the weird number? Im gonna guess that the answer is no. . . .
[Samsung Galaxy Nexus] codesplice:
The Google Voice app allows you to choose how outgoing calls are placed. Choose to make all calls via Google Voice and the recipient of the call will see your GV number for the caller ID.
[Samsung Galaxy Nexus] muyoso:
Even when you are placing a call using the Tmobile minutes instead of VOIP? That is awesome.
[Samsung Galaxy Nexus] codesplice:
Yup. On any other phone, you would place a GV call by dialing a special GV number (I forget what it is....) and then entering the number you wish to call. The GV system would then call you back. Once you answered, the call would be connected via Google Voice to the desired party.

Since we're on Android, the GV app is able to handle this messy callback business for us, seamlessly. It is actually placing a callback request (using your active data connection) and then connecting you to that call.
[Samsung Galaxy Nexus] muyoso:
Thanks so much for taking the time to explain this stuff to me and making this amazing thread.
[Samsung Galaxy Nexus] codesplice:
Glad to help!
[Samsung Galaxy Nexus] xdp:
I'd like to start playing around with these SIP VoIP options. I'm sure this has been asked but the search feature on XDA is currently missing. The OP says that I can use the option in Sipdroid to create a new PBX linked to Google Voice automatically. It then says this account will use the same login credentials. Same as my Google account? How could it get my password when I only use the built-in Android authentication to give it access? Is it smarter to create a PBXes.org account separately and provide that info to Sipdroid?

Edit: I actually don't see the option in Sipdroid to use Android's built-in authentication. Is the recommended setup to create the PBXes.org account first, or set it up via the New account button in Sipdroid and then change my password later?

Also, what are the latest opinions on Sipdroid vs. CSipSimple? I'm reading about peopling have setup issues with CSipSimple but the app is highly rated on Google Play.
[Samsung Galaxy Nexus] austriker27:
This is fantastic. I am oh so tempted to do it. Although I still would like to stay on the 'qwerty' bus so I cant decide between a G2/Desire Z or Nexus. I suppose I could do the same prepaid tmobile plan with the G2 (has correct bands)

Either way, with the news about the judge blocking gnex sales are people flocking out to buy them? The way I understand it now is that samsung is blocked from selling it, but carriers and businesses (best buy, google play etc) still can.
[Samsung Galaxy Nexus] xdp:
Okay, so I created an app-specific password for my account, used it in Sipdroid to create a PBXes account, and then created another app-specific password and updated my GTalk password in PBXes, just so they wouldn't be using the same password. Then I refreshed the PBXes password in Extensions since that seems to be necessary. Now calls via Sipdroid as well as the native SIP support in Android seem to be working. I'm experiencing a quirk though. I told the native dialer to ask me every time if I want to make an internet call. However, before it asks that, a strange, Froyo-looking popup comes up and the options are "Dial xxx (xxx being the number)", or "Use mobile." I have no idea what these options mean and it seems to happen even after I've killed Sipdroid and CSipSimple. After I pick an option I then get the native ICS popup asking if I want to make an internet call or not. Any ideas what this might be?
[Samsung Galaxy Nexus] codesplice:
I stand corrected. I thought there was an Android authentication option but it seems I was mistaken - that may have been with one of the other apps I tested. I also did as you did and gave SipDroid an app-specific password (love the 2-factor authentication!). Apologies for the confusion - I will update the OP when I have a chance.

As a general VoIP app, I prefer CSipSimple, but I have found SipDroid to work best with a PBXes.org account. It's definitely best to let SipDroid create the PBXes.org account so that all necessary routing and other configurations get taken care of. So easy!

As for that other popup you're getting I am afraid I am at a loss. I never tried to use the native SIP alongside another option. I could see how things could get confused if you have multiple providers trying to handle an outgoing call.
[Samsung Galaxy Nexus] ohwellariel:
Thanks for the great guide, I read the whole thread! I have a question about texting and Google Voice. I am planning to never give out or display my actual phone number, so I need outgoing calls and texts to show my Google Voice number. But since the T-Mobile Monthly 4G plans have unlimited texting, I would prefer to send and receive texts through their SMS. Why? Cause it should reduce data usage (I text a lot), and I like the idea of having text functionality even without a data connection.

Now I know that in Google Voice I can duplicate all my received texts and have them sent through T-Mobile messaging, which seems redundant but acceptable. Will I just get massive double notifications if I try this?

I've looked at a couple apps along the lines of Google Voice Deep Integration. Will this allow me to send texts through T-Mobile that come from my GV phone number?

TLDR: Ideally...

with available WiFi, calls use VoIP, texts use data and GV app, cell radio turned off to save power.

without available WiFi, calls use TMo cell, texts use Tmo's SMS.

If I have great stationary mobile data, I can always manually change Sipdroid's settings to handle incoming and outgoing calls (I think).
[Samsung Galaxy Nexus] :
So I've got the pbxes going through the native dialer without any issues. Seems to be working quite well (call quality) today. The standard setup has the transport type as UDP. When I try and change that to TCP, the account doesn't connect. Is TCP just not supported in the way I have it set up?

Thanks.
[Samsung Galaxy Nexus] codesplice:
With Google Voice, you pretty much have two options for texting. The first is to use the GV app (and your data) for texting. The other is to set up Google Voice to forward text messages to your carrier number. These will be handled as standard SMS messages and will be delivered to your default SMS app. This route can be a bit confusing since the sender shows up as a random forwarding number, but the contact's name will be at the beginning of each message.

The integration apps would still use GV (and thus your data) for texting but would just mirror those messages into your texting app.
[Samsung Galaxy Nexus] codesplice:
Hmm, I see my SipDroid connection to PBXes uses TCP without issue, though it is on a nonstandard port (5061). Does the native SIP client let you specify a port?
[Samsung Galaxy Nexus] :
It does let you specify. Initially, it's set to 5060. I just changed it to 5061 and now it registers! Will try that out and see how it goes and report back.