VOIP connection DNS issues

[wkuk]

So there are number of threads on here about getting VOIP working and i've read through some of them but has anyone done a summary of the settings that work so the rest of us don't need to dig through 100s of pages of back and forth conversation trying to find the crumbs of information we need?

I have contacted VF support and got the SIP details from them.  And I am reasonably confident I have all the other settings i need but I think I am running into a weird DNS problem and I'm not sure how to solve it.  Might need to talk to VF directly.

All of the stuff i have read so far says that the registrar should be resvoip.vodafone.co.uk and the proxy should be something ending in bbvoice.vodafone.co.uk.

The problem is i cannot resolve these addresses from my connection even if I specifically connect to VF's DNS servers directly.

This is the output from nslookup on my machine:

C:\Users\Person>nslookup
Default Server: dnsserver.localdomain
Address: 192.168.1.1

> server 90.255.255.255
Default Server: bbdns.vodafone.co.uk
Address: 90.255.255.255

> resvoip.vodafone.co.uk
Server: bbdns.vodafone.co.uk
Address: 90.255.255.255

*** bbdns.vodafone.co.uk can't find resvoip.vodafone.co.uk: Non-existent domain

> xbn.Z4.bbvoice.vodafone.co.uk
Server: bbdns.vodafone.co.uk
Address: 90.255.255.255

Name: xbn.Z4.bbvoice.vodafone.co.uk

>

This seems to be the same for any device on my network, weather i use VF's dns or not.  As a result none of the VOIP stuff is working for me.  Am i missing something?  Is this likely to be something local, or do i need to contact VF and get something enabled?

[mt_subnet]

Yes I am aware of those early posts mostly via mouldybread which makes it all the more surprising that my HT801 has run for over a year using 90.255.255.90. 

[Ripshod]

Do you have 90.255.255.255 set as the second dns, as that's the one you're actually using now for digital voice? 90.255.255.90 will not respond to the proxied requests (or at least it shouldn't). Without rummaging around in the logs or using wireshark you won't know. 

Then again, with the current state of the vf network, who knows.

[Cynric]

@Ripshod Any chance that VF have baked-in a direction to an entry-point in the same way that Microsoft have been doing for certain functions such as updating?

[Ripshod]

@Cynric It's possible, but I haven't seen any bulletins from vf. As far as I'm aware access is still the way it always has been. It's possible they've sneaked in and locked it down, but it's also possible that (due to breakdowns/overprovisioning) they could be running some wierd routing that we don't need to know about.