I was wondering if this e-mail hit the list or maybe I wasn't exactly clear on what I'm trying to achieve and that's why I got no answers.<br><br>Best regards,<br>Marcin<br><br><div class="gmail_quote">2012/2/16 Marcin Gozdalik <span dir="ltr"><<a href="mailto:gozdal@gmail.com">gozdal@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi<br><br>I am trying to export some variables to consumers (mod_fifo) or
callback agents (mod_callcenter). The basic scenario I am trying to
achieve is to associate some data with path taken in IVR (in form of
exported variable) and pass information on which option was chosen in
IVR to the agent. I took a look at the source to find out how
mod_fifo/mod_callcenter originate calls to consumer/callback agents and
it seems the calls are not associated with A-leg (somebody calling to
IVR and transferred to queue).<br>
Is it on purpose? Is there a workaround for that?<br><br>I also spotted
strange behavior of mod_fifo when originating calls to consumers. It
sets absolute_codec_string for calls originated to consumers to
variable_sip_use_codec_name from A-leg, adding PCMA/PCMU if not already
present. I find the logic there quite puzzling. If somebody is calling
to queue using e.g. G.729, mod_fifo will restrict codecs available in
leg to consumer to only G.729, PCMA, PCMU. Why is this narrowing of
choice of codecs implemented?<br clear="all"><br>Best regards<span class="HOEnZb"><font color="#888888"><br><br>-- <br>Marcin Gozdalik<br>
</font></span></blockquote></div><br><br clear="all"><br>-- <br>Marcin Gozdalik<br>