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
RE: [Asterisk-Users] Asterisk 1.2.4 IAX2 New Jitterbuffer Tuning
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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 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. ___ --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
Re: [Asterisk-Users] Asterisk 1.2.4 IAX2 New Jitterbuffer Tuning
On Feb 23, 2006, at 4:58 AM, Adam Robins wrote: 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. ??? What do you think this is windows 95??? I had a problem like that I would be looking at getting rid of asterisk. I don't ;~) I wonder what your leak is ? 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. I wonder if this is an ILBC frame size issue of some sort? Seems odd. ___ --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
RE: [Asterisk-Users] Asterisk 1.2.4 IAX2 New Jitterbuffer Tuning
It happened with g729a as well -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin Joseph Sent: Thursday, February 23, 2006 1:15 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] Asterisk 1.2.4 IAX2 New Jitterbuffer Tuning On Feb 23, 2006, at 4:58 AM, Adam Robins wrote: 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. ??? What do you think this is windows 95??? I had a problem like that I would be looking at getting rid of asterisk. I don't ;~) I wonder what your leak is ? 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. I wonder if this is an ILBC frame size issue of some sort? Seems odd. ___ --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. ___ --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
RE: [Asterisk-Users] Asterisk 1.2.4 IAX2 New Jitterbuffer Tuning
I am not running trunked IAX. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Willis Sent: Monday, February 20, 2006 8:02 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] Asterisk 1.2.4 IAX2 New Jitterbuffer Tuning Adam Robins wrote: 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. If you are running trunked IAX, try turning off the jitterbuffer entirely. Mark ___ --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. ___ --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
RE: [Asterisk-Users] Asterisk 1.2.4 IAX2 New Jitterbuffer Tuning
Title: RE: [Asterisk-Users] Asterisk 1.2.4 IAX2 New Jitterbuffer Tuning This is not going over the Internet. It is going over an MPLS IP-VPN. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael J. LiberatoreSent: Monday, February 20, 2006 7:55 PMTo: Asterisk Users Mailing List - Non-Commercial DiscussionSubject: RE: [Asterisk-Users] Asterisk 1.2.4 IAX2 New Jitterbuffer Tuning so you think this problem is asterisk and not a internet problem? My customers also complain alot about IAX2 connection to teliax which seemed to work better in older * versions. I have tried everything with no success, i switched to sip and its alot better but not perfect... From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adam RobinsSent: Monday, February 20, 2006 6:51 PMTo: Asterisk Users Mailing List - Non-Commercial Discussion; Asterisk Users Mailing List - Non-Commercial DiscussionSubject: RE: [Asterisk-Users] Asterisk 1.2.4 IAX2 New Jitterbuffer Tuning 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. From: [EMAIL PROTECTED] on behalf of Jesus E ZepedaSent: Mon 2/20/2006 5:02 PMTo: 'Asterisk Users Mailing List - Non-Commercial Discussion'Subject: RE: [Asterisk-Users] Asterisk 1.2.4 IAX2 New Jitterbuffer Tuning In my case I don't have a T1 or even a fractional T1, but cable and havenoticed that choppy calls can be reduced by adding tos settings. Like:Tos=lowdelay|throughput|reliabilityRegards,Jesus-Original Message-From: Adam Robins [mailto:[EMAIL PROTECTED]]Sent: Monday, February 20, 2006 14:43To: Asterisk Users Mailing List - Non-Commercial DiscussionSubject: RE: [Asterisk-Users] Asterisk 1.2.4 IAX2 New JitterbufferTuningI have now set the "resyncthreshold" to -1, to turn it off. I have alsoset the "maxjitterbuffer" to 2000.I still received 10 complaints of choppy calls today on Asterisk 1.2.4versus only 1 complaint on Asterisk 1.07.-Original Message-From: [EMAIL PROTECTED][mailto:[EMAIL PROTECTED]] On Behalf Of yusufSent: Monday, February 20, 2006 10:27 AMTo: Asterisk Users Mailing List - Non-Commercial DiscussionSubject: Re: [Asterisk-Users] Asterisk 1.2.4 IAX2 New JitterbufferTuningAdam Robins wrote:Hi Adam After many days of playing with the new jitterbuffer and trunkingoptions for IAX2, I have finally received almost acceptable quality. Iam receiving 5-8 complaints a day of calls "breaking up" from both thecustomer and agent sides. What I have discovered is that in most ofthese cases, the new jitterbuffer performed a resync during the call.Currently, I have the resyncthreshold, and all other jb parameters attheir default levels The traffic is running over a fairly high latencyWAN connection between Canada and Atlanta (IAX2, ILBC). Idle ping timesrun about 85ms.I am interested to know why you are using ilbc, n why not g729 ot g723or speex. What is the size of the WAN connection. How many calls areyou running over this link. I just need to see how others are fairingwith IAX2 over WAN links, as I am the final stages of testing on my sidethanks,yusuf___--Bandwidth and Colocation provided by Easynews.com --Asterisk-Users mailing listTo UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-usersThe contents of this email message and any attachments are confidentialand are intended solely for addressee. The information may also belegally privileged. This transmission is sent in trust, for the solepurpose of delivery to the intended recipient. If you have received thistransmission in error, any use, reproduction or dissemination of thistransmission is strictly prohibited. If you are not the intendedrecipient, please immediately notify the sender by reply email anddelete this message and its attachments, if any.___--Bandwidth and Colocation provided by Easynews.com --Asterisk-Users mailing listTo UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users___--Bandwidth and Colocation provided by Easynews.com --Asterisk-Users mailing listTo 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,
Re: [Asterisk-Users] Asterisk 1.2.4 IAX2 New Jitterbuffer Tuning
I had exactly the same experience running IAX2, but also experienced half-duplex calls on top of that (though I think that's a different but with IAX handoff), and in the end dropped it completely for SIP. We run g729 over dedicated fibre, and the resyncs were occurring all over the place with quite ludicrous values logged for delay. I tried tweaking the jitterbuf, turning it off completely, and reverting to the old jitterbuffer implementation. none of which made any difference. I also tried with and without trunking enabled. SIP is running much more acceptably now. Adam Robins wrote: After many days of playing with the new jitterbuffer and trunking options for IAX2, I have finally received almost acceptable quality. I am receiving 5-8 complaints a day of calls breaking up from both the customer and agent sides. What I have discovered is that in most of these cases, the new jitterbuffer performed a resync during the call. Currently, I have the resyncthreshold, and all other jb parameters at their default levels The traffic is running over a fairly high latency WAN connection between Canada and Atlanta (IAX2, ILBC). Idle ping times run about 85ms. Below are the resync messages for this past Friday. Knowing that I have a slow connection, should I set the resync at a much higher level? I appreciate any assistance you may provide. Thanks, Adam Feb 17 09:07:41 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -34, this delay 1651, threshold 1488, new offset -1651 Feb 17 09:07:42 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -120, this delay -1684, threshold 1000, new offset 33 Feb 17 10:21:04 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay 176, this delay 1835, threshold 1126, new offset -1835 Feb 17 10:21:04 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay 32, this delay 1673, threshold 1062, new offset -1673 Feb 17 10:21:04 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -150, this delay -1663, threshold 1300, new offset -172 Feb 17 10:21:04 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -150, this delay -1635, threshold 1300, new offset -38 Feb 17 10:21:48 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -22, this delay 2335, threshold 1054, new offset -2373 Feb 17 10:21:48 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay 11, this delay 2363, threshold 1082, new offset -2535 Feb 17 10:21:48 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -71, this delay 2249, threshold 1054, new offset -2249 Feb 17 10:21:48 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -180, this delay -2359, threshold 1360, new offset -14 Feb 17 10:21:48 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -150, this delay -2354, threshold 1300, new offset -181 Feb 17 10:21:48 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -120, this delay -2297, threshold 1240, new offset 48 Feb 17 10:34:28 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay 109, this delay 1556, threshold 1136, new offset -1556 Feb 17 10:34:28 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -30, this delay -1439, threshold 1000, new offset -117 Feb 17 10:34:32 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -7, this delay 1608, threshold 1048, new offset -1725 Feb 17 10:34:32 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -29, this delay -1616, threshold 1058, new offset -109 Feb 17 10:45:08 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay 21, this delay 1751, threshold 1620, new offset -1751 Feb 17 10:45:08 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -7, this delay 1724, threshold 1686, new offset -1724 Feb 17 10:45:08 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -60, this delay -1716, threshold 1000, new offset -8 Feb 17 10:45:08 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -119, this delay -1757, threshold 1000, new offset 6 Feb 17 11:28:45 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay 75, this delay 1421, threshold 1326, new offset -1421 Feb 17 11:28:45 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay 274, this delay 1595, threshold 1282, new offset -1595 Feb 17 11:29:03 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -1311, this delay 820, threshold 1824, new offset -2415 Feb 17 11:29:03 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -1349, this delay 761, threshold 1752, new offset -2182 Feb 17 11:29:03 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -299, this delay -2127, threshold 1598, new offset -288 Feb 17 11:29:03 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -270, this delay -2106, threshold 1540, new offset -76 Feb 17 11:46:15 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay 98, this delay 1878, threshold 1206, new offset -1878 Feb 17 11:46:15 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay 44, this delay 1799, threshold 1150, new offset -1799 Feb 17 11:46:15
RE: [Asterisk-Users] Asterisk 1.2.4 IAX2 New Jitterbuffer Tuning
Thank you for validating that I am not going mad! I made some additional tweaks for today. We'll see how it goes. If not well, then I'll try SIP for tomorrow. Thanks, Adam -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter Fern Sent: Tuesday, February 21, 2006 7:59 AM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] Asterisk 1.2.4 IAX2 New Jitterbuffer Tuning I had exactly the same experience running IAX2, but also experienced half-duplex calls on top of that (though I think that's a different but with IAX handoff), and in the end dropped it completely for SIP. We run g729 over dedicated fibre, and the resyncs were occurring all over the place with quite ludicrous values logged for delay. I tried tweaking the jitterbuf, turning it off completely, and reverting to the old jitterbuffer implementation. none of which made any difference. I also tried with and without trunking enabled. SIP is running much more acceptably now. Adam Robins wrote: After many days of playing with the new jitterbuffer and trunking options for IAX2, I have finally received almost acceptable quality. I am receiving 5-8 complaints a day of calls breaking up from both the customer and agent sides. What I have discovered is that in most of these cases, the new jitterbuffer performed a resync during the call. Currently, I have the resyncthreshold, and all other jb parameters at their default levels The traffic is running over a fairly high latency WAN connection between Canada and Atlanta (IAX2, ILBC). Idle ping times run about 85ms. Below are the resync messages for this past Friday. Knowing that I have a slow connection, should I set the resync at a much higher level? I appreciate any assistance you may provide. Thanks, Adam Feb 17 09:07:41 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -34, this delay 1651, threshold 1488, new offset -1651 Feb 17 09:07:42 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -120, this delay -1684, threshold 1000, new offset 33 Feb 17 10:21:04 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay 176, this delay 1835, threshold 1126, new offset -1835 Feb 17 10:21:04 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay 32, this delay 1673, threshold 1062, new offset -1673 Feb 17 10:21:04 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -150, this delay -1663, threshold 1300, new offset -172 Feb 17 10:21:04 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -150, this delay -1635, threshold 1300, new offset -38 Feb 17 10:21:48 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -22, this delay 2335, threshold 1054, new offset -2373 Feb 17 10:21:48 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay 11, this delay 2363, threshold 1082, new offset -2535 Feb 17 10:21:48 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -71, this delay 2249, threshold 1054, new offset -2249 Feb 17 10:21:48 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -180, this delay -2359, threshold 1360, new offset -14 Feb 17 10:21:48 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -150, this delay -2354, threshold 1300, new offset -181 Feb 17 10:21:48 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -120, this delay -2297, threshold 1240, new offset 48 Feb 17 10:34:28 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay 109, this delay 1556, threshold 1136, new offset -1556 Feb 17 10:34:28 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -30, this delay -1439, threshold 1000, new offset -117 Feb 17 10:34:32 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -7, this delay 1608, threshold 1048, new offset -1725 Feb 17 10:34:32 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -29, this delay -1616, threshold 1058, new offset -109 Feb 17 10:45:08 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay 21, this delay 1751, threshold 1620, new offset -1751 Feb 17 10:45:08 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -7, this delay 1724, threshold 1686, new offset -1724 Feb 17 10:45:08 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -60, this delay -1716, threshold 1000, new offset -8 Feb 17 10:45:08 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -119, this delay -1757, threshold 1000, new offset 6 Feb 17 11:28:45 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay 75, this delay 1421, threshold 1326, new offset -1421 Feb 17 11:28:45 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay 274, this delay 1595, threshold 1282, new offset -1595 Feb 17 11:29:03 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -1311, this delay 820, threshold 1824, new offset -2415 Feb 17 11:29:03 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -1349, this delay 761, threshold 1752, new offset -2182 Feb 17 11:29:03 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -299
Re: [Asterisk-Users] Asterisk 1.2.4 IAX2 New Jitterbuffer Tuning
Adam Robins wrote: Hi Adam After many days of playing with the new jitterbuffer and trunking options for IAX2, I have finally received almost acceptable quality. I am receiving 5-8 complaints a day of calls breaking up from both the customer and agent sides. What I have discovered is that in most of these cases, the new jitterbuffer performed a resync during the call. Currently, I have the resyncthreshold, and all other jb parameters at their default levels The traffic is running over a fairly high latency WAN connection between Canada and Atlanta (IAX2, ILBC). Idle ping times run about 85ms. I am interested to know why you are using ilbc, n why not g729 ot g723 or speex. What is the size of the WAN connection. How many calls are you running over this link. I just need to see how others are fairing with IAX2 over WAN links, as I am the final stages of testing on my side thanks, yusuf ___ --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
RE: [Asterisk-Users] Asterisk 1.2.4 IAX2 New Jitterbuffer Tuning
I was using G729 with Asterisk 1.07. With the new ability to do packet loss correction with ILBC, I felt I'd give it a try. The new PLC does not work with G729. I don't use Speex because my softphone does not support it. This is a 1.5mb IP-VPN connection with prioritized QOS for port 4569 (IAX2). I've never really stressed the bandwidth. Typically, only 10-20 concurrent calls. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of yusuf Sent: Monday, February 20, 2006 10:27 AM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] Asterisk 1.2.4 IAX2 New Jitterbuffer Tuning Adam Robins wrote: Hi Adam After many days of playing with the new jitterbuffer and trunking options for IAX2, I have finally received almost acceptable quality. I am receiving 5-8 complaints a day of calls breaking up from both the customer and agent sides. What I have discovered is that in most of these cases, the new jitterbuffer performed a resync during the call. Currently, I have the resyncthreshold, and all other jb parameters at their default levels The traffic is running over a fairly high latency WAN connection between Canada and Atlanta (IAX2, ILBC). Idle ping times run about 85ms. I am interested to know why you are using ilbc, n why not g729 ot g723 or speex. What is the size of the WAN connection. How many calls are you running over this link. I just need to see how others are fairing with IAX2 over WAN links, as I am the final stages of testing on my side thanks, yusuf ___ --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. ___ --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
RE: [Asterisk-Users] Asterisk 1.2.4 IAX2 New Jitterbuffer Tuning
I have now set the resyncthreshold to -1, to turn it off. I have also set the maxjitterbuffer to 2000. I still received 10 complaints of choppy calls today on Asterisk 1.2.4 versus only 1 complaint on Asterisk 1.07. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of yusuf Sent: Monday, February 20, 2006 10:27 AM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] Asterisk 1.2.4 IAX2 New Jitterbuffer Tuning Adam Robins wrote: Hi Adam After many days of playing with the new jitterbuffer and trunking options for IAX2, I have finally received almost acceptable quality. I am receiving 5-8 complaints a day of calls breaking up from both the customer and agent sides. What I have discovered is that in most of these cases, the new jitterbuffer performed a resync during the call. Currently, I have the resyncthreshold, and all other jb parameters at their default levels The traffic is running over a fairly high latency WAN connection between Canada and Atlanta (IAX2, ILBC). Idle ping times run about 85ms. I am interested to know why you are using ilbc, n why not g729 ot g723 or speex. What is the size of the WAN connection. How many calls are you running over this link. I just need to see how others are fairing with IAX2 over WAN links, as I am the final stages of testing on my side thanks, yusuf ___ --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. ___ --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
RE: [Asterisk-Users] Asterisk 1.2.4 IAX2 New Jitterbuffer Tuning
In my case I don't have a T1 or even a fractional T1, but cable and have noticed that choppy calls can be reduced by adding tos settings. Like: Tos=lowdelay|throughput|reliability Regards, Jesus -Original Message- From: Adam Robins [mailto:[EMAIL PROTECTED] Sent: Monday, February 20, 2006 14:43 To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: RE: [Asterisk-Users] Asterisk 1.2.4 IAX2 New Jitterbuffer Tuning I have now set the resyncthreshold to -1, to turn it off. I have also set the maxjitterbuffer to 2000. I still received 10 complaints of choppy calls today on Asterisk 1.2.4 versus only 1 complaint on Asterisk 1.07. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of yusuf Sent: Monday, February 20, 2006 10:27 AM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] Asterisk 1.2.4 IAX2 New Jitterbuffer Tuning Adam Robins wrote: Hi Adam After many days of playing with the new jitterbuffer and trunking options for IAX2, I have finally received almost acceptable quality. I am receiving 5-8 complaints a day of calls breaking up from both the customer and agent sides. What I have discovered is that in most of these cases, the new jitterbuffer performed a resync during the call. Currently, I have the resyncthreshold, and all other jb parameters at their default levels The traffic is running over a fairly high latency WAN connection between Canada and Atlanta (IAX2, ILBC). Idle ping times run about 85ms. I am interested to know why you are using ilbc, n why not g729 ot g723 or speex. What is the size of the WAN connection. How many calls are you running over this link. I just need to see how others are fairing with IAX2 over WAN links, as I am the final stages of testing on my side thanks, yusuf ___ --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. ___ --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 ___ --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
RE: [Asterisk-Users] Asterisk 1.2.4 IAX2 New Jitterbuffer Tuning
Title: RE: [Asterisk-Users] Asterisk 1.2.4 IAX2 New Jitterbuffer Tuning 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. From: [EMAIL PROTECTED] on behalf of Jesus E ZepedaSent: Mon 2/20/2006 5:02 PMTo: 'Asterisk Users Mailing List - Non-Commercial Discussion'Subject: RE: [Asterisk-Users] Asterisk 1.2.4 IAX2 New Jitterbuffer Tuning In my case I don't have a T1 or even a fractional T1, but cable and havenoticed that choppy calls can be reduced by adding tos settings. Like:Tos=lowdelay|throughput|reliabilityRegards,Jesus-Original Message-From: Adam Robins [mailto:[EMAIL PROTECTED]]Sent: Monday, February 20, 2006 14:43To: Asterisk Users Mailing List - Non-Commercial DiscussionSubject: RE: [Asterisk-Users] Asterisk 1.2.4 IAX2 New JitterbufferTuningI have now set the "resyncthreshold" to -1, to turn it off. I have alsoset the "maxjitterbuffer" to 2000.I still received 10 complaints of choppy calls today on Asterisk 1.2.4versus only 1 complaint on Asterisk 1.07.-Original Message-From: [EMAIL PROTECTED][mailto:[EMAIL PROTECTED]] On Behalf Of yusufSent: Monday, February 20, 2006 10:27 AMTo: Asterisk Users Mailing List - Non-Commercial DiscussionSubject: Re: [Asterisk-Users] Asterisk 1.2.4 IAX2 New JitterbufferTuningAdam Robins wrote:Hi Adam After many days of playing with the new jitterbuffer and trunkingoptions for IAX2, I have finally received almost acceptable quality. Iam receiving 5-8 complaints a day of calls "breaking up" from both thecustomer and agent sides. What I have discovered is that in most ofthese cases, the new jitterbuffer performed a resync during the call.Currently, I have the resyncthreshold, and all other jb parameters attheir default levels The traffic is running over a fairly high latencyWAN connection between Canada and Atlanta (IAX2, ILBC). Idle ping timesrun about 85ms.I am interested to know why you are using ilbc, n why not g729 ot g723or speex. What is the size of the WAN connection. How many calls areyou running over this link. I just need to see how others are fairingwith IAX2 over WAN links, as I am the final stages of testing on my sidethanks,yusuf___--Bandwidth and Colocation provided by Easynews.com --Asterisk-Users mailing listTo UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-usersThe contents of this email message and any attachments are confidentialand are intended solely for addressee. The information may also belegally privileged. This transmission is sent in trust, for the solepurpose of delivery to the intended recipient. If you have received thistransmission in error, any use, reproduction or dissemination of thistransmission is strictly prohibited. If you are not the intendedrecipient, please immediately notify the sender by reply email anddelete this message and its attachments, if any.___--Bandwidth and Colocation provided by Easynews.com --Asterisk-Users mailing listTo UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users___--Bandwidth and Colocation provided by Easynews.com --Asterisk-Users mailing listTo 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.___ --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
RE: [Asterisk-Users] Asterisk 1.2.4 IAX2 New Jitterbuffer Tuning
Title: RE: [Asterisk-Users] Asterisk 1.2.4 IAX2 New Jitterbuffer Tuning so you think this problem is asterisk and not a internet problem? My customers also complain alot about IAX2 connection to teliax which seemed to work better in older * versions. I have tried everything with no success, i switched to sip and its alot better but not perfect... From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adam RobinsSent: Monday, February 20, 2006 6:51 PMTo: Asterisk Users Mailing List - Non-Commercial Discussion; Asterisk Users Mailing List - Non-Commercial DiscussionSubject: RE: [Asterisk-Users] Asterisk 1.2.4 IAX2 New Jitterbuffer Tuning 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. From: [EMAIL PROTECTED] on behalf of Jesus E ZepedaSent: Mon 2/20/2006 5:02 PMTo: 'Asterisk Users Mailing List - Non-Commercial Discussion'Subject: RE: [Asterisk-Users] Asterisk 1.2.4 IAX2 New Jitterbuffer Tuning In my case I don't have a T1 or even a fractional T1, but cable and havenoticed that choppy calls can be reduced by adding tos settings. Like:Tos=lowdelay|throughput|reliabilityRegards,Jesus-Original Message-From: Adam Robins [mailto:[EMAIL PROTECTED]]Sent: Monday, February 20, 2006 14:43To: Asterisk Users Mailing List - Non-Commercial DiscussionSubject: RE: [Asterisk-Users] Asterisk 1.2.4 IAX2 New JitterbufferTuningI have now set the "resyncthreshold" to -1, to turn it off. I have alsoset the "maxjitterbuffer" to 2000.I still received 10 complaints of choppy calls today on Asterisk 1.2.4versus only 1 complaint on Asterisk 1.07.-Original Message-From: [EMAIL PROTECTED][mailto:[EMAIL PROTECTED]] On Behalf Of yusufSent: Monday, February 20, 2006 10:27 AMTo: Asterisk Users Mailing List - Non-Commercial DiscussionSubject: Re: [Asterisk-Users] Asterisk 1.2.4 IAX2 New JitterbufferTuningAdam Robins wrote:Hi Adam After many days of playing with the new jitterbuffer and trunkingoptions for IAX2, I have finally received almost acceptable quality. Iam receiving 5-8 complaints a day of calls "breaking up" from both thecustomer and agent sides. What I have discovered is that in most ofthese cases, the new jitterbuffer performed a resync during the call.Currently, I have the resyncthreshold, and all other jb parameters attheir default levels The traffic is running over a fairly high latencyWAN connection between Canada and Atlanta (IAX2, ILBC). Idle ping timesrun about 85ms.I am interested to know why you are using ilbc, n why not g729 ot g723or speex. What is the size of the WAN connection. How many calls areyou running over this link. I just need to see how others are fairingwith IAX2 over WAN links, as I am the final stages of testing on my sidethanks,yusuf___--Bandwidth and Colocation provided by Easynews.com --Asterisk-Users mailing listTo UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-usersThe contents of this email message and any attachments are confidentialand are intended solely for addressee. The information may also belegally privileged. This transmission is sent in trust, for the solepurpose of delivery to the intended recipient. If you have received thistransmission in error, any use, reproduction or dissemination of thistransmission is strictly prohibited. If you are not the intendedrecipient, please immediately notify the sender by reply email anddelete this message and its attachments, if any.___--Bandwidth and Colocation provided by Easynews.com --Asterisk-Users mailing listTo UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users___--Bandwidth and Colocation provided by Easynews.com --Asterisk-Users mailing listTo 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. This E-mail, including any attachments, may be intended solely for the personal and confidential use of the sende
Re: [Asterisk-Users] Asterisk 1.2.4 IAX2 New Jitterbuffer Tuning
Adam Robins wrote: 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. If you are running trunked IAX, try turning off the jitterbuffer entirely. Mark ___ --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
[Asterisk-Users] Asterisk 1.2.4 IAX2 New Jitterbuffer Tuning
After many days of playing with the new jitterbuffer and trunking options for IAX2, I have finally received almost acceptable quality. I am receiving 5-8 complaints a day of calls breaking up from both the customer and agent sides. What I have discovered is that in most of these cases, the new jitterbuffer performed a resync during the call. Currently, I have the resyncthreshold, and all other jb parameters at their default levels The traffic is running over a fairly high latency WAN connection between Canada and Atlanta (IAX2, ILBC). Idle ping times run about 85ms. Below are the resync messages for this past Friday. Knowing that I have a slow connection, should I set the resync at a much higher level? I appreciate any assistance you may provide. Thanks, Adam Feb 17 09:07:41 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -34, this delay 1651, threshold 1488, new offset -1651 Feb 17 09:07:42 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -120, this delay -1684, threshold 1000, new offset 33 Feb 17 10:21:04 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay 176, this delay 1835, threshold 1126, new offset -1835 Feb 17 10:21:04 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay 32, this delay 1673, threshold 1062, new offset -1673 Feb 17 10:21:04 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -150, this delay -1663, threshold 1300, new offset -172 Feb 17 10:21:04 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -150, this delay -1635, threshold 1300, new offset -38 Feb 17 10:21:48 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -22, this delay 2335, threshold 1054, new offset -2373 Feb 17 10:21:48 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay 11, this delay 2363, threshold 1082, new offset -2535 Feb 17 10:21:48 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -71, this delay 2249, threshold 1054, new offset -2249 Feb 17 10:21:48 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -180, this delay -2359, threshold 1360, new offset -14 Feb 17 10:21:48 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -150, this delay -2354, threshold 1300, new offset -181 Feb 17 10:21:48 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -120, this delay -2297, threshold 1240, new offset 48 Feb 17 10:34:28 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay 109, this delay 1556, threshold 1136, new offset -1556 Feb 17 10:34:28 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -30, this delay -1439, threshold 1000, new offset -117 Feb 17 10:34:32 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -7, this delay 1608, threshold 1048, new offset -1725 Feb 17 10:34:32 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -29, this delay -1616, threshold 1058, new offset -109 Feb 17 10:45:08 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay 21, this delay 1751, threshold 1620, new offset -1751 Feb 17 10:45:08 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -7, this delay 1724, threshold 1686, new offset -1724 Feb 17 10:45:08 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -60, this delay -1716, threshold 1000, new offset -8 Feb 17 10:45:08 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -119, this delay -1757, threshold 1000, new offset 6 Feb 17 11:28:45 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay 75, this delay 1421, threshold 1326, new offset -1421 Feb 17 11:28:45 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay 274, this delay 1595, threshold 1282, new offset -1595 Feb 17 11:29:03 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -1311, this delay 820, threshold 1824, new offset -2415 Feb 17 11:29:03 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -1349, this delay 761, threshold 1752, new offset -2182 Feb 17 11:29:03 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -299, this delay -2127, threshold 1598, new offset -288 Feb 17 11:29:03 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -270, this delay -2106, threshold 1540, new offset -76 Feb 17 11:46:15 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay 98, this delay 1878, threshold 1206, new offset -1878 Feb 17 11:46:15 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay 44, this delay 1799, threshold 1150, new offset -1799 Feb 17 11:46:15 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay 28, this delay 1781, threshold 1146, new offset -1781 Feb 17 11:46:15 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -150, this delay -1753, threshold 1000, new offset -46 Feb 17 11:46:15 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -150, this delay -1765, threshold 1000, new offset -16 Feb 17 11:46:15 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -149, this delay -1747, threshold 1298, new offset -131 Feb 17 11:54:36 WARNING[1078] chan_iax2.c: Resyncing the jb. last_delay -44, this delay 1136, threshold 1064, new
