Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > uk.telecom > #38572 > unrolled thread

Looking for a decent VOIP provider for a small business, 4 phones and 1 remote one

Started byPostman Pat <at@the-post-office-not.com>
First post2026-01-07 12:19 +0000
Last post2026-11-05 16:43 +0000
Articles 13 on this page of 33 — 10 participants

Back to article view | Back to uk.telecom


Contents

  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
              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-11-03 13:48 +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-11-03 15:34 +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-11-04 14:48 +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-11-04 16:50 +0000
                      Re: Looking for a decent VOIP provider for a small business, 4 phones and 1 remote one Richmond <dnomhcir@gmx.com> - 2026-11-04 17:06 +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-11-04 17:34 +0000
                          Re: Looking for a decent VOIP provider for a small business, 4 phones and 1 remote one Richmond <dnomhcir@gmx.com> - 2026-11-06 12:53 +0000
          Re: Looking for a decent VOIP provider for a small business, 4 phones and 1 remote one Pancho <Pancho.Jones@protonmail.com> - 2026-11-05 13:45 +0000
      Re: Looking for a decent VOIP provider for a small business, 4 phones and 1 remote one Richmond <dnomhcir@gmx.com> - 2026-10-31 15:44 +0000
      Re: Looking for a decent VOIP provider for a small business, 4 phones and 1 remote one Pancho <Pancho.Jones@protonmail.com> - 2026-11-05 13:38 +0000
        Re: Looking for a decent VOIP provider for a small business, 4 phones and 1 remote one Woody <harrogate3@ntlworld.com> - 2026-11-05 16:43 +0000

Page 2 of 2 — ← Prev page 1 [2]


#39987

FromRichmond <dnomhcir@gmx.com>
Date2026-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]


#39988

FromTheo <theom+news@chiark.greenend.org.uk>
Date2026-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] | [next] | [standalone]


#40043

FromPostman Pat <at@the-post-office-not.com>
Date2026-11-03 13:48 +0000
Message-ID<11cconk$3pu8v$1@dont-email.me>
In reply to#39988
Thank you :)

I enabled SIP ALG, so that is in addition to 5060 forwarding to the
phone's internal LAN IP (which is also fixed in the phone config) and
the phone rings OK now.

I still fail to see how SIP ALG *alone* can forward 5060 on incoming
calls while allowing in only A&A IPs. This is a Draytek router without
any remote or internal ("plug and play crap") config.

If I get any more hassle I will move the whole lot to Voipfone.
Simpler and non-arrogant... I am with them at another location and
have had zero downtime in 3 years (fibre + Grandstream VOIP).




 Theo <theom+news@chiark.greenend.org.uk> wrote:

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


#40044

FromTheo <theom+news@chiark.greenend.org.uk>
Date2026-11-03 15:34 +0000
Message-ID<4Vx*a-NUA@news.chiark.greenend.org.uk>
In reply to#40043
Postman Pat <at@the-post-office-not.com> wrote:
> Thank you :)
> 
> I enabled SIP ALG, so that is in addition to 5060 forwarding to the
> phone's internal LAN IP (which is also fixed in the phone config) and
> the phone rings OK now.
> 
> I still fail to see how SIP ALG *alone* can forward 5060 on incoming
> calls while allowing in only A&A IPs. This is a Draytek router without
> any remote or internal ("plug and play crap") config.

Roughly speaking, although it may differ from vendor to vendor (and may do
other stuff in addition):

1. Phone on LAN makes outgoing connection to SIP server port 5060, saying it
is available on RTP port range aaaa-bbbb.

2.  NAT rewrites the IP on the packet headers from phone's LAN IP to
public IP, creates an entry in the NAT table to remember the state of this
connection for its duration.  (this is what NAT does for every connection)

3.  SIP ALG rewrites the IP address inside the SIP connection to be the
public IP, not the LAN IP

4.  SIP ALG creates a temporary firewall rule to forward incoming RTP
traffic from the SIP server's source IP to the phone's LAN IP, based on the
ports described in the SIP connection

5.  Incoming audio: SIP server opens an RTP connection to the router in the
appropriate port range, using the same source IP as the initial SIP
connection.

6.  Using the temporary firewall rule, router forwards RTP traffic to the
phone's LAN IP

7. Phone receives and sends audio

8. <phone call happens>

9. Phone deregisters by closing SIP connection (perhaps it was turned off)

10. Server closes RTP connection

10. NAT drops NAT table entries for connections

