Hi Juha,
This is already covered in my earlier email from today:
And for being able to use outbound for NAT traversal on a single server
(so no Edge proxies):
* Make registrar able to detect that the top Path-URI for the
contact is actually an interface on the local server, and if it
has an ;ob parameter and a flow token, set $du based on that.
Similar to with the edge server, catching the return code from t_relay()
and the failure_route should do all that is needed.
Regards,
Peter
On Thu, 2012-12-06 at 13:35 +0200, Juha Heinanen wrote:
> Peter Dunkley writes:
>
> > Not sure how this would help with outbound as the proxy/registrar and
> > edge server (with the client connections) will be separate anyway?
>
> i would like to see support also for the case where there is only a
> single server that combines edge proxy and registrar. if i remember
> correctly, this was also in your original requirements list.
>
> -- juha
>
> _______________________________________________
> sr-dev mailing list
> [email protected]
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
--
Peter Dunkley
Technical Director
Crocodile RCS Ltd
_______________________________________________
sr-dev mailing list
[email protected]
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
