Hi,

thanks for your response. It's like that how I handle it currently but some "500 Internal server error" from freeswitch will result, that the message is send to all the other freeswitch server, too. They will of course respond in the same way than the first does. All the freeswitch server should have the same version and dialplan logic.

Best regards, Bernhard

-----Ursprüngliche Nachricht----- Von: kaiserbock2@googlemail.com [mailto:kaiserbock2@googlemail.com] Im Auftrag von Carsten Bock Gesendet: Donnerstag, 13. Januar 2011 11:39 An: Bernhard Suttner Cc: sr-users@lists.sip-router.org Betreff: Re: [SR-Users] Dispatcher Setting

Hi Bernhard,

that is simply up to you. But for my production setups so far, i used to catch 408, 5xx and 6xx. - 408 of course, it is a timeout (others were always valid responses in my case) - 5xx is, according to the RFC, a server failure, so that particular server cannot process the request. - 6xx is, according to the RFC, a global failure, a definite answer about the destination.

Actually, if you take the RFC seriously, you should not disable based upon a 6xx response, since if it is implemented correctly, no-one can answer the question, not only the choosen destination. However, many network components do not take this too seriously, so that was a valid "failed" answer for a system

Kind regards, Carsten

2011/1/13 Bernhard Suttner bernhard.suttner@winet.ch:

Hi,

I am using the Dispatcher module to load-balance the calls to several freeswitch servers.

On which responses within the failure_route should be a fallback to another server (dst_next_dst())? I am sure, that on a 408 response there should be a fallback but whats about other 4XX responses and 5XX or 6XX?

Thanks in advance.

Best regards, Bernhard Suttner

---

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users