| commit | 30690adbc81a1fe15eb5e48b3201772486d79ed0 | [log] [tgz] |
|---|---|---|
| author | Holger Hans Peter Freyther <zecke@selfish.org> | Wed Oct 24 20:31:25 2012 +0200 |
| committer | Holger Hans Peter Freyther <zecke@selfish.org> | Mon Nov 12 10:45:03 2012 +0100 |
| tree | 0efb8f0cb11025304234cfe718076b9b55df615e | |
| parent | 38e02c51250d61bb78912a4f8e67a650691c5149 [diff] |
mgcp: Calculate the jitter with the formula/code from the appendix Use a usec timestamp for the local time. The seconds to usec will swap over to the lower bits but this appears to be correct. The CLOCK_MONOTONIC is used to fulfill the RFC 3550 requirement even if it is a bit slower than the gettimeofday. Make sure to initialize transit in a way that the first transit time will be 0. Otherwise the jitter will contain the difference of the localtime and the remote time.