I don't see any documentation readily available, and wanted to put this out
to those of you most familiar with the sipXecs system.

 

I'm looking to design a highly available production-ready environment of
sipXecs that would service a number of branch offices and number of
employees within each office (something around 2000 users to put a
hypothetical number out there, spread out over 20 offices). The system will
be housed in a central office that will act as a regional hub for calling
within (and without) the company (inbound/outbound calling will be handled
via ITSP or media gateways).  One of the core requirements is a wholly
highly available system: this means that each role of sipXecs must be
redundant, and if possible, scalable. This raises the following questions:

 

.             What is the best way to split the sipXecs roles into physical
servers (assuming each server is equipped with 2.8GHz dual processors, 4GB
RAM, and HDD space determined by role)?

.             What roles are readily highly available (besides the obvious
SIP Router role), and by what method are they made highly available (through
software on the system, SRV records, etc)?

.             Assuming that the role can be run in an HA mode, what kind of
scalability is available to a given role - for example: will it
load-balance, or will the 'active' working node be the only server available
for the given role? And again, how is this handled (I would assume SRV
records in this case)? 

.             Are there any roles of sipXecs that are NOT currently capable
of redundancy (I know voicemail was at one point but that was before
FreeSwitch was integrated, and I know the user interface portal is a
single-system only at this time)?

 

On a related note - has anybody done any load testing they could share with
a large subset of users (> 2000), or do any of you have experience with
running a system that large? Thanks all.

 

Peter Talbot

[v1.0.07.109]

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to