yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] ohwellariel:
I think after a lot of searching the "random forwarding number" you mention is the trick for sending outgoing texts through the native app that appear as if they came from your GV number but use your carrier's SMS like normal texts. They're called direct access numbers or sometimes routing numbers and they seem to be semi-permanent numbers assigned to your contacts. According to Google, as long as you never sign out of the GV app, these numbers will stay the same.

The easiest way to find out what your contacts' numbers are is to have them text you. That won't work for landlines but if we're using Monthly4G we're not interested in using the direct access to make calls, especially since the GV app does that already (actually, that may be how it bypasses the callback process). Then just associate the direct access numbers with your contacts and when you receive or send texts it should be grouped with that contact and it shouldn't use data at all. The only hiccup is that viewing received messages in the native app will have that little label that shows who the message is from.

PS. you still can't text short codes this way but you can call people whose direct access number you have without using the GV app.
[Samsung Galaxy Nexus] kcshmo:
Yes, it was free shipping indeed. I ordered it and waiting for it to show up now. I'll probably have more questions when I try to activate the $30 plan. Thx again.
[Samsung Galaxy Nexus] codesplice:
Good additional information on the "direct access" numbers. One note - as far as I know / can tell, calls made via Google Voice simply use an existing data connection to request a callback from the GV servers. Unless things have changed, you're generally unable to place a GV call without some manner of data connection. You may be onto something though - calling a contact's direct access number may get around this requirement and all you to place a GV call without any data whatsoever. I may have to test this out later.
[Samsung Galaxy Nexus] xdp:
Thanks, it appears the pop-up I was seeing was from CSipSimple. I kept closing it but after a minute or so it would show up again in my Recent Apps list. At that point I would see the pop-up when making a call. If I closed it again and immediately made a call I would not see the pop-up. I don't like how it kept relaunching itself so I uninstalled it for now.

The native SIP works well, the audio seems relatively clear but still quieter and more "tinny" than a normal call. I wish there was a way to improve this. Has anyone tried the "HD voice" codec that is offered with a PBXes premium account?
[Samsung Galaxy Nexus] dipole:
Secure settings for tasker just released an update with settings for sip, can't wait to play with it
[Samsung Galaxy Nexus] :
Basically, you'd want receive calls unchecked when disconnected from wifi because you'd be getting them over the cell network?

What do the other options mean- Internet calling always vs only for Internet calls vs ask each time? I've tried several configurations and they don't seem to make a difference. That is, it's never asked me anything before a call.
[Samsung Galaxy Nexus] :
Not sure how to get attachments rolling from the mobile app... It's at 10.5 hours so far and at 71% remaining.

Also, here's my battery life so far today. This is with the native sip client using a pbxes account (sipdroid not installed) using tcp on port 5061. On crappy work wifi all day (so airplane mode profile), 1:11 screen on time. Stock JB. GSM Galaxy Nexus.

Very satisfied. Coming from a vzw Galaxy Nexus.

Thanks again for this thread :-)
[Samsung Galaxy Nexus] codesplice:
Sweet, that does look cool.

1) Correct

2) "only for Internet calls" would take over if you were dialing something like "user@sipgate.com", I believe.

Impressive!
[Samsung Galaxy Nexus] austriker27:
I am sold on doing the prepaid with tmobile. Although I am still leaning towards keeping a qwerty keyboard. I have good things about the (old yes) "Tmobile G2/HTC Desire Z'' and it has an amazing qwerty. It has strong dev community and can be overclocked to 1.2 Ghz. I am waiting for the next great qwerty android (rumors there might be a nexus qwerty for nov)..

Is there any disadvantage to getting a G2 instead of the nexus for this lil operation? Perhaps then I could pocket the savings and wait for my precious perfect qwerty nexus (which may not happen).. Thanks!
[Samsung Galaxy Nexus] shovelheadhd:
I hate to question you but I has always been my understanding that the Google Voice app uses cell min when a call is initiated from the phone even if you use the Google voice option to call using Google voice. I thought the only way to use no cell min was to have Google voice call your sip and then make the outbound call for you.

I haven't found any solid info so far either way. I hope you're right and I'm wrong as I have always used call back apps and it's clunky to use for calls.
[Samsung Galaxy Nexus] mau006:
Sweet Guide

