sipXpbx is a full-featured SIP pbx proxy. Configuration is done
via a web interface that also configures User Agents (aka SIP
phones).
From http://www.sipfoundry.org/features.html
We think sipX is the leading open source IP PBX in terms of
scalability, robustness and ease of use. The sipX IP PBX has been
successfully deployed in a lot of places. The largest known
installation serves more than 5,000 users connected to one redundant
(HA) system. Small installations go all the way down to a few users
served by very low cost hardware.
There is a detailed list of features on the sipX Wiki (it is too
long to re-produce here). Here is why you should consider using
sipX:
1) sipXconfigYou need an IP PBX that is robust, stable and easy to use
2) Need a system that offers plug & play management of all the
components including phones
3) It is a mission critical system and therefore you insist in
high-availability redundat configuration. A server failure should
not interrupt calls
4) Voice quality is important to you and therefore you want a system
that routes media peer-to-peer and not through the PBX
5) SIP standards compliance that allows flexible call routing including
SIP trunking
6) Need scalability - sipX is known to work for deployments
in excess of 5,000 users connected to one redundant server
7) Lots of features - of course, who does not want that
8) Unlimited number of simultaneous calls, and unlimited number of
trunks using distributed gateways
9) Need IT integration with no special needs for specific HW.
10) Runs on off-the-shelf Intel servers
WWW: http://sipx-wiki.calivia.com/index.php/Main_Page
family. It shares a number of common components with the rest of the
family, but can be used alone. It implements several powerful address
mapping capabilities in addtion to supporting UAC registration.
WWW: http://sipx-wiki.calivia.com/index.php/Main_Page
PR: ports/107931
Submitted by: Michael Durian <durian at shadetreesoftware.com>
packets and WAV files. It is a necessary dependancy of the sipX
project.
WWW: http://sipx-wiki.calivia.com/index.php/Main_Page
PR: ports/107931
Submitted by: Michael Durian <durian at shadetreesoftware.com>
package types can be added through a dynamically linked library
interface, configured through a simple XML plugin configuration file.
WWW: http://sipx-wiki.calivia.com/index.php/Main_Page
PR: ports/107931
Submitted by: Michael Durian <durian at shadetreesoftware.com>
various sipX components. It is a necessary dependancy of the sipX
project.
WWW: http://sipx-wiki.calivia.com/index.php/Main_Page
PR: ports/107931
Submitted by: Michael Durian <durian at shadetreesoftware.com>
processing utilities. It is a necessary dependancy of the sipX
project.
WWW: http://sipx-wiki.calivia.com/index.php/Main_Page
PR: ports/107931
Submitted by: Michael Durian <durian at shadetreesoftware.com>
abstraction APIs. It is a necessary dependancy of the sipX project.
WWW: http://sipx-wiki.calivia.com/index.php/Main_Page
PR: ports/107931
Submitted by: Michael Durian <durian at shadetreesoftware.com>
explicitely use ${SETENV} KMODDIR="${KMODDIR}" before calling sub-make. [1]
- Use 700015 as __FreeBSD_version to detect if ipw(4) is using firmware(9).
Reported by: Benjamin Close [1]
was supposed to work is useless, because if we can't trust the distfile from
the remote machine, we can't trust the signature from the same machine either.
Our MD5 and SHA256 are good for checking both the sanity and the
trustiness of distfiles.
Approved by: portmgr (erwin), erwin (mentor)
