[Krunk]

The first post on the 2nd page of the thread contains the following ZIP FILE:
NOTHING TO SEE HERE.ZIP

This ZIP file contains a firmware file to convert the PAP2 into a Sipura SPA-1001 as well as another firmware file to revert the SPA-1001 back into a PAP2.  Somebody please host a copy of this ZIP file for B$ because it'll likely get yanked off of BBR once Linksys/Sipura gets wind of this!

here's a backup if needed:
http://www.krunk4ever.org/NOTHING_TO_SEE_HERE.zip

//krunk (^_^x)

[TheDiggler]

Thanks Krunk. I edited my posted and added your link.

[Pekkle]

Need a little more clearifcation about the GPP K and GPP D strings. Since the PAP2 is unlocked, and we have the control of admin password for the PAP2, why do we still need to mess around with GPP K? what is the benfit of obtaining the admin password for vonage? if I don't ever plan on using the PAP2 on Vonage, should I still need to worry about the GPP K string that's on the router currently? or can I safely remove it from PAP2?

and will I need GPP K for other VOIP companies such as voipbuster or skype?

Also, can some one please post the settings needed for skype? I would rather use skype than those other ones..

Thanks..

[Krunk]

Need a little more clearifcation about the GPP K and GPP D strings. Since the PAP2 is unlocked, and we have the control of admin password for the PAP2, why do we still need to mess around with GPP K? what is the benfit of obtaining the admin password for vonage? if I don't ever plan on using the PAP2 on Vonage, should I still need to worry about the GPP K string that's on the router currently? or can I safely remove it from PAP2?

and will I need GPP K for other VOIP companies such as voipbuster or skype?

Also, can some one please post the settings needed for skype? I would rather use skype than those other ones..

Thanks..

according to posts found on Skype's forums, because Skype uses a closed network instead of open SIP protocols, it is not compatible with devices like the PAP2. people have actually concluded to the point there is no stand-alone device that works with skype without a computer.

my sources:
http://forum.skype.com/viewtopic.php?t=37952&highlight=pap2
http://forum.skype.com/viewtopic.php?t=35103&highlight=pap2
http://forum.skype.com/viewtopic.php?t=31659&highlight=pap2

hope this helps.

//krunk (^_^x)

[Pekkle]

according to posts found on Skype's forums, because Skype uses a closed network instead of open SIP protocols, it is not compatible with devices like the PAP2. people have actually concluded to the point there is no stand-alone device that works with skype without a computer.

my sources:
http://forum.skype.com/viewtopic.php?t=37952&highlight=pap2
http://forum.skype.com/viewtopic.php?t=35103&highlight=pap2
http://forum.skype.com/viewtopic.php?t=31659&highlight=pap2

hope this helps.

//krunk (^_^x)

Hi krunk, Thanks for the quick reply, I thought since netgear is coming out with a wifi phone for skype, then there should be a way to use it on voip routers, but I guess not..

How about GPP K? Do I really need to crack the admin password for voange to consider fully unlocked?

[Pekkle]

To get voipbuster to work, I probably reinstalled the firmware on these about three times.  I  kept screwing up all the settings after messing with it so much.

Finally today i decide to do something different.  I changed out the phone i was using and it started working.

     

lesson of the day....start with the simplest solutions first

cron, does that means there is not a reset to default button that we can click on? (back to a clean unlock state that is).

[TheDiggler]

Need a little more clearifcation about the GPP K and GPP D strings. Since the PAP2 is unlocked, and we have the control of admin password for the PAP2, why do we still need to mess around with GPP K? what is the benfit of obtaining the admin password for vonage? if I don't ever plan on using the PAP2 on Vonage, should I still need to worry about the GPP K string that's on the router currently? or can I safely remove it from PAP2?

The GPP_K and GPP_D values stored in your Vonage PAP2 are for use by Vonage and no one else. The adapter, by default, does not have a GPP_D value stored in it. It receives one of these values if/when the adapter "phones home" to Vonage.

