LDAP not matched

[thomas.betz1@vodafone.com]

Hello,
I have the problem that we have to enter the number after E164 in our LDAP directory with +49 for Germany.
The call is not displayed with +49 but with 0.
Does anyone have an idea how to set this up?
With other manufacturers you can tell the phone your country code is +49 and this matches the searches in the LDAP server.

When I search in the LDAP server I find the names.
The server connection is fine, we just don't match because the number
+49 711652245723 is stored in the LDAP and the caller arrives on the phone with the number 0711652245723.

[ahancock]

(04-09-2024 09:40 PM)thomas.betz1@vodafone.com Wrote:  Hello,
I have the problem that we have to enter the number after E164 in our LDAP directory with +49 for Germany.

Following this.. as I'm facing the same issue in the US

I can put +12255551212 in the LDAP, but incoming calls are 2255551212 and so they aren't matched

Same goes with the local directory.. incoming calls are matched only if the local directory is entered as 2255551212

If there was a way for the yealink to attempt a match using our default country code.. +1 that should work.

Fixing this will help with RingCentral's new External Shared Contacts Directory which we are trying to use.

[thomas.betz1@vodafone.com]

Yes, that's exactly how SNOM solved it.
RingCentral does not want or cannot adapt their LDAP, meaning it can only be solved by Yealink, otherwise the customers will not be happy with the Yealink devices in relation to Ringcentral.

[thomas.betz1@vodafone.com]

now it works!!!


ldap.call_in_lookup
phone_setting.reverse_lookup.contact_list.replace.pattern=(\+49)*(.+)
phone_setting.reverse_lookup.contact_list.replace.with=$2
phone_setting.reverse_lookup.incoming_call.replace.pattern=^00|^0
phone_setting.reverse_lookup.incoming_call.replace.with=