tag:blogger.com,1999:blog-2158853543793456735.post204388839160194635..comments2023-10-02T04:50:01.667-07:00Comments on VoIPNorm's Collaboration Blog: More on Lync Inbound NormalizationChris Normanhttp://www.blogger.com/profile/07200178774058910421noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-2158853543793456735.post-4127788100089212612011-04-05T13:05:38.862-07:002011-04-05T13:05:38.862-07:00To normalize inbound caller id you will need to ap...To normalize inbound caller id you will need to apply translation rules/patterns to the caller id from CUCM. I did it based on the inbound route pattern in CUCM that was bound for Lync and prefixed +1etc,etc,etc to the caller id but I am sure there are other ways to do it in CUCM using translation patterns.<br /><br />Cheers<br />ChrisChris Normanhttps://www.blogger.com/profile/07200178774058910421noreply@blogger.comtag:blogger.com,1999:blog-2158853543793456735.post-4404892758215124162011-04-05T11:36:01.468-07:002011-04-05T11:36:01.468-07:00Chris,
We have a Direct SIP from CUCM to Lync. Wh...Chris,<br /><br />We have a Direct SIP from CUCM to Lync. While I understood different level of Normalization, What I am seeing is I am not able to normalize Source number in Lync. So basically, if a user is associated with user dial plan and user is receiving a PSTN call, Caller id is not getting normalized to E.164 and hence if the number shwos up in "Frequent contacts", it is is not dialable. <br /><br />Where as if the user makes an outbound call that works fine as through user dial plan, it gets converted to E.164 format.<br /><br />Any idea how can I normalize Source number to E.164.<br /><br />This was not an issue in OCS 2007 R2 as mediation server was assigned Location profile where as in Lync all the dial plan looks like are to convert destination number and not Source number.Anonymousnoreply@blogger.com