By default Zaptel runs with 8 byte chunk size. This equates to 1ms interrupt on TDM hardware! This causes congestion on the PCI bus and overal creates a bottle neck.
Sangomas hardware is able to automatically detect ZAPTEL chunk size and adjust accordingly. One can configure ZAPTEL for 8bytes (1ms - default)- 16bytes (2ms) - 40byte (5ms) or 80byte (10ms) chunk size. This would drastically reduce number of interrutps on your system and allow you to scale better with large number of ports.
To configure ZAPTEL for higher chunk size
./Setup install --zap-chunk=
Where CHUNK SIZE: 8, 16 , 40 or 80
Setup will patch zaptel source for selected chunk size and will remove wct4xxx (digium) driver out of zaptel Makefile. Reason for this is that digium wct4xxx driver does not support any chunk size other than 8bytes (1ms).
Once Setup recompiles zaptel and wanpipe drivers. There are no other configuration needed! Just start wanpipe and zaptel and Asterisk:
- wanrouter start
- ztcfg -vvv
- asterisk
- asterisk -c -r
In order to confirm that you are running with new zaptel chunk size. run:
- ifconfig w1g1
-> confirm that MTU = configured chunk size.
IMPORTANT:
This option has been tested in production and is SAFE for T1/E1 PRI Mode.
If running meetme chunk size of 40 is suggested.
Otherwise chunk size of 80 is most efficient..
Software echo cancelers are made for a chunk size of 8, so they may not function correctly.
This option does not work very well for ANALOG and T1/E1 E&M wink!
because zaptel hard codes the chunk size to 8 in some of the Analog/RBS
timing code. Sangoma is working on this problem.
If you are having trobule with this configuraiton please contact Sangoma Support.
No comments:
Post a Comment