[cisco-voip] LDAP custom filter for ipPhone field

[John Snow]

I'm with you guys on +E164 as well.
Thanks for the suggestions, i have some options to consider, well see how it goes.



Sent from my iPhone

On Oct 22, 2015, at 8:03 PM, NateCCIE <nateccie at gmail.com<mailto:nateccie at gmail.com>> wrote:

I completely second the proposal to use +E.164 in directories.

What I haven’t figured out what the right thing to do for non-DID extensions.

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Anthony Holloway
Sent: Thursday, October 22, 2015 7:59 PM
To: John Snow <John.Snow at cnrl.com<mailto:John.Snow at cnrl.com>>
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] LDAP custom filter for ipPhone field

You're right about CUC being able to manipulate the data it pulls from AD.  That's a pretty good feature of CUC, though, I've never seen it used before.  But, still nice to have options like that.
For a while now, I have been proposing +E164 directories, so that numbers are dialable from any device, any acquisition, any merger, etc.  Maybe you can just get AD updated to +E164 and add that functionality into the dial plan?  You could relatively easily script the update into AD so that your change is bulk in nature.

On Thu, Oct 22, 2015 at 4:37 PM, John Snow <John.Snow at cnrl.com<mailto:John.Snow at cnrl.com>> wrote:
Yeah what happened here is an AD migration took place to consolidate two domains with two CM clusters (A=4 digits, B=10 digits). The ipPhone field on ClusterA was being entered as 10digits so the business wanted me to write a script to strip it down to 4 – not my recommendation so I was hoping this was not possible ☺
I thought based on the default filter ipphone=* ,  that * in itself was a regular expression and it would be possible to write something more elaborate similar to what UCXN can do.

Regards,

John Snow
Senior VoIP Analyst
Canadian Natural Resources Limited
Suite 1800, 324 – 8th Ave SW
Calgary AB, T2P 2Z2
T:  403 517 7238<tel:403%20517%207238>
C:  587 585 2924<tel:587%20585%202924>
Email: john.snow at cnrl.com<mailto:john.snow at cnrl.com>

From: avholloway at gmail.com<mailto:avholloway at gmail.com> [mailto:avholloway at gmail.com<mailto:avholloway at gmail.com>] On Behalf Of Anthony Holloway
Sent: Thursday, October 22, 2015 3:07 PM
To: John Snow
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] LDAP custom filter for ipPhone field

Just so you know the LDAP filters do not manipulate data synced in from LDAP.  They simply filter which records will be synced.  If you already have the ipPhone field filled in, within LDAP, as the last 4 of the phone, then you're probably only missing the mapping in the LDAP directory.  It looks like this:

[Inline image 1]

I believe in 9.1(2) you cannot change this field on the fly.  Instead, you have to delete the integration and then re-add it with that field set.  In CUCM 10x you can just change it whenever you want.

I hope that helps.

On Thu, Oct 22, 2015 at 3:33 PM, John Snow <John.Snow at cnrl.com<mailto:John.Snow at cnrl.com>> wrote:
I am searching for a regular expression(s) syntax to import the last 4 digits from the ipPhone field attribute.  Anyone know if this can be accomplished in CUCM 9.1.2 ?


Regards,

John Snow
Senior VoIP Analyst
Canadian Natural Resources Limited
Suite 1800, 324 – 8th Ave SW
Calgary AB, T2P 2Z2
T:  403 517 7238<tel:403%20517%207238>
C:  587 585 2924<tel:587%20585%202924>
Email: john.snow at cnrl.com<mailto:john.snow at cnrl.com>


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip[puck.nether.net]<https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_cisco-2Dvoip&d=CwMFaQ&c=aCXjXS7ZZ-mOR1xNksNgTg&r=0dwR7MgCdcKS3L4tuPBDuwL8G7meAwcyDgMIephsLj8&m=XCQaqLO7tgU5cE4sY2wA9IQLz2nFhh0lZFZghE705oc&s=MA1OO6ZEC29yb4Y0C0D6j6guwbMAF8_ulwT3zwRcKAE&e=>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20151023/40388a00/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 12620 bytes
Desc: image001.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20151023/40388a00/attachment.png>