Genesys T-Server: Standby T-Server can’t register for route points

ROUTE_REGISTER_CLIENT_SHARE_KEY_MISMATCH.
ROUTE_REGISTER_CONTROL_NOT_PERMITTED.
ROUTE_REGISTER_INVALID_PERIPHERALID.
ROUTE_REGISTER_DEDICATED_TO_OTHER.
ROUTE_REGISTER_DN_NOT_CONFIGURED.

• Mismatched Primary/Standby T-Server share key mismatch.

Look at status code in CTI-Server log returned on the ROUTE_REGISTER_REPLY_EVENT
If ROUTE_REGISTER_CLIENT_SHARE_KEY_MISMATCH

One Genesys T-Server is registering for the route point with a different key. Check T-Server key configuration on the primary and standby T-Server.

If ROUTE_REGISTER_CONTROL_NOT_PERMITTED

Look up the Dialed Number in the UCCE DN explorer and check 'Permit Application Routing'.

If ROUTE_REGISTER_INVALID_PERIPHERALID

Check Peripheral ID configuration in Genesys setup.

If ROUTE_REGISTER_DEDICATED_TO_OTHER

Check for another client that registered and didn't use a key.

(Probably the ACMI PIM in a CTI-Only Deployment).

(clients from procmon in CTI-Server will show this).

If so most likely the RP is configured for control in Genesys and shouldn't be.

If ROUTE_REGISTER_DN_NOT_CONFIGURED

Check the Dialed Number table in UCCE - This indicates this is an unknown DN.