28 May
2010
28 May
'10
5:15 a.m.
Hi, Ricardo...
Just help us understand your needs so that we can better help you...
When you talk on scalability, on how many registered users are we
talking about?
Are all this users just registered, or are you planning to use RTPProxy?
If so, on the same machine?
Just let say that just for registration and SIP message routing (as for
what an SIP-proxy is for... :) ) Kamailio can easily handle 10k users in
a well designed and dimensioning server. Maybe Marius or Henning could
share with us fresh numbers from their environment, but the numbers are
impressive... really huge...
So, back to your requirement, are you aiming scalability or
availability? For the first, I already commented. For the second, the
path to obtain is other: load-balancing.
Edson.
Em 27/05/2010 18:09, Ricardo Coelho escreveu:
I am working on a project that aims to improve
scalability of a system and it is required that only some phones are attached to openserA
and all the others are attached to openserB. I am new to openser so forgive me for the
lack of knowledge.
Thanks
On May 27, 2010, at 5:05 PM, Klaus Darilion wrote:
Am 27.05.2010 17:09, schrieb Ricardo Coelho:
_______________________________________________
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
I have 2 machines running openser and some phones
are registered on openserA and some on openserB.
Why are some phones registered at openserA and others at openserB?
- Do they have different SIP domains where one SIP domain point to A and other domain
point to B?
- Are they using the same SIP domain but the domain has multiple NAPTR/SRV/A records
causing the segmentation?
- Are they using the same SIP domain which points to a load balancer which forwards some
clients to A and other to B?
- something else?
regards
Klaus