Manually Copying OCR Data From One System to Another
Manually Copying OCR Data From One System to Another
Disclaimer: The supported method of adding OCR table entries is still to enter them individually in Admin. This document is a how-to provided for experienced AltiGen technicians. The procedures outlined here involve manual database manipulation. Do not proceed without verifying you have a current backup of the configuration.
Description: In the scenario where you have a very large number of Out Call Routing entries, it is possible to duplicate them to another server without manually keying in the data.
Note: Both servers must be at the same version (i.e. both on 5.2 or both on 6.0), the quick fix level does not have to match.
FROM server:
- Make a backup of c:/altiserv/openldap folder
- Open up c:/altiserv/exe/ldapexplorer
- Click on Service and choose Connect.
- Then click on service again and choose Copy LDAP
- From within the window, choose the "Ldap to file" radio button
- Choose a source, browse to Sys/OCR
- Target, browse to any location you wish and create a folder called "OCR" and click on the copy button.
This will create multiple .txt files.
- Bring this folder onto the "TO" server
TO Server:
- Copy the OCR folder into the c:/altiserv folder.
- Open Ldapexplorer
- Click on Service and choose Copy LDAP
- From within the window, choose the "File to LDAP" radio button
- Choose a source, browse to the OCR folder.
- Target, browse to Sys/OCR.
- If Sys/OCR does not exist, do the following:
- In MaxAdmin, open the OCR configuration window, and create a single route entry, and click "Apply".
- Delete this entry, and then click "Apply" again.
- Go back to Ldapexplorer and click on the "Refresh" button. Sys/OCR should now exist.
- Then, click on the copy button. This should bring over all the configurations of the OCR table.
- Stop and start all altigen services.
- Once services are started, you should have all the configurations of the OCR table from the "FROM" server. The only note here is that you may need to define your Member trunks for each route definition again.
Attachments
No attachments were found.
Related Articles
Visitor Comments