11. SIP ALG deletes temporary firewall rule

Any point from 4 onwards if an attacker tries to connect, their source
IP will not match the source IP in the temporary firewall rule and
their connection will be blocked.  Before point 4 they would be blocked by
default.

A key issue here is the temporary firewall rule in step 4 only works if this
SIP server is talking to a single SIP endpoint on the LAN.  If you have
multiple SIP clients on the LAN then the firewall sees an incoming
connection and has no means to identify which SIP client it is for,
resulting in one way audio and/or no rings.  That problem is solved by IPv6,
but it's also solved by setting the RTP ports in each client to be
different.  That way the firewall knows that RTP to ports aaaa-bbbb goes to
client 1 and cccc-dddd goes to client 2, ie you end up with two temporary
firewall rules.

(a separate one-way calling issue is clients on mobiles going to sleep and
not being ready to receive the connection when a call is incoming, but
that's not relevant here)

> If I get any more hassle I will move the whole lot to Voipfone.
> Simpler and non-arrogant... I am with them at another location and
> have had zero downtime in 3 years (fibre + Grandstream VOIP).

I've had zero downtime with A&A VOIP in ~10 years...  aside from the
internet connection which they don't control.

TBH, given how much of a hack the above is and the weird stuff the router
vendor could be doing, which is impossible to packet-capture if it's also
your DSL modem in the same ISP-locked-down box, I'm not surprised they would
much rather you use IPv6 and have a limited time to debug IPv4 problems.

I think a lot of it would also be solved if you're running the SIP client on
the router, ie with a public IPv4, like most ISP boxes are running their own
VOIP.  Then you aren't putting it behind NAT and it all works sensibly.  So
a router with maybe a DECT base and an analogue socket avoids a lot of NAT
issues, ie VOIP is never going over the LAN.

That said, I've used A&A with Gigaset boxes behind numerous ISPs and it's
'just worked'; the most I've had to do is turn on the SIP ALG setting in the
ISP router.

Theo

[toc] | [prev] | [next] | [standalone]


#40045

FromPostman Pat <at@the-post-office-not.com>
Date2026-11-04 14:48 +0000
Message-ID<11cfgj4$oors$1@dont-email.me>
In reply to#40044
Thank you again. SIP ALG is a horrible hack.

The bit I wondered about was

>4.  SIP ALG creates a temporary firewall rule to forward incoming RTP
>traffic from the SIP server's source IP to the phone's LAN IP, based on the
>ports described in the SIP connection

which will work only if the VOIP server always uses the same IP. A&A
gave me several IP ranges which I have set up in the NAT port
forwarding.

This, no SIP ALG config, worked for probably 2-3 years, and stopped
only recently. So I have to wonder - what's changed??

As an aside, I had *incoming* VOIP working with a Nokia 808 (year
2014). Nokia were heavily into the corporate sphere and got this stuff
working. The phone obviously had to keep-alive (I recall configuring a
STUN server or some such). The weak link was the home wifi... Nowadays
the phone companies sell "wifi calling" which does the same job.


 Theo <theom+news@chiark.greenend.org.uk> wrote:

>Postman Pat <at@the-post-office-not.com> wrote:
>> Thank you :)
>> 
>> I enabled SIP ALG, so that is in addition to 5060 forwarding to the
>> phone's internal LAN IP (which is also fixed in the phone config) and
>> the phone rings OK now.
>> 
>> I still fail to see how SIP ALG *alone* can forward 5060 on incoming
>> calls while allowing in only A&A IPs. This is a Draytek router without
>> any remote or internal ("plug and play crap") config.
>
>Roughly speaking, although it may differ from vendor to vendor (and may do
>other stuff in addition):
>
>1. Phone on LAN makes outgoing connection to SIP server port 5060, saying it
>is available on RTP port range aaaa-bbbb.
>
>2.  NAT rewrites the IP on the packet headers from phone's LAN IP to
>public IP, creates an entry in the NAT table to remember the state of this
>connection for its duration.  (this is what NAT does for every connection)
>
>3.  SIP ALG rewrites the IP address inside the SIP connection to be the
>public IP, not the LAN IP
>
>4.  SIP ALG creates a temporary firewall rule to forward incoming RTP
>traffic from the SIP server's source IP to the phone's LAN IP, based on the
>ports described in the SIP connection
>
>5.  Incoming audio: SIP server opens an RTP connection to the router in the
>appropriate port range, using the same source IP as the initial SIP
>connection.
>
>6.  Using the temporary firewall rule, router forwards RTP traffic to the
>phone's LAN IP
>
>7. Phone receives and sends audio
>
>8. <phone call happens>
>
>9. Phone deregisters by closing SIP connection (perhaps it was turned off)
>
>10. Server closes RTP connection
>
>10. NAT drops NAT table entries for connections
>
>11. SIP ALG deletes temporary firewall rule
>
>Any point from 4 onwards if an attacker tries to connect, their source
>IP will not match the source IP in the temporary firewall rule and
>their connection will be blocked.  Before point 4 they would be blocked by
>default.
>
>A key issue here is the temporary firewall rule in step 4 only works if this
>SIP server is talking to a single SIP endpoint on the LAN.  If you have
>multiple SIP clients on the LAN then the firewall sees an incoming
>connection and has no means to identify which SIP client it is for,
>resulting in one way audio and/or no rings.  That problem is solved by IPv6,
>but it's also solved by setting the RTP ports in each client to be
>different.  That way the firewall knows that RTP to ports aaaa-bbbb goes to
>client 1 and cccc-dddd goes to client 2, ie you end up with two temporary
>firewall rules.
>
>(a separate one-way calling issue is clients on mobiles going to sleep and
>not being ready to receive the connection when a call is incoming, but
>that's not relevant here)
>
>> If I get any more hassle I will move the whole lot to Voipfone.
>> Simpler and non-arrogant... I am with them at another location and
>> have had zero downtime in 3 years (fibre + Grandstream VOIP).
>
>I've had zero downtime with A&A VOIP in ~10 years...  aside from the
>internet connection which they don't control.
>
>TBH, given how much of a hack the above is and the weird stuff the router
>vendor could be doing, which is impossible to packet-capture if it's also
>your DSL modem in the same ISP-locked-down box, I'm not surprised they would
>much rather you use IPv6 and have a limited time to debug IPv4 problems.
>
>I think a lot of it would also be solved if you're running the SIP client on
>the router, ie with a public IPv4, like most ISP boxes are running their own
>VOIP.  Then you aren't putting it behind NAT and it all works sensibly.  So
>a router with maybe a DECT base and an analogue socket avoids a lot of NAT
>issues, ie VOIP is never going over the LAN.
>
>That said, I've used A&A with Gigaset boxes behind numerous ISPs and it's
>'just worked'; the most I've had to do is turn on the SIP ALG setting in the
>ISP router.
>
>Theo

[toc] | [prev] | [next] | [standalone]


#40046

FromTheo <theom+news@chiark.greenend.org.uk>
Date2026-11-04 16:50 +0000
Message-ID<6Vx*qITUA@news.chiark.greenend.org.uk>
In reply to#40045
Postman Pat <at@the-post-office-not.com> wrote:
> Thank you again. SIP ALG is a horrible hack.
> 
> The bit I wondered about was
> 
> >4.  SIP ALG creates a temporary firewall rule to forward incoming RTP
> >traffic from the SIP server's source IP to the phone's LAN IP, based on the
> >ports described in the SIP connection
> 
> which will work only if the VOIP server always uses the same IP. A&A
> gave me several IP ranges which I have set up in the NAT port
> forwarding.

Yes.  A&A say they do that:

"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

Their server currently advertises multiple IPs:
$ host voiceless.aa.net.uk
voiceless.aa.net.uk has address 81.187.30.116
voiceless.aa.net.uk has address 81.187.30.118
voiceless.aa.net.uk has IPv6 address 2001:8b0:0:30::5060:1
voiceless.aa.net.uk has IPv6 address 2001:8b0:0:30::5060:3

but they're saying that when you pick one to connect to, the audio will come
back from the same one.

That also means that two phones behind the same NAT may work if one
registers on .116 and the other on .118, as the SIP ALG can create distinct
firewall rules for them, but if the round-robin DNS happens that they both
land on the same IP then one may not work.

You can see why there are so many variables they just don't want to get
involved with debugging :-(

> This, no SIP ALG config, worked for probably 2-3 years, and stopped
> only recently. So I have to wonder - what's changed??

Not sure.  They do say that the IP range for firewalling purposes is broader
than the IPs they publish in the DNS, which suggests they are free to change
advertised IPs without needing changes at the customer end.

> As an aside, I had *incoming* VOIP working with a Nokia 808 (year
> 2014). Nokia were heavily into the corporate sphere and got this stuff
> working. The phone obviously had to keep-alive (I recall configuring a
> STUN server or some such). The weak link was the home wifi... Nowadays
> the phone companies sell "wifi calling" which does the same job.

Likewise I've found Gigaset fairly bulletproof.  They actually don't have
too many VOIP settings, which makes them easier to configure than the old
PAP2T I used to use.

Theo

[toc] | [prev] | [next] | [standalone]


#40047

FromRichmond <dnomhcir@gmx.com>
Date2026-11-04 17:06 +0000
Message-ID<82wlqsh6g3.fsf@example.com>
In reply to#40046
Theo <theom+news@chiark.greenend.org.uk> writes:

>
> That also means that two phones behind the same NAT may work if one
> registers on .116 and the other on .118, as the SIP ALG can create
> distinct firewall rules for them, but if the round-robin DNS happens
> that they both land on the same IP then one may not work.
>

I don't know if it would help but I have two phones connected to the
router, and in the settings on the router under SIP service provider, I
have two different Outbound Proxy Ports, 5061 and 5062. SIP ALG is
enabled. But the two phones use different VOIP providers, one uses AA
the other uses Voipfone. It all seems to work.

[toc] | [prev] | [next] | [standalone]


#40048

FromTheo <theom+news@chiark.greenend.org.uk>
Date2026-11-04 17:34 +0000
Message-ID<5Vx*KSTUA@news.chiark.greenend.org.uk>
In reply to#40047
Richmond <dnomhcir@gmx.com> wrote:
> Theo <theom+news@chiark.greenend.org.uk> writes:
> 
> >
> > That also means that two phones behind the same NAT may work if one
> > registers on .116 and the other on .118, as the SIP ALG can create
> > distinct firewall rules for them, but if the round-robin DNS happens
> > that they both land on the same IP then one may not work.
> >
> 
> I don't know if it would help but I have two phones connected to the
> router, and in the settings on the router under SIP service provider, I
> have two different Outbound Proxy Ports, 5061 and 5062. SIP ALG is
> enabled. But the two phones use different VOIP providers, one uses AA
> the other uses Voipfone. It all seems to work.

The problem is if both phones are talking to the same service provider IP. 
When the service provider IP wants to make a connection towards you, your
router can't tell which phone to forward it to.

If you have different service provider IPs (which you will using different
companies), the router can use the source IP to work out which phone
previously contacted that IP and so forward it correctly.

ie if phone 1 last talked to the A&A server, then an incoming connection
from the A&A server should be forwarded to phone 1.  If phone 2 talked to
the Voipfone server, incoming connections from Voipfone should go to phone
2.  But if phone 2 was also talking to the same A&A server, the router
doesn't know whether to send the connection to phone 1 or phone 2.

The wrinkle above is that the 'same server' may not actually be the same IP
due to DNS load-balancing.  If phone 1 is talking to .116 and phone 2 to
.118 then the router can tell them apart and everything works.  But if phone
2 looked up voiceless.aa.net.uk and got .116 which phone 1 was already
talking to, then the router can't tell them apart.  Maybe by default it
always sends the incoming connection to the first device it saw (phone 1),
in which case phone 2 won't get incoming audio.

There are lots of variables and if you can't packet-capture the WAN port of
the router it's hard to work out what's happening.

Theo

[toc] | [prev] | [next] | [standalone]


#40058

FromRichmond <dnomhcir@gmx.com>
Date2026-11-06 12:53 +0000
Message-ID<82v76ace8v.fsf@example.com>
In reply to#40048
Theo <theom+news@chiark.greenend.org.uk> writes:

> Richmond <dnomhcir@gmx.com> wrote:
>> Theo <theom+news@chiark.greenend.org.uk> writes:
>> 
>> >
>> > That also means that two phones behind the same NAT may work if one
>> > registers on .116 and the other on .118, as the SIP ALG can create
>> > distinct firewall rules for them, but if the round-robin DNS
>> > happens that they both land on the same IP then one may not work.
>> >
>> 
>> I don't know if it would help but I have two phones connected to the
>> router, and in the settings on the router under SIP service provider,
>> I have two different Outbound Proxy Ports, 5061 and 5062. SIP ALG is
>> enabled. But the two phones use different VOIP providers, one uses AA
>> the other uses Voipfone. It all seems to work.
>
> The problem is if both phones are talking to the same service provider
> IP.  When the service provider IP wants to make a connection towards
> you, your router can't tell which phone to forward it to.
>
> If you have different service provider IPs (which you will using
> different companies), the router can use the source IP to work out
> which phone previously contacted that IP and so forward it correctly.
>
> ie if phone 1 last talked to the A&A server, then an incoming
> connection from the A&A server should be forwarded to phone 1.  If
> phone 2 talked to the Voipfone server, incoming connections from
> Voipfone should go to phone 2.  But if phone 2 was also talking to the
> same A&A server, the router doesn't know whether to send the
> connection to phone 1 or phone 2.
>
> The wrinkle above is that the 'same server' may not actually be the
> same IP due to DNS load-balancing.  If phone 1 is talking to .116 and
> phone 2 to .118 then the router can tell them apart and everything
> works.  But if phone 2 looked up voiceless.aa.net.uk and got .116
> which phone 1 was already talking to, then the router can't tell them
> apart.  Maybe by default it always sends the incoming connection to
> the first device it saw (phone 1), in which case phone 2 won't get
> incoming audio.
>
> There are lots of variables and if you can't packet-capture the WAN
> port of the router it's hard to work out what's happening.
>
> Theo

I've installed Linphone on an Amazon tablet and using this, I was able
to phone my home phone number from my home phone number and leave a
message. To get Linphone working though I had to disable IPv6. So I
think this verifies that SIP ALG is kicking in with IPv4, but IPv6 is
blocked by the firewall because I haven't set up any rules. It might be
a good way to test things though.

[toc] | [prev] | [next] | [standalone]


#40053

FromPancho <Pancho.Jones@protonmail.com>
Date2026-11-05 13:45 +0000
Message-ID<11ci19g$1ikqp$1@dont-email.me>
In reply to#39983
On 30/10/2026 12:08, Theo wrote:

> 
> 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.
>

Yeahbut, my old hardware, Gigaset N300, A580, etc doesn't do IPv6.
Did people here buy new hardware for VoIP IPv6? I'm at my son's house 
now, he has CGNAT, so I was forced to go IPv6 for some things, but A&A 
VoIP seems to work fine over CGNAT IPv4. (Caveat still early days)

[toc] | [prev] | [next] | [standalone]


#40011

FromRichmond <dnomhcir@gmx.com>
Date2026-10-31 15:44 +0000
Message-ID<82ecd598o2.fsf@example.com>
In reply to#39933
Postman Pat <at@the-post-office-not.com> writes:

> Almost a year later I am having to revisit this issue, and I am
> looking for recommendations.

Maybe you could use a VPN to bypass all your local hazards directly into
the office network? I don't know how you would do that exactly, maybe
set up an old computer to VPN and plug the VOIP phone into the ethernet
port.

[toc] | [prev] | [next] | [standalone]


#40052

FromPancho <Pancho.Jones@protonmail.com>
Date2026-11-05 13:38 +0000
Message-ID<11ci0s5$1ikka$1@dont-email.me>
In reply to#39933
On 29/10/2026 12:56, Postman Pat wrote:

>> I am all ears for any recommendations :)

I, and many others here, used Sipgate for many years. The only thing 
they ever did wrong to me was stop offering the service I was using.

If you are willing to pay, I would assume they still offer a good service

[toc] | [prev] | [next] | [standalone]


#40055

FromWoody <harrogate3@ntlworld.com>
Date2026-11-05 16:43 +0000
Message-ID<11cibmt$1pa3u$1@dont-email.me>
In reply to#40052
On Thu 05/11/2026 13:38, Pancho wrote:
> On 29/10/2026 12:56, Postman Pat wrote:
> 
>>> I am all ears for any recommendations :)
> 
> I, and many others here, used Sipgate for many years. The only thing 
> they ever did wrong to me was stop offering the service I was using.
> 
> If you are willing to pay, I would assume they still offer a good service


I had several accounts with them, one was for comms with family 
(daughter) who only had a mobile. I still have the line I used at my end 
so that calls were free and it still works and is still free. Sadly all 
of the other lines have long since died.

Has to be said that Sipgate were (and for me still are) very quick and 
helpful if I had/have any queries. What is more I used the lines with 
SPA2102 before they were Linksys, PAP2T when Linksys (and thence Cisco) 
bought them which worked and still work very well. The nice thing about 
Sipgate is that they use ports in the 40000 range which keeps them away 
from 5060 and up.

[toc] | [prev] | [standalone]


Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | uk.telecom


csiph-web