Re: SIP clients & AEBS hardware
Re: SIP clients & AEBS hardware
- Subject: Re: SIP clients & AEBS hardware
- From: Mark Thomas <email@hidden>
- Date: Mon, 31 Jul 2006 23:43:10 +0100
- Organization: Coderus Ltd
Hi,
>> Any thoughts or know issue maybe ?
>
> Short answer: probably a known issue.
>
guess it might (rdar://4660816)
> SIP is not a NAT-friendly protocol. There have been various attempts
> to work around the problem of NAT and SIP interop, but I haven't paid
> close enough attention recently to know if one of them has settled
> out as the preferred approach. Last I heard, STUN was the best
> available solution, but it's an "add-on" that would need to be
> integrated with SIP, and I don't know whether that integration has
> sorted itself out yet.
>
I've been using other router's at my client's work and they use NAT and
not STUN setup and all OK.
> The fact you are trying to use the "DMZ" feature of AirPort Extreme
> suggests you have a SIP implementation that doesn't try to use STUN.
> I'll bet it recommends you use the "DMZ" feature if you are behind a
> NAT, and somebody has probably told you that AirPort Extreme has such
> a feature.
>
No I've seen the "DMZ" feature there for a while, but Yes the SIP client
support's STUN but I'm presently unaware if there is STUN server's somewhere
will have to investigate that. I wasn't told but trying to work out why not
working. Also somsething else to find out as not aware of STUN.
> AirPort Extreme does not have a "DMZ" feature.
>
Yes it does call it "Default Host", but the tooltip say's "also sometimes
referred as virtual DMZ" which where I might have got mislead.
> AirPort Extreme has a feature it calls the "Default Host" mapping, in
> which it will 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. It is not a "DMZ" in any sense of the term
> as it's commonly used in networking. When flows are translated by
> AirPort Extreme for the "Default Host" mapping, TCP and UDP source
> ports on outbound flows are still floated, unlike as would happen
> with a "DMZ" feature. Your SIP user agent probably doesn't like
> this, but it's necessary to keep the default hosts mappings for
> outbound flows separated from the AirPort's own transient local port
> binds.
>
I have no port mappings, which is why I confused nothing is being
forwarded on. Even in normal DHCP mode it doesn't work right.
Also what do you mean by
"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"
Do you mean setup in the port forward dialog, or internally when the
tcp/ip traffic is flowing through ?
But even with this "Default Host", there's nothing talking the traffic it
should be directing it to my machine.
Thanks for help
Mark.
_______________________________________________
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