Elastix IPBX安装指南

需积分: 14 118 浏览量更新于2024-08-02 收藏 10.34MB PDF 举报

"Elastix without Tears - 一本关于Elastix IPBX分布发展的ICT连载书籍，作者Ben Sharif，适用于Elastix v1.x-x与unembedded freePBX®2.x，版本1.6e，始终是草案状态并持续更新。" "Elastix without Tears" 是一本专注于Elastix IPBX系统使用的指南，由Ben Sharif编写，他同时也是《Asterisk@Home without tears》和《Trixbox® without tears》的作者。这本书旨在帮助读者轻松理解和部署Elastix VoIP解决方案，降低使用过程中的复杂性。 Elastix 是一个开源的统一通信平台，它基于 Asterisk 开源PBX系统，并集成了多种VoIP相关服务，如呼叫中心功能、传真服务器、视频会议等。该书针对Elastix v1.x到x的版本，同时兼容未嵌入的freePBX®2.x版本。freePBX是一个流行的PBX管理界面，提供图形化的工具来配置和管理Asterisk。文档的修订版1.6e表明它在发布时已经经过多次改进，而“ALWAYS A DRAFT”则提示读者，这个文档始终处于动态更新的状态，可能包含最新的技术信息和修正。作者鼓励读者如果发现错误或有建议，可以通过电子邮件（bensharif@gmail.com）与他联系，以促进文档的完善。此外，书中还包含了对Elastix的安装、配置、维护以及故障排查等方面的指导，帮助用户充分利用Elastix的功能，实现高效、稳定的VoIP通信环境。虽然提供的内容片段没有深入细节，但可以推测全书会涵盖如何设置电话线路、创建拨号计划、管理用户账户、设置IVR（交互式语音应答）系统、监控系统性能等多个关键主题。对于想要深入了解Elastix并希望在其上构建企业通信解决方案的人来说，"Elastix without Tears" 是一份宝贵的资源。这本书不仅提供了技术指导，还体现了开源社区的共享精神，通过作者的不断更新和完善，确保了内容的时效性和实用性。

Elastix Without Tears Page 16 of 287

I.III.V VOIP Service Providers

If you are in Australia, the Whirlpool VOIP forum has a list of VOIP providers in

Australia at the following link:

http://forums.whirlpool.net.au/forum-replies.cfm?t=370536

Elastix Without Tears Page 17 of 287

1 INITIAL PREPARATION AND PLANNING

1.1 FAMILIARISATION

Before setting up your IP PBX, it is recommended that you familiarise yourself with the

Elastix GUI and make a note of all the default passwords.

1.1.1 Default passwords

Interface Login Password

Elastix admin palosanto

freePBX admin admin

FOP admin eLaStIx.2oo7

Calling Cards (A2Billing) admin mypassword

MySQL mysql –p (from root) eLaStIx.2oo7

SugarCRM admin password

vTiger admin admin

Openfire admin Whatever set at

install

All other Elastix related password can be found in /etc/amportal.conf

1.2 MAP YOUR REQUIREMENTS

Map out what your home (or small office) telephony requirements are and compare the

requirements with what facility you already have. You may find that you may need to

provide extra facilities that you do not already have e.g. Network switches, router, ATAs

or IP Phones and needless to say a suitable broadband service.

For the purpose of this guide, I have determined that we will start with the following:

• 2 extensions with voicemail using a Linksys PAP2 ATA

• 1 extension using a Linksys SPA3000 ATA

• 2 extension using Softphone (we will use these 2 extension for initial testing)

• 3 extension using IP Phones

• 2 VoIP service providers

• 2 PSTN trunks – for the purpose of this exercise, I will be using a Linksys

SPA3000 for one PSTN trunk and a X100P for the other PSTN trunk.

• IVR and MOH

• A number of customised voice prompts and announcements

Once the above are set-up, I will customise it further with the following;

• Time conditions

• Ring groups

• Follow me

• Conference facility

• DISA etc

In this exercise we will cover all of the above (not necessarily in the stated sequence) and

we may also look at other possibilities as we go along, if time and/or resources permit.



This is not an industrial grade installation. This installation is for training purposes

only and to assist new hopeful to get started with Elastix and nothing more.

Elastix Without Tears Page 18 of 287

1.3 PLAN YOUR SECURITY

This part of the setting is most important and cannot be over stated.

1.3.1 Tim Yardley’s Securing Trixbox CE

For starter, the document written by TimYardley is a must read. While this document

refers to Trixbox CE, it applies equally to Elastix. This document on securing your box

can be found here:

http://engineertim.com/wp-content/uploads/2008/12/securing_trixbox_ce_ver1.pdf

1.3.2 Seven Easy Steps to Better SIP Security on Asterisk