Should your adapter "phone home" to Vonage, it will receive a new set of adapter settings, among which include a new GPP_K value, a populated GPP_D value, new user & admin passwords, and will re-lock your adapter & turn off its web interface! Furthermore, it will likely perform a firmware upgrade to the latest version of the PAP2 firmware (which now makes it extremely difficult to unlock the adapter w/o knowing your adapter's admin pw).

By storing your "factory fresh" GPP_K value off to the side, you can use it to download and decrypt your Vonage XML Provisioning file(s) at will. A very slick Windows program posted @ BBR, VuckFonage, has been written to automate this process as much as possible.

Since the unlocking process instructs you to disable automatic provisioning, in theory your adapter should never "phone home" to Vonage. HOWEVER, if you perform a FACTORY RESET on the adapter while it's connected to the internet... POOF! It will immediately "phone home," change its settings, lock itself, and upgrade its firmware. Without your FACTORY FRESH GPP_K value saved off to the side, you won't be able to download and decrypt your PRIMARY XML provisioning file (which will contain your admin pw at that time).

If you perform a FACTORY RESET while the PAP2 is NOT connected to the internet, the adapter will still get re-locked; however, you can repeat the standard unlocking process to re-unlock it.

Note: If you switch your adapter over to SPA-1001 firmware, there is no chance of it re-locking even if it "phones home" to Vonage. This is because the PAP2 XML config files aren't compatible w/ SPA-1001 firmware. Also, performing a FACTORY RESET w/ the adapter in SPA-1001 mode wipes out all configured settings (including the Vonage settings) and keeps the adapter UNLOCKED.

I hope this answers your question(s).

Diggler

This post has been edited by TheDiggler: 1-16-06, 9:19pm

[Pekkle]

I hope this answers your question(s).
Diggler

Diggler, Thank you very very much for the detail information, I have learned a lot from your post, so I have saved the GPP K's string just in case I ever need it. So far I have been able to use stanaphone, but not voipbuster for some reason, no dial tone and my account has been activated since Aug last year, the only thing I can think of that is not working is I have only $1 in the account, which the refill takes min $10. don't know if that is the problem.

[vickh]

is it possible to use PAP2 w/ PPPoE connection

[Pekkle]

has anyone tried the voipstunt.com and got it to work? I would like to know the settings if possible.. thanks..

[TheDiggler]

is it possible to use PAP2 w/ PPPoE connection

The PAP2 is not a router, it's only an ATA (Analog Terminal Adapter). Thus, it can't directly use a PPPoE connection. It can be plugged into a router though, where the router can handle a PPPoE connection.

Diggler

This post has been edited by TheDiggler: 1-17-06, 2:40pm

[ungsunghero]

For those of you still using Telepacket/Callpacket (I have to, since I can't cancel without being forced to pay an early termination fee), I'm beginning to think my phone is the problem, and not Telepacket.

I set call forwarding through Telepacket to my cell phone, and now incoming calls seem to be working just fine...

[Krunk]

ok, that was scary. i've been trying to upgrade the firmware to 1001 with no success. however, I did manage to screw up and let vonage take over my pap2 for the past 4 hours and turned it almost into a paper weight.

so I tried to upgrade the to 1001 with http://pap2-ip/upgrade?tftp://myserver/filename.bin

the file would be transferred, the device would blink, but wouldn't turn red or signal it flashed. looked like it just rebooted and my firemware # stayed the same.

actually, let me rewind, i was unable to call http://pap2-ip/upgrade directly because it wanted an admin password which i didn't have, but i was able to call http://pap2-ip/admin/upgrade and that worked in the sense the file was downloaded and the pap2 seemed to do something.

so believing that i needed the admin password to use the upgrade function in http://pap2-ip/upgrade, i went ahead and downloaded the SPA0000.xml file and decrypted it with the GPP_K key. the password from that file didn't work which led me to my next thought.

maybe it needs to download this new .xml file for it to work. i tried the plain text xml with the admin password file from my tftp server, but it didn't seem to like it, but that didn't seem to do anything. So I went ahead and did the factory reset and allowed it to download the new xml. turns out it also downloaded the new firmware 3.1.9 LSc. For whatever reason, DO NOT DOWNLOAD THIS NEW FIRMWARE. One of the things is they prevent users from upgrading firmware and requires admin priviledges.

I spent the next few hours trying to undo the damage. I was about to give up. With the new xml file (which I had the password to), the web user interface was disabled. Factory resetting the device left me gave me the web user interface, but wouldn't allow me to upgrade the firmware without the admin password which i didn't have.

I tried to feed it a plain text xml file with my predefined password, but it didn't like that either.

So almost about to give up, I was wondering if they used the same key to encrypt and decrypt. I went ahead and used the same openssl command that decrypted the file to encrypt it with web interface enabled and user/admin passwords blank. BOOM! It worked!

At this point, I could modify anything in that xml file and it'd take it.

But now, I'm left with a 3.1.9 LSc firmware which won't upgrade to the 1001 which was my original plan. I was able get both VoipBuster and TelePacket working so I was back to square 1.

So I went around reading forums and was wondering if it could be that the firmware just isn't compatible... I went ahead used SPATools and made my own PAP2toSPA2000 and SPA2000toPAP2 bin files and actually got my firmware back down to 3.1.6. However, at this stage, I still can't upgrade to 1001 and was wondering if anyone had a clue on what I might need to do? I can upgrade from http://pap2-ip/upgrade? now tho.

Thanks!

//krunk (^_^x)

This post has been edited by Krunk: 1-22-06, 5:12am

[TheDiggler]

I'm not sure why you weren't able to upgrade to SPA-1001. I've upgraded 2 PAP2's to SPA1001 w/o issue.

When converting your PAP2 to SPA1001, use firmware file:
spa1001-03-01-08-SE-c_TO_PAP2hardware.bin

If the TFTP transfer occurs, give the PAP2 perhaps 3-5 minutes to let it process the firmware.

Note: I don't recall whether SPA1001 firmware causes any indiactor lights to turn RED during the upgrade process. When it's done, you're left w/ 1 BLUE indicator light (and that's how it remains thereafter while in SPA1001 mode).

Diggler

P.S. You were very lucky to have saved your GPP_K value for your PAP2 connected to the internet and upgraded by Vonage to PAP2 firmware 3.1.9. You could have used the adapter's IVR (integrated voice response) system to re-enable web access (which would have required the ADMIN PW from the downloaded & decrypted XML file).

[Krunk]

i'm having some problems with Telepacket and was wondering if you guys hit this problem. With the soft phone, I can make and receive calls. With the PAP2 and my AT&T 900Mhz cordless phone, I can receive calls and conversation works, but seem to have some trouble making outgoing calls.

When I try to make an outgoing call, the destination phone rings, but then immediately it plays the busy signal and the connection with the other party is lost. My cell phone would ring once and then display a missed call message. As I stated, it works fine with the soft phone.

At first, I was thinking it might be the phone or the pap2, but I was able to make outgoing calls with VoipBuster without any problems.

I was wondering if anyone knew what the problem may be. I've attached a screenshot of my pap2 settings for telepacket (senesitive info blacked out):

http://www.krunk4ever.com/gallery/d/4543-1..._telepacket.png

[ungsunghero]

i'm having some problems with Telepacket and was wondering if you guys hit this problem. With the soft phone, I can make and receive calls. With the PAP2 and my AT&T 900Mhz cordless phone, I can receive calls and conversation works, but seem to have some trouble making outgoing calls.

When I try to make an outgoing call, the destination phone rings, but then immediately it plays the busy signal and the connection with the other party is lost. My cell phone would ring once and then display a missed call message. As I stated, it works fine with the soft phone.

At first, I was thinking it might be the phone or the pap2, but I was able to make outgoing calls with VoipBuster without any problems.

I was wondering if anyone knew what the problem may be. I've attached a screenshot of my pap2 settings for telepacket (senesitive info blacked out):

http://www.krunk4ever.com/gallery/d/4543-1..._telepacket.png

I had the same problem with an AT&T 2.4GHz phone...I tossed the phone, got another cheapo phone, and the problem went away.

[Krunk]

I had the same problem with an AT&T 2.4GHz phone...I tossed the phone, got another cheapo phone, and the problem went away.

interesting...

guess I'll have to find another fone to try. wonder if costco still has that 5.8ghz fone for $30.

//krunk (^_^x)

[ungsunghero]

interesting...

guess I'll have to find another fone to try. wonder if costco still has that 5.8ghz fone for $30.

//krunk (^_^x)

The phone I replaced my cheapo AT&T phone with was a 5.8ghz phone, for the record.

This is not to suggest that there is some compatibility issue between AT&T phones with the PAP2 and/or Telepacket/Callpacket.

This post has been edited by ungsunghero: 2-4-06, 11:09pm

[ungsunghero]

Anyone here still using Telepacket (not Callpacket, even though they are essentially now one and the same)?

I am signed up for the 95c/month "pay per call" plan, and it has been brought to my attention that the wording of the plan details seems to suggest that I am not getting 100 free in/out minutes PER MONTH. Instead, it looks like I'll be getting 100 in/out minutes to start (meaning once I use up the 100 minutes, I'll be paying 2.9c/min out, 1c/min in).

