search

Sunr1ses / google-voice-sipsorcery-dialplans

Automatically exported from code.google.com/p/google-voice-sipsorcery-dialplans
1 stars 0 forks source link

Problems dialing out with IpKall #17

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I setup IpKall to work with sipsorcery by tying my ss sip address to my 
IpKall number.  Incoming calls work fine and I can use the Google voice web 
site to make outgoing calls fine as well.  However, using the Google Voice 
simple dialplan to dial out exhibits erratic behavior.  7 digit dialing 
works sometimes while 10 digit dialing rarely works.

Here is the current dial plan I am using (identifying information has been 
removed but it is structured the way I use with all fields filled in):

#==================== BEGIN CODE ======================#

# Settings
AREA_CODE = '313'                    # my area code
GV_USER = 'noname@gmail.com'       # my GV e-mail address (user@gmail.com)
GV_PASS = 'mypassword'              # my GV password
SG_NUMBER = '425XXXXXXX'             # my 10-digit Sipgate number (not 
always 415)
G5_NUMBER = '747XXXXXXX'             # my 10-digit Gizmo5 number (always 
747)

SPEED_DIAL = {                       # my speed dial numbers
  '1'   => '19879879876',                 # Mom
  '123' => '12345678901',                 # Work
  '45'  => '417479876543',                # Gizmo BFF
  '411' => '8004664411',                     # Google 411
  '266' => '4153767253@podlinez.net',     # CNN Headlines
}

# Logic
number = req.URI.User.to_s
SPEED_DIAL[number] && number = SPEED_DIAL[number]
case number
  when /^4(1?747\d{7})$/ then sys.Dial("#{$1}@Gizmo5")
  when /@/ then sys.Dial(number)
  when /^1?([2-9]\d{2})?([2-9]\d{6})/
    number = '1' + ( $1 || AREA_CODE ) + $2
    vsp = SG_NUMBER =~ /^\d+$/ ? [SG_NUMBER,1] : [G5_NUMBER,7]
    sys.GoogleVoiceCall(GV_USER,
GV_PASS,vsp[0],number,'.*',vsp[1],30)
end

#===================== END CODE =======================#

Original issue reported on code.google.com by lovin...@gmail.com on 17 Jan 2010 at 8:34

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Here is an example of the no rhyme or reason nature of outbound calls I am 
experiencing.  I called to Goog-411 (1-800-466-4411) twice using 11 digit 
calling and 
the first time it failed and the second time it went through.  Below is the 
console 
information for both calls.

Failed call:

DialPlan 20:51:48:223: New call from udp:98.224.207.xxx:5060 successfully 
authenticated by digest.
DialPlan 20:51:48:551: Using dialplan Google Voice Simple Dial Plan for Out 
call to 
sip:18004664411@sipsorcery.com;user=phone.
NewCall 20:51:48:598: Executing script dial plan for call to 
sip:18004664411@sipsorcery.com;user=phone.
DialPlan 20:51:48:739: SDP on GoogleVoiceCall call had public IP not mangled, 
RTP 
socket 98.224.207.xxx:49152.
DialPlan 20:51:48:739: UAS call progressing with Ringing.
DialPlan 20:51:48:739: Logging into google.com for noname@gmail.com.
DialPlan 20:51:48:770: Google Voice pre-login page loaded successfully.
DialPlan 20:51:48:786: GALX key opwN3c7it6M successfully retrieved.
DialPlan 20:51:49:583: Google Voice home page loaded successfully.
DialPlan 20:51:49:598: Call key Bqi+m0U6OHPrfxx9FoyGGbGIurA= successfully 
retrieved 
for noname@gmail.com, proceeding with callback.
DialPlan 20:51:49:676: Google Voice Call to 18004664411 forwarding to 
425xxxxxxx 
successfully initiated, callback timeout=30s.
DialPlan 20:52:19:676: Google Voice Call timed out waiting for callback.
DialPlan 20:52:19:848: Dial plan execution completed without answering and with 
no 
last failure status.
DialPlan 20:52:19:848: UAS call failed with a response status of 480.

Successful Call:

