yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] austriker27:
Thanks. Has anyone told you lately that you are awesome- because you are. Super helpful.

So I rebooted the phone. I have not flashed a new rom nor done a backup since I flashed ICS about 1 month ago. Google voice now prompts me each time I dial. When I choose without google voice it does say internet call, but still gives the timeout message. Although after it timed out on my screen my friends number who I dialed begun to ring. Interesting.

i have the correct pbxes account and extension. It even says "receiving calls" in the dialer- so it registered correctly. The correct port is also specified. It is set to internet call outgoing when data network is available.

Sounds like others have had it work out after changing the special app specific gmail password several times. I will do that and report back. Not sure what else it could be at this point

EDIT: turns out if you get the timeout error the best thing to do is generate another gmail app specific password. That fixed it. Although the person on the other line is still getting a weird echo (like in a cave, etc) but my side is quite clear..
[Samsung Galaxy Nexus] jarjar124:
i heard the tmobile $30 plan is a 2 year thing...someone correct me on this.
[Samsung Galaxy Nexus] tom1l21:
This is incorrect. It's monthly.
[Samsung Galaxy Nexus] jarjar124:
so i can cancel anytime right? its a no contract monthly plan.
[Samsung Galaxy Nexus] krazykeyur:
Yup. That's the beauty of prepaid.

I had the $30 plan for two previous months. Have Simple Mobile right now and maybe next month. After that, back to the TMobile $30 plan.
[Samsung Galaxy Nexus] gthing:
I'm on ICS with a Samsung Galaxy S III.
[Samsung Galaxy Nexus] codesplice:
I hope this doesn't come across as a stupid/insulting question, but have you checked your wifi sleep policy under Settings -> Wifi -> (menu) -> Advanced? "Keep Wi-Fi on during sleep" should be set to "Always".

This is completely separate from what apps like Wifi High Performance Widget hope to accomplish. The Wifi Sleep policy specifies the conditions under which the wifi radio will automatically turn itself off (temporarily); the High Performance Widget only keeps the Wifi radio from going into a power-saving-but-still-enabled mode.
[Samsung Galaxy Nexus] gthing:
Yea, I have my wi-fi on during sleep setting set to always.

I found in another thread a trick that seems to be working so far. From the stock dialer dial #*0011#, hit the menu key and select wifi, and turn PSM (power save mode) to OFF. Unfortunately you need to do this every time you boot your phone as the setting does not appear to be permanent (if anyone knows how to make it permanent that would be awesome - or if it could be triggered from tasker or something).

I tested both wifi high performance widget and Advanced Wifi Lock and neither of them effect this setting.

Another setting I changed was under settings/wifi/advanced I changed the frequency to 2.4Ghz only. Some people were reporting leaving it on auto caused disconnects.

It seems to be more reliable now, but only time will tell. I'll report back if this solution isn't working reliably.
[Samsung Galaxy Nexus] jgrinst1:
If you have the time and inclination, try using Sipdroid and forcing the Speex codec. It has built in Auto echo cancellation and may help you determine if it is the phone or the connection.

For an addition to the TCP vs. UDP transport debate: If you use Sipdroid and specify "Improve Audio" under the "Pbxes features" in Settings, a dual stream of packets will be sent. This requires twice the bandwidth for the codec you are using, so likely would require a Wifi or 4G connection. This results in very little packet loss and a very good quality call. Most importantly, this will ONLY work if TCP transport is selected.
[Samsung Galaxy Nexus] austriker27:
Well I have used sipdroid before and it worked well I think. So I guess its probably the stock dialer. Id rather stick to the stock dialer if I can, but if I can't figure it out guess ill go with sipdroid.

Thanks for your help. Hope someone can chime in with how to fix the echo if possible, thanks
[Samsung Galaxy Nexus] jgrinst1:
As there are no level controls with the native SIP, you are only left with turning down your earpiece volume. It's likely the echo comes from them hearing themselves from your earpiece back into your mic. I have the same problem with my Galaxy Exhibit, which is why I have to use a SIP client that allows me to adjust that.

The best fix, of course, is just to buy a new Nexus... :)
[Samsung Galaxy Nexus] Megatr0n.:
I'm having issues where I no longer receive incoming calls using SIPdroid & pbxes.org. It used to work fine, then I got an email from pbxes.org telling me to update my personal information after which I no longer received incoming calls unless I restarted SIPdroid (and even then, it stops working after 5 minutes). I did update my personal information, but the issue hasn't resolved.

