[Asterisk-Users] SIP Jitter Buffer for 1.2.5
Rosario Pingaro
rpingar at nesec.it
Fri Mar 31 10:40:19 MST 2006
seems that if you get that log you didn't use jitetr buffer at all.
In my opinion the latest jitter 1.2-branch is not working, the last working
seems 1.2.1 patched.
Hope Zoa could lead us to fix it.
Regards
Rosario
----- Original Message -----
From: "Adam Moffett" <adam at plexicomm.net>
To: "Asterisk Users Mailing List - Non-Commercial Discussion"
<asterisk-users at lists.digium.com>
Sent: Friday, March 17, 2006 11:10 AM
Subject: Re: [Asterisk-Users] SIP Jitter Buffer for 1.2.5
>
>> jitterbuffer for svn trunk + jitterbuffer
>> jitterbuffer-1.2 for 1.2 + jitterbuffer
>> test-this-branch for the test branch with a lot of cool stuff
>> including
>> the jitterbuffer
>
> I installed the jitterbuffer-1.2 branch and I have a few questions.
>
> First and foremost I'm getting hundreds of lines like this in my log file:
>
> Mar 17 10:54:03 WARNING[22831] abstract_jb.c: Recieved frame with invalid
> timing info: has_timing_info=0, len=1668178290, ts=1718447988
> Mar 17 10:54:03 WARNING[22831] abstract_jb.c: Recieved frame with invalid
> timing info: has_timing_info=0, len=1668178290, ts=1718447988
>
> The console shows something similar:
> Mar 17 10:57:09 WARNING[22866]: abstract_jb.c:347 ast_jb_put: Recieved
> frame with invalid timing info: has_timing_info=0, len=-1, ts=166273064
> Mar 17 10:57:09 WARNING[22866]: abstract_jb.c:347 ast_jb_put: Recieved
> frame with invalid timing info: has_timing_info=0, len=-1, ts=166273064
> Mar 17 10:57:10 WARNING[22866]: abstract_jb.c:347 ast_jb_put: Recieved
> frame with invalid timing info: has_timing_info=0, len=-1, ts=166273064
>
> My log file is going to be very big today. What could be responsible for
> frames (every frame?) having invalid timing info?
>
> Second I'm not sure if it's actually doing anything. For testing, I tried
> setting the max size to 2000ms and implementation to fixed.....if I'm
> reading the comments in the sample config correctly that should create a
> 2000ms fixed jitter buffer, which in turn should mean a 2 second delay in
> audio, but I wasn't hearing any delay at all. Is this not a valid way to
> test whether the jitter buffer is doing something?
>
> Third....I'm interested in a way to create some jitter ;) I was thinking
> I might take an ethernet hub and try to saturate it with several
> simultaneous large file transfers or something like that. Another
> possibility might be an 802.11 wireless connection at a fairly long range.
> If anyone knows of a more convenient way for me to create a jittery
> connection I'd be very interested.
> _______________________________________________
> --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
>
>
More information about the asterisk-users
mailing list