<br><br><div class="gmail_quote">On Mon, Jul 11, 2011 at 3:26 PM, David Ponzone <span dir="ltr"><<a href="mailto:david.ponzone@ipeva.fr">david.ponzone@ipeva.fr</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style="word-wrap:break-word">Well, I used to think that should be 2 different things.<div>Early media is a way to provide ringing, including custom ringing and custom message without answering the call.</div><div>So it was logical for me to think that it should be possible to pass it from B to A, without flagging leg-B as answered, as it is not.</div>
<div>Is it specific of FS, or is it a general rule ?</div><div><br></div><div>Perhaps Mathieu could solve its issue (going from first route to next one) by using leg_timeout/originate_timeout on each bridge ?</div><div><br>
</div></div></blockquote><div><br></div><div>One of the dangers in this situation is that you don't necessarily know what kind of early media the far end is sending. If you bridge the early media on leg B to leg A then the call is bridged. Are you going to monitor the early media on leg B and then unbridge if you get something you don't like? Not likely.</div>
<div><br></div><div>If you cannot rely on early media then it's wise to ignore it and handle ringback on your own. Unless, of course, there's a third option that someone else has to offer.</div><div><br></div><div>
-MC</div></div>