Showing results for 
Search instead for 
Did you mean: 

When the user presses the Services button to access Personal Directory Fast Dials, the -7ffbffcf: User (3177) was unable to be validated. (49) error message is displayed


Core Issue

When setting up Fast Dials under Cisco IP phone services, it works well until the user changes the PIN or password, which prompts the error.


The problem is with the PIN the user enters or how the PIN is set up.  Typically, in a new Cisco CallManager or Cisco Unity phone system, users must deal with two passwords and one PIN. The first password is the one used to access voice mail. For example, the one you key into the phone when you press the Messages button. The second password is the one you use to access the phone feature web page. The PIN is the personal ID number that you use to validate your user ID when using various services, such as My Fast Dials and the My Address Book services.

If you try to set up and use My Address Book on the phone, and you receive a Personal    Address Book (PAB) error message similar to this one on your phone display, perform this    procedure to ensure your PIN is set correctly.

  1. By default, your PIN is 123456. Change that default PIN through the "Change your PIN" link on the first page after you log in.
  2. Choose the Configure your IP Phone Services link and select My Address Book.
  3. Enter your new PIN


  • Repeat the procedure for My Fast Dials.

Once these have been updated, you should be able to add your own address    book entries and assign Fast Dials. Note the interaction between the web page    and the phone interfaces. You may find it more convenient to do the    setup through the web interface, then use the feature on the phone. For more information, refer to the Configuring Personal Directory section of Personal Directory.

The error can also occur if Active Directory (AD) integration on Cisco CallManager points to    a wrong Organizational Unit (OU).

For a workaround, perform this procedure:

  1. Move users to an OU where Cisco CallManager integration is set up.
  2. Re-run AD Plugin, and point to the correct OU.

For more information, refer to these documents:

Content for Community-Ad