yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] HemRoyd:
In the voip.ms "Order DID" panel, if you select "Virtual Numbers" you can create a virtual SIP number that you can set up with an IPKall number to handle incoming calls routed through your GV number. The virtual DID is .25/month and incoming calls are billed at .001/minute (or $.0001 every 6 seconds). So, for example, you could pay $1.25/month for 1000 incoming minutes vs. $10.00 just using the main DID account number for incoming.

I've been keeping an eye on the Simonics GV Gateway. The guy that runs it claims to be looking into implementing low bandwidth codecs (currently G.711 only) and TCP transport. May turn out to be a reasonably cheap paid (donation only for now) alternative to PBXes.
[Samsung Galaxy Nexus] krazykeyur:
Interesting. So what's your incoming route? GV -> IPKall -> voip.ms -> CSipSimple?

And what about outgoing? Seems like outgoing would stay the same as what I have right now.. 1 cent per minute.

What about the added hop to IPKall.. does that affect end-to-end latency?
[Samsung Galaxy Nexus] HemRoyd:
I had to leave the GNex because T-Mobile coverage is bad in my area. I moved over to a Razr so I am trying to avoid statements in this forum that may only be specific to my device. With the Razr and OTA ICS, I had some issues with CSipSimple and SIPDroid. I eventually ended up using the Media5 (paid app and further cost for G.729 codec) and it has been rock solid. So:

GV -> IPKall -> voip.ms -> Media5

Yes. I haven't experimented with premium routing yet, which is a little higher.

I have not measured this, however I have not noticed any appreciable reduction in call quality operating in this manner.

I have a couple of calling configurations in the Media5 app. I use a configuration for GV through PBXes when I am on my home Wifi as it works excellent. However, when on the road, I am using the voip.ms configuration. I am trying to decide whether to force the G.729 codec in the voip.ms settings for this configuration or not. I am still experimenting, but so far it's been acceptable. I may try to revisit CSipSimple app to experiment between GSM and G.729 as GSM is not available in the Media5 app.
[Samsung Galaxy Nexus] krazykeyur:
I had never tried the premium routing myself.. so I just did some echo tests. Premium routing did sound better (crisper voice.. lesser "other" noise) than value routing.. good enough to pay 12 cents extra for an hour for voice calls for. I also noticed a lower latency (quicker time) in hearing myself back while doing echo test. I switched back and forth 5-6 times between value and premium plans while doing the tests.. and did my test using the built in SIP client.

So far, I am impressed enough with the premium routing to switch to it.

Built in ICS SIP client supports GSM codec.. so you might want to try that too.
[Samsung Galaxy Nexus] krazykeyur:
I have changed settings in Google Voice and VoIP.ms so that now it does the following whenever someone calls me:

Google Voice forwards call to VoIP.ms only.. so that the built in SIP client on phone recieves it. It waits 17 seconds for me to pick up the phone.. after which it (VoIP.ms) forwards the call to my TMobile number. When that happens, I have 8 seconds to pick it up before call goes to Google Voicemail. That way, in case if I am in a bad data coverage area, I can just wait till the call is forwarded to TMobile to pick it up.. otherwise I have 17 seconds to pick it up through VoIP.. which isnt too bad.

Google Voice goes to voicemail after 25 seconds.. so 17 seconds VoIP ring + 8 seconds TMobile ring seems like a good combo.
[Samsung Galaxy Nexus] whitedragonz83:
This is interesting because I have been hesitant to remove the voicemail from my TMobile number, but calls will use that voicemail service before GVoice has a chance to kick in normally. Using your method, I should never receive a voicemail through TMobile because it won't ring long enough. Does that sound right?

Also, do you notice any echo issues using the built-in SIP client?
[Samsung Galaxy Nexus] HemRoyd:
So you are registered onto voip.ms through the built in SIP client, exclusively? Verizon has stripped that out of the dialer settings. I'll have to start thinking about rooting and looking for a ROM. Trouble is, I need the international GSM option available for when I travel to Canada in a few weeks. I hoping to get by strictly on Fido's pay as you go data and use VOIP exclusively.
[Samsung Galaxy Nexus] krazykeyur:
Yeah.. that sounds about right.

I notice echo issues only if the headset volume is 100%. It's mostly gone if I lower the volume by 1 level.. and completely by 2 levels. I am also using the premium route.

Yes.. built in SIP client exclusively.

