yah, I looked into that and it's not possible to do.<br><br>Your usage of the dialplan like a database is just not a good way to do it.<br>I suggest you use a database or something else to store that routing data like others do.<br>
<br><br><br><div class="gmail_quote">On Wed, Jul 22, 2009 at 10:55 AM, Tamas Cseke <span dir="ltr"><<a href="mailto:cstomi.levlist@gmail.com">cstomi.levlist@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello,<br>
<br>
we are using mod_loopback for outbound calls to be able to do a dialplan<br>
hunt before the actual call origination.<br>
change caller number, change routing according to the prefix and<br>
something like that.<br>
We have talked about a lot, that this is "not very" efficient because<br>
we have 2 extra channels (loopbacks) for every call.<br>
<br>
I diged into the state machine code and figured out that if I change the<br>
on_routing state handler functions for switch_ivr_originate to don't<br>
veto the standard behavior I can perform a dilplan hunt.<br>
But I still have to originate a channel which makes a dialplan hunt and<br>
originate another. and this isn't what we really would like to...<br>
<br>
I've got the following tip from Anthony earlier:<br>
0416 16:39:28 <@anthm> maybe i could make an api command to pretend to<br>
do a dialplan run and print out a list in inline format of what to do<br>
0416 16:39:48 <@anthm> that you could feed to originate inline dialplan<br>
<br>
But I don't know how to implement this. I need some explanation.<br>
<br>
1) the dialplan pretender api returns applications in inline format<br>
2) we feed it to inline dialplan<br>
but how could we originate the call, how should the whole process look like?<br>
could you please give me an example?<br>
<br>
I was thinking about someting like this, but it doesn't make sense I quess.<br>
${originate(call_url inline ${pretend_dialplan_hunt(exten XML context)})}<br>
<br>
Thanks in advance,<br>
Tamas<br>
<br>
<br>
<br>
_______________________________________________<br>
FreeSWITCH-dev mailing list<br>
<a href="mailto:FreeSWITCH-dev@lists.freeswitch.org">FreeSWITCH-dev@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-dev" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-dev</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Anthony Minessale II<br><br>FreeSWITCH <a href="http://www.freeswitch.org/">http://www.freeswitch.org/</a><br>ClueCon <a href="http://www.cluecon.com/">http://www.cluecon.com/</a><br>
Twitter: <a href="http://twitter.com/FreeSWITCH_wire">http://twitter.com/FreeSWITCH_wire</a><br><br>AIM: anthm<br><a href="mailto:MSN%3Aanthony_minessale@hotmail.com">MSN:anthony_minessale@hotmail.com</a><br>GTALK/JABBER/<a href="mailto:PAYPAL%3Aanthony.minessale@gmail.com">PAYPAL:anthony.minessale@gmail.com</a><br>
IRC: <a href="http://irc.freenode.net">irc.freenode.net</a> #freeswitch<br><br>FreeSWITCH Developer Conference<br><a href="mailto:sip%3A888@conference.freeswitch.org">sip:888@conference.freeswitch.org</a><br><a href="http://iax:guest@conference.freeswitch.org/888">iax:guest@conference.freeswitch.org/888</a><br>
<a href="mailto:googletalk%3Aconf%2B888@conference.freeswitch.org">googletalk:conf+888@conference.freeswitch.org</a><br>pstn:213-799-1400<br>