Social Business starts with communications. What use are all the social networks without the ability to communicate?
- One place for unified presence: Unified means that the user has all information relevant to presence aggregated in one system
- One buddy or friends list: Users want integration. Just because 'Social' is the new trend it makes no sense to add a buddy list to every system in the universe.
sipXecs communications enables Social Business, bringing together real-time and non real-time communications into one place. Thought this would be easy? Now it is!
Concerned about the money you spend on IT infrastructure? Architecture matters.
- Manageability and ease of use translate into operating cost savings
- Open systems give you choice and prevent vendor lock-in
- Architecture facilitates cloud deployments, virtualization, and centralization
Six years of concerted effort were required to build sipXecs. Now it is mature and ready to be used in large and smaller enterprises. The transition to software and IT changes everything.
Communications enabling the Web and IT is so different from what commuications used to be.
Come try it out.
Take sipXecs for a test drive.
SIP Service Oriented Architecture TM (SSOA) is fundamentally different in its basic concepts as compared to the architecture of typical legacy PBX systems and first generation IP phone systems. Legacy and first generation PBX systems were not designed as native SIP systems, but instead SIP capabilities were added later to an already existing design. This resulted in systems whereby SIP is primarily used as a message transport protocol alongside other proprietary IP protocols such as Nortel Unistim and Cisco Skinny, and in addition to TDM transport still available in hybrid systems. Communication features for the most part remained implemented in a legacy feature server, a new term for an old PBX, and not using the SIP standard. Therefore, such legacy systems have very different scalability and redundancy characteristics, and the enormous level of complexity of such legacy hybrid systems makes them costly to own and maintain and undesirable for a modern IT environment.
Key SSOA Design objectives
In developing SSOA the following key design objectives were at the center of consideration:
Instead of an (IP) PBX system connected to the network, we wanted to embed SIP session management and routing into the network, thereby creating a load-sharing and self-healing distributed infrastructure capable of controlling real-time communications as part of the infrastructure. That ruled out using Back-to-Back User Agent (B2BUA) designs and instead asked for a native SIP proxy based design, laid out as a resilient SIP message router in the network.
We needed a significant reduction in overall system complexity in order to achieve our goal of creating a much simpler system that is easy and cost-effective to administer without compromising critical functionality. Therefore, SSOA disaggregates features into individual components or services that run as independent applications. These independent components or services communicate over SIP with the rest of the system. Additionally, to maintain system simplicity SSOA introduces a single Web based configuration and management application, eliminating all the legacy element managers and manager of managers hierarchy seen in many legacy systems.
For scale and redundancy we needed a distributed system that could seamlessly load-share at the transaction level. The requirement for ultimate extension mobility without requiring the usual branch prefix based addressing required a global address space with all user credentials, permissions, aliases and registration information available to all participating call control systems at all times. To sustain scalability and overall simplicity of the architecture, we could not rely on a centralized database to be in the transaction path as a bottle neck and single point of failure, but instead introduced an innovative distributed data replication mechanism based on a NoSQL1 data store that is ‘eventually consistent', always available, and fast.
Because communications is a real-time application and in order to allow distributed environments to be configured as one global, centrally managed system we needed to strictly separate media from SIP signaling. This offers key advantages: a) server failures do not interrupt calls, b) no limitation on the maximum number of concurrent calls, c) codec agnostic call servers with end points solely responsible to negotiate the codec used, d) WAN bandwidth savings with local media that stays in a local geography even if the call servers are centralized, and e) better voice and video quality due to lower latency and jitter.
- For unified presence and Instant Messaging (IM) the requirement was for a standard based and widely used protocol that allows for the widest possible interoperability and federation between systems and organizations. For SSOA we chose XMPP as the protocol of choice allowing native federation with systems such as Google Talk, Cisco CallManager presence & IM, and many Jabber based enterprise systems in use today. SSOA provides for a tight integration between SIP session management and XMPP presence and IM, allowing unified presence to be exchanged with clients that use the XMPP protocol, but also with clients that use the SIP/SIMPLE protocol for presence and IM.
SSOA is a SIP Session Manager based design that takes this concept significantly beyond just SIP call routing to include extension mobility, branch resiliency, seamless load-sharing among a large number of peer nodes, seamless redundancy and server failover, trunk failover, unified presence and instant messaging. In addition, SSOA enables federation between systems and organizations, and a significantly simplified management using Web Services based centralized management with a modeling and plugin infrastructure that accommodates all the system components, including third party devices such as phones and gateways delivering a pure plug n' play experience. An SSOA system provides the flexibility to be deployed as distributed or centralized as required for a particular customer, creating one large system that provides cohesive and centrally managed communications services. SIP call control becomes a service in the network like IP routing itself.