In voip.ms settings, I only have GSM and g.729 codecs as active.. so the built in client uses GSM as g.729 is not supported. When using CSipSimple, calls use g.729 as I have disabled GSM in CSipSimple.
[Samsung Galaxy Nexus] austriker27:
Well it's not just the gnex because I am doing this setup on my HTC G2 not a gnex and it echoes.

sent from my rocking HTC G2 loaded with ICS
[Samsung Galaxy Nexus] adrman:
If that's the case, it's difficult to point a finger at anything. I've experienced the high mic gain with cSipSimple and SipDroid, on both PBXes and voip.ms. My only constant was the gnex, therefore my conclusion.

Sent from my Nexus 7
[Samsung Galaxy Nexus] wicozani:
Ok, so using the native dialer (internet call, using the same PBXes.org account I automatically set up through Sipdroid) and I hear myself perfectly well using the native dialer (and my native SIP account with PBXes.org). No delays, no echoing, no nothing, just a perfectly responsive call. I have experienced the same on random incoming calls (using internet) through my random dialer; it is as good as any other SIP client I have tried (CSipSimple, Sipdroid, Talkatone). HOWEVER, I now have enough experience to say that this level of clarity on an internet call using the native SIP client (and PBXes.org) only works on a very strong WiFi signal. It's still usable with a dimished signal, but the folks I'm talking to definitely note some breakage and we talk over the top of each other. So, the native dialer setup may not have the best codecs available to it, but if the WiFi signal is strong you'll have super crisp calls. For that reason, I haven't even been using CSipSimple, Sipdroid, or Talkatone.
[Samsung Galaxy Nexus] krazykeyur:
I suspect that's because there is no way to disable PCMA/PCMU codec in pbxes.org..and so that codec is used all the time. Since that codec is kinda bandwidth heavy (using about 160 kbps total) it's only good when using in a WiFi environment. If there was a way to disable those codecs and use GSM in place of that..it would be much better.

Anyways..from my testing, built in SIP drains battery at a faster rate than using a standalone app like csipsimple or sipdroid. Anyone else notice that or is it jusr me?
[Samsung Galaxy Nexus] whitedragonz83:
I found great success with sipdroid and speex codec for 3G/4G. With PCMU for wifi.

Recently tried out csipdroid but while I had no echo issues with sipdroid with echo stuff turned off I can not get csipsimple to prevent echoing most noticeably with speaker phone. Any thoughts?
[Samsung Galaxy Nexus] krazykeyur:
Just did a quick battery test. With nothing running and screen off, built in SIP client used up 10% of my battery in 1 hour. That is ridiculous.

CSipSimple and SipDroid use way less.
[Samsung Galaxy Nexus] Pkt_Lnt:
I'm getting everything moved to my Google Galaxy Nexus from a Samsung Galaxy Exhibit (as I posted much earlier).

Just to clarify settings under Audio Codecs:

G72HD Voice, PCMA, GSM and BV16 set to "Never"

PCMU set to "Only over WLAN"

speex to "Always try"?

Is that how you have them selected? Thanks (button punched too).
[Samsung Galaxy Nexus] whitedragonz83:
Yes through SipDroid+PBxes I have:

PCMA over WLAN

PCMU over WLAN

speex always try

----

So I made a typo earlier as PCMA is the dominate codec I use over WLAN. It seemed to keep the delay under 1s, while PCMU was ~3 seconds. I think it has to do with how much the CPU works. So to reiterate, use PCMA over WLAN.

I also have it so it won't use Sipdroid over Edge, only 3G and WLAN.

Just in case this helps too, I don't seem to have echo issues using the following under Audio/Video:

Earpiece Gain: medium

Microphone Gain: medium

Headset Gain: medium

Headset Mic: medium

Hope that helps and is clear.
[Samsung Galaxy Nexus] Pkt_Lnt:
Thanks for the PCMA clarification, I saw two posts that contradicted, so I searched all your posts on both codecs, and I was not clear, now I am. Still have to ask, if PCMA has less delay over PCMU, why not disable PCMU by setting to "Never" in Sipdroid?
[Samsung Galaxy Nexus] whitedragonz83:
Yes, it makes sense to just disable it, I never went back and did. I will now :)
[Samsung Galaxy Nexus] codesplice:
I don't have much else to contribute at this point (I've actually ceased using VoIP for the moment, as I ended last month with only about 8 minutes used) but I did want to quickly pop in and thank you guys for continuing the discussion. Lots of good solid info here, and it's actually starting to be hard for me to keep up with it. That's awesome, I never thought this thread would take off like it has. I'm really impressed with the community interaction going on here - keep it up!
[Samsung Galaxy Nexus] whitedragonz83:
Thank you for starting the thread! It's been a lot of work, but this thread has brought me an awesome Galaxy Nexus and only a $28.50/month cell bill. The money I am saving is well worth the extra research required by reading this thread.
[Samsung Galaxy Nexus] krazykeyur:
Props to you for starting it and answering many many questions and everyone had.

