Ipkall, Sipsorcery, X-lite 3.0, Google Voice time out waiting for callback

[GoogleCodeExporter]

What steps will reproduce the problem?
1.In bound calls are working
2.Out bound calls using X-lite,ipkall, Sipsorcery, GV produce a time out 
message waiting for callback from GV
3.I am using a simple plan script

What is the expected output? What do you see instead?
On making a call, the X-lite phone rings through but then fails with the 
message: "Call failed: TemporarilyUnavailable"

What version of the product are you using? On what operating system?
Running X-lite 3.0 build 56015 on a Mac running OSX 10.4

Please provide any additional information below.

Here's the console report:
NewCall 15:49:39:314 sip1: Executing script dial plan for call to 8278517.
DialPlan 15:49:39:392 sip1: ** Call from "pat healy" 
<sip:xxxxx@sip1.sipsorcery.com>;tag=7740d253 to 8278517 **
DialPlan 15:49:39:392 sip1: Calling 1aaabbbcccc via Google Voice
DialPlan 15:49:39:392 sip1: SDP on GoogleVoiceCall call had public IP not 
mangled, RTP socket 71.120.87.117:50444.
DialPlan 15:49:39:392 sip1: UAS call progressing with Ringing.
DialPlan 15:49:39:392 sip1: Logging into google.com for xxxxxxx@gmail.com.
DialPlan 15:49:39:439 sip1: Google Voice pre-login page loaded successfully.
DialPlan 15:49:39:439 sip1: GALX key 97ygvawzepY successfully retrieved.
DialPlan 15:49:40:298 sip1: Google Voice home page loaded successfully.
DialPlan 15:49:40:298 sip1: Call key F343WPqUKEIYJ64j4N1X2MZSk0I= successfully 
retrieved for xxxxxxgmail.com, proceeding with callback.
DialPlan 15:49:40:314 sip1: SIP Proxy setting application server for next call 
to user xxxxxx as udp:69.59.142.213:5070.
DialPlan 15:49:40:376 sip1: Google Voice Call to 1aaabbbcccc forwarding to 
1aaabbbcccc successfully initiated, callback timeout=30s.
NATKeepAlive 15:49:46:548 sip1: Requesting NAT keep-alive from proxy socket 
tcp:69.59.142.213:5060 to tcp:71.120.87.117:50576.
NATKeepAlive 15:50:07:016 sip1: Requesting NAT keep-alive from proxy socket 
tcp:69.59.142.213:5060 to tcp:71.120.87.117:50576.
DialPlan 15:50:10:376 sip1: Google Voice Call timed out waiting for callback.
DialPlan 15:50:10:454 sip1: Dial plan execution completed without answering and 
with no last failure status.
DialPlan 15:50:10:454 sip1: UAS call failed with a response status of 480.

I have looked for similar problems in Issues without much luck. I am an 
absolute newbie at this. Let me know if posting my plan would be of help.

Appreciate anything you can help me with.

Original issue reported on code.google.com by pheal...@gmail.com on 1 Aug 2010 at 4:08

[GoogleCodeExporter]

Thanks for opening a ticket, Pat.

You said you're a newbie, so here's some background: Have you ever placed a 
call manually using the website? You enter a phone number or choose a contact 
from your address book. You indicate which phone you're using and click Call 
(or Connect?) The phone you're using starts ringing. You answer the call and 
immediately start hearing an outbound ring. That ringing you hear is Google 
Voice connecting you to the number you entered or selected on the web site.

The timeout at 15:50:10:376 indicates that the call never arrived at SIP 
Sorcery when Google Voice tried to call you at your IPKall number. Also, check 
the phone numbers at 15:49:40:376 to make sure that one of them is your IPKall 
number. If neither of those numbers (you masked them the same way) is your 
IPKall number, then Google Voice is not trying to complete your outbound call 
via your IPKall number (and therefore SIP Sorcery).

I know that your incoming calls are working, but having the wrong CB_NUMBER in 
your dialplan will not affect inbound calls since they are just forwarded 
straight in. Can you sign up for a free sipgate one number at sipgate.com and 
follow the steps on wiki page 08 to get it integrated? If IPKall is 
intermittently not forwarding calls to SIP Sorcery, we may never solve it here.

Original comment by easter...@gmail.com on 1 Aug 2010 at 4:28

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

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Closing due to inactivity

Original comment by easter...@gmail.com on 8 Feb 2011 at 1:40

• Changed state: Invalid