DialPlan 20:52:50:098: New call from udp:98.224.207.xxx:5060 successfully 
authenticated by digest.
DialPlan 20:52:50:426: Using dialplan Google Voice Simple Dial Plan for Out 
call to 
sip:18004664411@sipsorcery.com;user=phone.
NewCall 20:52:50:489: Executing script dial plan for call to 
sip:18004664411@sipsorcery.com;user=phone.
DialPlan 20:52:50:520: SDP on GoogleVoiceCall call had public IP not mangled, 
RTP 
socket 98.224.207.xxx:49152.
DialPlan 20:52:50:520: UAS call progressing with Ringing.
DialPlan 20:52:50:520: Logging into google.com for noname@gmail.com.
DialPlan 20:52:50:567: Google Voice pre-login page loaded successfully.
DialPlan 20:52:50:567: GALX key 7WZ2z2QgHu0 successfully retrieved.
DialPlan 20:52:51:348: Google Voice home page loaded successfully.
DialPlan 20:52:51:364: Call key Bqi+m0U6OHPrfxx9FoyGGbGIurA= successfully 
retrieved 
for noname@gmail.com, proceeding with callback.
DialPlan 20:52:51:458: Google Voice Call to 18004664411 forwarding to 
425xxxxxxx 
successfully initiated, callback timeout=30s.
DialPlan 20:52:53:973: Google Voice Call callback received.
DialPlan 20:52:53:973: Answering client call with a response status of 200.
DialPlan 20:52:54:208: Google Voice Call was successfully answered in 3.69s.
DialPlan 20:52:54:614: Dial plan execution completed with normal clearing.
Registrar 20:53:03:661: Authentication required for username@sipsorcery.com 
from 
udp:127.0.0.1:5060.
Registrar 20:53:03:895: Binding update request for username@sipsorcery.com from 
udp:98.224.207.xxx:5060, expiry requested 1800s granted 180s.
RegisterSuccess 20:53:04:005: Registration successful for 
username@sipsorcery.com 
from udp:98.224.207.xxx:5060 (proxy=udp:10.248.58.xxx:5060), expiry 180s.
DialPlan 20:53:05:583: Matching dialogue found for BYE to 
sip:174.129.xxx.x:5060 from 
udp:10.248.58.xxx:5060.

Original comment by lovin...@gmail.com on 17 Jan 2010 at 8:59

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I see you're already on IPKall.. the return calls that are coming
from Google Voice are not reliably appearing on any of your SIP lines.

Alternatively, assuming you have a Gizmo5 number, could you please add an "x" 
to the
end of your sipgate number, effectively disabling it? There's really nothing to
change in the script to make Google Voice do a better job at calling you back. 
I'm
starting to wonder if these free services are running out of gas. There are
alternatives for hosting your own version of SIP Sorcery, but it can be a major
undertaking unless you're skilled in managing Linux systems.

Original comment by easter...@gmail.com on 17 Jan 2010 at 9:15

GoogleCodeExporter commented 9 years ago

Original comment by easter...@gmail.com on 17 Jan 2010 at 9:15

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
These console messages sound eerily similar to what I have been seeing...

Have you also noticed Google Voice actually trying to call you back (I don't 
mean 
from in the console, but I mean actually trying to call you on your number at 
the 
same time you are trying to make a call)?

You should check out my situation here, but there probably is not much there 
for you 
either:
http://code.google.com/p/google-voice-sipsorcery-dialplans/issues/detail?id=14

I wonder if it is the free services that are having problems, as Google Voice 
does 
not have any record of literally trying to call me on my SIP number when I am 
making 
calls (my account only shows the number I was trying to call). 

Also, you forgot to blank out your gmail address (unless you have no problems 
posting it), you will find it if you look hard enough or use the find button on 
your 
browser for your email address. :)

Original comment by XANAVi...@gmail.com on 18 Jan 2010 at 3:10

GoogleCodeExporter commented 9 years ago 
I am getting erratic results with all three dialing types (ie 7, 10, and 11 
digit 
dialing).  Sometimes they work and other times they don't.  There seems to be 
no 
rhyme or reason to it.  I do notice that if it works the first time, it almost 
always 
does not work if you try again right after.

Here is the console info for a failed 10 digit call:

