<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>6 dec 2012 kl. 11:44 skrev Peter Dunkley <<a href="mailto:peter.dunkley@crocodile-rcs.com">peter.dunkley@crocodile-rcs.com</a>>:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta http-equiv="Content-Type" content="text/html; CHARSET=UTF-8">
<meta name="GENERATOR" content="GtkHTML/4.4.4">
<div>
Hi Olle,<br>
<br>
I haven't had any time for the last few months to work on outbound. So there is some module boiler plate and a set of notes (attached) at the moment and not much more.<br>
<br>
I have a requirement for outbound myself for early next year, so will be picking it up again soon, but there is little to no chance of it making it into Kamailio 3.4.<br>
<br>
One thing that would speed up the development of outbound is if someone else (who knows about the internals of the registrar and usrloc modules) took on the tasks relating to those. These are basically:
<ul>
<li>Handle multiple registrations with same instance ID but difference reg-id (may already be supported)
</li></ul></div></blockquote>It needs to be handled properly in parallell and serial forking, which I have not seen. May have missed it though.</div><div><br><blockquote type="cite"><div><ul><li>Have registrar populate an AVP array (specified as a modparam), ordered by reg-id, when a lookup() is performed - similar to dispatcher (but don't break parallel and serial forking) - set $du to first contact in the AVP array.
</li></ul></div></blockquote>Right.<br><blockquote type="cite"><div><ul><li>New API (lookup_next_dest()) in registrar that allow you to work through the set in order if a 430 is returned (API needs to remove failed contacts from the location table) - again, similar to dispatcher
</li></ul>
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.
</li></ul>
<br>
This would allow me to focus on the Edge server behaviour, which involves changes to path, rr, a new outbound module, and some configuration examples (for edge and proxy/registrar).<br></div></blockquote>And new response codes. </div><div><br></div><div>I do long for an eventroute for broken TCP connections from clients.</div><div><br></div><div>Thanks for the feedback. I guess we have to visit Berlin and feed an unspecified group of developers with Bratwurst and Beer to get some help here... :-)</div><div><br></div><div>/O<br><blockquote type="cite"><div>
<br>
Regards,<br>
<br>
Peter<br>
<br>
<br>
On Thu, 2012-12-06 at 09:43 +0100, Olle E. Johansson wrote:
<blockquote type="CITE">
<pre>Peter,
What's the current status of the outbound support? Which branch is it?
Can we do anything to help to get this into the coming release?
/O
_______________________________________________
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%">
<tbody><tr>
<td>
<pre>--
Peter Dunkley
Technical Director
Crocodile RCS Ltd
</pre>
</td>
</tr>
</tbody></table>
</div>
<span><outbound_design.txt></span>_______________________________________________<br>sr-dev mailing list<br><a href="mailto:sr-dev@lists.sip-router.org">sr-dev@lists.sip-router.org</a><br>http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev<br></blockquote></div><br></body></html>