[asterisk-users] PAP2T provisioning

[Jeff LaCoursiere]

On Wed, 21 Jan 2009, Andres wrote:

> Why don't you just edit the Trixbox endpoint manager files.  They
> produce basic XML files for Linksys and Polycom phones.  It is trivial
> to add support for any Linksys ATA as well.
>
> File is:  /var/www/html/maint/modules/11_endpointcfg/endpoint_linksys.php
>
> Just start by editing this line: $smarty->assign("phone_types",
> array('SPA942' => 'SPA942', 'SPA941' => 'SPA941', 'SPA921' => 'SPA921',
> 'SPA922' => 'SPA922', 'SPA962' => 'SPA962','SPA2102' => 'SPA2102'));
>
> ...and add the devices you need.  As you can see we already added the
> SPA2102.
>
>

I looked at this briefly a while back and although it does give you a nice 
GUI to manage your endpoints, I still prefer my text file method. 
Consider it this way - to setup a new 50 station system I generally get a 
spreadsheet from the client with names and extension numbers.  I can 
quickly turn this into a text file that I currently process with a csh 
script that turns out the Polycom XML files and creates the extensions in 
the Trixbox database.

Otherwise I would be hand entering all the Trixbox extensions, then again 
hand entering all the devices with MAC addresses to tie them to the 
extensions.

A new project has 40 PAP2Ts involved, and I hadn't until yesterday ever 
tried to centrally manage these things, because usually the project only 
has a few involved.  Unlike the Polycom interface the Linksys web 
interface is actually fairly decent IMO, and I have always gotten by that 
way.

If I need to make a change in the future, to say the dialplan, I make a 
change to one XML file that is included by all the Polycom phones, and 
reboot them.  What would be the procedure through the endpoint manager?

For grins I poked around looking for the source of the Linksys template, 
as I noticed it doesn't include the dialplan tag.  I couldn't find it... 
do you know where it is?

Cheers!

j