DialPlan 20:20:25:333: New call from udp:98.224.207.XXX:5060 successfully 
authenticated by digest.
DialPlan 20:20:25:661: Using dialplan Google Voice Simple Dial Plan for Out 
call to 
sip:248XXXXXXX@sipsorcery.com;user=phone.
NewCall 20:20:25:708: Executing script dial plan for call to 
sip:248XXXXXXX@sipsorcery.com;user=phone.
DialPlan 20:20:25:770: SDP on GoogleVoiceCall call had public IP not mangled, 
RTP 
socket 98.224.207.XXX:49152.
DialPlan 20:20:25:770: UAS call progressing with Ringing.
DialPlan 20:20:25:770: Logging into google.com for noname@gmail.com.
DialPlan 20:20:25:786: Google Voice pre-login page loaded successfully.
DialPlan 20:20:25:786: GALX key 26TcnxC0tJ4 successfully retrieved.
DialPlan 20:20:26:880: Google Voice home page loaded successfully.
DialPlan 20:20:26:926: Call key Bqi+m0U6OHPrfxx9FoyGGbGIurA= successfully 
retrieved 
for noname@gmail.com, proceeding with callback.
DialPlan 20:20:27:036: Google Voice Call to 1248XXXXXXX forwarding to 
425XXXXXXX 
successfully initiated, callback timeout=30s.
DialPlan 20:20:57:036: Google Voice Call timed out waiting for callback.
DialPlan 20:20:57:567: Dial plan execution completed without answering and with 
no 
last failure status.
DialPlan 20:20:57:583: UAS call failed with a response status of 480.

Here is the console info for a failed 11 digit call:

DialPlan 20:25:09:848: New call from udp:98.224.207.XXX:5060 successfully 
authenticated by digest.
DialPlan 20:25:10:208: Using dialplan Google Voice Simple Dial Plan for Out 
call to 
sip:1313XXXXXXX@sipsorcery.com;user=phone.
NewCall 20:25:10:270: Executing script dial plan for call to 
sip:1313XXXXXXX@sipsorcery.com;user=phone.
DialPlan 20:25:10:333: SDP on GoogleVoiceCall call had public IP not mangled, 
RTP 
socket 98.224.207.XXX:49152.
DialPlan 20:25:10:333: UAS call progressing with Ringing.
DialPlan 20:25:10:333: Logging into google.com for noname@gmail.com.
DialPlan 20:25:10:364: Google Voice pre-login page loaded successfully.
DialPlan 20:25:10:380: GALX key ZHuyDduRc4c successfully retrieved.
DialPlan 20:25:11:473: Google Voice home page loaded successfully.
DialPlan 20:25:11:520: Call key Bqi+m0U6OHPrfxx9FoyGGbGIurA= successfully 
retrieved 
for noname@gmail.com, proceeding with callback.
DialPlan 20:25:11:583: Google Voice Call to 1313XXXXXXX forwarding to 
425XXXXXXX 
successfully initiated, callback timeout=30s.
Registrar 20:25:16:348: Authentication required for USERNAME@sipsorcery.com 
from 
udp:127.0.0.1:5060.
Registrar 20:25:16:520: Binding update request for USERNAME@sipsorcery.com from 
udp:98.224.207.XXX:5060, expiry requested 1800s granted 180s.
RegisterSuccess 20:25:16:645: Registration successful for 
USERNAME@sipsorcery.com 
from udp:98.224.207.XXX:5060 (proxy=udp:10.248.58.XXX:5060), expiry 180s.
NATKeepAlive 20:25:16:911: Requesting NAT keep-alive from proxy socket 
udp:10.248.58.XXX:5060 to udp:98.224.207.XXX:5060.
NATKeepAlive 20:25:26:989: Requesting NAT keep-alive from proxy socket 
udp:10.248.58.XXX:5060 to udp:98.224.207.XXX:5060.
DialPlan 20:25:41:583: Google Voice Call timed out waiting for callback.
DialPlan 20:25:41:848: Dial plan execution completed without answering and with 
no 
last failure status.
DialPlan 20:25:41:848: UAS call failed with a response status of 480.

Original comment by lovin...@gmail.com on 18 Jan 2010 at 3:28

GoogleCodeExporter commented 9 years ago 
Thanks Xanavi.  Hopefully I caught all of them now.

