Re: Same provider - IAX sounds bad, SIP sounds great

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

On Wed, Feb 29, 2012 at 8:34 AM, Kevin P. Fleming <kpfleming@xxxxxxxxxx> wrote:
> Certainly there are plenty of examples of SIP endpoints working poorly
> behind NAT devices, and replacing that endpoint with an IAX2 endpoint curing
> the symptoms. Invariably, this is caused by the fact that the NAT device was
> attempting to 'help' the SIP endpoint, and failed miserably. In every case I
> can remember, turning off any SIP-specific functionality in that NAT device
> (which is not always possible) allowed the SIP endpoint to work as expected.

We have *never* found a single SIP "helper" to actually help anything.
 They always break everything.  The only SIP-related setting I can
think of that works is "Enable consistent NAT" found in Sonicwall
routers (but turn off all other SIP "helpers").  The WRT54G and Apple
Airport come to mind as stable and reliable home/small business
routers that seem to just work.  The WRTs seem to go bad every few
years and need an occasional reboot, the Airports work forever in our
experience without being touched.  All stock out of the box.

> options already present in Asterisk. Deploying SIP *clients* behind NATs,
> talking to a SIP server that is on a public IP, is generally trivial and
> takes no special effort at all.

This is today's reality.  That's why I mentioned the possibility that
he's using ancient devices and routers, or that Yugo.

Carlos Alvarez

-- Bandwidth and Colocation Provided by --
New to Asterisk? Join us for a live introductory webinar every Thurs:

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:

[Gnu Gatekeeper]     [IETF Sipping]     [Info Cyrus]     [ALSA User]     [Fedora Linux Users]     [DCCP]     [Gimp]     [100% Free Online Dating]     [Yosemite News]     [Arts & Crafts]     [Yosemite Photos]     [Deep Creek Hot Springs]     [Yosemite Campsites]     [ISDN Cause Codes]

Add to Google Powered by Linux