Closed GoogleCodeExporter closed 8 years ago
Here's the error from sipsorcery console
DialPlan 01:44:05:901 sip1(192): Exception on GoogleVoiceCall. Could not find
_rnr_se key on your Google Voice account page, callback cannot proceed.
Original comment by ijav...@gmail.com
on 12 Oct 2011 at 1:46
Most certainly you mistyped your GV credentials (login, password). It could
also be 2-step verification issue, refer to:
http://forum.sipsorcery.com/viewtopic.php?f=6&t=3165
> Mike
Original comment by mte...@gmail.com
on 13 Oct 2011 at 6:06
DialPlan 16:19:53:603 sip1(632): Logging into google.com for xxxxxx@gmail.com.
DialPlan 16:19:53:932 sip1(632): Google Voice pre-login page loaded
successfully.
DialPlan 16:19:54:088 sip1(632): GALX key XRoXtXdXGXx successfully retrieved.
DialPlan 16:19:56:619 sip1(632): Google Voice home page loaded successfully.
DialPlan 16:19:56:916 sip1(632): Exception on GoogleVoiceCall. Could not find
_rnr_se key on your Google Voice account page, callback cannot proceed.
It seems to login fine but cannot find the rnr key. When i log into gmail i can
see the source code and find the hidden value.
I do not have 2-step verification setup so that cannot be the issue.
I changed my password as well which used to have characters in them to just
words thinking that could be it. But that didnt do that trick either.
Running out of things to try. Any suggestions are welcome.
Original comment by ijav...@gmail.com
on 13 Oct 2011 at 4:23
Ok so i think i found the problem. Google voice complained about unauthorized
access cause of different ip logging into google voice. So on my main account i
couldnt configure it. So i gave up and created a fresh google voice account
which i never logged into and used that on dialplan and it worked. Hope this
helps someone out there.
Original comment by ievilw...@gmail.com
on 14 Oct 2011 at 12:33
creating new google voice account using US proxy worked for me as well.
Thanks.
Original comment by sohailt...@gmail.com
on 1 Nov 2011 at 4:43
Closing as resolved. It was not a problem caused by our scripts. Thank you for
opening a ticket here.
Original comment by easter...@gmail.com
on 1 Mar 2012 at 10:12
Original issue reported on code.google.com by
ijav...@gmail.com
on 11 Oct 2011 at 8:14