Securing PINs and Passwords in Cisco Unity Connection SRSV
See the following sections:
•Cisco Unity Connection SRSV Passwords and Shared Secrets
•Changing the Cisco Unity Connection SRSV User PIN
Cisco Unity Connection SRSV Passwords and Shared Secrets
All the requests initiated from the central Connection server to the Connection SRSV server use administrator credentials of Connection SRSV for communication whereas the requests from Connection SRSV to Connection use secret tokens for authentication.
The central Connection server uses the administrator username and password of Connection SRSV to authenticate access to the server. The username and password of the Connection SRSV get stored in the Connection database as you create a new branch on the central Connection server.
During each provisioning cycle with Connection SRSV, the central Connection server generates a secret token and shares the token with Connection SRSV. After the provisioning is completed from the Connection SRSV site, it notifies Connection using the same token. Then this token is removed from both Connection and Connection SRSV servers as soon as the provisioning cycle is completed. This concept of runtime token keys is known as shared secrets.
For more information on Connection SRSV, refer to the Cisco Unity Connection Survivable Remote Site Voicemail (SRSV) Guide for Cisco Unity Connection Release 9.x at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/quick_start/guide/9xcucqsgsrsv.html.
Changing the Cisco Unity Connection SRSV User PIN
If you want to change the PIN of a Connection SRSV user, you can do it through the Cisco Unity Connection Administration interface. After changing the PIN of the selected user, you need to provision the associated branch to update the user information in the Connection SRSV database.
Note You cannot change the PIN of an SRSV user through Cisco Unity Connection SRSV Administration interface.