What you say...John Novack (jnov...@stromberg-carlson.org): > > Carlos Alvarez wrote: > > > > > >On Tue, Mar 5, 2013 at 2:32 PM, Hose <hose+aster...@bluemaggottowel.com > ><mailto:hose+aster...@bluemaggottowel.com>> wrote: > > > > We have an asterisk frontend terminating all our SIP phones to, and an > > asterisk backend with a wildcard PRI card in it connecting to the PTSN. > > The frontend handles 99% of dialplan logic and just hands off anything > > outgoing to the backend via IAX2, which dials out on one of the open > > channels. > > > > > >IAX is buggy. We've never seen a reliable system using it. We've given up > >on it. > I have seen this assertion from time to time, but never any real details > > There is a world wide network of users who communicate using IAX, and many > with PSTN service from providers using IAX. with no complaints > Can someone please provide meaningful details on what "buggy" really means? > Rather than such a sweeping condemnation. If it is so buggy, why isn't it > either fixed or discontinued? > > It certainly is much less prone to hacking and abuse than SIP. Probably not > due to the protocol design as much as it isn't as universal > > John Novack
I'll keep the SIP option open - never really considered it actually, just figured the go-to protocol for connecting two * boxes together would be IAX2. It'd be good for troubleshooting purposes at least to narrow down issues and compare results. If anyone else has suggestions, I'm all ears. hose -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
