[SIPForum-discussion] [Sip-implementors] retrying servers in the SRV response:draft -ietf-sip-srv-06.txt

[Manpreet Singh]

Ok, so any 5xx, the client should try right? It simply said 503 so I was
wondering. Also the retry mechanism using SXRV for SIP thing is really
handled at the stack level and not the application level right?

Manpreet 

-----Original Message-----
From: Sanjay Sinha (sanjsinh) [mailto:sanjsinh at cisco.com] 
Sent: Friday, August 04, 2006 6:30 PM
To: Manpreet Singh; discussion at sipforum.org
Cc: sip-implementors at cs.columbia.edu
Subject: RE: [Sip-implementors] retrying servers in the SRV
response:draft-ietf-sip-srv-06.txt

This draft is RFC 3263.
Also I think the client would try other hosts for error responses unless
error response indicates a global failure, like 6XX.

Sanjay

-----Original Message-----
From: sip-implementors-bounces at cs.columbia.edu
[mailto:sip-implementors-bounces at cs.columbia.edu] On Behalf Of Manpreet
Singh
Sent: Friday, August 04, 2006 4:57 PM
To: discussion at sipforum.org
Cc: sip-implementors at cs.columbia.edu
Subject: [Sip-implementors] retrying servers in the SRV
response:draft-ietf-sip-srv-06.txt
Importance: High

Hi
 
I read the draft for locating SIP servers using SRV and there is a section
on how to retry in the event of failure. The only thing mentioned there is
if the client gets a 503 or there are transport level timeouts. Now is that
the only implementation? Can the client implement retries based on certain
4xx or 5xx responses? I was testing a case where I was sending 500 and the
client wont retry but for 503 it would.
So is this really the final implementation or its really client specific.
 
Thanks
 
Manpreet
_______________________________________________
Sip-implementors mailing list
Sip-implementors at cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20060804/f3d316e2/attachment-0005.html>