[asterisk-users] Dahdi complete 2.5.0.1 - dahdi_dummy not compiled

[Administrator TOOTAI]

Le 07/11/2011 10:19, Tzafrir Cohen a écrit :
>
>> How can we get dahdi_dummy compiled on those machines?
> You no longer need to. Merely loading the module dahdi provides timing
> and pseudo channels for conferences if no DAHDI hardware is available.

Well:

output of 1.6.20 without dahdi_dummy Debian Squeeze (Bad)

--- Results after 124 passes ---
Best: 100.000 -- Worst: 99.604 -- Average: 99.882464, Difference: 100.001599
dh at pabx2:/etc/dahdi$ sudo lsmod|grep dahdi
dahdi                 171134  0
crc_ccitt               1323  1 dahdi


output of 1.6.20 without dahdi_dummy Debian Lenny Backport (Bad)

--- Results after 269 passes ---
Best: 100.000 -- Worst: 99.607 -- Average: 99.953130, Difference: 99.999378
dh at kumquat:~$ sudo lsmod|grep dahdi
dahdi                 171150  26
crc_ccitt               1323  1 dahdi


output of 1.6.20 with dahdi_dummy Debian Lenny (Good)

--- Results after 184 passes ---
Best: 100.000 -- Worst: 99.979 -- Average: 99.997323, Difference: 99.997337
dh at asterix:~$ lsmod|grep dahdi
dahdi_dummy             8080  0
dahdi_transcode        11912  1 wctc4xxp
dahdi_voicebus         40768  2 wctdm24xxp,wcte12xp
dahdi                 200912  18 
dahdi_dummy,xpp,dahdi_transcode,wcb4xxp,wctdm,wcfxo,wctdm24xxp,wcte11xp,wct1xxp,wcte12xp,dahdi_voicebus,wct4xxp
crc_ccitt               6528  1 dahdi


output of 1.8.7-1 with dahdi_dummy from Ubuntu server package 
asterisk.org (Good)

--- Results after 84 passes ---
Best: 99.998 -- Worst: 99.993 -- Average: 99.996689, Difference: 99.996689
dh at bescomx:/var/log/asterisk$ sudo lsmod | grep dahdi
dahdi_transcode         6836  0
dahdi_dummy             2760  0
dahdi                 210885  2 dahdi_transcode,dahdi_dummy
crc_ccitt               1675  1 dahdi


Our problem is that on servers without dahdi_dummy (the 2 first) we face 
problem with cutted calls or bad audio (words are cutted or one syllabe 
of three). We are using SIP and ulaw/alaw codec. Face the same behavior 
with g722.

Problem appears on phones (SNOM) connected directly to the servers and 
not to users using their own asterisk server connected to those two 
servers.

-- 
Daniel