Closed GoogleCodeExporter closed 9 years ago
Check out if the call appears in the Console on Sipsorcery.com. If it doesn't,
the
problem must be in your ATA's dialplan, it wouldn't allow international calls.
If the
call does appear there, copy/paste console output here (remove personal and
sensitive
data).
Original comment by mte...@gmail.com
on 22 Feb 2010 at 10:29
I couldn't find anything in the console screen, but I did find the the CDRs
records
in the calls screen. The recorders for the international calls say that the
status
are 404 and the Ans.Reason are "Not found (illegal format)" . There are two
records
for each international call, the first Dirn is "In" and the second is "Out",
and the
first destination is "sip:011+country code+phone number@sipsorcery.com" and the
second destination is "sip:00+country code+phone number@sipgate.com"
It seems that all my phone calls are not routing throught Google Voice.
Sorry, I don't know how to copy/paste the CDRs from the sipsorcery screen.
Thank you.
Original comment by victor...@gmail.com
on 22 Feb 2010 at 11:07
Where there is a CDR record, there is console output. I think you forgot to
click on
"Connect" in the Console (must do it prior to making a call).
Original comment by mte...@gmail.com
on 22 Feb 2010 at 11:20
DialPlan 23:25:00:415 sip1: Using dialplan Google Voice Complex for Out call to
sip:01186xxxxxxxxxxx@sipsorcery.com.
NewCall 23:25:00:477 sip1: Executing script dial plan for call to
01186xxxxxxxxxx.
DialPlan 23:25:00:555 sip1: ** Call from "xxxxxxxxxxx"
<sip:xxxxxxxxxx@sipsorcery.com>;tag=1f79dbf1bce1393o0 to 01186xxxxxxxxxxx **
DialPlan 23:25:00:555 sip1: Local time: 02/22/2010 17:25
DialPlan 23:25:00:571 sip1: Number in ENUM format: 86xxxxxxxxxx
DialPlan 23:25:00:680 sip1: Default route applied
DialPlan 23:25:00:680 sip1: Commencing Dial with: 0086xxxxxxxxxxx@Sipgate.
DialPlan 23:25:00:680 sip1: Attempting to locate a provider for call leg:
sip:0086xxxxxxxxxxx@Sipgate.
DialPlan 23:25:00:680 sip1: ForkCall commencing call leg to
sip:0086xxxxxxxxxxx@sipgate.com.
DialPlan 23:25:00:680 sip1: Switching to sip:0086xxxxxxxxxxx@sipgate.com:5060
via
udp:10.215.50.4:5060.
DialPlan 23:25:00:680 sip1: SDP on UAC call had RTP socket mangled from
192.168.1.100:16394 to 173.30.117.78:16394.
DialPlan 23:25:00:774 sip1: Response 404 Not found (illegal format) for
sip:0086xxxxxxxxxxxx@sipgate.com.
DialPlan 23:25:00:774 sip1: Call failed: code 404, Not found (illegal format)
DialPlan 23:25:00:774 sip1: UAS call failed with a response status of 404 and
Not
found (illegal format).
DialPlan 23:25:01:212 sip1: Dial plan execution completed with normal clearing.
ContactRegisterInProgress 23:25:18:884 sip1: Checking SIP Provider registration
for
Gizmo5.
ContactRegisterInProgress 23:25:18:884 sip1: Sending initial register for
xxxxxxxxx
and Gizmo5 to udp:198.65.166.131:5060.
ContactRegisterInProgress 23:25:18:994 sip1: Initiating registration for
xxxxxxxxxxx
on sip:proxy01.sipphone.com:5060.
ContactRegistered 23:25:19:337 sip1: Contact successfully registered for
xxxxxxxxxxx
on sip:proxy01.sipphone.com:5060, expiry 3600s.
Here is the console copy/paste
Thank you
Original comment by victor...@gmail.com
on 22 Feb 2010 at 11:31
Here is the problem point:
DialPlan 23:25:00:774 sip1: Response 404 Not found (illegal format) for
sip:0086xxxxxxxxxxxx@sipgate.com
What happened, the dialplan reformatted the number adding 00 prefix to it and
passed
it over to SIPGate. Apparently SIPGate expected the number in some different
format
(e.g. 011 + number). Is it a bug in the code? Probably so, but...
The main difference between "Simple" and "Complex" dialplan is that the first
is
using Google Voice for all destinations while the latter routes only North
America to
Google Voice. International calls are made with their respective providers.
Let's go back to the origins:
http://www.mysipswitch.com/forum/viewtopic.php?t=1634
Read "Instructions" in the opening post, right after the dialplan. P.4 there
specifically says that you need to edit VSPtable and selectVSP to get your
international calls properly routed. BTW, the original VSPtab uses Future-Nine
(F9)
for international calls. 00, 02, 03, 04 prefixes instruct F9 to use default,
grey,
white and premium routes, respectively.
For some reason easternpa modified the table replacing F9 with SIPGate. Complex
Dial
Plan correctly followed the change and substituted dialed number adding 00 in
front
of the number but apparently SIPGate doesn't honor this prefix. I can't check
it
since I don't have SIPGate account.
So... conclusions: if you want to use Google Voice as your only VoIP provider,
you'd
be better off with Simple Dial Plan. If you have several VoIP providers, you
should
use Complex Dial Plan, but in this case you need to follow instructions and
make
appropriate changes to VSPtab and selectVSP.
Original comment by mte...@gmail.com
on 23 Feb 2010 at 4:01
Victor any updates here?
Original comment by easter...@gmail.com
on 26 Mar 2010 at 2:41
I changed to StuartofOz Intl Dialing v3. It works well for me.
Original comment by victor...@gmail.com
on 31 Mar 2010 at 8:58
Thanks, Victor. Sorry I didn't see your post earlier.
Original comment by easter...@gmail.com
on 28 Apr 2010 at 5:44
Original issue reported on code.google.com by
victor...@gmail.com
on 22 Feb 2010 at 9:18