[reSIProcate] UAS State Issue

[Scott Godin]

To fix this I added a UAS_WaitToOffer state.  I committed modified .dot
state diagrams and changes to the teltel branch.

For now a refers are not queued.  So a refer will be sent regardless of
whether the ACK has been received or not.

Scott

-----Original Message-----
From: Scott Godin [mailto:slgodin at icescape.com] 
Sent: Monday, March 07, 2005 4:08 PM
To: 'jason at iii.ca'; 'derek'
Cc: resiprocate-devel at list.sipfoundry.org
Subject: [reSIProcate] UAS State Issue

For a UAS - In the teltel branch:

When the application calls accept() to send a 200, the onConnected
callback is called.  The time between this callback and receiving the
ACK from the other party, opens up an interval, where you cannot call
provideOffer (or refer), since the state machine is in the UAS_Accepted
state, until the ACK arrives.  

 

This appears to be handled (at lead in the providedOffer) case for
re-Invites, with a WaitingToOffer state.  If provideOffer is called in
UAS_Accepted - we should consider either transitioning to WaitToOffer or
adding a UAS_WaitToOffer state.  

 

Thoughts?

 

 

Scott Godin

Research and Development

Computer Talk Technology

slgodin at icescape.com

905-882-5000 and 'Say my name' or x127