Question about

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Both are handled too. For clock drift scenario, the handling may be outside
the jitter buffer, depending on which clock is faster.

Btw OT, why are you setting your mailer to use right justification? It makes
it hard to reply inline (and harder to read as well)

On Fri, Jul 3, 2009 at 9:19 AM, jay bing <jaya.bing at gmail.com> wrote:

> hi all
>
> what happend if VAD is on?
> in this case there will be more get then put..
>
> also, what happend if one clock is faster then the other?
> i ask because these are the kind of problem i am facing..
>
> thanks
> jay
>
>  2009/7/3 Benny Prijono <bennylp at teluu.com>
>
>>  On Wed, Jul 1, 2009 at 9:38 AM, ??? <shchoi at etri.re.kr> wrote:
>>
>>> Hi, all.
>>>
>>> I am studying Adaptive Jitter Buffer in pjsip.
>>>
>>> In pjsip code,
>>>
>>> /* States */
>>>    int             jb_level;           /**< delay between source &
>>>                                             destination (calculated
>>> according
>>>                                             of the number of burst
>>> get/put
>>>                                             operations)
>>>  */
>>>
>>> I can't understand to calculate the delay by just GET/PUT operation
>>> How different is between that delay and E2E delay of real packet
>>> timestamp?
>>>
>>>
>> GET is called periodially every 20 ms (or whataver frame_ptime is). PUT is
>> called everytime frame arrives from the network. So if there is no jitter,
>> then the number of GET and PUT will be equal all the time (plus/minus one).
>> If there is jitter, then the jitter value is the difference between the
>> value of the two operations.
>>
>> The pro of this approach is it doesn't rely on wall time, and if there is
>> actually jitter in the GET operations too, then it will be accommodated by
>> the jbuf as well.
>>
>>
>>
>>> Is there a PAPER or a PATENT about adaptive jitter buffer algorithm
>>> implemented pjsip?
>>>
>>>
>> I'm not aware of that, and definitely I don't want to know about it!
>>
>> cheers
>>  Benny
>>
>>
>>  Thanks.
>>>
>>> Seunghan.
>>>
>>>
>>> _______________________________________________
>>> Visit our blog: http://blog.pjsip.org
>>>
>>> pjsip mailing list
>>> pjsip at lists.pjsip.org
>>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>>>
>>
>>
>> _______________________________________________
>> Visit our blog: http://blog.pjsip.org
>>
>> pjsip mailing list
>> pjsip at lists.pjsip.org
>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>>
>>
>
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
>
> pjsip mailing list
> pjsip at lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20090703/50b3a071/attachment.html>


[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux