Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Re: A&A VOIP - which router ports need to be open?
9 views
Skip to first unread message
tony sayer
Dec 13, 2019, 5:06:19 PM12/13/19
to
In article <qt0l1r$dde$1...@dont-email.me>, Peter <occassionally-
conf...@nospam.co.uk> scribeth thus
>We are getting a system (from Andrews & Arnold) and I wonder what will
>be needed.
>
>The router is a Draytek 2955. We have the usual config, doing NAT.
>
>If I just open ports, those ports will pass everything sent to those
>ports onto the internal network.
>
>If I port forward, that passes the traffic to specific internal IPs,
>but that means configuring the phones with fixed IPs (which I am sure
>is doable).
>
>Getting info from the super bright A&A people is not easy :)
We use VoIPfone never had to alter anything in the Draytek router we
have and thats not one with built in VoIP ports either!!..
--
Tony Sayer
Man is least himself when he talks in his own person.
Give him a keyboard, and he will reveal himself.
conf...@nospam.co.uk> scribeth thus
>We are getting a system (from Andrews & Arnold) and I wonder what will
>be needed.
>
>The router is a Draytek 2955. We have the usual config, doing NAT.
>
>If I just open ports, those ports will pass everything sent to those
>ports onto the internal network.
>
>If I port forward, that passes the traffic to specific internal IPs,
>but that means configuring the phones with fixed IPs (which I am sure
>is doable).
>
>Getting info from the super bright A&A people is not easy :)
We use VoIPfone never had to alter anything in the Draytek router we
have and thats not one with built in VoIP ports either!!..
--
Tony Sayer
Man is least himself when he talks in his own person.
Give him a keyboard, and he will reveal himself.
Woody
Dec 14, 2019, 3:44:25 AM12/14/19
to
On Sat 14/12/2019 02:16, Anthony R. Gold wrote:
> routers in four locations. But if you have a multi-WAN setup and for some
> reason you prefer to keep the VOIP traffic on one particular WAN, then in
> the router's Load Balancing setup you use to steer the VOIP to the preferred
> WAN, make sure you choose Force NAT and not Force Routing in the
> Load-Balance/Route Policy else you will get very unreliable VOIP
> connections.
>
> To nail a LAN appliance to a fixed IP address my favorite way is to use the
> Vigor router's LAN configuration where you can bind the LAN device's MAC to
> a particular LAN IP address. So the device stays with DHCP and whenever it
> appears on the LAN the router will always issue it the same reserved
> address.
>
Per the last comment, the fixed IP address can be outside the DHCP range
and will still connect solidly every time. That is how I have my network
set up so from the allocated IP address I can always spot a 'visitor.'
--
Woody
harrogate three at ntlworld dot com
> On Fri, 13 Dec 2019 22:01:02 +0000, tony sayer <to...@bancom.co.uk> wrote:
>
>> In article <qt0l1r$dde$1...@dont-email.me>, Peter <occassionally-
>> conf...@nospam.co.uk> scribeth thus
>>> We are getting a system (from Andrews & Arnold) and I wonder what will
>>> be needed.
>>>
>>> The router is a Draytek 2955. We have the usual config, doing NAT.
>>>
>>> If I just open ports, those ports will pass everything sent to those
>>> ports onto the internal network.
>>>
>>> If I port forward, that passes the traffic to specific internal IPs,
>>> but that means configuring the phones with fixed IPs (which I am sure
>>> is doable).
>>>
>>> Getting info from the super bright A&A people is not easy :)
>>
>> We use VoIPfone never had to alter anything in the Draytek router we
>> have and thats not one with built in VoIP ports either!!..
>
> I also did nothing with Siemens Gigaset VOIP adapters and Draytek Vigor
>
>> In article <qt0l1r$dde$1...@dont-email.me>, Peter <occassionally-
>> conf...@nospam.co.uk> scribeth thus
>>> We are getting a system (from Andrews & Arnold) and I wonder what will
>>> be needed.
>>>
>>> The router is a Draytek 2955. We have the usual config, doing NAT.
>>>
>>> If I just open ports, those ports will pass everything sent to those
>>> ports onto the internal network.
>>>
>>> If I port forward, that passes the traffic to specific internal IPs,
>>> but that means configuring the phones with fixed IPs (which I am sure
>>> is doable).
>>>
>>> Getting info from the super bright A&A people is not easy :)
>>
>> We use VoIPfone never had to alter anything in the Draytek router we
>> have and thats not one with built in VoIP ports either!!..
>
> routers in four locations. But if you have a multi-WAN setup and for some
> reason you prefer to keep the VOIP traffic on one particular WAN, then in
> the router's Load Balancing setup you use to steer the VOIP to the preferred
> WAN, make sure you choose Force NAT and not Force Routing in the
> Load-Balance/Route Policy else you will get very unreliable VOIP
> connections.
>
> To nail a LAN appliance to a fixed IP address my favorite way is to use the
> Vigor router's LAN configuration where you can bind the LAN device's MAC to
> a particular LAN IP address. So the device stays with DHCP and whenever it
> appears on the LAN the router will always issue it the same reserved
> address.
>
Per the last comment, the fixed IP address can be outside the DHCP range
and will still connect solidly every time. That is how I have my network
set up so from the allocated IP address I can always spot a 'visitor.'
--
Woody
harrogate three at ntlworld dot com
Andy Burns
Dec 14, 2019, 8:34:21 AM12/14/19
to
Peter wrote:
> Are these phones normally set up with a fixed IP? How does the VOIP
> server (at A&A) know which phone to reoute the call to? If the phone
> gets its IP over DHCP,
The internal (usually RFC1918) address is not routeable from the
internet, the phone connects outward to the SIP server, and often to a
STUN/TURN server too.
> and it doesn't need port forwading etc in the
> router, then it must keep the NAT hole open with keep-alive packets,
yep
> Are these phones normally set up with a fixed IP? How does the VOIP
> server (at A&A) know which phone to reoute the call to? If the phone
> gets its IP over DHCP,
The internal (usually RFC1918) address is not routeable from the
internet, the phone connects outward to the SIP server, and often to a
STUN/TURN server too.
> and it doesn't need port forwading etc in the
> router, then it must keep the NAT hole open with keep-alive packets,
yep
0 new messages