Using a Lync phone edition device, or using SEFAUtil, we can set forwarding/simulring settings for a particular user. Once that user logs in on a Lync client (running on Win7), the forwarding/simulring settings are removed after a few seconds. On the Lync client UI, the settings are disabled. When using SEFAUtil or a Lync phone edition device to set the forwarding/simulring settings again, they are removed after a moment by what appears to be the Lync client.
The Lync client and Front End servers have been updated to the latest version in an attempt to solve this problem.
After installing the Lync client on a clean machine, the issue does not occur. However, after a few days the problem resurfaces. So far, all Lync clients and user combinations have this issue.
There is nothing in the SIP tracing which suggests why this happens. It seems to be the Lync client itself which decides to remove the setting. This is supposed by the fact that our Lync Phone edition devices are perfectly capable of setting forwarding and simulring even though they have the exact same settings applied to them.
The Global voice policy as well as a new voice policy created and assigned to the specific user have the call forwarding and simulring options enabled. This is either routed via PSTN usages or to Internal clients only, both do not work.
No issues on the Front End servers in the Windows event log or issues with the replication state. Also no (glaring) issues in the .etl log file of the client.
My guess, the Lync client thinks the voice policy is faulty. Maybe some faulty configuration is left over from before we upgraded to Lync Enterprise edition. The Lync client uses this information to disable the UI which also triggers the reset of the forwarding/simulring routing information back to a blank state.
Any directions, comments, suggestions are welcome. Even if it's just to say that you can't think of additional troubleshooting steps. I'm thoroughly stuck on this problem that has plagued us for months.