> For non-invite transaction , example for message method > 200 ok response is receiving after 500ms. So client > starts to re-transmit the MESSAGE method before response > is reaching. Is it a valid behavior otherwise client has > to wait more than 500ms for receiving a response.
Yes; it may take more than 500ms to receive a final response for non-invite transactions and T1 defaults to 500ms. Additionally, RFC 4320 section 4.1 imposes restrictions concerning the 100 response and other 1xx responses. "An SIP element MUST NOT send any provisional response with a Status- Code other than 100 to a non-INVITE request. An SIP element MUST NOT respond to a non-INVITE request with a Status-Code of 100 over any unreliable transport, such as UDP, before the amount of time it takes a client transaction's Timer E to be reset to T2." _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
