msRTCSIP-OptionFlags Set to 2147483007

I just love my luck sometimes.

So, I hear from one of my co-workers that some accounts have this really odd number for their msRTCSIP-OptionFlags attribute. He is very concerned about what this means.

Research will take you down the path of http://technet.microsoft.com/en-us/library/bb663647(v=office.12).aspx. The long and short of this TechNet article is that the ms-RTCSIP-OptionFlags attribute is a simple bit mask and that each bit identifies whether a setting has been enabled or disabled. The bits from 1-1024 are all documented in the TechNet article. For example, if the number is odd, that means the first bit has been flipped and that the user has been Enabled for public IM connectivity.

Here are the documented bits.

· 1: Enabled for public IM connectivity

· 2: Reserved

· 4: Reserved

· 8: Reserved

· 16: RCC (remote call control) Enabled [Telephony]

· 64: AllowOrganizeMeetingWithAnonymousParticipants (allow users to invite anonymous users to meetings

· 128: UCEnabled (enable users for unified communications)

· 256: EnabledForEnhancedPresence (enable user for public IM connectivity)

· 512: RemoteCallControlDualMode

· 1024: Enabled auto-attendant (enables the use of auto attendant)

I just happen to notice that “32” is missing for some reason. So, assuming that every documented bit is flipped, you would get 11111011111, which is equal to 2015. So, how in the world do you get a number of over 2 million? Short answer is that you don’t.

So, back to the number 2147483007 that equates to 1111111111111111111110101111111 in binary. In this case, “32” is flipped, but it isn’t documented. Of course, all of the numbers from 2048 and higher are not documented either.

Microsoft’s response? “Oh, that must be wrong. You should fix it.”

So, fix it, I did. There are a couple of ways to fix it.

  1. Delete the offending users (yes, there were several, but not a large percentage by any means) from OCS and then re-enable them and re-configure them.
  2. Manually set them using PowerShell. I found that it was much easier after installing the Quest module. I ended up using the following cmdlets: get-qaduser <UserName> | set-qaduser -oa @{‘msRTCSIP-OptionFlags’=’257’}

Of course, “257” is not what everyone needed, but that is just one example.

Advertisements
This entry was posted in Lync, Office Communications Server. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s