<br><br><div class="gmail_quote">2010/8/20 Matt Riddell <span dir="ltr"><<a href="mailto:matt@venturevoip.com">matt@venturevoip.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 20/08/10 5:10 AM, Grygoriy Dobrovolskyy wrote:<br>
><br>
><br>
> 2010/8/19 Mamadou Lamine KA <<a href="mailto:lamineka@groupechaka.com">lamineka@groupechaka.com</a><br>
</div>> <mailto:<a href="mailto:lamineka@groupechaka.com">lamineka@groupechaka.com</a>>><br>
<div class="im">><br>
> Hello all,<br>
><br>
> I need to setup a voicemail system for a telco that will handle up<br>
> to 150,000 calls per hour with 3,000,000 to 3,500,000 users.<br>
><br>
> It will be the first time for me to design such a plateforme. So I<br>
> need your advices about dimensioning and architecture for high<br>
> availability system.<br>
><br>
> - Did you ever experience running asterisk with such level of traffics?<br>
><br>
> Hello, dont use asterisk for that, you need opensips or kamalio, its an<br>
> sip proxy capable of handling lots of users and calls with loadbalancing.<br>
<br>
</div>Except that he's looking to set up a voicemail system rather than a<br>
phone call platform.<br>
<br>
Basically, you could use Asterisk, but if you're only using one feature<br>
it may be excessive.<br>
<br>
You're basically looking at around 42 calls per second, which isn't a<br>
super huge number.<br>
<br>
The number of users is likely to create a bit of a problem unless you're<br>
able to spread them across multiple instances.<br>
<br>
If you could, and had lots of servers, (with Kamalio etc in front<br>
distributing as Grygoriy mentioned) then it's likely to be not too much<br>
effort.<br>
<br>
Are you really going to be doing it with Analogue line cards though?<br>
<br>
Surely SIP or something would be easier?<br>
<br>
If you are using line cards then Kamailio etc won't help.<br>
<br>
If we say that the average call lasts say 2 minutes (120 seconds) then<br>
you would have 42 calls per second multiplied by 120 (length of call)<br>
equals 5040 concurrent calls.<br>
<br>
If you are using primary rate E1 cards with say 120 channels per box,<br>
you'd be looking at 42 boxes :) Lol the numbers keep repeating :D<br>
<br>
Obviously if you wanted to go to two quad span primary rate cards per<br>
box you'd be looking at 21 servers (although both of these numbers leave<br>
no room for redundancy).<br>
<br>
If you're running 42 boxes, you're definitely going be having some<br>
failures, which means that you'd better have some system to distribute<br>
the file system etc and have hot swap servers available to fill the void<br>
if others die.<br>
<br>
--<br>
Cheers,<br>
<br>
Matt Riddell</blockquote><div><br></div><div>Oh, yea sorry about that, for voicemail i would use freeswitch really with a remote storage for voicemail. In this way we just have redundancy and couple of sip proxy in front.</div>
<div><br></div><div>Well, but anyways most of people asking such a questions do not realize the size of the project. I have seen couple of demands like that, people think that they will put couple a servers pay a student to do it and voila. And when you are telling them that they need 20 servers at least they drop the project. And most of the time they go to proprietary where they pay more they using opsnsource, its a paradox.</div>
</div>