List - Non-Commercial Discussion
Subject: [asterisk-users] Interesting problem with IP's
Have a trunk 1.4 asterisk, running on centos on the lan at work.
A long story, but we had the entire work network on a public address
range (90.1.0.x), going to a firewall, then out to the net.
At home
snip
Just a guess, but the connection probably went from full to half duplex.
/snip
Full vs. Half duplex networking would NOT cause half duplex phone calls.
-Dave
___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
...@lists.digium.com] On Behalf Of David Gibbons
Sent: Wednesday, December 09, 2009 8:28 AM
To: 'Asterisk Users Mailing List - Non-Commercial Discussion'
Subject: Re: [asterisk-users] Interesting problem with IP's
snip
Just a guess, but the connection probably went from full to half duplex.
/snip
Full vs. Half
-users-boun...@lists.digium.com] On Behalf Of Julian
Lyndon-Smith
Sent: Tuesday, December 08, 2009 8:54 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: [asterisk-users] Interesting problem with IP's
Have a trunk 1.4 asterisk, running on centos on the lan at work.
A long
Don't forget that many routers treat the designated private address space
differently because it assumes the device is being implemented as a border
router. In this configuration they block most traffic unless you
specifically set rules to permit traffic to flow.
-dbc.
Have a trunk 1.4 asterisk, running on centos on the lan at work.
A long story, but we had the entire work network on a public address
range (90.1.0.x), going to a firewall, then out to the net.
At home (192.168.1.x network) I have a router that connects to the
firewall via a vpn tunnel.
All was
