<div dir="ltr">hmmm seems I had to play further with <div><br></div><div>sip_route_uri<br></div><div>and </div><div>sip_invite_req_uri<br></div><div><br></div><div>to make this work, but it works now..</div><div><br></div><div><br></div><div>I do still wonder if simplify should use the request URI in the Refer-To header instead of what appears to be the SIP To URI.</div><div><br><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 19 February 2015 at 23:12, jay binks <span dir="ltr"><<a href="mailto:jaybinks@gmail.com" target="_blank">jaybinks@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Im bringing up a call ( "Freeswitch node A" ) where im using sip_route_uri to send the call via a specific node in my network "Freeswitch node B".<div><br></div><div>but I also want to get this "Freeswitch Node A" out of the call path after the call is answerd.</div><div>"simplify" works great for this.</div><div><br></div><div>however when I try and simplify a call, that was brought up with a sip_route_uri </div><div>my simplify fails ! :(</div><div><br></div><div>The Refer-To: sent by "FS node A" contains the SIP URI for my call , but has no reference to the details used in sip_route_uri meaning nothing was sent to "Freeswitch node B" </div><div><br></div><div>is this a bug, or am I missing something in the use case of these 2 features ??<span class="HOEnZb"><font color="#888888"><br><div><div><br></div>-- <br><div>Sincerely<br><br>Jay</div>
</div></font></span></div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Sincerely<br><br>Jay</div>
</div>