search for: 43x

...seen a problem where the autoattend detects the first digit twice? What I am seeing is this: My extensions are 421-468. When a caller calls in and dials exten 433 from the autoattendant, they get exten 443. This is happen for any extension that is valid in the 44x range (i.e. 42x -> 442, 43x -> 443, 44x -> 444, etc.). I am seeing this problem about 1/3 of the time. My setup is 6 PSTN (POTS) lines -> AccessBankII channel bank -> T100P card on the asterisk server -> Cisco 7940's and 7960's. I have been through the wiki and the archives, but haven't found any...

Erik de Castro Lopo wrote: >> Currently, compression settings are as follows >> >> -6, -l 8 -b 4096 -m -r 6-A tukey(0.5) >> -7, -l 8 -b 4096 -m -e -r 6-A tukey(0.5) >> -8, -l 12 -b 4096 -m -e -r 6-A tukey(0.5) >> >> I suggest the following, in case my previous patch is accepted >> >> -6, -l 8 -b 4096 -m -r 6 -A tukey(0.5);partial_tukey(2)

...> > Any thoughts? From <http://www.rockbox.org/wiki/CodecPerformanceComparison> it seems that the decoding of -8 is about 6% slower than -5. Sometimes the difference is bigger but doesn't exceed 10%. The only exception is "Freescale i.MX21 (454MHz ARM926EJ?-S, Fuze+)": 43x vs 35x realtime. But the decoding time is so small (4 sec vs 5 sec) that it can be some measurement error.

Joseph Little wrote: > I''d love to "vote" to have this addressed, but apparently votes for > bugs are no available to outsiders. > > What''s limiting Stanford EE''s move to using ZFS entirely for our > snapshoting filesystems and multi-tier storage is the inability to > access .zfs directories and snapshots in particular on NFSv3 clients.