User Tools

Site Tools


ldap_on_unify_openstage_openscape

LDAP on Unify OpenStage

This setup has been confirmed to work on a Unify OpenStage 60 SIP with firmware V3R5.21.0 SIP. It should also work on the OpenStage 40/80 SIP; the OpenStage 15/20 only have LDAP from certain firmware versions on. The example uses the EPVPN directory.

General server settings are described on LDAP Phonebook.

Important: no empty attributes in the template

Unify's example templates leave unused fields empty (ATTRIBxx=“”). Do not do this. The phone sends every empty field as an empty attribute name in its search request, and the server then closes the connection without an answer. The phone shows this as “No matches found”, even though the server, search base and filter are all correct.

Fill every ATTRIBxx line with an attribute name instead, as in the template below. The name does not have to exist in the directory; unused ones just stay blank on the phone.

1. Directory settings

Open the phone's web interface (WBM) at https://<phone-ip> and log in as administrator. Go to Administrator → Local functions → Directory settings:

Setting Value
Server address guru3.eventphone.de
Server port 389
Authentication Simple
User name ou=EPVPN
Password any value

Binding as ou=<event> is optional. Anonymous authentication also works, because the search base below already selects the event.

2. LDAP template

Create a plain text file, e.g. ldap-template.txt:

OpenStage LDAP TEMPLATE (v.1)
SEARCHBASE="ou=EPVPN,dc=eventphone,dc=de"
ATTRIB01="sn"
ATTRIB02="givenName"
ATTRIB03="telephoneNumber"
ATTRIB04="otherTelephone"
ATTRIB05="mobile"
ATTRIB06="homePhone"
ATTRIB07="ou"
ATTRIB08="l"
ATTRIB09="department"
ATTRIB10="title"
ATTRIB11="mail"
ATTRIB12="sn"
EOF
  • For another event, replace EPVPN in SEARCHBASE with that event's ou.
  • ATTRIB12 turns on wildcard search (firmware V3R3 and later), so typing part of a name finds it.

What appears where on the phone:

Template field Phone field eventphone attribute Content
ATTRIB01 Last name sn Name, e.g. “PoC Hotline”
ATTRIB03 Business 1 telephoneNumber Extension, e.g. 2000
ATTRIB07 Company ou Event, e.g. EPVPN
ATTRIB08 Address 1 l Location
ATTRIB12 (search only) sn Used for wildcard search

The other fields are fillers; eventphone has no data for them.

3. Upload the template

  1. Put ldap-template.txt on a file server the phone can reach (FTP, or HTTPS where the firmware offers it).
  2. In WBM, go to Administrator → File transfer → LDAP.
  3. Enter the server, path and file name, and start the download.

NOTE: even the latest firmware does not support modern TLS and fwiw only supports TLS 1.0 and TLS 1.1 and refuses plain HTTP, therefore it's recommended to use the FTP download

The phone stores the file as /data/ldap/ldap-template.txt.

On the phone, open Contacts → Corporate directory (the LDAP tab) and search by name.

  • Type a single word, e.g. PoC. A space splits the input into last name and first name, and eventphone has no first names, so two-word searches never match.
  • The name search only looks at sn. Searching for an extension number does not work there.

Troubleshooting

  • “No matches found”: first check for empty ATTRIBxx=“” lines in the template (see above).
  • Check the template is loaded: in WBM, go to Diagnostics → Fault trace configuration, turn up the directory/LDAP components and do a search. The trace should show Template file found at /data/ldap/ldap-template.txt and LDAP search base = ou=EPVPN,dc=eventphone,dc=de.
  • See the exact request: the trace does not show the LDAP filter or attribute list. To see them, point the phone at a test LDAP server you control, or capture the traffic on port 389 with Wireshark (filter: ldap).
ldap_on_unify_openstage_openscape.txt · Last modified: by luxploit

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki