| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
PR: ports/116639
Submitted by: aDe
Notes:
svn path=/head/; revision=200411
|
| |
|
|
|
|
|
|
|
|
| |
fully chrooted DESTDIR, which does not need such any more.
Sponsored by: Google Summer of Code 2007
Approved by: portmgr (pav)
Notes:
svn path=/head/; revision=197075
|
| |
|
|
|
|
|
|
|
| |
- plist cleanup
Submitted by: Mike Durian <durian@shadetreesoftware.com>
Notes:
svn path=/head/; revision=192438
|
| |
|
|
| |
Notes:
svn path=/head/; revision=191683
|
| |
|
|
|
|
|
|
| |
- Set X11BASE to ${LOCALBASE} for recent ${OSVERSION}.
- Bump PORTREVISION for ports intalling files in ${X11BASE}.
Notes:
svn path=/head/; revision=191544
|
| |
|
|
|
|
|
|
|
|
|
|
| |
build problem with sipxpbx
- Bump PORTREVISION
PR: ports/111152
Submitted by: Mike Durian <durian@shadetreesoftware.com> (maintainer)
Approved by: miwi (mentor)
Notes:
svn path=/head/; revision=189036
|
| |
|
|
|
|
|
|
|
|
|
| |
it installs. Perviously, the toplevel port, sipxpbx, changed ownership for
not only its files, but all the dependant ports too.
- Bump PORTREVISION
Submitted by: Mike Durian <durian@shadetreesoftware.com> (maintainer)
Notes:
svn path=/head/; revision=188478
|
| |
|
|
|
|
|
|
|
|
| |
- Fix point to the correct locations for INSTALL.ssl
- Bump PORTREVISION
Submitted by: Mike Durian <durian@shadetreesoftware.com> (maintainer)
Notes:
svn path=/head/; revision=184932
|
| |
|
|
|
|
|
|
|
| |
mod_cplusplus no longer core dumps.
Submitted by: Mike Durian <durian@shadetreesoftware.com> (maintainer)
Notes:
svn path=/head/; revision=184442
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
Notes:
svn path=/head/; revision=183919
|
|
|
WWW: http://sipx-wiki.calivia.com/index.php/Main_Page
PR: ports/107931
Submitted by: Michael Durian <durian at shadetreesoftware.com>
Notes:
svn path=/head/; revision=183914
|
