Difference between revisions of "Implementations"

From Kolmisoft Wiki
Jump to navigationJump to search
 
(76 intermediate revisions by 5 users not shown)
Line 1: Line 1:
This page shows some ways how MOR billing system can be used. Examples are from real implementations.
Here you can review the possible MOR implementations.
<br>
----
<br>


==2 servers solution==
You can start with a single-server solution and scale the system as your business grows.
[[Image:2serversaASTDBandGUIDB.png|200px]]


This solution has two replicated databases.
On all listed implementations it's recommended to deploy Asterisk and DB servers in the same datacenter to ensure stable system functioning.  


Asterisk connects to one database and GUI connects to another, so it increases performance when Web interface is used intensively.
Even though it's possible to deploy these elements in different locations, such implementations may cause many issues, related to delays between different networks.


<br>
<br><br>
----
 
<br>
= 1 Server Basic System =
 
Up to 500cc
 
This is a very basic solution All-in-one-Server. No redundancy, no High-Availability, no Scalability.
 
We recommend to use it only in the testing environment.
 
Not safe to use in the real business environment.
 
 
[[Image:MOR_1server.png|600px]]
 
<br><br>
 
= 2 Servers Solution with 2 IP Addresses =
 
Up to 1000cc
 
The solution allows placing two servers in different locations.
 
In case of broken connection or broken database replication between servers, each site will become separated systems and runs its own billing, which is not desirable in most cases.
 
It provides double capacity with increased risk of malfunctioning in case of hardware/software/network failure.
 
2 IP Addresses allows route balancing at the side of the customers/vendors. They will use 2 IPs to balance traffic on their side.
 
[[Image:2serversaASTDBandGUIDB_v2.png|800px]]
 
 
<br><br>
 
=2 Server Redundant High-Availability Solution=
 
Up to 500cc


==2 server redundant solution==
[[Image:2serverredundant_withlinuxha.png|200px]]
This is the most popular solution because it is fully redundant and most stable.
This is the most popular solution because it is fully redundant and most stable.


More info: [[2 server redundant solution]]
More info: [[2 Server Redundant Solution]]
 
 
[[Image:2serverredundant_withlinuxha_v2.png|800px]]
 
 
 
<br><br>
 
=3 Server Non-High Availability Solution =


<br>
Up to 1000cc
----
<br>


==4 server redundant solution==
Not-recommended solution because of the risk to have main components on one server.
[[Image:4serverredundant_withlinuxha.png|200px]]
Stable and redundant solution for high performance.


More info: [[4 server redundant solution]]
[[Image:mor_proxy_1000cc_non_ha.png|800px]]


<br>
----
<br>


==[[Image:ita.jpg]] 4 server solution in Italy with 16 E1==
<br><br>




[[Image:impl_2ast1db1gui16e1.png]]
=4 Server High Availability Redundant Solution =


* Such system is in Italy serving Call Shops
Up to 1000cc
* E1 hardware is 2 x [http://www.sangoma.com/datasheets/a108-specs Sangoma A108DE] cards
* This implementation is used for high volume calls to/from PSTN network over 16 E1 links were 4+4 E1 is for incoming and 4+4 E1 is for outgoing (on Asterisk 1 server 4 incoming/4 outgoing and same on server Asterisk 2).
* Separate server is dedicated to database which minimizes load on Asterisk servers.
* GUI is on separate server with it's own DB connected to main DB server over MySQL Replication.


<br>
The recommended solution for High-Availability, Redundant System.
----
<br>


==Many Asterisk servers with DB Replication==
[[Image:mor_proxy_1000cc_ha.png|800px]]


[[Image:impl_nast2db1gui.png]]


<br>
<br><br>
----
<br>


==Multiple Asterisk servers with SIP balancer and DB Replication==
=Complete Redundancy, high-performance system with SIP balancer=


[[Image:impl_1sipbalnast2db1gui.png]]
Up to 2000cc, 100 CPS


* [[SIP balancer| SIP balancer]]
* GUI is on DB servers
* If one of Asterisk servers fails, SIP balancer routes calls via remained Asterisk servers.
* Proxy servers share 1 IP managed by Heartbeat
* DB (Core-Asterisk/GUI) servers share another 1 IP also managed by Heartbeat
* LinuxHA heartbeat monitors Database servers
* LinuxHA heartbeat monitors Database servers
** When Main Database fails - Backup Database sees that and after 10s (default) will take Virtual IP, it is done automatically.
* If one of the Core-Asterisk servers fails, SIP balancer routes calls via remained Core-Asterisk servers.
** When Main Database is back up - Backup Database returns Virtual IP to Main Database and system starts to function in normal work flow (done automatically).
* More Core-Asterisk Nodes can be connected, example with 2 is a bare minimum
 
* When Main Database fails - Backup Database sees that and after 10s (default) will take Virtual IP, it is done automatically.
* When Main Database is back up - Backup Database returns Virtual IP to Main Database and system starts to function in normal work flow (done automatically).
* GUI server is connected to Backup Database to avoid load on Main Database in normal work flow.
* GUI server is connected to Backup Database to avoid load on Main Database in normal work flow.


This solution can handle up to 1000 simultaneous calls. Certain amount of calls may vary depending on hardware, codecs used and transcoding. Additional Asterisk servers can be added if larger amount of simultaneous calls is needed.
For more details about SIP Balancer solution click [[SIP_balancer|here]]
 
[[Image:MOR_proxy_full.png|1001px]]
 
=See Also=
 
* [[M4_System_Architecture | M4 Implementations]]

Latest revision as of 11:49, 9 November 2023

Here you can review the possible MOR implementations.

You can start with a single-server solution and scale the system as your business grows.

On all listed implementations it's recommended to deploy Asterisk and DB servers in the same datacenter to ensure stable system functioning.

Even though it's possible to deploy these elements in different locations, such implementations may cause many issues, related to delays between different networks.



1 Server Basic System

Up to 500cc

This is a very basic solution All-in-one-Server. No redundancy, no High-Availability, no Scalability.

We recommend to use it only in the testing environment.

Not safe to use in the real business environment.


MOR 1server.png



2 Servers Solution with 2 IP Addresses

Up to 1000cc

The solution allows placing two servers in different locations.

In case of broken connection or broken database replication between servers, each site will become separated systems and runs its own billing, which is not desirable in most cases.

It provides double capacity with increased risk of malfunctioning in case of hardware/software/network failure.

2 IP Addresses allows route balancing at the side of the customers/vendors. They will use 2 IPs to balance traffic on their side.

2serversaASTDBandGUIDB v2.png




2 Server Redundant High-Availability Solution

Up to 500cc

This is the most popular solution because it is fully redundant and most stable.

More info: 2 Server Redundant Solution


2serverredundant withlinuxha v2.png




3 Server Non-High Availability Solution

Up to 1000cc

Not-recommended solution because of the risk to have main components on one server.

Mor proxy 1000cc non ha.png





4 Server High Availability Redundant Solution

Up to 1000cc

The recommended solution for High-Availability, Redundant System.

Mor proxy 1000cc ha.png




Complete Redundancy, high-performance system with SIP balancer

Up to 2000cc, 100 CPS

  • GUI is on DB servers
  • Proxy servers share 1 IP managed by Heartbeat
  • DB (Core-Asterisk/GUI) servers share another 1 IP also managed by Heartbeat
  • LinuxHA heartbeat monitors Database servers
  • If one of the Core-Asterisk servers fails, SIP balancer routes calls via remained Core-Asterisk servers.
  • More Core-Asterisk Nodes can be connected, example with 2 is a bare minimum
  • When Main Database fails - Backup Database sees that and after 10s (default) will take Virtual IP, it is done automatically.
  • When Main Database is back up - Backup Database returns Virtual IP to Main Database and system starts to function in normal work flow (done automatically).
  • GUI server is connected to Backup Database to avoid load on Main Database in normal work flow.

For more details about SIP Balancer solution click here

MOR proxy full.png

See Also

Retrieved from "https://wiki.kolmisoft.com/index.php?title=Implementations&oldid=29180"