|
Hello all,
I'm pretty sure someone has already had
thise same problem. I'd like to know how can I deal (and delay) the timeout
triggered by most clients when an INVITE is sent. The RFC 3261 says the UAC
behavior should be to set timeout (for which the value is usually
announced in an Expires field in the INVITE request) until a non-provisory
response is received (usually 200 OK or 488... I think).
In clients like Windows Messenger the
timeout is not stated in the INVITE Expires field but does expire after 120
seconds. Is there anyway to postpone this timeout within the client to enabled
delayed INVITE responses (like when the INVITE gets queued)?
I've seen some descriptions of the
semantics of provisory responses like the 182 Queued but it seems
those have only effect in the proxies timeouts and not the client, is that
so? I can't belive there is no clean way to enable a SIP client to support
queued sessions...
I'd like to thank you for any help in
advance.
Best regards and happy codding,
Tiago Dias
|
_______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
