said by tpgopi :

Did anyone used the method described in the thread to configure the LINE1 on these devices for TWO providers?

said by sherryPAP2 :

File one: PAP2SP2K.bin and SP2KPAP2.bin.

said by joneill :

Can someone pls post a link to the software and firmware(that works best)that I need for this mod.

said by rizzo2dial :

... the copy of firmware you have sitting on your laptop is bad...

said by navjun :

I have an unlocked PAP2-UV. that i like to use both lines with one phone.
can you please comment on how to convert pap2 to spa1001 and also how can I find the right firmware. I'm running Firmware Version: 3.1.3(LS) on my PAP2-UV.

said by DogFace05 :

Well, would you believe the MX29LV081 flash chip in most (if not all) PAP2s, so happens, isn't in the list.

said by mazilo :

Since your PAP2 now runs on an SPA3K firmware, you will need to mod a PAP2 firmware so that it will have an SPA3K header string for your PAP2 to recognize.

Which PINs did you short?

said by tkprojects :

However, when I configure it for a SIP provider on Line 1 it registers and I get a dial tone. I couldn't dial though. Perhaps I should preface my number with a #, as described with respect to some other sipura mod. I need to play with it a bit more, I guess.

Anyway, I tried to upgrade it back to some sane FW, but it just sits there claiming that it will do it when it isn't busy. I wasn't holding my breath for long enought on that.

I also tried the flash address pin shorting trick, but it just locked up the box until powerdown, i.e. I didn't see it do a bootp/dhcp request as hoped for so that I could tftp a recovery image.

said by mazilo :

What exactly did you mean? Did you brick your PAP2 from flashing it with a modded SPA1K firmware?

BTW, how do you know if you have a bricked PAP2? Does it keep rebooting itself indefinitely or a complete shut off?

said by tkprojects :

I wish I read you post earlier, I just "bricked" (not really, but it isn't very usefull now) my pap for nothing trying to do the spa3k trick.

said by cdcl0pht :

Also do you guys know of anything on how to bypass an ISP that blocks SIP? I am trying to send this to a friend in United Arab Emirates. Only one ISP there "Etisalat" GOvt monopoly. I have heard mixed things, some say its blocked while others say its not. This guys dosent even know what the internet is. Actually an old family friend of my parents. We were planning on having him sign up for dls and just use that for SIP since he dosent know how to run computers either.

said by cdcl0pht :

Thanks rizzo. That post did help a lot, but i dont have cross over cbles, and now i will need to install ISS server and configured on XP :(

said by cdcl0pht :

I cant do another factory reset. it asks me for a password and when i try teh 1234# the user password I had set when unlocking PAP2 it syas its invalid and also 1# is not being accepted. I dont know what other password to use. I did not save my Factory GPP_K value. :(

said by beaver :

couldn't go to spa1001-03-01-05-SE.bin directly from PAP2-3.1.3.

said by technoboy2 :

I've had some success and possibly some failure.
1.I loaded the bin file up to the Net onto some web space.
2. I set my router to block connections to Vonage.
3. I connected the PAP2 to the router.
4.I gained user access and pointed the upgrade to the web site.

Result: Rapid flashing of the ethernet LED.
After waiting about 15 minutes I tried accessing the PAP2 Web interface. The browser could not access it. I checked out the IP via the phone connection - it was still the same IP.

said by technoboy2 :

I also tried loading the file up directly, as well as with http, as I can't see why it, necessarily, needs to go via http or ftp as it is available on the same computer. In this case I used:-
»192.168.1.9/upgrade?file:///c:/h···ware.bin

The response is the same as with a hypertext link:-
"PAP2 will upgrade to the new firmware when it is not in use.
Fast blinking of the Status LED indicates that firmware upgrade is in progress.
Please do NOT unplug the power while the Status LED blinking rapidly.
You can click basic or advanced to return to the configuration page when upgrade is completed."

said by technoboy2 :

Yes, I followed that procedure EXCEPT that I used my local apache server and used http instead of ftp. Sadly a password was requested at this point. I did get it to go beyond that, at one point, but it reported that the software would install when the ATA was free - well it was free, it was doing nothing else. So, no luck so far :-(
I have also tried some web referrer spoofing but so far no luck - still it wants a password.

5.  In SYSTEM, set a User password of 1234
6.  Click the SAVE SETTINGS button.
7.  Refresh the link (you login with user and 1234)

said by technoboy2 :

I did get it to go beyond that, at one point, but it reported that the software would install when the ATA was free - well it was free, it was doing nothing else.

said by papsmear :

Wow, cool stuff, thanks Alberto, Mazillo, rizzo2dial, et al. !
A couple of questions..

1. a downgrade of firmware from spa1001 3.1.8 to 3.1.5 should simply be flashing the stock 3.1.5 firmware, correct? (I'm just being cautious)..

2. What is the exact dialing plan entry to call out with just a #?
Please excuse my n00biness :)
Thanks!

said by hardly :

So, is the consensus that 3.1.8 is stable, or that 3.1.5 is the latest stable firmware for use on a PAP2.
Thanks.

said by rizzo2dial :

The LED on the adapter is IMO NOT a sure-fire way to determine whether the adapter is re-registering. It appears as though LINE2's maximum registration time is 178 seconds (regardless of what value you type in which may be GREATER than this amount). I've determined this by refreshing the adapter's web interface on the INFO page.

said by rizzo2dial :

STUN seems to be working fine on my adapter. In the LINE1 / LINE2 tabs, make sure you enable both "NAT Mapping Enable" and "NAT Keep Alive Enable" (i.e. set both options to yes).

said by rizzo2dial :

Agreed. This is probably cosmetic. Perhaps I'll sniff my network traffic one of these days to answer this question definitively.

Try configuring the settings as mentioned above to see if it improves things for you. I've only loaded SPA1001 firmware v3.1.8, not 3.1.5, and the behaviors above haven't prevented my adapter from being fully functional for my needs.

If you only need 1 VoIP provider for INCOMING CALLS configured on your adapter, consider getting the SPA-3000 (which is now available for a reasonable price from Buy.com):
»[Equipment] Source for cheap SPA-3000

That adapter can handle 1 INCOMING/OUTGOING VoIP provider and 4 additional OUTGOING ONLY VoIP providers, all on a single FXS port.

Rizzo

said by papunlock :

Hey Rizzo,

Any random reboot on your 3.1.8 ?
This is the reason I moved to 3.1.5 So far My modded PAP2 is very happy with it. And I got my Power LED on RED

said by Veazer :

-With SPA1001 firmware, line 2 re-registers very frequently (as little as every second guessing from the light, varies with other settings)

said by Veazer :

-I can only use OB proxy servers to place calls. STUN is no longer working. I even reverted to some older pap2 firmware and still had to use OB proxies. My pap2 is out in the DMZ.

said by Veazer :

-Port usage doesn't follow settings

said by Veazer :

Hopefully this a fluke or something that can be overcome, but i am ready to give up on my unit after a stressful day of firmware changes. I am hoping I can get it fully working as a PAP2 again.

said by Veazer :

I do realize now I prefer the 1001 setup and I think I am going to get one. I wish using two providers on a single FXS port was simply an option on the PAP2 or other SPA devices!

said by mazilo :

I hope you will be able to un-brick your PAP2. Perhaps, you may want to try the PIN15 shorting trick and/or even the TFTP method used to flash open source firmware on a Linksys WRT54G/S router.

said by rizzo2dial :

Thus, the PAP2 I've loaded w/ SPA-3000 firmware is esentially a "brick."

said by rizzo2dial :

9) The SPA-1001 mode should now contain the PROVISIONING SETTINGS (i.e. GPP_K, etc.)

said by VOIPnYC :

just another thought, can we patch the header of sipura 2000 firmware and "convert" the Pap2 to sipura 2000 or pap2-na?

said by DogFace05 :

Sipura fw does not recognize the Vonage factory defaults stored in the adapter. I suspect it is a situation analogous to why the headers of the Sipura firmwares have to be patched to be accepted by the Linksys fw upgrade function and vice versa. Vonage factory defaults are stored separate from the firmware, and probably stored with a header identifying them as Linksys PAP2 specific, which Sipura won't recognize. We know they are not in the firmware, as there are no differences between Vonage and NA fw.

said by mazilo :

3. **** 73738#1# (factory reset) doesn't cause the PAP2 running with SPA1001 v3.1.8(SEc) firmware to phone home.

said by mazilo :

4. Then XML file that I used to provision my PAP2 doesn't seem to be processed by my PAP2 even though the TFTP log show the file got fetched by my PAP2. Perhaps, I need to regenerate a new XML file using SPC for SPA1001.

said by mazilo :

5. After a factory reset, it appears the GPP_K values becomes lost (I guess this also happens with SPA2K firmware) and the DNS entries seemed to be filled with the ones from the router.

said by mazilo :

What is interesting regarding item #3 is we no longer fear our unlocked PAP2 gets provisioned and locked by Vonage.

said by rcilink :

Hmm.. I am curious if you take that PAP2 with SPA1001 v3.1.8(SEc) and put Linksys PAP2 3.1.3 firmware on it... and then try the factory reset to see if the vonage stuff is really gone (GPP_K wiped, so did it wipe the 'customization' portion of the flash that the PAP2 uses?)

I have a hunch that the SPA1001 firmware uses a different memory map (most likely to store the second provider info), and it is overwriting the memory portion used for PAP2 customization (core Vonage settings that restore at factory reset). We stumbled across this with the SPA2000 firmware, noting that it wiped the Admin Passwd and a few provision settings..