Anyways, the battery drain with the built in SIP (10% in 1 hour) seems to be gone now that I changed ROMs. I went from CM10 Nightlies to MIUI ROM and over the past 40 minutes, battery has only gone down by 3%.. and that's with about 2-3 minutes of screen on time.
[Samsung Galaxy Nexus] Pkt_Lnt:
Like you, I don't use many minutes either, but my service is weak and spotty in the tiny town where I live (but the views of the Pacific are wonderful). VoIP is my way to talk in the house and not out on the second floor deck that is foggy or windy in the summer, and very wet in the winter rains.

This thread changed my entire cell phone experience, thanks for getting it rolling! :cowboy:
[Samsung Galaxy Nexus] dzshopping:
Does it use my mobile minutes?

If I have enable both Google Chat and my T-mobile to Go number in my Google Voice number. When I receive a call via Sipdriod, does it use my mobile minutes?

BTW, I have purchased GrooveIP before, but the calling quality is really bad. So, I would like to try this new Sipdriod to see how good it is.

Thanks for your tips.
[Samsung Galaxy Nexus] codesplice:
Any time you are using a VoIP solution (SipDroid, GrooveIP, etc) you are making/receiving data calls which will not use your minutes.

If, however, you answer an incoming call using the native Phone application instead of a VoIP client, the call will use your minutes.
[Samsung Galaxy Nexus] dzshopping:
How to increase the volume?

Thanks for your reply. I just tried to use the SipDriod to make serveral calls and found calling quality was much better than that of GrooveIP. I wish I know SipDroid earlier so that I could have saved 5 bucks for the GrooveIP:laugh:

My only complain is the calling volume is too low. I even cannot hear the other side when I was in a little noisy environment. When I make a call using the native caller, it is much louder. It seems the other side might not be able to hear me too. Is there any way to adjust the volume?
[Samsung Galaxy Nexus] whitedragonz83:
There is an option under audio settings for earpiece gain.

Yeh I would have saved $5 also if I knew this much about Sipdroid.
[Samsung Galaxy Nexus] Pkt_Lnt:
Live and learn! Outgoing voip calls with

PCMU disabled were fine. I received two calls and could not answer. The sipdroid screen would not stay up to answer. I went into codecs, enabled PCMU, and incoming calls can be answered. Not sure if it is the disabled codecs. Searching for info.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] jgrinst1:
From the Wiki page on G711, both PCMU and PCMA codecs are essentially the same.

If the caller or callee can support PCMA, it appears to be slightly less CPU intensive, while using the same bandwidth.
[Samsung Galaxy Nexus] herzzreh:
Battery drain can be explained... Native client doesn't use tcp, right? It uses udp iirc. If so, this explains huge battery drain.

It also looks like that voip.ms is a no-go for me because they don't support sip over tcp... This is a shame.
[Samsung Galaxy Nexus] Pkt_Lnt:
Found that, it was discussed earlier in the thread, probably by you; PCMA has less delay / latency as @whitedragonz83 states a few posts above . I was searching for what and how sipdroid and PBXes use and control the codecs. Not much if any info there, unless one is a programmer that can delve into lines of code. That is NOT me.

I'm guessing that on an incoming call to your phone via PBXes and sipdroid, if you have disabled a codec that is in use, the call fails. It likely needs to connect with any and all codecs based on bandwidth at the time, and then negotiate to whatever is the optimum codec once the call is established. Might be a WAG, but my years as a cell phone tech during the 1990s makes me think this is likely.
[Samsung Galaxy Nexus] :
I use the native client with reasonable results. It does allow TCP - just go to "Optional Settings" and change the port number from 5060 to 5061 and transport type from UDP to TCP.

I also use the Google Voice Airplane Mode explained in the OP. To that profile, I've additionally added some settings allowed by the "Secure Settings" app. Namely, the ability to uncheck "receive calls" under the native SIP client options (which is what says drains the battery) when I am not using the Google Voice Airplane Mode (ie out of the house).

