Teo's r3nd architecture provides for the most robust, reliable, and resilient Unified Communications system available. The architecture supports multiple deployment models to accommodate the needs of any organization.
Each Teo Resilient Node is a fully functional self-reliant UC system with internally redundant components and a real time RAID 1 array for configuration and storage data. Since all UC capabilities are supported bylightweight robust software and enabled by purpose-built hardware, each node can support an entire organization's full UC suite
Other solutions that require multiple servers to support a full UC application can only provide what is called "graceful degradation" in the event of a component or network failure. This means that while phone calls may be able to be made, voicemails may not be accessible, IM may not work, and conference bridges may not be available.
Teo's Resilient Node architecture allows for 100% of system capabilities to be fully operational, even in the event of network failures, power interruptions, or hardware component failures.
Teo Resilient Nodes can be clustered to create a Teo Resilient Network. Each additional node adds to the total possible users that can be supported, and to the resiliency of the network as a whole. Teo Resilient Nodes can be geographically distributed to minimize network traffic and better serve isolated sites in the event of wide area network failures.
Once Teo Nodes are configured to create a Teo resilient network, all system resources behave as a unified core. All individual node resources such as local PSTN interfaces, conferencing, and storage facilities are shared by the system.
Each node is aware of every other node's availability and activity at all times. In the event that a single node is unavailable due to a network, power, or component failure, the other nodes can adapt immediately without any administration interaction to keep the system 100% operational.
Teo endpoints are designed to be resilient in the case of node or network failures. If a primary node connection fails, the endpoint will automatically reregister to an available auxiliary node so that the endpoint service is not affected.