Very nice guide, been doing something similar with a Samsung Vibrant for awhile now. Just ordered a Galaxy Nexus this weekend, although I'm not sure if it is going to ship anytime soon/ever due to Apple's injunction...
[Samsung Galaxy Nexus] austriker27:
I believe you are right.

It sounds like thats why you setup the program which disables your radio band (via the cell phone company) via airplane mode when you are connected to wifi. Then using the wifi you use talkatone (through gvoice) to use it as a VOIP type setup to avoid gvoice using cell minutes.

If I am wrong someone shoot me down.

---------- Post added at 05:07 PM ---------- Previous post was at 05:05 PM ----------

Keep us (or at least me via PM) when it ships. I am interested in this but only if I can get the nexus shipped out to me. I thought the lawsuit was only on samsung selling the gnex directly (thus google, VZ, etc) could still sell it

Clarification would be great- I will order mine asap if its a worry
[Samsung Galaxy Nexus] codesplice:
I'm sorry for being a bit unclear. Google Voice uses data to initiate the callback. Once the callback is in place the call is handled as a standard voice call - so it does use your voice minutes. The whole callback process is pretty much hidden on an Android device, but this is essentially what happens (during the brief time the phone displays "placing call via Google Voice):

The Google Voice app reaches out to a GV server with a data request to connect the caller (you) with the recipient.

The GV server places a voice call to your device. This would appear as in incoming call from your GV number to your carrier number.

The GV app automatically answers this callback, and the server then starts ringing the person you are calling - sending your GV number as the caller ID

They (hopefully) answer, and the voice call is connected.
[Samsung Galaxy Nexus] bigdoug2005:
First of all thanks for this excellent guide. I set everything up tonight except for the VOIP and one thing I have noticed is that if I ignore a call on my Nexus when a call is coming in through my Google Voice number it will stop ringing for a few seconds and then start to ring again right when the voicemail picks up to play my outgoing message. So to ignore a call I swipe to hang up.... wait a few seconds... then the phone rings again and I can either answer or ignore but either way it goes to Google Voicemail. If I answer on the second set of rings I only get silence. I have gone through all the settings and cant find anything set up incorrectly. Does anyone else experience this?

Edit: I found a way to work around this is to just hit the power button instead of swiping to ignore the call. This will silence the phone and turn off the screen. It's still bugging me though. I am using Jelly Bean btw, but I dont think that will make a difference.
[Samsung Galaxy Nexus] codesplice:
So here's a crazy question... how do you make outgoing calls using the native SIP while Airplane Mode is enabled? I started experimenting with the Secure Settings update to toggle the use of the native SIP when I'm on WiFi. Incoming calls seem to work but I get a message about "To place a call, first disable Airplane Mode" whenever I try to dial out. This is with the option selected to always use the Internet calling when data service is available - I would assume that should work over WiFi, right?

I guess I will go back to SipDroid until I can get that sorted - any ideas?
[Samsung Galaxy Nexus] codesplice:
Hmm, and you don't have any VoIP configured, not even GrooveIP? That's certainly odd. I know that when I reject a call it stays rejected for good. The only exception is if I'm getting a call both via the carrier network and via GrooveIP or similar.
[Samsung Galaxy Nexus] :
I've gotten that error once. I used to use Voice+ to initiate call back, however, now I use Google Voice Call Back: http://code.google.com/p/free-phone-call/downloads/detail?name=GV-Call-Back.apk&can=2&q=

It's nice because it has a tasker plugin as well, so I have a profile set so that when I'm connected to WIFI, that it sets the GVCB to Always (when possible) and then when WIFI is not connected, it reverts to Never.

Side bar- do you think that I could add this tasker bit to the existing Google Voice Airplane Toggle profile? If so, how?

Also note, I tried a few of the settings in GVCB that seem to have messed things up- now I leave auto answer the call back unchecked and leave show waiting screen checked (under advanced). Little less clean, but at least it functions.

The way I have it going now, my call history looks clean (proper caller IDs show incoming and outgoing).

Keep us posted on how you integrate the secure settings plugin into your tasker profiles.

Thanks!
[Samsung Galaxy Nexus] codesplice:
Good suggestion on using the GVoice Callback app - I've used it in the past and it works well. I am a bit disappointed that the auto-answer function doesn't seem to work with the native dialer. This will probably make me fall back on using SipDroid for my PBXes.org connectivity. It's a little bit cleaner, and works just as well as far as I can tell.

I did play with automating some of the settings via Tasker though. For the enter task:

And the exit task:

That also includes the new Secure Settings SIP functions, as well as an additional setting for adjusting the Wifi Sleep profile. When I'm connected to one of my known-good VoIP access points, Wifi will never sleep when the screen is off. When I'm not connected, it will sleep when the screen is off to conserve a bit of power. I don't like to turn off my wifi completely as it helps significantly with getting a quick GPS lock.
[Samsung Galaxy Nexus] :
Is this tour main profile? The one that starts out with the "http get" deal where it tried to load Google.com in the background?

Right now I have 3 separate profiles that all start with the Wifi being connected to a trusted network. One is your GVAM profile from the first post, the next unchecked receive SIP calls and the last turns on the GVCB. I could probably do them all under one, but I am a totally new to Tasker.
[Samsung Galaxy Nexus] codesplice:
Yep, that's the main one. I try to keep as much of the GV-related stuff in the same Profile - though I have been lately toying with the idea of replacing all of the actions inside the If statement with a single Task. Having all the individual actions under the one profile helps to make sure that when the GV profile is active, all of the appropriate settings are applied.
[Samsung Galaxy Nexus] Whyzor:
I don't believe Google Voice app on Android uses callback (maybe on iphone or other devices). On Android, anytime someone has called or texted you gets a random number assigned, then Google Voice syncs and gets that number. So when you initiate a call to a contact that has reached you before, no data connection is needed. The Google Voice app automatically routes the outgoing call to this random number over cell network (so they see your GV number as callerID). I usually keep my data off and can initiate calls to my contacts without a data connection as long as they have called (or texted me before), and I have sync'ed with GV. I think this was a recent update to GV app for Android in the past 6 months or so.
[Samsung Galaxy Nexus] codesplice:
Hmm, okay. So replace my "request a callback" words with "request the direct access number for the dialed number" and call it a day :-D

Good info though - thanks!
[Samsung Galaxy Nexus] dipole:
Hey Codesplice, been following your thread all along and awesome job, I've been making tweaks here and there when I see you mention them. I was wondering if you could update the OP or this thread with your current setup, like what is your current tasker profiles (they look different than OP with different numbers), what SIP client and service you're currently (Pbex?) using etc as it looks like you've been learning and tinkering and tweaking a lot. Thanks again, this thread is the main reason I bought a nexus.
[Samsung Galaxy Nexus] codesplice:
Thanks for following along :)

I've been tinkering with my setup a lot recently (and tinkering a lot in general, having just yesterday installed the plain-jane unofficial official Jelly Bean preview ;)), but here's a quick run-down of what I'm using:

Cell Service: T-Mobile $30/mo 5GB data plan (loving it)

SIP Service: PBXes.org GoogleChat connection (configured super-easily via SipDroid)

SIP Client: SipDroid, using the default settings for the PBXes.org Google Voice interface

On SipDroid, I've got it configured to make and receive calls only when on Wifi, and I have the "Preferred Call Type" option set to "Sipdroid, when available". This way, SipDroid automatically handles outgoing calls made from the stock dialer when I'm connected to Wifi.

As for the Tasker profile, not a whole lot has changed since what's listed in the OP - the only current difference (that I can think of off the top of my head) is that I also now toggle the Wifi Sleep policy along with Airplane mode. I have that set to Never when entering my GV Airplane Mode magic fun time, and set it to Default with that Profile's Exit Task.
[Samsung Galaxy Nexus] dipole:
Using the new secure settings SIP options or were you just experimenting a few posts back?

Also volume seems really low using the sipdroid / pbx route, any solutions?
[Samsung Galaxy Nexus] codesplice:
Nope (to the Secure Settings options) - those only work with the native SIP client, and I couldn't find a nice/clean way for the native SIP to handle outgoing calls while Airplane Mode is enabled. I'd rather not mess with a callback if I can avoid it.

I haven't noticed a low call volume issue, but I also haven't actually talked to anyone (other than an echo test) in a few days - I'm really popular :cyclops:
[Samsung Galaxy Nexus] muyoso:
In the settings you can adjust the gain to increase volume. They say that it may introduce an echo though, but I haven't experienced that yet.
[Samsung Galaxy Nexus] jgrinst1:
Got to say "Thanks" again for this thread. After experiencing some Twilight Zone stuff with CSipsimple, I'm currently (re)testing SipDroid. I haven't seriously considered it for about a year now, due to echo problems back then. It is MUCH more robust in it's workings, even if the appearance still isn't awesome, and I have tested 78ms delay using PCMU over Wifi, which resulted in a very good calling experience. Incoming and outgoing calls all work famously.

So, great! The free app is currently beating out all the ones I paid for... go figure.

---------- Post added at 04:27 AM ---------- Previous post was at 04:07 AM ----------

I have the Galaxy Exhibit (Exhibit II 4G), which doesn't have as good hardware as the Nexus, or indeed, other higher end phones.

So, I have had problems with VOIP apps with echo. I conversed with the devs at Talkatone about the Exhibit mic being overly sensitive, and they responded thus:

I have to say that I disagree with them on that. Lowering the SipDroid gain settings as in Mic - Low, Earpiece - Medium, seems to work great for me.

So, assuming that your phone volume is already maxed out, you can try raising the earpiece gain, but you may have to compensate by lowering the mic gain.

YMMV, of course.
[Samsung Galaxy Nexus] austriker27:
Ahem.

SO can I buy a HTC G2 (Desire Z) and do this same setup?

Would it need to be ICS for it to work?? I was thinking of flashing an ICS rom to it once I acquire it. I dont want to buy it though if I cant do this setup for VOIP/wifi calls (100 min probably wont be enough- Id do that plan from tmobile). I was going to pick up a G2 tomorrow thats why I want to know before I leave. Thanks!
[Samsung Galaxy Nexus] a5pe4:
Yep. Works with any GSM phone.
[Samsung Galaxy Nexus] bigdoug2005:
Yeah, this was testing with the setup before I configured any VoIP stuff. It seems like this was a big issue a couple years ago for some people but I cant seem to find a solution. I have the "Go straight to voicemail" setting checked in Google Voice and only have my cell phone and Gmail enabled. I am also not consistently receiving calls in Gmail.

Edit: According to this thread using PBXes will intercept all the incoming calls so that they wont make it to the Gmail Google Talk meaning your computer will never ring. Thats kind of a bummer.
[Samsung Galaxy Nexus] noneone:
Is the HTC G2 that you have t-mobile?

The OP's origional plan is a T-mobile $30 per month, unlimited DATA, 5 GB at 4g, txt and 100 mins of talk.

Any GSM phone that works on T-mobile "works" with this setup. BUT, many ATT unlocked phones are limited to 2g data speeds on T-mobile. Some folks are using the 5 Gb of data to do VOIP when no wifi is near, to supplement their minutes. You don't want to do that on 2G speeds!

SO, if your HTC G2 is from T-mobile, you are probably set. If you its an unlocked ATT phone, you might need some more research to see what data speeds you can get.

Either way even with an ATT phone, the 100 voice minutes will work fine, and the OP's setup to use VOIP when on WIFI will work fine too.

GL!
[Samsung Galaxy Nexus] codesplice:
That's interesting. Under that logic, after setting up the SipDroid with PBXes.org I should not be able to receive calls via GrooveIP. Quite to the contrary, GrooveIP still works. I haven't used my computer for calls since the last time I was in the desert though.

Update: I did test and confirmed that my computer does not receive incoming calls. I don't know for sure whether or not this is directly related to PBXes.org, but I've updated the OP a bit so folks are at least aware.

A question for those using the native SIP (with any service): I didn't see an option for specifying a STUN server for getting around NAT. Have you had any problems with not receiving calls on a WiFi network which uses NAT?
[Samsung Galaxy Nexus] bigdoug2005:
According to this if you use the native SIP support it will automatically go over Wifi when you have a connection. That would mean you dont have to do any of the fancy airplane mode stuff at all. I'm still trying to get outgoing calls to go over VoIP. Its not giving me the choice between voice network or data network when I place a call like it should. Incoming calls work though.

Edit: I have not had a problem receiving calls but I don't know much about NAT so I cant help with that. I did notice that the native SIP accepts incoming calls over the cell data network and I dont see a way around that. It could be good for some people but not if you have an Edge connection. Sipdroid seems to be the best option for now.

Double Edit: I get the choice of voice/internet call only if I go into Google Voice and change it to ask to use my Google Voice number before each call. To make an internet call you have to choose "Call without Google Voice" and then on the next popup "Internet Call" this then place a VoIP call using your google voice number. To make a cellular network call choose "Call with google voice" on the first popup and it will go through. Kind of complicated to get it all working.
[Samsung Galaxy Nexus] austriker27:
Yes. It is. So sounds like I am good to go! Thanks and happy america day.
[Samsung Galaxy Nexus] Luxferro:
That's cause you have Google Voice set to use for all calls. I had the same problem. Apparently it thinks "how am I going to initiate a call to your real cell # if you have it in air-plane mode?" lol.

To solve it, I set Google Voice to never be used for calls. And just use VOIP all the time, even when not on wifi (not that I do voice calls often).
[Samsung Galaxy Nexus] :
I am not having this problem while using the native SIP client in airplane mode. I have GV set to make all calls. I have GVCB set to "always (when available). Here's how I do it:

Here's what I have it setup to do when on a trusted wifi network:

1-Turn on airplane mode (with Tasker set so that it leaves wifi on, of course)

2-Secure Settings to receive SIP calls enabled

3-GVCB to callback when "always (when available)"

4-Secure Settings to SIP call options for "all calls when data is available"

5-Wifi sleep policy to never

The results:

When I initiate an outgoing call, GVCB flashed a few windows and does it's thing. I get a call showing my GV number at the top and my GV number with an IP address following it just under that and under that in green it shows that it's an internet call. I answer that incoming call and am connected to the call. One thing I have noted, is that if I haven't answered the callback and the other party has picked up, they get some static/weirdness because they've beaten me to the call. If they stay on and then I answer the call back, we are connected, no issue, it's just a little strange, I guess. Upon hanging up, the correct outgoing number is shown in my call log (not something I was getting when trying to use other setups).

The thing that I wish I could get to work is the feature in GVCB is the "auto-answer the callback" It says that it only works with the stock dialer (which is what I'm using) but it doesn't seem to work. To be fair, GVCB shows a popup regarding that Android 2.3 users might have issues with what I'd like it to do.

I hope this helps someone. This thread has helped me a ton.
[Samsung Galaxy Nexus] codesplice:
Thanks guys for the info on the native SIP client. I just tested and confirmed that it will place outgoing calls while in Airplane Mode as long as it isn't set to always use Google Voice. That makes sense, I had just never thought about it.

So really it looks like the native SIP would be a great solution for me if only I had a way to automatically toggle the local GV settings. I could do it with a widget but I would really rather automate the entire process - after all, that's why so much of my setup hinges on Tasker. And I still do make frequent voice calls so I don't want something to get in the way of that.

I'll be sure to post if I find a good solution.

Thanks again guys - I may have started this thread, but your contributions really make it worth following!
[Samsung Galaxy Nexus] bigdoug2005:
I think the issue with the native SIP client (on Jelly Bean at least) is there is no way to choose between an incoming call using the data network vs cellular voice. It defaults to VoIP. The only way is to manually toggle the "Receive incoming calls" in the SIP settings when you are not on a wifi connection. If this can be automated then it should work but really wouldn't be any better than sipdroid + PBXes since you still have to set up the automation either way. I wish the native client had a setting to only use VoIP when connected to Wifi.
[Samsung Galaxy Nexus] muyoso:
Been having a weird issue with Sipdroid where it only rings for about 15 seconds when receiving a call. Tested it out at home by calling myself, and the home phone keeps ringing for another 10 seconds at least while at around 15 seconds in on my cell it just hangs up and stops ringing.

Those are 3 calls from my home phone to my cell. Each hangs up right around 15 seconds by itself.

Edit: Holy hell music on hold is hilarious and awesome. Can't wait to put some solicitor on hold with an edited version (starting at 16s) version of this playing:

[youtube]V7dg8vRDM68[/youtube]