_rnr_se key rears its ugly head again

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Dial out on ATA
2. Call fails, sipsorcery log is below, with _rnr_se key fail.  I know this is 
usually a username/password problem, but I've triple checked it.
3. Dialing out from inside GVoice (so it rings my ATA and the other number) 
also doesn't work.

What is the expected output? What do you see instead?
DialPlan 20:07:18:624 sip1(84376): New call from udp:82.35.247.44:5060 
successfully authenticated by digest.
DialPlan 20:07:18:640 sip1(84376): Using dialplan default for Out call to 
sip:411@sipsorcery.com.
NewCall 20:07:18:655 sip1(84376): Executing script dial plan for call to 411.
DialPlan 20:07:18:687 sip1(84376): ** Call from "SIPSORCERYUSERNAME" 
<SIPSORCERYUSERNAME@sipsorcery.com>;tag=5f032aebdd2694co0 to 411 **
DialPlan 20:07:18:687 sip1(84376): Calling 18004664411 via Google Voice
DialPlan 20:07:18:687 sip1(84376): SDP on GoogleVoiceCall call had public IP 
not mangled, RTP socket 82.35.247.44:16432.
DialPlan 20:07:18:687 sip1(84376): UAS call progressing with Ringing.
DialPlan 20:07:18:687 sip1(84376): Logging into google.com for 
GVOICEUSERNAME@gmail.com.
DialPlan 20:07:18:733 sip1(84376): Google Voice pre-login page loaded 
successfully.
DialPlan 20:07:18:733 sip1(84376): GALX key QdK6fSziTVs successfully retrieved.
DialPlan 20:07:18:952 sip1(84376): Google Voice home page loaded successfully.
DialPlan 20:07:18:999 sip1(84376): Exception on GoogleVoiceCall. Could not find 
_rnr_se key on your Google Voice account page, callback cannot proceed.
DialPlan 20:07:18:999 sip1(84376): Dialplan cleanup for SIPSORCERYUSERNAME.
DialPlan 20:07:19:187 sip1(84376): Dial plan execution completed without 
answering and with no last failure status.
DialPlan 20:07:19:187 sip1(84376): UAS call failed with a response status of 
480.

What version of the product are you using? On what operating system?
SimpleDialPlan

Please provide any additional information below.
I am on an ATA from outside the US, however, my Google voice account has 
existed and worked for years.

Original issue reported on code.google.com by rexford....@gmail.com on 21 Jul 2011 at 8:14

[GoogleCodeExporter]

More googling has uncovered that it is likely related to google's increased 
security mechanisms, as I usually log into Gvoice from a UK-based IP, 
SIPSorcery's IP comes up as an unknown login attempt.  Currently there is no 
solution, but I will keep prodding at it.

Original comment by rexford....@gmail.com on 22 Jul 2011 at 8:49

[GoogleCodeExporter]

More details and possible solution:

http://forum.sipsorcery.com/viewtopic.php?f=6&t=3671

Original comment by mte...@gmail.com on 23 Jul 2011 at 6:53

• Changed state: Accepted

[GoogleCodeExporter]

I was able to fix the "Could not find _rnr_se key ..." problem on my local 
copy. When trying to authenticate in GoogleVoiceCall.cs, the response text from 
google was that my cookies weren't enabled. I was able to fix it by adding this 
after the galx request, before the login request, "m_cookies.Add(new 
Uri(PRE_LOGIN_URL), galxResponse.Cookies);" My change is on line 187.

Original comment by godwin....@gmail.com on 11 Sep 2011 at 9:25

Attachments:

• GoogleVoiceCall.cs

[GoogleCodeExporter]

Adding a comment here, since I am experiencing the same issue as the parent, 
but I am in the US.

Up until earlier today, the GoogleVoice functionality worked, and then it 
stopped about an hour ago.  I am able to dial from the GV site, and have it 
dial me on my PAP2T (sipgate is my sip provider).  It seemed to happen just 
after I logged into the GV site to make a call from there.  the _rnr_se key is 
in the page.  

I have tried changing my password, dial plans to the Simple Dial Plan stock, 
and some of the other suggested.

DialPlan 23:35:35:164 sip1(7092): New call from udp:198.160.139.1:6828 
successfully authenticated by digest.
DialPlan 23:35:35:180 sip1(7092): Using dialplan default for Out call to 
sip:2@sipsorcery.com.
NewCall 23:35:35:195 sip1(7092): Executing script dial plan for call to 2.
DialPlan 23:35:35:226 sip1(7092): ** Call from "NAME" 
<sip:NAME@sipsorcery.com>;tag=6f8b77f5b85432f2o1 to 2 **
DialPlan 23:35:35:242 sip1(7092): Calling 14XXXXXXXX via Google Voice
DialPlan 23:35:35:242 sip1(7092): SDP on GoogleVoiceCall call had RTP socket 
mangled from 192.168.2.2:16386 to 198.160.139.1:16386.
DialPlan 23:35:35:242 sip1(7092): UAS call progressing with Ringing.
DialPlan 23:35:35:242 sip1(7092): Logging into google.com for NAME@gmail.com.
DialPlan 23:35:35:351 sip1(7092): Google Voice pre-login page loaded 
successfully.
NATKeepAlive 23:35:35:430 sip1(1932): Requesting NAT keep-alive from proxy 
socket udp:69.59.142.213:5060 to udp:198.160.139.1:6828.
DialPlan 23:35:35:633 sip1(7092): GALX key HGdUg-9I8Zo successfully retrieved.
DialPlan 23:35:36:523 sip1(7092): Google Voice home page loaded successfully.
DialPlan 23:35:36:633 sip1(7092): Exception on GoogleVoiceCall. Could not find 
_rnr_se key on your Google Voice account page, callback cannot proceed.
DialPlan 23:35:36:633 sip1(7092): Dialplan cleanup for NAME.
DialPlan 23:35:36:773 sip1(7092): Dial plan execution completed without 
answering and with no last failure status.
DialPlan 23:35:36:773 sip1(7092): UAS call failed with a response status of 480.

