search for: dsli

I have a server with dual nic's running centos 5.2 1 nic connects to the cable modem, which has 15m d and 2m up, but speed tests barely come back at 5mb down including road runner's internal speed test. I hook up my laptop to the same modem, same port, using the same cable and I get 17mb down. I have ruled out iptables, nics (because same result on both nics), cables, cable modem(with

auth 57b5848b subscribe icecast svetter@dsli.com --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe mess...

Greetings all, I just installed the beta now my SIP phone doesn't correctly hang up and clear trunks once the call is answered. First one is fine because it didn't answer on the far end. The second one stayed connected. -- Executing SetCallerID("SIP/100-5ab0", "<516301xxxx>") in new stack -- Executing Dial("SIP/100-5ab0",

Hi all, In GOOS[1] they use an assertion called assertEventually which samples the system for a success state until a certain timeout has elapsed. This allows you to synchronise the tests with asynchronous code. Do we have an equivalent of that in the Ruby / RSpec world already? I know capybara has wait_until { } but that''s fairly rudimentary - the failure message isn''t very

Just had a thought... Under Linux can you have one user session run icecast and in another user session run ices? I don't see why not, but thought I would ask... Scott --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word

The source is for ices-0.1.0. The errors occurs at the compile within the make for parse.c. The errors are: parse.c:41 parse error before 'doc' (same for 42 and 43) parse.c:44: parse error before 'ices_xml_get_root_element' parse.c:45: parse error before 'ices_xml_get_children_node' parse.c:45: parse error before 'cur' and the rest are warnings. Scott -------

I just install a Digium TDM04B card. I created 4 separate Zap channels and one outbound routing containing zap channels from 1 to 4. If a phone line is plug in Zap/1 then works fine, but if I unplug phone line from Zap/1 (simulating fail) the system keep dialing out on Zap/1, even with no dial tone; Only if Zap/1 is busy it will use Zap/2. There is any work around or different setting to avoid

I tried the 3.70 rpm and received an error that rpm couldn't handle the version of whatever packaged it. So I had to do things by getting the source and compiling. The same was true with lame. Also I copied all the lame headers to the /usr/local/include directory, did the ./configure which seemed to work and then did the make, which didn't. Any other ideas? Thanks, Scott ANGEL

Where can I find the 3.87 version of LAME? I've seen nothing later than 3.80 and this was just for documentation. The place I'm looking is lame.sourceforge.net. Perhaps you know a site that has the latest and greatest... Scott -------- Thomas Vander Stichele wrote: > > OK, I found LAME's web site and installed it using the source for it. That > > appears to work.

Hello: This is the first time I've used icecast and ices. I've got SuSE Linux 6.3, and downloaded icecast 1.3.11 and ices 0.1.0. For icecast I've done some configuring on it and am running it. I've pointed it to yp.icecast.org and the admin console says it's server id = 69. ices is not running now (see next paragraph) should I see my icecast server on yp.icecast.org?

Mr. Cully: Thanks for replying. Any idea where I can find such for a SuSE 6.3 system? I've looked at Yast's installable features and there is no such thing... Thanks, Scott ----- Brendan Cully wrote: > On Wednesday, 22 August 2001 at 17:53, Scott Vetter wrote: > > Now for ices, I've gotten through the "./configure" and get several > > error

Never mind I found the latest version of LAME and got the 3.87 version as you mentioned. When I did the gmake (interesting that it is no longer make) it still got the same errors. I copied the lame.h file to the directories /usr/local/include, /usr/local/include/lame, and even to the same directory as ices and still got the same error! Any ideas what to try next? Thanks, Scott -----

OK, I found LAME's web site and installed it using the source for it. That appears to work. I also found a couple of libxml... packages and either replaced the existing ones and added a few others. That went without problem. However the same problem exists. I found that the lame.h file is in a directory of /root/lame3.70 Perhaps the make can't find it at this directory? IS there