This is still very much a work-in-progress, as we’re merging two unfinished products and I’ve not had enough of a chance to test it thoroughly either so I’m hoping for some response from the community on this one. I think this is quite possibly the first time that FreePBXv3 has been tied into a major distro, and I reckon it’d be cool to see Elastix-2.0 support FreePBXv3 officially.

I have however tested Ext’s registering happily, calling each other, so I know that FreePBXv3 is tied in correctly.

Anyway, I’ve tar’d up a slightly older version of FreePBXv3, as they’re undergoing some design changes right at the moment which mean that the current version doesn’t install. So, we’ll be using this.

Total installation should only take about 5 minutes, so this How-To will be nice and short!

So what you’re going to do is start by installing the latest Elastix-2.0 RC3. In my case I used i386.

Once it’s installed, ssh into the server and run:

cd /var/www/html
wget http://c2s.co.nz/dumpfiles/freepbxv3.tar.bz2
tar xvjf freepbxv3.tar.bz2
cd freepbxv3
sh preinstall.sh

It’s 8.5MB, and this is the snapshot of FreePBXv3 that we’re going to be using.

I’ve already modified the preinstall.sh so it uses the user “asterisk” instead of “nobody”, keeping in line with how Elastix does things.

You’re going to then run the following commands to upgrade PHP:

yum install yum-priorities
cd /etc/yum.repos.d/
wget http://dev.centos.org/centos/5/CentOS-Testing.repo
yum --enablerepo=c5-testing install php
/etc/init.d/httpd restart

We need PHP-5.2 because of one of the FreePBX dependencies (Kohana) and Elastix only comes with PHP-5.1

Now you need to fire up the Elastix WebUI, but instead of just going to the regular URL, add in /freepbxv3/ to the end and you should be greeted with the install window:

Agree, hit Next.

You will be prompted with a pre-flight checklist. It should pass the lot. Again, hit Next.

Now, on the next screen, you’re going to see the database details.

Set the database to freepbxv3, the username to “root” and put in the default Elastix root MySQL password: eLaStIx.2oo7

You might also want to adjust your timezone.

Now, create a Username and a Password that you will use to access the system. Whatever you enter in here will be the email address used to log you in, it’ll create the account based off this, so remember the address / password you use. Don’t worry, this account is unique to your Elastix / FreePBXv3 installation.

On the next screen you need to change it from the FreeSWITCH driver to the Asterisk driver. All the other defaults are fine except the AMI admin password which needs to be changed to “elastix456″

The next screen will complain a little about a few bits n pieces relating to Media Management. We’re going to ignore this for now simply because I’m lazy. Scroll right the way down and hit “Next”, as the default selections suit us fine.

It will then go through and do the installation of everything:

When that’s done you’ll be taken to your newly installed FreePBXv3 system!

One thing I’ve found is that the default passwords didn’t seem to work until I modified the password on the accounts. You can do this under Destinations –> Devices

Select Device 1 and choose Edit. Adjust the password and then hit Save.

You should now be able to take a phone and register it using the Username “sip1″.

I then did the same for Device 2, registered with “sip2″ after changing the password, and was able to make calls freely between them.

Granted there’s a lot more to be tested, but that should be enough to get you pointed in the right direction. I’d love to hear from some people how they get on with this, and the blog will be updated in-future.

This has also been cross-posted at http://www.c2s.co.nz/blog/?p=380

Sunshine Networks has posted a great step by step article on how to install Fail2Ban on Elastix systems. More and more PBX systems are being hacked these days and we should be trying everything to stop hackers from getting in and making expensive calls. Fail2Ban is one more feature you can use to keep people out.

http://www.sunshinenetworks.com.au/how-to/56-install-fail2ban-on-elastix-16.html

An update for Elastix invoicing has been completed to fix a bug in the older version which caused it to report incorrectly. ICT has given their time to do this. You can find the new version on sourceforge here

http://sourceforge.net/projects/ictinvoice/

Also Elastix have asked for this module to be put into Elastix 2.0 as default. If you would like to see this happen please leave a comment saying you would like it in there.

Date: Friday June 25, 2010
Time: 10:00 – 17:00 GMT -5 (15:00 – 21:00 GMT 0)
IRC Channel: #elastix-dev
Network: irc.freenode.net

The built-in Elastix Backups is great, but only if you remember to do it. I have the memory of a sieve so unfortunately I rarely remember.