Original comment by pgarde...@gmail.com on 12 Dec 2011 at 11:49

[GoogleCodeExporter]

The problem might be in 2-step authentication; there's no simple solution. Try 
creating a fresh GV account and using it for your calls.

Original comment by mte...@gmail.com on 17 Dec 2011 at 7:09

[GoogleCodeExporter]

Except I am not using 2-step authentication.  I specifically did not use that, 
and have made sure it is not enabled, as well as tested it on a brand new 
computer.

Original comment by pgarde...@gmail.com on 17 Dec 2011 at 7:25

[GoogleCodeExporter]

Anyway, creating a fresh GV account only takes a few minutes. Or, PM to 
Sipsorcery's admin your account details and ask to look into the problem. You 
never know what kind of extra authentication Google is asking when you log in 
from Sipsorcery server's IP; the admin has access to the server and can check 
it out.

Original comment by mte...@gmail.com on 18 Dec 2011 at 5:05

[GoogleCodeExporter]

Original comment by easter...@gmail.com on 2 Mar 2012 at 1:29

[GoogleCodeExporter]

I've noticed a lot of people are studying this issue report. If you're getting 
the _rnr_se key error, the best thing you can do is PM Aaron in the SIP Sorcery 
support forum. It would probably help your case if you have a paid account, and 
it also helps Aaron keep the service up and running for everyone.

If you have an Android device, you're willing to leave SIP Sorcery and don't 
need the advanced features that SIP Sorcery makes available through its 
scripting language, please go to wiki page 10 to learn how to use sipdroid to 
automatically create and configure an account for you at pbxes.com. I've had 
the _rnr_se key issue since last year but the sipdroid/pbxes combination worked 
perfectly on the first try. Learn more here

http://code.google.com/p/google-voice-sipsorcery-dialplans/wiki/10_Sipdroid_Inte
gration_with_PBXes

Original comment by easter...@gmail.com on 13 Jun 2012 at 12:17

[GoogleCodeExporter]

Try using the clearing the CAPTCHA link in this page 
https://support.google.com/mail/bin/answer.py?hl=en&answer=78754
also works when getting the "suspicious sign in prevented" email that prevents 
Sipsorcery from signing in and causes the Could not find _rnr_se key on your 
Google Voice account page issue

Original comment by 214zax...@gmail.com on 18 Jun 2012 at 12:56

[GoogleCodeExporter]

Had the same problem and clearing the CAPTCHA link worked perfectly. Thanks!!!

Original comment by mikenaus...@gmail.com on 30 Jun 2012 at 3:20

[GoogleCodeExporter]

I just tried using https://www.google.com/a/sipsorcery.com/UnlockCaptcha

It will not accept my username/password even though they are correct... not 
sure what to do.

Original comment by jyj...@gmail.com on 3 Jul 2012 at 12:50

[GoogleCodeExporter]

Had the same problem and clearing the captcha worked for me as well.  I have 
two step authentication disabled and when i logged into my account i was seeing 
the suspicious login message at the top.  Didn't have to change passwords or 
create a new account.  Just cleared captcha and dialed out like normal with my 
ata and it worked fine.

Original comment by whoop...@gmail.com on 5 Jul 2012 at 12:09

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

@jyjjy7 don't use that link.

First, make sure your SIP Sorcery credentials are correct. Test by calling your 
inbound SIP gateway number. Your SIP client should ring and you should have 
audio in both directions. If you can receive inbound calls correctly, visit 
this page (not the one you visited) and fill out the CAPTCHA.

https://www.google.com/accounts/DisplayUnlockCaptcha

You must then place an outbound call via a SIP client logged into SIP Sorcery 
within 10 minutes. The rnr se key issue should be cleared and your call should 
go through just fine. I just fixed two accounts using this process this morning.

Original comment by easter...@gmail.com on 5 Jul 2012 at 1:45

• Added labels: Type-Other
• Removed labels: Type-Defect

[GoogleCodeExporter]

Clearing the captcha didn't work for me. I have 2-step authentication on though 
(and have had it on since I signed up for SIPSorcery). Is it a known issue that 
it doesn't work with 2-step authentication?

Original comment by kni...@gmail.com on 5 Jul 2012 at 2:09

[GoogleCodeExporter]

Yes, @knifed, I recall reading about that a couple years ago. Been an issue for 
a long time. Since you are doing "the right thing" with respect to 2-step 
authentication, you may wish to setup another account just for Google Voice. 
Painful, I know, but it comes down to how hard you wish to stand up for your 
beliefs.

Original comment by easter...@gmail.com on 5 Jul 2012 at 2:14

[GoogleCodeExporter]

This link worked for me too right away
https://www.google.com/accounts/DisplayUnlockCaptcha
Thanks guys

Original comment by katieca...@gmail.com on 7 Jul 2012 at 4:23

[GoogleCodeExporter]

Awesome worked perfect!

Original comment by araque.r...@gmail.com on 30 Jul 2012 at 4:55