Broadband Related > Voice over IP (VoIP)
Porting EE VDSL number to A&A VOIP service
bogof:
Bit of background; had ZEN FTTP installed a couple of months ago (documented here: https://forum.kitz.co.uk/index.php/topic,25446.0.html ). Coming from EE VDSL, which I left in place while making the the FTTP install was sound.
The service is working phenomenally well. I had considered keeping the FTTC as backup, but really it's £25 a month I could do with keeping in my pocket, and the FTTC has so many shared points of failure with FTTP that I'm not sure it is a very good fallback option. So fallback will be 3, 4G based (see here: https://forum.kitz.co.uk/index.php/topic,26059.0.html)
I have a few months left on my 18 month EE contract which I was planning on just letting run; however it turns out they work out their cancellation by taking off any discounts you have, and also any charges they will save to Openreach. This makes the cancellation for 4 remaining months only £20. So I'm porting the number to A&A. This should cause a cease on the EE VDSL service. The savings in line rental will pay for my preloaded 4G SIM card.
Once I have the number on VOIP, I planned to add the VOIP service to mine and my wife's mobile phone. Not sure yet if I'll get an adapter so that I can use the VOIP number on the existing DECT handsets in the house. On the one hand, it's nice to have a phone in the house always wired up, on the other hand, extra cost. I guess I could equally get a hard-wired SIP phone / DECT base station. The Zen contract came with a Fritzbox router too which does support some voice capabilities, and I wonder if perhaps it might even be possible to use that just to interface the old DECT phones to SIP without using it as a router (I use Ubiquiti gear for most of the networking in the house.
Timeline of the port (will update):
14/06/2021 - Went on A&A VOIP page and arranged to have a VOIP account, requesting a port in of my number.
15/06/2021 - Email from a person at A&A confirming the account details for the number being transferred in (I had confirmed during application I thought, perhaps they are just thorough).
16/06/2021 - Email from same person at A&A confirming port in date / time as 22/06/21 10am
22/06/2021 - 10.05am - VOIP incoming calls and voicemail appear to be working fine from my landline number to Android device on office wifi. VDSL ceased service around same time.
I did try using my account details on my mobile phone for SIP setup and they didn't work yet. I don't know if this is because they don't work until the inbound number is attached, or whether there is some other networking issue. I will dig into this a bit when I have a moment, as I would like to ideally know the SIP is up and running before the number ports so we don't have a loss of service on the number. Any thoughts on this?
aesmith:
Keeping an eye on this. By the way, for testing we used to use a free SIP softphone called X-Lite, now Bria Solo. That was handy for checking account settings and credentials.
Personally I don't like analogue adapters, they seem to be the worst of both analogue or digital worlds for example you may not get CLI properly displayed. At home we use a Gigaset N300A which worked with our existing DECT handsets, and supports analogue line as well as SIP services.
Having said that we now get hardly any landline calls, and make most outbound call via mobile making them effectively free. I generally give out the landline number to people I don't want to have calling the mobile.
Regarding the AA SIP service, when we went SIP there were a couple of points of concern. Firstly they say they don't support NAT, and secondly they specified that the media could be sourced on almost any originating IP address (in contrast to say Gamma where there is a dedicated media address). This latter point might or might be an issue depending on how you manage your firewall, and whether your SIP equipment cooperates in a firewall friendly way.
bogof:
--- Quote from: aesmith on June 16, 2021, 12:53:13 PM ---Keeping an eye on this. By the way, for testing we used to use a free SIP softphone called X-Lite, now Bria Solo. That was handy for checking account settings and credentials.
Personally I don't like analogue adapters, they seem to be the worst of both analogue or digital worlds for example you may not get CLI properly displayed. At home we use a Gigaset N300A which worked with our existing DECT handsets, and supports analogue line as well as SIP services.
Having said that we now get hardly any landline calls, and make most outbound call via mobile making them effectively free. I generally give out the landline number to people I don't want to have calling the mobile.
Regarding the AA SIP service, when we went SIP there were a couple of points of concern. Firstly they say they don't support NAT, and secondly they specified that the media could be sourced on almost any originating IP address (in contrast to say Gamma where there is a dedicated media address). This latter point might or might be an issue depending on how you manage your firewall, and whether your SIP equipment cooperates in a firewall friendly way.
--- End quote ---
Thanks for the reply and the pointer to the softphone.
Similarly, we hardly ever get calls on the landline, mostly they are sales. I'm tempted, in a way, to leave the SIP number just going to a voicemail permanently, with the voicemail being emailed to myself and the wife, and then we just call back whoever called. Sometimes the wife has friends who insist on calling landline as they have limited mobile minutes and some free minutes package on the landline, though, so I guess it would be useful to work out how to get it working.
On the NAT point - is that a service provider related issue? I thought SIP and NAT was all about firewall setup at my network, not something related to A&A's service? Quite a lot of internet connections these days are behind the likes of CGNAT so this would seem perhaps to be a pretty big limitation.
I don't understand as yet about media address matters, I will have to do some reading up on this. Thanks for alerting me to the possible issues though.
aesmith:
Regarding NAT the issue is that a lot of SIP headers contain the original IP address of the device inside your network, particularly the SDP headers that tell the other end where to send their media, that's the "c" header giving IP address and port that your device is listening on. There are some other headers in the SIP itself but these are less often an issue (but we did see one provider looking at the Contact header".
Basic NAT as we all know it will re-write the source IP address and port, leaving any IP addresses mentioned in the payload untouched.
Some services are happy with this, and use their own techniques to work out what's going on. Some require you to enable SIP Inspection or SIP ALG (terminology varies with the equipment). And in some cases these conflict with certain call behaviour.
In terms of A&A they did not say it wouldn't work, but they advise against it.
The issue with media source addresses is that in the worse case you would need to have a pretty huge hole in your firewall to allow all their potential source addresses in. However depending on the behaviour of the service (which they don't specify) and of your kit this may not be necessary. My Gigaset for example does some things that specifically keep firewall ports open just for the conversations in use.
Alex Atkin UK:
Interesting, as I had noticed VoIP will not failover on my Gigaset to 4G when my DSL goes down. I assume its probably something to do with this? (as my 4G is double-NAT)
I do have the router with a static IP and set as the DMZ with SIP ALG enabled on the Huawei B535-232 but not sure it actually does anything on a DMZ configuration. Not even sure Voxi issue a public IP.
Ah seems I had the wrong MAC address set for the router, that won't help as it was being issued a random IP from the pool.
[UPDATE]
Can confirm, Voxi is giving out a private IP, apparently Vodafone as a whole have always done this and have no option to get a publc IP. :'(
Navigation
[0] Message Index
[#] Next page
Go to full version