The good thing is it’s now no longer difficult for you to backup a system automatically!

Because I don’t do any faxing or the likes on my systems, it doesn’t get backed up. This also won’t backup FOP2, your amportal.conf and other such things.

Here’s what it will do:

• All core Asterisk files in /etc/asterisk
• Custom sound files used in voicemails / recordings
• Voicemail boxes
• CDR records
• FreePBX custom system files
• Differential backups from the previous day, so you’re not wasting storage space and transferring large volumes of data regularly.

It’s enough for you to basically take a stock Elastix system and be back up and running in seconds.

Scenario: Your HDD died. You didn’t have any monitoring in place and so the SMART warnings went undetected. Your system is now down. Thankfully you have the ISO of Elastix, so you quickly throw it into the machine and reinstall (Or if you’re like me, you have a “vanilla” system ready on another HDD).  It boots the brand new Elastix installation and you’re now in a position to restore from your backups.
You now restore from your backups by simply copying everything in your last daily backup to your / folder, and it overwrites everything it needs to. You quickly reimport the .sql file into MySQL and you’re back, with minimal disruption.

1. The script
2. The prep work
3. Adding it to your crontab (So it works automatically of course)
4. Testing
5. Password-less logins
6. More testing = Success!
7. Restoring

Here’s how you do it:

1) The script

#!/bin/sh
# Version 0.1
# Written by Josiah Spackman - www.c2s.co.nz

# Run on the client machine that you want to be backed up to another server
# Set the local SQL server details. Pretty generic across all Elastix, so hopefully your MySQL port isn't public
MSQLU="root"
MSQLP="eLaStIx.2oo7"

# Set the destination username and servername
DSTUSER="backupuser"
DSTHOST="destination.backupserver.com"
DSTFULLDIR="/home/backupuser"
# We want the Hostname of the current box so we can backup multiple boxes and easily distinguish them with as little modification to this script as possible
# NOTE: You need to create this Dir on the remote host prior to the first backup run
HOST="elastixtest"

# Set the local tempdir to store the files in. Default is usually sufficient
TMPBACKUPDIR="/tmp/asteriskbackup"

# Setting the day
DAY=`date +%a | tr '[A-Z]' '[a-z]'`

case $DAY in
  sun ) PDAY=sat ;;
  mon ) PDAY=sun ;;
  tue ) PDAY=mon ;;
  wed ) PDAY=tue ;;
  thu ) PDAY=wed ;;
  fri ) PDAY=thu ;;
  sat ) PDAY=fri ;;
esac

# Setting options for rsync to run with
OPTS="-aHL --link-dest=$DSTFULLDIR/$HOST/$PDAY/ --delete --stats"

# Copying everything locally and doing it all in one go
mkdir -p $TMPBACKUPDIR/etc/ $TMPBACKUPDIR/var/spool $TMPBACKUPDIR/var/lib/asterisk/sounds $TMPBACKUPDIR/var/www/html/admin/modules/core
cp -Rs /etc/asterisk $TMPBACKUPDIR/etc/
cp -Rs /var/spool/asterisk $TMPBACKUPDIR/var/spool/
cp -Rs /var/lib/asterisk/sounds/custom $TMPBACKUPDIR/var/lib/asterisk/sounds/
cp -Rs /var/www/html/admin/modules/core/etc $TMPBACKUPDIR/var/www/html/admin/modules/core/

# MySQL Dump so we have all parts of the server
mysqldump --add-drop-table -h localhost -u$MSQLU -p$MSQLP -A > $TMPBACKUPDIR/database.sql

# Running rsync now
rsync $OPTS $TMPBACKUPDIR $DSTUSER@$DSTHOST:$HOST/$DAY/

# Cleaning up afterwards, no point in keeping the database or other links...
rm -rf $TMPBACKUPDIR

Now here’s how you use it:

Copy all of that text and save it as /root/backups.sh using your favorite editor

2) The prep work

Change a few values, namely the DSTHOST, DSTUSER and DSTFULLDIR.

You need to specify the full directory where the files are stored remotely, usually this is just the home directory.

Now we’re going to give it execute permissions:

chmod +x /root/backups.sh

3) Adding it to your crontab (So it works automatically of course)

As root, run:

crontab -e

Add in the following line by pressing “i” to “insert” text:

0 1 * * * /root/backups.sh

