[cisco-voip] jabber directory lookup attributes (UDS)

Justin Steinberg jsteinberg at gmail.com
Wed Aug 5 15:49:51 EDT 2015


Yes you can just delete the ldap directory & authentication and rebuild it
with the new telephone number mapping.  the users wont disappear (even
though it will warn you they will).     that should take care of the
inbound caller ID extension mapping as well.

On Wed, Aug 5, 2015 at 3:46 PM, Matthew Loraditch <
MLoraditch at heliontechnologies.com> wrote:

> I can’t remember when this was added, it might be in 9,  but I know in 10+
> you can temporarily convert everyone back to local users and then redo the
> sync. That would make sure no one got deleted. When and how you can do that
> depends on how heavily dependent you are on that ldap information.
>
>
>
> Matthew G. Loraditch – CCNP-Voice, CCNA-R&S, CCDA
> Network Engineer
> Direct Voice: 443.541.1518
>
> Facebook <https://www.facebook.com/heliontech?ref=hl> | Twitter
> <https://twitter.com/HelionTech> | LinkedIn
> <https://www.linkedin.com/company/helion-technologies?trk=top_nav_home> |
> G+ <https://plus.google.com/+Heliontechnologies/posts>
>
>
>
> *From:* cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] *On Behalf
> Of *Lelio Fulgenzi
> *Sent:* Wednesday, August 5, 2015 3:40 PM
> *To:* Justin Steinberg <jsteinberg at gmail.com>
> *Cc:* cisco-voip at puck.nether.net
>
> *Subject:* Re: [cisco-voip] jabber directory lookup attributes (UDS)
>
>
>
>
>
> Thanks Justin,
>
>
>
> I'm gathering options, so that might definitely be a possibility. Not sure
> how I would handle that though, basically, having to create a new LDAP sync
> without deleting the existing users.
>
>
>
> I'm also trying to resolve how Jabber does a search on the UDS contacts
> with an inbound caller ID (extension). Apparently, that's the only time the
> directory lookup rules are used?
>
>
>
> ugh. this was supposed to be easy. :)
>
>
>
> Lelio
>
>
>
> ---
> Lelio Fulgenzi, B.A.
> Senior Analyst, Network Infrastructure
> Computing and Communications Services (CCS)
> University of Guelph
>
>
>
> 519‐824‐4120 Ext 56354
> lelio at uoguelph.ca
> www.uoguelph.ca/ccs
> Room 037, Animal Science and Nutrition Building
> Guelph, Ontario, N1G 2W1
>
>
> ------------------------------
>
> *From: *"Justin Steinberg" <jsteinberg at gmail.com>
> *To: *"Lelio Fulgenzi" <lelio at uoguelph.ca>
> *Cc: *cisco-voip at puck.nether.net
> *Sent: *Wednesday, August 5, 2015 2:29:12 PM
> *Subject: *Re: [cisco-voip] jabber directory lookup attributes (UDS)
>
>
>
> someone correct my if I'm wrong, but I don't think Jabber will search any
> of the custom LDAP attributes as part of cucm dirsync.      I would
> recommend configuring your directory numbers in AD in the ipPhone field in
> the format YYYYY.   then change your cucm dirsync so that cucm imports
> the ipPhone field into CUCM as the CUCM telephone number.    that why you
> won't need any dial rules or lookup rules for this setup.
>
>
>
> On Wed, Aug 5, 2015 at 10:54 AM, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
>
>
>
> Trying to find a way around the way telephone numbers are stored in our
> Active Directory so Jabber users can search by DN.
>
>
>
> Right now, we're using UDS so that way the experience is the same on
> premise and off-premise. CUCM is LDAP integrated with Active Directory.
>
>
>
> Unfortunately, our telephone numbers are stored as follows:
> "+1-NPA-NXX-XXXX xYYYYY". (small x is a literal x, big X and Y are 0-9)
>
>
>
> The dashes and blank are ignored, but the little x is interpreted as a 9,
> so in Jabber, a directory search using the user name shows
> "+1NPANXXXXXX9YYYYY"
>
>
>
> For the most part, I can build dial rules to work around this, dropping a
> whole bunch of digits before dialing so that way only the extension is
> dialed.
>
>
>
> But searching for extensions is gonna be almost impossible since I can't
> write a directory lookup rule to include the spaces, etc.
>
>
>
> I'd like to be able to use the other attributes mentioned here:
>
>
>
>
> http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/10_5/CJAB_BK_D6497E98_00_deployment-installation-guide-ciscojabber/configure_directory_integration.html#CJAB_RF_A590F694_00
>
>
>
> I'm just wondering if I simply use "otherTelephone" and "otherTelephone"
> in the custom LDAP synchronization fields. Will it only take the first one?
>
>
>
> Anyone else play with this?
>
>
>
> Lelio
>
>
>
>
>
> ---
> Lelio Fulgenzi, B.A.
> Senior Analyst, Network Infrastructure
> Computing and Communications Services (CCS)
> University of Guelph
>
>
>
> 519‐824‐4120 Ext 56354 <519%E2%80%90824%E2%80%904120%20Ext%2056354>
> lelio at uoguelph.ca
> www.uoguelph.ca/ccs
> Room 037, Animal Science and Nutrition Building
> Guelph, Ontario, N1G 2W1
>
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150805/0fe3b508/attachment.html>


More information about the cisco-voip mailing list