1 Apr
2014
1 Apr
'14
3:18 a.m.
Also, MongoDB is not a relational database like MySQL or PostgreSQL. The choice to use a
schemaless/NoSQL database vs. an RDBM must be rooted entirely in the type of data
you're storing and how you want to store it. These concepts are not freely
interchangeable.
On 1 April 2014 03:16:13 GMT-04:00, Alex Balashov <abalashov(a)evaristesys.com>
wrote:
All modules are listed here:
http://kamailio.org/docs/modules/4.1.x/
On 1 April 2014 03:12:10 GMT-04:00, Rizwan Khan <rizkhan(a)gmail.com>
wrote:
some
as
<abalashov(a)evaristesys.com>
getting
mailing
--
Sent from my Nexus 10, with all the figments of autocorrect that might imply.
Alex Balashov - Principal
Evariste Systems LLC
235 E Ponce de Leon Ave
Suite 106
Decatur, GA 30030
United States
Tel: +1-678-954-0670
Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
Thanks a lot Pedro.
Just one question? Do we have module for Mongodb? how do i use it?
Rizwan Khan
On Mon, Mar 31, 2014 at 5:52 AM, Pedro Niño <nino.pedro(a)gmail.com>
wrote:
choke
As Alex said, I/O and calls per second (CPS) is
Dependant on what
type of
> design you are using.
>
> As a tip, mysql is good for small to medium sizes, but begin to at
> 1000 of concurrent connections. but in a scalable size like you are
> planning, I would recommend to make a design with resilience and
high
availability, with mongodb or postgres as db back end.
There are some good examples on internet about enabling multiple
kamailio
> server with high availability configuration, using heartbeat and other
> scripts.
>
> A nice design would be:
>
> 2 or more kamailio servers, maybe virtual or physical, with high
> availability configuration (if one goes down, the other takes all
the
load)
120.000
2 or more DB servers, also with high availability design.
At least 10G connection, server and switch (for the call flow you're
expecting) remember to make estimation for calls established, and
codec
> used, (using g711, rtp audio might come up to 80kbps, so like calls
> is the top for a 10G connection)
>
> Also separate vlan for calls and server control, too.
>
> Just my 2 cents
> El mar 28, 2014 11:58 AM, "Rizwan Khan" <rizkhan(a)gmail.com>
escribió:
Thanks Alex.
>
> What are the components that I should take into account. Based on
answer
> in another thread I will be using SIP trunk
with an NGN to route
the
>> outside traffic (other than SIP-SIP).
>>
>> I'll have NATed clients so I'll need the media proxy or rtp proxy
> well.
What about their dimensioning? I am sorry if some questions
are
> really naive. I am new to all this and trying
to get hold of the
whole
>> technology stack.
>>
>> Rizwan
>> On Mar 28, 2014 3:41 PM, "Alex Balashov"
>
wrote:
>
>> 1. Kamailio does not handle RTP, so audio is not a scaling factor
at all;
>>
>> 2. The only scaling factors are transactional memory (TM) and any
dialog
>> state you are keeping;
>>
>> 3. Without I/O wait from external sources, Kamailio can handle a
>> practically infinite amount of concurrent calls and CPS. But, most
>> practical applications of Kamailio require database backing;
>>
>> 4. Therefore, performance and throughput will depend almost
entirely on
>> the database you are using for database
backing, and any tuning on
its
>>> settings. This certainly includes the CDRs and storage, and the
>>> most performance out of your database is outside the domain of
your
>>> question (or this list);
>>>
>>> 5. A quad-core host with 8 GB of RAM should be more than
sufficient
for
>>> Kamailio itself to meet your needs. But most of the answers to
your
>>
question don't have much to do with Kamailio.
>>
>> -- Alex
>>
>> On 03/28/2014 06:36 AM, Rizwan Khan wrote:
>>
>> HI Guys,
>>>
>>> can you refer me to some resources which help me dimension the
hardware
>>> for a setup.
>>>
>>> Total users will be 20,000. What percentage should i assume for
>>> concurrent audio and video calls? What is the standard practice?
How
>>> does this all map to the cpu, ram and
storage etc. given that I
will be
>>> storing the cdrs as well.
>>>
>>> In the futute this setup should be scalable so that it should
support
>>> 200,000+ users within a span of 6-8
months. What would be the
ideal
>>>> architecture?
>>>>
>>>> Thanks,
>>>>
>>>> Rizwan Khan
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users list
list
list
>>> sr-users(a)lists.sip-router.org
>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>>
>>>
>>
>> --
>> Alex Balashov - Principal
>> Evariste Systems LLC
>> 235 E Ponce de Leon Ave
>> Suite 106
>> Decatur, GA 30030
>> United States
>> Tel: +1-678-954-0670
>> Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
>>
>> _______________________________________________
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
list
>> sr-users(a)lists.sip-router.org
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
------------------------------------------------------------------------
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Sent from my Nexus 10, with all the figments of autocorrect that might
imply.
Alex Balashov - Principal
Evariste Systems LLC
235 E Ponce de Leon Ave
Suite 106
Decatur, GA 30030
United States
Tel: +1-678-954-0670
Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
------------------------------------------------------------------------
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users