Does anyone know how the Linksys PAP2T ATA's can be mass provisioned? Documentation seems to be sketchy, even on the Linksys web site. Thanks, Doug. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070607/3f90695c/attachment.htm
At 11:44 6/7/2007, Douglas Garstang, wrote:>Content-class: urn:content-classes:message >Content-Type: multipart/alternative; > boundary="----_=_NextPart_001_01C7A923.2703ACD7" > >Does anyone know how the Linksys PAP2T ATA's can be mass >provisioned? Documentation seems to be sketchy, even on the Linksys web site. > >Thanks, >Doug.Don't know, but would like to find out. By the way, the "T" in PAP2T stands for "Trash". We've had about a 70% failure rate. Get the PAP2-NA's with the blue LEDs if you can. Green LEDs = Grief.> >_______________________________________________ >--Bandwidth and Colocation provided by Easynews.com -- > >asterisk-users mailing list >To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users
On Thu, 7 Jun 2007, Douglas Garstang wrote:> Does anyone know how the Linksys PAP2T ATA's can be mass provisioned? > Documentation seems to be sketchy, even on the Linksys web site.If it's like the pap2, you can use tftp and xml. This should get you started. /tftpboot/spa000F66A83C90.xml: <?xml version="1.0" encoding="ISO-8859-1"?> <flat-profile> <!-- tag case appears to be important --> <!-- system, system configuration --> <Admin_Passwd></Admin_Passwd> <User_Passwd></User_Passwd> <!-- system, optional network configuration --> <HostName>example</HostName> <Domain>example.com</Domain> <Primary_DNS>192.168.0.4</Primary_DNS> <Secondary_DNS>192.168.0.4</Secondary_DNS> <DNS_Server_Order>DHCP,Manual</DNS_Server_Order> <Syslog_Server>192.168.0.4</Syslog_Server> <Debug_Server>192.168.0.4</Debug_Server> <!-- provisioning, configuration profile --> <Profile_Rule_B>[--key $K] tftp://tftp.example.com:$P/spa000F66A83C90.xml</Profile_Rule_B> <!-- line 1, proxy and registration --> <Proxy_1_>dt</Proxy_1_> <!-- line 1, subscriber information --> <Display_Name_1_>example-line-1</Display_Name_1_> <User_ID_1_>example-line-1</User_ID_1_> <Password_1_>example-line-1</Password_1_> <!-- line 1, proxy and registration --> <Proxy_2_>sip.example.com</Proxy_2_> <!-- line 1, subscriber information --> <Display_Name_2_>example-line-2</Display_Name_2_> <User_ID_2_>example-line-2</User_ID_2_> <Password_2_>example-line-2</Password_2_> </flat-profile> Thanks in advance, ------------------------------------------------------------------------ Steve Edwards sedwards@sedwards.com Voice: +1-760-468-3867 PST Newline Fax: +1-760-731-3000
> You can reload via http using a command like: > wget\ > --output-document=/dev/null\ > --quiet\ > "http://<ip-address-of-pap>/upgrade?http://<ip-address-of-web- > server>:80/asterisk/spa000F66A83C90.cfg"> I tried it with my xml file and it complains about the file being corrupt.> I'm guessing you need Sipura's configuration compiler. I managed to talk > their support people out of the compiler for the spa3k several years ago. > Maybe you can pratice your SE skills.I believe that you should use the 'resync' keyword instead of 'upgrade'; the latter is intended to specify the URL of a new firmware image. I'm guessing that in some cases it looks at the file contents to decide whether it's configuration data or firmware, so it works anyway. See http://www.sipura.com/Documents/faq/Section_2.html#11 --Stewart