Project

General

Profile

Readme 095 » History » Version 2

Jörg Ebeling, 12/12/2021 10:32 PM

1 1 Jörg Ebeling
# LDAP-2-CardDAV Phone Book Gateway (l2cpbg)
2
3
An LDAP to CardDav (1 way read) Phone Book Gateway.
4 2 Jörg Ebeling
![Functional L2CPBG Diagram](https://projects.shbe.net/attachments/download/159/L2CPBG%200.9.5%20Diagram.svg "Functional L2CPBG Diagram")
5 1 Jörg Ebeling
6
## Use case
7
8
Most modern (business) voice phones have the capability to do
9
comfortable LDAP directory look-up like:
10
11
-   Directory search by alphabet letters
12
-   Reverse lookup for in- or out-bound calls
13
-   Reverse lookup by entering parts or the phone number
14
15
Unfortunately, most of the 'smaller' companies (i guess companies beyond
16
100 employee) don't have an 'enterprise' LDAP directory, much less than
17
private persons.
18
19
Most of such companies do have something like a cloud address book,
20
often based on WebDAV / CardDAV (i.e. Nextcloud, Ownlcoud, Baïkal,
21
Daylite, Synology Contacts, ...).
22
23
This is, where this Gateway might make your live easier.
24
25
If this program (daemon/service) get started on some kind of hardware (Windows, macOS or Linux), it will do the following:
26
27
1.  Synchronize your CardDAV Server, to a small local database cache
28
2.  Wait and answer for LDAP requests from your voice/desktop phone(s)
29
30
## Features
31
32
-   Query the contacts of your CardDAV address book(s) by entering
33
    the alphabetic letters (or parts of the telephone number) in your (LDAP capable) phone (and dial one of the matching numbers)
34
-   Reverse lookup inbound calls and display matching contact
35
    informations on the phone
36
-   Work with local formatted (non- E.164) entered phone numbers
37
    like: '040-123456' or '001 807 1234567' as well as '+49 (0)40
38
    1234567-8', so that there's no need to format the phone numbers of your CardDAV contacts in a special notation
39
-   Supports short internal extension phone numbers as well as Fritz!Box specific **\<extension> or *\<line> format
40
-   Support dial prefix for external line
41
-   Support selection of a specific addressbook per phone, via "ou=\<addressbook>, \<BaseDN>"
42
43
## Usage
44
45
You need some kind of 24/7 machine where this gateway live. Windows PC,
46
Linux, macOS, Raspberry or the like.
47
48
By default it will look for a configuration file in the following places (in the
49
given order):
50
51
1.  ./l2cpbg.conf
52
2.  /etc/l2cpbg.conf
53
3.  /usr/local/etc/l2cpbg.conf
54
4.  \<exec directory\>/l2cpbg.conf
55
56
It will write to a small local database directory (defaults to 'os.TempDir()/l2cpbg.db').
57
58
At the moment there's no "Admin GUI". But for miminimal infos like "uptime", "license", "number of search requests", "number of sent result records", as well as immediate CardDAV-Server sync trigger, you might send the l2cpbg process a `SIGHUP` signal and check the logs afterwards.
59
60
You might be also interested in the output of `l2cpbg --help`.
61
62
## License change
63
Since L2CPBG became more and more usable, it got necessary to ensure that the free version get only used by private persons and not by companies or professionals. That's why I limited the "Free" version to 2 phones (LDAP clients) as well as a max. of 100 contacts.
64
65
Luckily I also got convinced that it would be more approriate (in special for smaller companies) to have a more fair price-matrix instead of a "one for all fee".
66
67
If you get hit by the new limitations of the free version, think about selling a license (also to support further development). Here's the price matrix:
68
69
| Version | max. phones [^1] | Version blaming in Phone Display | max. LDAP requests/h | max. phonebook entries [^2] | Gold features [^3] | Price/€ [^4] |
70
|:----------|:---------:|:--:|:---------:|:---------:|:---:|-------:|
71
|Free       | 2         | ✓  | 12        | 100       | ✗   |   0,00 |
72
|Max3       | 3         | ✗  | unlimited | 500       | ✗   |  29,00 |
73
|Max5       | 5         | ✗  | unlimited | 1000      | ✗   |  49,00 |
74
|Max10      | 10        | ✗  | unlimited | 2000      | ✗   |  79,00 |
75
|Pro10      | 10        | ✗  | unlimited | unlimited | ✓   | 149,00 |
76
|Pro50      | 50        | ✗  | unlimited | unlimited | ✓   | 299,00 |
77
|Enterprise | unlimited | ✗  | unlimited | unlimited | ✓   | 499,00 |
78
79
[^1]: Every device/phone which successful login to L2CPBG, lock a phone-slot (via IP) for 8 hours
80
81
[^2]: In real, the number of imported CardDAV contacts get limited
82
83
[^3]: Gold features are: Multi-instance capability, Multi-CardDAV Server (planned, not yet implemented), Multi-AddressBook-Merge (planned, not yet implemented)
84
85
[^4]: Inkl. German VAT
86
87
Before deciding to buy a license, please ensure that L2CPBG work as expected with all your phones and your CardDAV server. If you can't test it because of the free limitations, or any other reason, don't hesitate to ask for a 60 day evaluation license. Simply drop me a mail to projects@shbe.net with your real name.
88
89
## Installation
90
91
### Linux Debian ".deb" packages
92
93
`dpkg -i l2cpbg_<version>_<architecture>.deb` to install the package.
94
95
- A sample configuration get places at `/etc/l2cpbg.conf`.  
96
- Initial startup will fail due to wrong/missing settings in config section `[dav]`!  
97
- Adapt at least `[ldap]`, `[ldap.bind]`, `[dav]` as well as `[location]` sections (in /etc/l2cpbg.conf) to your need.
98
- Once done, restart l2cpbg by `systemctrl restart l2cpbg` and check startup by `systemctrl status l2cpbg`.  
99
- The full log can be read by `journalctl -u l2cpbg`.  
100
- To watch the actual/live logging, use `journalctl -fu l2cpbg`.
101
102
If l2cpbg started up, adapt your phone(s) to point their "LDAP Directory" lookup requests to l2cpbg with the settings you defined in /etc/l2cpbg.conf.
103
104
### Linux binary "tar.gz" packages ("systemd" Systems)
105
106
1. Extract binary i.e. to /usr/local/bin: `sudo tar xvf l2cpbg_0.9.2_linux-amd64.tgz -C /usr/local/bin/ l2cpbg`
107
2. Extract config file, i.e. to /etc: `sudo tar xvf l2cpbg_0.9.2_linux-amd64.tgz -C /etc/ l2cpbg.conf`
108
3. Adapt config section `[ldap]`, `[ldap.bind]`, `[dav]` as well as `[location]` to your need.
109
4. Do a first foreground start via `l2cpbg` and check terminal output for any issues. \<Ctrl-c\>, edit config and start `l2cpbg` till terminal output is okay.
110
5. If terminal output is okay and everything work as expected. \<Ctrl-c\> to stop forground process.
111
6. Install L2CPBG as service/daemon via `sudo l2cpbg --service=install`. You should see a single "... 'install' succeed" message.
112
7. Now that L2CPBG got installed as a service/daemon you can use `sudo systemctrl start|stop|restart l2cpbg`. When booting next, L2CPBG should get started automatically and log output to systemd journal.
113
8. The full log can be read by `journalctl -u l2cpbg`.  
114
9. To watch the actual/live logging, use `journalctl -fu l2cpbg`.
115
116
Adapt your phone(s) to point their "LDAP Directory" lookup requests to l2cpbg with the settings you defined in /etc/l2cpbg.conf.
117
118
Uninstalling the service/daemon is simply done by `sudo l2cpbg --service=uninstall`
119
120
### Linux binary "tar.gz" packages ("SysV" Systems)
121
122
1. Extract binary i.e. to /usr/local/bin: `sudo tar xvf l2cpbg_0.9.2_linux-amd64.tgz -C /usr/local/bin/ l2cpbg`
123
2. Extract config file, i.e. to /etc: `sudo tar xvf l2cpbg_0.9.2_linux-amd64.tgz -C /etc/ l2cpbg.conf`
124
3. Adapt config section `[ldap]`, `[ldap.bind]`, `[dav]` as well as `[location]` to your need.
125
4. Do a first foreground start via `l2cpbg` and check terminal output for any issues. \<Ctrl-c\>, edit config and start `l2cpbg` till terminal output is okay.
126
5. If terminal output is okay and everything work as expected. \<Ctrl-c\> to stop forground process.
127
6. Install L2CPBG as service/daemon via `sudo l2cpbg --service=install`. You should see a single "... 'install' succeed" message.
128
7. Now that L2CPBG got installed as a service/daemon you can use `sudo service l2cpbg start|stop|restart`. When booting next time, L2CPBG should get started automatically and log output get send to /var/log/l2cpbg.err|log.
129
130
Adapt your phone(s) to point their "LDAP Directory" lookup requests to l2cpbg with the settings you defined in /etc/l2cpbg.conf.
131
132
Uninstalling the service/daemon is simply done by `sudo l2cpbg --service=uninstall`
133
134
### Important macOS upgrade info:
135
If you already have l2cpbg versiom 0.9.2 installed, you need to deactivate your old l2cpbg instance via `l2cpbg --service=stop` and `l2cpbg --service=uninstall`, **before** installing the new version. After installing the new version, activate it again (via `l2cpbg --service=install` and `l2cpbg --service=start`)
136
137
### MacOS "pkg" package ("launchd" System)
138
139
The package (pkg) installer does the following:
140
141
- Extract the L2CPBG package to '/opt/l2cpbg'.
142
- Place a l2cpbg command symlink into '/usr/local/bin' (which is in PATH), so that you're able to call the gateway binary 'l2cpbg' independent of your working directory.
143
- A sample l2cpbg configuration file get places in `/usr/local/etc/l2cpbg.conf`.
144
145
After installation, initial startup would fail due to wrong/missing settings in config section `[dav]`!
146
147
1. Edit config by opening '/usr/local/etc/l2cpbg.conf' i.e. with TextEdit `open -a TextEdit /usr/local/etc/l2cpbg.conf`
148
2. Adapt at least `[ldap]`, `[ldap.bind]`, `[dav]` as well as your `[location]` sections to your need.  When done, don't forget to save!
149
3. Do a first foreground start via `l2cpbg` in Terminal, and check terminal output for any issues. \<Ctrl-c\> (abort l2cpbg), edit config and start `l2cpbg` again, till terminal output is okay.
150
4. If terminal output is okay and everything work as expected. \<Ctrl-c\> (abort l2cpbg) to stop forground process.
151
5. Install L2CPBG as service/daemon via `sudo l2cpbg --service=install`. You should see a single "... 'install' succeed" message.
152
6. Now that L2CPBG got installed as a service/daemon you can use `sudo l2cpbg --service=start|stop|restart`. When booting next time, L2CPBG should get started automatically and log output is send to /usr/local/var/log/l2cpbg.log.
153
154
Adapt your phone(s) to point their "LDAP Directory" lookup requests to l2cpbg with the settings you defined in /usr/local/etc/l2cpbg.conf.
155
156
Uninstalling the service/daemon is simply done by `sudo l2cpbg --service=uninstall`
157
158
Uninstalling the whole package is done by `sudo /opt/l2cpbg/uninstall.sh`
159
160
### Windows binary "zip" packages
161
162
1. Extract content of zip package to your preferred location, i.e. `C:\Program Files\LDAP2CardDAV-Gateway`. Take attention that the 32-bit version should be installted (by convention) somewhere under `C:\Program Files (x86)`!
163
2. Run "notepad" as Administrator, open `C:\Program Files\LDAP2CardDAV-Gateway\l2cpbg.conf` within Notepad, and adapt config section `[ldap]`, `[ldap.bind]`, `[dav]` as well as `[location]` to your need. When done, don't forget to save!
164
3. Now it's time to try a first start of the Gateway. Run a "Command" shell as Administrator and change to the installation directory, i.e. `cd C:\Program Files\LDAP2CardDAV-Gateway`, start it in foreground by `l2cpbg.exe` and check terminal output for any issues. \<Ctrl-c\>, edit config and start `l2cpbg.exe` till terminal output is okay.
165
4. If terminal output is okay and everything work as expected. \<Ctrl-c\> to stop forground process.
166
5. Install L2CPBG as service/daemon via `l2cpbg.exe --service=install`. You should see a single "... 'install' succeed" message.
167
7. Now that L2CPBG got installed as a service you can use `l2cpbg.exe --service=start|stop|restart`. After 'start'ed as service, log entries can be viewed by Windows Event Viewer (eventvwr). When booting next time, L2CPBG should get started automatically.
168
169
Uninstalling the service/daemon is simply done by `l2cpbg.exe --service=uninstall`
170
171
## Configfile syntax
172
173
Since version 0.9.0 the config file syntax has changed from 'ini' to 'toml'. Not a big deal, but you need to adapt some entries. Mainly strings have to be entered within quotes!
174
175
Following a quick minimal sample:
176
```
177
# Comments get started with a hash character
178
179
#
180
# The Gateway will act as LDAP Server, listening
181
# for requests from your phone(s).
182
#
183
[ldap]
184
  host      = "0.0.0.0"
185
  #port     = 1389
186
  base      = "dc=example, dc=com"
187
188
[ldap.bind]
189
  dn   = "cn=pbx"
190
  pass = "your-password"
191
192
#
193
# Your CardDAV server where this Gateway get the contacts from
194
#
195
[dav]
196
  server       = "https://cloudserver.example.com/remote.php/dav"
197
  user         = "cloud-login-name"
198
  pass         = "cloud-login-password"
199
  #pass         = "[AES256]encrypted-cloud-login-password" # Please see command line option '--encryptPassword'
200
201
[location]
202
  int           = 1     # Your international code. 1 = US, 49 = Germany, ...
203
  area          = 807   # Your local area code (without a leading 0)
204
  maxarealength = 7
205
  country       = "EN"
206
```
207
208
### Config file description (by section)
209
210
#### \[ldap\] = LDAP Server settings
211
212
`host` : Which IP to listen for LDAP requests. Defaults to "0.0.0.0" = 'Listen on all interfaces'. You've to point your LDAP phone settings to this machines IP/hostname.
213
214
`port` : Which port to listen for LDAP requests. Defaults to port 1389. The standard LDAP port is 389, so you need to change your phone to the port you configure here.
215
216
`base` : This LDAP's 'base DN'. Choose whatever you want, but use the same settings within your phone's LDAP settings. Defaults to 'dc=example, dc=com'.
217
218
#### \[ldap.bind\] = LDAP bind/auth settings
219
220
`dn` : Distinguish name. Name, how the phone has to log into/authorize
221
to the gateway.
222
223
`pass` : Related 'dn' password, a phone has to use when logging in/authorize to the gateway.
224
225
#### \[dav\] = WebDav/CardDav server settings
226
227
`server` : Your WebDAV/CardDAV server address/URL. Please see 'Limitations'!
228
229
`user` : WebDav username with read access to the relevant addressbook which shall be requested for phone book lookups. Might also be a 'shared' address book.
230
231
`pass` : Related user password. If you don't like to store your CardDAV-Server password in clear-text here, you've also the possibility to use the AES-256 encrypted variant of the password here. Please check l2cpbg's command line option `--encryptPassword` via `l2cpbg --help`. If you already stored the encrypted password variant here, you can also check/validate it with command line option `--testDavPassword`.
232
233
`addressbooks` : Optional regular expression string of matchable addressbook(s)
234
used for phone book lookups. If unsure, enter something. l2cpbg will log
235
all found address books of the logged in CardDav user during startup and
236
log them as 'Non-matching' or 'Matching' address book(s).
237
238
`syncinterval` : Interval of CardDav sync checks. Given as string with suffix 'm' for minutes, or 'h' as hours. Has to be greater than "2m".
239
240
`chunksize` : If an address book get loaded the first time, it get loaded in "chunks of contacts" in this given size. You may increase this value for quicker initial load, but if your CardDAV server answer with an "507 Insufficient Storage" error or similar, you need to lower this value. Default to 200. This option was added in L2CPBG version 0.8.1.
241
242
`insecurecert` controls whether a client verifies the server's certificate
243
chain and host name. If insecurecert is true, crypto/tls accepts any
244
certificate presented by the server and any host name in that certificate.
245
In this mode, TLS is susceptible to machine-in-the-middle attacks unless
246
custom verification is used. This should be used only for testing or in
247
trusted environments. Defaults to *false*. This option was added in L2CPBG version 0.9.1.
248
249
#### \[dav.map\] = CardDav mapping
250
251
`tel` : CardDAV attribute which contain phone numbers. Normally (and
252
by default) 'TEL'. Don't change this, except your really know what you're doing.
253
254
#### \[location\] = Local area settings
255
256
`int` : International area code (1 = North America, ..., 44 = United
257
Kingdom, 49 = Germany, ...) of your location.
258
259
~~`intPrefix` : Dial prefix for international calls. Mostly "00". Defaults to "00".
260
ATTENTION: Has to be entered as string like "00".~~
261
262
`area` : Local area code without leading 0 (20 = London (UK), 40 =
263
Hamburg (DE), ...).
264
265
`areaPrefix` : Dial prefix for national calls. Mostly "0". Defaults to "0".
266
ATTENTION: Has to be entered as string like "0". 
267
268
`maxarealength` : Longest possible length of a telephone number within
269
your local area. If a CardDAV or incoming number is shorter or equal, it's
270
identified as a number within your local area.
271
272
`country` : Two-letter [ISO 3166-1 alpha-2](https://wikipedia.org/wiki/ISO_3166-1_alpha-2) country code (i.e. US, GB, DE, ...).
273
274
`maxintlength` : Maximum length of internal phone numbers. These numbers
275
don't get harmonized or E.164 converted.
276
277
`prettifyNums` : By default phone numbers loaded from CardDAV get prettified in two ways:
278
At first, if a CardDAV number is stored in international format, but you live in the same country, the international part get removed.
279
At second, the number get formatted in (spaced or braced) number groups as it's common in your country.
280
You can disable this prettifying by setting the value to false.
281
282
`prettifyNoAreaInSameArea` : Strip local area code from destination number when located in same area. Boolean true|false, defaults to true.
283
284
`prettifyRemoveSpaces` : Boolean (true|false) which will remove all spaces from a prettified phone number. Defaults to false.
285
286
`extdialprefix` : Optional external dial prefix for getting an external line. Get prefixed before the phone number if outgoing number length \> `maxintlength`
287
288
#### [log] = Logging
289
290
`level` : Log level. Might be one of "trace", "debug", "info", "warn", "error" or "fatal". Defaults to "info".
291
292
The log levels are organized as follows:
293
294
`trace` : This is the most verbose log level. It logs simply everything.
295
Never use it in production environment as it might produce an awful amount of log entries!
296
When started as Windows-Service, 'trace' messages doesn't get send to windows event console.
297
298
`debug` : Logs a lot internal stuff, probably interesting when searching
299
a solution for an issue. Should not be used in production environment as
300
it produce also a lot log entries!
301
When started as Windows-Service, 'debug' messages doesn't get send to windows event console.
302
303
`info` : This is the most usual log level. Logs only stuff which is relevant.
304
305
`warn` : Logs stuff which doesn't behave as expected. Not critical (generic functionality should be okay) but should be noticed/checked.
306
307
`error` : Something essential/critical happened. Functionality is limited or aborted at all.
308
309
`fatal` : Game over.
310
311
#### [db] = Internal database
312
313
`directory` : An own directory where to store the internal database. Defaults to
314
'os.TempDir()/l2cpbg.db' which is not very useful on Linux based systems as it normally get cleaned after each reboot.
315
316
Choose yourself where to store the database.
317
If you've a small CardDAV server with <= 200 contacts, let the DB in the default location.
318
An initial sync of 200 contacts (after a reboot) will be quickly done.
319
Not much storage space is needed. An CardDAV server with approx. 4 thousand contacts, take about 10 MByte storage.
320
321
ATTENTION: If you use one of the .deb packages, the binary get started as user=l2cpbg.
322
Thus, the given directory, manually need to made owned by l2cpbg via
323
`chown -R l2cpbg:l2cpbg /your/db/directory`! Otherwise the DB process will fail on missing read/write permissions!
324
325
#### [ldap.map...] = LDAP/CardDav mapping
326
327
Every LDAP attribute which is used within a phone(s) filter or response, need to have a corresponding CardDav mapping which get done as follows:
328
329
First you need to define a separate block for the LDAP attribute in the following syntax: `[ldap.map.<ldap attribute name (case sensitive)>]`
330
Within such a LDAP mapping block you have to define:
331
332
`dav` : Corresponding CardDav field/attribute name.
333
334
and optional define the following settings:
335
336
`itypes` : Regular expression (RE2 syntax) of including relevant CardDav types or *Apple addressbook label* (Apple Adressbook extension: X-ABLabel).
337
338
`etypes` : Regular expression (RE2 syntax) of **excluding** relevant CardDav types or *Apple addressbook label* (Apple Adressbook extension: X-ABLabel).
339
340
`index` : Zero based index in the case of a multi-value CardDav field.
341
342
For an overview of the predefined/default LDAP/CardDav mappings, take a
343
look into 'l2cpbg.sample.conf' file.
344
345
## Phone configuration
346
347
### Gigaset
348
349
Here's a configuration sample of a Gigaset N510 IP PRO:
350
![Gigaset N510 IP PRO settings sample for L2CPBG 0.7.0](https://projects.shbe.net/attachments/download/19/config_gigaset-n510-ip-pro_v070_de.jpg "Gigaset N510 IP PRO settings sample for L2CPBG 0.7.0")
351
Take attention that 'Server Address' point to the machine where this gateway lives (as well as 'Serverport')
352
353
'BaseDN', 'Common User Name' and 'Common Password' get filled with the same values as defined in your L2CPG config file.
354
355
### Yealink
356
357
Another configuration sample of a Yealink SIP-T52S:
358
![Yealink SIP-T52S settings sample for L2CPBG 0.7.0](https://projects.shbe.net/attachments/download/18/config_yealink-t52s_fw7084_v070_en.jpg "Yealink SIP-T52S settings sample for L2CPBG 0.7.0")
359
Take attention that 'Server Address' point to the machine where this gateway lives (as well as 'Port').
360
361
'Base', 'User Name' and 'Password' get filled with the same values as defined in your L2CPG config file.
362
363
### Snom
364
365
The LDAP configuration of Snom phones look similar to the ones of
366
Gigaset or Yealink.
367
But a user reported that entering `(|(cn=*%*)(sn=*%*)(givenName=*%*)(company=*%*))` within 'LDAP name filter' did the trick for working name searches.
368
369
## Special features
370
371
### Multi-Instances (Pro or Evaluation license required)
372
373
There might be special configuration requirements like different CardDAV Server/Phonebook combinations/permissions, or multi-locations requirements which can't yet configured in L2CPBG.
374
375
For such special cases, you might start multiple L2CPBG instances. Each with his own configuration or even with the more comfortable merge/overlay configuration loading.
376
377
Imagine: You already have a standard instance running, like described within the [Installation](https://projects.shbe.net/projects/l2cpbg/wiki/Readme_093#Installation) section. But now you've a special requirement like a office branch (which has access through your office VPN to your L2CPBG server) for which you need other [location] settings.
378
379
`--instance-suffix` functionality might solve this for you!
380
381
Do the following to configure and install a new instance:
382
383
1. We need to give the new instance some kind of meaningfull name. In the following we decide for 'foo'
384
2. Copy your l2cpbg.conf file (as described in [Installation](https://projects.shbe.net/projects/l2cpbg/wiki/Readme_093#Installation)) to l2cpbg-foo.conf, and open it in notepad (or whichever editor your prefer
385
3. Change the [ldap] port to a free port. I.e. from 1389 to 1390
386
4. If you have configured a [db] directory, give the new instance a separate (and exclusive) db directoy. If you don't have a configured [db] directory entry, you can leave it as it is. By default the db get stored at OS.Tempdir()/l2cpbg-\<instance-suffix\>.db
387
5. Change the configuration stuff why you where interested in a separate instance.
388
6. Test your new configuration in foreground (the same way as you did during the normal instance installation see [Installation](https://projects.shbe.net/projects/l2cpbg/wiki/Readme_093#Installation), but with '--config' option pointing to your new instance configuration.
389
7. Once the configuration is good, you can call `l2cpbg.exe --instance-suffix=foo --service=start|stop|restart` like during normal install (except the additional parameter --instance-suffix=foo)
390
391
When dealing with the configuration of multi-instances, you will heavily benefit from L2CPBG's possibility to do merge/overlay config loading, which is not more than loading each subsequent config on top of the previous one. 
392
By this you'll have i.e. your main configuration in l2cpbg.conf whereas your l2cpbg-foo.conf contains only the two or three config changes you're interested in. Then, by adding `--config=<your config directory>/l2cpbg.conf,<your config directory>/l2cpbg-foo.conf` as l2cpbg command option, it's done.
393
394
## Compatibility
395
396
L2CPBG was tested with:
397
398
-   CardDAV Server:
399
    -   [Baïkal](https://sabre.io/baikal/) version 0.7.x
400
    -   [Daylite](https://www.marketcircle.com/)
401
    -   [Nextcloud](https://nextcloud.com/) version 13, 15, 16, 18, 20, 22
402
    -   [Synology Contacts](https://www.synology.com/dsm/packages/Contacts)
403
-   Desktop & Mobile Phones:
404
    -   [Gigaset](https://www.gigasetpro.com/) N510 IP PRO, N670 IP Pro
405
    -   [Grandstream](http://www.grandstream.com/) GXP2170
406
    -   [Snom](https://www.snom.com/) 300, D315, D335
407
    -   [Yealink](https://www.yealink.com/) SIP-T52S, SIP-T54S, SIP-T54W, SIP-T58 (Android)
408
    -   [Fanvil](https://fanvil.com/) X3U, X7C, X210
409
-   Gateway Host OS:
410
    -   [Debian](https://www.debian.org/) Stretch 9.x, Buster 10.x (running at amd64 as well as ARMv7), Bullseye 11.x
411
    -   [Gentoo](https://www.gentoo.org) amd64
412
    -   [macOS](https://www.apple.com/macos/) ™ Sierra 10.12.6, Catalina 10.15.7, Big Sur 11.6
413
    -   [Ubuntu](https://ubuntu.com/) 20.04 (Focal Fossa)
414
    -   [Windows](https://www.microsoft.com/windows) 10, Server 2016
415
416
## Limitations and Known Issues
417
418
-   The internal LDAP Server doesn't support LDAPS (encrypted LDAP
419
    communication) at the moment. Therefore 
420
    **it should not be used in an untrusted network!**
421
    If you're interested to run it in an untrusted network,
422
    please drop me a short note.
423
424
## Support & getting help
425
426
For getting help or discussing l2cpbg, please browse the [L2CPBG
427
Forum](https://projects.shbe.net/projects/l2cpbg/boards) or check/open
428
the [Tickets](https://projects.shbe.net/projects/l2cpbg/issues) area.
Go to top