<br><br><div class="gmail_quote"><br><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">
>> Ok, nice to know; so you went with one Asterisk per customer.<br>
>> May I ask why you set it up like this? Protection, mainly?<br>
>><br>
><br>
> Security, obscurity and adaptability. If one asterisk fails one<br>
> customer is angry. If one multi-customer asterisk fails, lots of<br>
> customers get angry. ;)<br>
><br>
</div>On the other hand, it's harder to build a scalable solution that<br>
way... There's no reason why we could not have another Asterisk<br>
standing by when one fails. The issue here is that calls would go down<br>
and states would be lost for blinking lamps. That will always happen<br>
(unless someone magically adds the needed code to handle that).<br>
<br>
There are architecture problems that we haven't solved in Asterisk<br>
today in regards to multi-hosting. There's a lack of segmentation of<br>
Asterisk that could prevent overlaps. I've been doing a few things,<br>
like multiparking and SIP domains that are steps toward a solution.<br>
Tilghman has some extra headers for AMI in testing and we've discussed<br>
how to use that for more segmentation by applying event filters to<br>
those headers. Next step would be to be able to restrict access for<br>
orignate-like actions in manager by applying contexts to each manager<br>
account.<br>
<br>
The settings in feature.conf are also pbx-wide, which might be a<br>
problem. There are propably a lot more issues that I don't see right<br>
now.<br>
<br>
So there are a lot of reasons why you want a single PBX per customer<br>
today. Hopefully someone will fund work so that we can support at<br>
least 50% of the cases in a large PBX with failover, and have the rest<br>
that are advanced users using their own. That would be very beneficial<br>
for all of us.<br>
<br>
There's also some interesting development in the SIP proxy arena<br>
(OpenSIP/kamailio/sip-router/ser/openser group) that may lead to new<br>
architectures for the 50% of the customers.<br>
<font color="#888888"><br>
/O<br></font></blockquote><br><br>But at the end of it, is there a solution for IAX2, what is the best setup we can<br>come up with using this protocol on a HA configuration?<br><br>Is there a IAX2 proxy somewhere or are they just pass through setups (e.g. ultramonkey) ?<br>
<br></div>Are there any drawbacks?<br><br>