<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.14.1">
</HEAD>
<BODY>
Nick,<BR>
<BR>
Pretty much - it builds the XML output on the fly, and delivers it over HTTP (PHP/Apache).<BR>
<BR>
It "works the same" for all of the mainstream Linksys kit - including SPA phones.<BR>
<BR>
Generally, where we've installed IP phones, we've also installed an Asterisk appliance in the form of a Linux box, so those ones we provision via TFTP on-site.<BR>
<BR>
We've not yet had any problems with security. Please let's talk of that no further now :p<BR>
<BR>
We don't disable / lock anything. We don't want to become one of "those" providers. Our customers buy their CPE, and thus probably expect to completely own it. We have information on our web which shows the customer how to (reasonably) easily get the unit to start provisioning itself against our prov server again. Alternatively, we get them to establish it's LAN IP, then send them an email with a link to click which does this for them.<BR>
<BR>
Where available, the latest firmware is sent to the device as part of the pre-provisioning process.<BR>
<BR>
Differences between PAP2 and PAP2T are:<BR>
<BR>
- Plainer packaging - more "OEM" style<BR>
- LED colour<BR>
- No "stand-up" attachment (which could lead to overheats, given the vent placement)<BR>
- PAP2T supports T.38<BR>
- PAP2T has more RAM<BR>
- PAP2T is *supposed* to be able to handle 2 concurrent G729 calls - but it can't<BR>
- Different chipset<BR>
<BR>
<BR>
On Fri, 2007-06-08 at 00:34 -0400, Nick Seraphin wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">On Fri, 8 Jun 2007, Mattt wrote:</FONT>
<FONT COLOR="#000000">> Doug,</FONT>
<FONT COLOR="#000000">> </FONT>
<FONT COLOR="#000000">> We just "pre-provision" the Linksys CPE (including PAP2(T)-NA's) in</FONT>
<FONT COLOR="#000000">> the lab over TFTP after barcode-scanning the relevant information for</FONT>
<FONT COLOR="#000000">> that unit into a web management interface and, once the unit is deployed</FONT>
<FONT COLOR="#000000">> onsite, it continues to pull it's config from our prov server over HTTP.</FONT>
<FONT COLOR="#000000">> </FONT>
<FONT COLOR="#000000">> The provisioning service itself is just a PHP engine which pulls the</FONT>
<FONT COLOR="#000000">> relevant settings for that CPE from a database - this way, we can have</FONT>
<FONT COLOR="#000000">> individual parameters for certain customers (who might be, for instance,</FONT>
<FONT COLOR="#000000">> having issues with echo or latency, etc, etc, or some need for a</FONT>
<FONT COLOR="#000000">> different config to our "norm").</FONT>
<FONT COLOR="#000000">Does your PHP engine just generate a plain text XML file to HTTP via</FONT>
<FONT COLOR="#000000">stdout?</FONT>
<FONT COLOR="#000000">Does it work the same for both PAP2's and the IP Phones (SPA942/SPA962,</FONT>
<FONT COLOR="#000000">etc)?</FONT>
<FONT COLOR="#000000">I've successfully provisioned an SPA942 via plain text XML from a tftp</FONT>
<FONT COLOR="#000000">server, but I've never tried a PAP2 remotely, nor have I tried with HTTP.</FONT>
<FONT COLOR="#000000">Do you find any problems with security with it being in plain text?</FONT>
<FONT COLOR="#000000">Do you disable the "restore to factory defaults" thing?</FONT>
<FONT COLOR="#000000">Do you upgrade to the latest firmware before shipping out your PAP2's?</FONT>
<FONT COLOR="#000000">(more below)</FONT>
<FONT COLOR="#000000"> </FONT>
<FONT COLOR="#000000">> Works a treat, is easy as (once the coding is done), and takes about</FONT>
<FONT COLOR="#000000">> 10 seconds to pre-prov (also provides the opportunity to ensure the unit</FONT>
<FONT COLOR="#000000">> isn't a DOA). Customer simply receives the device and plugs it in, waits</FONT>
<FONT COLOR="#000000">> a few seconds (the pre-prov doesn't configure the unit, just prepares it</FONT>
<FONT COLOR="#000000">> for remote provisioning from the target site), then starts making calls.</FONT>
<FONT COLOR="#000000">> </FONT>
<FONT COLOR="#000000">> Oh - and, unless you can locate some "new, old stock", you won't find</FONT>
<FONT COLOR="#000000">> the PAP2-NA (with the blue LEDs) anywhere. They were discontinued many</FONT>
<FONT COLOR="#000000">> months ago...</FONT>
<FONT COLOR="#000000">What's the difference(s) between a PAP2 and a PAP2T? I've only got</FONT>
<FONT COLOR="#000000">PAP2's, and I've got several spares in inventory that I'm hoping I won't</FONT>
<FONT COLOR="#000000">regret having. :-)</FONT>
<FONT COLOR="#000000">Thanks,</FONT>
<FONT COLOR="#000000">-- Nick</FONT>
<FONT COLOR="#000000">_______________________________________________</FONT>
<FONT COLOR="#000000">--Bandwidth and Colocation provided by Easynews.com --</FONT>
<FONT COLOR="#000000">asterisk-users mailing list</FONT>
<FONT COLOR="#000000">To UNSUBSCRIBE or update options visit:</FONT>
<FONT COLOR="#000000"> <A HREF="http://lists.digium.com/mailman/listinfo/asterisk-users">http://lists.digium.com/mailman/listinfo/asterisk-use</FONT>rs</A>
</PRE>
</BLOCKQUOTE>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
Cheers,<BR>
Mattt.<BR>
<BR>
- ROMATel - VoIP made easy - http://romatel.net<BR>
- SpotSafe - WiFi Hotspot solution - http://spotsafe.net<BR>
<BR>
There are only 10 kinds of people.<BR>
Those who understand binary, and those that don't...
</TD>
</TR>
</TABLE>
</BODY>
</HTML>