Using LDAP on Fanvil Phones

In this example, we will demonstrate how to configure and use LDAP phonebook using a Fanvil X4.

Configuring LDAP

  1. Log in the Fanvil X4 web interface, navigate to “Phonebook > Cloud phonebook > LDAP settingspage.
  2. Fill in the LDAP server address, attributes and filter information. 
  3. Once the configuration is done, click “Apply”.


LDAP Configuration Example

The example configurations are set according to S-Series LDAP server default settings. You can use the following settings as a starting point and adjust the filter and display attributes according to your needs.

Display Title: LDAP

Version: Version 3

Server Address:   (IP address of Yeastar S-Series IPPBX)

Server Port: 389

Authentication: None

Line: SIP1 (Line of extension which register on Yeastar S-Series IPPBX)

User Name: cn=admin,dc=pbx,dc=com

Password: password

Search Base: dc=pbx,dc=com

Enable Calling Search: √

Telephone: telephoneNumber

Mobile: mobile

Other: home

Display Name: cn

LDAP Name Filter: objectclass=*

Using LDAP Phonebook

  1. Press the Phonebook key to access it on the Fanvil X4 idle screen.
  2. Press “LDAP” soft key.
  3. Enter the search parameters for name or number as needed.
  4. Press the navigation key to select the desired contact.
  5. Press “Dial” to call the person.
Have more questions? Submit a request


  • 0

    I'm using Version, phone is able to detect calls coming in but when trying to access ldap through the phone's menu the phone is stuck at a "loading" screen. (ldap doesn't contain a lot of user, about 100 users but roughly 20-30 of those have phone numbers in them)

    I wonder if it has to do with the default 'telephone' field I've changed...

  • 0

    ok I've solved the issue but I can't get the "ldap number filter" to work (doesn't show in the screenshot since it shows up on the new firmware)

  • 0

    same problem here

    LDAP Name Filter and LDAP Number Filter

    when i press ldap

    it shows useless data

    and i can not search even





  • 1

    Ethan, it had to do with poor implementation on fanvil's part. it didn't save the username field as it should since the field was limited to X characters and the ldap path was too long.

    so I put the username in a shorter ldap path. the phone didn't crawl for username/contacts so I redirected the phone to one location where I store all of my contacts and this is how it works.

    It works when someone calls in from outside but doesn't work when an extension calls another extension, for those I update the phones manually. I guess half a solution is better then none


    oh and I think it has issues with non English characters

    Edited by Shachar Petrushka
  • 0

    Tnx for the reply Shachar

     after upgrading to the latest frame ware I eliminate  field limitation, also the phone loads the contacts but the search result its not satisfying. how did you redirected the phone to another location? did you use Cloud phonebook URL?

    if so please guide me how you did this?


    Edited by Ethan Hanif
  • 0

    Let's see. in phonebook -> cloud phonebook -> LDAP (Lightweight Active Directory Protocol) Settings

    server address is your domain name like domain.local

    authentication: simple

    version is version 3

    server port is 389 (you can use telnet to check if the port is open and not blocked, you'll have to install telnet via windows settings -> apps -> add windows features or something like it)

    username is in the format of cn=username,ou=businessOU,dc=domain,dc=local

    password is the username password

    enable calling search is checked (when the phone calls somewhere else, although I couldn't figure out extension to extension calling with LDAP)

    Search Base is ou=contacts,ou=users,ou=City,ou=businessOU,dc=domain,dc=local

    Search line is set to auto

    then what you're actually looking for like telephone is set to telephonenumber

    mobile is mobile

    display name is cn

    other is homephone

    ldap name filter is objectclass=*

    LDAP Number Filter is (TelephoneNumber=*)


    I remember I had issues as well and had to dig to find some information. I also think I had issues with non English characters and simply used English (I wonder if a firmware update fixed that issue as well).

    I couldn't manage to get calling extension to extension to work with LDAP, I thought about opening a case/emailing Fanvil but didn't.

    I was also thinking of a way to distribute the config via IIS but was in a dilemma on how to limit the testing phase to only my phone.

    Edited by Shachar Petrushka
Please sign in to leave a comment.