How to provision your own Linksys PAP2 unit

[pap2boy]

With the recent Linksys/Vonage PAP2 unlocking scheme released by Matt Wafro through his SPATools, there are so many Linksys/Vonage unlocked PAP2 units operating on the Internet. Before I proceed further, let me make this clear that the procedures outlined here is for owners of Linksys unlocked PAP2 (which Linksys refers this device as a PAP2-NA). Regardless it is a Linksys PAP2 and/or Linksys PAP2-NA, the requirement here is you will need to be able to access the Provisioning page through the Admin login button. So, unless otherwise stated, a reference to a Linksys PAP2 in this guide means an unlocked Linksys PAP2 unit that you can freely access any of its Admin pages. Please note that some smaller VoSPs distribute Linksys PAP2-NA devices to their customers that are locked. If you own a Linksys PAP2/PAP2-NA that is used with some paid VoSPs services, please don't try to unlock and provision them by yourself. Doing so perhaps will cause your service interrupted/terminated by your VoSPs, let alone you are violating their ToSs.

As of this writing, a Linksys PAP2 unit doesn't offer some features to let its owner to Backup and Restore its existing configuration file like some other ATA devices do. This is because a Linksys PAP2 unit is designed from the ground up to let itself provisioned by its own assigned VoSP. (Perhaps Linksys can be urged to provide this feature added to their new firmware releases.) That said, it is possible for the owners of Linksys PAP2 units to setup their own TFTP servers and automatically/manually provision their own Linksys PAP2 unit(s) at their own schedules. That way, Linksys PAP2 owners don't have to manually make any necessary changes to their devices. At least, this is how I have done it on all my unlocked Linksys/Vonage PAP2 units.

To make a long story short, this is how I do (wrote this off my head) to provision my own unlocked Linksys/Vonage PAP2 units (assuming you run your own TFTP server and be sure to have your TFTP server correctly registered to a DNS server if you want to provision your own Linksys PAP2 unit(s) on a live Internet connection):

1. Grab the XML Provision (encrypted) file for your Linksys PAP2 from its previous VoSP (mine was Vonage) and decrypt it with the GPP_K value found on your Linksys PAP2 unit. If you own an unlocked Linksys/Vonage PAP2 unit, this step can be done automatically with this VuckFonage utility written by rizzo2dial. The complete thread of this VuckFonage utility can be found here. You can even edit the newly grabbed XML Provision encrypted/text files with this VuckFonage utility.
2. Edit the unlocked/text XML Provision file to suite your configurations. This step is only needed for the first time to do-it-yourself -- DIY -- to provisioning your own Linksys PAP2 unit.
3. On your Linksys PAP2 unit and under the Provision menu, you will need to disable the Provision Enable and enable the following (also found on the XML Provision text file so they can be set accordingly after the unit get provisioned):
   
   1. Resync On Reset.
   2. Forced Resync Delay set to 0 (instant resync).
   3. Resync After Upgrade Attempt.
   4. Upgrade Enable. This is for firmware upgrades only.
   5. Under the Profile_Rule_C, replace the TFTP URL with your own as shown below:
      

      Code: Select all

      <Profile_Rule_C ua="na">
(GPP_E = "$D";)!
[--key $K] tftp://<Your TFTP Server>:$P/$D/spa$MAU.xml
</Profile_Rule_C>


      The existence of the above step is very critical unless you want your Linksys PAP2 unit mistakenly provisioned by the default TFTP server, i.e. ls.tftp.vonage.net (Linksys/Vonage PAP2). Watch out for the GPP_D ($D) values that specifies the directory where the next XML Provision encrypted file resides on the TFTP server once the device gets provisioned with the current XML Provision file.
   6. For me, I just take an additional precautious step to replace the GPP_K values found on my Linksys PAP2 units as well as on their respective XML Provision text file with something else, preferably with the same GPP_K values for each Linksys PAP2 units. That way, I don't have to worry about my Linksys PAP2 units be mistakenly provisioned by the previous/factory default TFTP server. Note, this doesn't mean you can factory reset your unit and worry free from the device provisioned by the TFTP server set by default factory values.
4. Whenever you need to make any mods on your Linksys PAP2, all you need is to:
   
   1. modify/edit/[gzip]/encrypt the XML Provision text file,
   2. put the newly created XML Provision encrypted file on your TFTP server for your Linksys PAP2 to retrieve,
   3. then go to your Linksys PAP2 Provision Menu to enable the Provision Enable, save, and
   4. do a reboot.
   Your Linksys PAP2 unit will go and grab the new XML provisioned file to reconfigure with new configuration you have just made. Because you have disable the Provision Enable feature on the XML Provision text file, your Linksys PAP2 unit is now run with the Provision Enable feature disabled.

Please note that you can basically leave the Provision Enable feature always enabled and just send an INVITE from your TFTP server for your Linksys PAP2 unit to automatically be resynced/provisioned whenever you want. A reboot on your Linksys PAP2 will also perform a provision if the feature is enabled. For further information on this feature, please read the PAP2 and RT31P2 Admin Guide (sorry I don't have the link here).

Please also note that I am just sharing and providing the above information here for you to read. It may contain some errors that may render your Linksys PAP2 units to useless. So, use these information under your own discretion and don't hold me from any responsibilities should you fail to provision your own Linksys PAP2 unit(s), let alone to have rendered your own Linksys PAP2 unit(s) to useless. You have been warned!