This will run the backup every night at 1AM

To save and quit, write:

:wq

Then press enter

4) Testing

Run a test backup, by using:

sh /root/backups.sh

See if it runs OK.

Chances are it’s going to fail. This is because you need to remotely create the “host” directory. Example:

You’re backing up a machine called AcmeInc, you want to create a directory on the destination backup server called “AcmeInc” first, and then it will do the rest. This should be the same value as $HOST, remember it’s case sensitive.

Now that you’ve got your directory on the server, run it again:

sh /root/backups.sh

It should do a successful initial run.

But it doesn’t stop there.

5) Password-less logins

Up until now it’s been prompting for your password. This isn’t going to work if you’re trying to run the job automatically via a scheduled cron job, because naturally you’re not going to be around at 1AM (Or at least you shouldn’t be).

We’re going to create password-less logins with:

ssh-keygen -N '' -t rsa -f ~/.ssh/id_rsa

Now you should have /root/.ssh/id_rsa.pub so run this to see the contents

cat ~/.ssh/id_rsa.pub

Now you want to copy that and on the server you’re backing up to, you want to edit ~/.ssh/authorized_keys

Put in the contents of the id_rsa.pub file.

Now, we’re going to secure it down just a little more:

chmod 700 ~/.ssh
chmod 600 ~/.ssh/authorized_keys

Great stuff, you’re almost there!

6) More testing = Success!

Now if you run:

sh /root/backups.sh

It should complete successfully, and not ask you for a password!

What we’re now going to do is time-warp forwards a day and make sure it’s doing the differential transfers correctly. Login to your backup server and rename the folder so that the day is the previous days. For example if today is tuesday, then rename “tues” to “mon”. The day is always the first 3 chars of the day name. Easy enough yes?

Now, login to your server and make a change of some description, perhaps even create a dummy Extension, just so that some of the files will change.

Re-run the script and it should tell you it’s completed happily and it should only take a *very* short time to run, under 7 seconds for me on a barely used system.

If you see an error such as:

--link-dest arg does not exist: mon

This means your absolute path is not correct. Double-check your home dir and the DSTFULLDIR variable in the script.

7) Restoring

It’s all well and good to have a flashy system like this, but if you don’t know how to restore, it’s relatively useless. Thankfully it’s incredibly easy to restore!

Grab the contents of the last “day” that you backed up, for example yesterdays backups and save them in /root. We’ll use Tuesday as a reference. Run this on the PBX server you’re wanting to restore:

