[OpenSIPS-Users] Configure OpenSIPS to use USER based gateway

Bogdan-Andrei Iancu bogdan at opensips.org
Tue Apr 4 09:12:20 EDT 2017


Thank you Sagar,

I see you use topology hiding - could you please disabled the dialog and 
TH support for the call and try it again ?

Regards,

Bogdan-Andrei Iancu
   OpenSIPS Founder and Developer
   http://www.opensips-solutions.com

OpenSIPS Summit May 2017 Amsterdam
   http://www.opensips.org/events/Summit-2017Amsterdam.html

On 04/04/2017 03:39 PM, sagar malam wrote:
>
> Yes.
>
> Please find attached file.
>
> On Tue, Apr 4, 2017 at 5:06 PM Bogdan-Andrei Iancu 
> <bogdan at opensips.org <mailto:bogdan at opensips.org>> wrote:
>
>     Whatever headers are added in failure route are visible only to
>     that particular branch, they are are not inherited by any future
>     branch. So, if you do uac_auth() from failure route only, I do not
>     see how the Auth hdr may propagate to other branch.
>
>     Do you have a pcap or txt capture for the call flow ?
>
>     Regards,
>
>     Bogdan-Andrei Iancu
>        OpenSIPS Founder and Developer
>        http://www.opensips-solutions.com
>
>     OpenSIPS Summit May 2017 Amsterdam
>        http://www.opensips.org/events/Summit-2017Amsterdam.html
>
>     On 04/04/2017 01:54 PM, sagar malam wrote:
>>     Hello Bodgan,
>>
>>     Thanks for reply.
>>
>>     Do you use the uac_auth() (which add the Auth hdr) only from
>>     failure route, right ?
>>     Yes exactly.
>>
>>     Also , does your INVITE have any already populated Auth hdr (when
>>     received by OpenSIPS) ?
>>     No,we are adding it using uac_auth function.
>>
>>
>>     On Tue, Apr 4, 2017 at 4:18 PM Bogdan-Andrei Iancu
>>     <bogdan at opensips.org <mailto:bogdan at opensips.org>> wrote:
>>
>>         Hello,
>>
>>         Do you use the uac_auth() (which add the Auth hdr) only from
>>         failure route, right ?
>>
>>         Also , does your INVITE have any already populated Auth hdr
>>         (when received by OpenSIPS) ?
>>
>>         Best regards,
>>
>>         Bogdan-Andrei Iancu
>>            OpenSIPS Founder and Developer
>>            http://www.opensips-solutions.com
>>
>>         OpenSIPS Summit May 2017 Amsterdam
>>            http://www.opensips.org/events/Summit-2017Amsterdam.html
>>
>>         On 04/03/2017 11:26 AM, sagar malam wrote:
>>>         Hello,
>>>
>>>         I am trying to configure OpenSIPS to support
>>>         Username-password based authentication Gateway.
>>>
>>>         Hence i am using uac_auth function to generated
>>>         Authorization header before relaying INVITE packet to gateway.
>>>
>>>         I am facing issue in removing old Authorization header and
>>>         append new Authorization header in Failure route before
>>>         trying next gateway.
>>>
>>>         OpenSIPs is not detecting old Authorization headers but when
>>>         i see sip trace ,headers are present.
>>>
>>>
>>>         Script flow is something like this :
>>>         request_route{
>>>            select_gateway
>>>           relay_route
>>>         }
>>>         relay_route{
>>>         t_relay
>>>         }
>>>
>>>         failure_route{
>>>         Remove old Authirization header
>>>          on,407 or 401,Add Authorization header using uac_auth
>>>         select_next gateway
>>>         relay_route
>>>         }
>>>
>>>         In Users mailing list i read that headers added in request
>>>         route cannot be removed later,hence i need to add headers
>>>         during branch route but uac_auth function works only in
>>>         failure route.
>>>
>>>         Please help me on this.
>>>
>>>         Thanks in advance
>>>
>>>
>>>
>>>         _______________________________________________
>>>         Users mailing list
>>>         Users at lists.opensips.org <mailto:Users at lists.opensips.org>
>>>         http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20170404/0112eba7/attachment-0001.html>


More information about the Users mailing list