Here are the details of the pay per call plan.

The TelePacket 95¢ Plan is our pay per call plan. Pay $0.95 a month and receive 100 FREE outbound minutes (local and long distance calling within the U.S. and Canada only) and 100 FREE incoming minutes. Each outbound minute thereafter is 2.9¢ per minute and 1¢ for each additional inbound minute.

The funny thing is, I have been charged only once ($0.95) since I've had the service, and I've been using Telepacket since December. Also, I have not used up all 100 incoming or outgoing minutes since signing up, so perhaps that's why I'm not being charged any more...

[coolpizza]

Hi, there,

I just got a 3.1.3 and it shoule be easy to unlock according to others' comments.
And I carefully followed everything in the quick summary,
and it goes through the first upgrade for PAP2-SP2K.bin smoothly and I saw The power LED will turn RED.
But just after I got excited, the problem came:
" Click the "admin login" link near the top-right. Click the PROVISIONING tab and set PROVISION ENABLE=NO."
After I clicked the link, it poped out a window asking for the pass word for "pap2 admin".
And then I got stuck there and couldn't move forward. I even tried to factory reset again using 73738#, and start the whole process all over, but it didn't work either. Can anyone give me a clue?
Thanks a lot, I really appreciate.

[ungsunghero]

Hi, there,

