Lync Normalization Rules

We are running Lync Server 2013.
I'm trying to build a dial plan with several extension ranges. The range I'm working with is 3001-4417. When I try to add the normalization rule below, I get the message "The builder does not support advanced regular expressions. To start
using the builder, click Reset. To modify the regular expression manually, click Edit."
Pattern -
^([3]\d\d[1-9]) | ([4][0-4][01-][0-7]$
Translation -
+1734895
I can add the separate expressions but would like to narrow the number of rules down.
Thanks,

Ranges like this can get rough. How precise do you need to be? If you use ^(3\d{3}|4[0-4]\d{2})$ for example, that would be 3000-4499. If 3000 normalizes or 4418, does it matter much? If not, you could stick with that. Otherwise,
you could really dive in but your rule might get long. Your pattern above wouldn't work because 3200 and 4218 wouldn't work even though they're in the range.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications
This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Similar Messages

Normalization rules seem to be used but ipPhone telephone number not appearing in contact cards

We keep our CUCM-style telephone numbers in the AD ipPhone attribute. The format is 000-0000.
I have added a normalization rule to Company_Phone_Number_Normalization_Rules.txt to make these E.164-ish and to add a prefix (3) that we use to route calls from Lync to CUCM.
Testing both with abserver.exe and observing a trace, the rule is being applied correctly.
args[1]: 824-2072
824-2072 -> tel:+38242072
    Matching Rule in Company_Phone_Number_Normalization_Rules.txt on line 19
        ^(8\d{6})$
Component: ABServer
Function: Contact.AddAttribute
(ABServer,Contact.AddAttribute:contact.cs(317))(0000000036D00C4F)Id: 13 Name: ipPhone Value: tel:+38242072
However, I still don't see this +38242072 in the contact card.   I tried looking in the rtcab.dbo.AbAttributeValue table and I also don't see any ipPhone (ID 13) values there.
I looked in absconfig.exe and the "Include phone number value that is currently present in AD for the phone attributes" option is selected (first choice).
Should I instead be using "Use normalization rules and include normalized number"?

There are still a few folks where the numbers aren't being published as expected. To review, we have this normalization rule:
## Company_Phone_Number_Normalization_Rules.txt
## 824-2072 -> 3-8242072
(8\d{6})
3-$1
and these two users (LDIF format):
dn: CN=User with incorrect Lync contact data
telephoneNumber: +1 (123) 456-5009
otherTelephone: +1 (123) 456-5009
ipPhone: 810-5009
mobile: +1 (123) 533-5009
dn: CN=User with correct Lync contact data
telephoneNumber: +1 (123) 456-5034
otherTelephone: +1 (123) 456-5034
ipPhone: 810-5034
mobile: +1 (123) 533-5034
The "good" user ends up with this "other" attribute (as seen from a dbimpexp.exe dump:
<phone type="other">
<readOnly>true</readOnly><displayString>810-5034</displayString>
<uri>tel:3-8105034;phone-context=enterprise</uri>
</phone>
The "bad" user ends up with the E.164 number repeated.
<phone type="other">
<readOnly>true</readOnly>
<displayString>+1 (123) 456-5009</displayString>
<uri>tel:+11234565009</uri>
</phone>
Where else should I be looking to figure out this inconsistency?

Voice Routing: Normalization Rule vs. Route

We're just testing some Enterprise Voice stuff within our Lync Environment but there's still one Thing not clear to me: On the specific user tab, we're able to assign a "Dial plan policy" and a "Voice policy"
In the Dial plan policy we're able to enter the normalization rules for Digit Manipulation.
In the Voice policy we can assign routes the call will take (e.g trunk).
But for example if there is a normalization rule which translates +402221111 to 1111 and on the route there are just numbers allowed starting with 1, why the call will fail? In my opinion the number should be translated to 1111 right after dialing and
this should match the proper route.
Can someone describe how the callflow is working in Detail. Will it maybe check for the specific route before there is any Digit Manipulation process?
Thanks in advance

Typically you'd do it the other way around, you'd translate 1111 to +402221111 so that it's in proper E.164 format, and you'd have your routes match that.
What you described should work though, at a very high non-mechanical level:
A number is typed into Lync
The number is normalized by the users dial plan (typically to a standard such as E.165)
The normalized number is compared against the voice policy, which will match if it finds a route that matches that's tied to the policy through a PSTN usage.
An INVITE is sent through the trunk using the path determined.
What kind of errors are you getting and do you get a "pass" in the Lync Control Panel -> Voice Routing -> Test Voice Routing when you enter the information? If not, you've got a typo or misconfiguration somewhere and giving more detail
will help.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications
This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Plus sign normalization rule

Hi all,
I am new to Lync so pardon in advance.
I have a set of normalization rules that allow a user to dial a number starting with a plus sign. this works fine for me (North America) while dialing international numbers. what I have today removes the + , adds +011. But more often than not there
are north american numbers that have plus sign. this would translate a +17162223333 to +0111716222333 which is not correct.
Can someone help me as to how create a rule that would leave out north american numbers?
cheers

I agree with Michael, Ken Lasko is the kind of Lync dial plans, definitely read that article, it should clear a lot up. Ken also has tools for automatically creating Dial Plans with proper normalization.
The + is the 011, they're the same prefix, just in different formats. You should never have +011 as a result, even on international numbers, because it's redundant.
So, a US phone number dialed as 17162223333 should normalize to +17162223333 and a South African phone number dialed as 01127315551212 should normalize to +27315551212. As it leaves Lync, you may need to modify that so your Telco
understands it, so at the gateway you might strip the +, or +1, and you may need to add the 011 at your gateway or as a translation rule on your trunk.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications

Extensions normalization rules with dis-contiguous DID's

Hi all,
I have about 250 users who had 3 digit extensions before moving to Lync. Unfortunately my provider was unable to give me DIDs that would have same last 3 digits. Now in order to give my users extensions, Do I and Can I create normalization rules? would it
not slow down the performance of the server or is there another way to do it?
Thanks

So yes, you will create normalization rules for each range (or each number if they're all non-contiguous), unfortunately there's no way around doing this. It should not slow down the performance of the server.
If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer"
Georg Thomas | Lync MVP
Blog www.lynced.com.au | Twitter
@georgathomas
Lync Edge Port Check (Beta)
This forum post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Normalization rule issue OCS 2007 R2

I've recently noticed a number of "Invalid_AD_Phone_Numbers" appearing.
Upon investigation it looks like these uses where added with a different phone number pattern to what is currently been setup in the normalization rules.
I'd like to modify/add a new normalization rule to handle these new numbers.
The current normalization rule is
^(\d*)$
+$1
Which seems to handle just numbers. The new telephonenumbers are coming through
1. (xx) xxxx xxxx
2. xxxxx/xxxxx - They're including 2 extensions
3. xxxxx or xxxxx - They're including 2 extensions
I can cope with 2 and 3 not working but number 1 I need to find a solution for.
Has anyone got a suggestion/solution.
Thanks

The best tool OCS 2007 R2 is route helper http://technet.microsoft.com/en-us/library/dd572316(v=office.13).aspx
http://technet.microsoft.com/en-us/library/dd425124(v=office.13).aspx
http://technet.microsoft.com/en-us/library/dd572368(v=office.13).aspx
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer" Regards Edwin Anthony Joseph

Voice Routing and Normalization Rules

Hello All,
I am very weak about Lync ENT voice. I want to configure the Lync 2013 for below scenarios.
PABX extensions – 2xx, 3xx.
Lync extensions – 4xx
Access code – 9 for external access (This will be added from the AudioCodes gateway)
What should i configure ?

please may i know the Build Numbers of latest patches ?
i have Cu4 on of Lync 2013 Server.
Should i want to add below line ?
$x = New-CsClientPolicyEntry -Name "ShowExtensionInFormattedDisplayString" -Value "True"
$y = Get-CsClientPolicy -Identity Global
$y.PolicyEntry.Add($x)
Set-CsClientPolicy -Instance $y

Adding participants to the conference by dilout

Hi everyone,
We have a problem with Lync 2013 conferences.
When we try to add a participant by calling him to the phone number - we receive error that "Phone number can not be reached".
If try to add the same number few times - it will dial normally. It usually takes up to 4 times for number to be dialed.
If dial directly from Lync (not from the conference) - no one have any problem.
Can some one suggest something?
P.S.
We have 2013 Lync, containing 3 FE servers with collocated meditation servers and DNS load balancing. 2 EDGE servers, also with DNS load balancing. And 2 Cisco ISR as BorderElements.
I'm not able to find any related error in event log.
In Call reports - there is still no usefull information (

Hi,
This happens with multiple numbers randomly. It can be so that you need to redial number 4 times to dial out and next day same number will dial out from the first try.
It happens when users dial out from the conference to any PSTN destination.
And we transform all numbers to International with Lync normalization rules.
Internally we have numbers like "tel:+37517293*****;ext=7XXX"
We have only one DialIn plan with region assigned.
S C:\Windows\system32> Test-CsDialInConferencing -TargetFqdn mypool.scnsoft.com
arget Fqdn : mypool.scnsoft.com
esult : Success
atency : 00:00:27.9162636
rror Message :
iagnosis :
Any other idea?
Hi,
Did the issue happen only for one special number or for multiple numbers?
Did the issue also happen if other Lync users start Lync conferences and add a participant by calling him with the phone number?
Did the number you invited a PSTN number or an internal phone number?
Please check if all dial plans are assigned regions. If not, you can run the
Get-CsDialPlan and
Set-CsDialPlan cmdlets to make sure that all dial plans have a region assigned.
You can use the Test-CsDialInConferencing cmdlet to test that the access numbers for the specified pool work correctly.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Lync Phone Edition - extension normalization search

Hi Guys,
Here is what I got going on:
Lync Enterprise Voice Standard Edition - single frontend - single edge.
Lync User LineURI = tel:+1222333xxxx;ext=xxxx
Active directory user telephone number = +1222333xxxx
Lync dialplan normalization rule - Internal Extension - ^(47\d{2})$ --> +1222333$1
This setup allows all call flow to work spectacularly well. Except... when a user dials the 4 digit extension on the lync phone edition (polycom cx600) the translation rule kicks in and changes it to E.164. Example: user dials 4784 and it normalizes
the number to +12223334784. This again works great except it never associates the translated number to a lync user account. so no presence, no contact card with other numbers, etc.
Additional information: Lync client (2013 and Skype for business) - when i input 4784 into the "find someone or dial number" field, it will normalize the number and show 2 contacts. 1. the first contact it shows is the same as lync
phone edition, only the normalized number. 2. the second contact is the lync user with presence and additional numbers, etc.
So my question is this: What settings above should be adjusted in order for a 4 digit extension to be associated with the user in all searches?
I thought that if i normalized the extension to the AD telephone attribute it would search and find the correct contact but it seems that is not the case.
What settings from above should i adjust to make extension dialing seamless for my users.
Thank you for reading this long post. I look forward to your insights!
-Brandon

Hi Brandon,
Here’re some suggestions for your reference.
1. It’s recommend to install the latest update of the Lync Phone Edition for your device.
2. Have you tried to sign in by connecting the device to your computer by using a USB cable ?
3. Try to configure the value of client policy parameter AddressBookAvailability to WebSearchOnly.
Best regards,
Eric
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Questions on Lync 2010 to 2013 Addressbook Migration

Hi Team,
We are in the process of migrating the users from Lync 2010 to Lync 2013 pilot pool.
https://technet.microsoft.com/en-us/library/jj205160.aspx
According to the above article, basically the Lync Server 2010 Address Book is migrated along with the rest of your topology and don’t have to worry about the post migration steps if we don’t have customized settings such as GAL partition (By setting
up an attribute ‘msRTCSIP-GroupingID’), customized AB normalization rules and customized phone normalization rules.
Questions:
1. How do we confirm that there is no customized settings of phone normalization, AB normalization and GAL partition in the existing Lync 2010 environment?
2. Is there any powershell command to validate the current Lync 2010 settings?
Please advise.
Many Thanks.

The grouping ID is not something you'd normally put in. If all users can search for and see all other users, you'd be fine.
For the AB normalization look for Company_Phone_Number_Normalization_Rules.txt in your Lync file share in
X-WebServices-X\ABFiles (replace the X with whatever you see). If you have one, you could copy it over to your new Lync 2013 file share. This file is for normalizing phone numbers found in AD. To validate current settings, you can run
the BPA http://www.microsoft.com/en-us/download/details.aspx?id=4750 but if you're moving away from it, I wouldn't kill myself resolving issues. From PowerShell, there
are many things you could validate, is there something specific you're worried about?
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications
This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Lync User Phone Number Changed in AD - Still Showing Old (Normalized) Number Days Later in Lync Client Contact Detail

Environment: Lync 2013 backend; Lync 2010 and Lync 2013 clients. Enterprise Voice not implemented. November 2013 CU Applied on Server.
Issue: Lync user (User A) phone number changed in AD but still showing old number for others days later.
Believed Cause: User A has not logged into Lync since change to republish new phone number?
So after reading this http://masteringlync.com/ I am beginning to think that something I perceived as an issue may actually be by design?
Action:
User A work phone number changed in AD. User A has only one phone entry in AD. Normalization rule in place to basically leave number unchanged (working)
Result:
New phone number propogated fine to Exchange/Outlook fine. Old number displaying only in Lync client when viewing User A contact card detail
Lync 2010 Client displays only old number when looking at Client A contact detail (this client only presents phone numbers if they are actually normalized)
Lync 2013 Client displays two work numbers.
One that we identify as a "display number" just as entered in AD - this shows correctly as the new number. Another that we identify as the "normalized number" which is still the old
number (same as 2010 Client)
Same results whether contact is saved in Lync Client or not and is not related to Outlook contacts - in fact one test was with a Lync account that is not Mail Enabled.
I did a dbanalyze to view the SQL database detail for User A and see that Category 'userInformation' has the old phone number and the time stamp on it seems to coincide with a Lync Cllient database change (user login or refresh on that end) so this seems
to futher confirm my findings thus my reaching the point of conceding it might be out of my control.
My Question I guess is ....
Have others discovered this? Is this a bug or do normalized phone numbers actually requre a client login to accept/republish the number correctly to others even though the information is updated in AD? User detail and how it propogates seems to
be the biggest mystery and it gets harder and harder to explain to users why changes aren't displaying accuralely.

Thanks Richard... your blog definitely hit home with what I was seeing but guess I just didn't want to accept that as the end of the road on this. I'm still in a little misbelief that client interaction is necessary to update a backend change.
This process really makes phone numbers in Lync an unreliable source given a user will never know if it is it up to date. And the problem with Lync 2013 client is it shows both numbers in the client ... the address book one with the
updated AD numbers and the one the normalized AD one that the user has to login to republish. I now more fully understand the process but trying to explain that to users when they see different work numbers .. ugh.
Oh well, guess the important part is to understand the process so thanks again.

AD contact user not showing up in Lync

Hello,
I'm trying to add Active Directory contact users in my Lync adress book but it seems not working.
AD contact have correct phone number (E164) and i run "update-csaddressbook" and "update-csuserdatabase" on my Lync server. I have also deleted GALContacts on my Lync client profil but if i search "JordanExternal" (name of my
AD Contact) no result are returned.
My AD contact users seems to be correctly save in Lync database, this query return a result :
"SELECT [UserId],[AdDn]FROM [rtcab].[dbo].[AbDnMapping] where AdDn like '%JordanExternal%'"
I'm using Lync hosting pack so i try to set "tenantid" and "groupingid" attributes on my contact like other Lync user of this organization but this does not solve the problem..
Thanks
Cordialement,
Jordan
Ing&eacutenieur syst&egravemes - OPENHOST
Si vous trouvez ma r&eacuteponse utile, merci de voter ;)

I'd like to point out that the AD contact phone number should comply to E.164 numbering format or it will be dropped from the Address Book.
By default the ABS sync happens at 1:30 am (an event of the failed entries will be recorded a few minutes after the event in the Front Ends Event Log).
The results are recorded on your Lync Share at \\Server\LyncShare\1-WebServices-1\ABFiles\00000000-0000-0000-0000-000000000000\00000000-0000-0000-0000-000000000000\Invalid_AD_Phone_Numbers.txt
You have 2 choices in how to resolve this.
1. Simply edit the AD contact to comply to eg +6495xxxxx
2. Add a normalization rule set to be used during the ABS Sync called Company_Phone_Number_Normalization_Rules.txt
(let me know if you want more info on this one)
If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As
Answer" | Blog lyncsorted.blogspot.com

How to append work numbers to lync clients

could anyone explain me how to set this up:
I have 2 users in a test environment
the standard for danish tel number seems to be eg. +45 12345678
i want to append 20304050 to user1 and 20304051 to user 2, with extension 9000 & 9001
what is the exact tel uri i need to use, and how do i set up nomalization for these to be able to call eachother, i have looked at various guides and examples, but i simply dont get the system behind. my goal is to be able to call out via enterprise voice.
any help would be greatly aprecciated.
my setup includes:
doman lynclab1.local
lync fe on 10.10.21.2
ad on 10.10.21.1
user1 on 10.10.21.3
user2 on 10.10.21.4
mediation with 2nics 10.10.21.5 & 192.168.1.8 for external access.
at this time i havent set up the pstn gateway, is this crucial for my users to call eachother by number internally, at this time im only able to call by username.

I would think:
tel:+4520304050;ext=9000
and
tel:+4520304051;ext=9001
Create a normalization rule like this:
Description: Extensions
Starting digits: 900
Length: Exactly 4
Digits to remove: 3
Digits to add: +452030405
With this, the users could call each other by dialing the extension, and outbound enterprise voice calls would look like the E.164 +45xxxxxxxx number.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications
i have set up these parameters, but i am still not able to call between 2 internal users by using extensions. i havve also tried pushing the address book, without any result.

Lync 2010 - Using DID numbers and extensions that do not correlate

Hi everyone,
I have a situation that I believe is unique and am trying to find a good way to deal with it. I am hoping that someone out there may have a different view on how we might achieve the goal of using our existing collection of extensions and DID numbers. Here
are the implementation details...
- Around 200 locations that each have a gateway for local PSTN in and out calling
- One Enterprise Pool running Lync 2010 to service all locations
- 90%+ sites have DID numbers, however the DID numbers are not in complete blocks. There are skips in the numbers.
- Extension ranges are unique per location and have been in place for years
- DID numbers and extensions do not have any common parts... ie tel:+13275551212;ext=78943
The challenge is that we are moving the locations over into the Lync 2010 environment from a Cisco deployment and in planning out the steps, it appears that we would need to create a unique normalization rule per number that is similar to the example above.
Because the locations span different area codes that have the ability to dial 7 digit and 10 digit numbers is not consistent, we would need to have multiple dial plans. If we need different dial plans and unique normalization rules per extension
number, we would need to ensure that the all of the extension numbers normalize across the dial plans requiring that we include the unique extension normalization rules in each dial plan. (wow I sure hope you can follow this) So 200 locations with 20
norm rules each will add up quickly.
The real solution I have come up with is to migrate to Lync 2013 but this is not an option until next year. We also need to send out the correct unique CLID for the users who have a DID.
Here are the other possible solutions I have came up with each have a draw back.
- No unique CLID for outbound calls
- One Dialplan and everyone dials 10 digits externally
- Gateway adjusts a "common" base number based on extension to a unique CLID. This may not be able to be done on the existing gateways.
- An additional gateway that can adjust the outgoing CLID is put in to make changes to all CLID's based on extension.
- Create a unique normalization rule for each number set and assign that normalization rule to every other dial plan. - The long road that I think may have performance issues
due to the size of the normalization rules needed.
I really appreciate any thoughts or ideas on this one.
Cheers,
Ken Braley Voice Data Systems

Hi,
As you said, you can only use one dial plan and everyone dials 10 digits externally, however,
if your organization maintains a single dial plan across multiple locations, you may still need to create a separate dial plan for Enterprise Voice users who are migrating from a private branch exchange (PBX) and who need to have their existing
extensions retained.
If you want to keep the DID numbers like before, I think you may need to create a separate dial plan for every users.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Problems with SNOM 7XX phones and presence of Lync Edge server

Hi to all,
we have this problem, this is the scenario (two Lync 2013 st ed. servers):
- lync 2013 FE server have internal IP address 172.21.212.XXX with internal gateway 172.21.212.254
- lync 2013 edge server have two network interface:
First INTERFACE: 3 IPs in 172.21.30.XXX (Access, web and A/V Edge) for external connection with 172.21.30.254 and internal gateway (IP NAT with public IP)
Second INTERFACE: IP 172.21.212.XXX for internal connection without gateway
- snom 7XX (50 phones) are connect to the lync server and all internal call works fine. All phones are in an internal dedicated network 172.21.218.XXX with default gateway 172.21.218.254
- when making external call with 7XX SNOM phones, the call was routed to Trunk COLT with Lync Mediation server and all works fine.
- when Lync Mediation server receive a call from our trunk COLT we have this situation:
All Lync 2013 clients work fine, audio is OK, (network 172.21.216.XXX)
Polycom CX3000 work fine audio is OK (network 172.21.218.XXX)
SNOM 710, 720, 760 FW 8.8.2.16 UC series, phones ring but NO SOUNDS from the phones and after a few seconds "Call failed due to network issues."
The only way to solve the problem is to disable the connection with Lync Edge server (remove gateway 172.21.30.254)
BUT this is not the solution because now we have no connection with INTERNET (skype, web conferencing doesen't work without edge gateway)
Why SNOM phones try to use the EDGE gateway to connect the call? Why doesn't use Lync Mediation server?
Can you help us to find a solution?
Thanks
Aurelio

Hi,
Thanks to all for yours support.
Today, we have done some test (no employee in office today
J) and we have solved the problems.
The old implementation have had this configuration:
- the phone numbers have had a no E.164 format compliant: for all users number, the phone number have had this format TEL:012345XYZW ; EXT=XYZW with the normalization
rules:
Starting digits: 01234567
Length: At least 8 digits
Digit to remove: 0
Digit to add: nothing
Pattern to match ^(01234567\d*)$
All worked fine with this previous configuration:
Lync 2010 std with only mediation server function + Lync 2013 std front-end with all the others functions and Lync 2013 std Edge server for external connection with
Lync client Skype world, BUT we have had disabled in SNOM phones ICE function because if ICE was enabled no voice can we hear from the phones.
After dismissed Lync 2010 with only a Lync 2013 infrastructure, this configuration don’t permit to use edge server because with ICE enabled or disabled no voice from
SNOM phones.
Today we have done this operation:
Setting in Lync 2013 control panel all number for all users, in E.164 format compliant:
The phone number now have this format TEL:+39012345XYZW ; EXT=XYZW and we have deleted the previous normalization roles.
We have added this role for the EXT numbers:
Name: Routing Interno
Starting Digits: XY
Length: Exactly 4 (i.e. XYZW)
Digit to remove 0
Digit to add: +39012345
Pattern to match: ^(XY\d(2))$
Translation rule: +39012345$1
Internal extension = checked
And now all work fine.
We have solved another problem:
Lync client 2013 can't find new users:
all new Lync users are not discovered from Lync 2013 client, probably because this setting is present with Lync 2010:
PS C:\> Get-CsAddressBookConfiguration
Identity
: Global
RunTimeOfDay
: 1:30 AM
KeepDuration
: 30
SynchronizePollingInterval : 00:00:30
MaxDeltaFileSizePercentage : 20
UseNormalizationRules
: True
IgnoreGenericRules
: False
EnableFileGeneration
: True
With only Lync 2013 servers we have changed
IgnoreGenericRules to True
To set UseNormalizationRules and IgnoreGenericRules to true for Lynk 2013 infrastructure.
http://technet.microsoft.com/en-us/library/jj205160.aspx
For us all the problems are SOLVED!
Aurelio

Lync Normalization Rules

Similar Messages

Maybe you are looking for