On 10/11/06, Sumin Seo <[EMAIL PROTECTED]> wrote: > > 1. Do you mean that UA can't initate INVITE client transaction if > there is uncompleted or uncomfimed INVITE server transaction? > For example, if there is uncompleted or uncomfimed INVITE server > transaction, UA can't initiate re-INVITE for session timer request?
That's correct. Have you read RFC 3261, Section 14.1? It's pretty clear. 2. Even though B2B has INVITE server transaction related with UA1, > there is no pending transaction between B2B and UA2. What happen in > UA2 if B2B sends 491 although all previous INVITE transactions between > B2B and UA2 completed? Again, RFC 3261, Section 14.1 is pretty clear about how the UAS should react to the 491 Request Pending response. Which part didn't you understand? I guess an alternative to the 491 Request Pending response would be a 500 Internal Server Error response, with a Retry-After header telling the UA when to try the re-INVITE again. - g _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
