1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  2. If you had a PIAF Forum account in the vBulletin days, log in with your old credentials. Otherwise, sign up again and we'll get you back in business as soon as we can.
  3. Please keep Message Subjects/Titles short until we can get suhosin and mod_security issues resolved. Otherwise, your thread cannot be read, edited, or deleted. Thanks.

Aastra 57i Troubles

Discussion in 'Endpoints' started by rossiv, Jan 29, 2012.

  1. rossiv Guru

    Solved: Aastra 57i Troubles

    I now have a 57i, the "Asterisk Wonder Phone" but it is doing nothing but giving me headaches. Silly me, I upgraded the firmware to the latest revision (3.2.2.1136) and now it won't pull the updated softkey configuration from the Aastra scripts on PIAF. Something else that is strange is that when I do a factory reset, it doesn't actually *reset* per se. It leaves the previous config from the last logged in user. I finally got it to downgrade to the latest 2.x revision, but something even stranger just happened. About a week ago when I first got my phone, I changed one of the softkey captions with the Keys softkey on the phone itself. Now after I have just flashed a new firmware that caption is still there. How can I actually 100% put it back to factory?
    *Edit: The softkey caption issue is only experienced on one extension on the 57i. By extension, I mean the account that you login with when you first boot the phone. If I login with an extension that I haven't used before, it pulls the config files just fine and updates the softkeys. Thoughts?
  2. rossiv Guru

    Fixed it. As it turns out, the button configuration for each extension is stored on the server in /var/cache/aastra/$EXT.context where $EXT is the extension number. For my phone at least to pull the new keys for an existing user, I had to delete the file. So now all is well.
  3. The dreaded cache!! good detective work.

Share This Page