<div class="gmail_quote">Thank you Ovidiu. I had assumed that the Custom-Headers parameters works only for the initial INVITE request. It works as expected. I have another concern here:<div>I dont want the "100 Trying" response going out to the call initiator because I know that "407" is will obviously come from the "Proxy Opensips". While using t_relay I could have done that using the flags inside the t_relay function. Is it possible to avoid the "100 Trying" somehow when relaying the call in B2B mode?</div>
<div>To be honest, I have a web application which initiates the call and expects a "407" response and then will send the INVITE again with digest credentials. When that application gets the "100 Trying" response, the application gets confused :)</div>
<div>Either I will have to tweak the application to just ignore the 100 response which is little difficult or else find a way to avoid sending 100 response from opensips. Please Help !!</div><div><br></div><div>Thanks in advance.</div>
<div><br></div><div><font color="#888888">--- Jayesh</font><div class="im"><br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Try adding your extra headers to the "cusotm_headers" parameter:<br>
<a href="http://www.opensips.org/html/docs/modules/devel/b2b_logic.html#id250014" target="_blank">http://www.opensips.org/html/docs/modules/devel/b2b_logic.html#id250014</a><br>
<br>
Regards,<br>
Ovidiu Sas<br>
<br>
On Sat, Jul 2, 2011 at 5:46 AM, Jayesh Nambiar <<a href="mailto:jayesh.voip@gmail.com" target="_blank">jayesh.voip@gmail.com</a>> wrote:<br>
> Hi All,<br>
> I have a following situtation:<br>
> Sip-Endpoint --> Opensips B2B (with REFER scenario) --> Opensips Proxy(Using<br>
> Proxy Authorize for Authentication) --> PSTN Gateway<br>
> I need the "B2B Opensips" in between so that it can handle the REFER<br>
> requests properly. The problem is that the "Proxy Opensips" responds back as<br>
> 407 with Proxy-Authenticate header along with the realm and nonce value; but<br>
> the "B2B Opensips" would only send the 407 response to the Endpoint without<br>
> any Proxy-Authenticate header. Thus the call fails. I cannot authorize the<br>
> Sip-Endpoint on the "B2B Opensips" because of the limitations of my<br>
> architecture.<br>
> What I need is, the 407 response gets back to the Sip-Endpoint transparently<br>
> and the response to the same also reaches the "Proxy Opensips" properly, so<br>
> that the proxy authorization becomes successful and the call can go through<br>
> properly.<br>
> Is there something that can be done on the b2b_response route? Any pointers<br>
> or directions in achieving this will be very helpful !!<br>
> Thanks in advance.<br>
> --- Jayesh<br>
><br><br></blockquote></div></div></div>
</div><br>