Reference13r3:Concept Number Resolution and LDAP: Difference between revisions
Jump to navigation
Jump to search
(New page: === URL definition === In general, reverse lookup uses the above created result after number conversion with prefixes. Depending on the use phone book source, the reverse lookup URL might...) |
No edit summary |
||
| Line 9: | Line 9: | ||
** if phone book entries are stored in international format with "00xyz", leading "00" may be prepended by using this notation: '00%n' | ** if phone book entries are stored in international format with "00xyz", leading "00" may be prepended by using this notation: '00%n' | ||
* %u - h323 name of the current object. Used to change the relationship of the searchbase to the user. A specific LDAP source can be requested depending of the user which receive the call. | * %u - h323 name of the current object. Used to change the relationship of the searchbase to the user. A specific LDAP source can be requested depending of the user which receive the call. | ||
: See [[{{NAMESPACE}}:Concept_App_Service_Contacts#Reverse_Number_Lookup_for_Personal_Directories | Reverse Number Lookup for Personal Directories]] for how the PBX's LDAP client handles user information | |||
==== Contacts App ==== | ==== Contacts App ==== | ||
Revision as of 09:25, 28 March 2023
URL definition
In general, reverse lookup uses the above created result after number conversion with prefixes. Depending on the use phone book source, the reverse lookup URL might look different. The number handed over to those source needs to be adapted by use of following variables:
- %n - cgpn
- if phone book entries are stored in international format with "+xyz", leading "+" may be prepended by using this notation: '+%n'. This is the default setting configured by Installer.
- if phone book entries are stored in international format with "00xyz", leading "00" may be prepended by using this notation: '00%n'
- %u - h323 name of the current object. Used to change the relationship of the searchbase to the user. A specific LDAP source can be requested depending of the user which receive the call.
- See Reverse Number Lookup for Personal Directories for how the PBX's LDAP client handles user information
Contacts App
ldaps://ap.domain.tld/dc=entries?givenname,sn,company?sub?(metaSearchNumber=+%n)?bindname=domain.de\contacts
Contacts is asked by further instances (e.g. PhoneAPP) for details about the found contact via websocket query.
Estos MetaDir
ldap://metadir.domain.tld:712/dc=meta?givenname,sn,company?sub?(|(telephoneNumber=+%n)(mobile=+%n)(homePhone=+%n))?bindname=username
C4B
ldap[s]://c4b.domain.tld:[Port]/vdir=VDir?givenname,sn,company?sub?(|(telephoneNumber=+%n)(mobile=+%n)(homePhone=+%n))?bindname=c4b.domain.tld\telbook
Active Directory
ldaps://domain.tld:636/OU=tld,OU=company,DC=city,DC=LOCAL?givenname,sn,company?sub?(|(telephoneNumber=+%n)(mobile=+%n)(homePhone=+%n))?bindname=domain\username
PBX as LDAP Server
This refers to the legacy PBX-directory solution.
ldap://ldap.domain.tld/cn=PBX0?dn,e164,email?sub?(&(node=PhoneBook)(e164=000%n))?bindname=telbook