You're not using callprogress=yes or busydetect=yes are you? That could easily cause these problems with Zap ports.
On Tue, 2004-09-07 at 19:25, Kris Boutilier wrote: > > -----Original Message----- > > From: Chris Shaw [mailto:[EMAIL PROTECTED] > > Sent: September 7, 2004 5:14 PM > > To: Asterisk Users Mailing List - Non-Commercial Discussion > > Subject: Re: [Asterisk-Users] Maximum tollerable lag/jitter for IAX2 > > w/ojitterbuffer enabled? > > > > > > > Is 'jitterbuffer=no' not sufficent to clobber that function? > > > > Yes, sorry I didn't see that part... Hmm.... > > > > And IAX2 debug on doesn't give you any hints at all? like who > > hung up first, > > etc... ? > > > > Alas, I haven't caught it in the act yet - there have been 420 IAX2 to Zap > and another 500+ Zap to Zap calls on that server so far today. I've had > reports of about 30 dropped calls. > > What I really need is to find a better way to post-mortem debugging for > large numbers of concurrent IAX2 calls... > > Kris Boutilier > Information Systems Coordinator > Sunshine Coast Regional District > _______________________________________________ > Asterisk-Users mailing list > [EMAIL PROTECTED] > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users -- Eric Wieling * BTEL Consulting * 504-899-1387 x2111 "In a related story, the IRS has recently ruled that the cost of Windows upgrades can NOT be deducted as a gambling loss." _______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
