From: Manpreet Singh <[EMAIL PROTECTED]> 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.
The central question is whether the situation suggests that retrying with another server would improve the situation. Clearly, if you cannot contact the server in question, or it returns 503, then your message was not handled. Clearly, 3xx, 4xx, and 6xx responses indicate that the message was "processed according to its contents", and there is no reason to believe that retrying with another server would improve things. (Of course for this judgment, a transport-level timeout should not be treated as a 408.) For 5xx responses, we might analyze the situation: 500 Server Internal Error - Since we have no information about why the server failed, retrying with another server might be useful. 501 Method Not Implemented - Retrying is probably not useful, since alternative servers are likely to be the same software, and fail in the same way. 503 Service Unavailable - Clearly, retrying might be useful. 504 Server Time-out - Similar to 500, the server handling a retry might access a different external server. 505 Version Not Supported - Similar to 501. 513 Message Too Large - Similar to 501. Dale _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
