diff options
| author | russell <russell@f38db490-d61c-443f-a65b-d21fe96a405b> | 2006-06-01 16:47:28 +0000 |
|---|---|---|
| committer | russell <russell@f38db490-d61c-443f-a65b-d21fe96a405b> | 2006-06-01 16:47:28 +0000 |
| commit | f796193575703618e2b05e84545e3354543a8276 (patch) | |
| tree | 65c18318da656f3d8bdc20876d5774763985c46a /configs/zapata.conf.sample | |
| parent | 9f95248be1f852e3b6d2171eb0d95c715471f881 (diff) | |
- add the ability to configure forced jitterbuffers on h323, jingle,
and mgcp channels
- remove the jitterbuffer configuration from the pvt structures in
the sip, zap, and skinny channel drivers, as copying the same global
configuration into each pvt structure has no benefit.
- update and fix some typos in jitterbuffer related documentation
(issue #7257, north, with additional updates and modifications)
git-svn-id: http://svn.digium.com/svn/asterisk/trunk@31413 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'configs/zapata.conf.sample')
| -rw-r--r-- | configs/zapata.conf.sample | 10 |
1 files changed, 3 insertions, 7 deletions
diff --git a/configs/zapata.conf.sample b/configs/zapata.conf.sample index aacbce020..c20ecbe5f 100644 --- a/configs/zapata.conf.sample +++ b/configs/zapata.conf.sample @@ -501,11 +501,7 @@ immediate=no ; be used only if the sending side can create and the receiving ; side can not accept jitter. The ZAP channel can't accept jitter, ; thus an enabled jitterbuffer on the receive ZAP side will always - ; be used if the sending side can create jitter or if ZAP jb is - ; forced. - -; jbforce = no ; Forces the use of a jitterbuffer on the receive side of a ZAP - ; channel. Defaults to "no". + ; be used if the sending side can create jitter. ; jbmaxsize = 200 ; Max length of the jitterbuffer in milliseconds. @@ -514,8 +510,8 @@ immediate=no ; big jumps in/broken timestamps, usualy sent from exotic devices ; and programs. Defaults to 1000. -; jbimpl = fixed ; Jitterbuffer implementation, used on the receiving side of a SIP - ; channel. Two implementation are currenlty available - "fixed" +; jbimpl = fixed ; Jitterbuffer implementation, used on the receiving side of a ZAP + ; channel. Two implementations are currenlty available - "fixed" ; (with size always equals to jbmax-size) and "adaptive" (with ; variable size, actually the new jb of IAX2). Defaults to fixed. |