> > Consider the following scenario in the context of Fig 10 of bis-04: > > > > UAC sends INVITE and receives 1xx from UAS, that means UAC is in Call > > Proceeding state. While in this state, if UAC doesn't receive > > any other > > response from UAS, how long UAC SHOULD wait before giving up? > > Should it be > > client defined timeout interval or 32s or anything else? > > It is implementation specific. Some products > allow the call stay in ringing state for > 30 seconds; others allow the call-leg to stay > in ringing state indefinitely. > > For products that allow for long call setup > times after a 18x has been received with a tag, > an INFO message without a body potentially > can be sent to test if the leg is still alive. > A 481 would be returned if the call leg is no > longer established. Uh, I certainly wouldn't rely on this to determine anything. Maybe it's just me, but I am unaware of bis-04, or anywhere else for that matter, specifying this behaviour. - Jo. _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
