RFC 4320 updates RFC 3261; thus, it would require ignoring the "MUST NOT" if decide to quickly send the 100 response.
Section 4.1: "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." > c) Do you think we can have it ? > > 1815 50.987832 10.48.4.2 10.52.39.194 SIP/SDP > Request: UPDATE sip:10.52.39.194:5060;transport=UDP, with session > description > 1828 50.987835 10.52.39.194 10.48.4.2 > SIP/SDP > Status: 100 trying > . > 3.5 seconds later > . > . > 1828 53.987731 10.52.39.194 10.48.4.2 SIP/SDP > Status: 200 OK, with session description _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
