...
This integration offers the following features:
- Migration Synchronization of call record metadata and their related audio quality, speech transcription, and screen recording metadata from VFC to WFE.
- Migration Synchronization of switch platforms, and extensions from VFC to WFE.
- Migration Synchronization of groups and users from VFC to WFE.
...
The integration supports the migration synchronization of all VFC users, including users created by an Active Directory synchronization.
...
A data source object in the appsettings.Production file can only be of one platform type and must be in a single time zone. However, it can represent multiple switches of the same platform type, in the same time zone, being recorded by one or more VFC recorders. If the extensions are configured for the data source object, the specified extension numbers are associated to the WFE data source upon creation.
...
Note |
---|
At a minimum, you must have one data source object without extensions per platform type. If you have data source objects with extensions specified, it is still recommended to have one a data source without extensions specified to ensure that no missed extensions get excluded from the synchronization. |
...
If the Integrator finds an existing data source with matching details, it notes the switch_ID of the WFE data source. If the Integrator does not find an existing data source with matching details, it creates one.
Info |
---|
All data sources created as part of the integration are created with the switch/sub-type External Recorder. |
Recorders and call metadata
The Integrator migrates synchronizes recording metadata to WFE by periodically checking the VFC database for new recording data and marking them for synchronization. Call marking is the process of reading in a call record from the database, evaluating it against the Integrator configuration, and sending it to the WFE database.
...
- To access the WFE APIs, port 80 or 443 must be open on the WFE Application Server(s) running the WFO_ProductionDomain_ProductionServer service for incoming communication from the Integrator.
- Ensure that the port configured for the VFC database is open on the server running the database to accept incoming communication from the Integrator.
Deployment process
The VFC to WFE Metadata Integrator deployment process requires configuration in the VFC and WFE environments before the installation of the Integrator. The configuration of the synchronization details is carried out in the appsettings.Production.json file of the Integrator tool after installation.
...
- Open your browser in Administrator mode and go to your VFC Web Interface.
- Follow the Server Certificates topic to download the server certificate for the VFC Media Repository server from the VFC Certificate Authority.
- Install the downloaded certificate on VFC the server that runs the Integrator service.
...
Follow the Troubleshooting Guide to troubleshoot issues with the VFC to WFE Metadata Integrator.
Post-deployment tasks
After the migration completedOnce the integration is configured and active, the following items must be completed and checked:
...
- Verify that the parent organization with the name specified during configuration exists in WFE.
- Verify that the parent group with the name specified during configuration exists in WFE.
- Verify that the VFC Synced group exists as a child of the parent group in WFE.
- Verify that the VFC user groups exist in WFE.
- Verify that VFC users are available in WFE, are associated with the same groups as in VFC, and have the right extensions associated to them.
- Verify that the data sources configured in the Integrator appsettings.Production file exist in WFE, and have the right name, time zone, and extensions associated with them.
- Verify that calls are accessible in the Automated Verification component of WFE.
- Verify that calls recordings are associated with the right users, extensions, and data sources.
- Verify that calls are associated to the recorder with the virtual Serial Number specified in the Integrator.
...