AuditSimon
IS-IT--Management
While testing a disaster recovery scenario for our Call Manager cluster, we built a Publisher from scratch and used BARS to restore a copy of the database. This all seemed to work fine.
We then built a subscriber from scratch and connected in two handsets for testing. The handsets register fine and seem to let you log in using Extension Mobility, but rather than update the phone with the details from the user device profile during login, it displays that login is successful, but doesn't update details such as the Alerting Name and Line Text Label. When selecting Extension Mobility again, it gives you the option to log out, so some part of the login process seems to be working.
When we put the mirrored disk from our real subscriber into the server, everything works fine, including Extension Mobility.
Has anyone got any ideas what is going on ?
We then built a subscriber from scratch and connected in two handsets for testing. The handsets register fine and seem to let you log in using Extension Mobility, but rather than update the phone with the details from the user device profile during login, it displays that login is successful, but doesn't update details such as the Alerting Name and Line Text Label. When selecting Extension Mobility again, it gives you the option to log out, so some part of the login process seems to be working.
When we put the mirrored disk from our real subscriber into the server, everything works fine, including Extension Mobility.
Has anyone got any ideas what is going on ?