Hardware:	Standard server certified for RHEL Linux
Recommended configuration:	Dual redundant power, RAID-1 disk
Memory:	2GB ECC DRAM minimum (up to 150 users), 4GB to 8 GB recommended
Disk:	250GB sufficient for about 4,000 hours of voicemail message storage
Network:	1 Gbit/s Ethernet
Operating system:	RHEL 5 or CentOS 5, 32 bit or 64 bit versions

Redundant servers and additional servers deployed to scale media services are typically of the same HW specification. A full openUC system requires a minimum of one server. The maximum number of servers used depends on deployment options, redundancy requirements, geographical distribution, number of users served, as well as the expected usage of media services. All servers centrally managed.

Virtualization and hosting in the Amazon EC2 cloud requires an instance of type 'Large':

• 7.5 GB memory
• 4 EC2 Compute Units (2 virtual cores with 2 EC2 Compute Units each)
• 850 GB instance storage (2×420 GB plus 10 GB root partition)
• 64-bit platform

Procurement of Hardware:  If you need assistance with a customized configuration contact your local eZuce partner for more details. eZuce does not provide hardware.  Hardware is procured by the channel partner or customers directly at most favorable prices. However, eZuce provides end-to-end support for the entire solution that is based on eZuce certified components (see list below).

The following performance limitations are conservative numbers that were obtained through load tests on a dual-core 2.3 GHz system with 2 GB of RAM.  More aggressive load testing has been performed by several groups using more capable hardware such as quad core or dual quad core CPU with 8 GB or 16 GB of RAM.  Up to between 1,000 and 2,000 simultaneous media sessions per server have been obtained. Instant Messaging (IM) and Presence performance is known to scale up to 250,000 simultaneous users.  In addition, several servers can run in parallel as part of a distributed system.

Number of registered users:     10,000 (target of 20.000 for release 4.6)

Call setup:    15 cps (54,000 BHCC) per node (authenticated calls with CDR reporting). Scales linearly by adding nodes. Maximum of 3 load-sharing redundant nodes, extended to more than 50 load-sharing and distributed nodes with release 4.6.

Parallel (concurrent) calls:

• Voice: No limit  (limited by LAN / WAN bandwidth)
• Video: No limit (limited by LAN / WAN bandwidth)

Conferencing:  

• Single conference up to 300 participans per server (G.711 and G.722 codecs), no transcoding
• Single conference up to 200 participans per server (G.711 and G,722 codecs), with transcoding
• Up to 100 conferences with 5 participans each, no transcoding

Voicemail:

• Up to 400 ports of voicemail
• Up to 10,000 inboxes
• VM storage based in disk capacity

IVR:

• Up to 400 ports

SIP trunking:

• 500 parallel sessions per server (media relay), codec agnostic
  (requiering 14% CPU on E6550 dual-core @ 2.3 GHz)

PSTN trunking:

• Unlimited number of PSTN gateways
• Gateways can be located in different locations on the network
• Gateways offer seamless trunk failover

Instant Messaging:

• Up to 10,000 signed-in users
  (known to scale to 250,000 concurrent users on a single machine)

Contact Center:

• 30 agents, 50 calls in queue per server
  (we are working on improving this)

Notes: 

• openUC allows individual services to be installed on dedicated hardware
• More than one conferencing or ACD server can be used per cluster
• In a high-availability configuration serveral nodes run in parallel load-sharing mode scaling call/s performance lineraly
• The theoretical limit on a 100 Mbit/s Ethernet is 700 parallel media sessions (allows for media and signaling) Gbit/s Ethernet performance depends on network interface hardware and othe network related factors.

openUC is compatible with SIP & XMPP standard compliant phones, softphones, IM clients, gateways and applications.  The large number of features provided by openUC does not work with every phone or gateway as there are differences in the quality of firmware supplied with these devices. Therefore, we distinguish between certified third party products, supported products, and unsupported products.

Certified products:  These are fully tested and certified products for which eZuce offers it's full range of support services.

Supported products:  These are products for which there is some plug & play management support in openUC, but eZuce does not offer formal support contracts. Products in this category are supported on a best effort basis. There might be features that do not work with these devices or applications.

Unsupported products: These are products known not to work in critical areas or products for which there is no plug & play support yet.  Such products can be manually configured and might work with openUC. eZuce does not offer support for such products, but might be interested in assisting with establishing interoperability or help develop a plug & play plugin. Contact us for more information.

List of certified products:

• Polycom SoundPoint SIP IP phones (all models)
• Polycom SoundStation SIP IP conference phones
• Audiocodes gateways
• Counterpath Bria softphone (Windows, Mac)
• Pidgin open source IM client (Windows, Mac, Linux)
• GTalk client for fixed mobile convergence (FMC) on Android, iPhone, Blackberry, Nokia and others
• eZuce Communicator IM client (derivative of the Spark IM client) on Windows, Mac, Linux

 List of supported products:

• Avaya 12xx SIP IP value line of phones
• Snom, select models
• Yealink phones
• Cisco phones, select models
• Cisco gateways are known to work well
• ACME Packet SBC
• Gtek phones
• Audiocodes phones
• Patton Smartnode gateways
• VOP Soft Operator Panel
• RSI Revolution Web Call Accounting software
• Adium open source IM client on Mac
• SIPDroid SIP client on Android
• CSipSimple Android client
• iSip on iPhone

Unsupported products:

• Grandstream  (these phones are known to cause problems with certain call flows)
• Mediatrix gateways are not supported
• Astra phones

More info is available on the SIPfoundry Wiki.