Hi, >>I guess the only current way is to send a BYE in the backward >>direction, but I have a feeling many clients would either >>reject it or release the whole session setup. > >Unfortunately, BYE doesn't quite work. The called UA can't >send BYE until the dialog is established (after the UA has >sent a final response) (per section 15, para. 1),
Correct. I messed up the message directions. >and after a 4xx response has been sent, a dialog doesn't exist, so the UA >can't send a BYE after that. Correct. And, the calling party may not even receive that 4xx, since the forking proxy would "store" it, in order to wait for possible final responses from other forked dialogs. >The UA can get "prompt releas signaling" by accepting the call and then sending an >immediate BYE, but the 2xx will tend to terminate other forks. Yes, and that would be just another hack in order to something that probably COULD be done much easier, but would require some standardization work. Regards, Christer > _______________________________________________ > Sip-implementors mailing list > [email protected] > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
