Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > uk.telecom > #38572 > unrolled thread
| Started by | Postman Pat <at@the-post-office-not.com> |
|---|---|
| First post | 2026-01-07 12:19 +0000 |
| Last post | 2026-10-30 17:45 +0000 |
| Articles | 2 on this page of 22 — 9 participants |
Back to article view | Back to uk.telecom
Looking for a decent VOIP provider for a small business, 4 phones and 1 remote one Postman Pat <at@the-post-office-not.com> - 2026-01-07 12:19 +0000
Re: Looking for a decent VOIP provider for a small business, 4 phones and 1 remote one Woody <harrogate3@ntlworld.com> - 2026-01-07 14:37 +0000
Re: Looking for a decent VOIP provider for a small business, 4 phones and 1 remote one "J. P. Gilliver" <G6JPG@255soft.uk> - 2026-01-07 16:32 +0000
Re: Looking for a decent VOIP provider for a small business, 4 phones and 1 remote one Postman Pat <at@the-post-office-not.com> - 2026-01-13 15:07 +0000
Re: Looking for a decent VOIP provider for a small business, 4 phones and 1 remote one Woody <harrogate3@ntlworld.com> - 2026-01-13 15:54 +0000
Re: Looking for a decent VOIP provider for a small business, 4 phones and 1 remote one Postman Pat <at@the-post-office-not.com> - 2026-01-13 16:45 +0000
Re: Looking for a decent VOIP provider for a small business, 4 phones and 1 remote one David Wade <g4ugm@dave.invalid> - 2026-01-13 18:15 +0000
Re: Looking for a decent VOIP provider for a small business, 4 phones and 1 remote one Postman Pat <at@the-post-office-not.com> - 2026-01-22 16:28 +0000
Re: Looking for a decent VOIP provider for a small business, 4 phones and 1 remote one David Wade <dave@is.invalid> - 2026-01-07 18:42 +0100
Re: Looking for a decent VOIP provider for a small business, 4 phones and 1 remote one jkn <jkn+nin@nicorp.co.uk> - 2026-01-08 12:32 +0000
Re: Looking for a decent VOIP provider for a small business, 4 phones and 1 remote one Theo <theom+news@chiark.greenend.org.uk> - 2026-01-08 13:16 +0000
Re: Looking for a decent VOIP provider for a small business, 4 phones and 1 remote one Richmond <dnomhcir@gmx.com> - 2026-01-08 13:36 +0000
Re: Looking for a decent VOIP provider for a small business, 4 phones and 1 remote one Postman Pat <at@the-post-office-not.com> - 2026-10-29 12:56 +0000
Re: Looking for a decent VOIP provider for a small business, 4 phones and 1 remote one Richmond <dnomhcir@gmx.com> - 2026-10-29 13:35 +0000
Re: Looking for a decent VOIP provider for a small business, 4 phones and 1 remote one Postman Pat <at@the-post-office-not.com> - 2026-10-29 14:48 +0000
Re: Looking for a decent VOIP provider for a small business, 4 phones and 1 remote one Postman Pat <at@the-post-office-not.com> - 2026-10-29 15:31 +0000
Re: Looking for a decent VOIP provider for a small business, 4 phones and 1 remote one Chris Green <cl@isbd.net> - 2026-10-29 13:46 +0000
Re: Looking for a decent VOIP provider for a small business, 4 phones and 1 remote one Theo <theom+news@chiark.greenend.org.uk> - 2026-10-30 12:08 +0000
Re: Looking for a decent VOIP provider for a small business, 4 phones and 1 remote one Postman Pat <at@the-post-office-not.com> - 2026-10-30 16:45 +0000
Re: Looking for a decent VOIP provider for a small business, 4 phones and 1 remote one Chris Green <cl@isbd.net> - 2026-10-30 17:19 +0000
Re: Looking for a decent VOIP provider for a small business, 4 phones and 1 remote one Richmond <dnomhcir@gmx.com> - 2026-10-30 17:38 +0000
Re: Looking for a decent VOIP provider for a small business, 4 phones and 1 remote one Theo <theom+news@chiark.greenend.org.uk> - 2026-10-30 17:45 +0000
Page 2 of 2 — ← Prev page 1 [2]
| From | Richmond <dnomhcir@gmx.com> |
|---|---|
| Date | 2026-10-30 17:38 +0000 |
| Message-ID | <82a4nvcclr.fsf@example.com> |
| In reply to | #39984 |
Postman Pat <at@the-post-office-not.com> writes: > Theo <theom+news@chiark.greenend.org.uk> wrote: > >>Chris Green <cl@isbd.net> wrote: >>> Postman Pat <at@the-post-office-not.com> wrote: >>> > Almost a year later I am having to revisit this issue, and I am >>> > looking for recommendations. >>> > >>> > The main A&A VOIP system is working most of the time. Sometimes call >>> > transfers fail but not much. >>> > >>> > I now find, yet again, that the 5th "office" phone which is at my >>> > house no longer rings on incoming calls. A&A are unhelpful, saying in >>> > their usual arrogant way that it won't work through NAT. Well I know >>> > that which is why I have port 5060 open and forwarded to the phone's >>> > internal LAN IP. And this works. It stopped working at one point and >>> > then started, and now I've found it stopped working again. >> >>I'm surprised this works, since the outgoing SIP (or RTP?) packets will have >>your LAN address embedded in them, which the A&A server doesn't know what to >>do with. > > Outgoing calls have always worked. The phone is configured with an A&A > server URL etc. > >>The SIP ALG should inspect the packets passing through the router and >>rewrite them with the correct public IP. > > I've been reading up on this. > > It seems that with ALG you do *not* enable port forwarding, and the > router works out the phone's private IP by inspecting its *outgoing* > (presumably keep-alive) packets. So if it gets a 5060 packet, it knows > where to send it. > > But then I don't get the opportunity to enable the forwarding only > from A&A IP ranges, which is obviously crucial otherwise all of china > will be in there hammering port 5060 ;) > > So currently I have both port forwarding (with the above firewall > rule) and SIP ALG and the phone rings OK. > > Voipfone have a much cleaner system where their phones keep alive > every 60s so not port forwarding or any other router config is needed. > >>I've used A&A on a variety of broadband connections with a variety of >>provider routers (and double NAT through two routers), and at most it needed >>the SIP ALG turning on in the router settings. > > Digging into this, it looks like A&A may have changed their server > config: > > From Claude: If the router hasn’t changed, then the change was on the > other side, so the provider is the likelier explanation. A typical > candidate is how their servers handle NAT. Many SIP providers quietly > correct for private addresses in the Contact and SDP headers, by > replying to the address and port the packet actually came from. If > they tightened or changed that behaviour, phones behind NAT without an > ALG would stop working, and enabling the ALG would fix them, exactly > as you saw. > > A&A would never admit that though ;) > > I *am* concerned about security. AFAICT the inbound IP firewall rule > prevents VOIP phone fraud, but if ALG allows incoming packets to > bypass NAT, that is bad because they could be malformed. > >>> Wouldn't the best/simplest answer be to get IPV6 working? Then there is >>> simply no issue with NAT. >> >>Yes, I think A&A assume you don't need NAT because they offer you IPv6. As >>you're an A&A broadband customer you by definition have IPv6 on your >>connection. It would seem to make sense to do the thing they offer support >>for. > > I don't want to touch IPV6. I have other stuff set up which doesn't > support it, and life is too short :) > >>(or is the problem your home broadband is a different provider who doesn't >>have IPv6? As above even IPv4 double-NAT has never been a problem for me) > > Yes my home fibre is Voipfone and that phone is on A&A. > > Voipfone can take over the office number and I am sure their system is > much better (their support is certainly excellent) but the number > would apparently go dead for 7 days, which is not acceptable. To avoid > this, I would need to transfer the whole office to Voipfone but then I > have to reconfig a lot of stuff - which I can do if needed. Maybe A&A does not like the phone's IP address not being on their network? I have managed to make calls using Linphone on Android. And for it to ring there is an option in that app to send keep alive messages. The phone has its own ipv6 address but I disabled ipv6 in the settings of Linphone to make it work. There is an option on the A&A control pages to disable use of the phone number from other IP addresses as a security measure. It is off by default so it should work from your home IP. You could try getting it to work with Linphone and also maybe depending on your router plug in a traditional phone to the router and see if that works. You could switch on SIP ALG just to see if it works.
[toc] | [prev] | [next] | [standalone]
| From | Theo <theom+news@chiark.greenend.org.uk> |
|---|---|
| Date | 2026-10-30 17:45 +0000 |
| Message-ID | <dUy*PxtUA@news.chiark.greenend.org.uk> |
| In reply to | #39984 |
Postman Pat <at@the-post-office-not.com> wrote: > > Theo <theom+news@chiark.greenend.org.uk> wrote: > > >The SIP ALG should inspect the packets passing through the router and > >rewrite them with the correct public IP. > > I've been reading up on this. > > It seems that with ALG you do *not* enable port forwarding, and the > router works out the phone's private IP by inspecting its *outgoing* > (presumably keep-alive) packets. So if it gets a 5060 packet, it knows > where to send it. > > But then I don't get the opportunity to enable the forwarding only > from A&A IP ranges, which is obviously crucial otherwise all of china > will be in there hammering port 5060 ;) I think the idea is that the SIP ALG sees a local device connecting to A&A port 5060, and rewrites it with the public IP but also remembers the LAN IP. When media connections come back from A&A to your router, the ALG knows to forward them on to the phone's LAN IP. If somebody else sends you SIP or RTP traffic, it doesn't come from the A&A IP and the ALG doesn't forward it, so the firewall dumps it. That means you don't need to add extra firewall rules. As A&A say: "RTP is the actual media (e.g., the audio). On our platform the RTP will come from the same call server IP address as the SIP control messages. " https://support.aa.net.uk/VoIP_Firewall so just the SIP ALG should be enough to make sure only packets from A&A's server make it back to your SIP device. > So currently I have both port forwarding (with the above firewall > rule) and SIP ALG and the phone rings OK. I think your additional firewall rules may be making the problem worse, particularly if they're taking priority over the ALG. Although that page talks about complications around having multiple SIP devices - the ALG can't tell which device the incoming connection is for. That could be a problem. > Voipfone have a much cleaner system where their phones keep alive > every 60s so not port forwarding or any other router config is needed. I think A&A do that too? SIP clients stay connected, they don't drop off through inaction. I haven't done a packet capture, but with Gigaset endpoints things 'just work'. > >I've used A&A on a variety of broadband connections with a variety of > >provider routers (and double NAT through two routers), and at most it needed > >the SIP ALG turning on in the router settings. > > Digging into this, it looks like A&A may have changed their server > config: > > From Claude: If the router hasn?t changed, then the change was on the > other side, so the provider is the likelier explanation. A typical > candidate is how their servers handle NAT. Many SIP providers quietly > correct for private addresses in the Contact and SDP headers, by > replying to the address and port the packet actually came from. If > they tightened or changed that behaviour, phones behind NAT without an > ALG would stop working, and enabling the ALG would fix them, exactly > as you saw. > > A&A would never admit that though ;) Did something change? If anything, I'd expect A&A not to 'quietly correct' - given their NAT stance they would rather the connection doesn't work so the user sorts it out properly, rather than silently enabling bad behaviour. > I *am* concerned about security. AFAICT the inbound IP firewall rule > prevents VOIP phone fraud, but if ALG allows incoming packets to > bypass NAT, that is bad because they could be malformed. I'm not seeing how it's worse than any other kind of NAT? A NAT+firewall only let packets in if somebody inside initiated them. If they didn't, it blocks them. When you connect to www.example.com TCP port 443, the response is let through because you sent out the first packet. If somebody on the internet tries to send a packet to my web browser, it won't succeed unless there is an entry in the NAT table recording that a packet was previously sent to them. If you're adding firewall rules to this mix, they need to be in addition to rather than instead of the NAT rules. eg you add additional filtering so that www.example.com can only send packets back to me if the connection is to their port 443 (ie the rule is IF existing_connection AND dest_IP==104.20.23.154 AND dest_port==443). It doesn't allow www.example.com access any time to your LAN, which you'd get if skipping the 'existing_connection' check. The SIP ALG is just a hack on top of NAT so that it rewrites the addresses inside the SIP/RTP packets as well as rewriting the headers. It also allows outgoing SIP and incoming RTP traffic from the same host to share the same NAT table entry (so a incoming RTP connection is allowed after an outgoing SIP). (AIUI anyway) If you're using a STUN server, it's another way for clients to find out their public IPs which handles the first part (ie clients can embed the correct public IP in their packets), but it does not touch the firewall's NAT rules so incoming media wouldn't be accepted without the ALG rules. > >> Wouldn't the best/simplest answer be to get IPV6 working? Then there is > >> simply no issue with NAT. > > > >Yes, I think A&A assume you don't need NAT because they offer you IPv6. As > >you're an A&A broadband customer you by definition have IPv6 on your > >connection. It would seem to make sense to do the thing they offer support > >for. > > I don't want to touch IPV6. I have other stuff set up which doesn't > support it, and life is too short :) Other stuff can carry on using IPv4 oblivious to the presence of IPv6. It's pretty simple to enable and, if you let it do its thing, 'just works'. If you want to nail it down then that's more work. > >(or is the problem your home broadband is a different provider who doesn't > >have IPv6? As above even IPv4 double-NAT has never been a problem for me) > > Yes my home fibre is Voipfone and that phone is on A&A. > > Voipfone can take over the office number and I am sure their system is > much better (their support is certainly excellent) but the number > would apparently go dead for 7 days, which is not acceptable. To avoid > this, I would need to transfer the whole office to Voipfone but then I > have to reconfig a lot of stuff - which I can do if needed. I suspect A&A will actually work for you fine and perhaps you have overcomplicated it which is the source of problem? Theo
[toc] | [prev] | [standalone]
Page 2 of 2 — ← Prev page 1 [2]
Back to top | Article view | uk.telecom
csiph-web