I've been using it for a while now with great success. I was using the VOIP last night for a 1.5 hour call and experienced great call quality.

Very satisfied. Thanks again for the great thread, codesplice!
[Samsung Galaxy Nexus] krazykeyur:
Do you use your Google/PBXes account with the built-in SIP client?

If yes, does that not mean that you would always use PCMA/PCMU.. and so it's not bandwidth friendly at all while you're on the road? That's probably why you disable incoming calls while you're on the road.
[Samsung Galaxy Nexus] codesplice:
Nice use of the Secure Setting app!
[Samsung Galaxy Nexus] codesplice:
I'll edit the OP to mention AutoAP sooner, thanks for that feedback.

For troubleshooting purposes, disable AutoAP. Work on getting the calls to work first and then go back and re-enable AutoAP.

When you use SipDroid to set up the PBXes.org Google Voice trunk, you shouldn't really need to adjust any settings within the app. It should make all the configurations you need to at least get started working (you can go back and fine-tune it later). As for deleting your account, you *should* be able to do so via the Delete Account button at the bottom of your Personal Data page at PBXes.org (or https://www4.pbxes.com/config.php?display=20, if the link happens to work). I deleted and recreated mine a few times before settling on an instance that worked; I really don't know why it would tell you that you couldn't delete your account.

As for manually setting up SipDroid, here's the information you should need:

Authorization Username: username-XXX (this will be your PBXes.org username and the number of your Sipdroid extension, as listed under Extensions on the PBXes.org page - mine is jbowdre-200 )

Password: the password associated with that Sipdroid extension - you can change this under the Device Options category on your Sipdroid extension properties at PBXes.org

Server or Proxy: pbxes.org

Domain: (leave empty)

Username or Caller ID: (leave empty)

Port: 5061

Protocol: TCP
​

The part about disabling carrier voicemail is the workaround for getting Google Voice voicemail set up. Any calls made to your GV number will go to your GV voicemail.

Those guides aren't making use of the Google Talk voice interface, and are instead going the route of more traditional VoIP service. Either route works just fine, they're just different ways of accomplishing the same thing.

Really, I would recommend that you check out Talkatone or GrooveIP, as they are FAR easier to set up and get going and work just fine over a solid Wifi connection.

I hope this helps at least a little bit.
[Samsung Galaxy Nexus] krazykeyur:
I'm thinking of a completely new setup for VOIP.. one which has not been done yet.

Inbound: Caller -> Google Voice -> Voip.MS -> PBXes -> Built in SIP

Outbound: Built in SIP -> PBXes -> Voip.MS -> Caller

The advantage of this setup would be being able to use both TCP protocol AND using GSM codec at the same time.

With google -> pbxes -> SIP route, I can use TCP.. but I cant make it use GSM... and it uses the bandwidth hungry PCMA/PCMU

With google -> Voip.MS -> SIP route, I can use GSM codec.. but I cant use TCP protocol.

By using both, I can make voip.MS pass throuth GSM codec only, and then use TCP connection with PBXes.org for a better connection.

I'll have to play around with the connection settings in PBXes to make this possible though... Wish me luck :p
[Samsung Galaxy Nexus] sborman:
Thank you

Codesplice -- I'm sure I speak for many other XDA Developers members when I say that your expertise in this field is admirable and that we all owe you a debt of gratitude for being incredibly generous with your time. You are providing a great public service by creating and continuing to monitor this thread. Thanks. -- Stu Borman
[Samsung Galaxy Nexus] codesplice:
You're just showing off how complicated you can make it, aren't you? Haha, looking forward to seeing the results!

Glad to help, and I'm thrilled that so many people are finding it useful. :)
[Samsung Galaxy Nexus] :
Correct. When I started, I installed sipdroid for the sole purpose of obtaining/automatically setting up the pbxes.org account. So in the native SIP client my account name is "username-200" or whatever and the server is pbxes.org

I only use the VOIP setup when on a known and reliable WIFI connection, so bandwidth isn't really a concern. On the road for voice, I rely on T-Mobile.

