Difference between revisions of "Implementations"
From Kolmisoft Wiki
Jump to navigationJump to search
| Line 1: | Line 1: | ||
This page shows some ways how MOR billing system can be used. Examples are from real implementations. | This page shows some ways how MOR billing system can be used. Examples are from real implementations. | ||
<br> | <br> | ||
| Line 46: | Line 23: | ||
* How many network cards are necessary for each server? | * How many network cards are necessary for each server? | ||
** They can work with one card, but better to have 2 cards for each server and interconnect servers on dedicated LAN | ** They can work with one card, but better to have 2 cards for each server and interconnect servers on dedicated LAN | ||
<br> | |||
---- | |||
<br> | |||
==[[Image:ita.jpg]] 4 server solution in Italy with 16 E1== | |||
[[Image:impl_2ast1db1gui16e1.png]] | |||
* Such system is in Italy serving Call Shops | |||
* 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> | |||
---- | |||
<br> | |||
==Many Asterisk servers with DB Replication== | |||
[[Image:impl_nast2db1gui.png]] | |||
Revision as of 19:30, 11 September 2008
This page shows some ways how MOR billing system can be used. Examples are from real implementations.
3 server redundant solution
- By default calls go to first Asterisk server
- If first Asterisk server fails, DNS SRV points to second Asterisk server
- If database server fails, second Asterisk server is still functional and can serve calls
- How it will work with DNS?
- Traffic should come to some URL, which is configured using DNS SRV, e.g. it should route calls from URL to first server IP, if this IP is not available - then this URL points to second server IP
- Do we need separate DNS server?
- It is not necessary, DNS SRV can be configured on your Internet providers' DNS server.
- What hardware is recommended for each server?
- Main Asterisk server should have powerful CPU (Dual/Quad Xeon) and at least 2GB RAM
- DB/GUI server should have FAST HDD and 2-4Gb RAM. CPU is not so important here
- Asterisk/DB server can be not so powerful as other two
- How many network cards are necessary for each server?
- They can work with one card, but better to have 2 cards for each server and interconnect servers on dedicated LAN
4 server solution in Italy with 16 E1
- Such system is in Italy serving Call Shops
- E1 hardware is 2 x 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.
Many Asterisk servers with DB Replication
