<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/4.4.4">
</HEAD>
<BODY>
Hi Juha,<BR>
<BR>
This is already covered in my earlier email from today:<BR>
<BR>
And for being able to use outbound for NAT traversal on a single server (so no Edge proxies):
<UL>
<LI>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.
</UL>
<BR>
Similar to with the edge server, catching the return code from t_relay() and the failure_route should do all that is needed.<BR>
<BR>
Regards,<BR>
<BR>
Peter<BR>
<BR>
<BR>
On Thu, 2012-12-06 at 13:35 +0200, Juha Heinanen wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
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
<A HREF="mailto:sr-dev@lists.sip-router.org">sr-dev@lists.sip-router.org</A>
<A HREF="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev</A>
</PRE>
</BLOCKQUOTE>
<BR>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
<PRE>
--
Peter Dunkley
Technical Director
Crocodile RCS Ltd
</PRE>
</TD>
</TR>
</TABLE>
</BODY>
</HTML>