My application dials 100's of numbers, waits for user to answer, plays a .wav file, and waits for some DTMF. I'm using the Javascript interface to do all this now (actually it's a Perl script which launches JS by sending jsrun commands through the RPC XML interface). But at high call rates, I'm running into JS garbage collection issues fairly quickly. At 10 calls per second, after about 300 calls it looks like JS GC kicks in and runs for like 45 seconds, during which time I can't launch any more calls with JS (RPC XML accepts them, but then they are getting Q'd up inside the spidermonkey code, and eventually some of them fail because GC is taking so long, etc). Is JS the best way to do this application, and if so, any ideas how I workaround the GC? If not, what is the alternative (where I would still have access to the simple programming interface that JS gives me, as far as all the session. functions like waitForAnswer, streamFile, getDigits). Tom =============== tuhl@ix.netcom.com