Archive > Asterisk

Support for more hard phones

(1/2) > >>

archived:
I'm about to embark on adding support for the IAXy from Digium. It is an IAX2 hardware FXS device designed specifically to work with Asterisk. I'm planning on using the Snom 220 device template for the IAXy itself. I haven't looked at configure_snom.pl yet. Has anyone added support for any other hardphones? I have the IAXy laying around, but in the future I'd like to have a broader choice of SIP handsets. There are plenty of choices without having to go hog wild with the $300-400 Snom 220.

archived:
In our office we also have the Cisco SIP phones, but they are about $1,000.  So I don't they are so popular.

Regarding adding another phone, adding the device template is trivial--that takes 1 minute.  All you do is specify a range of mac addresses for the IAXy and a configure script (like configure_IAXy.sh).  Then when the dhcp server detects a new request from a device within that range, it automatically adds an instance of the IAXy device, and calls the configure script, passing in the IP Address, Mac Address, and device ID as parameters.  So all that is trivial.

The work is in the configure script itself, since that's what has to do whatever needs to be done to make the device work.  configure_snom.pl won't help too much since it's specific to the Snom.  The Snom's have a built in web browser used to do the configuring.  So what configure_snom.pl does is use wget and other internet tools to programatatically fill in the Snom's web page with the device ID, the server, etc., and then programmatically hit 'update' (a form submit).  So the configure script has nothing really to do with Pluto--it's purely for setting up the phone.

That process is likely to be completely different on the IAXy device, so I'm not sure anything in the configure_snom.pl can be shared.

archived:
BTW, hopefully by tonight we will post the .23 release, which includes AMP.  This also changes some things.  Before we used our own Asterisk configuration pages, which were mysql driven.  However, the mysql back-end for Asterisk doesn't seem to be widely used or tested--it's quite new.  And, we figured it's best to use an off-the-shelf Asterisk portal that is full-featured.  So starting with .23, the AMP configuration files become the 'master'.  Dan T wrote a script that sync's Pluto's own Device database to match what's in AMP's--but the AMP data is the master.

So, we may need to change our configure_snom, and also any new scripts going forward should add the device to AMP's config whan they detect the phone.

archived:

--- Quote from: "aaron.b" ---....

Regarding adding another phone, adding the device template is trivial--that takes 1 minute.  All you do is specify a range of mac addresses for the IAXy and a configure script (like configure_IAXy.sh).  Then when the dhcp server detects a new request from a device within that range, it automatically adds an instance of the IAXy device, and calls the configure script, passing in the IP Address, Mac Address, and device ID as parameters.  So all that is trivial.

...
--- End quote ---


Hi,

I'm curious how do you get info on MAC ranges for specific HW devices - do manufacturers suply them ? Anyone else ?

BTW, I'm looking forward to this functionality in Pluto....

I'll try to add plug&play support for Grandstream phones (I think there is a way to put certain files on tftp server to configure them automatically)...


Regards,

Rob.

archived:
http://coffer.com/mac_find/

Navigation

[0] Message Index

[#] Next page

Sitemap 
Go to full version