| Author |
Sipgate Incoming - Not coming in!
|
|
|
| Seems sipgate numbers are not accepting calls.
"This number is not accepting calls at present.. Please try later"
| |
| Martin Jay 2006-07-21, 1:11 pm |
| In message <e9qiuq$nok$1@news.freedom2surf.net>, Sean
<seanhardy88NOSPAM@yahoo.co.uk> writes
>Seems sipgate numbers are not accepting calls.
>
>"This number is not accepting calls at present.. Please try later"
I was just about to post a new thread about that, but then I read your
article.
So it's not just me. 
Sipgate have had a few problems recently. I wonder what's going on
there?
--
Martin Jay
Phone/SMS: +44 7740 191877
Fax: +44 870 915 2124
| |
|
|
"Sean" <seanhardy88NOSPAM@yahoo.co.uk> wrote in message
news:e9qiuq$nok$1@news.freedom2surf.net...
> Seems sipgate numbers are not accepting calls.
>
> "This number is not accepting calls at present.. Please try later"
>
>
Mine are OK......
| |
| Ivor Jones 2006-07-21, 1:11 pm |
|
"Sean" <seanhardy88NOSPAM@yahoo.co.uk> wrote in message
news:e9qiuq$nok$1@news.freedom2surf.net
> Seems sipgate numbers are not accepting calls.
>
> "This number is not accepting calls at present.. Please
> try later"
>
From where..? Landline, mobile, another Sipgate number..?
Mine are ok.
Ivor
| |
|
| Ivor Jones wrote:
> "Sean" <seanhardy88NOSPAM@yahoo.co.uk> wrote in message
> news:e9qiuq$nok$1@news.freedom2surf.net
>
> From where..? Landline, mobile, another Sipgate number..?
>
> Mine are ok.
>
> Ivor
>
>
They are working now.
A friend of mine said his were not working, and mine were not... From BT
PSTN and mobiles
| |
| mattpark 2006-07-21, 1:11 pm |
| Yep, same here...
Very temperamental at my end too. Must be doing maintenance at the
moment I guess?
Matt
External Post from http://ukvoiptalk.com
| |
| Ivor Jones 2006-07-21, 1:11 pm |
|
"mattpark" <admin@ukvoiptalk-dot-com.no-spam.invalid> wrote
in message news:1153493398.110495@ntop.griffin.com
> Yep, same here...
>
> Very temperamental at my end too. Must be doing
> maintenance at the moment I guess?
Apparently the PSTN binding came unbound..! It has been reset from what
I'm told.
Ivor
| |
| M.Dexter@blueyonder.co.uk 2006-07-21, 7:11 pm |
| On Fri, 21 Jul 2006 15:39:32 +0100, "Ivor Jones"
<ivor@despammed.invalid> wrote:
>Mine are ok.
Yours have always been ok Ivor .
| |
| Ivor Jones 2006-07-21, 7:11 pm |
| <M.Dexter@blueyonder.co.uk> wrote in message
news:e962c2t5nbpgua2pi0a2vap7j7pjcdokmn@
4ax.com
> On Fri, 21 Jul 2006 15:39:32 +0100, "Ivor Jones"
> <ivor@despammed.invalid> wrote:
>
>
> Yours have always been ok Ivor .
Oh do shut up.
Ivor
| |
| Joe Harrison 2006-07-23, 7:11 am |
| I have a Sipgate/SPA3000 setup that mostly works fine, but in parallel was
experimenting using X-lite with another account with a different PSTN
prefix. For ages the second account was behaving as you describe, outgoing
calls OK but incoming calls not. Depending on which was my calling network I
got variations on the "number not in use" message when trying to call into
X-lite.
So I was convinced the other area code prefix just plain didn't work on
Sipgate and finally contacted tech support - they were very helpful, must
have done quite a bit of diagnostic work then told me the fault was on my
end with the X-lite configuration. Which it was, egg on face. So if you are
running more than one account behind same NAT you have to give X-lite a
non-default port config e.g. 5602.
Joe
| |
| Ivor Jones 2006-07-23, 1:11 pm |
|
"Joe Harrison" <newscontrol@crylo.com> wrote in message
news:N1Iwg.59400$Z61.11545@newsfe4-win.ntli.net
> I have a Sipgate/SPA3000 setup that mostly works fine,
> but in parallel was experimenting using X-lite with
> another account with a different PSTN prefix. For ages
> the second account was behaving as you describe, outgoing
> calls OK but incoming calls not. Depending on which was
> my calling network I got variations on the "number not in
> use" message when trying to call into X-lite.
> So I was convinced the other area code prefix just plain
> didn't work on Sipgate and finally contacted tech support
> - they were very helpful, must have done quite a bit of
> diagnostic work then told me the fault was on my end with
> the X-lite configuration. Which it was, egg on face. So
> if you are running more than one account behind same NAT
> you have to give X-lite a non-default port config e.g.
> 5602.
Yes, I do that with X-Pro (the full version) on my laptop, but other
people were apparently experiencing problems at the same time, so I don't
think it was all you.
Ivor
|
|
|
|