(by J Todd http://blogs.digium.com/2009/03/28/sip-security/)

1) Don’t accept SIP authentication requests from all IP addresses. Use the

“permit=” and “deny=” lines in sip.conf to only allow a reasonable subset of IP

addresses to reach each listed extension/user in your sip.conf file. Even if you

accept inbound calls from “anywhere” (via [default]) don’t let those users reach

authenticated elements!

2) Set “alwaysauthreject=yes” in your sip.conf file. This option has been around

for a while (since 1.2?) but the default is “no”, which allows extension information

leakage. Setting this to “yes” will reject bad authentication requests on valid

usernames with the same rejection information as with invalid usernames,

denying remote attackers the ability to detect existing extensions with brute-force

guessing attacks.

3) Use STRONG passwords for SIP entities. This is probably the most important

step you can take. Don’t just concatenate two words together and suffix it with

“1″ - if you’ve seen how sophisticated the tools are that guess passwords, you’d

understand that trivial obfuscation like that is a minor hindrance to a modern

CPU. Use symbols, numbers, and a mix of upper and lowercase letters at least

12 digits long.

4) Block your AMI manager ports. Use “permit=” and “deny=” lines in

manager.conf to reduce inbound connections to known hosts only. Use strong

passwords here, again at least 12 characters with a complex mix of symbols,

numbers, and letters.

5) Allow only one or two calls at a time per SIP entity, where possible. At the

worst, limiting your exposure to toll fraud is a wise thing to do. This also limits

your exposure when legitimate password holders on your system lose control of

their passphrase - writing it on the bottom of the SIP phone, for instance, which

I’ve seen.

6) Make your SIP usernames different than your extensions. While it is

convenient to have extension “1234″ map to SIP entry “1234″ which is also SIP

user “1234″, this is an easy target for attackers to guess SIP authentication

names. Use the MAC address of the device, or some sort of combination of a

common phrase + extension MD5 hash (example: from a shell prompt, try “md5 -

s ThePassword5000″)

7) Ensure your [default] context is secure. Don’t allow unauthenticated callers to

reach any contexts that allow toll calls. Permit only a limited number of active

calls through your default context (use the “GROUP” function as a counter.)

Prohibit unauthenticated calls entirely (if you don’t want them) by setting

“allowguest=no” in the [general] part of sip.conf.

Elastix Without Tears Page 20 of 287

2 A BRIEF COURSE IN NETWORK DESIGN

(Using Elastix)

One of the most common issues that appears on the forums, are issues that users are

having with Asterisk based distributions, which includes Elastix.

Elastix has done a great job of improving how this is setup on your system, but it still

needs some thought put into the process.

This chapter is by no means the “be all and end all” in Network theory, and in fact many

network aficionados would probably cringe with some terminology and explanations in

this chapter, but the purpose is for you to gain a basic understanding of what you are

typing in as it will and does have an impact on how your system behaves, and how

software interacts with your Elastix system.

First of all, when your Elastix box is finally built, it comes up on the network using a DHCP

Address. For 99% of users this will be true. You either have a Dedicated DHCP Server on

the Network or your Router is acting as a DHCP Server. What this means is that your

Elastix system is assigned a dynamic IP address on your Network, which will last about 7-

8 Days (normally). After that time period, it will request a new address. In most cases it is

allocated the same address, unless you have a busy network, where in some cases it

may allocate that address to another device.

So the first thing we need to do is to allocate and set a static IP address for your Elastix

System. But before we can do this, we need to understand how your Network is setup,

which includes your Domain Name Service (DNS) entries, the domain name of your

Elastix System, whether you are going to make your Elastix system available from the

Web (e.g. externally connected Phones).

Let’s ignore the Elastix system for the time being and assume that you have a basic

Network system. You have one or two Windows workstations connected to a router and

this router connects to the Internet. This router has probably allocated IP addresses to

the workstations, and it would be useful to obtain the information from one of these

workstations to allow us to correctly fill in the Elastix Network Details.

On one of the Windows workstations, click on the Green START button, and from the

Menu select RUN. Now in the box type the letters cmd and click on OK. See the

illustration below if you are not sure what it is.

Next a black box will come up. Don’t worry if the directory is not the same, as long as it

comes up with a prompt.

剩余286页未读，继续阅读

free_bird816

粉丝: 2
资源: 6

Elastix IPBX安装指南

elastix2.4汉化

elastix中文语音包

elastix without tears

Elastix 中文版用户手册+Elastix_without_tears(Elastix没有眼泪英文版)

matlab_elastix：MATLAB Elastix包装器

elastix 用户手册

如何使用Elastix

elastix配准参数

elastix_napari:用于itk-elastix的napari插件

Laravel开发-elastix

最新资源