Re: SIP clients & AEBS hardware
Re: SIP clients & AEBS hardware
- Subject: Re: SIP clients & AEBS hardware
- From: james woodyatt <email@hidden>
- Date: Mon, 31 Jul 2006 16:19:45 -0700
On Jul 31, 2006, at 15:43, Mark Thomas wrote:
"forward flows to a specific static private address if there are
no other
port mappings or local services on the base station to take the flow"
With "Default Host" enabled in AirPort Extreme, it means that ports
not explicitly mapped with the "Port Mapping" feature, and not used
by the AirPort Extreme itself (either transiently or permanently) are
mapped to the private IP address you specify as the "default" host.
The complication is with UDP, which is 1) not connection-oriented,
and 2) used with VoIP for the transport flows. Outbound UDP flows
from the "default host" get their private ports floated to a new
public port. Inbound UDP flows do not. If this were not so, then
outbound UDP flows from the default host could "capture" a public
port used by another private host or by the AirPort base station
itself. With inbound flows, the non-default hosts can capture flows
that would otherwise go to the default host, but that's a normal
function of the "default host" feature.
In any case, the optimal solution to your problem is to put the
AirPort Extreme into "bridge mode" i.e. turn off the NAT, and use
static, globally routed IP addresses. The next best solution is to
figure out how to use STUN with your VoIP setup. I wouldn't expect
SIP to work with the "Default Host" feature. I would expect a
limited measure of success with the "Port Mapping" feature, but it
would be a headache.
--
james woodyatt <email@hidden>
member of technical staff
apple computer, inc.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden