Unable to verify IPKall number in Google Voice

[GoogleCodeExporter]

I decided to switch calling providers, since you guys now want IPKall to be 
used.

The problem is, that something along the line isn't excepting calls.

See this console output:
DialPlan 10:31:38:804 sip1(32264): Using dialplan default for In call to 
sip:[me]@sipsorcery.com.
NewCall 10:31:38:836 sip1(32264): Executing script dial plan for call to [me]
DialPlan 10:31:38:976 sip1(32264): ** Call from "My GV Number's City" <sip:[my 
google number]@66.54.140.46>;tag=as762ac5aa to [me] **
DialPlan 10:31:38:976 sip1(32264): Local time: 02/08/2011 05:31
DialPlan 10:31:38:976 sip1(32264): FromName: '[My Google Number]'
DialPlan 10:31:39:070 sip1(32264): URI dialing: [me]@local
DialPlan 10:31:39:070 sip1(32264): Commencing Dial with: [me]@local.
DialPlan 10:31:39:101 sip1(32264): Call leg is for local domain looking up 
bindings for [me]@sipsorcery.com for call leg [me]@local.
DialPlan 10:31:39:117 sip1(32264): 2 found for [me]@sipsorcery.com.
DialPlan 10:31:39:117 sip1(32264): ForkCall commencing call leg to sip:[me]@[my 
cable modem IP address]:5060.
DialPlan 10:31:39:132 sip1(32264): SIPClientUserAgent Call using alternate 
outbound proxy of udp:69.59.142.213:5060.
DialPlan 10:31:39:132 sip1(32264): Switching to sip:[me]@[my cable modem IP 
address]:5060 via udp:69.59.142.213:5060.
DialPlan 10:31:39:132 sip1(32264): SDP on UAC call had public IP not mangled, 
RTP socket 66.54.140.46:16670.
DialPlan 10:31:39:336 sip1(32264): Information response 100 Trying for 
sip:[me]@[my cable modem IP address]:5060.
DialPlan 10:31:39:336 sip1(32264): Response 486 Busy Here for sip:[me]@[my 
cable modem IP address]:5060.
DialPlan 10:31:39:664 sip1(32264): Call failed: code 486, Busy Here
DialPlan 10:31:39:664 sip1(32264): UAS call failed with a response status of 
480 and [me] Not online.
DialPlan 10:31:39:664 sip1(32264): Dialplan cleanup for [me].
DialPlan 10:31:40:117 sip1(32264): Dial plan execution completed with normal 
clearing.

So, I'm using a Linksys PAP2T-NA that I bought from VOIPLink (and I'm thinking 
of contacting them soon; they do offer some technical support since I bought 
from them).

I've got the first line (the only one I'm using) configured correctly, no 
outbound proxies no special tricks, just sipsorcery.com, my username and 
password, and that's about it.

Not sure what's going on to have it reject incoming calls. Can you help me?

Original issue reported on code.google.com by XANAVi...@gmail.com on 8 Feb 2011 at 10:42

[GoogleCodeExporter]

The weird thing is that both SIPSorcery's console and my Linksys ATA's webpage 
both report me as online, but the dial plan does not and it gives me the error 
of 486 Busy Here.

If I launch a softphone on my computer, I can sign in just fine and accept 
calls (but, I can't answer calls for some reason on the softphone; I tell it to 
accept an incoming call and it tries to but then it says the call hung up on 
me).

Original comment by XANAVi...@gmail.com on 8 Feb 2011 at 10:46

[GoogleCodeExporter]

Couple things with your update 1.

1) The dial plan doesn't know anything about your online status. There may be 
an issue with SIP Sorcery receiving calls from IPKall

2) First you say if you launch a softphone on your computer you can sign in and 
accept calls but then immediately say you can't answer calls.

Could you please rewrite your question? Where exactly are you getting a 486 
Busy Here? Can you or can you not answer calls?

Original comment by easter...@gmail.com on 8 Feb 2011 at 12:49

• Changed state: Started
• Added labels: Type-Other
• Removed labels: Type-Defect

[GoogleCodeExporter]

I continued working on it last night and got incoming calls to actually ring my 
ATA phone (somehow...).
I can't answer them from the phones hooked up to the ATA, though; if I press 
the 'Talk' or 'Speakerphone' keys, it will just act like I wanted to make a new 
outbound call instead of answering the incoming one (which will be like it 
never happened at that point, if I press 'Flash' or do what I just said above, 
the incoming call won't be there anymore).

For my softphone on my computer: I think it's just my laptop; probably the 
firewall blocking incoming connections, cause I can answer calls coming onto my 
cellphone's SIP client. From my laptop (running ExpressTalk), I'll see the 
incoming call and I can press the answer key on ExpressTalk, but it will not 
accept the incoming call, it will just hang up and act like the call never came 
in.

Original comment by XANAVi...@gmail.com on 8 Feb 2011 at 11:00

[GoogleCodeExporter]

Sorry for posting so often right now.

I just wanted to say that I did get the number to verify with Google Voice, and 
I changed it on the dial plan. But, when I dial out from my ATA-connected phone 
now, it will act like it's ringing and then just give me a busy signal (I'm 
connected and online in SIPSorcery).

Finally, I didn't have incoming calls working in SIPGate either. They just 
never showed up (SIPSorcery console reported that 486 Busy Here status), but 
that was then and I now have incoming calls to show up through IPKall 
forwarding to SIPSorcery (but I really don't feel like maybe taking a step 
backwards since registering with SIPGate isn't the best thing to do and it 
might just not see incoming calls again).

Original comment by XANAVi...@gmail.com on 8 Feb 2011 at 11:05

[GoogleCodeExporter]

Okay, I got outbound dialing working again (it was wrong settings on my ATA).

I still don't have incoming calls able to be answered by the ATA-connected 
phones, though. It still will ring through and I'll see the call, but if I go 
to answer it, it will act like I want to make a new call outbound...

The only device I can answer incoming calls for sure on is my cellphone running 
Linphone. I can't see any difference between the settings on my ATA and the 
settings on Linphone.

Original comment by XANAVi...@gmail.com on 8 Feb 2011 at 11:33

[GoogleCodeExporter]

Lowering the priority since outbound calling is working. I suggest that you 
also pursue this in the SIP Sorcery forums and maybe even IPKall. The only part 
we support here is working fine since you can place outbound calls. Will leave 
this open so you can post updates for the recorded history.

Original comment by easter...@gmail.com on 9 Feb 2011 at 9:29

• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Original comment by easter...@gmail.com on 9 Feb 2011 at 10:49

[GoogleCodeExporter]

Closing due to inactivity for over one year. Marking invalid as the issue was 
incorrect credentials entered into the ATA.

Original comment by easter...@gmail.com on 1 Mar 2012 at 10:39

• Changed state: Invalid