On Fri, Jan 23, 2009 at 4:39 PM, Michael Collins <msc@freeswitch.org> wrote:

On Fri, Jan 23, 2009 at 2:15 PM, Shelby Ramsey <sicfslist@gmail.com> wrote:
> Sorry for the double post ... actually hit send too early ...
> 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 ...
> 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 (not to xml cdr ... and the "proxying" of
> media) ...
> Would like to do something like:
> -- originate request (looks simple enough)
> -- on answer XML_CURL posts info

Several choices, depending upon how much you want it handled inside
the dialplan vs. handled in the scripting language. For the sake of
testing you could do something like this:
<extension name="ivr-start">
<condition field="destination_number" expression="ivr_whatever">
<action application="set" data="execute_on_answer=transfer
IVR_ANSWER XML default"/>

</condition>
</extension>

Then have:
<extension name="ivr-answer">
<condition field="destination_number" expression="IVR_ANSWER">
<action application="lua" data="post-info.lua ${some_important_value}"/>
</condition>
</extension>

This would have any answered call go to the "ivr-answer" extension
while unanswered calls could stay in the ivr-start extension to get
properly handled. (Busy, no answer, invalid/SIT, etc.)

You could then have the "ivr-answer" extension do whatever is
appropriate, like listen for digits, play announcement, beg for money,
etc. :)

-MC

> But for the life of me I can't figure out how to translate this into the xml
> response ...
> [campaign]
> exten => 100,1,ANSWER()
> exten => 100,n,WAIT(2)
> exten => 100,n,BACKGROUND(${SOUND_DIR}/somefile)
> exten => 100,n,WAITEXTEN(10)
> exten => 100,n,HANGUP()
> exten => 1,1,PLAYBACK(goodbye)
> .... and so on ...
> I've looked at the ivr.conf stuff but it's all static and all of this has to
> be manageable via a web interface .... meaning dumping into a DB and
> returning an XML response seems reasonable ... but trying to stick or modify
> static text files from the web interface is too much text parsing and bad
> things will happen ...
> Any thoughts or pointing me in the right direction would be appreciated.
> Shelby
>
>
>

> _______________________________________________
> Freeswitch-users mailing list
> Freeswitch-users@lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
>
>

_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org