<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 07/10/2013 10:08 AM, Giuseppe De
Marco wrote:<br>
</div>
<blockquote
cite="mid:1373443736.31020.YahooMailNeo@web171401.mail.ir2.yahoo.com"
type="cite">
<div style="color:#000; background-color:#fff; font-family:times
new roman, new york, times, serif;font-size:12pt">
<div style="font-family: 'times new roman', 'new york', times,
serif;"><span></span>
<div class="yiv9623467773y_msg_container"><span>
<div class="yiv9623467773y_msg_container">a) sipXecs IP
PBX uses external gateways. It supports as many external
gateways you need without limit and offers automatic
failover in case a gateway is unavailable or busy. It
also offers least cost routing where gateways can be
deployed anywhere you need them.</div>
<div class="yiv9623467773y_msg_container"><br>
</div>
<div class="yiv9623467773y_msg_container">b) sipXecs IP
PBX does not route calls (media) through the server
because it separates signaling from media. Therefore,
sipXecs can support as many simultaneous calls as your
LAN / WAN bandwidth permits. Asterisk has a hard limit
because calls go through the Asterisk server. For a
dual-core XEON with 2 GB RAM that limit is 60
simultaneous calls. </div>
<div class="yiv9623467773y_msg_container"><br>
</div>
<div class="yiv9623467773y_msg_container">c) Routes calls
direct peer-to-peer and not through the call control
server. The sipXecs IP PBX also supports HD voice for
both end points as well as PBX services such as
conferencing, voicemail and auto-attendant. Video
support poses no additional load on the sipXecs IP PBX
as the media streams do not go through the PBX server.</div>
<div class="yiv9623467773y_msg_container"><br>
</div>
<div class="yiv9623467773y_msg_container">Asterisk is
modeled like a more traditional TDM PBX where lines
("channels") come into the PBX that carry voice and
signaling. The IAX protocol even explicitly bundles
voice and signaling along the same route. This not only
uses more bandwidth than necessary, imposes additional
delay, injects additional jitter, and represents a
single point of failure, this also severely limits the
total number of calls that can go on at any given time
for the system. <br>
</div>
</span></div>
</div>
</div>
</blockquote>
<br>
Direi che merita di essere sperimentato. Sul sito è possibile
scaricare la iso di installazione di un sistema CentOS con incluso
sipXecs.<br>
<br>
Dopo non pochi sbattimenti l'ho installata su una VM, try it out<br>
<a class="moz-txt-link-freetext" href="https://10.87.1.70">https://10.87.1.70</a><br>
login:<br>
superadmin<br>
hacklabcosenza<br>
<br>
<br>
<pre class="moz-signature" cols="72">--
Vincenzo Pirrone</pre>
</body>
</html>