Jonathan Lennox wrote:
I wouldn't suggest that you try to make receiving the ACK part of the CFW state machine, since it's not at the same state machine layer as the offer/answer exchange, and there are cases where it isn't present (e.g. delayed offer, or reliable provisional responses). I'm not sure I follow what the issue is with the race between the SDP answer and the SYNC, anyway. The endpoint receiving both may need to wait until it gets the SDP answer before it can respond to the SYNC, but is this a problem?
Hello,I would prefer waiting for the SIP ack before sending the CF sync - rather than having to block the CF sync if the 200 OK hasn't been received. It will also define the sequence more tightly (eg implementations may choose to wait for the SIP ack anyway).
Cheers
John