User Tools
voice:pbx:freepbx_distro
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
voice:pbx:freepbx_distro [2012/04/10 13:02] gcooper |
— (current) | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== FreePBX Distro ====== | ||
| - | http:// | ||
| - | |||
| - | The FreePBX distro is: | ||
| - | |||
| - | * A complete bare-metal iPBX | ||
| - | * Based on CentOS 5.7 | ||
| - | * Includes Asterisk 1.8 | ||
| - | * Includes Fail2Ban | ||
| - | * Initial memory usage is under 130MB | ||
| - | * iSymphony is integrated as the Operator Panel | ||
| - | |||
| - | ===== Updating ===== | ||
| - | |||
| - | http:// | ||
| - | |||
| - | ===== Installation ===== | ||
| - | |||
| - | Netinstall: http:// | ||
| - | |||
| - | http:// | ||
| - | |||
| - | * Set the first interface to DHCP if possible | ||
| - | * Set a DHCP reservation, | ||
| - | * Set the root password during install | ||
| - | * Set the administrative username and password on first login with a web browser | ||
| - | |||
| - | ===== First Steps ===== | ||
| - | |||
| - | http:// | ||
| - | |||
| - | ===== Trunks ===== | ||
| - | |||
| - | ==== DAHDI (ZAP) ==== | ||
| - | |||
| - | FIXME | ||
| - | |||
| - | http:// | ||
| - | |||
| - | * DAHDI is the newer interface for TDM cards | ||
| - | * ZAP is the old name | ||
| - | * When naming a ZAP/DAHDI trunk | ||
| - | * ' | ||
| - | * ' | ||
| - | |||
| - | ==== Mediatrix ==== | ||
| - | |||
| - | FIXME | ||
| - | |||
| - | http:// | ||
| - | |||
| - | http:// | ||
| - | |||
| - | Create a trunk | ||
| - | Mediatrix gateway is SIP trunk | ||
| - | Name, Description, | ||
| - | No authentication | ||
| - | Routes -> Inbound Routes | ||
| - | Create a new inbound route | ||
| - | Choose a DID number to use (such as 999) | ||
| - | |||
| - | Also, you can create a new Feature extension and use that. Security implications? | ||
| - | |||
| - | On the Mediatrix 1204 gateway | ||
| - | No authentication | ||
| - | Point ports to extension 999 on server for inbound calls | ||
| - | See setup info on web site for SAIL | ||
| - | Logging | ||
| - | Device Info -> Monitoring | ||
| - | Enable syslog to PBX IP | ||
| - | On PBX, enable remote logging | ||
| - | vi / | ||
| - | add ' | ||
| - | service syslog restart | ||
| - | |||
| - | ==== Vitelity ==== | ||
| - | |||
| - | * You can use Vitelity either as a registered or an IP-routed trunk | ||
| - | * Vitelity recommends using the more efficient IP-routed method to connect PBXs with static IPs | ||
| - | * You must specify a single CLID for a ' | ||
| - | * You can manipulate the CLID normally for ' | ||
| - | |||
| - | === PBX With Dynamic IP === | ||
| - | |||
| - | ^Caller ID^Number^Comment^ | ||
| - | |Outbound CLID|XXXXXXXXXX|Extension CLID overrides trunk CLID| | ||
| - | |||
| - | ^Prepend^^ | ||
| - | |1520|NXXXXXX| | ||
| - | |1|NXXNXXXXXX| | ||
| - | |||
| - | ^Outgoing Settings^ | ||
| - | |vitelity-outbound| | ||
| - | |||
| - | < | ||
| - | type=friend | ||
| - | dtmfmode=auto | ||
| - | host=outbound.vitelity.net | ||
| - | username=your_vitelity_login_name | ||
| - | fromuser=your_vitelity_login_name | ||
| - | trustrpid=yes | ||
| - | sendrpid=yes | ||
| - | secret=your_vitelity_password | ||
| - | allow=all | ||
| - | nat=yes | ||
| - | canreinvite=no | ||
| - | qualify=yes | ||
| - | </ | ||
| - | |||
| - | ^Incoming Settings^ | ||
| - | |vitelity-inbound| | ||
| - | |||
| - | < | ||
| - | type=friend | ||
| - | dtmfmode=auto | ||
| - | host=inbound23.vitelity.net | ||
| - | context=from-trunk | ||
| - | username=your_vitelity_login_name | ||
| - | secret=your_vitelity_password | ||
| - | allow=all | ||
| - | insecure=very | ||
| - | nat=yes | ||
| - | canreinvite=no | ||
| - | qualify=yes | ||
| - | </ | ||
| - | |||
| - | ^Registration^^ | ||
| - | |Register String|your_vitelity_login_name: | ||
| - | |||
| - | === PBX With Static IP === | ||
| - | |||
| - | FIXME | ||
| - | |||
| - | IP-routed method shown here with separate trunks for inbound and outbound. | ||
| - | |||
| - | Note that you can only manipulate outbound caller ID if using IP routing. | ||
| - | |||
| - | Create SIP Trunk | ||
| - | Name: vitel-inbound | ||
| - | Description: | ||
| - | Host: inbound23.vitelity.net | ||
| - | Direction: Inbound | ||
| - | Context: from-outside | ||
| - | Caller ID: Sonora Comm < | ||
| - | Codecs: G.711u, G.729, GSM # order by preference | ||
| - | DTMF mode: Auto | ||
| - | Other options: insecure=very | ||
| - | Provider' | ||
| - | |||
| - | Clone the inbound trunk to create the outbound trunk: | ||
| - | |||
| - | Name: vitel-outbound | ||
| - | Host: 64.2.142.93 | ||
| - | Description: | ||
| - | Direction: Outbound | ||
| - | Context: from-inside | ||
| - | Codecs: G.711u, G.729, GSM | ||
| - | DTMF mode: Auto | ||
| - | Provider' | ||
| - | |||
| - | ===== Day/Night Mode ===== | ||
| - | |||
| - | http:// | ||
voice/pbx/freepbx_distro.1334084569.txt.gz · Last modified: 2012/04/10 13:02 by gcooper
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