I have deleted and re-created my pbxes.org account multiple times (since if I change any of the registration settings on SIPdroid it'll give me a 401 Unauthorized error when trying to log in), but the issue still persists.

The main reason I wanted to use SIPdroid was because GrooveIP was basically unusable over 3G/4G, but not being able to receive any incoming calls is big drawback.

Does anyone know if there's something I need to change? Perhaps on pbxes.org?
[Samsung Galaxy Nexus] rafa3L:
Why not just start over. Uninstall sipdroid and delete your account on pbxes and then reinstall sipdroid and let it recreate your pbxes account.
[Samsung Galaxy Nexus] Megatr0n.:
Because I've already done that about 6 times. I mentioned in my post that I deleted and re-created my account. That included deleted SIPdroid & my pbxes.org account.
[Samsung Galaxy Nexus] austriker27:
I will try that next time. Oddly I made a voice call via tmobile while coming home and I don't think it was echoing for them on the other line.

Haha nice try it is oh so tempting but the g2 is amazing, especially with ics on it. So smooth and fast and I love qwerty.
[Samsung Galaxy Nexus] HemRoyd:
Potential Workaround for PBXes Issues

OK, I'm off GNEX and onto a Droid Razor for reasons I'll explain later. I'm back here to share a little bit of what has helped me with my SIP strategy.

I had a lot of trouble getting decent quality out of the many dialers. Before experimenting with SIPDroid and PBXes, I had the best luck with a CSIPSimple/GV Callback method with Tasker profiles. Now I'm on a (Verizon) Razr, rooted with stock OTA ICS and no native SIP option.

I'm all in on Google Voice.

I went through a pile of dialers and then decided to try the SIPDroid/PBXes route. Followed the guide here and was not really getting great results with the SIPDroid/PBXes/GV implementation. After poking around a little bit, I came up with this alternative:

Google Voice Gateway | Simon Telephonics

Basically, the guy is hosting a gateway to connect SIP devices to GV. It is a donation based service right now, but hopefully there will be enough satisfied supporters to keep it running for a while. Of course, you still have deal with the idea of giving out your GV credentials, so...do some soul searching.

Anyhow, I first set up a PBXes account, installed SIPDroid and then blew off the GV account setup. I went over to Simonics and created my gateway and then went back to PBXes and created a custom GV trunk based on the gateway credentials from Simonics instead of the one generated by SIPDroid and PBXes. All else, being the same.

The result was excellent and I did not experience the "15 second" limited ring duration and my GMail application (opened on my desktop) as well as my connected phones all rang as well.

I did ultimately kick SIPDroid to the curb in favor of the Media5 Fone app, but for other reasons I may share later. For now I would be interested in seeing if this alternative Simonics GV gateway approach is at all beneficial to others going this route (without any added confusion).

Disclaimer: I am by far a seasoned veteran with all of this, however I have put a considerable effort with my current strategy and hope to share and learn as much as possible.
[Samsung Galaxy Nexus] codesplice:
Good info. I will have to. Be sure to check that out when I get a bit of time to play. Thanks for reporting back!
[Samsung Galaxy Nexus] pdxtechdoctor:
fixed the 15 sec ring issue..

Ok suddenly the 15 sec ring issue is gone with pbxes...

Ok I was thinking that the ring issue is related to the pbxes interface with GTALK... I figured that I could workaround the ring issue by having my phone ring without having to go to gtalk..

To do this, I setup ipkal give seperate phone number to ring my pdxes extention and then have gvoice forward the call to pbxes.

I setup the number and tried to add the ipkall number to gvoice. I was never able to get this fully setup because, it wouldn't accept my DTMF tones to enter the code to verify the number. Calling the number directly would ring the phone the full number of rings.

After attempting this, suddenly calls going to pdxes through gtalk now ring the proper number of times - about 30 seconds before going to voicemail.

Something in the process of receiving calls through a sip 2 sip has reset the way it is picking up calls on gtalk.

it would be great if someone else could give this a try and see if it helps...

If you need instructions on how to setup ipkall, let me know and I'll provide them.
[Samsung Galaxy Nexus] Pkt_Lnt:
I just purchased my first refill from www.KeepCalling.com and paid $50 for a $50 refill. I had signed up before and did not examine the website carefully before purchase, so it is my fault that I did not get the 5% discount I expected. I got an email that my transaction was "pending" even though it was paid with PayPal, and I needed to contact Keep Calling.

I had to call and sit on hold for a long time, multiple times while the person on the other end wanted information that was none of his business, asking for billing address and contact number, which I understand to verify what I entered on the site. He was asking for mobile phone number, physical address (I use GV and a PO Box on all billing).

I got annoyed and stated that I was going to call PayPal and cancel the transaction, he finally stated that the transaction was approved. It took over 30 minutes to get my PIN emailed.

Needless to say, I will not be using that site again. I did see the "always on" 5% discount when I visited a week or so before, but it is not there today. Just so everyone else knows. I will be using Calling Mart from now on.

@codeslice, you might want to alter the OP that I quoted above.
[Samsung Galaxy Nexus] codesplice:
Interesting. I used KeepCalling for my last refill and didn't have too much of an issue. I did have to call to confirm my billing information (as I had missed their call seeking to do the same), but it was a relatively painless process and my PIN was received probably 30 seconds after I got off the phone with them. You're correct though... I don't see the discount listed on their site anymore. A bummer, but I guess I will have to remove the suggestion from the OP. Thanks for the feedback.
[Samsung Galaxy Nexus] bender29:
I thought I had done everything right but I'm having problems getting the plan..

Got the Galaxy Nexus and then bought the sim card activation fit for $.99, got it in the mail today. Tried to activate online - entered activation code, SIM card serial, and IMEI. Picked the $30 plan, picked my city.

Then, on the final page, it says "We’re sorry, we’re still working to process your activation. Please wait a few moments and then try navigating to another web page. You should receive a text message to your device when your activation is processed."

I never got a text message. I tried to do the automated activation over the phone like someone earlier suggested, but my SIM # is already activated. Tried to do it online again, and it complains that my SIM number is already activated.

Finally I call customer service and I'm got nowhere. Asked for a higher level person and after trying some things, they say they'll call me back in 5 minutes (was 60 mins ago). I guess I really didn't expect a call back anyhow.

But I'm in limbo.. Any help on what my next step is?
[Samsung Galaxy Nexus] Lythandra:
Doing my first refill and I just wanted to verify that this is the correct one to get.

http://www.callingmart.com/products/wireless/ProductDetail.aspx?ID=265&name=T-Mobile-Monthly-Plan

I'm guessing they send me a code and I go to T-Mobile, enter my account and enter the code for the $30 credit?

I don't want to waste $30 so just making sure I do this right the first time.

Thanks

Edit: Nevermind, I just saw the exact answer at the bottom of the OP.

Edit 2: Nice, worked perfectly.
[Samsung Galaxy Nexus] codesplice:
I'm afraid I don't have much additional information to contribute; it sounds like you've done everything that you should. I'd just keep calling their prepaid support folks at 1-877-778-2107 (or dial *611) until they're able to get you sorted. Sorry I can't provide any more help :(

Glad you got it sorted!
[Samsung Galaxy Nexus] dipole:
Ugh, having same issue. I'm thinking of setting up my own personal VOIP server on my new raspberry pi. I'm tired of deleting and re-creating accounts
[Samsung Galaxy Nexus] codesplice:
I did have to delete and recreate my PBXes.org account, but only once. After I got the notice to update my personal information (and that account never worked correctly again), I made sure to put in valid personal info shortly after creating the new account. I've been on that one for a month with absolutely zero issues.
[Samsung Galaxy Nexus] austriker27:
This is great and

should be included in the OP

. I just signed for an account using codesplice as the referring person (come on man you deserve tons of cred for his beautiful guide) and that coupon code for 5%. Success!
[Samsung Galaxy Nexus] haley_joel_osteen:
This happened to me because even though they gave me the option to choose a certain area code, there weren't actually any numbers available in that area code. As soon as I chose a different area code, worked immediately.
[Samsung Galaxy Nexus] noneone:
Any update? Good luck, sometimes the activation can take a couple hours. Does it work today?
[Samsung Galaxy Nexus] bender29:
I didn't want to bother calling CSR again, so I went to a Tmobile store and told them my story and the person was nice enough to give me a new SIM card.

Fortunately, my activation code was still good, so I went through the online activation process and this time, everything worked smoothly! I did use Firefox instead of Chrome browser this time, as I had some glitchy behavior with the activation website last time, but I don't know if that really affected things. I picked all the same options this time (area code, city, etc) so for me, that didn't seem to be the issue.

So I'm rocking on Tmobile $30 prepaid thanks to everyone and this thread! Now to read up on different ROMs and radios :)
[Samsung Galaxy Nexus] zurdo82:
I had the same issue. I called CSR and they were pretty much useless. I also had the hunch that it had to do with the number availability in my region. I tried different nearby regions until it worked.

Right now, I'm on my first month of freedom and it feels nice to be contract free.

I'm going to try to use skype for my outgoing calls ($3 a month for unlimited in the US/Canada). I'm currently waiting for confirmation that my skype caller id is all set up. I don't get too many long incoming calls so the 100 min should suffice for all incoming traffic. I can always say "Let me call you right back".

I'll try to post my experience with this setup. Today I was on a conference call on the road with groove ip and I can see the complaints about its quality outside a good wifi network. Everyone else had a rough time understanding me. I heard them ok but not great. This made me consider skype as a solid voip solution. Fyi I'm in the Northern VA area.

Thanks codesplice and everyone else for your input!
[Samsung Galaxy Nexus] c0LdFire:
If you need to frequently attend conference calls and the like, I'd probably stick to Straight Talk or look very closely at how many minutes you use. VOIP is great and all, but I just can't seem to rely on it... I'll use it from outgoing calls via gmail at home from time to time, but on the phone itself it seems to just not work very well 50% of the time. I don't want to gamble with whether or not my calls will have acceptable quality.

Personally, I go through anywhere from 150 - 250 a month. I'm planning to just keep pre-paying $45/mo on T-mobile to have those extra minutes available - so I'll be paying the same as straight talk, but for less restricted data. If I used 400+ minutes I'd probably just swap over to one of their SIMs. Luckily most of my calls for work I can just send to voicemail and call back with my desk phone right away.
[Samsung Galaxy Nexus] zurdo82:
True. I tend to take these calls from gmail at home and I've also used groove IP on my tablet when I'm too lazy to pick up my laptop. Right now I'm just testing what works for me. I usually take these conf calls from home but yesterday I had to drive that morning. They range anywhere from 15 min to 2hr long so they would eat up my t-mobile min right away. *I take them 3+ times a week.

I just got off a call that I took from home using skype (on wifi) and it was flawless - even with the extra delay of my bluetooth headset.

In the end, if I'm not satisfied, I could always prepay t-mo for the extra minutes, like you said.
[Samsung Galaxy Nexus] c0LdFire:
Since you were driving around...

did you have the call drop out at all? I drive through a couple of small EDGE-only areas every day. Not a big deal for me, but I can't imagine what the switchover would do to a VOIP call.
[Samsung Galaxy Nexus] codesplice:
Glad to hear you got it sorted!

Yeah guys, this $30 plan isn't realistically suitable for users that need a lot of minutes (unless you spend most of your time next to a good wifi network and are comfortable with one of the free VoIP options). If you regularly need more than ~350 minutes and don't regularly use more than 2GB of data, one of the Straight Talk plans would really make a lot more sense. If you need more than ~500 minutes and 5GB of data, T-Mobile also has a $70/mo plan that may suit you better.

I don't personally believe that VoIP is really yet at the point that it can be used reliably over a carrier's data - and really it is sometimes a stretch to use it regularly even on Wifi, depending on traffic conditions.
[Samsung Galaxy Nexus] codesplice:
Unless you're using an extremely compressed codec (which would probably sounds like crap), I really doubt that the call would be able to continue.
[Samsung Galaxy Nexus] whitedragonz83:
VOIP Delay?

I've been reading this thread for most of the year and been on the $30/mo TMobile Plan since March. Loving it, though after much trial-and-error, I have settled on using my 100 minutes (or willing to go over) during the day and using SipDroid+PBxes at night for basically free nights/weekend calling. My question is this though.

(These comments are on WiFi only)

When using GrooveIP on WiFi it appears I have as much as a 3 second delay when talking or when the other person is talking. This is quite annoying. However, when I use SipDroid+PBxes with the PCMA/PCMU (not sure which it is) codec, I only notice at most ~1 second delay. This is a much more enjoyable experience.

Why does GrooveIP directly connecting to the GTalk servers cause a higher delay then Sipdroid->Pbxes->GTalk? Is there a setting in GrooveIP that I need to adjust?

Thanks,

Ted
[Samsung Galaxy Nexus] c0LdFire:
I'm actually quite interested in this as well. That's my main complaint about GrooveIP -- within a minute or two in to a call, the delay just becomes unacceptable. On the other end of the call they can hear me just fine with no quality issues or whatever, but I hate talking over people.
[Samsung Galaxy Nexus] codesplice:
Interesting observations. I haven't used GrooveIP in a while so I'm afraid I can't provide much insight. Random guess: It sounds like it might be an issue with audio processing within the GrooveIP application rather than a network issue (maybe?).
[Samsung Galaxy Nexus] c0LdFire:
That would definitely make sense if it's trying to compress it, but I just can't imagine the Nexus getting slowed down by that - it's not like it's compressing a bluray film..

I might experiment with it a bit after work and see if downclocking makes the delay worse.
[Samsung Galaxy Nexus] codesplice:
Are you on Jelly Bean yet? I know JB was supposed to include a fix for audio playback latency.
[Samsung Galaxy Nexus] whitedragonz83:
My issues are on stock everything JB.

I did not notice "High Pref WiFi Lock" in the GrooveIP settings to change things.

I did try turning off Echo Cancellation effects and most audio settings, but did not notice any significant changes with the delay in GrooveIP.

Maybe it is a CPU issue being in a low-state, as I did not try "Partial Wake Lock" in GrooveIP settings. Nore did I try leaving the screen on.

It most likely has to be an app problem with GrooveIP that SipDroid deals with automatically or better. Right?
[Samsung Galaxy Nexus] c0LdFire:
Yep, stock 4.1.1 but running Trinity kernel with a 1.35ghz overclock / interactive governor.
[Samsung Galaxy Nexus] codesplice:
Have either of you tried the Wifi High Performance Widget to automatically keep a wifi high-performance wake lock when on a call? Might be worth a shot.
[Samsung Galaxy Nexus] Luxferro:
It's because gtalk itself uses only one codec, which needs good bandwidth for good audio quality.

With pbxs you can use more efficient codecs. So from you (wireless) to pbxs you're using an efficient codec that works good for lower bandwidth connections. Then from pbxs to gtalk they must have better (wired) connections to support the gtalk codec.
[Samsung Galaxy Nexus] whitedragonz83:
Correct me if I am wrong, but based on:

en.wikipedia.org/wiki/G.711

G.711 uLaw = PCMU

SipDroid/pbxes uses PCMU (G.711 uLaw), which is the same voice codec GrooveIP receives/uses through GTalk-Google Voice:

snrblabs. com /snrb/Apps/GrooveIP/FAQ.aspx (can't find a link from google about how GV using only this codec).

So audio codecs would be equivalent in either form of VOIP communication under these conditions?

This would mean the problem still is an App issue and not a google voice issue, right?
[Samsung Galaxy Nexus] codesplice:
This was my initial thought, but I believe the codec difference would have more of an impact on quality rather than latency.
[Samsung Galaxy Nexus] Luxferro:
I guess you guys are right. I just thought the way I explained it was the reason it worked better then grooveIP since that's what I had read somewhere.
[Samsung Galaxy Nexus] codesplice:
I think you are right, you're just addressing the wrong problem ;)
[Samsung Galaxy Nexus] zurdo82:
No, it did not drop. I was on the phone for about 40 min. If you are familiar with the Northern VA area. I drove from Centreville to Fairfax and then to Chantilly taking mostly route 66. I'm actually pretty happy with the signal that t-mo has around here.
[Samsung Galaxy Nexus] whitedragonz83:
Expanding on this, I was a little wrong. SipDroid defaults (for me) to PCMA first. Trying a few tests through an Echo Number (over 3G/HSPA), it appeared PCMA was slightly better then PCMU. So if GrooveIP is only using PCMU (GoogleVoice) , that would be at least one issue of GrooveIP vs SipDroid/PBxes.

I also tested multiple settings in GrooveIP just now and none made a noticeable difference in latency issues. Echo on/off, CPU Lock, WiFi Lock, Buffer Size (small vs x-large).

So tentatively maybe it is just a codec thing. The wiki mentions "G.711 defines two main compression algorithms, the µ-law algorithm (used in North America & Japan) and A-law algorithm (used in Europe and the rest of the world). Both are logarithmic, but A-law was specifically designed to be simpler for a computer to process."

Is it still possibly a cpu issue in the Galaxy Nexus of PCMA (SipDroid/PBxes) vs PCMU (GrooveIP) (hard to believe right?) and not a network latency?