Actions
Feature #82
open
Support Grandstream UCM63xx as LDAP client
Start date:
02/18/2026
Due date:
% Done:
90%
Estimated time:
8:00 h
Description
It’s possible to use the Grandstream UCM63xx PBX as the LDAP client so that it will fetch the contacts from L2CPBG and then use that information to re-write the proper header, so the Caller ID will show correctly on all the phones (especially softphone apps that do not have LDAP settings available) and the contact name will be applied to the Call Detail Record logs in the PBX as well.
To get that working, an US user complained that his Grandstream deployment fails about the leading international prefix as well as any US specific formatting like (419)... area code or other punctuation formatting's.
Files
Updated by Jörg Ebeling 9 days ago
Please test this hardcoded test binary if we're on the right track.
Updated by Jörg Ebeling 4 days ago
- File l2cpbg_0.10.1-rc1_amd64.deb l2cpbg_0.10.1-rc1_amd64.deb added
- Status changed from New to Resolved
- % Done changed from 10 to 90
Add a new location.numberFormat option:
# numberFormat: Defines the format of phone numbers returned by the LDAP server.
# "nationalPretty" (default): National format with pretty formatting
# like "(040) 123-456" if your're located in a different area,
# "123-456" if your're located in the same area.
# "nationalPrettyWithArea": National format with area code even if you're located in the same area.
# "nationalDigits": National digits only without formatting like "40123456" (useful for Grandstream UCM63xx PBX).
# "international": International format like "+49 40 123456".
# "e164": E.164 format like "+4940123456".
#numberFormat = "nationalPretty"
Actions