Reference13r1:Concept Number Resolution and LDAP: Difference between revisions

From innovaphone wiki
Jump to navigation Jump to search
Line 17: Line 17:
Otherwise, you can use every other LDAP Server that you want. The URL is an [https://tools.ietf.org/html/rfc2255 RFC2255] encoded string. The format is explained [[Reference13r1:PBX/Config/General|here]]
Otherwise, you can use every other LDAP Server that you want. The URL is an [https://tools.ietf.org/html/rfc2255 RFC2255] encoded string. The format is explained [[Reference13r1:PBX/Config/General|here]]


Note: There exist a [[#Known_issues|known issue]] for LDAP responses that return an empty value in a specific field
Of course only attributes which exist at the external directory will be resolved.
 
Note: There's a [[#Known_issues|known issue]] that LDAP responses are stopped upon return of empty values in a specific field


=== Contacts App ===
=== Contacts App ===

Revision as of 08:41, 21 August 2019

General

This document shows the V13 concept of number resolution, LDAP search and reverse lookup.

Applies to

This information applies to

  • V13 and up

Reverse Lookup

There is a central backward resolution per PBX for all incoming calls to one dedicated source. A PBX wide Reverse Lookup URL for LDAP queries can be configured under PBX/Config/General.
If a resolution occurs via this mechanism, the resolved Name is given to all other applications/locations. (MyApps, Phones (also DECT), CDRs, Reporting, eg.) This means that no further instance has to perform an LDAP query.

PBX Configuration

If you want to use the central PBX Reverse Lookup you can use one of the following examples for your Reverse Lookup URL.
Otherwise, you can use every other LDAP Server that you want. The URL is an RFC2255 encoded string. The format is explained here

Of course only attributes which exist at the external directory will be resolved.

Note: There's a known issue that LDAP responses are stopped upon return of empty values in a specific field

Contacts App

ldaps://ap.domain.tld/dc=entries?givenname,sn,company?sub?(metaSearchNumber=+%n)?bindname=domain.de\contacts

Estos MetaDir

ldap://metadir.domain.tld:712/dc=meta?givenname,sn,company?sub?(telephoneNumber=+%n)?bindname=username 

C4B

to be tested

PBX as LDAP Server

ldap://ldap.domain.tld/cn=PBX0?dn,e164,email?sub?(&(node=PhoneBook)(e164=000%n))?bindname=telbook

The three zero's before the %n depends on the diable format, how your number is stored in the Phone Directory

For the legacy Howto:Maintaining a Phone Directory in the PBX solution.

Legacy Device Configuration

By default, in V13 the reverse number lookup is done at the PBX and displayed at the phone. Phone originated directories such as internal phone book, pbx access and external ldap are disabled.

Optionally, it is possible to enable the resolution directly at the phone. This is done by unticking the option "Disable Phonenumber Look-up" at Phone/User/Preferences.

The phone will then use the directory settings of the appropriate user, which are defined in the user object or config template.

If the resolution on the local phone provides a result, this is shown instead of the resolution of the PBX.

Be aware that this might lead to a different result than displayed on the PhoneAPP/SoftphoneAPP/CallList etc. as these applications always resolve against PBX-located settings.

Search

Search can be done by use of various sources. Those may be

  • PBX itself (UsersApp)
  • included ContactsApp
  • any other external directories

UsersApp

All PBX users can be searched via the UsersApp.

ContactsApp

Further contacts can be managed and searched within the ContactsApp.

It is possible to define several contact instances hosting different contact data and assign those to dedicated users/config template.

Usage

Configure LDAP query with Contacts e.g. at phone:

  • use of the correct user incl. domain (e.g. domain.de\contacts)
  • Correct password (in plain text in PBXManager/APContacts/configuration)
  • Search attributes:
    • Meta Name Attributes -> metaSearchText
    • Meta Number Attributes -> metaSearchNumber

PhoneApp / SoftphoneApp / myPBX

Search requests can be done via dedicated directory applications such as UsersAPP or ContactsAPP or within the Phone/SoftphoneAPP and also myPBX.

Search requests are performed towards multiple sources in parallel if assigned to the respective user.

User objects and configuration templates offer possibility to define search against the PBX and one external source. In case of more external sources are required (e.g. Contacts and C4B), an LDAP-object has to be defined and assigned to the user.

LDAP Object

To extend the amount of external search sources you can use the LDAP Object in the PBX.

To be defined depending on the external source attributes according to this description.

LDAP object has to be assigned via App-tab to dedicated user / configuration template.

Hardware Phone

Search on the hardware phone is done by use of the configured directories at the phone.

Related Articles

Known issues

  • #60684 - Reverse Lookup URL - empty return value stops parsing further values