<br><br><div class="gmail_quote">On Tue, Nov 3, 2009 at 9:31 AM, Olle E. Johansson <span dir="ltr"><<a href="mailto:oej@edvina.net">oej@edvina.net</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;">
<br>
3 nov 2009 kl. 15.19 skrev Frederic Jean:<br>
<div class="im"><br>
><br>
><br>
> Thanks Olle, I can only agree with you; it needs love to work<br>
> properly, lots of love : )<br>
</div>And propably a major redesign to fulfill the expectations from the<br>
users :-)<br>
<div class="im"><br>
><br>
> So talking about the "other" school, you put a SIP Proxy on the two<br>
> servers with a virtual IP<br>
> and get the Asterisk to talk with the same database setup we<br>
> described here I guess.<br>
<br>
</div>The proxys need to handle one or two virtual IPs if you need NAT<br>
support. By design,<br>
the SIP protocol uses DNS for load balancing and failover, so it<br>
should not be needed,<br>
but most phones (as well as Asterisk) doesn't implement this fully so<br>
in the end you<br>
usually end up with heartbeat.<br>
<br>
How much of the database you need to talk with from Asterisk in this<br>
setup depends on<br>
what you do in the proxy. Some information that the proxy looks up<br>
regardless can be<br>
sent in sip headers to Asterisk.<br>
<br>
It all depends on your application. Running a SIP-PSTN gateway service<br>
for consumers is one thing, running a hosted PBX is completely<br>
different and requires a different setup.<br>
<div class="im"><br></div></blockquote><div><br>It is actually for hosting several companies' PBXs on one platform, this including<br>voicemail, etc, and video in a near future.<br><br>I then might have been off track since the beginning, but hey, that's why mailing lists exists ; )<br>
<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">
><br>
> It sure is less complicated and more straight forward in terms of<br>
> dialplan, etc.<br>
</div>Well, it does require some new thinking to get it right if you're used<br>
to have Asterisk matching<br>
peers and users.<br>
<br>
Maybe we need an AstriSIPcon for having time to discuss this work. :-)<br>
<br>
/O<br>
<div><div></div><div class="h5">><br>
><br>
><br>
><br>
><br>
> On Tue, Nov 3, 2009 at 3:44 AM, Olle E. Johansson <<a href="mailto:oej@edvina.net">oej@edvina.net</a>><br>
> wrote:<br>
><br>
> 3 nov 2009 kl. 02.35 skrev Frederic Jean:<br>
><br>
> > Is this something "standard" in a HA Asterisk solution? Has anybody<br>
> > tried something similar?<br>
> > Any comments are appreciated!<br>
><br>
> There are basically two different schools. The one you describe is<br>
> focused on Asterisk and is based on realtime/dundi. The other one<br>
> focuses on SIP and builds an extensible SIP network based on SIP<br>
> proxys that load balance SIP traffic to a set of Asterisk servers. In<br>
> this case, Asterisk doesn't receive registrations and doesn't "own"<br>
> devices. On the other hand, you can easily add other SIP applications<br>
> than voice. Video, presence, instant messaging...<br>
><br>
> Asterisk is a great platform, but only for telephony and since it's<br>
> call stateful, it doesn't scale as easily as a SIP proxy. The<br>
> combination is great. This is how I built platforms for service<br>
> providers during many years, and this is also what we teach in the<br>
> Asterisk SIP Masterclasses.<br>
><br>
> Since I need SIP scalability, I haven't focused on realtime/DUNDI. I<br>
> personally feel that the realtime/SIP implementation needs love to<br>
> work properly and that DUNDI is a bit limited to Asterisk. Nothings<br>
> stops other products from implementing DUNDI, but so far, no one has<br>
> been interested.<br>
><br>
> Regards,<br>
> /Olle<br>
><br>
> _______________________________________________<br>
> --Bandwidth and Colocation Provided by <a href="http://www.api-digital.com--" target="_blank">http://www.api-digital.com--</a><br>
><br>
> asterisk-ha-clustering mailing list<br>
> To UNSUBSCRIBE or update options visit:<br>
> <a href="http://lists.digium.com/mailman/listinfo/asterisk-ha-clustering" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-ha-clustering</a><br>
><br>
> _______________________________________________<br>
> --Bandwidth and Colocation Provided by <a href="http://www.api-digital.com--" target="_blank">http://www.api-digital.com--</a><br>
><br>
> asterisk-ha-clustering mailing list<br>
> To UNSUBSCRIBE or update options visit:<br>
> <a href="http://lists.digium.com/mailman/listinfo/asterisk-ha-clustering" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-ha-clustering</a><br>
<br>
</div></div>---<br>
<div class="im">* Olle E Johansson - <a href="mailto:oej@edvina.net">oej@edvina.net</a><br>
</div>* Cell phone +46 70 593 68 51, Office +46 8 96 40 20, Sweden<br>
<div><div></div><div class="h5"><br>
<br>
<br>
<br>
_______________________________________________<br>
--Bandwidth and Colocation Provided by <a href="http://www.api-digital.com--" target="_blank">http://www.api-digital.com--</a><br>
<br>
asterisk-ha-clustering mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-ha-clustering" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-ha-clustering</a><br>
</div></div></blockquote></div><br>