Elastix Endpoint Manager

 

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.

  • Share/Bookmark

10 Responses to “Elastix Endpoint Manager”

  1. Tweets that mention Elastix Blogs » Blog Archive » Elastix Endpoint Manager -- Topsy.com Says:

    [...] This post was mentioned on Twitter by rbonifaz, elastix. elastix said: We need your help to improve #Elastix Endpoint Manager: http://ur1.ca/06goh #asterisk #voip [...]

  2. Franck Danard Says:

    Hi Marsk

    The idea that I had, it was to detect automanically the device (vendor, model) and register it. With. A mixe of nmap and arp commands and compare these inforamations with the sip agent type into asterisk.

    regards

  3. Franck Danard Says:

    oups..Mark :) Sorry.

  4. Ali Onur Uyar Says:

    I would recommend you to check the Phone Provisioning functionality of sipXecs (http://www.sipfoundry.org) before defining the design specs.

  5. Mark Brooker Says:

    Thanks for the suggestions Franck and Ali

    Franck – This will definitely be part of the model. Pulling information from FreePBX and using the phone data to bring the phone up with a couple of clicks.

    Ali – I have had a look at their spec and it looks very good. At this point we have a list of features we would like to start with but we need a budget to start developing. Palosanto cant develop everything and if the community cant come together then this project will fail.

  6. Chito Says:

    have you look at the phone provisioning tools written for Freepbx? http://projects.colsolgrp.net/projects/show/endpointman

    What will you add additional to this although I line the sipx one much better

  7. Mark Brooker Says:

    HI Chito

    Thanks for the reference. The endpointman module has come a long way since I last saw it. I will be contacting the developer to see if we can bring something together on this. I would not like to reinvent the wheel if i dont have to.

  8. Andrew Says:

    Hello,

    Just letting you all know that I’d love to work with you on this project with you.

    -Andrew (Developer of http://projects.colsolgrp.net/projects/show/endpointman)

  9. Vijay Says:

    From remote office we are not able to connect ip phone with elatix
    its very very leack faclity in Endpoint manger.
    Becoue of this reason costomer not ready to get install elastix

  10. Mark Brooker Says:

    Well help the endpoint manager by contributing and we can improve it.

Leave a Reply