2009/5/4 hanifa.mohammed <[email protected]>: > All, > > Should Expires header be startd for re-Invite? > > Expires header in initial INVItE helps to avoid the race condition of > infinite waiting since transaction > stops timer B, on receiving the first 1xx. The same can happen for reINVITE > also. > > If Expires can be started, should CANCEL be sent for reINVITE when it > fires?
This CANCEL will stop the re-INVITE transaction, but the call would remain active, so I expect sending CANCEL would be valid. For example, after the establishment of an audio call, the caller/callee could send a re-INVITE to add video session in that call. The receiver UA could ask the user for confirmation on it, so it could take long time until the user (human) accepts/rejects the re-INVITE. During that time, the sender could cancel the re-INVITE by sending a CANCEL. It sounds 100% valid for me. -- Iñaki Baz Castillo <[email protected]> _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
