[sr-dev] alias_contact()/handle_alias() ready for testing
Klaus Darilion
klaus.mailinglists at pernau.at
Mon Nov 9 13:26:11 CET 2009
Juha Heinanen schrieb:
> Klaus Darilion writes:
>
> > It is not possible to detect if a reply comes from a proxy or not.
>
> klaus,
>
> yes, but the two via test tells that ua is not taking directly to this
> sr instance and i thus don't need to care about it.
I think the "reply" problem needs to be solved using the registrar NAT
bflag. If NAT flag is set for callee, activate a reply-route with
add_alias() (can be done per branch).
klaus
>
> > could add the alias anyway and handle the problem in "handle_alias": If
> > alias parameter is removed from RURI (in-dialog request), set $du only
> > if it was not already set by loose_route().
>
> i first thought to add the $du test, but looks like the via test makes
> it unnecessary. however, loose_route() may be key to solving the reply
> problem: if loose_route() sets $du, it means that next hop is another
> proxy. then it is possible to set TO_PROXY flag and test it
> onreply_route. right?
>
> > I think the functions are great to have, but would like different naming
> > (either have "alias" always at the beginning or at the end of the
> > function name).
> >
> > e.g: add_alias(), handle_alias()
>
> i can change the names. thanks for helping out on this.
>
> -- juha
>
>
More information about the sr-dev
mailing list