|
|
FIRST TIME READERS: It's suggested you start with the 2006-11-14 post below, then read up (newer posts), then if you have the interest read the older posts (nearer the bottom).
Methods for unlocking the Linksys PAP2The following is a list of updates tracking the progress of unlocking the Linksys PAP2:
2010-2-7
WARNING!!! Do not buy PAP2 v1 boxes at this time, since there is too much of a risk you will get a v3.1.7 box or higher. These boxes CANNOT be unlocked unless you sign up for vonage service to get the provisioning xml. Vonage has stopped sending provisioning xml's for devices that are not active. They do have a 30 day money back guarantee though, but I'm not sure how often you can use that...
2009-1-24
Should you still be able to find one of these PAP2 in its original packaging (strangely, they do turn up now and then, but remember you want an UNOPENED one in a box with an ORANGE band, not the SILVER one) here are a few additional hints (especially for those of us who haven't done this in a while and may have forgotten what we did).
1) Make sure that at NO time until the unlock is completed do you ever connect the PAP2 to the Internet, or to a computer, switch, or router that is connected to the Internet. The PAP2 and the computer you are using to configure it MUST remain as a network unto themselves, with NO way to gain access to the net. MAKE SURE YOU TOTALLY DISABLE ANY WIRELESS NETWORKING CAPABILITY IN THE COMPUTER!!!
2) Do NOT succumb to the temptation to set the adapter to a static IP address. Set up Internet Connection Sharing on the computer (of course you are NOT really sharing the Internet) or do whatever you have to do to get the computer to act as a DHCP server and feed the adapter its IP address and (most important) DNS server information. If you don't do this, you may find yourself in a situation from which it is very difficult to recover.
3) Do NOT get the binary files confused and download the PAP2 binary first. You MUST download the Sipura binary first.
4) If you did not see my above warning (for #2 and/or #3) until it was too late, all may not be lost as long as the adapter did not see the Internet. The very first thing to do is try to reset the device again by using **** and then 73738# as per the original instructions - if you can do this it will (hopefully) dump the firmware you loaded by mistake and bring in the original firmware from ROM, letting you start over from scratch (well, almost). But a problem arises - when you pick up the phone, you hear a short ring followed by a ghastly sounding busy signal, and hitting **** does nothing! Just have patience - you just have to wait a few seconds (after the trashy busy signal starts) and then the **** may work! By the way, if you are prompted for a password, try any of these: 78196365#, 50274537#, 7756112#, 8995523#, 5465866# (and if one works, then hit 1 to confirm).
5) If you tried to use a static IP address and then got into the situation in #4, you may have to do the procedure in the 2006-12-19 post below. But it may be harder because, since the device isn't trying to pull addresses from a DHCP server, it may actually looking for two (or more) different IP addresses - one is the DNS server itself, and the other is one or more of the addresses you entered manually. You can use Wireshark to see what it's trying to access. You will have to make your computer pretend to be the DNS server it wants to see as described in the 2006-12-19 post below, but you may have to actually create a mini-network consisting of the PAP2 and TWO other computers, one acting as the DNS server and the other being the other address it's trying to get to (note that it IS possible to make one NIC respond to multiple IP addresses, by using advanced TCP/IP options, but this can cause other complications, particularly since Windows assumes you don't know what you're doing and will sometimes block you from doing the very thing you really need to do!). Now, if you happen to have two NIC cards in your computer, then you should set one to be the DNS server, set the other to be the other address(es) that the device is looking for, and set up your Internet Connectiong Sharing or DHCP server on that last one. It's probably easier with two computers and a small switch or hub, but remember that under NO circumstances can ANY of the devices be allowed to connect to the Internet while you are trying to recover!!!!!
6) If #5 sounds like a royal pain in the neck (or perhaps a lower part of the anatomy), believe me when I say it IS! Unless, of course, you are a networking guru, in which case you probably wouldn't make these types of dumb mistakes in the first place. I strongly suggest you heed the warnings in #2 and #3, and I only post this to let you know that if you DID make such a mistake, the unit may still be recoverable if you stop and think about what you are doing and IF YOU DO NOT AT ANY POINT CONNECT THE DEVICE TO THE INTERNET, OR TO A COMPUTER THAT IS CONNECTED TO THE INTERNET until it is FULLY unlocked. But whether it is worth the extra time it will take you to figure out what works is another matter altogether!
2009-1-6
Don't buy locked pap2, the latest firmware is very hard to unlock. bot unlocked from Mutualphone , for $45
2008-04-16
I can confirm the odd packet size mentioned in the 2007-05-03 entry below. I got my PAP2 off eBay. It was listed as unlocked, but it turned out to be locked. It came with firmware 3.1.9 LSc. For me it lists the total packet size as 27990, but only grabbing 100 bytes on the wire. I'm not uber enough to find the TCP window size on linux, so I am unable to continue my unlock attempt.
2007-07-03
Hello All,
I did the Short Jumper at the PAP2v1 (like the figure below) this only do a Reset like the reset by the IVR **** 73738# 1 to Confirm it doen´t work. I will keep trying
2007-06-21
For whatever it's worth, rumor has it that the PAP2v1 units run a little-known operating system that comes from Green Hills Software
2007-05-03
After hours of trying to upload the Sipura to my PAP2 with 3.1.9Lsc, I took a closer look at the packets with Ethereal. One of the response packets from my HTTP server was basically that the packet was fragmented or too big (I don't remember the actual message, but that was what i meant when I looked it up). The way I finally got around this and forced it to eat the Sipura firmware was by using DrTCP (normally used to change MTU) to change the window size of the TCP packets to 20000 on the ethernet adapter the HTTP was listening on. After this, the download of the .bin worked. I presume they made the http request with a huge TCP packet size to attempt to prevent "unauthorized" upload of firmware. I'd like to know if anyone else has gotten it to work this way.
2007-02-25
The PAP2v1 units I have are all based on v0.03.4 board where the SW1 block has four jumper PINs (exactly as shown on the snapshot below). I took a working PAP2v1 unit configured with FWD accounts and shorted out the outer two PINs (red circles) and my PAP2v1 seemed to perform a factory reset (the power LED activities indicated so). However, upon returning from this factory reset, all the configured parameters were still there and Line 1/2 were still registered to FWD as if the unit was never factory reset. To this date, my PAP2v1 unit that undergone this jumper shorting is still operating normally as before. This is all I can say about shorting the two outer PINs on the SW1 block. So, if you want to do this, do it at your own discretions and I take no responsibility of any mishaps.
2007-02-23
There is a graphic that I saw that purports to show the location of reset jumper pads on the majority of newer PAP-2 version 1 boards, which apparently do not have the jumper pins and shorting block that older boards have. In the photo below, there are red circles around the purported jumper pads (to the right of the phone line jacks). I do not know precisely how these are used (I've never had to use that method), but I would suppose either you short the pads while powering the unit up, or perhaps while doing a factory reset (of course you would only do that while the adapter is not connected to the Internet). I do not recommend that anyone experiment with this because if the information I received is wrong, you could damage your adapter. But if it's a choice between using a unit as a paperweight and trying the jumpers, I suppose I'd try them at least. If anyone can provide more information on unlocking a PAP-2 by using the jumper pads, please post it.

2007-01-17
Addendum to 2006-11-14 notes:
If you're lucky enough to be running a wireless router — such as the Linksys WRT-54G — and it uses the DD-WRT open-source firmware, the simplest way to do this is in the "Administration / Services" menu. Enable DNSMasq, Enable Local DNS, and enter something similar to "address=/vonage.net/10.10.50.224" into the Additional DNS Options box. Any machines that use the router's DNS server to resolve IPs will then report the IP 10.10.50.224 for the entire vonage.net domain, so put in your tftp's IP address instead.
With the wireless router's WAN port disconnected and the PAP2 behind it's firewall, it will try (and fail) to reach Vonage's hard-coded DNS ip addresses, then fall back to using the router's DNS which we've redirected to our tftp server.
http://www.voip-info.org/wiki/view/Linksys+PAP2+Unlocking+Methods
|
|