Deploying the sipXecs IP PBX is easy and installation is usually done in hours. Because of its Web based administration interface as well as the ability of sipXecs to put the users in control, ongoing system administration is easily done by a receptionist or similar person. The following examples are intended to give some typical and therefore recommended system configurations. They range from very small deployments at small offices with a few users up to very large and therefore fully redundant deployments serving several thousand users.
The sipXecs IP PBX is designed to be the ideal enterprise IP voice solution for any office, starting at 4 to 12 users with 4 analog trunk lines up to several hundred users in a single location using one or several digital trunk lines (T1 / PRI). It's hardware cost are low and operating expenses are minimized by leveraging low-cost computer servers, commodity hardware, and Linux. sipXecs connects to the telephone network (PSTN) using traditional analog (FXO) or digital (T1 / E1 / PRI) trunks. Alternatively sipXecs can leverage SIP trunking services provided by a service provider (ITSP). This configuration requires a SIP-aware firewall or Session Border Controller (SBC) to securely traverse the Enterprise firewall and NAT. Possible solutions we tested include SBCs from Ingate or Intertex. Connecting remote workers either requires a corporate Virtual Private Network (VPN) or an SBC capable of offering services to remote workers. A native sipXecs based solution for SIP trunking and remote workers is in progress (project sipXbridge).
The sipXecs IP PBX can scale up easily using more powerful servers or by distributing its components over more than one server. Such configurations can serve up to several thousand users per location and are also suited for multi-branch deployments. Branch offices can have different configurations: a) The branch office runs its own instance of sipXecs, b) The branch office uses the corporate IP network to connect to sipXecs running in a central location, and c) Each branch office can have a redundant or non-redundant configuration of sipXecs. Each branch office can have local gateways. This can improve resiliency for emergency calls, offer least-cost routing, or off-load the corporate WAN network connecting calls directly to the telephone network locally.
The sipXecs IP PBX provides a complete solution to your enterprise telephony needs. The system’s architecture lets you easily distribute servers, gateways and intelligence strategically on your network, within one office or among branch offices, for cost savings, high reliability, backup and load balancing. Capabilities such as automatic trunk fail-over and redundancy, high-availability, and least cost routing are must-have features in today’s environment.
Bundles are given below for the following scenarios:
- Small office with 4 to 12 users using analog trunk lines
- Small office with 12 to 25 users using analog trunk lines
- Mid-size office up to about 100 users using a single T1 / E1 digital trunk
- Mid-size office up to about 200 users using a dual T1 / E1 digital trunk
- Mid-size office up to about 400 users using a quad T1 / E1 digital trunk
- Large office up to about 1000 users using 8 T1 / E1 digital trunks
- Large office up to about 5,000 users
Recommended phones for both desk phones, attendant consoles and softphones are valid across all deployments. Capabilities of phones vary and the recommended list given below is based on high quality phones with excellent support in sipXecs (meaning they are tested across different firmware releases). Phone support is based on simple plugins. If the phone you like is either not on the list or not well supported it is fairly easy to fix.
The reason for recommending Audiocodes gateways is simple: The sipXecs IP PBX supports plug & play management for Audiocodes gateways, which greatly simplifies deployment. In addition we have done the most testing with Audiocodes gateways and they are therefore known to work. Audiocodes does not pay SIPfoundry to advertise its gateways. Other gateways known to work are from Cisco or Patton Electronics, although for now they need to be manually configured. Other SIP compliant gateways most likely will work too, but have not been as extensively tested.
Deployment for a small office with between 4 and 12 users:
| < Prev |
|---|