Incoming call won't ring my phone attached to ATA2

[GoogleCodeExporter]

I don't have any In Dial Plan set up in my SIPSORCERY Account. Do I need a 
In Dail Plan? Some time the incomming call does ring the phone, but 
majority of the time, the phone call goes to my GOOGLE Voice voice mail 
box.

Here is the copy/paste from the SIPSORCERY Console screen

DialPlan 00:08:16:994 sip1: No dialplan specified for incoming call to 
netghoster@sipsorcery.com, registered bindings will be used.
DialPlan 00:08:17:072 sip1: Forwarding incoming call for 
netghoster@sipsorcery.com to 1 bindings.
NewCall 00:08:17:072 sip1: Executing script dial plan for call to 
netghoster.
DialPlan 00:08:17:072 sip1: Commencing Dial with: 
netghoster@sipsorcery.com.
DialPlan 00:08:17:134 sip1: Call leg is for local domain looking up 
bindings for netghoster@sipsorcery.com for call leg 
netghoster@sipsorcery.com.
DialPlan 00:08:17:259 sip1: 1 found for netghoster@sipsorcery.com.
DialPlan 00:08:17:259 sip1: ForkCall commencing call leg to 
sip:netghoster@173.30.117.78:5060.
DialPlan 00:08:17:259 sip1: SIPClientUserAgent Call using alternate 
outbound proxy of udp:10.215.50.4:5060.
DialPlan 00:08:17:259 sip1: Switching to sip:netghoster@173.30.117.78:5060 
via udp:10.215.50.4:5060.
DialPlan 00:08:17:259 sip1: SDP on UAC call had public IP not mangled, RTP 
socket 74.125.240.66:31050.
DialPlan 00:08:21:681 sip1: No dialplan specified for incoming call to 
netghoster@sipsorcery.com, registered bindings will be used.
DialPlan 00:08:21:744 sip1: Forwarding incoming call for 
netghoster@sipsorcery.com to 1 bindings.
NewCall 00:08:21:744 sip1: Executing script dial plan for call to 
netghoster.
DialPlan 00:08:21:760 sip1: Commencing Dial with: 
netghoster@sipsorcery.com.
DialPlan 00:08:21:853 sip1: Call leg is for local domain looking up 
bindings for netghoster@sipsorcery.com for call leg 
netghoster@sipsorcery.com.
DialPlan 00:08:21:900 sip1: 1 found for netghoster@sipsorcery.com.
DialPlan 00:08:21:900 sip1: ForkCall commencing call leg to 
sip:netghoster@173.30.117.78:5060.
DialPlan 00:08:21:900 sip1: SIPClientUserAgent Call using alternate 
outbound proxy of udp:10.215.50.4:5060.
DialPlan 00:08:21:900 sip1: Switching to sip:netghoster@173.30.117.78:5060 
via udp:10.215.50.4:5060.
DialPlan 00:08:21:900 sip1: SDP on UAC call had public IP not mangled, RTP 
socket 204.155.29.58:15520.
DialPlan 00:08:38:651 sip1: Client call cancelled halting dial plan.
DialPlan 00:08:38:651 sip1: Dialplan call was terminated by client side 
due to ClientCancelled.
DialPlan 00:08:38:651 sip1: Cancelling all call legs for ForkCall app.
DialPlan 00:08:38:651 sip1: Cancelling forwarded call leg, sending CANCEL 
to sip:netghoster@173.30.117.78:5060.
DialPlan 00:08:38:651 sip1: Dial command was halted by cancellation of 
client call after 21.39s.
DialPlan 00:08:38:729 sip1: Dial plan execution completed with normal 
clearing.
DialPlan 00:08:54:417 sip1: Dial plan execution completed without 
answering and a last failure status of TemporarilyNotAvailable Timeout, no 
response from server.
DialPlan 00:08:54:417 sip1: UAS call failed with a response status of 480 
and Timeout, no response from server.

Original issue reported on code.google.com by victor...@gmail.com on 26 Feb 2010 at 12:26

[GoogleCodeExporter]

You do not need an inbound dial plan the way we're using the site. I, too, have 
had
issues with inbound calls not ringing, but it varies which devices or 
softphones ring
and which ones don't. If I make an outbound call the PAP2, invariably it will 
ring
for inbound calls for at least a few minutes, but then not ring after that.

Original comment by easter...@gmail.com on 26 Feb 2010 at 1:32

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

[GoogleCodeExporter]

Yes, I have this exact same problem; the exact same one (in "problems with 
incoming 
calls").

I hope that maybe there will be a fix for this somehow.

In the meantime, information in my issue thread might help you, so take a look 
there if 
you like.

Original comment by XANAVi...@gmail.com on 26 Feb 2010 at 2:09

[GoogleCodeExporter]

hi, i'm also having the same problem as described above. i am using ata spa1001 
and 
setup with sipsorcery+sipgate+gv, however incoming calls most of the time 
doesn't work.

i haven't not open the 5060 port forwarding yet but is necessary to open the 
port?

please advise, thanks!
-shey 

Original comment by myvoipph...@gmail.com on 13 Mar 2010 at 8:39

[GoogleCodeExporter]

Please the comment 7 in the following link. My problem got sovled at lease part 
of 
it after I followed the instruction to make the changes in the PAP2T setuping.

http://code.google.com/p/google-voice-sipsorcery-dialplans/issues/detail?id=11

Original comment by victor...@gmail.com on 13 Mar 2010 at 2:39

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Soonki, if you're still having the issue, could you please open your own ticket 
so
that we may give you personal attention? The main issue in this ticket appears 
to
have been resolved some time ago, and I need to start closing these tickets 
hanging open.

Thank you!

Original comment by easter...@gmail.com on 28 Apr 2010 at 5:43

• Changed state: Verified

[GoogleCodeExporter]

easternpa,

I followed the instruction on the comment 7 again, it seems working now. I am 
going to 
delete above my comment to avoid any confusion to other users.

Thanks for checking the status.

Original comment by soonki...@gmail.com on 28 Apr 2010 at 9:01