Reset procedure for a 57i phone using the aastra-trixbox scripts?

I am not around a system to give you the exact location, I think it's /var/cache/aastra/astersisk.

One file contains a list of the MAC's, you need to delete the phones line. The other file has the MAC in the filename.

Good luck

OK, well I at least have my local phone working..

Not sure what the deal is, as I thought the multicast support took care of this, but the phone was NOT finding the configuration server. I went into the local phone, set the tftp server to the IP of the trixbox server, let the phone restart and bingo it took off, configured, and is happy at this time.

Still not sure why the phone I have at a location cross country, is not coming up, and asking for the user and password, and from what I am told this doesn't work when entered, or should I say it bitches about the stuff being already configured. Should I remove the cache info on this phone as well??

I'll eventually learn the aastra phones.. *grin*

Looking at this thread, I think it is time to explain (again) the self-configuration mechanism (in freePBX 'extension' mode) and what files are used.

Here it is

1. Plug a 'new' phone on the network
2. Thanks to mDNS, phone gets the Trixbox server IP address that will be used for the TFTP server
3. Phone downloads aastra.cfg which sets the action uri startup to the login script
4. Phone fails to download MAC.cfg as it is a 'new' phone unknown to the server
5. User logs in
6. The script checks the credentials and create /tftpboot/MAC.cfg which clears the action uri startup to avoid a loop at the next reboot
7. The script stores the login in its cache /var/cache/aastra/startup_asterisk.cfg
8. Phone reboots
9. Phone downloads aastra.cfg and the newly created MAC.cfg

So basically only 2 files are involved in the process /var/cache/aastra/startup_asterisk.cfg and /tftpboot/MAC.cfg

So now let's look at your 2 problems.

If you factory default a phone that was 'self-configured', the phone will automaticaly get back its configuration because the phone boots, gets the TFTP server address via mDNS and download aastra.cfg and MAC.cfg, both files did not change. So to reset a user and go back to the login you have to

1. delete the right MAC.cfg on /tftpboot
2. edit /var/cache/aastra/starup_asterisk.cfg and remove the user entry

The complete process can now be applied again, necits is perfectly right. This is exactly what is done when a user logs out.

Now for your remote user if the phone boots and ask for username and password that means that the phone was not able to download MAC.cfg (this is where we reset the action uri startup), so either the phone has trouble to access your Trixbox server for TFTP or the MAC file is corrupted on the tftp server. Looking at the Web UI on the phone will probably tell you what happened, in the troubleshooting section get 'local.cfg' and 'server.cfg', the 'server.cfg' should have aastra.cfg and MAC.cfg together. You maust make sure that 'local.cfg' does not override some key parameters such as acton uri startup of the TFTP server address.
From there maybe the best solution would be to reset the user and login again.

I hope this helps.

Regards