ProCall DataCenter known problems and limitations

ProCall DataCenter is not suitable for use with Active Directory AD SnapIns (schema extension).

Existing ProCall Enterprise configuration prevents correct ProCall DataCenter installation

If a user is moved from one UCServer to another (change of home server), then the line becomes active on one UCServer immediately, but remains active on the other UCServer for about 15-30 seconds. I.e. for a short time the line is active on both UCServers.
In addition, there may be the problem that by opening the TAPI line twice, the used licenses expire, because in this case two licenses are occupied for a user for a short time. If this occurs, then it can take 900 seconds (15 min) until ECSTA tries again to open the line. Other problems are also conceivable here, depending on the PBX.

Existing ProCall Enterprise configuration prevents correct ProCall DataCenter installation

Currently, existing configuration settings can only be applied via the path described in the installation instructions. For a correct installation, it must currently be ensured that no setting and configuration artifacts from ProCall Enterprise are on the system.

Federation only via SIP proxy

SIP federation can currently only be performed via a separate, upstream SIP proxy.

Different UCConnect ID's

From the point of view of UCConnect, the UCServers of the multi-server environment act as independent servers and are not recognized as a multi-server environment. This results in each server having its own UCConnect ID. If a user changes a server and uses Mobility Services or ProCall Meetings, the server ID in his user login must be updated. 

Monitor and favorite contacts

Contacts in the monitor or favorites are not moved when the server is changed and are therefore not available on the other server.

Computer profiles cannot be assigned across servers

Computer profiles can be used to assign a phone number to a computer, which is bound to the user as soon as he logs on to this PC. Since the user and the line must currently be on the same server, it cannot be guaranteed that this will work for all users, since they may be registered on a different home server than the corresponding line.