I have tried .call files and it seems slow. I would put 50 call files in the /outgoing directory and my server would pick up about 5 or 6 of them at a time and as those calls completed, it would pick up another .call file. I was getting results of >3.5 minutes for it to process the 50 calls. I have already confirmed with my voip provider that I have hundreds of channels available to me.
Most recently, I have been using AMI and passing the Originate command (using URL with rawman? parameters) which seems to work but fear the http overhead will bite me when trying to make many calls. Also, this approach seems to have a show-stopper. The Originate action implies a Dial() app and since I need to set some CDR values BEFORE the Dial() takes place, Originate does not allow for this. I also need to make decisions based on DIALSTATUS. For instance, if I pass info using Originate and number dialed is BUSY, the call never enters my dialplan context where I set and evaluate Dialstatus and CDR values. If a line is BUSY, my voip provider just sends a message back to my server and the context in my dialplan is never entered into. I cannot figure out another way to enter the dialplan via AMI - Originate seems to be the only way in. Is there another way?
I am now looking into using FastAGI. Thanks for your help.
Main Topics
Browse All Topics





by: xuserx2000Posted on 2009-06-01 at 09:39:19ID: 24519299
Have you looked at using call files ? iki-index. php?page=A sterisk+au to- dial+ou t
http://www.voip-info.org/t
You can also generate calls using the AMI, without a web interface.....I guess it depends on how you have things setup as to which solution is best for you. Can you give a more detailed description of your setup ?....