Original comment by lovin...@gmail.com on 18 Jan 2010 at 3:31

GoogleCodeExporter commented 9 years ago 
You did.
I am very sure no one got hold of your email address through that message 
though, 
but just making sure for you. :)

Anyhow, when you login to SIPSorcery, and go the SIP Providers tab...
In the second box on the page, what is the expiry time of the registration?

I think a proper working provider registration would show 3600 as the expiry 
time 
(mine has just 600).

You and I have almost identical problems and we use totally different providers 
(maybe even clients as well).

Original comment by XANAVi...@gmail.com on 18 Jan 2010 at 3:40

GoogleCodeExporter commented 9 years ago 
I have 600 but I don't think that is necessary for my current setup because 
IpKall 
connects to sipsorcery.  I am not currently using an SIP provider like sipgate 
for my 
set up.

Original comment by lovin...@gmail.com on 18 Jan 2010 at 4:34

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I checked and even though I have sipgate configured for 3600, sipgate does 
indeed ramp 
it down to 600.

Original comment by easter...@gmail.com on 18 Jan 2010 at 12:49

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
So, both IPKall and SIPGate downgrade the expiry time to 600, when it should be 
3600 
(at least that is what I think is normal, since my client's connection is with 
a 
3600 expiry time, and not the weird 600)...

I would think now, that is a provider problem, since both of our services have 
this 
same thing going on, and at least I am the only one seeing actual calls from 
Google 
Voice, as opposed to SIPSorcery answering and passing that down.

I still can't figure out if lovingj1 is seeing actual calls from Google Voice 
when 
they're trying to make a call, but it seems much more like the case right now, 
their 
SIPSorcery console is basically identical to what mine produces when I get 
those 
"phantom calls".

Are you sure you are having no problems making calls at all, EasternPA, 100% 
outgoing answers? 
I wonder if your console from SIPSorcery is showing up like ours is a few times 
out 
of however-many calls you make.

I don't think there is a way of fixing this anymore, since it now seems like a 
provider problem, but I found weird that only 2 people have reported this in 
who-
knows-how-many are using this for their calls, including those who have the 
hardware 
phones.

Maybe it can be waited out, or if that 600 expiry time could be fixed some 
way...

Original comment by XANAVi...@gmail.com on 18 Jan 2010 at 1:10

GoogleCodeExporter commented 9 years ago 
Well it just got interesting. Repeated attempts at calling out through sipgate 
failed 
with the same error. I logged into my sipgate account, and sipgate shows no 
calls 
arriving from Google Voice. So I called my sipgate number directly from my 
cellphone, 
and received a message about the caller being unavailable. Also, the call did 
not 
show up on my call history page. On my settings page, my SIP phone is shown as 
online, meaning SIP Sorcery has successfully logged in to receive calls.

You're not alone. sipgate appears to be having major issues passing calls 
through to 
SIP clients. Now I wonder if they are shutting down "abusers" who don't fund 
their 
account. There are a couple of people here who pay for their sipgate line. It 
would 
be interesting to see if they are also having issues or if sipgate is giving 
preferential treatment to paying customers.

So no, none of this is your fault.

Original comment by easter...@gmail.com on 18 Jan 2010 at 1:35

GoogleCodeExporter commented 9 years ago 
I was able to at least partially fool SIPSorcery (or however or which way those 
"phantom calls" are coming in), by doing the following:

1. Create a fake dialplan (put something basic like the Hello World script 
you're 
given at SIPSorcery for new accounts).

2. Go to the first tab in SIPSocery (SIP Accounts) and set "In Dialplan" or 
whatever 
it is called to the fake dialplan.

3. Test call to somewhere, it should work 99% of the time as opposed to the +/- 
75%
we were seeing.

It's worked 100% of the time for me. But, it will require the creation of 
another 
SIPGate/IPKall account in order to receive calls like it should be (you know, 
in the 
dialplan, where it should go through SIPSorcery).

Original comment by XANAVi...@gmail.com on 18 Jan 2010 at 1:57

GoogleCodeExporter commented 9 years ago 
Okay, I have had 100% failures since you asked me to double check. I have tried 
calling out via sipgate and via Gizmo5 on one GV number and also via Gizmo5 on 
a 
second GV number. I also tried by configuring Gizmo5 to forward calls via SIP 
to SIP 
Sorcery and also by just letting SIP Sorcery answer the call as a SIP client. 
Neither 
worked.

