And I assume you did try this with a regular LDAP client and in there
the ID appeared as a regular jid?
Jup, Softerra LDAP Browser.
Yes, it seems that we do normalize the LDAP numbers. My bad. Vieri,
apologies for confusing you.
But actually this is independent from the actual
attribute used, it could be any. Try adding 'mail' into one of Jitsi's phone
lookup configuration and you see the same thing happening.
Phone numbers are also parsed btw. +41 76 xxx xx xx becomes the same number,
but without spaces.
Well yeah. That's the whole point after all.
Also, what would be the point of entering a JID in the work phone field?
Why not adding it in the IM field? (Althoug a SIP ID would admitedly
make sense there).
The ipPhone could be added to the E-Mail fields, then it appears as a normal
JID and you can chose one of the addresses to add it as a contact. Doesn't
solve the problem for non-numeric SIP addresses though, were you'd expect to
be able to click the call-button without adding a contact first (E-Mails
aren't even listed as an option to call someone).
When calling numbers from the search bar we only normalize them if they
don't contain letters (thanks Yana for checking this out).
We could apply the same logic to the numbers we get from LDAP ... but in
that case we'll also lose the functionality for 1-800-GO-FEDEX numbers.
And what IM field are you referring to? Another LDAP-attribute? A Jitsi
config? If the latter, then there isn't such a thing as an IM field in the
I was referring to the mail field (and we should probably change its
name to something like "IM/Mail" to indicate that this is what we are
using it for).
On 05.04.12 23:54, Ingo Bauersachs wrote: