Sipgate not working with Plusnet

[I'm Old Gregg]

Since moving from BT Broadband to Plusnet Fibre my Sipgate voip phones have
stopped working.

My router is a BiPac 8800NL, it has been working ok for the last month, the
only changes to it's setup
were account name and password for plusnet.

Any help would be welcomed, I'm not too clever with the technical stuff

G



--

[Bob L]

Voip works on standard Plusnet ADSL.


Double check your stun setting, also you can change your 5060 port to
something else eg 15000, I do that when away from home as certain
hotels block 5060 but not other ports.

Callers do not need to make any changes.

Unplug all your phones , download Zoiper and try that on the PC, and
or remove all phones bar one and re-enter the Sipgate details and see
if that connects.

[I'm Old Gregg]

"Bob L" <b...@thisaddressisnowhere.com> wrote in message
news:ur738adklom1gk0mq...@4ax.com...

Thanks for reminding me to double check all the settings, I noticed that the
DNS settings had changed with the change to Plusnet. I've put the new DNS
into both my phones and they are now working.

Thanks for nudging me in the right direction.

G

--

[Graham.]

On Fri, 5 Dec 2014 13:42:55 -0000, "I'm Old Gregg"

Check that you havn't specified the DNS servers specific to your old
ISP in the config of your IP phone or ATA.

Alternatively try 217.10.79.23 as the SIP proxy instead of
sipgate.co.uk

as Bob says, you can download a softphone and see if that works.

I think that if you download X-Lite from the Sipgate site while you
are logged in to your account, it installs ready configured.

Can we have more info about the phone you are using and are inbound
and outbound calls affected?




--

Graham.

%Profound_observation%

[I'm Old Gregg]

"Graham." <m...@privicy.net> wrote in message
news:lr748aha6k58i86id...@4ax.com...

Thanks Graham

It's all working now, I hadn't realized that the DNS server had to be
changed.

I thought that I would only need to change my login details when I changed
ISP
but I was wrong.

Thanks to both.

G

[Woody]

"I'm Old Gregg" <fan...@btnet.invalid> wrote in message
news:m5um1o$242$1...@dont-email.me...

Simple solution, try an external DNS server. I cannot
remember their source but
Primary 208.67.222.222
Sec 208.67.220.220
Since moving to these from the VM in-house I have never had
a moments trouble.


--
Woody

harrogate three at ntlworld dot com

[Graham J]

Anthony R. Gold wrote:

[snip]

>> It's all working now, I hadn't realized that the DNS server had to be
>> changed.
>>
>> I thought that I would only need to change my login details when I changed
>> ISP
>> but I was wrong.
>>
>> Thanks to both.
>>
>> G
>

> I am also surprised you needed to do that. Sounds like BT Broadband may be
> blocking their local resolvers from access from off their network. If you
> use a public resolver such as Google's 8.8.8.8 that should work anywhere,
> and your SIP kit does not depend on having the fastest resolution possible.

I think most domestic ISPs restrict lookup access to their DNS servers
to their own users.

The convention is to configure your router to hand out its own address
as the DNS server, and set up all the client devices to pick up all the
parameter (IP, gateway, DNS) from the router. If you want a client to
have a specific IP address then use the "bind IP to MAC" facility in the
router - not all routers have this, of course.

I see no good reason why a VoIP device should not follow that convention.

However, I have noticed that BT has many DNS servers, not all of which
are available at any one time. Your router will learn about 2 or 3 of
these when it first establishes the PPP session; but later one of this
subset may become unavailable. I have seen no evidence that routers on
BT connections renegotiate their connections when this happens; so
sometimes DNS requests time out and users report that the "internet is
slow". Rebooting the router cures the problem.

So it is normally a good idea to configure the router with a public DNS
resolver, and continue to leave the VoIP device to get its perameters
from the router.

By contrast most other ISPs list only one or two DNS servers (so the
load balancing and failover is done a different way).

--
Graham J

[fred]

In article <m5upa9$cud$1...@dont-email.me>, Woody <harro...@ntlworld.com>
writes

>
>Simple solution, try an external DNS server. I cannot
>remember their source but
>Primary 208.67.222.222
>Sec 208.67.220.220
>Since moving to these from the VM in-house I have never had
>a moments trouble.
>

That's opendns:

http://www.opendns.com/

Was just about to accuse them of being slow but on running a traceroute
I found that the delay was the in the response from my router!
--
fred
it's a ba-na-na . . . .