Nicholas, First off thanks for the ongoing improvements that you make to FOP2.

I have the new 2.28 version installed on two very recent PiaF boxes and am having the same symptom on both. The Majority of the Users are generated with the extension as a password, granted this is because our default installs are built that way, but the password in FOP2 is not updated when the voicemail password is changed by the user. I have poked around a bit and noticed that if I go to a user in FOP2 manager, remove the asterisks and leave the password blank it seems to read the vm password then but if the user changes their password in VM the FOP2 remains unchanged.

Do you have any hints for me to look at or is this the normal behavior?

Thanks,
mike

Nicholas,
I was scratching my head on this as it seems that the voicemail and FOP2 passwords were synced in the past, possibly before the new administration tool? Is this a feature that will be on the road map or possible could be implemented as a plugin? Seems to be adding a huge admin time waste to larger implementations.

Thanks again,
Mike

I am confused now too.

I have my setup so that, in the FOP2 User setup, the "Secret" field is left blank. The information popup for this option says: "The secret to login to fop2. If none specified the voicemail secret will be used."

I have tested this, and if I change my voicemail password, the NEW password is what I have to use to log into FOP2. That is, I use my current voicemail password, whatever it is.

My only caveat is that I am running FOP2 2.2.7. However, this has been the behaviour since I first started using FOP2, which was a few years and a few versions earlier still.