[reSIProcate] DUM state machine

[Steve Robichaud]

The only reason that I was interested in the Ack was to know for sure 
that the UAS state is 'Connected'.  When the 200 is sent with accept() 
the UAS state transitions to UAS_Accepted, and until the state goes 
Connected (on  the Ack) you cannot use certain methods such as 
InviteSession::requestOffer().  The reason... an automated B2BUA that 
may be using reinvites.

Steve

-----Original Message-----
From: Jason Fischl
Sent: 20/11/2005 12:33 PM

>I'm still not clear on why anybody cares when the ACK is received. The
>only case where the ACK is relevant to the application is where the
>answer is carried in the ACK and in this case onAnswer will be called.
>
>On 11/18/05, Scott Godin <slgodin at icescape.com> wrote:
>  
>
>>Sticking with the "no changes to current apps" philosophy.  Considering
>>that onAckReceived doesn't really make sense - since this would not be
>>called in the case when the ACK carries an answer - and could be
>>misleading.   I vote for onConnectedConfirmed - seems to make more sense
>>to me then onConnectReturn.  : )
>>    
>>