You should fix your application to properly handle 100 Trying. Regards, Ovidiu Sas
On Mon, Jul 4, 2011 at 7:08 AM, Jayesh Nambiar <[email protected]> wrote: > 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: > 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? > 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 :) > 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 !! > Thanks in advance. > --- Jayesh > >> >> Try adding your extra headers to the "cusotm_headers" parameter: >> http://www.opensips.org/html/docs/modules/devel/b2b_logic.html#id250014 >> >> Regards, >> Ovidiu Sas >> >> On Sat, Jul 2, 2011 at 5:46 AM, Jayesh Nambiar <[email protected]> >> wrote: >> > Hi All, >> > I have a following situtation: >> > Sip-Endpoint --> Opensips B2B (with REFER scenario) --> Opensips >> > Proxy(Using >> > Proxy Authorize for Authentication) --> PSTN Gateway >> > I need the "B2B Opensips" in between so that it can handle the REFER >> > requests properly. The problem is that the "Proxy Opensips" responds >> > back as >> > 407 with Proxy-Authenticate header along with the realm and nonce value; >> > but >> > the "B2B Opensips" would only send the 407 response to the Endpoint >> > without >> > any Proxy-Authenticate header. Thus the call fails. I cannot authorize >> > the >> > Sip-Endpoint on the "B2B Opensips" because of the limitations of my >> > architecture. >> > What I need is, the 407 response gets back to the Sip-Endpoint >> > transparently >> > and the response to the same also reaches the "Proxy Opensips" properly, >> > so >> > that the proxy authorization becomes successful and the call can go >> > through >> > properly. >> > Is there something that can be done on the b2b_response route? Any >> > pointers >> > or directions in achieving this will be very helpful !! >> > Thanks in advance. >> > --- Jayesh >> > >> > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
