I agree with what Phil has mentioned. In my opinion - if you don't need
the fancy features of 10.x (aka Asterisk 1.10.x) stick to Asterisk 1.8
or older. However - I would recommend anyone to stay away from any
variant of 1.8 or 10.x where possible.
We process over a million minutes per month per server, exceeding 400K
calls per server in a given month. Many moons ago, as soon as 1.8 was
released, we jumped from 1.4 to 1.8 - and it was a huge mistake.
Asterisk service crashed with dead locks within the first few thousand
calls.
We downgraded from 1.8 to 1.6. We found that Asterisk 1.6.2.17 (plus
certain patches) -- was the most successful and stable deployment,
capable of handling 100+ simultaneous calls per server.
Handling about 100+ calls per server on Asterisk 1.8.x.x and Asterisk
10 -- killed Asterisk within hours. The primary cause is dead
locks. The stats I presented is that of a production deployment.
If stability and high availability is your primary focus - then I would
say stick to version 1.6.2.17.
If your client is "ok" with a reboot or two every week - then 1.8 should
be ok.
Overall - we have been testing all versions of Asterisk - as they are
released by deploying them as production.
All servers monitor each others availability by means of an actual sip
call - server to server.
In our production scenario - we keep a hot standby servers with version
1.6.2.17 ready,
while we route calls to the server with a newly released 1.8.x.x or
10.x.x within the production environment.
As soon as 1.8.x.x or 10.x.x fails and/or enters into a dead lock - hot
standby 1.6.2.17 starts processing calls.
To date, we've had 100% failure with 1.8.x.x and 10.x.x within a 24
hour period, prior to having processed 10K calls.
As soon as a dead lock is confirmed, we downgraded the recent version
back to 1.6.2.17.
Therefore - in an ITSP scenario, or in a scenario where you are
processing calls in the thousands - definitely stay away from 1.8.x.x
and 10.x.x and stick to 1.6.2.17 (with certain security patches).
I would LOVE to hear from anyone out there - processing the volume we
are handling (or more), in an Asterisk environment -- using 1.8.x.x or
10.x.x versions of Asterisk.
Thanks and regards,
Reza.
--
FOUNDER & SR. TELECOM ANALYST
VOIPERNETICS COMMUNICATIONS
NATION WIDE DIDS, SIP TRUNKS & VOIP 911.
PARTIAL / FULL VIRTUAL PRI - NO CONTRACTS!
HOSTED PBX & TERMINATION SERVICES.
TEL: 647-476-2067
Philip Mullis wrote the following on 8/7/2012 10:42 PM:
Asterisk 10 has a number of major improvements as several things where
rewritten, it has extended support for a wider range of codes lots of
focus on the hd stuff, better performance and stability. It now also
supports video conferencing more extensively and has a new conference
application all together that no longer requires the use of the dahdi
timer.
FreePBX is used by loads of people, its great for people that want a
gui, however big note to self there.. you have to button it up/make it
safe. There have been a massive amount of boxes hacked over the years
with things like freepbx/trixbox etc.. installed on them because they
where not buttoned up so to say :)
In a small office environment your not really going to see any killer
differences with 1.8/1.10 unless you get into conferencing/ alternate
codecs.
Hope that helps.
Regards
Philip Mullis
On 08/07/2012 10:22 PM, Steven McCann wrote:
Hi All,
I'm setting up a new phone system for a small organization (about 15
extensions). I'm using the FreePBX distro. There is two main versions of
the FreePBX distro out right now - one with Asterisk 1.8, and one
with 1.10.
I'm curious if there are any pros/cons to deploying 1.10 VS 1.8? 1.10
sounds like it may have some fancy new features, however 1.8 I think
is an
LTS release..
Does anyone have any experience with 1.8 VS 1.10 or even just with
FreePBX?
Any advice or feedback?
Thanks,
Steve
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
