SipXecs

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
SIPfoundry sipXecs
SipXecs logo.png
SipXecs Admin UI.png
Screenshot of the sipXecs Admin UI
Developer(s) SIPfoundry
Stable release 14.04.2 / July 7, 2014
Development status Active
Operating system CentOS RHEL
Platform x86-64
Available in English, prompts in 15 languages
Type IP telephony, Software as a service, CAAS
License Affero General Public License
Website www.sipfoundry.org

sipXecs is an open source enterprise communications system.[1] It was initially developed as a proprietary voice over IP telephony server in 2003 by Pingtel Corporation in Boston, MA,[2] and later extended with additional collaboration capabilities in the SIPfoundry project. Its core feature is a software implementation of the Session Initiation Protocol (SIP), which makes it an IP based communications system (IP PBX).

sipXecs is often compared to other open source telephony and softswitch solutions such as Asterisk,[3] FreeSWITCH,[4] and the SIP Express Router, but the design of sipXecs is substantially different from Asterisk and FreeSWITCH.

History

Development of sipXecs was started in 2003 by Pingtel Corp, a Boston, MA based venture backed company. In 2004, Pingtel adopted an open-source business model and contributed the codebase to the not-for-profit organization SIPfoundry.[5] It has been an open source project since then.[6]

Pingtel's assets were acquired by Bluesocket in July 2007.[7] In August 2008 the Pingtel assets were acquired from Bluesocket by Nortel.[8] Subsequent to the acquisition by Nortel, Nortel released the SCS500[9] product based on sipXecs. SCS500 was positioned as an open and software-only telephony server for the SMB market up to 500 users and received some recognition.[10] It was later renamed SCS and positioned as an Enterprise Communications System.[11]

Subsequent to the Nortel bankruptcy[12] and the acquisition of the Nortel assets by Avaya,[13] Avaya has backed away from SCS in an effort to rationalize its product portfolio post acquisition of Nortel. The sipXecs solution continued to be used as the basis for the Avaya Live cloud based communications service.

In April 2010 the founders of SIPfoundry founded eZuce.[14] eZuce commercialized the sipXecs solution in close cooperation with SIPfoundry and the open source community.

sipXecs is typically deployed by enterprises wanting to replace a traditional private branch exchange (PBX) with a software-based solution that can be produced in a cloud environment. In addition to telephony features, sipXecs offers collaboration capabilities such as enterprise instant messaging and conferencing.

Design philosophy

sipXecs is designed as a software-only, distributed cloud application. It runs on the Linux operating system CentOS or RHEL on either virtualized or physical servers. A minimum configuration allows running all of the sipXecs components on a single server, including database, all available services, and the sipXecs management. Global clusters can be built using built-in auto-configuration capabilities from the centralized management system.

sipXecs uses MongoDB as a distributed and partition tolerant database for global transactions, includes CFEngine for orchestration of clusters and JasperReports for reporting. The management and configuration system is based on the Spring Framework. sipXecs includes FreeSWITCH as its media server and Openfire for presence and instant messaging services.

sipXecs follows standards such as Session Initiation Protocol (SIP), SRTP, Extensible Messaging and Presence Protocol (XMPP), SIP and XMPP over TLS, and several Web standards including WebRTC, WebSOCKET and Representational State Transfer (REST).

Adoption

Adoption of open source solutions is difficult to quantify. SIPfoundry claims on its Web site that over one million users adopted sipXecs in small and large companies worldwide.

Amazon.com was an early adopter of sipXecs.[15] This initial 5,000 user deployment expanded considerably in the following years.

OnRelay, a company in the UK, selected sipXecs for its fixed-mobile convergence solution sold to carriers.[16]

Colorado State University and Cedarville University of Ohio committed to sipXecs in 2010.[17]

Red Hat deployed sipXecs globally in 2012.[18]

Under the SIPfoundry Higher Education Program (HEP) and as of 2014[19] Lafayette College, Holy Cross University, St. Mary's University, Messiah College, Colorado School of Mines,[20] Carthage College, and Francis Tuttle University deployed sipXecs to replace their respective PBX systems.

sipXecs is used by small and large enterprises ranging up to about 20,000[21] users per cluster. SIPfoundry lists the following users on its Web site:[19] Garrett County MD, Brevard County FL, Cash Advance America, Dutch Police, Coral Telecom, Globant, PennyMac, Easter Seals, Prosodie (Cap Gemini), Siemens Transportation, Genesys, CareSpot Healthcare, Axcess Financial, Shoreline Public Schools, British Airways.

Availability

sipXecs is available for Red Hat Linux and CentOS. It runs virtualized in different cloud environments such as the Amazon Elastic Compute Cloud, the Google Compute Engine, the HP Cloud, IBM SoftLayer, VMware vCloud and VMware ESX, OpenStack environments, and clouds from other vendors using these technologies.

Licensing and Copyright

SIPfoundry distributes the sipXecs source code under the Affero General Public License (AGPL).[22]

Many different corporate and individual contributors contributed to sipXecs,[23] including Pingtel, Bluesocket, Nortel, Avaya, and eZuce as some of the larger corporate contributors. In addition, the sipXecs solution includes many other open source components. SIPfoundry holds Copyright on all derivative work. Contributions to sipXecs are made under a Contributor Agreement, which grants SIPfoundry shared Copyright with the original author on all contributed code.

Hardware

sipXecs supports a wide range of SIP compatible hardware, such as PSTN gateways, desk phones, softphones and mobile phone applications. A plug n'play auto-configuration capability is available for phones from currently (software release 14.04) 18 different vendors.

SIP reference implementation

The sipXecs system represents a reference implementation of the SIP standard. It was used at SIPIT interoperability events organized by the SIP Forum to test interoperability of SIP solutions from many different vendors.[24]

See also

References

<templatestyles src="Reflist/styles.css" />

Cite error: Invalid <references> tag; parameter "group" is allowed only.

Use <references />, or <references group="..." />

External links


  1. ↑ Enterprise Communications System
  2. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  5. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  6. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  7. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  8. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  11. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  12. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  13. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  14. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  15. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  16. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  17. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  18. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  19. ↑ 19.0 19.1 Lua error in package.lua at line 80: module 'strict' not found.
  20. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  21. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  22. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  23. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  24. ↑ Lua error in package.lua at line 80: module 'strict' not found.
Retrieved from "https://infogalactic.com/w/index.php?title=SipXecs&oldid=706251548"