calling through jabber showing different name than calling through phones???

[baselzind]

i noticed today when i created a new 7940 phone that when i called it using my jabber it showed a different name than what it is actually assigned to under the line , calling it using another phone shows the correct name , when i checked the name it was for an end user in the AD but he didnt have a phone but had the same extension in his user profile , how do i fix this please?

[Jaime Valencia]

You cannot "fix" this as this is WAD, Jabber will go back to the directory to find a user who matches the called number, and will bring the first one it matches, the only way to fix this, is to avoid having the same number in two users.

[baselzind]

then under line , the display name and the alerting name have no effect???

[Jaime Valencia]

Not for Jabber, that only works for ip phone to ip phone calls.

[Gilmar Silva]

Hello community

About this, I did some test with a similiar scenario.

It seems the lookup always returns the first user that was set with the number in the AD.

If you remove the number in the first user, clear the Jabber cache, and set the number again, you will see the second user.

So, I am considering that, if you create a generic user (maybe something to represent the department) and set his number in the first time, you will never see the other two users with the same number.

I will do more tests to be sure.

Regards,

Gilmar Silva

[baselzind]

what is WAD?

[jakeriley]

It's an esoteric acronym for "Working as Designed".  We ran into this recently and the fix was fairly simple.  If I remember right, we just searched the contacts and called the new user from Jabber by name as opposed to the dialing the number.  Seems like it displayed correctly once the new association was made.  My apologies if you're already beyond that - but thought I'd mention it.  Not very scalable, but simple enough.

[iptsupport]

Do you have a document on this issue?

[voc-unibi]

Is everything still the same or has something changed in recent years? Is there a way to change the behavior?

[AJB1965]

It's still occurring on Jabber 14.2 and CUCM 12.5 so I assume no, nothing has changed.