Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here


1616/1608 problem with auto login after restart

1616/1608 problem with auto login after restart

1616/1608 problem with auto login after restart

Hi experts! I have an inussual behavior with ip phones. We have 60 ip station with an IPO 500v2 R11 between 1608 and 1616 ip phones.
When I restart the IPO for a change some phone doesn´t back automatically, they ask the extension and password for login. But is not for all of them, some phones are logged automatically.

The entire config is the same for all phones

Any advice?

RE: 1616/1608 problem with auto login after restart

Are you hotdesking at all? ie do the Extensions and Users match?

RE: 1616/1608 problem with auto login after restart

Thank you for your response! And yes, I´ve configured matching users and passwords

RE: 1616/1608 problem with auto login after restart

Hmm... the only time I've seen this is when we found users were pressing Reset when the handset fails to Discover.

Might want to check for any fw updates.

RE: 1616/1608 problem with auto login after restart

We have had this.

Do you have Media Security enabled on the system?

If so, disable it from any IP Extension you have programmed that is a 16xx phone.

There is an issue where if the phone loses connection to the system, kit reboot or network issue, then they will not recover from this. Disabling Media Security on the Extn Tab fixes this.

We got bored of arguing with Avaya that the handsets shouldn't pay any attention to this setting because thye do not support it, and this therefore was a bug. But they ignored us and took the answer that disabling this fixes the issue, therefore we program our systems wrong, even though this is not documented anywhere.

Jamie Green

Avaya Registered Specialist Engineer

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close