On Mon, Aug 29, 2016 at 05:23:46PM +0200, Daniel-Constantin Mierla wrote:
> can you try to change the module exports for uac module and allow
> uac_auth() for REQUEST_ROUTE or BRANCH_FAILURE_ROUTE (not sure right now
> by heart which one is required) and see if it actually works. Then the
> flags c
Hello,
can you try to change the module exports for uac module and allow
uac_auth() for REQUEST_ROUTE or BRANCH_FAILURE_ROUTE (not sure right now
by heart which one is required) and see if it actually works. Then the
flags can be extended if all ok.
Cheers,
Daniel
On 29/08/16 11:22, Daniel Tryba
On Fri, Aug 26, 2016 at 01:58:57PM +0200, Daniel-Constantin Mierla wrote:
> try to see if it works to do the authentication in the branch failure
> event route. There you can do processing as soon as the 401 arrives --
> it has to be tried to see if uac auth works fine there, if not probably
> need
Hello,
try to see if it works to do the authentication in the branch failure
event route. There you can do processing as soon as the 401 arrives --
it has to be tried to see if uac auth works fine there, if not probably
needs some tuning.
Cheers,
Daniel
On 25/08/16 15:42, Daniel Tryba wrote:
>
Trying to implement a way to authenticate outgoing INVITEs to endpoints
that need/want to. uac_auth in the initial failure route works fine when
there is only 1 registered user to send the INVITE to. But with at least
2 locations are available and 1 accepts the INVITE without
authentication, the 40
