This doesn't exactly answer your question, but RFC 3312 says that the UAS should delay alerting the user until all mandatory preconditions are met. There are no mandatory preconditions in the case you describe - only optional ones. An optional precondition means that the UA should attempt to satisfy the preconditions, but the call should continue regardless of whether it's met. So there's really no reason for the UAS to suspend session establishment and wait for the UAC to send a confirmation status.
Now, if you change the "qos optional" to "qos mandatory" in your example, then you have a good question. RFC 3312 says the UAS should suspend session establishment (i.e. not alert the user) until the precondition is met, but doesn't say how long the UAS should wait to receive the confirmation status from the UAC. I'm also not aware of any timers in RFC 3261 that would be relevant here. Both the client and server invite transactions would be in the "Proceeding" state. So, I guess it would up to your application to determine how long it's willing to wait in the proceeding state. -- Gary Cote www.awardsolutions.com _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
