|
1. There are
two cases - based on whether offer1 is carried in INVITE or 200OK. 2. In any case INVITE or Re-INVITE should be differentiated/identified as any other transaction. 3. It's a race. Rest of the flow is as follows - 1. Callee will retransmit 200OK (INVITE). 2. Caller will retransmit ACK (INVITE). 3. Callee will retransmit 200OK (Re-INVITE). 4. Caller will retransmit ACK (Re-INVITE). 4. It's an implementation issue - UAC may wait for some timer [till UAS is in Moratorium state]. UAC may delink subscriber behaviour (pressing some key on mobile let's say for hold) from sending Re-INVITE to avoid such race. RFC 5407 is what you are looking for. Dushyant P S Dhalia Rancore Technologies, Gurgaon, INDIA zabi wrote: Caller (A) Callee(B) | INVITE | |---------------------------> | | 200 OK | |<---------------------------- | | ACK(dropped) | | ------------x-> | | re-INVITE | | ----------------------------->| | 200 OK | | (retx for 1st Invite) | |<------------------------------| -- "When work is a pleasure, life is a joy! When work is duty, life is slavery." |
<<attachment: dushyant_dhalia.vcf>>
_______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
