<!-- Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please use this template only for feature requests.

If you have questions about using Kamailio or related to its configuration file, ask on sr-users mailing list:

* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

If you have questions about developing extensions to Kamailio or its existing C code, ask on sr-dev mailing list:

* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev

Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot the issue.

If you submit a feature request (or enhancement) add the description of what you would like to be added.

If there is no content to be filled in a section, the entire section can be removed.

You can delete the comments from the template sections when filling.

You can delete next line and everything above before submitting (it is a comment). -->

### Description

All ips destination of DNS Failover are tried only if either no response or 503 response. I woud like to try others ips when receiving code other than 503 response (example when receiving 408 from a previous one).

<!-- Explain what you did, what you expected to happen, and what actually happened. -->

### Expected behavior

#### Actual observed behavior

#### Debugging Data

``` None ```

#### Log Messages

<!-- Check the syslog file and if there are relevant log messages printed by Kamailio, add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site). -->

``` None ```

#### SIP Traffic

<!-- If the issue is exposed by processing specific SIP messages, grab them with ngrep or save in a pcap file, then add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site). -->

``` obvious ```

### Possible Solutions

A possible solution will be to modify the reply_received function of tm's t_reply.c file.

``` int reply_received( struct sip_msg *p_msg ) {

} ```

<!-- If you found a solution or workaround for the issue, describe it. Ideally, provide a pull request with a improvement. -->

### Additional Information

* **Kamailio Version** - output of `kamailio -v`

``` (paste your output here) ```

* **Operating System**:

<!-- Details about the operating system, the type: Linux (e.g.,: Debian 8.4, Ubuntu 16.04, CentOS 7.1, ...), MacOS, xBSD, Solaris, ...; Kernel details (output of `uname -a`) -->

``` (paste your output here) ```