I just got a 3.1.3 and it shoule be easy to unlock according to others' comments.
And I carefully followed everything in the quick summary,
and it goes through the first upgrade for PAP2-SP2K.bin smoothly and I saw The power LED will turn RED.
But just after I got excited, the problem came:
" Click the "admin login" link near the top-right. Click the PROVISIONING tab and set PROVISION ENABLE=NO."
After I clicked the link, it poped out a window asking for the pass word for "pap2 admin".
And then I got stuck there and couldn't move forward. I even tried to factory reset again using 73738#, and start the whole process all over, but it didn't work either. Can anyone give me a clue?
Thanks a lot, I really appreciate.

If you got that far, then you already changed the user password to "1234."

When that window pops up, leave the username field blank, and type "1234" for the password (unless you used a different user/pass)

[coolpizza]

If you got that far, then you already changed the user password to "1234."

When that window pops up, leave the username field blank, and type "1234" for the password (unless you used a different user/pass)

Thanks for the reply, but it didn't work for me either.

[letapteej]

I also have same problem to log into admin.

Pl. some one reply.

[cron]

Which firmware version are you using?

[letapteej]

Thanks Cron for reply & asking.

But Puzzel is solved.

In first stage, the file was nor trasfered to PAP2. So after booting, again Linksys Menu was coming. After proper trafer of file using tftp, new Sipura Menu came & was able to log in Admin.

Thanks again for your excellent info.

[DrZoidberg]

allright, so i was trying to setup this adapter at a friends house and i performed a factory reset while connected to the internet. I just boned myself didnt I? I tried to redo the unlock but its not working.

[Krunk]

allright, so i was trying to setup this adapter at a friends house and i performed a factory reset while connected to the internet. I just boned myself didnt I? I tried to redo the unlock but its not working.

if you reset it to factory conditions you might be able to get it to work. there's instructions somewhere on this thread on how to get that to work.

//krunk (^_^x)

[TheDiggler]

allright, so i was trying to setup this adapter at a friends house and i performed a factory reset while connected to the internet. I just boned myself didnt I? I tried to redo the unlock but its not working.

You've boned yourself in the sense that the original (easy) unlock process won't work anymore as the adapter has now been upgraded to firmware 3.1.9 (assuming you left the adapter powered on for a while after performing the factory reset while connected to the internet). As of firmware 3.1.7, USER MODE firmware upgrades are no longer permitted (which was the security hole permitting the original unlock method).

Now, if you've saved the GPP_K value for this adapter from when you first unlocked it, the easiest and fastest way to re-unlock it is to:

1) Download & decrypt your adapter's INITIAL UPDATE config file from Vonage (use VuckFonage to simplify this process)

2) Inside the decrypted config file will be a USER PASSWORD and an ADMIN PASSWORD

3) Assuming your adapter's web-server is disabled (check first), dial into the adapter's IVR interface, enter the command 7932# (that command toggles the adapter's web-server on/off), follow that command w/ the ADMIN PW (obtained in the previous step), and then hit the # key. If the ADMIN PW isn't purely numeric, here's a conversion chart for entering letters and symbols:

