Gentlemen,
here is a patch implementing the outbound proxy (with "force" flag) at
the AmSipDialog level following the "guidance of the bible" (RFC3261).
Though it is not tested, please have a close look at it (especially the
code for AmSipDialog::send_request()) and tell me if this could satisfy
your needs.
-Raphael.
PS: I haven't ported the code for the SIPRegistrarClient yet... please
forgive me!
On 20.04.10 15:32, Juha Heinanen wrote:
Raphael Coeffic writes:
> This means that the intended behavior is:
> 1. send the first request to the outbound proxy (if existing).
> 2. send subsequent requests using the route-set and standard behavior
> (means: no outbound proxy there).
>
> Forcing the proxy is an option, but should definitely not be the default
> behavior. At least not if we claim to have some level of compliance with
> standards ;-)
raphael,
i agree that standard behavior is to follow route set, but for security
reasons, it makes sense to have an option for force ob also for inbound
requests.
-- juha
_______________________________________________
Semsdev mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/semsdev
