Rotten mud: Small Call voice system migration

This article was sponsored by Xiuyi linfeng and first launched in the dark world.

The company's voice call system uses small calls because of work needs. You need to migrate the server to the system. That is, the current Windows Server 2003 Enterprise Edition is upgraded to Windows Server 2008 64bit.

Several steps are required for server migration:

1. Database Backup

2. Call for backup

3. Install Windows Server 2008 r2

4. database recovery

5. Install Tom

6. Xiao Linghu coverage

7. Start a call

Because the current database used by this server is SQL Server 2005, it is easy to back up. For SQL Server 2005 database backup and recovery, refer to my previous article "rotten mud: SQL Server 2005 database backup and recovery".

After the database is backed up, let's back up the image. According to the official documents, you only need to back up the it9000 and WAV directories in the installation directory. Among them, the it9000 is the program running directory of the call, while the wav directory is the directory that stores the recording.

After the backup is completed, you can view the IVR card model. Open the config file under the Directory D: \ it9000 \ lcall4 \ v \ runenv, find the ctype = LC-3216 line, such:

The LC-3216 represents the IVR card model, which is required in the installation of the applet call process below.

The following describes how to install the starter package and double-click the setup.exe file, for example:

The IVR card should select the LC-3216, because according to the IVR model we have seen above this. You can also view the label information on the IVR card.

Note that the OS installed this time is 64bit. When you install the IVR card driver, a message indicating that the hardware driver is-1 is displayed.

This is because the built-in driver of Tom is 32bit. If it is 64bitos, it is necessary to install 64bit driver.

64bit driver, that is, the hybrid driver is as follows:

Baidu Network Disk: http://pan.baidu.com/s/1qWlrSZE

115 Network Disk: http://115.com/lb/5lbcyldvol4a

Click "no" in the serial number.

Do not start the call after installation.

After the installation is complete, we can now overwrite the previously backed up ghost call it9000 to the current installation directory. After overwriting, we can install the driver of the IVR card. We can see the LC-3216 of this device in the Device Manager, such:

After the installation, coverage, driver installation, and database recovery are completed, we can start the call. For example:

PS: There is no database configuration file for Tom. This is a conclusion based on the information provided by their official customer service.

Because the official information provided is that the database that is installed by default is access, if you want to change the database, You need to log on to the background to make the change.

I think this is unscientific. But they said that, I cannot.

At the same time, I am not sure to compliment them on their official website. Especially for the IVR card driver, I gave them multiple calls at the beginning of the migration. The feedback shows that there is no problem with migration, but the migration is true. However, it is found that the IVR card has been unable to be identified, and therefore the call cannot be started. Later, I consulted online customer service and reported that the problem was caused by the IVR driver. 64bit driver must be installed. Unfortunately, the driver is not downloaded from the official website.

Later, they waited for them to send it to me to start the service normally.

This is a pitfall ......