To input the password using the phone keypad, the following translation convention applies:

o To input: A, B, C, a, b, c -- press ‘2’
o To input: D, E, F, d, e, f -- press ‘3’
o To input: G, H, I, g, h, i -- press ‘4’
o To input: J, K, L, j, k, l -- press ‘5’
o To input: M, N, O, m, n, o -- press ‘6’
o To input: P, Q, R, S, p, q, r, s -- press ‘7’
o To input: T, U, V, t, u, v -- press ‘8’
o To input: W, X, Y, Z, w, x, y, z -- press ‘9’
o To input all other characters in the administrator password, press ‘0’

Note: This translation convention only applies to the password input.
For example: to input password “test#@1234” by phone keypad, you need to press the following sequence of digits: 8378001234.

4) Once the web interface is enabled, in a web-browser navigate to the PAP2's IP address. (You can find out the IP address using the IVR command 110#).

5) If prompted to login, you may first need to login as "user" (followed by the USER PASSWORD obtained in step #2). No conversion gets applied to passwords in the web-interface.

6) Once logged in as "user," click the link for "Admin" mode. Enter the username "admin" (followed by the ADMIN PASSWORD obtained in step #2). Again, no conversion gets applied to passwords in the web-interface.

7) Assuming the above is successful, go to the PROVISIONING TAB, turn off automatic provisioning. Go to the SYSTEM tab, remove Vonage's DNS servers. Feel free to DOWNGRADE the firmware to 3.1.6 (or lower) so that USER MODE firmware upgrades can be performed.

8) The adapter is now unlocked.

If you haven't saved the adapter's GPP_K value (shame on you), and if you can continue to factory reset the adapter, you can still unlock it using an isolated LAN running your own DNS server mimicing Vonage's TFTP & HTTP servers. This is much more involved, so I'll only go through posting those steps if you feel you need to go this route.

Diggler

This post has been edited by TheDiggler: 4-20-06, 11:26am

[DrZoidberg]

i have the GPP_K for my other but I never saved it for this adapter, thanks for your help.

[TheDiggler]

Ok, since you don't have the GPP_K value of the adapter which has been upgraded to firmware 3.1.9, before going any further, make sure you can FACTORY RESET THE ADAPTER (while it's disconnected from the internet).

STEP 1: Factory Reset the adapter:

1) Disconnect the adapter from the internet
2) Connect a simple telephone to LINE1
3) Enter IVR mode by dialing: ****
4) Enter the command: 73738# (i.e. R E S E T #)
5) If/when prompted for password, enter one of the 5 "known/common" Vonage USER Passwords:
• 78196365
• 50274537
• 7756112
• 8995523
• 5465866
6) Press the # key after entering a password
7) Repeat the process above until one of the passwords works or you've exhausted the list
8) If prompted to "Press 1 to confirm," do so.

If the adapter successfully factory resets, you may proceed with the next series of steps.
If not, you're pretty much "stuck" at this point and need to find a working Vonage USER Password.


STEP 2: Attempt to access the PAP2's WEB INTERFACE & remove Vonage's DNS settings:

1) Disconnect the internet connection from your BROADBAND ROUTER or BROADBAND MODEM
2) Connect the PAP2 to your ROUTER
3) Connect a PC to the ROUTER
4) In a web-browser, navigate to the PAP2's IP address (if you don't know it, go back into IVR mode and issue command 110#)
5) Go to the "SYSTEM" tab and clear out the "Primary DNS" and "Secondary DNS" entires.

