Monthly Archives: July 2009
Taken from Microsoft UC Team:
The RTC Sustained Engineering Team has signed off and published the July update packages for R2!
Updates for Communications Server 2007 R2
Update for Communicator 2007 R2: July 2009
Office Communicators Server 2007 R2 Attendant hotfix rollup package: July 2009
Office Communicator 2007 R2 Phone Edition update: July 2009
1. The Knowledge Base articles are being published and all should be available within 24 hours.
2. All of these patches are now available via Microsoft Customer Support Services (specifically, the Unified Communications Support Team), except for the Communicator Phone Edition R2 release, which is available via web download.
3. We will also have the OC 2007 R2 on Microsoft Update today. The OCS 2007 R2 (server update) will not be on Microsoft Update due a dependency on the back-end fix that cannot be delivered via Microsoft Update.
4. KB 968802 is a rollup of all OCS 2007 R2 released patches. This KB article will be continuously updated as newer patches are released.
Portland, ME (July 29, 2009) – Today, Winxnet, Inc. announced the launching of their new online store, which sells Microsoft-certified telephones, headsets, and accessories. Winxnet now has one of the only web stores exclusively selling this optimized hardware.
This new online store, which is located at www.mscertified.com, targets organizations who have converted to the more cost effective Microsoft Unified Communications and provides them with a convenient and quick method of purchasing additional equipment. As the cornerstone of Microsoft’s Unified Communications, Office Communications Server is the platform for instant messaging, audio and video conferencing, and internet based telephone communications for businesses worldwide.
“We have seen organizations purchasing equipment which was not designed to work with this new cutting edge Microsoft communications suite,” said Chris Claudio, CEO of Winxnet, Inc. “Winxnet recognized the need in the marketplace for these users to find the right product which will work for them and their communications needs.”
As a Microsoft Gold Certified Partner and Voice Certified Partner, Winxnet is a leader in implementing Microsoft’s Unified Communications technology throughout New England and considers this new online store as the next step in providing complete service.
“As more of our own clients convert to Microsoft Unified Communications, we wanted to offer a place to easily purchase Microsoft-certified headsets, phones, conferencing equipment and accessories,” said Chris Claudio, CEO of Winxnet, Inc. “I am proud that our own e-commerce team designed and developed this site and that we have already seen sales since our beta launch.”
Winxnet has deployed Unified Communications throughout New England for organizations such as Stanley Works, Harvard Vanguard, Eastern Maine Healthcare Systems, Aetna, Boston Medical Center and Children’s Hospital Boston.
The new Winxnet online store features Microsoft-certified devices from leading communication manufacturers such as Jabra, Polycom, and Plantronics.
Winxnet, founded in 1999, was created to provide customer-focused IT consulting services to organizations and businesses throughout southern Maine and has grown its operations to include offices in Waltham, Massachusetts and Chattanooga, Tennessee, employing more than 30 people. Winxnet’s clientele consists of both publicly and privately held businesses across a variety of industries, including retail, professional services, healthcare, hospitality, energy, and technology in addition to both non-profit and governmental organizations. Cultivating partnerships with clients has been a cornerstone of Winxnet’s success and continues to be a top business priority moving forward.
Winxnet is a premier Microsoft Gold Certified Partner and is headquartered in Portland, Maine. For more information, please visit www.winxnet.com.
Microsoft has just released a new white paper for OCS 2007 R2 on Site Resiliency. This covers in detail how to architect a solution that is dispersed among two different sites and also offers complete redundancy for the OCS 2007 R2 Services.
Very Cool Read, check it out:
One of the common end user complaints during OCS Deployments is that end users have to manually add contacts to their Communicator 2007 contact list when they are first setup with Communicator. Microsoft has included a tool in the OCS 2007 and OCS 2007 R2 Resource kit for administrators to manage this functionality for individual users or entire Active Directory Containers.
This tool is very simple to use however I have not seen much documentation on it, there are a couple things you will need to gather to run this tool:
List of contacts to be added to the user or OU of users contact list
- This list must be in the form of sip:firstname.lastname@example.org with each contact separated by a line break
- You can gather this list through various methods, whether it is LDAP searches using LDP or a 3rd party tool, whatever method you prefer to gather AD user attributes and dump them to a text file. Make sure to clean up the text file so it only contains the SIP:email@example.com attribute. For reference this attribute in active directory is: msRTCSIP-PrimaryUserAddress
List of users or an Active Directory Container of the users whose contact list you wish to manage
- This must be in the form of sip:firstname.lastname@example.org or the full CN in the form of DN: OU=OUName DC=Domain,DC=(com,net,etc)
- If specifying the individual user names you can follow the same methods I mentioned above to gather the text files needed.
- The OCS 2007 R2 Resource Kit which can be found here: http://www.microsoft.com/downloads/details.aspx?FamilyID=b9bf4f71-fb0b-4de9-962f-c56b70a8aecd&DisplayLang=en
The syntax for the LCSAddContacts.WSF script is: CSCRIPT LCSAddContacts.WSF /usersfile:textfile /contactsfile:textfile /contactsgroup:group to add contacts to [/delete] can be used to remove contacts from the users list
In the below example I will be using a Users file of users.txt and a Contacts file of contacts.txt and a contacts group of Test to be added to my contact list.
This is a users file specifying an Active Directory OU of which I am the only user for testing purposes.
Contacts file with two contacts I will be adding to my group “Test”.
Once you have gathered all of this information the script is very simple to run:
As you can see I executed the script with all files located in the same directory and the output is also shown above. It will provide very clear errors if you have not entered something correctly.
Without signing out of communicator or any action on me as an end point my communicator list was updated with a new group called Test with the two new users in there:
This is a great tool and relieves a lot of end user stress on finding contacts, and also gives greater control over managing user contacts in an OCS environment.
Sometimes it is neccisary to change a user’s SIP URI, or change the SIP Domain for the entire organization in some cases. When doing this there will most likely be technical issues immediately with attempting communications.
A few key things to keep in mind when performing this change is that the address book is going to be locally downloaded to all users with the “Old” SIP URIs of all users. Because of this end users will experience trouble communicating immediately after the changes are made and until a new address book is downloaded or regenerated on the server.
To ensure a quick download of a new address book on the end user machine you can simply exit out of communicator and sign back in, if that does not work you will want to delete the communicator cache and then close and re open communicator. The communicator Cache on Vista/Windows 7 is located at C:\Users\ActiveUser\AppData\Roaming\Microsoft\Communicator. Delete the entire Communicator Folder and close and reopen communicator, you should then notice the user has updated SIP URIs of all users and can communicate.
If this doesn’t do the trick you may also have to rebuild the address book by syncing what is currently in Active Directory with the SQL Database, and rebuilding the address book files downloaded by the clients with that information.
On the OCS Server, open a command prompt and navigate to %programfiles%\Microsoft Office Communications Server 2007\Server\Core
From the command prompt run:
abserver.exe –RegenUR (Pulls data from AD and imports to SQL)
abserver.exe –SyncNow (Pulls data from SQL to create ABS files for client download)
Now after signing out and back in to communicator you should have the most up to date version of the address book with all of the correct SIP URIs for all users.
I have run into two instances recently when using DMG2000 series gateways to integrate with OCS there is a delay when making calls to the PBX/PSTN.
You call a PSTN number from Communicator, the user on the other end answers the call however your communicator does not show the call as answered. Sometimes this will answer after 5 seconds or so, other times it will not answer at all. The fix is a simple setting in the dialogic configuration.
The Dialogic gateways have a setting under TDM->T1/E1 called ISDN Answer Supervision Enable. By default this setting is “Yes”. If set to yes the gateway will wait for voice activity to answer the calls, if set to No it will only listen to ISDN Messages.
This seems to only be the fix when you are making outbound calls to the PBX or PSTN, the inbound call answer delays are another issue. There are two things I have run into relating to delays when a MOC user is answering an inbound call from the PBX.
1. Make sure the Dialogic firmware is the newest version ( needs to be at least 6.0128 for OCS 2007 R2)
As of this posting this is the latest DMG2000 firmware available on the Dialogic website.
2. Make sure the RFC 3960 Early Media Support setting under VoIP->Media is set to Always
3. Make sure Voice Activity Detection is set to Off