Skip to end of metadata
  • Created by Former user, last modified by Former user on Feb 11, 2011
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Introduction

sipXecs, the Open Source SIP PBX for Linux is based on a fully distributed architecture that allows you to leverage any SIP compliant component anywhere in the network. In particular, PSTN / SIP gateways can be added as autonomous devices (with their own IP address) where sipx provides centralized configuration and management (certain vendor's models), and flexible XML-based call routing including least cost routing of calls and load balancing. Redundancy and HA is therefore achieved easily as an inherit feature of the chosen architecture. The sipXecs system also scales using load balancing mechanisms that rely on DNS SRV records and providfe alternative routes on demand to distributed gateways. In particular, this means that for large PBX systems a large number of PSTN gateways and phones register with a few strategically located sipXecs servers. In contrast to other systems, SIP strictly separates between media (RTP) traffic and signalling (SIP) traffic optimizing performance for both.

For more information on how to add additional gateways and phones refer to:

Supported Enterprise SIP VoIP Gateways

Any SIP compliant gateway is compatible with sipX and should work just fine.

SIP Media Gateways

Residential and SOHO SIP VoIP Gateways

All the gateways and terminal adaptors below are claimed to be SIP compliant by their respective manufacturers and therefore should work with sipX.

Digium and Sangoma gateway cards

Digium and Sangoma cards at present cannot be used with sipX as there is no SIP driver software available. However, a PC running the Asterisk PBX or the Yate Telephony Software in conjunction with Digium or Sangoma cards can serve as a media gateway for sipXecs.

VoIP SIP Firewalls

  • No labels