Note: If you can't access the adapter's web interface, so long as the adapter remains disconnected from the internet, the inability to perform this series of steps is not a big deal. The adapter will simply take longer resolving DNS requests (by trying Vonage's IP addresses first, and after failing to reach them, trying DHCP assigned DNS entries next).

STEP 3: Gather/setup the following items:

1) Sipura SPA-2000 Firmware 2.0.9 converted to PAP2 mode firmware and renamed to file: PAP2-bin-03-01-09-LSc.bin (An already converted version of the firmware is availabe in Post #3, Step 3. Use file PAP2-SP2K.bin. If the aforementioned link is down, an alternate location for the files is listed in Post #504).
2) An HTTP Server running on your LOCAL LAN
3) A TFTP Server running on your LOCAL LAN @ Port 69 (for simplicity make this the same PC as the HTTP server)
4) A DNS Server running on your LOCAL LAN (for simplicity make this the same PC as the HTTP & TFTP servers)
5) A DHCP Server running on your LOCAL LAN:
• If you have a BROADBAND ROUTER, this may be used provided you:
  i) Disconnect the INTERNET CONNECTION to the router (i.e. unplug the cable going to the router's WAN port and/or disable any WDS settings)
  ii) Manually configure the PAP2's DNS server to use the IP ADDRESS of your local DNS server (i.e. STEP #4 above). This will need to be done through the PAP2's IVR:
  a) Enter IVR mode by dialing: ****
  b) Enter command 160# to review the current DNS server IP address (if you so desire)
  c) Enter command 161# to set/change the DNS server IP address
  d) Type in the IP address of your LOCAL DNS SERVER, separating octects with an asterisk (*). End input with the # key. Example: if your DNS SERVER's IP address is 192.168.0.50, enter: 192*168*0*50#
  e) Press 1 to SAVE, Press 2 to REVIEW, Press 3 to RE-ENTER, Press * to exit
  f) Upon successfully reviewing the DNS Server IP Address setting, SAVE THE SETTING!
  iii) Remember to clear the PAP2's DNS Server settings after it's been unlocked! (This can be done through the adapter's web interface).
• Internet Connection Sharing (ICS) built into XP may work. Try enabling it on the ETHERNET adapter of your PC (i.e. the same PC running the HTTP, TFTP, and DNS servers)
• 3rd Party DHCP software should work too (for simplicity, make this the same PC as the HTTP, TFTP, and DNS servers)
6) A copy of your adapter's ENCRYPTED Config File (from Vonage's TFTP server) named spa000000000000.xml (where 000000000000 is the MAC ADDRESS of your PAP2)
7) A CROSSOVER Ethernet cable

STEP 4: Configure your LOCAL LAN's DNS Server to mimic Vonage's Servers:

1) Point httpconfig.vonage.net to the LAN IP address running your HTTP server
2) Point ls.tftp.vonage.net to the LAN IP address running your TFTP server
3) (Optional but recommended) Point *.vonage.net to the LAN IP address running your HTTP/TFTP servers
4) (Optional but recommended) Forward UDP ports 21 & 2400 to Port 69 (so that your TFTP server receives traffic on ports 21, 2400, and the default TFTP port of 69). If you don't know how to configure this, setup a 2nd TFTP server listening on PORT 2400. (Vonage seems to use ports 69 & 2400 the most, but they also use 21).

STEP 5: Prepare your local file structure:

1) In your TFTP ROOT directory (or directories if running mulitple TFTP servers), copy your adapter's ENCRYPTED config file to that directory as spa000000000000.xml (where 000000000000 is the MAC ADDRESS of your PAP2)
2) In your HTTP ROOT directory, create sub-directory: +000000000000 (where 000000000000 is the MAC ADDRESS of your PAP2)
3) Copy the modified SPA-2000 v2.0.9 firmware to the HTTP-ROOT/+000000000000/ directory (where 000000000000 is the MAC ADDRESS of your PAP2) as filename PAP2-bin-03-01-09-LSc.bin

STEP 6: Start the UNLOCK PROCESS (i.e. load SPA2000 2.0.9 firmware into your PAP2):

1) Disconnect the ethernet cable from the PC running the HTTP/TFTP/DNS servers
2) Disconnect the POWER cable from the PAP2
3) Connect the PAP2 and the PC to each other:
If using a PC as your DHCP server:
Connect the CROSSOVER Ethernet cable to the PAP2 (on one end) and to the PC running the DNS, TFTP, and HTTP servers (on the other end).
If using a BROADBAND ROUTER as your DHCP server:
• Using a standard ethernet cable, connect the PAP2 to a LAN PORT on your Broadband Router
• Using a standard ethernet cable, connect the PC (running the DNS, TFTP, and HTTP servers) to a LAN PORT on your Broadband Router
• Make sure NOTHING is connected to the WAN PORT of the Broadband Router!
• Make sure any WDS (Wireless Distribution System) settings have been disabled on the Broadband Router! If you don't know what a WDS is and/or haven't set one up, chances are there is nothing to disable.
4) Make sure the PC is powered up and that the DNS, TFTP and HTTP servers are running
5) Power on the PAP2
6) If all goes well, your TFTP server's log will show the PAP2 grabbing the encrypted file.
7) Shortly thereafter, the HTTP server's log should show the PAP2 grabbing the modified SPA2000 v2.0.9 firmware file.
8) Once the PAP2 has loaded the SPA-2000 firmware, one of the indicator lights on the PAP2 should turn RED