Here's where it got interesting. When I reactivated my sipgate line in SIP 
Providers, 
the SIP Provider Bindings list showed a timeout of 3600 for a short time. Not 
only 
that, but when I called my sipgate number from my cellphone, SIP Sorcery 
answered and 
passed the call through to my ATA! After the call, the timeout dropped to 600, 
and 
none of the GV calls worked after that one successful inbound call from my 
cellphone.

Original comment by easter...@gmail.com on 18 Jan 2010 at 1:59

GoogleCodeExporter commented 9 years ago 
Check out this thread. It appears that SIP Sorcery is using load balancing on 
its DNS 
names and that the return calls are coming on servers that may be different 
from where 
your client is registered. You must register against an IP to force the ATA to 
be on 
the same server on which the return calls are appearing.

http://www.mysipswitch.com/forum/viewtopic.php?t=2101&start=20

Original comment by easter...@gmail.com on 18 Jan 2010 at 2:11

GoogleCodeExporter commented 9 years ago 
Okay, now I'm seeing that I can't make calls from ExpressTalk.

I set it to login to SIPSorcery's ip address for sip.sipsorcery.com 
(174.129.236.7), 
but it is not letting me make calls.

SIPSorcery properly detects that I'm logged in and is able to login to Google 
Voice 
just fine, but now it is failing 100% at the point where it needs the callback 
(and 
I'm not getting called back from that SIPGate address either).

The last time I was able to make a call was at least a couple hours ago, way 
before 
I had even heard of or tried using SIPSorcery's actual IP Address.
I made the change to try using the IP Address a couple minutes ago, and now it 
starts failing...

Original comment by XANAVi...@gmail.com on 18 Jan 2010 at 8:04

GoogleCodeExporter commented 9 years ago 
This from StuartofOz. No need to create a second sipgate account and line. Just
create an additional VOIP phone on your primary account. Then in SIP Sorcery, 
modify
your sipgate line to be your new "sipgate line 1" and add a second line as 
"sipgate
line 2". You will use a different set of credentials for each line, and you 
will also
enter a different "contact" address. It is no longer your 
SS_name@sipsorcery.com.
Configure each one according to Stuart's text. I now have 100% dialing through
sipgate restored.

"Define two voip phones in sipgate. Then create and register two sip providers 
in
sipsorcery:  one with the the registered contact as sip:account@174.129.236.7 
(the
primary sipsorcery server) and the other as sip:account@174.129.234.254 (the 
other
sipsorcery server)."

Original comment by easter...@gmail.com on 19 Jan 2010 at 2:22

GoogleCodeExporter commented 9 years ago 
Okay, I've configured SIPSorcery with the two providers.

But, does that mean I need to change my SIPSorcery login details in ExpressTalk 
to 
login to one of the IPs and not sip.sipsorcery.com.

I just don't get it. Does it mean I need to configure my SIPSorcery login 
details 
twice (one for each IP)?

It works like you said, :), but I am just curious.

Original comment by XANAVi...@gmail.com on 20 Jan 2010 at 2:32

GoogleCodeExporter commented 9 years ago 
No, that's the beauty of it. The only "doubling up" in the path is in the 
segment 
between SIP Sorcery and sipgate.

You log into SIP Sorcery one time. Google Voice routes calls to just one 
sipgate 
number. You created a second VOIP phone in sipgate and configured SIP Sorcery 
to 
force sipgate to route each incoming call to both of the SIP Sorcery servers. 
Sipgate 
doesn't know which SIP Sorcery server you logged into, so it attempts to route 
the 
call to both SIP Sorcery servers, only one of which was expecting the call. The 
server expecting the call answers it and the other attempt to transfer the call 
is 
terminated. It was pretty sweet was StuartOfOz came up with.

Original comment by easter...@gmail.com on 20 Jan 2010 at 2:59

GoogleCodeExporter commented 9 years ago 
Great! It works like 99% of the time for me (instead of the less than 50% I was 
seeing).
That is a great plan/idea he had! :)

Original comment by XANAVi...@gmail.com on 20 Jan 2010 at 5:08

