as chilling_silence asked, how are you configuring, if by endpoint manager, it is currently broken, (see other posts by myself and others for aastra and provisioning and possible fixes).
If manually, then it should work, but if tftp is being used, I believe the the 9133 is broken to the point of "forget it", should you get avahi and the xml scripts from aastrato work, (basically you have to change from http to https for the scripts, or change your http server config to not rewrite http calls) this seems to work perfectly, but you will need a clear brain and the ability to use uncle google.
Once you have an ip address on the phone you can http into that address (admin, 22222) and fix all the errors in the username/password etc. that get scrambled by the 9133. save it and reboot and it will work, (local config overrides provisioning until the phone is hard reset)
p.s. All your problems have been previously asked and answered on these fori.
Wasted a few hours onsite trying to sort the AASTRA phones out with Endpoint provisioning. Would not have persisted but was performing Trixbox to Elastix changover and the old Trixbox had what appeared to be a provisioning setup on it. Found out several hours later that all but the phone I was working on was set to FTP (disabling the TFTP setup).
I am actually going to do some work on the provisioning side this weekend to see if we can finally get to the bottom of it. Have setup a fully logged TFTP server in the lab for testing.Will manually create the files for the phone to see what is breaking. Then I will compare code and config files on Elastix to see what is causing it.
I have the Aastra phones now working with the standard endpoint configuration in Elastix, which means you don't need the XML provisioning setup (RPM's) with all the additional stuff. That's not to say the XML option is not needed, but it is not required in many of the cases.
First of all sorry for the delay, but it needed a real look into what was going on. I have had SYSLOG servers running (for the phone), separate TFTP Server with realtime display and logs, SSH into the Elastix system, Web page to view and restart the phone.
Anyhow, partially thanks to the posts in this forum and via the resolution of other issues, it appears I have a working setup. I will write it up in the next 24 hours as I want to retest and complete some final changes, but needless to say, the phone was provisioned without any details entered into the phone or the Web Interface, which is what I wanted.
Hello, I have a extrange question. Can you help me? my problem is if I delete sip trunk all aastra on the lan works well, but when i define again sip trunk, and STOP the router, all aastras becomes NO SERVICE.