STEP 7: (Re-)Open WEB access and configure known USER & ADMIN pws:

1) Create a TEXT FILE called spa000000000000.xml (where 000000000000 is the MAC ADDRESS of your PAP2) as follows:

CODE
<flat-profile>
    <Admin_Passwd ua="na">4321</Admin_Passwd>
    <Enable_Web_Server ua="na">Yes</Enable_Web_Server>
    <Web_Server_Port ua="na">80</Web_Server_Port>
    <Enable_Web_Admin_Access ua="na">Yes</Enable_Web_Admin_Access>
    <Protect_IVR_FactoryReset ua="na">No</Protect_IVR_FactoryReset>
    <User_Password ua="na">1234</User_Password>
</flat-profile>
If creating the file above in NOTEPAD, when SAVING it, it must be saved with ANSI encoding, not UNICODE!!!
2) Copy the new spa000000000000.xml (where 000000000000 is the MAC ADDRESS of your PAP2) file to your TFTP ROOT directory (or directories if running multiple TFTP servers)
3) Power cycle the PAP2
4) Check your TFTP Server's log to see when the file has been grabbed
If the TFTP Server's log shows a FILE NOT FOUND error message, and if the file attempting to be grabbed was requested from an obscurely named sub-directory (i.e. /a12BcdeFgH/spa000000000000.xml), create that sub-directory (a12BcdeFgH) underneath the TFTP Root and move (or copy) the spa000000000000.xml file to that sub-directory. Then re-Power Cycle the PAP2 and re-check the TFTP Server's log.
5) After it's been grabbed & loaded, the adapter's USER password is "1234" and the ADMIN password is "4321"

Note: Sipura SPA-2000 2.0.9 firmware allows PLAIN TEXT config files to be loaded and processed. That is why this unlock "trick" works.

STEP 8: Revert back to PAP2 firmware:

1) Use PAP2 firmware 3.1.6 or LOWER!!!
2) Follow the directions here: Basic Firmware Update Instructions

STEP 9: Obtain the FACTORY FRESH GPP_K key (OPTIONAL but recommended)

1) In STEP 6, the encrypted Vonage Config File got loaded into the adapter. This caused the adapter's FACTORY FRESH GPP_K value to be overwritten w/ one supplied by Vonage.
2) With the adapter disconnected from the internet and loaded w/ PAP2 firmware 3.1.6 or lower, FACTORY RESET THE ADAPTER. This will cause the FACTORY FRESH GPP_K value to be re-loaded, but it will also re-lock the adapter. Before FACTORY RESETTING the adapter though, delete your Vonage Encrypted spa000000000000.xml file from your TFTP ROOT! Otherwise, upon performing a FACTORY RESET, your adapter will request and process this file, a file which DISABLES THE ADAPTER'S WEB INTERACE!
3) Repeat the ORIGINAL (easy) UNLOCK process (i.e. perform the entire series of steps listed in POST #4 of this thread)
4) After the adapter has been re-unlocked, extract the GPP_K value and save it! This value is located in the "Provisioning" tab of the adapter's web-interface (i.e login as "admin," switch to "advanced" mode and click on the "Provisioning" tab).

How do you tell the difference beween the FACTORY FRESH GPP_K value and a Vonage assigned one?

Attributes of the FACTORY FRESH GPP_K value:
• 44 characters long
• Comprised of alpha (A-Z, a-z), numeric (0-9), and symbols
• Ends with an EQUAL SIGN (=)
• Example: n6KClGUoMXzIQ/JmmuSFBE1GOu+M8335eHfPeYHeRAs=

Attributes of a Vonage Assigned GPP_K value:
• 64 characters long
• Comprised of HEX characters (A-F, a-f, 0-9) only!
• Example: 9190ca44e4cffb893c2ae43c4bca57fb18f04482a84dcce30d28017e7715a8a0

Diggler

P.S. For a flow-chart summary of most of the above, download pap2-318unl.zip which is also contained in the 4th post here:
http://www.dslreports.com/forum/remark,144...9999~start=1520

This post has been edited by TheDiggler: 5-16-07, 8:25am