09.10.2018
Due to a new LDAP component with SwyxWare there might be a conflict between the LDAP port 389 of "3iMedia MetaServices" and SwyxWare LDAP components.
As LDAP port in SwyxWare components cannot be changed by now the only way to keep both components running simultaneously on the same server the LDAP components port of MetaServices has to be changed.
To do so follow these steps:
Client components like MetaServices Add-In don't need to be changed as there's no direct LDAP request done by these components.
If MetaServices are used on a separate machine the LDAP port hasn't to be changed either.
If queries against MetaServices are performed out of a Extended Call Routing this call routing has to be changed as well to use the new port.
Future versions of 3iMedia MetaServices will use LDAP port 390 as default port.