Thanks Andrei.<br>I will follow your advise.<br><br>Regards,<br><br><br><div class="gmail_quote">On Wed, Nov 5, 2008 at 5:25 PM, Andrei Pelinescu-Onciul <span dir="ltr"><<a href="mailto:andrei@iptel.org">andrei@iptel.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="Wj3C7c">On Nov 05, 2008 at 17:20, Nuno Ribeiro <<a href="mailto:nribeiro82@gmail.com">nribeiro82@gmail.com</a>> wrote:<br>
> Hi all,<br>
><br>
> I have a scenario where I was testing DNS failover and this feature seems to<br>
> fail. I will try to explain the scenario:<br>
> I'm trying to establish a call between two user Agents, where one of the<br>
> users has services associated (trigger to ASs) to the session establishment<br>
> signaling (INVITE). So when SER makes the DNS query receives 2 ip addresses<br>
> for this AS. The sip message will be correctly forwarded to one of this two<br>
> entries and if in case of failure it will try to send the message to the<br>
> next entry (second ip address). But when we are triggering to the AS we will<br>
> add a route header and this header is not created in the second case, i.e.<br>
> after DNS failover as the SIP INVITE will be created based in the SIP<br>
> message received and not in the SIP message sent in the first place.<br>
> So anyone has any thoughts about this question and a solution to it?<br>
<br>
</div></div>Yes, try ser 2.1 :-)<br>
(it's fixed in there, see the reparse_on_dns_failover parameter).<br>
<font color="#888888"><br>
Andrei<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Nuno Ribeiro<br>