<div>Yes, thanks for confirming, that it doesn't matter which leg refer is coming from, now the question is :</div><div><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
<destination><br> <value type="header">Refer-To</value><br></destination></blockquote><div> </div></div><div>What is the purpose of the above block when there is no change in the generated INVITE !! I mean isn't it supposed to get the URI of the C party from this header and send out invite !</div>
<div><br></div>Also I just looked at b2b_request and it seems like it'll help me alot , however, I can detect a REFER request in that route, there I added a custom Header and that is nowhere to be found in siptraces, also changing anything in my SIP message doesn't work either. Is this correct behaviour for this route/module?<div>
<br><div>Thanks alot for replying to my noobish questions. I really appreciate.</div><div><br><br><div class="gmail_quote">On Thu, Aug 25, 2011 at 12:16 AM, Anca Vamanu <span dir="ltr"><<a href="mailto:anca.vamanu@gmail.com">anca.vamanu@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi Sammy,<br><br><div class="gmail_quote"><div class="im">On Wed, Aug 24, 2011 at 11:54 AM, Sam Govind <span dir="ltr"><<a href="mailto:govoiper@gmail.com" target="_blank">govoiper@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hey Anca, <div><br></div><div>Please tell me why can't I capture the "Refer-To" header coming from B-leg of the call ? earlier in your reply you said its for A-leg. I can't seem to have it working for B-leg.</div>
<div><br></div></blockquote></div><div>It doesn't matter if it is A or B. <br>You can take the Refer-To header in the b2b_request route: <a href="http://www.opensips.org/Resources/B2buaTutorial#toc19" target="_blank">http://www.opensips.org/Resources/B2buaTutorial#toc19</a>.<br>
<br>Regards,<br><font color="#888888">Anca<br><br> <br></font></div><div><div></div><div class="h5"><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
<div></div><div>Thanks,</div><div>Sammy</div><div><div>
</div><div><div><br><br><div class="gmail_quote">On Tue, Aug 23, 2011 at 9:21 AM, Sam Govind <span dir="ltr"><<a href="mailto:govoiper@gmail.com" target="_blank">govoiper@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thanks Anca for the explanation, but can you just tell me if what I'm trying to do here is possible with B2BUA or not? if you are saying that A side Refer-to header will be read then obviously I need to take care of the client1 and server1 parameters accordingly.<div>
<br></div><div>I've a FreeSwitch as Media-Server to play some IVR to User-A and collect DTMF.OpenSIPS will be acting as B2BUA for this call.</div><div><br></div><div>Once DTMF are collected, Media-Server Refers the call back to OpenSIPS</div>
<div>At OpenSIPS I need to do some accounting on the collected DTMF (I may need more than one XML script to get the control back)</div><div>If I get OK from AAA then Send INVITE to the DTMF destination</div><div>else Send INVITE to Media-Server to play some Message.</div>
<div><div></div><div>
<div><br></div><div><br><div class="gmail_quote">On Tue, Aug 23, 2011 at 12:22 AM, Anca Vamanu <span dir="ltr"><<a href="mailto:anca.vamanu@gmail.com" target="_blank">anca.vamanu@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Sam,<br><br>Seems that you have a bad understanding of what the Refer scenario must do. Let's say A and B are in a call. When a Refer message is received from A, the B2B will terminate the call leg with A and will try connect B and the URI in the Refer-To header. The connection is done indeed by sending first an Invite without any SDP to B and doing a late SDP negotiation in 200OK and ACK.<br>
So what you observed, is in fact the wanted behavior.<br><br>Regards,<br>Anca Vamanu<br><br><div class="gmail_quote"><div><div></div><div>On Mon, Aug 22, 2011 at 1:07 PM, Sam Govind <span dir="ltr"><<a href="mailto:govoiper@gmail.com" target="_blank">govoiper@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div></div><div><div class="gmail_quote"><br><p class="MsoNormal">Hello,</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">I’ve been trying to configure the <a href="http://www.opensips.org/Resources/B2buaTutorial#toc15" target="_blank">REFER scenario</a>
but so far no luck. I've successfully called the scenario on initial INVITE and seems like I'm getting B2B responses and replies but when I see sip traces the following two anomalies exist.</p><p class="MsoNormal">
<br></p><p class="MsoNormal">1- Refer-To header value is not used anywhere in new INVITE</p><p class="MsoNormal">2- SDP is not sent in new INVITE.</p><p class="MsoNormal"><br></p><p class="MsoNormal">Please help.</p><p class="MsoNormal">
</p>
<p class="MsoNormal"><a name="131fd3949bac570b_131fb0079267b94c_131f4df79a4411c0_131f2f28cefdb84a_131f0f5e857c0ed3_131f0f26eaba17dd__MailAutoSig"><span style="font-size:10.0pt">Best Regards,</span></a></p>
<p class="MsoNormal"><span><b><span style="color:#1F497D">Sam</span></b></span><span><b><span style="color:#1F497D"></span></b></span></p>
</div><br>
<br></div></div>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div></div></div><br>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br></div></div>