Which brings me to a side question- right now I have GV set to make all calls using GV. If I am on the road and have a voice signal (but no data) am I able to make or receive calls? I could argue that it should receive the call, as Google's server should see the incoming call to my GV number and forward to the real T-Mobile number (as well as any other lines [offfice, landline, etc] I have GV set to forward to). But for outgoing, does GV need a data connection to route the call? Worst case, I have to toggle the GV setting to ask every time and I'd be able to make an outgoing call from T-Mobile number, but the recipient of the call of course, would not see my GV number as the caller ID, but the actual T-Mobile number

(I guess I should find/replace all instances of "T-Mobile" with "my Carrier")
[Samsung Galaxy Nexus] NoobNeutralizer:
Gonna be switching from the $50 plan to the $30 plan (with this setup) next month...

Thanks for this guide...

Samsung Galaxy Exhibit powered by Peach Sunrise 2.0.4 (2.3.6 Gingerbread Kernel)
[Samsung Galaxy Nexus] jaybeeunix:
I just tried disabling mobile data and WIFI on my phone, which is set to "use GV for all calls". Then, I called someone. The call went through "via Google Voice", but the recipient saw "unknown caller" rather than my GV or T-Mobile numbers.

I'm also able to receive calls, but, as you stated, that's expected.
[Samsung Galaxy Nexus] sborman:
Very low volume on Galaxy Nexus, calls almost inaudible

In setup of my Google/Samsung Galaxy Nexus, I called T-Mobile support to request that carrier voicemail be disabled, and I didn't notice any volume problem when speaking to the customer service representative. But once the phone was set up to make calls via Sipdroid/PBXes over wifi or over the data side of T-Mobile's $30-a-month plan, the volume of all calls became extremely low -- almost inaudible -- despite setting the volume control on the side of the phone to maximum. People I call can hear me fine, but I cannot hear them well at all.

I called Google support, and the rep said that support calls about volume problems on the Galaxy Nexus are not common at all. He therefore concluded that there is something wrong with my phone, and he offered to exchange it for a new one. I told him that I had actually bought two Galaxy Nexus phones, one for me and one for my wife, but that I had not yet set up the second phone. He recommended I set up the second phone as well and that I should call him back today to let Google support know whether I was experiencing the same problem on the second phone.

I did set up the second phone last night, and I am experiencing the exact same volume problems with it when it operates via Sipdroid/PBXes and GoogleVoice. It seems unlikely to me that two new phones could have the same technical problem, so I'm wondering if the problem is caused by the Sipdroid/PBXes/GoogleVoice setup. I searched this thread for the word "volume" and found very little -- only 19 hits -- so I'm surprised that other followers of this thread apparently are not experiencing the same problems as me. My two phones are virtually unusable for phone calls. It is as if I purchased two new cars, and they work really well, except that they can't go any faster than 10 mph.

I have not yet had time for one remaining test -- to disable all Sipdroid/PBXes/AutoAP/GoogleVoice customization on both phones and see if I still experience volume problems when simply using the phone over T-Mobile's network. If the volume of the phones returns to normal under that condition, then that would mean that the problem is specific to the Sipdroid/PBXes/AutoAP/GoogleVoice setup.

I briefly tried the Equalizer app to increase the volume, but it is complicated and didn't seem to solve the problem. I also briefly tried Volume+ Free, but that didn't work to increase the volume for me either.

Pending my final tests, I am currently considering either returning the phones (I'm still within the allowed return period) and trying something else in the future -- I'm still on Republic Wireless's beta list, for example -- or just paying the usual high T-Mobile monthly rates for conventional prepaid service with a number of minutes that we could live with.

If you can suggest any fixes for this problem or you have experienced the same problem, please let me know. Thanks.

Stu Borman
[Samsung Galaxy Nexus] whitedragonz83:
First, did you increase the volume through sipdroid?

Second, there is a volume+ patch on these forums if you want to try it. It should be in a sticky in the development forums here.
[Samsung Galaxy Nexus] codesplice:
This sounds like an issue with Sipdroid. None of the other components should play a part in the volume of calls. This definitely is not a hardware issue, nor an issue related to Google Voice or T-Mobile service.

Dig around a bit in the Sipdroid settings, under Audio/Video. There are options for setting the amount of gain in the earpiece and for the headset. I think the default setting is medium - bump that up to High and see if it helps.
[Samsung Galaxy Nexus] Lythandra:
Anyone ever use the $70 refill from CallingMart.com?

I've used the $30 one before but as theres no refunds and in theory it should work just fine, I would prefer to get confirmation that the PIN will add to our account just fine.

thanks
[Samsung Galaxy Nexus] codesplice:
I've used the $60 one without any issues.