The other thing to consider within the "flow switching part" is the ability to "provide a limited version of a STUN server on the same interface and UDP port" as SIP.<div><br></div><div>That sounds like heavy going. Would it be doable within Kamailio? </div>
<div><br></div><div>I think this is a great RFC so would be happy to help with testing. I am working with a handset manufacturer to implement this now and they have caught up Kamailio on reg-id / sip.instance and are now looking for an SBC with which to test the flow-switching part. </div>
<div>
<div><br></div><div>Wondering if a bounty would help?</div><div><br></div><div><div class="gmail_quote">On 11 July 2012 14:21, Olle E. Johansson <span dir="ltr"><<a href="mailto:oej@edvina.net" target="_blank">oej@edvina.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
11 jul 2012 kl. 15:16 skrev Daniel-Constantin Mierla:<br>
<div><br>
><br>
> On 7/11/12 9:28 AM, Olle E. Johansson wrote:<br>
>> 11 jul 2012 kl. 09:00 skrev Daniel-Constantin Mierla:<br>
>><br>
>>> Hello,<br>
>>><br>
>>> On 7/11/12 4:23 AM, mike wrote:<br>
>>>> dear kamilio developers :<br>
>>>><br>
>>>> i read the kamilio 3.3.0' s new features , it say it support outbound , and i have place to handle reg-id and sip.instance . so , i wonder if the kamilio3.3.0 support RFC5626 now，so that the<br>
>>>> kamilio can be used as a edge proxy . i ask why because i can't find where kamilio add flow-token and path for the register request.<br>
>>> sip.instance and reg-id are handled by the registrar/usrloc modules. Path has to be added by intermediary proxies and it is also handled by registrar module. If the intermediary proxies are kamailio, then adding path is possible via path module.<br>
>> How do you recognize the flows and switch between them in case of failure?<br>
> the flow switching part is not implemented in the module. the sip.instance and reg-id are used to update the location record. Haven't looked at it, but it might be possible to do the switching via config operations.<br>
</div>Cool.<br>
<br>
There has to be a way to easily handle two registrations with the same instance.ID as one contact in all operations in regards to lookup() and forking.<br>
<br>
You want to know that you have more than one flow for the same contact (i.e. the same device). And possibly which flow (which ingres proxy) that is currently active.<br>
<span><font color="#888888"><br>
<br>
/O<br>
</font></span><div><div>_______________________________________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
</div></div></blockquote></div><br></div></div>