Versions Compared

Version Old Version 4 New Version 5
Changes made by

Former user

Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The SIP protocol was designed in support of a fully distributed architecture where different features are provided by servers that again communicate among themselves using the SIP protocol. There is a strict separation between Media and Signaling, which allows a globally scalable system to be built with the necessary redundancy and resiliency. Media streams, once setup, flow directly between end-points (phones and gateways) without any requirement for media to go through a central signaling server.

Image RemovedImage Added

Highlights

  • Modular: 12 different server components that can coexist on one server HW or be distributed to different systems
  • Resilient: Offers HA redundancy between call control components
  • Scalability: Load balancing using the DNS SRV system
  • SIP Proxy based: sipXecs is not based on a B2BUA but implements a true SIP proxy architecture
  • Better Voice Quality: Media goes direct point-to-point between the end points and never through the call control system
  • Standard SIP: sipXecs is all about a standards compliant implementation
  • Plug & Play Management: Phones are managed plug & play from within the system
  • IT Integration: LDAP, SOAP, and database integration. System looks like and operates like an IT application
  • No Special HW: sipXecs does not require any special HW. A standard Intel server will do
  • Features: Yes, there are lots of them
  • Roadmap: Yes, got a clear and public roadmap

    Comments

  • B2BUA server (sipXbridge) released with version 4.0
  • Conference bridge included in package
  • Freeswitch based Auto Attendant and Voicemail integrated

 

 

 Given its architecture, the sipXecs system is designed to interoperate with other third party feature servers. In addition, as we accomplished our objective of a truly distributed system, several instances of every component can be run on dedicated hardware and in different geographical locations to render a very scalable system. The sipXecs Configuration Server provides plug & play management for core components, all feature servers, as well as connected peripherals such as phones and gateways. An XML-based plug-in framework allows easy inclusion of additional components, both feature servers as well as additional peripherals. Documentation exists about how to add support for additional [phones] and [gateways].

...