Many thanks! This answers the question perfectly. My head is held in shame since I've not spent the time to read Section 16 carefully because I'm working on a UA only ;)
FM ------------------------------------------------ On Fri, 17 Sep 2004 20:21:16 +0530, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Hi Frank, > > Response Inline... > > ----- Original Message ----- > From: <[EMAIL PROTECTED]> > To: "Markus Hofmann" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Friday, September 17, 2004 6:53 PM > Subject: RE: Fwd: Re: [Sip-implementors] Call flow for forking proxy > > > > > > > > > > Thanks! > > > > Let me be a bit more specific. Here's an example call flow I'm seeing: > > > > > > UA Proxy > > | INVITE | > > |------------------------>| > > | 100 Trying | > > |<------------------------| > > | 180 Ringing: To tag=A | > > |<------------------------| > > | 180 Ringing: To tag=B | > > |<------------------------| > > | 180 Ringing: To tag=C | > > |<------------------------| > > | 200 OK: To tag=C | > > |<------------------------| > > | ACK: To tag=C | > > |------------------------>| > > | | > > > > The question I have is what about the dialogs for A and B? Are you > supposed to send a CANCEL for each? Does the ACK for C implicitly tell the > proxy to CANCEL A and B? > > When a forking proxy receives a 200 OK from C, the proxy will also generate > CANCEL for A and B( refer 16.7.10 in RFC 3261). The UA will simply update > its dialog state with the received 200 from C and connect with C. There may > be a scenario wherein the UA may receive multiple 200 OK (a CANCEL and 200 > OK racearound), for which, the UA will send an ACK for the second 200 OK and > subsequently a BYE for the same dialog. > > > > > > > Thanks, > > FM > > > > Regards, > -Sridhar > Mistral Software > > > > > Frank W. Miller, Ph.D. > > Cornfed Systems, LLC. > > www.cornfed.com > > 410-404-8790 > > > > > > ------------------------------------------------ > > On Fri, 17 Sep 2004 10:44:56 +0200, "Markus Hofmann" <[EMAIL PROTECTED]> > wrote: > > > > > "Markus Hofmann" <[EMAIL PROTECTED]> schrieb am 17.09.04 10:44:22: > > > > > > > > > > > > Hi Frank, > > > > > > > > I hope it will be readable. > > > > > > > > |------ >INVITE > [EMAIL PROTECTED] > > > > |<----- 302 > > > > |-------> ACK > > > > INVITE sip:[EMAIL PROTECTED] --------| > > > > |-------> INVITE > [EMAIL PROTECTED] > > > > |<------- 200 OK > > > > <--200 OK---| > > > > ----ACK----->| > > > > |----------->ACK > > > > > > > > Greeting > > > > > > > > Markus > > > > > > > > "Frank W. Miller" <[EMAIL PROTECTED]> schrieb am 17.09.04 06:43:13: > > > > > > > > > > > > > > > Greetings, > > > > > > > > > > Can anyone point me at a concise call flow for a User Agent that > > > > > initiates a session through a forking proxy? > > > > > > > > > > Thanks in advance, > > > > > FM > > > > > > > > > > Frank W. Miller > > > > > Cornfed Systems, LLC > > > > > www.cornfed.com > > > > > > > > > > _______________________________________________ > > > > > Sip-implementors mailing list > > > > > [EMAIL PROTECTED] > > > > > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > > > > > > > > > > > > > > > > > ____________________________________________________ > > > Aufnehmen, abschicken, nah sein - So einfach ist > > > WEB.DE Video-Mail: http://freemail.web.de/?mc=021200 > > > > > > _______________________________________________ > > > Sip-implementors mailing list > > > [EMAIL PROTECTED] > > > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > > > > > _______________________________________________ > > Sip-implementors mailing list > > [EMAIL PROTECTED] > > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > > _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
