On Fri, 2015-02-20 at 06:03 +, Chuck Mariotti wrote:
You could try TCP for the OpenVPN if the phones will support it. The vast
majority of your traffic will be UDP so you wont get the joy of TCP in TCP
exponential standoffs.
Cheers
Jon
The phones do support TCP (an option on a per
That's definitely the cable modem's NAT getting confused. If you can get the
phones to randomize their source ports on their OpenVPN traffic, that might
resolve. I'm not sure if that's possible on those phones. In stock OpenVPN,
specifying lport 0 in the config will make it choose a random
On 19 February 2015 at 14:51, Chuck Mariotti cmario...@xunity.com wrote:
That's definitely the cable modem's NAT getting confused. If you can get
the phones to randomize their source ports on their OpenVPN traffic, that
might resolve. I'm not sure if that's possible on those phones. In stock
You could try TCP for the OpenVPN if the phones will support it. The vast
majority of your traffic will be UDP so you wont get the joy of TCP in TCP
exponential standoffs.
Cheers
Jon
The phones do support TCP (an option on a per line basis offers UDP/TCP).
Could you clarify what you mean by
: February-19-15 8:04 AM
To: pfSense Support and Discussion Mailing List
Subject: Re: [pfSense] OpenVPN (pfSense 2.1.5-RELEASE) - VoIP Phone Issues
On 19 February 2015 at 14:51, Chuck Mariotti
cmario...@xunity.commailto:cmario...@xunity.com wrote:
That's definitely the cable modem's NAT getting confused
On Wed, 2015-02-18 at 06:38 +, Chuck Mariotti wrote:
That's definitely the cable modem's NAT getting confused. If you can get the
phones to randomize their source ports on their OpenVPN traffic, that might
resolve. I'm not sure if that's possible on those phones. In stock OpenVPN,
I have 4 Yealink T46G phones, 3 on one network (problematic), 1 on a separate
network... all phones are OpenVPNing into pfSense box at datacenter... then
using a phone system through the OpenVPN connection.
The problematic location keeps having issues with phones not receiving calls or
making
On Tue, Feb 17, 2015 at 9:50 PM, Chuck Mariotti cmario...@xunity.com wrote:
I have 4 Yealink T46G phones, 3 on one network (problematic), 1 on a
separate network… all phones are OpenVPNing into pfSense box at datacenter…
then using a phone system through the OpenVPN connection.
The
On Tue, Feb 17, 2015 at 11:13 PM, Chuck Mariotti cmario...@xunity.com wrote:
Think you forgot the logs. That should be enough of a summary to have a good
idea though.
What's the firewall/router/NAT device on the network where the 3 phones
reside? That sounds like what could happen with a NAT
Think you forgot the logs. That should be enough of a summary to have a good
idea though.
What's the firewall/router/NAT device on the network where the 3 phones
reside? That sounds like what could happen with a NAT device that doesn't
handle UDP well. Some consumer-grade routers and some NAT
That's definitely the cable modem's NAT getting confused. If you can get the
phones to randomize their source ports on their OpenVPN traffic, that might
resolve. I'm not sure if that's possible on those phones. In stock OpenVPN,
specifying lport 0 in the config will make it choose a random
11 matches
Mail list logo
