Hi Kingston,
RFC 3261 section 8.2.6.1 suggests the following ...
One largely non-method-specific guideline for the generation of
responses is that UASs SHOULD NOT issue a provisional response for a
non-INVITE request. Rather, UASs SHOULD generate a final response to
a non-INVITE request as soon as possible.
When a 100 (Trying) response is generated, any Timestamp header field
present in the request MUST be copied into this 100 (Trying)
response. If there is a delay in generating the response, the UAS
SHOULD add a delay value into the Timestamp value in the response.
This value MUST contain the difference between the time of sending of
the response and receipt of the request, measured in seconds.
So, Its expected that the UAS respond to non-INVITE requests
immediately with preferably a final response and not a
provisional response...
So, I think if the case that you have mentioned takes place I think
Transaction User (TU) must take care and Transaction Layer
shall remain un-noticed ....
Thanks & Regards,
Somesh S. Shanbhag
[EMAIL PROTECTED] wrote: Hi,
If the non-IST doesn't receive any RESPONSE message then what will
happen?
RFC 3261 (in Figure 8: non-INVITE server transaction ) doesn't mention
properly
what will happen if the non-IST doesn't receive any provisional
response/final response.
Regards,
S.Kingston Smiler.
*********************** FSS-Unclassified ***********************
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
-----------------------------------------
SIMPLICITY IS THE BEAUTY.
BE NATURAL LIVE NATURAL.
-----------------------------------------
Somesh S. Shanbhag
Focus Area - VoIP Team (FA-VoIP)
Mascon Global Limited
#59/2, 100Ft Ring Road
Banashankari II stage
Bangalore-560070
Karnataka
INDIA
Website: http://www.mgl.com/
-----------------------------------------
---------------------------------
Do you Yahoo!?
Next-gen email? Have it all with the all-new Yahoo! Mail Beta.
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
