search for: lantenc

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I''m using HTB to shape my outgoing traffic over a ADSL-link with PPPoE with a nominal bandwidth of 128kbit/s. My goal is to favour small packets like ACKs and interactive services like ssh; in other words, I want to achieve low lantency. If there are some big packets going over the wire, everything works fine. But if there are many small packets saturating my uplink, I get pings of 1000ms and above. To minimize this effect I''ve set the HTB qdisc rate to 100kbit/s. But even now, throttling my uplink to lower than 80%...

...ine was locked and we had to restart asterisk. How can we verify that asterisk is actually capable of receiving and placing calls? 4) We have no Digium boards and all kernels are 2.6 or above, so we end us using ztdummy, if needed. The client's agents are in a different country and the average lantency is around 250ms. Most of the time, call quality is good. However, there are a few situations where people complaint about echo. Is there a way to measure or "improve" this? I know it has been a topic discussed at lenght and if we could probably script a way to measure some sort of a MOS...

..." or "The network path was not found". Our Novell file server returned a perfect score card. They finally upgraded to 2.2.5 a month or so ago. This fixed many of our database problems as per the fixed bug list for 2.2.4 and 2.2.5, but we were still seeing these 30 second random lantencies when opening particularly office/MS project documents. We also had certain files which would consistently have delays of around 30 seconds yet opening it up on a PCNFS share worked fine. So there were still oplock problems in 2.2.5. There is a mention of batch oplock deadlock problems where...