<br><br><div class="gmail_quote">On Mon, Jun 13, 2011 at 9:37 AM, Hector Geraldino <span dir="ltr"><<a href="mailto:Hector.Geraldino@ip-soft.net">Hector.Geraldino@ip-soft.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div lang="EN-US" link="blue" vlink="purple"><div><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Hi Michael,</span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p><p class="MsoNormal">
<span style="font-size:11.0pt;color:#1F497D">I finally figure out how to connect both calls using the command ‘intercept’. From the inbound call (handled by the OB socket) I just do an execute intercept legB uuid, and both calls are bridged perfectly. Thanks very much.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">So the only thing that stills concerns me is why the event CHANNEL_ANSWER is always generated on the outbound call (legb), even if the user doesn’t pick up the call. Also I can’t find any differences on the CHANNEL_CALLSTATE or CALL_UPDATE events that allows me to determine when an outbound call generated from FS is actually answered or not.</span></p>
</div></div></blockquote><div>Did you ever post the full call debug log with a siptrace? I don't recall seeing that...</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div lang="EN-US" link="blue" vlink="purple"><div><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">BTW, I bought the FS 1.0.6 book on Amazon last week and I want to congratulate you and Anthony/Darren for the excellent work you’ve done, it has been really helpful. My only complaint is that it doesn’t have an eBook format so I can read it on my Kindle. Besides that, great work.</span></p>
</div></div></blockquote><div>Yes, that complaint has been levied on more than one occasion. We've been imploring Packt to rectify the situation. We'll keep you posted on the status.</div><div><br></div><div>-MC</div>
<div><br></div></div>