Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[bogof]

[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]

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.

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. 

[aesmith]

SIP may work over CGNAT, depending on the carrier, the equipment and the ITSP.  I found it slightly flakey over Smarty, maybe it's the address changes rather than the CGNAT itself.  Regarding failover I wonder if your gear is hanging onto the original NAT even though the route is changed.  That's what I found mine was doing, because the Gigaset keeps polling this keeps the NAT entry alive.  Nowadays my main router just does the routing, NAT isn't done until it reaches the ADSL or the LTE router.

[Alex Atkin UK]

It shouldn't be, I have Flush all states when a gateway goes down enabled as I also use Do not create rules when gateway is down so I have more control over how failover works, rather than just relying on Gateway Groups.

[aesmith]

Speaking of firewalling I am dealing with an issue that has arisen again with a connection to "Gradwell".  Gradwell operate on the principle that your equipment sends its signalling to a defined destination within Gradwell for your outgoing calls.  So far so good.  However for incoming calls Gradwell sources their call setup messages on a wide range of addresses within a whole page worth of prefixes and lists.  So no sort of stateful firewall can cope by default, your firewall needs to be configured to permit unsolicited SIP from any of the addresses on this list ..
https://my.gradwell.com/kA04G0000000DAO?name=what-ip-addresses-may-gradwell-send-voip-traffic-from

To make matters worse the list is subject to change, with no guarantee they will update that web page.  So incoming calls are liable to stop working at any time, with some detective work needed to try and figure out what new addresses are being used.  This is exactly what was reported by this particular user today.  The only other solution would be for the customer to leave their equipment open to unsolicited call attempts from anywhere on the Internet.

[Alex Atkin UK]

I've not even looked into incoming calls yet, POTS based calls seem to get routed fine, I presume this is only if you want pure IP to IP calls?

[Wilt]

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?

When I ported my number in to AA I also tried to set up my phone before the port was complete but it didn't work - was fine once the number had ported though, so it looks like they just don't activate the account until they have the number.

I have been using a Gigaset N300 IP with the service behind NAT just fine, I haven't enabled SIP ALG or anything like that.

[bogof]

When I ported my number in to AA I also tried to set up my phone before the port was complete but it didn't work - was fine once the number had ported though, so it looks like the just don't activate the account until they have the number.

I have been using a Gigaset N300 IP with the service behind NAT just fine, I haven't enabled SIP ALG or anything like that.

Thanks, that's reassuring.  I can see the service appears to have an install date of 22/06/21, I guess it makes sense to only provision the service once the number is transferred in and working.   

-----

Interestingly though the port is scheduled I have had no "sorry you are leaving" etc from EE as a result of the port request.  You would think something would come through their various retention systems.

[bogof]

Well, that was all surprisingly pain free.  At 10.05 I attempted to connect my Android mobile phone using the inbuilt SIP client to my SIP account and it connected first time (over my NAT'd office Wifi, running on Ubiquiti Unifi USG3 with more or less default settings).  A few minutes later I checked and the VDSL connection is no longer up it seems (TBB ping monitor is now failing).  So it appears the cease has rippled through EE's systems. 
Nice one!   

We will see how well it works on my mobile, and I'll probably look to set up something for the house as I did like us having phones within reach on each floor.

[bogof]

I've managed to abuse the Zen-provided Fritzbox 7530 into being a client device on my home network, serving as a DECT SIP base station.  The 3 cheap old DECT handsets from a Siemens Gigaset POTS base station set have connected up just fine to the Fritzbox.  So it seems like I've managed to get a 3 handset DECT SIP setup for nowt!

Seems to work well.  The Fritzbox is behind the router in the house, so it is being NAT'd.  Things go a bit wrong if my mobile has the SIP client enabled and connects to the home wifi network - the phones on the Fritzbox stop receiving incoming calls.  Not sure if it is possible to get them all able to receive incoming SIP calls if connected to the home network. 

Will have to do a bit more reading and playing.

[Alex Atkin UK]

That's weird, I thought the whole point with SIP is you can effectively login on as many clients as you want and they should all receive calls.

What are you using for SIP on the mobile?  Last I tried all the SIP apps were horrible.

[bogof]

That's weird, I thought the whole point with SIP is you can effectively login on as many clients as you want and they should all receive calls.

What are you using for SIP on the mobile?  Last I tried all the SIP apps were horrible.

Yes, but there are problems with several clients behind one NAT gateway, so there are several ways around it it seems.  Just working out if I care enough to make it work...

Android has a built in SIP client which you set up in the Calls app.  Seems to work well.