<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Philipp and Miguel.<br>
<br>
Thanks to both of you. <br>
<br>
rb<br>
<br>
Philipp Kempgen wrote:
<blockquote cite="mid49C90421.2070801@amooma.de" type="cite">
<pre wrap="">Miguel Paolino schrieb:
</pre>
<blockquote type="cite">
<pre wrap="">2009/3/23 Ron Byer Jr. <a class="moz-txt-link-rfc2396E" href="mailto:ronb@netweave.com"><ronb@netweave.com></a>:
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">I have a 2 node Asterisk (v 1.4.18) solution in what right now is an
active-passive configuration, utilizing heartbeat and a virtual-ip as
the shared resource.
Simply put, I can easily contact the primary server using the
virtual-ip, but the primary server responds with it's own ip, and all
the SIP/SDP fields (From, Contact, etc) as well as the rtp media
definition use the master's IP address. This screws up the down stream
devices which expect to be talking to the virtual IP address.
</pre>
</blockquote>
<pre wrap="">Configure SIP on Asterisk to bind to the virtual interface, not all of
them, this will solve it.
</pre>
</blockquote>
<pre wrap=""><!---->
Right. :-) bindaddr in sip.conf. How could it not come to my mind.
Philipp Kempgen
</pre>
</blockquote>
<br>
</body>
</html>