Hi,<div><br></div><div>I am working with Jason on implementing the basics for the dialog_2 module.</div><div><br></div><div>I've got a question concerning the concurrently confirmed call scenario. If multiple 200 OKs are received very close to the same time, the new dialog design proposal says we should create a separate dialog_in structure and assign a different DID to it, essentially creating multiple dialog_in structures and multiple dialog_out structures.</div>
<div><br></div><div>Should we not just absorb/ignore the subsequent 200 OK's in this case? I would imagine that if a SIP client received multiple 200 OKs it would ACK the first and ignore the rest as it is effectively already in a call (haven't checked the specs for this yet). So why should we track this in the dialog module? If we just absorb/ignore the subsequent 200 OK the client sending this 200 OK would eventually timeout due to no ACK.</div>
<div><br></div><div>Regards</div><div>Richard.</div><div><br><div><br><div class="gmail_quote">On 7 September 2011 12:50, Jason Penton <span dir="ltr"><<a href="mailto:jason.penton@gmail.com">jason.penton@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Great, thanks Timo.<br><br>We're going to go ahead and see what we can come up with. We are initially thinking of building a new module from scratch, obv. with a lot of reuse from the original dialog module. Our goal then is to get all the correct data structures in place (in and out tables, etc) and being built up correctly using a state machine. Once we're are there we will create a branch for everyone else to help and provide feedback.<br>
<br>We will def. need help when it comes to termination of early dialog, etc - but I think we will get a very good start in.<br><br>Cheers<br><font color="#888888">Jason</font><div><div></div><div class="h5"><br><br><div class="gmail_quote">
On Wed, Sep 7, 2011 at 11:40 AM, Timo Reimann <span dir="ltr"><<a href="mailto:timo.reimann@1und1.de" target="_blank">timo.reimann@1und1.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On 07.09.2011 11:22, Timo Reimann wrote:<br>
> If you find more points to discuss, I (and Iņaki and others possibly<br>
> too) would be glad to share in. In addition, I think that opening up<br>
> another branch for the new dialog module at a rather early stage of<br>
> development might be a good idea in order to get more eyes on the code.<br>
<br>
</div>One more comment: If the new implementation gives you an opportunity to<br>
redo the reference counting portion of the module, I suggest to take it.<br>
Reference counting management has grown into the most complicated part<br>
of the module, and thus can surely benefit from a new, fresh approach.<br>
<div><div></div><div><br>
<br>
--Timo<br>
<br>
_______________________________________________<br>
sr-dev mailing list<br>
<a href="mailto:sr-dev@lists.sip-router.org" target="_blank">sr-dev@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev</a><br>
</div></div></blockquote></div><br>
</div></div><br>_______________________________________________<br>
sr-dev mailing list<br>
<a href="mailto:sr-dev@lists.sip-router.org">sr-dev@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev</a><br>
<br></blockquote></div><br></div></div>