...
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 Removed |
 Image 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
- B2BUA server (sipXbridge) released with version 4.0
- Conference bridge included in package
- Freeswitch based Auto Attendant and Voicemail integrated
|
...