The hallowed RFC says:
--
8.2.6.1 Sending a Provisional Response
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.
--
Is this something that is actually followed in practise?
What if I have a registrar that must do a lengthy database dip across a
WAN link to find user-specific authentication information for a REGISTER
request? My tendency has been to issue a 100 Trying for the REGISTER in
order to prevent UAC retransmissions of the request, because processing
the request can sometimes take as long as 2-3 seconds.
Is this something I should not do in case other SIP stacks do not quite
understand the relevance of a provisional response to a REGISTER
transaction per the above recommendation?
Thanks,
-- Alex
--
Alex Balashov
Evariste Systems
Web : http://www.evaristesys.com/
Tel : (+1) (678) 954-0670
Direct : (+1) (678) 954-0671
Mobile : (+1) (706) 338-8599
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
