Open GoogleCodeExporter opened 9 years ago
Don't use that button unless you want to manually fix your PBX. Instead, go to
settings and full out your simonics server and authentication info in the first
account.
Original comment by dbird1...@gmail.com
on 28 Sep 2013 at 4:57
All, one reason this will happen is if your Google password has a special
character in it. PBXes can not handle the special character which causes it not
to connect/authenticate your Google Voice account.
Original comment by dbin78@gmail.com
on 9 Oct 2013 at 5:57
I have tried every solution I can think of and haven't been able to fix this. I
had Sipdroid working perfectly with PBXES and Google Voice. Changing the server
in Personal Data did not fix it. Reverting Hangouts back to Google Chat in my
GMail did not fix it. Remove Google Chat as forwarding phone in Google Voice
settings did not fix it. Deleting my PBXes account and recreating it did not
fix it. I am really at a loss and desperate here because I heavily relied on
this for voice calls. This all coincided with the Hangouts transition. Does
anybody have a solution for this?
Original comment by Jonathan...@gmail.com
on 10 Oct 2013 at 11:49
Hey hey, I made a switch over to the Simonics gateway as suggested above and
that allowed me to make outgoing calls but still wouldn't work for any incoming
calls to my GVoice number. Switching back to my original trunk a week later
somehow "reset" Things. But, it's worth noting if you go the Simonics route,
WRITE DOWN THE ONE-TIME password.
I suggest trying that, whatever Google did definitely appears to have
temporarily "cut" our connection, but it can be restored with patience.
Original comment by melvinwh...@gmail.com
on 11 Oct 2013 at 11:45
Unfortunately I can't go the Simonics route because every time I try to make an
account, Google blocks access. Even if I tell them it's me, it still won't
allow it. :-\
Original comment by Jonathan...@gmail.com
on 12 Oct 2013 at 12:35
I had this problem and was able to fix it by changing my google password and
then the pbxes.org password to what I just changed my google password to, and
making sure the sipdroid app and my native dialer had the new passwords put in.
I would seriously recommend this as after a couple hours of no-go's and
headaches, this turned out to be an extremely simple fix.
Good luck!
Original comment by zackhar...@gmail.com
on 24 Oct 2013 at 7:15
After many months of trying different things, I found this thread, and #18
above is what worked for me! Sipdroid now works, again. Samssung Galaxy
Player 5 (WIFI).
Original comment by jim...@gmail.com
on 29 Nov 2013 at 5:20
Yeah, following what was said above, I changed my password in the pbxes.org
trunk section even though I was positive I set it up correctly. At the top it
should say, "User: xxxxxx/Talk - Connected", when I first went there it said
Disconnected in red.
Just type your google password in the Trunk section even if you think you did
it correctly the first time.
Original comment by jeffrey....@gmail.com
on 14 Dec 2013 at 3:12
@ #58 jeffrey....@gmail.com
When I go to the Trunks section on my profile on PBXES.org
https://www7.pbxes.com/config.php
At the top in RED it says "User: xxxxxx/Talk - Disconnected" and under my
username the password is a three character password "***" even though my gmail
password is a 11 character one. And no matter how many times i change it. the
password never updates.
And on the Sipdroid app the password is a 8 charcater password. And I cant even
read either of them.
So no matter how many times i delete my PBXES account and uninstall/reinstall
Sipdroid I end up with three passwords. My 11 character gamil password, my 3
character PBXES password, and my Sipdroid 8 character password
Also when I sign up for my PBXES account with Sipdroid it wont even let me type
in my gmail username as my PBXES username since I have a period in it.
Original comment by logos.ascetic
on 16 Feb 2014 at 11:54
I am having the same problem too
Original comment by lpeterse...@gmail.com
on 16 Oct 2014 at 2:00
It still always obfuscate to *** no matter how many characters are in your
password. Correct more if I'm wrong, but didn't Google remove xmpp support
rendering this thread useless?
Original comment by dbird1...@gmail.com
on 20 Oct 2014 at 2:10
It's still working for me. I couldn't make calls this summer from overseas to
the US, but I can still make calls inside the US.
Original comment by cyhasti...@gmail.com
on 20 Oct 2014 at 8:17
Original issue reported on code.google.com by
jesses...@gmail.com
on 9 Feb 2011 at 5:36