Hi Mehdi,
if you choose the right hardware (Jetway, APU2 or a VM - checkout our Wiki) the
AstLinux server itself will rarely be the culprit of an outage.
IMHO in 90% of all cases is either the internet down, there are problems with
DNS or other ISP issues or the SIP-trunk provider has issues.
Other cases from experiences would be broken power supplies, CompactFlash cards
or mSATAs (very rarely). Some of my customers have a second backup box.
None of them ever really used them ("in production"), they only tried to use
them only to figure out, that the internet/SIP trunk is really down :-).
Michael
http://www.mksolutions.info
> Am 15.07.2017 um 07:14 schrieb Mehdi Shirazi via Astlinux-users
> <[email protected]>:
>
> Hi
> This is my modified version of two servers poor mans Load balancing & High
> Availability plan:
>
>
> 1- Servers are Active/Active. Sip phones are registered base on DNS-SRV or
> they support primary and
>
> secondary server.
>
> 2-Servers realize sip phone registration states by DUNDi and route the call
> to correct server.
> 3-Not saving any Persistence data in internal Asterisk database Astdb and
> implementing service like
>
> DND... in dialplan and saving any service and persistence data in BOTH
> servers another odbc database at SAME time in dialplan(number of writing for
> service configuration change is very low vs reading so no performance penalty
> for writing in both servers databases from one server dialplan )=> no need to
> database replication.
> 4-Configuration files, voice files... should be synchronized between two
> servers by Unison.
>
>
> any opinion and any experience with astlinux and DUNDi(Corosync).
>
> Regards
> M.Shirazi
>
> ________________________________
> From: Mehdi Shirazi via Astlinux-users <[email protected]>
> To: AstLinux Users Mailing List <[email protected]>
> Cc: Mehdi Shirazi <[email protected]>
> Sent: Monday, July 10, 2017 12:22 PM
> Subject: Re: [Astlinux-users] RAMdisk and HA
>
> Hi
>
> Thanks for Answers.
> My compromised design about a VOIP system is this:
> 1-It is Active/Standby and saving Call states are NOT important and switch
> over up-til 5
> minutes is ok (if Active server fails ,sip phones should register again in
> Standby server)
>
>
> 2-Not saving any Persistence data in internal Asterisk database Astdb and put
> it in RAMDisk.
> According to Freeswitch wiki(similar project)it greatly improve performance
> and prolong SSD life:
> "On a normal configuration, core.db is written to disk almost every second,
> generating hundreds of
>
> block-writes per second. To avoid this problem, turn /usr/local/freeswitch/db
> into an in-memory
>
> filesystem. If you use SSDs, it is CRITICAL that you move core.db to a RAM
> disk to prolong the life of
>
> the SSD."
> https://wiki.freeswitch.org/wiki/FreeSWITCH_DB_In_RAMdrive
> https://wiki.freeswitch.org/wiki/Performance_testing_and_configurations#FreeSWITCH.27s_core.db_I.2FO_bottleneck
> https://freeswitch.org/confluence/display/FREESWITCH/SSD+Tuning+for+Linux
>
> 3-Persistance data saved in another Sqlite3 or odbc database.
> Configuration files, voice files... should be synchronized between Active and
> standby server
> bidirectionally(GlusterFs,csync2,unison) also Sqlite3(rqlite?) or odbc
> database(postgresql bdr , mysql
>
> master master).
>
> Bidirectionally because I want when master server recovered from a failure it
> has all changes Slave
>
> server done (follow me changes , voice message deletes... ) another reason
> for bidirectional replication
>
> is may be we can put some load on standby server( some queue or some
> IVRs...with fallback to Active capability)
>
> 4-It is possible to use sip phones with capability of setting primary and
> secondary servers but IP float
> (Keepalived) is preferred.
>
> Regards
> M.Shirazi
> ________________________________
> From: Michael Knill <[email protected]>
> To: AstLinux Users Mailing List <[email protected]>
> Sent: Monday, July 10, 2017 3:11 AM
> Subject: Re: [Astlinux-users] RAMdisk and HA
>
>
>
> Hi Mehdi
>
> 1. Im interested in your requirements here. Are you having performance
> issues with the current setup? Are the DB lookups your bottleneck? Are you
> using an SSD?
> 2. Astlinux supports WAN failover only. There are a few articles available
> regarding solutions for Asterisk HA but it is not an inbuilt Asterisk
> feature. What are your requirements for HA?
> 3. It should be fairly simple to build some middleware for this
>
> Regards
> Michael Knill
>
> From: AstLinux List <[email protected]>
> Reply-To: Mehdi Shirazi <[email protected]>, AstLinux List
> <[email protected]>
> Date: Saturday, 8 July 2017 at 3:33 pm
> To: AstLinux List <[email protected]>
> Cc: Mehdi Shirazi <[email protected]>
> Subject: [Astlinux-users] RAMdisk and HA
>
> Hi
> Thanks for maintaining good project.
> 1-Is it possible to put internal Asterisk database in RAMdisk (tmpfs) for
> performance and save other persistence database in another database?
> 2-Is there any HA solution ? (Active /Standby, keepalived)
> 3-Is there any automatic two way file(database) synchronization utility ?
>
> Regards
> M.Shirazi
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Astlinux-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to
[email protected].
