Skip to content

SIPfoundry

Narrow screen resolution Wide screen resolution Increase font size Decrease font size Default font size
Home arrow sipXecs IP PBX Project
sipXecs IP PBX Project
sipXecs Family of Projects PDF Print E-mail
Written by Administrator   
Monday, 30 October 2006

sipXecs - A native SIP based Unified Communications Solution

What is it we are trying to do?

Session Initiation Protocl (SIP) has become to real-time communications what HTTP is to Web surfing and SMP for email communication. We have set an ambitious goal for ourselves aiming at building the most interoperable, feature complete, scalable, robust and easy to use SIP unified communications system in open source.

The sipXecs solution is a new open source Enterprise unified communications solution natively based on the Session Initiation Protocol (SIP). Voice over IP (VoIP) should be easy, so sipXecs was built with that in mind. Architected as a pure SIP solution sipXecs comes complete with lots of features such as voicemail, auto-attendant, call center solution, group paging, intercom, personal attendant, find-me / follow-me, integration with Microsoft Active Directory and Exchange 2007, plug & play management, and many more.

We often get asked whether the SIP standard is mature and complete enough to implement all the features and capabilities required for a comprehensive solution. This is a legitimate questions since all the other existing commercial solutions either add proprietary extensions to the standard to "fill some gaps that otherwise could not be overcome in a standards compliant way" or merely use the SIP protocol as a transport infrastructure combined with a vendor proprietary core for call control. We think SIP is fully mature as a standard to rely on for everything that is needed to build a standards compliant unified communications solution. The sipXecs is vivid proof of this as we have yet to come accross something that cannot be implemented in a standards compliant way. 

Who do we think should use sipXecs?

A project without a clear target user group is like a speaker without an audience. Therefore sipXecs is a project with a clear focus on making something that can be used successfully for an intended purpose. sipXecs is not just an experiment, but a serious solution that aims at replacing existing PBX systems, small and large, with a better solution. 

sipXecs is architected as a fully distributed system with a centralized configuration and management application. As such all the components can run on a single server rendering a very cost effective and powerful system for the smallest offices. If configured to run on different hardware a powerful system can be created that serves thousands of users in different locations. 

sipXecs is a modular server based solution that runs on standard Linux and does not require any additional hardware as it interoperates with any SIP compliant gateway, phone or application. If offers redundancy for both servers, applications and trunk lines and therefore allows creating a system as resilient as required by the user's environment.

Why should you join the sipXecs project as a developer or tester?

If you are interested in a professional athmosphere and would like to interact with some of the industry's premier experts on the SIP protocol, the sipXecs project might be right for you. The project uses a lot of interesting technoologies and operates in a sophisticated environment using lots of tools. We are open to suggestions and good ideas and since components are fairly independent of each other you can come in and do it your way. A good example of this is the recent edition of our new group paging server, a component written in Java and using the JainSIP stack in stark contrast to the otherwise usual C++ enviroment based on the sipX SIP stack.

 

Last Updated ( Sunday, 02 March 2008 )
Read more...
 
Tag it:
Delicious
Furl it!
digg
blogmarks
De.lirio.us
YahooMyWeb
Library Components PDF Print E-mail
Written by Administrator   
Wednesday, 18 October 2006

The sipXecs solution is architected as a distributed set of independent servers. We wanted to accomplish both scalability as well as load-sharing redundancy between components. Therefore sipXecs consists of a set of application components that are independent and therefore can run either on the same server or different hardware. Typically the components communicate among themselves using SIP for signaling and XML RPC for management and control. A more detailed discussion of the architecture is on the project Wiki.

The projects below each provide one or more components (libraries, scripts, definitions) that are used by other projects; these are not generally directly usable other than by developers.

1. Call Control Server 

sipXpbx
The sipXecs umbrella project that includes process management (watchdog), Apache CGIs, presence server (RLS server) and many infrastructure scripts.
sipXproxy
The applications that performs powerful and highly configurable SIP routing. The sipXproxy project also includes the Call Detail Record collection and processing server, which runs independently.
sipXregistry
A SIP Registry / Redirect server.
sipXpublisher
A server to handle SIP SUBSCRIBE/NOTIFY handling with a flexible plugin architecture for different event types.
sipXcommserverLib
Common code shared by sipXproxy, sipXregistry, and sipXpublisher.
 
2. SIP Stack
sipXportLib
Common utility and platform abstraction functions (used by all of the other sipXecs family projects).
sipXtackLib
A SIP protocol implementation
3. Media Server
sipXvxml
Combines a VXML scripting engine with the sipXtack to support the creation of IVR and other VXML applications. Includes auto-attendant and voice mail applications. The CGI required for the media server applications is included in the sipXpbx project.
4. Paging Server
 
 5. Management and Configuration Server
sipXconfig
A SIP configuration server, supporting configuration of all of the above, and SIP UAs.
 6. Libraries
sipXcallLib
Telephony call control.
sipXmediaLib
Media streaming support (Codecs, RTP, RTCP).
Last Updated ( Sunday, 24 February 2008 )
 
Tag it:
Delicious
Furl it!
digg
blogmarks
De.lirio.us
YahooMyWeb