(08-09-2017 02:44 AM)Paul Wrote: (08-07-2017 12:53 PM)StefanL Wrote: Hi,
I'm operating a larger LDAP directory. Some people have a set of numbers for mobile phones, office, lab numbers, etc. Unfortunately, there is no way to see the number type behind the number.
Is there a chance to separately search for the LDAP number attributes in order to be able to distinguish between the number types?
Example:
LDAP number attributes: "IPphone mobile Telephone"
Phone display - now:
Name: Number1
Name: Number2
Name: Number3
Phone display - wish:
Name in Headline
IPphone: Number1
mobile: Number2
Telephone: Number3
The next step would be to self-define values for displaying the number type:
LDAP number attributes: "IPphone mobile Telephone"
LDAP number attributes replacement strings: "Office Mobile LabX"
Phone display shows:
Name in Headline
Office: Number1
Mobile: Number2
LabX: Number3
Regards, StefanL
Dear Customer,
This is Paul from Yealink Technical Support Team, nice to meet you.
About your query, we will support the LDAP feature in V82 version, like below:
Name in Headline
Number1:
Number2:
Number3:
……
Attached is the picture for your reference.
About the LDAP number attributes: "IPphone mobile Telephone", they are configured in the server side. You can change it in the LDAP server.
We will release the official V82 version next month.
BR
Paul
Hi Paul,
thanks for the reply...
Maybe I did not make myself clear.
My request was on distinguishing the number type, like office number, mobile number, assistent number, Lab number, etc.
Number1, Number2, Number3, ... does not help here.
It's also confusing that - depending on the available LDAP entries - the number type (of Number1, Number2, Number3) change. E.g. if I have a LDAP entry at 'telephoneNumber' , Number1 is the always the 'telephoneNumber' number. If I do not have an entry at 'telephoneNumber' (on LDAP server), Number1 could be the mobile or whatever number.
I dont know your implementation, but IMHO it should be simple to implement that feature.
1. By parsing the output of the single LDAP search or readout the result structure
2. By doing separate searches for each number attribute. (Pseudocode: foreach entry in "LDAP number attribute" do ldapsearch -LLL cn sn entry)
Of course, I can use standard attributes on the LDAP server or self-define attributes - that is not the point.
With the suggested "LDAP number attribute replacement string" it's possible to use a standard LDAP scheme such as inetOrgPerson. The "LDAP number attribute replacement string" is a phone-internal thing. It is just a 1:1 mapping and defines, which number type description the phone end user sees on the phone display. This implementation is very simple and flexible for the phone administrator.
Best regards,
StefanL.