"New PBX linked to my Google Voice" is immutably linked to the wrong account

[GoogleCodeExporter]

I'm using a Nexus One on AT&T, Android 2.2.1.

I have a Google Voice account set up properly with the phone, and the Voice 
application works correctly. I have a second Google account set for email and 
contacts, and the new sipdroid feature chooses this second one for the "Google 
Voice Name" without letting me correct the mistake.

The feature seems exciting, I look forward to using it.

Thanks for any help!

Original issue reported on code.google.com by evilgn...@gmail.com on 22 Nov 2010 at 4:32

[GoogleCodeExporter]

You can modify the trunk after account creation by logging into your PBXes 
account with a web browser.

Original comment by pmerl...@googlemail.com on 22 Nov 2010 at 5:25

[GoogleCodeExporter]

Issue 781 has been merged into this issue.

Original comment by pmerl...@googlemail.com on 9 Dec 2010 at 12:20

[GoogleCodeExporter]

Issue 857 has been merged into this issue.

Original comment by pmerl...@googlemail.com on 1 Mar 2011 at 9:35

[GoogleCodeExporter]

The ability to modify the voice account after pbx creation can be a 
deal-breaker for some.  For example, if the primary account on the phone is a 
work account, it may be against policy to enter the password, and therefore 
setup can't occur.

Would it not be possible to enumerate the accounts on the phone and provide a 
drop-down to select the one the user wants to use?

Original comment by shiblon on 23 Sep 2011 at 6:56

[GoogleCodeExporter]

In particular, would the attached patch do anything for you?  I probably missed 
something, but it's pretty small and should work (I'm having trouble getting 
Checkin.createButton set properly, and am not at all confident that I'm 
bootstrapping this correctly, so it would be awesome if a developer could path 
this in and give it a shot).

Original comment by shiblon on 24 Sep 2011 at 6:28

Attachments:

• sipdroid-selection.diff

[GoogleCodeExporter]

Issue 965 has been merged into this issue.

Original comment by pmerl...@googlemail.com on 7 Oct 2011 at 11:21

[GoogleCodeExporter]

I downloaded the patch to the phone and it didn't install when chosen... What 
do I do??

Original comment by lonemcc...@gmail.com on 18 Jan 2012 at 1:59

[GoogleCodeExporter]

I don't know that the patch really works.  I needed a SipDroid developer to 
look at it, but as you can see, I was met with complete silence.  Not sure why 
:)

Original comment by shiblon on 18 Jan 2012 at 2:24

[GoogleCodeExporter]

I don't think it's necessary. See my comment #1.

Original comment by pmerl...@googlemail.com on 2 Feb 2012 at 7:21

[GoogleCodeExporter]

You still don't think it's necessary after Comment #4?  That's a bit surprising.

Some people absolutely cannot afford to do an after-the-fact fixup because the 
account chosen by the phone is a corporate one, and policy *forbids entering 
credentials* in that situation.

So, fixing it up is a nice workaround for some, but I have the following 
rebuttals that I'd like to see a reply to:

1) That doesn't really address the problem, and
2) Fixing this properly is really easy.  There's no reason not to.

Original comment by shib...@google.com on 3 Feb 2012 at 9:15

[GoogleCodeExporter]

What is also possible is entering a wrong password, then correcting it for the 
correct username & password.

But I invite you to check your patch in. I've added you to the list of project 
members. Thanks.

Original comment by pmerl...@googlemail.com on 7 Feb 2012 at 1:34

[GoogleCodeExporter]

Ah, interesting about entering invalid credentials.  I hadn't thought of that 
(it still sucks, but at least it's a complete workaround with that).

Bold move adding me as a contributor.  I couldn't get the patch to work 
properly.  The only reason I didn't give up right away was that I couldn't get 
the unpatched code to compile properly, either.  It's been a long while since I 
last attempted it, however.

Original comment by shib...@google.com on 7 Feb 2012 at 2:56

[GoogleCodeExporter]

Hi,

I have the same issue where the default id that is set up by default is a 
password I cannot enter. Based on the last thread where there were 2 potential 
workarounds:
- a patch to check in to allow one to choose the default account
- a workaround to enter the incorrect password (has someone verified if this 
works. The reason I am hesistant to try this is because it seems a bit 
difficult to delete your pbx account after it has been setup etc.)

On a bit of a side topic but I tried the GrooveIP app that is very similar to 
SipDroid ($4.99). The setup was pretty simple, however, there seems to be quite 
a bit of delay when making a VoIP call. Seems like the client engine in 
GrooveIP is probably bufferring too many of the voice packets and adding quite 
a bit of delay (or maybe it's network related, not sure). For users who have 
gotten SipDroid to work, do you have a sense of its voice over packet quality 
in terms of delay, packetloss etc.

Thanks

Original comment by norepine...@gmail.com on 26 Aug 2012 at 5:47

[GoogleCodeExporter]

Based on http://pbxes.org/wiki/index.php?title=Talk:Main_Page&oldid=848 and 
personal experience, as of August 2012 pbxes.org no longer allows the creation 
of new GTALK links using free accounts. 

Neither the workaround mentioned at that site nor the workaround mentioned at 
http://lucas719.info/function/free_phone (tack config.php?display=6&tech=GTALK 
on to your configuration URL) seem to work at the moment.

So I think the ability to set the linked-to account to something other than the 
owner / default account of the android device within sipdroid (I assume this 
must still be possible but only via the API or something) is more important now 
then the last time a developer modified this ticket.

Original comment by da...@opensysadmin.com on 13 Mar 2013 at 2:56

[GoogleCodeExporter]

It turns out you can now transfer you google phone #, which might help some 
people: https://www.google.com/voice/account/transfer

Original comment by da...@opensysadmin.com on 13 Mar 2013 at 3:21