VoIP Mailing List Archives

[sicfslist at gmail.com]

OK ... Here goes another I'm doing this with AST ... but I want to move it to FS. Searched via google site:lists.freeswitch.org auto dialer and others ... nothing useful.

Today I have a platform for auto dialing with AST (centrally managed ... about 10 machines) and we do this:
-- Remote machines query central DB for numbers to call based on certain configs
-- Use AMI to generate the call
-- If call gets answered, extension info queried via rta (central db again)

The nice thing about all of this is it's relatively easy to manage (through one central web interface we built) and it works ... the bad part is reporting ... as anyone knows on this list that has used AST for auto dialing in this way (via .call or AMI) every call looks like it fails instead of showing a real cause code.

So ... conceptually I'm trying to accomplish the same thing ...

Today we use FS a lot for termination of VoIP traffic ... all done via XML_CURL ... which is awesome!

Would like to do something like:
-- originate request
-- on answer XML_CURL posts info

[egghunt at gmail.com]

On Fri, Jan 23, 2009 at 8:04 PM, Shelby Ramsey <sicfslist@gmail.com (sicfslist@gmail.com)> wrote:

[brian at freeswitch.org]

http://wiki.freeswitch.org/wiki/Mod_commands#originate

/b

On Jan 23, 2009, at 4:33 PM, Arnaldo de Moraes Pereira wrote:

[anthony.minessale at g...]

Does AST mean Asterisk Open Source PBX ?

If so, then yes I am familiar with it's archetechure as I am a former developer from that project.

You have 3 choices with FreeSWITCH

1) You can open a dedicated connection to mod_event_socket or XMLRPC per call and issue the originate command from there:
This will block until you know for sure the outcome of the attempt. If it's success it will give you the uuid if not it gives you the cause code.

2) You can use a single mod_event_socket or XMLRPC connection to send all calls but use the bgapi mechanism which will do the same as above
only asynchronously, The command will return immediately and the result will be fired as an event that you can pick up on the same or different event_socket connection or
other event consumer such as a custom C,perl,lua etc module.

3) You can use mod_xml_cdr to generate detailed 1-file-per-leg call files that will tell you when where and why the calls failed or did not fail.




On Fri, Jan 23, 2009 at 4:04 PM, Shelby Ramsey <sicfslist@gmail.com (sicfslist@gmail.com)> wrote: