QUOTE(springle1 @ 6-26-07, 5:46pm)

The God Lord has shined upon me! The PAP2 has grabbed the .bin file (but note via TFTP rather than HTTP, as I'd expected) and its now taken your unencrypted SPA<XML> file (with HTTP rather than TFTP). As you guidance said, the LED went red - and rather conceringly remains so after muliple power recycles of the unit. Is this normal behaviour?
The unit will remain w/ a RED led so long as it's loaded w/ Sipura SPA2K firmware. Once it gets re-loaded w/ PAP2 firmware, it'll revert back to BLUE. It's odd that your PAP2 grabbed its .bin file via TFTP and its decrypted XML file via HTTP. That's opposite of the expected/typical behavior.
QUOTE(springle1 @ 6-26-07, 5:46pm)

On giving the PAP2 '****' and 110#, the unit comes back with a "Sipura Configuration Menu" message - so its sounds as though the firmware is on-board.
Indeed your unit has been loaded w/ Sipura firmware. I hope it's version 2.0.9 (there's an IVR command you can issue to check -- search this thread or google for the correct command -- am too tired @ the moment to look it up). If it's newer than 2.0.9, it won't process plain-text files.
QUOTE(springle1 @ 6-26-07, 5:46pm)

However, when feeding my browser the unit's IP address, and being prompted for User Name & Password, neither USER/1234 or case combinations thereof let me thru.
It almost sounds like your PAP2 rejected the plain-text XML file, but the fact that your PAP2's web interface is enabled leads me to consider otherwise. Normally, after a PAP2 has loaded its Vonage ENCRYPTED XML FILE, its web interface is disabled. Based on what you've written, your adapter's web interace is enabled. Then again, your entire unlock process was different than the normal process. Thus, I'm uncertain as to whether your adapter processed or rejected its plain-text XML file. The usernames are in all lowercase, so "user" / "1234" (w/o the quotes) and "admin" / "4321" (again, w/o the quotes).
QUOTE(springle1 @ 6-26-07, 5:46pm)

I sense I'm on the threshold! Having got this far, I don't want to do any clumsey resets - any further tips that you could offer would be appreciated
Each time you power cycle your PAP2, check your TFTP and HTTP logs to see where it's attempting to provision from. It should be attempting from somewhere (either via TFTP or HTTP). If it's attempting an upgrade from a GPP_D based directory, place your plain-text file underneath that GPP_D based directory in the TFTP_ROOT or HTTP_ROOT directory accordingly. Ensure that your plain-text XML file has been saved as ANSI TEXT, not UNICODE TEXT. (These are ENCODING OPTIONS in Notepad.)
Diggler