[WXC/VFX] PAP2T Problem Re-establishing Provisioning

Forums › Vodafone New Zealand › [WXC/VFX] PAP2T Problem Re-establishing Provisioning

IB4

13 posts

Geek

Topic # 25716 29-Aug-2008 21:01

In the process of disconnecting my second line, help@xnet have accidently loaded an auto-provisioning file that has completely opened up my PAP2T. Some of you might think that’s excellent, but I would rather not have to mess around setting up the PAP2T myself at the moment. The helpdesk have apparently now put the correct provisioning file in place, but unfortunately my PAP2T refuses to load it. I have set the provisioning profile, and the spa$MA.cfg file downloads, but then the PAP2T spits a syslog message “Resync failed: zero length key”. I will call tech support tomorrow and try my luck getting them to tell me the key and where to put it. In the mean time can anyone suggest any other solution?

coffeebaron

5290 posts

Uber Geek
+1 received by user: 2318

Trusted

Lifetime subscriber

Reply # 160806 29-Aug-2008 21:17

Factory reset the PAP2T - plug phone in, dial **** then 73738# then 1 then hang up phone.
This should factory reset.
Reenter the provisioning link:

http://58.28.20.69/configs/default/default$MA.cfg
Save
Power off / on, wait 5min

Chorus has spent $1.4 billion on making their xDSL broadband network faster. If your still stuck on ADSL or VDSL, why not spend from $150 on a master filter install to make sure you are getting the most out of your connection?
I install - Naked DSL, DSL Master Splitters, VoIP, data cabling and general computer support for home and small business.
Rural Broadband RBI installer for Ultimate Broadband and Full Flavour

Need help in Auckland, Waikato or BoP? Click my email button, or email me direct: [my user name] at geekzonemail dot com

IB4

13 posts

Geek

Reply # 160812 29-Aug-2008 22:01

That did the trick. Many thanks.
After a factory reset I entered the provisioning link:
http://58.28.20.69/configs/pap2t/spa$MA.cfg
Changing this to /default/default$MA.cfg fixed it.
It's still sending out syslog messages, because I naturally didn't think to turn syslogging off before the resync, and now I don't appear to have access to turn it off. Oh well, will just live with that!

Interestingly, shortly after resyncing with default$MA, it then resynced succesfully with spa$MA.cfg. Hmm.