dead ata

[burris]

Or as they would say in legalese....
force majeure

[WildKid]

Or as they would say in legalese....
force majeure

It came back from the dead! Yay!

However, I had to press the reset button and send it a dummy file via tftp, including a dummy xml (config) file that basically wiped out all the settings.

Basically, it became unlocked!

So I then updated it to the last firmware revision from the linksys web site. This was possible because it identified itself as a pap2t-na (rather than a pap2t-al unit). That is, I updated the router side from 1.20 to 1.38, and the voice side from 2.02 to 3.1

So basically, now I have two options:

a) set it up as a byod device
b) have them lock it down via config file

which one is preferable?

fyi: this a replacement unit from voipo that I received a while back for a unit with an overheating psu. no overheats yet!

I'll be getting a proper siemens ip phone with my christmas and birthday money next month, so I could care less which route is taken.

[usa2k]

b) have them lock it down via config file

As this is a VOIPo device, that is the right choice.
For support and such, when all else fails, it will be the only supported hardware.

[fisamo]

Where's the reset button on the PAP2? Or is this the RT31P2?

Regardless, if the device was sent to you by Voipo, you should have them lock it down again. After all, it's their device.

If you are not one of the early adopters who was given 'core' SIP credentials (ie. not from the 'BYOD' tab of vPanel), use of the device with the BYOD option would limit you to no international calling (and whatever other restrictions Voipo has imposed on the BYOD servers).

I'd suggest that you submit a support ticket asking them what URL to put into the 'provision' field, reboot, and then enjoy your Voip service!

[chpalmer]

Ive seen this kind of thing on high radio sites. Lightning hits the tower and a few pieces of equipment go wacky and need to have their config reloaded.
We ground these sites very well but 1.21 jigawatts can do funny things...

Probably a good thing you updated the firmware from a device point of view...

[burris]

If yours ia a PAP2T from VOIPo and you want to have them provision it and control it, suggested, this is the entry into the provision field..

http://provisioning.voipo.com/$MA

[WildKid]

If yours ia a PAP2T from VOIPo and you want to have them provision it and control it, suggested, this is the entry into the provision field..

http://provisioning.voipo.com/$MA

I have an rt31p2. Where is its provisioning field?

when I tryto te wget

http://provisioning.voipo.com/00121723d997.xml  gives me 'not allowed!'

it says 'not allowed!'. Is the access mac-address based? Does it require the mysterious password that they don't give out?

[usa2k]

I would go with KISS. Put in a ticket and all this figuring will be moot.

It seems that your ingenuity may be more than to just get it working?

[fisamo]

One other thing I'd suggest is to put the URL into the provision field directly...

http://provisioning.voipo.com/$MA

... literally. Don't substitute your MAC address, let your device do it for you. Also, don't try to wget it from a separate box--perhaps the provisioning server can tell when something other than the ATA is attempting to download the provision file...