You are correct, that is where you would use the normalization rules text file, or adjust the 7 digit UCM string into E.164.
From: Erick Wellnitz [mailto:[email protected]] Sent: Wednesday, May 7, 2014 3:48 PM To: Matt Slaga (AM) Cc: cisco-voip Subject: Re: [cisco-voip] info sent to Lync for RCC Okay. I see what is being sent and Lync is not matching the calling number to the address book. From what I understand Lync uses Telephone Number from AD as the Work telephone number displayed on the Lync contact card and uses this as the lookup field. What happens then is the 7 digit extension is not matched and the lookup fails. Is this where we would use normalization rules or is there a better way to do this? On Wed, May 7, 2014 at 10:13 AM, Matt Slaga (AM) <[email protected]<mailto:[email protected]>> wrote: Erick, Lync will perform a Reverse Number Lookup (RNL) on a dialed or received number against the Lync address book service, which is pulled nightly from AD. Your traces from CUPS will show the CSTA signaling outbound to Lync. You can also perform traces on Lync to see the inbound and RNL. You will not see anything from UCM to Lync directly. From: cisco-voip [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Erick Wellnitz Sent: Wednesday, May 7, 2014 10:55 AM To: cisco-voip Subject: [cisco-voip] info sent to Lync for RCC Does anyone kow what I should be looking for to see what information gets passed from IM/P or CUCM to Lync for RCC? I'm specifically looking for caller ID information sent to Lync. I'm sure I'm missing it or don't have th eappropriate trace turned on. Thanks! itevomcid
_______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
