[Asterisk-Users] Asterisk 1.2.4 IAX2 New Jitterbuffer Tuning

[Adam Robins]

Thanks,

We already have a cron reboot of all of our Asterisk servers every
night.  We've been doing this for over a year due to memory leak issues.

After 2 weeks of messing around with every conceivable IAX2 and
jitterbuffer configuration, I switched to SIP yesterday.  Complaints
went from 10-20 per day to ZERO.  Literally overnight.

 

-----Original Message-----
From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Simone
Cittadini
Sent: Thursday, February 23, 2006 4:37 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] Asterisk 1.2.4 IAX2 New Jitterbuffer
Tuning

Adam Robins ha scritto:

> Thanks, but we already have the TOS bits set to 0xB8, which matches 
> the QoS settings in our switches and routers.
>  
> This is definitely something that changed in the 1.07 to 1.24 upgrade.

> We have a pair of identical 1.07 servers connected via the same 
> network pipe that do not exhibit these issues.
>  
> I might try recompiling with the old jitterbuffer to see if it makes a

> difference.
>  
>
>  
> ----------------------------------------------------------------------
> --

I've not 1.24 in producton yet, still 1.21, anyway I've noticed that
restarting asterisk every night dramatically reduces complaints about
choppy calls (I think is something about a memory leak and not
jitterbuffer, anyway is something easy to do so it's worth trying)
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --

Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

The contents of this email message and any attachments are confidential and are intended solely for addressee. The information may also be legally privileged. This transmission is sent in trust, for the sole purpose of delivery to the intended recipient. If you have received this transmission in error, any use, reproduction or dissemination of this transmission is strictly prohibited. If you are not the intended recipient, please immediately notify the sender by reply email and delete this message and its attachments, if any.