[jitsi-users] LDAP contacts


#1

Hi,

Jitsi can correctly list my Active Directory contacts. I can see the telephoneNumber for each contact. And if I click on the phone icon, I can choose to either call via a SIP account or via Jabber/XMPP (I defined 2 accounts: SIP + Jabber). Of course, if I want to call, I need to select "via SIP", and it works. But how can I send a Jabber message to that LDAP user (supposing he is registered, of course)? I would prefer not to add the contact to my "buddy list".

Thanks,

Vieri


#2

For example, Active Directory already has a field called "ipPhone". I could populate this field with, say, "user@jabber.mydomain.org".
However, when I search this user within Jitsi (and add the ipPhone field within Jitsi's LDAP config), I can see that Jitsi translates the letters into numbers so "calling" via my Jabber account won't work.

How can I just tell Jitsi to "call via my jabber account" the "user@jabber.mydomain.org" from the LDAP contact?

Thanks,

Vieri

···

--- On Tue, 4/3/12, Vieri <rentorbuy@yahoo.com> wrote:

Hi,

Jitsi can correctly list my Active Directory contacts. I can
see the telephoneNumber for each contact. And if I click on
the phone icon, I can choose to either call via a SIP
account or via Jabber/XMPP (I defined 2 accounts: SIP +
Jabber). Of course, if I want to call, I need to select "via
SIP", and it works. But how can I send a Jabber message to
that LDAP user (supposing he is registered, of course)? I
would prefer not to add the contact to my "buddy list".


#3

You would have to add them in the buddy list. It is quite rare for XMPP
deployments to allow you to send messages to JIDs that are not on your
roster.

Emil

···

On 03.04.12 19:16, Vieri wrote:

Hi,

Jitsi can correctly list my Active Directory contacts. I can see the
telephoneNumber for each contact. And if I click on the phone icon, I
can choose to either call via a SIP account or via Jabber/XMPP (I
defined 2 accounts: SIP + Jabber). Of course, if I want to call, I
need to select "via SIP", and it works. But how can I send a Jabber
message to that LDAP user (supposing he is registered, of course)? I
would prefer not to add the contact to my "buddy list".


#4

Hey Vieri,

···

On 03.04.12 19:16, Vieri wrote:

Hi,

Jitsi can correctly list my Active Directory contacts. I can see the
telephoneNumber for each contact. And if I click on the phone icon, I
can choose to either call via a SIP account or via Jabber/XMPP (I
defined 2 accounts: SIP + Jabber). Of course, if I want to call, I
need to select "via SIP", and it works. But how can I send a Jabber
message to that LDAP user (supposing he is registered, of course)? I
would prefer not to add the contact to my "buddy list".

You would have to add them in the buddy list. It is quite rare for XMPP
deployments to allow you to send messages to JIDs that are not on your
roster.

Emil

--
http://jitsi.org


#5

Maybe you could add this to the Jitsi TODO list:

Jitsi should NOT transcribe letters to numbers for the LDAP "phone fields" , or at least give the user/admin the option to enable/disable this feature. This way, one could set an LDAP field (such as AD's ipPhone field or any other) to an alphanumeric string such as "user@jabber.mydomain.com". So when a Jitsi user searches for an LDAP contact and clicks on the green phone icon, there will be a choice to call via "SIP" or "Jabber" or whatever other account and "user@jabber.mydomain.com" will be displayed correctly.

Am I making sense? :wink:

Thanks,

Vieri

···

--- On Tue, 4/3/12, Vieri <rentorbuy@yahoo.com> wrote:

For example, Active Directory already has a field called
"ipPhone". I could populate this field with, say, "user@jabber.mydomain.org".
However, when I search this user within Jitsi (and add the
ipPhone field within Jitsi's LDAP config), I can see that
Jitsi translates the letters into numbers so "calling" via
my Jabber account won't work.

How can I just tell Jitsi to "call via my jabber account"
the "user@jabber.mydomain.org"
from the LDAP contact?


#6

Hi Emil,

OK but is there an "easy" aka user-friendly way of doing it?
As I can tell, after searchng for an LDAP contact, I can click on the "add contact" icon and it shows me a list of field values it took from the LDAP directory, such as e-mail addresses. Selecting one of these addresses (which could be a jabber JID@domain) brings me to a dialog window that allows me to select an account, etc. Is that the way to go?

Thanks,

Vieri

···

--- On Wed, 4/4/12, Emil Ivov <emcho@jitsi.org> wrote:

Hey Vieri,

On 03.04.12 19:16, Vieri wrote:
> Hi,
>
> Jitsi can correctly list my Active Directory contacts.
I can see the
> telephoneNumber for each contact. And if I click on the
phone icon, I
> can choose to either call via a SIP account or via
Jabber/XMPP (I
> defined 2 accounts: SIP + Jabber). Of course, if I want
to call, I
> need to select "via SIP", and it works. But how can I
send a Jabber
> message to that LDAP user (supposing he is registered,
of course)? I
> would prefer not to add the contact to my "buddy
list".

You would have to add them in the buddy list. It is quite
rare for XMPP
deployments to allow you to send messages to JIDs that are
not on your
roster.


#7

Hey Vieri,

Hi Emil,

OK but is there an "easy" aka user-friendly way of doing it? As I can
tell, after searchng for an LDAP contact, I can click on the "add
contact" icon and it shows me a list of field values it took from the
LDAP directory, such as e-mail addresses. Selecting one of these
addresses (which could be a jabber JID@domain) brings me to a dialog
window that allows me to select an account, etc. Is that the way to
go?

If there are multiple contacts registered for the LDAP entry then we
need to ask you which one you want in your contact list.

The same goes for the accounts. If you have more than one account in
Jitsi then we need to know where you want the new contact added. We
can't just pick one for you.

Both of these dialog boxes should only appear if there's more than one
possible choice.

Emil

···

On 04.04.12 19:54, Vieri wrote:>

--
http://jitsi.org


#8

Hi Emil,

When a user hovers over an LDAP search result, there are basically two (or at least 2) "sections": "phones" and "email". In the "phone" section, there can be listed several "work phone numbers", "home numbers", etc.

Q1: can Jitsi avoid translating letters into numbers as far as the LDAP "phone" fields are concerned? That would allow a user to correctly list, say, a jabber URL and then select "Call via - jabber account".

If Q1 can't be fulfilled then can Jitsi list an extra "section" called "Jabber", right before "e-mail"? This way, users will know for sure that they need to add that JID to their buddy list.

Thanks for the great software.

Vieri

···

--- On Thu, 4/5/12, Emil Ivov <emcho@jitsi.org> wrote:

If there are multiple contacts registered for the LDAP entry
then we
need to ask you which one you want in your contact list.


#9

Hey Vieri,

If there are multiple contacts registered for the LDAP entry
then we
need to ask you which one you want in your contact list.

Hi Emil,

When a user hovers over an LDAP search result, there are basically two (or at least 2) "sections": "phones" and "email". In the "phone" section, there can be listed several "work phone numbers", "home numbers", etc.

Q1: can Jitsi avoid translating letters into numbers as far as the LDAP "phone" fields are concerned? That would allow a user to correctly list, say, a jabber URL and then select "Call via - jabber account".

I don't believe we are doing any translation of "letters to numbers"
anywhere in Jitsi. Are you seeing a different behavior anywhere?

Emil

···

On Thu, Apr 5, 2012 at 5:59 PM, Vieri <rentorbuy@yahoo.com> wrote:

--- On Thu, 4/5/12, Emil Ivov <emcho@jitsi.org> wrote:

If Q1 can't be fulfilled then can Jitsi list an extra "section" called "Jabber", right before "e-mail"? This way, users will know for sure that they need to add that JID to their buddy list.

Thanks for the great software.

Vieri

--
http://jitsi.org


#10

If I set, say, the string "me@jabber.mydomain.org" in an LDAP/AD field such as the field ipPhone in Microsoft Active Directory and then configure Jitsi to list the ipPhone field within the "work phone" section, then I won't be able to see the string within Jitsi after searching that contact. Instead, I will see a long number, which I'm guessing is some sort of string-to-number conversion but it could be some other artifact.

Vieri

···

--- On Thu, 4/5/12, Emil Ivov <emcho@jitsi.org> wrote:

I don't believe we are doing any translation of "letters to
numbers"
anywhere in Jitsi. Are you seeing a different behavior
anywhere?


#11

Hey Vieri,

···

On 05.04.12 18:52, Vieri wrote:

--- On Thu, 4/5/12, Emil Ivov <emcho@jitsi.org> wrote:

I don't believe we are doing any translation of "letters to
numbers" anywhere in Jitsi. Are you seeing a different behavior
anywhere?

If I set, say, the string "me@jabber.mydomain.org" in an LDAP/AD
field such as the field ipPhone in Microsoft Active Directory and
then configure Jitsi to list the ipPhone field within the "work
phone" section, then I won't be able to see the string within Jitsi
after searching that contact. Instead, I will see a long number,
which I'm guessing is some sort of string-to-number conversion but it
could be some other artifact.

Again, we are performing no such conversions and we just show whatever
we receive from LDAP. Could it be your active directory?

Emil

--
http://jitsi.org FAX: +33.1.77.62.47.31


#12

Hey

If I set, say, the string "me@jabber.mydomain.org" in an LDAP/AD
field such as the field ipPhone in Microsoft Active Directory and
then configure Jitsi to list the ipPhone field within the "work
phone" section, then I won't be able to see the string within Jitsi
after searching that contact. Instead, I will see a long number,
which I'm guessing is some sort of string-to-number conversion but it
could be some other artifact.

Again, we are performing no such conversions and we just show whatever
we receive from LDAP. Could it be your active directory?

Whatever performs that translation, it is there. I just tested it out, Vieri
is not seeing phantoms. E.g. ingo@jitsi.org becomes 464654874674. This
number appears in the tooltip of the LDAP result as well as in the
contextmenu for adding a contact.

And my Active Directory is definitely not bogus :slight_smile:
For reference, the ipPhone attribute is of type Unicode String, replicated
to the GCs and not indexed (so probably slow to search).

Could it be that the Google-Library that parses the phone numbers does that?
Take a look at a dialpad with letters mapped to digits:
4=i
6=n
4=g
6=o
@ not mapped
5=j
You get it...

Emil

Regards,
Ingo


#13

And I assume you did try this with a regular LDAP client and in there
the ID appeared as a regular jid?

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).

Emil

···

On 05.04.12 23:13, Ingo Bauersachs wrote:

Hey

If I set, say, the string "me@jabber.mydomain.org" in an LDAP/AD
field such as the field ipPhone in Microsoft Active Directory and
then configure Jitsi to list the ipPhone field within the "work
phone" section, then I won't be able to see the string within Jitsi
after searching that contact. Instead, I will see a long number,
which I'm guessing is some sort of string-to-number conversion but it
could be some other artifact.

Again, we are performing no such conversions and we just show whatever
we receive from LDAP. Could it be your active directory?

Whatever performs that translation, it is there. I just tested it out, Vieri
is not seeing phantoms. E.g. ingo@jitsi.org becomes 464654874674. This
number appears in the tooltip of the LDAP result as well as in the
contextmenu for adding a contact.

And my Active Directory is definitely not bogus :slight_smile:
For reference, the ipPhone attribute is of type Unicode String, replicated
to the GCs and not indexed (so probably slow to search).

Could it be that the Google-Library that parses the phone numbers does that?
Take a look at a dialpad with letters mapped to digits:
4=i
6=n
4=g
6=o
@ not mapped
5=j
You get it...

Emil

Regards,
Ingo

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31


#14

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. 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.

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).

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
LDAP config.

Emil

Ingo


#15

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.

OK.

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
LDAP config.

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).

Emil

···

On 05.04.12 23:54, Ingo Bauersachs wrote:


#16

Yes, it seems that we do normalize the LDAP numbers. My bad.
Vieri,
apologies for confusing you.

No problem!

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.

Maybe normalization could be enabled/disabled by the user or admin because it would be nice to be able to make a direct call ("Call via SIP") of an alphanumeric SIP URI from an LDAP contact listing and not just from the search bar.

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).

Yes, it would be better or even give it its own section.

Thanks,

Vieri

···

--- On Thu, 4/5/12, Emil Ivov <emcho@jitsi.org> wrote:


#17

What about a check (maybe additional) for '@' symbol? Jabber/SIP account
will contain it always (AFAIK), 1-800 probably never?

Just my 0.2 cents.

Tomas

···

On 6.4.2012 0:49, Emil Ivov wrote:

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.


#18

What about a check (maybe additional) for '@' symbol? Jabber/SIP account
will contain it always (AFAIK), 1-800 probably never?

Just my 0.2 cents.

Tomas

···

On 6.4.2012 0:49, Emil Ivov wrote:

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.