From: "Roman Shpount" <[EMAIL PROTECTED]> How would you deal with re-Invite collisions between MOH server and the UA that you placed on hold? The normal re-Invite back-off will not work properly if it was your UA that established the call to the held UA (otherwise you can just use Retry-After header). You probably need a section or at least some discussion on what happens in that case.
It seems to me that since the executing UA is passing re-INVITEs and their responses through itself, any re-INVITE collision will result in 491 responses from the held UA and the MoH source. (If this is not so, could you diagram an example?) It's true that the back-off algorithm won't work as well as usual, but I expect that the collision will always be resolved eventually. P.S. From my experience payload type restriction is really unnecessary and will just complicate compliant UA. What do you mean? Dale _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
