USAGE <call url> <exten>|&<application_name>(<app_args>) [<dialplan>] [<context>] [<cid_name>] [<cid_num>] [<timeout_sec>]
in place of &playback(foo) you can put an extension and optionally a dialplan name and context
and the call will hit the xml dialplan with the extension string as the destination_number field.
I've been using FS for almost a year now as a call-blaster type of
device (originating SIP calls and playing wav/mp3 when user answers).
In the past I was simply sending all calls to a single SIP switch,
but now I need to think about routing to several different SIP
switches, based on NPA-NXX for example.
The XML dialplan would seem perfect for this, but that's only
triggered by an incoming call, right? I am not sure how to cause
'outbound-only' calls to go through it (since Freeswitch is
originating the call, it only has 1 leg, if that makes sense).
Currently I am originating via XML-RPC from a Perl script, using a
command like 'originate <sip address> &playback(wav file)'. The final
caveat is that we not use javascript to originate the call because I
am still having problems with garbage collection during capacity
testing (the box is pushing out 20cps, 30-second calls, 600
simultaneous calls).
Thanks,
Tom
===============
tuhl@ix.netcom.com
_______________________________________________
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