-----Original Message-----
From: Shan Lu [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 09, 2001 10:24 AM
To: [EMAIL PROTECTED]
Subject: Re: [Sip-implementors] UAC state machine fork?
>Are you implying that only 2xx responses create call legs? We had a similar
discussion on
>another thread and could not pinpoint any text in bis-02 to support it.
I haven't gotten around to collecting my thoughts and commenting on that
thread, but here is some of my thinking on this particular issue.
Only a 2xx creates a call leg, in the sense that a call leg is an active
thing which must be hung up if its no longer desired. However, a 18x with a
tag/contact/RR set can effectively create an "early" call leg. It is a call
leg in the sense that the To+tag has been established, and that messages
(like PRACK, COMET, INFO) can be sent on this call leg (meaning they contain
the tag of that leg, and use its route set and CSeq space). It is not a
normal call leg in the sense that if a non-200 final is received, it is
destroyed and no BYE or other action is needed.
I will likely add text to bis-04 discussing this.
-Jonathan R.
-----Original Message-----
From: Vijay Ramachandran Iyer [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 30, 2001 1:31 AM
To: [EMAIL PROTECTED]
Subject: [Sip-implementors] UAC state machine fork?
The states that UAC going to maintain are transcation-specific.
So is it goin to have one FSM which will fork off to create different
instances of the FSM (to receive the responses from other UASs which
may have beenreached due toa forking proxy downstream) depending upon
what responses it gets? To address the problem of how-many-times
to fork, there can always be
an instance of the FSM that can listen and wait for a possible response
from a UAS/proxy downstream ... If none exists, then it can time out.
Am I getting this right or is it totally absurd??
To be clear, you are talking about handling of multiple 200 OK responses to
a single INVITE? Each creates a new call leg at the UAC, which can be
independently BYE'd, re-INVITEd, or whatever. To implement this, you might
choose to clone, or "fork" some call leg state on the receipt of a 200 OK to
create a call leg for it. So, what you are describing is a reasonable thing.
-Jonathan R.
---
Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Ave.
Chief Scientist First Floor
dynamicsoft East Hanover, NJ 07936
[EMAIL PROTECTED] FAX: (973) 952-5050
http://www.jdrosen.net PHONE: (973) 952-5000
http://www.dynamicsoft.com
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