GoogleCodeExporter commented 9 years ago 
Okay....Now something is defiantely up.
It seems something went wrong now, and that 99 success was just a coincidence 
the 
first time.

I set it up right (Setup 2 phones on SIPGate, 2 SIP Providers in SIPSorcery 
with the 
SIP URI of each server), and ExpressTalk is configured to login to 
sip.sipsorcery.com, and it shows on SIPSorcery as being online, but the calls 
are 
not being passed to it.

Here's SIPSorcery's call log:
Monitor 03:42:19:859: ipaddress=*, user=x, event=*, request=*, 
serveripaddress=*, 
server=*, regex=.*.
Monitor 03:42:48:524: ipaddress=*, user=x, event=*, request=*, 
serveripaddress=*, 
server=*, regex=.*.
DialPlan 03:43:05:031: New call from udp:x.x.x.83:9091 successfully 
authenticated by 
digest.
DialPlan 03:43:05:422: Using dialplan default for Out call to 
sip:x@sipsorcery.com.
NewCall 03:43:05:485: Executing script dial plan for call to 
sip:x@sipsorcery.com.
DialPlan 03:43:05:547: ** Call from "SIPSorcery Communication Link" 
<sip:x@sipsorcery.com>;tag=8320 to x **
DialPlan 03:43:05:563: Calling x via Google Voice
DialPlan 03:43:05:563: SDP on GoogleVoiceCall call had public IP not mangled, 
RTP 
socket x.x.x.83:24612.
DialPlan 03:43:05:563: UAS call progressing with Ringing.
DialPlan 03:43:05:563: Logging into google.com for x@gmail.com.
DialPlan 03:43:05:594: Google Voice pre-login page loaded successfully.
DialPlan 03:43:05:594: GALX key 9_ct5yku160 successfully retrieved.
DialPlan 03:43:06:579: Google Voice home page loaded successfully.
DialPlan 03:43:06:610: Call key zZEuMnmdXoof7UTDRpf/FTwF9uo= successfully 
retrieved 
for x@gmail.com, proceeding with callback.
DialPlan 03:43:06:735: Google Voice Call to x forwarding to xx successfully 
initiated, callback timeout=60s.
NATKeepAlive 03:42:41:062: Requesting NAT keep-alive from proxy socket 
udp:x.x.x.129:5060 to udp:x.x.x.83:9091.
NATKeepAlive 03:42:46:078: Requesting NAT keep-alive from proxy socket 
udp:x.x.x.129:5060 to udp:x.x.x.83:9091.
NATKeepAlive 03:42:56:125: Requesting NAT keep-alive from proxy socket 
udp:x.x.x.129:5060 to udp:x.x.x.83:9091.
NATKeepAlive 03:43:01:140: Requesting NAT keep-alive from proxy socket 
udp:x.x.x.129:5060 to udp:x.x.x.83:9091.
NATKeepAlive 03:43:21:234: Requesting NAT keep-alive from proxy socket 
udp:x.x.x.129:5060 to udp:x.x.x.83:9091.
NATKeepAlive 03:43:26:281: Requesting NAT keep-alive from proxy socket 
udp:x.x.x.129:5060 to udp:x.x.x.83:9091.
NATKeepAlive 03:43:36:421: Requesting NAT keep-alive from proxy socket 
udp:x.x.x.129:5060 to udp:x.x.x.83:9091.
DialPlan 03:44:06:777: Google Voice Call timed out waiting for callback.
DialPlan 03:44:07:059: Dial plan execution completed without answering and with 
no 
last failure status.
DialPlan 03:44:07:059: UAS call failed with a response status of 480.

Original comment by XANAVi...@gmail.com on 21 Jan 2010 at 4:00

GoogleCodeExporter commented 9 years ago 
Ah, nevermind. I was panicking. :o

I managed to narrow down the problem... Somehow, my SIPGate registrations were 
registering against their IP address, and not sipgate.com as I had configured.

I de-registered (by unchecking the box), and registered again and all is well.

Original comment by XANAVi...@gmail.com on 21 Jan 2010 at 4:13

GoogleCodeExporter commented 9 years ago

Original comment by easter...@gmail.com on 28 Apr 2010 at 6:01