[asterisk-users] PAP2T provisioning

[Andres]

Jeff LaCoursiere wrote:

>
>
> 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?

It does not contemplate that option as it stands.  I don't think it 
would requiere more than a few lines of code to implement that with the 
Endpoint Manager though.   I do agree that it would be very useful to 
have that feature.

>
> 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?
>
You need to add it.  Just look at where the <flat-profile> section is 
and add it like this example we have:
<flat-profile>
 <!-- Subscriber Information -->
  <Debug_Server ua="na">192.168.1.49</Debug_Server>
  <Debug_Level ua="na">3</Debug_Level>
  <Syslog_Server ua="na">192.168.1.49</Syslog_Server>
  <Text_Logo  ua="na">Customer</Text_Logo>
  <Select_Background_Picture  ua="na">BMP 
Picture</Select_Background_Picture>
  <BMP_Picture_Download_URL  
ua="na">tftp://192.168.1.49/customer.bmp</BMP_Picture_Download_URL>
        <Display_Name_1_ ua="na">$UserID</Display_Name_1_>
        <User_ID_1_ ua="na">$UserID</User_ID_1_>
        <Password_1_ ua="na">$Password</Password_1_>  
<Dial_Plan_1_ua="na">([2-8][1-9]xxxxx|[1-6]xx|30xxxxx|9xxx|01[2-9]xxxxxxxxx|0[2-9]xxxxxxxx.|*0xx|*800xxx)</Dial_Plan_1_>
</flat-profile>

This basically hard codes the dialplan.  You can probably edit the html 
file to actually enable you to input the values graphically, but that 
was more involved than what we needed to do.

Andres
http://www.neuroredes.com


> Cheers!
>
> j
>