scp -r user@backup.server.com:~/hostname/tue/ /root/
cp -Rvf /root/tue/asteriskbackup/* /
mysql -u root -peLaStIx.2oo7 < /root/tue/asteriskbackup/database.sql
/etc/init.d/mysqld restart
amportal restart

However, it’s going to prompt you for each file, so you might want to edit /root/.bashrc and remove the line:

alias cp='cp -i'

It is basically forcing you each time to answer “y/n” to the cp command, even if you don’t want it to. You then need to either log out and back in again, or you could just run:

su -

Re-run the cp command and anything after it and you should now be back up and running!

As always, I’m open to feedback, comments and suggestions. If this has helped you in any way, please just leave a brief message and say Hi!

This has also been posted here: http://www.c2s.co.nz/blog/?p=328

Update 18 June 2010

Andrew the developer of the FreePBX endpoint manager has come on board to help us build the new endpoint manager. He has already added support for the Linksys/Cisco handsets for those out there using the Linksys SPA range. We will keep moving forward with the development, however with very few donations and no vendor support it will be a rocky road ahead.

Original Post 

For a long time Elastix has lacked a good endpoint manager. The current endpoint manager is very good but it lacks a lot of settings which could make the endpoint manager a valuable tool to Elastix. Many Elastix users out there waste hours and hours of time provisioning their endpoints. Going into every phone and configuring each phone is tedious and is time we could be out making more money. Setting up the endpoints is normally the most time intensive part of building an Elastix system. With a good endpoint manager we can put all this behind us.

I am looking to develop a new endpoint manager. It will look to include the following features

• Provision many different vendors such as Linksys/Cisco, Snom, Aastra, Yealink, Polycom
• Provision all functions on each phone. This includes extension, all BLF buttons and regional settings
• All settings held on the Elastix machine in a mysql database
• Phones will grab all their settings TFTP
• Endpoint manager will be able to scan for extensions and provision
• Endpoint manager will be able to create a TFTP file so that the phone can be sent to site and it will be completely provisioned remotely
• Multilanguage support

What does this mean for you?

Vendors

With a good endpoint manager this will mean less support issues for vendors. It will make it easier for users to setup and use their IP phones. Vendors will have to do less support and the users of their phones will not have to have high end technical skills to use the best features of the phone.

Elastix Users

This will save you time, whether you are installing 10 phones or 100 phones. It will also make setting up phones very easy.

What is needed from Vendors and Users?

We need you to contribute. To build a decent module that will support many different types of phones we are looking at a budget of about $10000.00. If everyone can get together we will be able to build this and it will make installing Elastix better for everyone. All code developed for this project will be given back open source to the Elastix project.

Contributors

I have put together a scale of contributing. Not everyone can contribute a lot of money but if everyone can put in then it will help us get to the goal of $10000.00. The following sponsorships are available

Gold Sponsorship – $1000.00

Silver Sponsorship – $500.00

Bronze Sponsorship – $100.00

I am behind this project 100% and have put up $1000.00 to get the ball rolling. To donate to the project you can contribute to the paypal account – elastixprojects@mbit.com.au. Once you have contributed please let me know via email on mark@mbit.com.au

Total remaining – $8900.00

Contributors

MBIT Technologues – $1000.00

Sunshine Networks – $100.00

Hitec Solutions – $100.00

 Thank you for all who contribute. We are looking to make a great new feature for Elastix that will benefit everyone.

Many Elastix installed out there will be using Elastix in a large enterprise organisation. Elastix can be a great solution for a large corporate however underneith asterisk can struggle when many extensions are loading it down. As soon as you have more than 200-300 extensions asterisk can struggle on many boxes to keep up with all the registration requests coming in. Asterisk does a fantastic job of being a great PBX however when scaling to large enterprise you need a more robust SIP Server. This is where Kamailio steps in. Kamailio is a large scale SIP server that can handle thousands of SIP extensions on one box. The problem is you need a good PBX gateway for it to connect everything together.

For this I wanted to be able to have Kamailio as my SIP server but have asterisk provide all the features it has such as voicemail. For this a FreePBX module was created that brings together Kamailio and asterisk. How it works is everything registers to Kamailio. All internal calls stay within Kamailio and if any calls created are not internal then it sends it to asterisk to manipulate. All the extensions are created in FreePBX which is handy because this means you dont have to keep a record of the extension in asterisk and Kamailio.

This allows you to take your Elastix machine from handling around 200 extensions to up around 1000 with no sweat.

If you are looking to setup an environment that needs this many extensions then please email me on mail@mbit.com.au and I can send through the FreePBX module for you to test.

That’s great if you have ABE, but not so good if you’re one of the millions of installs out there that uses vanilla Asterisk.

This guide presumes you already have ADA downloaded and installed. If not, you can get the latest (At the time of writing) version 1.1 from here:

http://dl1.digium.com/ADA1.1/ADAInstall.exe

Now you’re going to ignore any instructions you’re previously read, and we’ll start from scratch. Don’t worry, you’ll be up and running in a matter of moments!

Once ADA is downloaded, installed and running, you should be greeted with a login window.

What you now need is the “manager” user to be setup.

The “manager” user is different from your regular extension, in that it allows you to control the actions of Asterisk. With this in mind, you need to be careful when setting up an Ext, not to have a weak password, and make sure you use the permit / deny lines, even for remote extensions. You can get a password generated for you here: http://www.thebitmill.com/tools/password.html

From the shell, we’re going to edit /etc/asterisk/manager_custom.conf like this:

nano -w /etc/asterisk/manager_custom.conf

You’re now going to create a new entry with the following details, in my case I’m Ext 199:

[199]
secret=mkHHa031kHMsGRu
deny=0.0.0.0/0.0.0.0
permit=192.168.0.0/255.255.255.0
read = system,call,log,verbose,command,agent,user
write = system,call,log,verbose,command,agent,user

Now you need to create a manager user for every Ext that will be using ADA. This is because ADA uses the username part as the Ext for it to ring to connect the call to.
Without it, it would be the same as you dialing the number, and the system just sitting there, holding it.

Ctrl + X to quit nano, and you can safely get your ADA desktop client to login with the username: Ext@asteriskIP

In my case it would be something like: 199@192.168.0.250

Use the password you specified above in the manager user, and not your regular SIP Secret.

If you find you’re unable to connect, confirm that you’ve got the right password, and adjust the “permit=” line as applicable. I would highly recommend leaving it in there and just adjusting it for your IP range. Same goes for external or remote clients, make sure that you have their IP Address.

Now that you’ve done that, you need to hook ADA into your dial-plan.

Again, the standard documentation is no good here, so, we’re going to edit another file:

nano -w /etc/asterisk/extensions_custom.conf

At the top of this file (Well under the first tow lines of comments) we’re going to add in the following:

[ada]
include => from-internal

Then hit Ctrl + X and follow the prompts to save and quit.

Again the standard documentation is no good for us there, as the “ADA” context is actually “ada” in lower case, and we’ll use the “from-internal” instead of “default”.

Now you need to refresh the dial-plan (Just this once) so run this:

asterisk -rx 'dialplan reload'

You’re now all good to go! On your ADA desktop client, you can create a test call! It’s easiest to test to another Ext in my opinion, so enter in the Ext # of another extension on the system and hit “enter”.

What should happen:

Your phone will ring immediately

You pick it up and will hear ringing, the destination phone should now also be ringing

Easy!

If this has helped you in any way, please leave a comment and say Hi.

Cheers

Chill.

This basic How-To shows you how to set it up to work with your Elastix system:

First off, you’ll want the following config which is a bit of a mash-up from some other documentation on making it work with an Aastra 800 (Include the header):

#----------------------------------------------------------------#
#                                                                #
# Template for SN4554/2BIS/UI to use with Elastix                #
# Use with firmware R5.1 or higher                               #
#                                                                #
# This template uses dhcp to retrieve an IP address. Comments in #
# the file indicate what to change (Start with '#')              #
#                                                                #
# See the SmartWare Software Configuration guide for command     #
# details (http://www.patton.com/manuals/SCG-r52.pdf)            #
# Modified by Josiah Spackman                                    #
# http://chillingsilence.wordpress.com                           #
#----------------------------------------------------------------#

cli version 3.20
webserver port 80 language en

system

  ic voice 0
    low-bitrate-codec g711alaw64k

system
  clock-source 1 bri 0 0
  clock-source 2 bri 0 1

profile ppp default

profile tone-set default

profile voip default
  codec 1 g711alaw64k rx-length 20 tx-length 20
  codec 2 g711ulaw64k rx-length 20 tx-length 20
  fax transmission 1 relay t38-udp

profile pstn default

profile sip default

profile aaa default
  method 1 local
  method 2 none

context ip router

  interface IF_IP_WAN
# replace 'dhcp' with your fix IP if needed, e.g. "ipaddress 172.16.1.20 255.255.0.0"
    ipaddress dhcp
    tcp adjust-mss rx mtu
    tcp adjust-mss tx mtu

context ip router
# uncomment the following line if you need to add routing table entries
  # route 0.0.0.0 0.0.0.0 172.16.1.1

context cs switch
  national-prefix 0
  international-prefix 00

  routing-table called-e164 RT_ISDN_TO_SIP
# 'T' in the following lines specifies "digit collection". The time for collection can be adjusted replacing 'T' wih 'T2' for 2 seconds.
    route T dest-interface IF_SIP

  routing-table calling-e164 RT_SIP_TO_ISDN
    route default dest-service SV_HUNT_PSTN MP_Unknown-Subscriber

# This mapping table sets the ISDN type of number for calls towards ISDN to 'subscriber'
  mapping-table calling-e164 to calling-type-of-number MP_Unknown-Subscriber
    map default to subscriber

  interface isdn IF_ISDN_0
    route call dest-table RT_ISDN_TO_SIP

  interface isdn IF_ISDN_1
    route call dest-table RT_ISDN_TO_SIP

  interface sip IF_SIP
    bind context sip-gateway GW_SIP
    route call dest-table RT_SIP_TO_ISDN
# This is the IP of your Asterisk. Replace with domain name if DNS server is available
    remote 192.168.0.250

  service hunt-group SV_HUNT_PSTN
    drop-cause normal-unspecified
    drop-cause no-circuit-channel-available
    drop-cause network-out-of-order
    drop-cause temporary-failure
    drop-cause switching-equipment-congestion
    drop-cause access-info-discarded
    drop-cause circuit-channel-not-available
    drop-cause resources-unavailable
    route call 1 dest-interface IF_ISDN_0
    route call 2 dest-interface IF_ISDN_1

context cs switch
  no shutdown

# The parameters realm, username and password have to match your Asterisk configuration
authentication-service AUTH_AASTRA800
  realm 1 smartnode-gw
  username patton password 6953789

# The parameters domain, username, identity (=username) below have to match your Aastra800 configuration
location-service LS_AASTRA800
  domain 1 smartnode-gw

  identity-group default

    authentication inbound
      authenticate 1 authentication-service AUTH_AASTRA800 patton 6953789

  identity 6953789

    authentication inbound
      authenticate 1 authentication-service AUTH_AASTRA800 patton 6953789

    registration inbound

context sip-gateway GW_SIP

  interface WAN
    bind interface IF_IP_WAN context router port 5060

context sip-gateway GW_SIP
  bind location-service LS_AASTRA800
  no shutdown

port ethernet 0 0
  medium auto
  encapsulation ip
  bind interface IF_IP_WAN router
  no shutdown

port bri 0 0
  clock auto
  encapsulation q921

  q921
    protocol pp
    uni-side auto
    encapsulation q931

    q931
      protocol dss1
      uni-side user
      bchan-number-order ascending
      encapsulation cc-isdn
      bind interface IF_ISDN_0 switch

port bri 0 0
  no shutdown

port bri 0 1
  clock auto
  encapsulation q921

  q921
    protocol pp
    uni-side auto
    encapsulation q931

    q931
      protocol dss1
      uni-side user
      bchan-number-order ascending
      encapsulation cc-isdn
      bind interface IF_ISDN_1 switch

port bri 0 1
  no shutdown

Copy this all into a notepad window and save it as “SN4554.cfg”

What you’re going to want to modify is the references to “192.168.0.250″ and point it to your Elastix / Asterisk system.

All the ISDN ports are set to “Point-to-Point”. You can adjust the “pp” settings to “pmp” if you require “Point-to-Multipoint”, though to be honest ISDN isn’t my strong point so I’m not entirely sure how relevant that is.

This will leave the WAN port using DHCP, hopefully you’ve got a semi-intelligent DHCP server that will give out the same IP each time.

Open the WebGUI of your SN4554 up, login with the default Username “administrator” and a blank password.

Click on “Import / Export” on the left-hand side, then hit the Import Configuration tab.

Select the file, import it, then reload the device.

Now, in asterisk you want to add a new SIP trunk. Name it “ISDN” and put the following in the SIP PEER Details:

username=patton
type=friend
secret=6953789
qualify=1200
insecure=very
host=192.168.0.141
dtmfmode=RFC2833
disallow=all
context=from-pstn
canreinvite=no
allow=alaw&g729

There’s no register string or USER details, though it may be worth specifying the max channels as “4″.

You’ll need to adjust the “host” setting to the WAN IP Address of your Patton box, as we’re semi-insecure with such a basic password.

You *could* adjust the password and username in the config etc as applicable, but specifying the host should be enough, especially considering (in my instance) the whole system is LAN-accessible only.

When you’re finished, you should be able to login to your Elastix system via SSH and run:

asterisk -rx ’sip show peers’

And see:

ISDN/patton                192.168.0.141        N      5060     OK (19 ms)

If you do, congratulations, you’re ready to go!

Now you just need to setup inbound and outbound routes as applicable.

If this was useful to you, please leave a comment and say hi.

I’d also like to thank Byron from SnapperNet in New Zealand, he’s been such a great help, and also provided me with the initial configuration samples.

This How-To has also been re-posted here: http://chillingsilence.wordpress.com/2010/05/06/using-the-patton-sn4554-for-isdn-with-elastix/

I have completed an active directory module for FreePBX. I am looking for some users to help test the module in many different windows environments. This module was built so a windows admin only has to keep one directory with all their users. The module searches the active directory then lists them on a page in Elastix. From there you can select the users in the active directory and add them as an extension in Elastix. Other features

• Mobile numbers within the active directory can be used to create followme within Elastix 
• Telephone numbers within the active directory can be used to create inbound routes
• Module will detect changes within the directory and allow the user to change the settings within Elastix 

If you are a windows admin and have an interest in testing the module please email mail@mbit.com.au. In your email please include your windows setup. The module will become a commercial module however the beta testers will have free access to using the module.