similar to: De-jitter buffer

On Tue, 2017-11-28 at 12:25 +0100, Julien Viard de Galbert wrote: CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hello, Le 28 nov. 2017 ? 00:39, Joakim Tjernlund via Syslinux <syslinux at zytor.com<mailto:syslinux at zytor.com>> a ?crit : On Mon, 2017-11-27 at 18:18

On Wed, 2017-12-13 at 10:34 -0500, Gene Cumm wrote: > CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. > > > On Wed, Dec 13, 2017 at 7:03 AM, Joakim Tjernlund > <Joakim.Tjernlund at infinera.com> wrote: > > On Mon, 2017-12-11 at 08:59 +0100, Joakim

On Tue, 2018-12-18 at 14:10 -0500, Gene Cumm wrote: > On Wed, Dec 12, 2018 at 6:30 PM Joakim Tjernlund via Syslinux > <syslinux at zytor.com> wrote: > > On Wed, 2018-12-12 at 17:10 -0600, Carl Karsten wrote: > > > CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is

On Wed, 2019-02-06 at 16:00 +0100, Joakim Tjernlund wrote: > On Tue, 2019-02-05 at 14:07 -0800, H. Peter Anvin via Syslinux wrote: > > CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. > > > > > > Hi all, > > > > It has been the case for

On Wed, Feb 6, 2019 at 2:35 PM H. Peter Anvin via Syslinux <syslinux at zytor.com> wrote: > > On 2/6/19 9:17 AM, Joakim Tjernlund via Syslinux wrote: > > On Wed, 2019-02-06 at 16:00 +0100, Joakim Tjernlund wrote: > >> On Tue, 2019-02-05 at 14:07 -0800, H. Peter Anvin via Syslinux wrote: > >>> CAUTION: This email originated from outside of the organization. Do

Hi, I thought I'd repost this to the -users list for some background on the jitter buffer and its workings and remaining issue.s I'll also pu a little executive summary here at the top: Where a channel is native bridged to another iax2 channel: 1) Lag is not measured and will usually show 0ms. Any other number is an old measurement from the start of the call 2) The jitter

On Wed, Nov 29, 2017 at 6:30 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Tue, Nov 28, 2017 at 2:38 PM, Joakim Tjernlund > <Joakim.Tjernlund at infinera.com> wrote: >> On Mon, 2017-11-27 at 18:18 -0500, Gene Cumm wrote: > >>> On Mon, Nov 27, 2017 at 6:07 PM, Joakim Tjernlund >>> <Joakim.Tjernlund at infinera.com> wrote: >>> > On

Hi, Attached is a small patch (based of r139696) which is required for clean builds on Solaris 10 / x86 using gcc 4.5.1 - it is simply a missing include. The exact same problem also exists in the 2.9-stable branch, but not in 2.8. Please consider it for inclusion. Cheers, Joakim -------------- next part -------------- A non-text attachment was scrubbed... Name: solaris_limit.patch Type:

On Wed, 2018-12-12 at 17:10 -0600, Carl Karsten wrote: > CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. > > > On Wed, Dec 12, 2018 at 4:54 PM Joakim Tjernlund > <Joakim.Tjernlund at infinera.com> wrote: > > > While I am here, I want to ask: >

On Wed, Dec 13, 2017 at 7:03 AM, Joakim Tjernlund <Joakim.Tjernlund at infinera.com> wrote: > On Mon, 2017-12-11 at 08:59 +0100, Joakim Tjernlund wrote: >> On Sun, 2017-12-10 at 14:41 -0500, Gene Cumm wrote: >> > CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is

On Wed, 2019-02-06 at 11:34 -0800, H. Peter Anvin wrote: > On 2/6/19 9:17 AM, Joakim Tjernlund via Syslinux wrote: > > On Wed, 2019-02-06 at 16:00 +0100, Joakim Tjernlund wrote: > > > On Tue, 2019-02-05 at 14:07 -0800, H. Peter Anvin via Syslinux wrote: > > > > CAUTION: This email originated from outside of the organization. Do not click links or open attachments

On Wed, 2018-12-12 at 17:05 -0600, Carl Karsten wrote: > On Wed, Dec 12, 2018 at 4:54 PM Joakim Tjernlund > <Joakim.Tjernlund at infinera.com> wrote: > > On Wed, 2018-12-12 at 16:00 -0600, Carl Karsten via Syslinux wrote: > > > CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know

Greetings list, Some time ago (probably about a year ago now) we disabled IAX jitter buffering on all our boxes because it was causing issues in a mixed 1.0 and 1.2 environment. One thing I've noticed over the last few months as more and more clients have moved from the 512k/1mb/2mb ADSL connections they were using onto "up to 8mb" connections is that whilst overall throughput is a

On Thu, 2019-02-07 at 06:12 -0500, Gene Cumm wrote: > On Wed, Feb 6, 2019 at 2:35 PM H. Peter Anvin via Syslinux > <syslinux at zytor.com> wrote: > > On 2/6/19 9:17 AM, Joakim Tjernlund via Syslinux wrote: > > > On Wed, 2019-02-06 at 16:00 +0100, Joakim Tjernlund wrote: > > > > On Tue, 2019-02-05 at 14:07 -0800, H. Peter Anvin via Syslinux wrote: > >

On February 11, 2019 12:29:41 PM PST, Joakim Tjernlund <Joakim.Tjernlund at infinera.com> wrote: >On Mon, 2019-02-11 at 12:15 -0800, H. Peter Anvin via Syslinux wrote: >> >> >> I think I botched syslinux-6.04-pre3. There are two fundamental >> problems with the build: >> >> a) The selection of what pieces of the library gets included in the >core

On 2/6/19 9:17 AM, Joakim Tjernlund via Syslinux wrote: > On Wed, 2019-02-06 at 16:00 +0100, Joakim Tjernlund wrote: >> On Tue, 2019-02-05 at 14:07 -0800, H. Peter Anvin via Syslinux wrote: >>> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. >>>

On Wed, 2018-12-12 at 16:00 -0600, Carl Karsten via Syslinux wrote: > CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. > > > On Tue, Dec 11, 2018 at 9:19 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > > > You should be able to

On Mon, 2018-12-17 at 23:52 +0100, Lukas Schwaighofer wrote: > CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. > > > Hi Joakim, > > On Wed, 12 Dec 2018 23:25:24 +0000 > Joakim Tjernlund via Syslinux <syslinux at zytor.com> wrote: > > > I

Hmm, I tried... I completly understand an idea of jitter buffer and I know there is a lot of kinds of this solution (eg. AJB - Adaptive Jitter Buffer). I simply want to know what type is used in speex codec and how could I use that. What is the reason for using jitter buffer implemented in speex against to my own (implemented at lower layer - transmission layer - eg. rtp). Kapul On Tue, Sep

Hi, I know that there was a jitter buffer patch (for sip) for the 1.0.9 branch some time agin. At this time, we can not upgrade to 1.4.x. Is there a useable, fairly stable INCOMING sip jitter buffer patch? That is.. I want Asterisk to jitter buffer incoming SIP packets. -------------- next part -------------- An HTML attachment was scrubbed... URL: