Integration › Clients

Innovaphone MyPBX UC Client

Add Innovaphone MyPBX UC-Client as a client interface to XPhone Connect Directory. LDAP serves as the interface.

Requirements

• Innovaphone IP232 - Version: 11r1sr1 11r2sr10

• Innovaphone myPBX UC Client - Version: 12r1

Configuration

• Open the configuration interface of the XPhone Connect Directory.

• Click on Add client interface.

• Select the client interface type Innovaphone MyPBX UC client.

• Click on the Next button.

• Carry out the steps in the dialog:

1. Configure the Basic settings

2. Configure IP & Port

3. Configure the Authentification

4. Configure the Alternative identity

   Alternative identity

   XPhone Connect Directory can dynamically change the user context within an LDAP query. This enables access to personal contact data by specially adapted applications via LDAP. Along with the suitable security settings, the LDAP client must ensure that no abuse is possible.

   • Identification feature

     If you want to use the alternative identity, activate the option Activate alternative identity via filter condition in the LDAP query and then select how the users are to be authenticated via Identification feature. The authentication of the user takes place via the LDAP filter element :authentication:=<value>. For each search query, an attempt is made to find the value <value> in the user data of the Active Directory or in the XPhone Connect Server user administration.

   • Security info

   Be sure to read and confirm the safety instructions.

   The Alternative identity is only required if…

   • …data sources for personal contact data are set up…

   • …and the LDAP clients are not able to authenticate the owner of the personal contact data via the LDAP login. This is usually the case when dealing with server applications or PBXs.

   XPhone Connect Directory therefore offers the possibility that these applications include in the LDAP query the identity of the user for whom the query is executed. The identity is determined by any user-specific feature known to the LDAP client and which is checked against an attribute in the Active-Directory or in the XPhone Connect Server user administration (e.g. phone number, MAC address, user name).

   With the Alternative identity option, the authentication security of the XPhone Connect Directory is disabled for this client interface. Please note the following:

   • The LDAP client must make the authentication.

     The LDAP client (e.g. a PBX, an end device or another server application) accessing this client interface must ensure that this identification feature is used correctly and by authenticated users only. This means that the LDAP client is responsible for authentication.

   • Protecting the LDAP client from unauthorised access.

     If an LDAP client is not able to perform authentication, it must be ensured that no unauthorized intervention can take place in its functionality (in particular the configuration). If it is possible to configure the client without authorization in such a way that a false identification feature can be incorporated into the query, the confidentiality of the contact data in personal contact data directories is no longer guaranteed.

   • Protecting the connection between the LDAP client and XPhone Connect Directory.

     The connection between the LDAP client and Virtual Directory must be secured as follows:

     • Set up a TCIP/IP connection only via SSL (LDAPS) (see client interface configuration IP & Port).

     • Activate the login via name/password in the configuration of the client interface under authentication. Always choose a sufficiently long password. We recommend at least 30 characters in random order with the additional use of special characters and numbers. Switch off Anonymous login.

     • Restrict the range of permissible IP addresses by making the corresponding settings in Security in the client interface configuration.

     • If possible, restrict the accessibility of the network connection by using VLANs or by configuring switches, gateways and firewalls accordingly. Under no circumstances should you operate secure and unsecure clients on the same client interface.

   If in doubt, dispense with the Alternative identity” function.

5. Configure Security

6. Configure the Search

7. Configure the Phone number conversion

8. Configure the Restricting the number of hits

9. Configure the Overview

10. Innovaphone configuration

    An external LDAP server can be configured via the Innovaphone PBX administration. The IP and client interface port as well as the authentication data must be entered there.

    • Search base:

      To access the personal contacts using the alternative identity, it is necessary to transport a user-specific feature in the search query, e.g. the user’s domain name (sAMAccountName). This feature is stored in the user-specific Innovaphone LDAP configuration in the Search Base input field. The client interface handles this special case automatically. The configured search base is only evaluated if the alternative identity is activated. If you are not using a data source personal contacts, set vdir=VDir as the search base.

    • Object Filter: 1=1

    • Full-text searches involve searches in NameAttributes.

    • When a phone number is entered, searches are conducted in both Name Attributes and Number Attributes.

    • Searches are only carried out in Number Attributes for detecting incoming calls.

    • The Detail Attributes in the Innovaphone devices are shown when depicting a contact.

    • The LDAP directory can also be entered directly in IP 232.