No calls coming in or going out

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Dialing out or receiving calls
2.
3.

What is the expected output? What do you see instead?
see log below... timeout on call back after connecting to GV

What version of the product are you using? On what operating system?
GV, Sipgate & Sipsorcery  PAP2

Please provide any additional information below.
itor 17:31:33:990: basetype=console, ipaddress=*, user=XXXXX, event=*, 
request=*, serveripaddress=*, server=*, regex=.*.
DialPlan 17:31:50:818 sip1(17016): New call from udp:67.180.46.119:55000 
successfully authenticated by digest.
DialPlan 17:31:50:818 sip1(17016): Using dialplan default for Out call to 
sip:XXXXXXX@sipsorcery.com.
NewCall 17:31:50:833 sip1(17016): Executing script dial plan for call to 
2797100.
DialPlan 17:31:50:865 sip1(17016): ** Call from 
<sip:XXXXX@sipsorcery.com>;tag=fd646c2276572729o0 to XXXXXXX **
DialPlan 17:31:50:865 sip1(17016): Calling 1XXXXXXXXXX via Google Voice
DialPlan 17:31:50:880 sip1(17016): SDP on GoogleVoiceCall call had public IP 
not mangled, RTP socket 67.180.46.119:16462.
DialPlan 17:31:50:880 sip1(17016): UAS call progressing with Ringing.
DialPlan 17:31:50:880 sip1(17016): Logging into google.com for XXXXX@gmail.com.
DialPlan 17:31:50:927 sip1(17016): Google Voice pre-login page loaded 
successfully.
DialPlan 17:31:50:943 sip1(17016): GALX key KNec5d_RaV4 successfully retrieved.
DialPlan 17:31:52:084 sip1(17016): Google Voice home page loaded successfully.
DialPlan 17:31:52:162 sip1(17016): Call key RB0Zn64JIDETp7O8Gs1MnEO4XmQ= 
successfully retrieved for XXXXX@gmail.com, proceeding with callback.
DialPlan 17:31:52:162 sip1(4004): SIP Proxy setting application server for next 
call to user XXXXX as udp:67.222.131.147:5070.
DialPlan 17:31:52:255 sip1(17016): Google Voice Call to 1XXXXXXXXXX initiated, 
callback #1XXXXXXXXXX, phone type 1, timeout 30s.
DialPlan 17:32:22:256 sip1(17016): Google Voice Call timed out waiting for 
callback.
DialPlan 17:32:22:381 sip1(17016): Google Voice Call to 1XXXXXXXXXX was 
successfully cancelled.
DialPlan 17:32:22:381 sip1(17016): Dialplan cleanup for XXXXX.
DialPlan 17:32:22:412 sip1(17016): Dial plan execution completed without 
answering and with no last failure status.
DialPlan 17:32:22:412 sip1(17016): UAS call failed with a response status of 
480.

Original issue reported on code.google.com by for...@gmail.com on 3 Jan 2013 at 5:39

[GoogleCodeExporter]

I would get this error when I let my IPKall inbound gateway number expire. If 
you dial your inbound gateway number (NOT your GV number), does your SIP client 
ring? What do you hear when you call your inbound gateway number?

Original comment by easter...@gmail.com on 3 Jan 2013 at 5:47

• Changed state: Started
• Added labels: Priority-Low, Type-Other
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

it rings

Original comment by for...@gmail.com on 3 Jan 2013 at 6:20

[GoogleCodeExporter]

Sorry, I asked two different questions. Do you hear ringing in the earpiece of 
the phone you're using to call your inbound gateway number, or does your SIP 
client ring to indicate an inbound call? If your SIP client rings and you can 
answer the call, it makes no sense since that's the same mechanism that is used 
to complete an outbound call. A year or two ago there was an issue when SIP 
Sorcery started using load balanced servers. The return call had a 50/50 chance 
of arriving at the server that was trying to establish an outbound call. If the 
return call arrived on the wrong server, this exact error would occur. Is it 
failing for every call? even in rapid succession?

Do you have an Android device handy? I have largely moved on to using the 
sipdroid client's ability to create a SIP extension for GV. It uses Google 
Chat's voice conferencing feature to gateway calls so it completely bypasses 
the whole sipgate, IPKall and SIP Sorcery infrastructure. If you can install 
sipdroid, you're a few clicks away from a much cleaner solution -- unless you 
require the scripting capability at SIP Sorcery.

Original comment by easter...@gmail.com on 3 Jan 2013 at 6:28

[GoogleCodeExporter]

thanks for the heads up on Sipdroid.  Will try it out on a OG Droid.  However, 
I still would like to use the PAP2 if possible.  When I call the gateway number 
from a POTS line it rings.  I hear a ring when I use the SIP client going to 
the gateway, but it keeps ringing until it times out.  Not getting any inbound 
calls.  

NOTE:  I was able to make one outgoing call and received a call this afternoon, 
but am getting timeouts once again.

Original comment by for...@gmail.com on 3 Jan 2013 at 11:02

[GoogleCodeExporter]

BTW... I've tried a call  through my PAP2 and also SIP client running on 
Android and iOS with the same results

Original comment by for...@gmail.com on 3 Jan 2013 at 11:19

[GoogleCodeExporter]

So you have a SIP client logged into your SIP Sorcery account. What are you 
using for your inbound SIP gateway? If you're using sipgate, you need to 
confirm that your SIP Sorcery account is logged into sipgate. If you're using 
IPKall, you need to make sure that your account is configured to forward calls 
to your userid@sipsorcery.com.

If incoming calls aren't ringing all the way through to your SIP client, it 
means there's a breakdown in that path. Also, once you establish the SIP 
account with sipdroid, you can use that SIP login on any SIP client.

You may find a shorter path if you go ahead and setup that SIP account using 
sipdroid and then reconfigure your PAP2 to use the SIP credentials created by 
sipdroid. I know it sounds like a copout, but as soon as Google Voice tries to 
call you for the return call, that's proof that everything we develop and 
support at this website is working properly.

Have you tried establishing a new inbound gateway connection? Sign up for a new 
account at IPKall? If inbound calls ring all the way through to your SIP 
client, then change your script to use the new IPKall as your gateway number.

Original comment by easter...@gmail.com on 3 Jan 2013 at 11:27

[GoogleCodeExporter]

just set-up a PBXes account and I'm getting this message "your call cannot be 
completed please try again later" 

The status and answer reason I continue to see through the sipsorcery portal 
using sipgae as my gateway is timeout 480/temporarily unavailable.

Original comment by for...@gmail.com on 3 Jan 2013 at 11:54

[GoogleCodeExporter]

thanks for all the help.  back up without any changes.  think it was a sipgate 
service issue.  played with sipdroid and pbxes and got that running as well.  
still not bale to get my sip credentials for pbxes to work with mt PAP2 or 
other softphone apps other than sipdroid get a "unauthorized" error message.  
will chek out the pbxes forum for more answers.  appreciate all your work and 
support on the dialplans.  two years of free phone service and counting.

Original comment by for...@gmail.com on 4 Jan 2013 at 11:19

[GoogleCodeExporter]

Glad to hear you got back up and running. Just so you know, I'm able to use my 
pbxes credentials with other SIP clients but only when I include "-200" in the 
userid (although I haven't tried it on my PAP2). Maybe that's the part that's 
missing for you.

Thanks for using the ticketing system and staying with me throughout. Good luck!

Original comment by easter...@gmail.com on 4 Jan 2013 at 11:35

• Changed state: Invalid