Monday, December 29, 2008

Planning tool for OCS 2007 R2

OCS 2007 R2 – Planning: Workbook and Tool that you can get more information on it here, is a great planning tool!

This issue below is fixed in the release:

But if you don't use the MS prefered Language setup in the OS (US-English) :)
You can get in to problems when doing a export of the setup to Visio.
To be exact when you try to open the Visio export you might get this error:

The problem is the delimiter in your language setup, in the OS, in my case it is Danish and here the delimiter is "," comma and not . dot, the quick solution for this is to do a search for "," and replace it with "." in the *.vdx file.

Sunday, December 28, 2008

OCS R2 clients against OCS R1 server

Update: Not supported

I need to have the new R2 clients running on my laptop and Mobile, so that I can use them against my R2 LAB, but the production environment is running R1.
Found this blog from Aaron describing R2 client against R1 server.
So I did some test and it seems to be working (NOT THAT I AM SAYING THAT IT’S SUPPORTED)
I got the Mobil Communicator- Communicator and Attendant Console running against my OCS R1 servers, and then I can switch between the R2 LAB and R1 productions without reinstalling clients.
Call forward setting on the Mobile Client that I have missed, is also working on the R1 server, very nice ;) (update: I can see forward settings and turn it off, but i can't set it up again from the COMO R2 or MOC R2) More information on the mobile client, get it here

Please remember I haven’t tested the clients in all functions, and it is NOT a Microsoft statement that it’s working and are supported!

Update: I won't spend more time on troubleshootting on this unsupported setup

Friday, December 26, 2008

Deploying R2 RTM in LAB

  • Update
    The setup in the old design isn't supported before Nortel will release MCM 4.0 for 64bit and x number of CS1000 5.5 patches, (release in Feb-Marts), I will instead use a gateway and a Q-SIG connection to CS1000.
    Remote Call Control will not be supported i the OCS R2 part of the lab.

  • *************************************************************************

  • Inspired by LCSKID R2 deployment information, I will post my LAB setup, I just got it up running, don’t know if it supported and I haven’t tested it fully. I can see that there is some issue in my configuration when looking at Snooper logs from my servers, when doing some call test.

  • The Nortel MCM application (32bit) running on OCS R1 proxy server is the part that I am not sure is supported in coexistent with R2. But as I see it this configuration will be real life scenarios when migrating from OCS R1 to OCS R2, you need some kind of side by side setup running.

  • I have heard some rumors about a new MCM 64bit version released when R2 is released.

In this setup I will test:

  • Remote Call Control

  • Dual forking

  • Enterprise Voice

  • Coexsitens R1 and R2 regarding to Voice

  • Exchange UM

When I know more about supported setup I will post more information.

Wednesday, December 24, 2008

OCS Contactlist application OCSCM

I found this contact tool, it look like very handy if you need to control global contactlists. I haven't tested it yet, because it OCS R2 RTM time :) building LAB right now, for as long i get permission to do it (from my home boss), you know, today it’s 24-12 :)

Get information here:

Sunday, December 21, 2008

Cisco Application Networking for Microsoft Office Communications Server Deployment Guide

Solution validation testing with Microsoft Office Communications Server 2007 and Cisco ACE and FWSM products yielded interesting insights about the details of Microsoft Office Communications Server 2007 operation and how Cisco ACE and FWSM can be configured to support Microsoft Office Communications Server 2007 Enterprise Edition in both consolidated and expanded mode deployments.

The Cisco ACE configuration required to support Office Communications Server 2007 is not complicated and can be easily deployed.
•Layer 3 Virtual IP (VIP) can be used to simplify load balancing configuration. Office Communications Server 2007 uses many different protocols to support various features of the product. The hardware load balancer configuration can be simplified by configuring the virtual IP address on the load balancer to listen on all IP ports and utilize Access Control Lists (ACLs) to restrict traffic to the VIP.
•The ACE Source Network Access Translation (SNAT) feature for server-initiated connections can be used to simplify Microsoft Office Communications Server 2007 deployments and traffic analysis. For simplicity, Microsoft recommends using source NAT for all pool traffic; however, further Cisco and Microsoft testing found it is only necessary to use source NAT for server-initiated traffic destined for VIP, thus saving resources. Cisco ACE supports this type of SNAT, which dramatically decreases the size of the NAT translation table and preserves source IP addresses of external client connections, which can be useful in troubleshooting and log file analysis.
Functional and performance testing with Cisco ACE in a Microsoft Office Communications Server 2007 consolidated deployment provides application availability and scalability:
•22,000 concurrent IM users can be supported by two dual-core Xeon-based servers with 2 GB RAM.
•Tests running a mix of instant messaging and conferencing traffic generate up to 45 Mbps of traffic.
•High availability failover scenarios have minimal impact on application operation to end users.

Get it all here:

New FIX Microsoft Office Communicator 2007 Hotfix KB 957465

Communicator 2007

and 2005 Communicator fix
Microsoft Office Communicator 2005 Hotfix KB 949280

Hope that Microsoft soon will set up some kind of service where you can subscribe to OCS update regarding FIX’ses , especially when we get so many update…………. Hmmmm could there be a solution in R2 for this, you never know, until then, I use this source

Wednesday, December 17, 2008

The OCS 2007 Automatic Sign-In Troubleshooting Tool V1.0

I found this little nice tool :)

Debugging Office Communicator 2007 automatic sign-in issues can be frustrating because of the different DNS records and their associated formats that are used to locate the home server or pool to attempt the sign-in. To simplify the debugging process, I wrote a small Windows tool that can be downloaded and run on the client.
The OCS Automatic Sign-In Troubleshooter programmatically performs DNS lookup’s for all the DNS records that the Office Communicator 2007 client uses to locate an OCS 2007 server, and displays the results. The tool performs the DNS queries as the client would (e.g. using the client DNS settings and cache), so that the results will reflect what Office Communicator will use. If people find the tool useful, I will add more functionality.
Additional Details:


Monday, December 15, 2008

Microsoft Office Communications Server 2007 Global Settings Migration Tool

Migrate OCS 2007 global settings from the System container to the Configuration container using the Microsoft Office Communications Server 2007 Global Settings Migration Tool.

You might need it for OCS R2.

New tool you can download it here:

Friday, December 12, 2008

Setting loglevel for Exchange 2007 UM

Enable Diagnostic logging on a UM Server

If you are troubleshooting an issue some logging is really usefull. On the UM server diagnostic logging is enabled by default on the lowest level. In case you need to have more logging you should manually change it to a higher level.
Changing the logging level can be done in two ways:
· via the registry editor
· via Powershell
The first method is really simple
· startup regedit
· go to HKeyLocalMachine\System\CurrentControlSet\services\MSExchange Unified Messaging\Diagnostics
· change the values from the item from which you need more logging. Valid values are: Expert 7, High 5, Medium 3, Low 1, Lowest 0
When you don’t want to change things in the registry yourself you can also do it via the Powershell, for example:
· Set-EventlogLevel “UM01\MSExchange Unified Messaging\UMService” -level
This command will change the logging level for the UMService, other valid parameters are:
· UMCore, change logging for theUMCore
· UMWorkerProcess, change logging for the UMWorkerProcess
· UMManagement, change logging for UMManagement
· UMClientAccess, change logging for UMClientAccess
· UMCallData, change logging for UMCallData
When you want to know what the current logging level is you need to execute the following Powershell command:
Get-EventlogLevel “UM01\MSExchange Unified Messaging”

Source for this:

Full detail on loging:

Microsoft’s Proposal to the SIP Forum

The purpose of a SIP Trunk as defined in this document is to enable an enterprise to connect their on‐premise voice network infrastructure to a service provider offering PSTN origination, termination, and emergency services by making use of the SIP protocol. The benefits to the enterprise customer is reduced costs in deploying voice by using an industry standard voice protocol (SIP) for PSTN access rather than deploying IP‐PSTN gateways within the enterprise network, where these gateways terminate legacy PSTN protocols such as ISDN and T1.
This specification documents the intended protocol interface between the call routing infrastructure (Enterprise Proxy) and the service provider’s network (Service Provider Proxy). It is meant as a complete specification suitable for implementation, testing, and certification of interoperability between the customer premise equipment and the service provider.

Get it all here:,com_docman/task,doc_download/gid,142/Itemid,75/

Thursday, December 4, 2008

America Online changed their root certificates on their SIP Access Gateway

If your organization leverages Public Internet Connectivity (aka: "PIC") in conjunction with their Live Communication Server 2005 and/or Office Communications Server 2007 servers, you may not be able to successfully communicate with (or see the presence status of) America Online Instant Messenger users.

look at Scott's blog:

Monday, November 24, 2008

Direct SIP to Cisco Unified Communications Manager 7.0(1) Simultaneous Ring Feature

Microsoft Office Communications Server 2007
Enterprise Edition using Direct SIP to Cisco Unified
Communications Manager 7.0(1) Simultaneous Ring

Here is the guideline how to:

I don't think that Dual forking (Simultaneous ring) is a good solution, because you don't get "in a call" status in Communicator when using the phone, only when using the Communicator as endpoint you change status to "in a call".

If you use Dual forking and Remote Call Control you will have "in a call" status even when you are using the phone. it's only Nortel that supports Dual forking and Remote Call Control right now.

If you need to understand all the different way to connect to your phone system, please look at Jochen Kunert's blog:

Here is the Supported IP-PBXs for Microsoft Office Communications Server 2007 link :

Saturday, November 15, 2008

Devices for your OCS deployment

  • I think that one of the most important factors on getting success in rolling out OCS as your primary voice plat form in the business is to choice the right device for your users.

  • First of all it must be plug and play, I don’t only mean that it should be drivers less but also it must be trimmed with the right microphone and speaker volume pr. default, by that 80-95% of your users don’t have to configure their new audio device, it’s really just plug and play.
  • And then there is the choice of type device, wired or not wired.
  • Everybody wants wireless and the “hip VIPs” people what’s just a little era plug inn.
    USB wired headset will work every time you plug it in the laptop, you can travel with it, and if you choice stereo headset it can be used music and webcast as well.
  • Stereo headset is perfect for long live meetings, the chance for interrupting sounds and noise are minimum, (yes you look like a “nerd” with that type of headset on J)
  • Wireless headsets are perfect for the user only working from their desktop, and have an everyday desk. (But remember to plug the headset in to the dock or it will run out of battery just when you need it) and the dock solution isn’t that useful when traveling.
  • The device must have a pickup button especially for heavy phone users, and if your get an incoming phone call and aren’t login. Don’t go the Skype way, your buy a low price headset and say “that’s good enough for my users” because I need to keep my investment founding low, this will never be a success and your TCO will be bad by running down that road, because your support cost will grow due to that decision.
  • Are you implementing Nortel Convergence Office with Dual forking and Remote Call Control (In Convergence Office solution it’s up to user what device that they will use, Normal phone or Communicator) A good device could be the GN 9350 this device is a “dual” device that can be used for Communicator and the “old” phone at the same time, this lower the cost and could be a way to moving your users from using the old phone “like they always do” to using Communicator as their primary “phone”. And if they should use Web conferencing with Audio, they need a good headset.
  • For users that are VERY glad for the PHONE, you know a handset you can “smack” on when you have ended a very bad phone call J you could choice the Catalina (from Nortel=IP8501 and from Polycom=CX200) this is a phone just without the number pad, and in the back it is possibly to plug some of the old headset with the RJ4 plug, my experience is that the sound in the old headset plugged in, wasn’t the best.
  • Someone was comparing Catalina and Tanjay with a B&O design,……….. hmmmm I come from B&O’s home country…….. And it’s NOT B&O design, maybe a “wannerbe” but not for real.
  • My conclusions don’t keep the investment down by choosing low end devices for your OCS deployment, and this could be the biggest investment in the OCS budget, but that’s the case in any IPT solution you choice.
  • Test a lot of devices and find 2-3 that are perfect and not to advanced and they must be “real plug and play” if you find devices that aren’t that support costly the broader range of device you can give you users to choice from without it will influence on your TCO.
  • Find devices optimized for Microsoft Office communicator here:
  • In my daily work I "OCSrun" on Nortel CS100 Rel 5.5 with GN 2000 as my traveling device and GN 9330 at my office, (yes I have two devices that because I am a OCS Nord J actually I have more but I primary use those ) btw: I love my GN 2000 it works every time and it never run out of battery .
  • I have tested a lot of the Microsoft OC ready devices Tanjay, Catalina; CX100, Roundtable unfortunately not any Plantronics devices because they didn’t exists at the OCS 2007 TAP time zone, over all devices optimized for Microsoft Office communicator are working very well when used in the right way/place.

Tuesday, November 11, 2008

OCS R2 and SIP Trunking is one way to do it.

I found this slideshow from by Russell Bennett.
I think that SIP Trunking from Service Providers could be very interesting, especially for small companies but also for Enterprises when OCS gets more and more PBX functionality (maybe OCS R2)

OCS 2007 and Windows 2008 Domain controller

Out in the real world, I was again reminded that OCS 2007 BPA can help you when you run in to problems.
I was deactivating a Mediation server but that wasn’t the biggest success I had doing that. I jumped to installing the new Mediation server, but after first step I couldn’t activate the Mediation server.
Now it was time for OCS 2007 BPA to help me, and in the report there was a hint “Windows 2008 server” but unfortunately the link to solve the problem wasn’t that helpful, so I found this solution on goog....... no I mean… I hope my Microsoft contact doesn’t read this:
The Office Communications Server 2007 can be deployed in a domain having Windows Server 2008 as a Domain Controller and its a normal deployment.

But if you already have an Office Communications Server 2007 setup running in a Windows Server 2003 forest, then you need to prepare your forest once again if you add any Windows Server 2008 Domain Controller (First time). Otherwise Office Communications Server 2007 will not work correctly; some UI elements will disappear, and you will be unable to add more Office Communication Server servers or pools. To resolve this issue, you need to prepare your forest once again for Office Communications Server 2007. You can either use Office Communications Server 2007 deployment wizard or simply reissue one command after the installation of Windows Server 2008, as follows:
LcsCmd.exe /forest /action:ForestPrep

Source for the solution:
Conclusion: use the OCS 2007 BPA if you run in to problems it might help, and yes it’s a great tool, but still room for improvement.

BTW: after the ForestPrep I could also deactivate the old Mediation server.

Friday, November 7, 2008

Remember to select the right audio device for OCS

I have over time been an advocate of buying the correct audio device for Communicator. My feeling has always been that it is very important to choose the right device, in addition to support cost if it is not plug and play.The audio experience is important, therefore, I have tried some audio devices. my farvorit audio device is GN 2000 USB, for several reasons, first of all it does not run out of power at the most inconvenient times. Then there are the sounds in both ears, and it perfectly with my laptop.

The sound device I use at the office is a GN 9330 and the sound is quite good, but those at the other end to the conversation say there is much echo. I can make it disappear by turning down the volume, but then failing to, I can't hear what is being said

So this is not an advertisement for the GN, in fact, data from our internal OCS QoE server actually said that GN 2000 USB is the winner ;)
do you have a winner ?

Microsoft Certified Master: Microsoft Office Communications Server 2007

Microsoft Certified Master: Microsoft Office Communications Server 2007

to becom Microsoft Certified Master: Microsoft Office Communications Server 2007You take the following exams:

Exam 70-638: TS: Microsoft Office Communications Server 2007, Configuring

Exam 088-924: Microsoft Office Communications Server 2007 – Unified Communication Voice Specialization (available fall 2008)

Exam 70-294: Planning, Implementing, and Maintaining a Windows Server 2003 Active Directory Infrastructure
Exam 70-640: MCTS: Windows Server 2008 Active Directory, Configuration

Exam 70-297: Designing a Windows Server 2003 Active Directory and Network Infrastructure
Exam 70-642: MCTS: Windows Server 2008 Network Infrastructure, Configuring

See Microsofts website for more information:

Thursday, November 6, 2008

Prepare for OCS R2: QFE required for interop with OC 2007 R2

Get ready for OCS R2 install the October 2008 Update for Communicator for all your existing OCS 2007 users.

see the blog-post by Tom Laciano - Sr. Program Manager

Btw: Communicator client update should be possibly from OCS R2 server, thats a very nice feature.

Wednesday, November 5, 2008

Contact with non US characters are Invisible in Communicator

If you have Outlook contacts with mail address with non US characters, then they can not be found when you do a search in Communicator.

characters like æ-ø-å Æ-Ø-Å sø

This must be a bug

Tuesday, November 4, 2008

OCS R2 platform (Paris) video from PDC2008

Here is a demo video on all the new stuff' in the OC API 2.0 ->

4 good user training videos (Demo) for Communicator

if the user is completely new in the use of Communicator is here 4 videos that explain the basic features in Communicator

Sunday, November 2, 2008

OCS R2 dial-in conference is the bussines case

I have calculated some of the savings that a company in Denmark could save by introducing OCS R2 dial-in conference.
A company with 500 employees where all hold at least 2 phone meeting each month, approximately. 30 min per meeting.
In Denmark a cheap phone meeting service is around. 1.85kr per. minutes

Per year, this company use 360,000 minutes on conference calls = 660.000kr ~100,000 euro ~ 100.000$ . If the company uses OCS R2 dial-in instead and although they all call through mobile telephone as in Denmark costs about 1kr per minute then the saving is 300,000kr ~ 50,000 euro ~50.000$.

I know this is "round" numbers, but I am quite sure that OCS R2 Dial-in can pay a big part the implementation costs of OCS R2 in many companies.

New OCS R2 videos

This video is showing the mobile client:

Note that the prensence stat dosen't change to "in a call" ....... let's hope that this is a Bug ;) .....but I think that might be a limitation because of technical dependencies on the mobile network.
On some Mobile networks you aren't able to be online and talk on the phone at the same time, thereby it's not possibly to set the prensence stat to "in a call".

This video is about the managment console.

John Weston just love OCS :) see the video "A day in the life of UC, my laptop is my phone"

John Weston demos for the Dallas Chapter of AITP(Association for IT Professionals). This time he shows them how his laptop is his phone. How UC brings together both the computer and phone networks.

Friday, October 31, 2008

security guys hate you, or maybe not after OCS R2

In OCS "R1" it's you need to get the security guys to open port 50.000 - 59.000 in the firewall.

You don't need that in OCS R2, see Jeff's blog:

Another welcome change to the A/V Edge configuration requirements is that the RTP TCP/UDP inbound port range of 50000 to 59000 is no longer required with R2, but is optionally supported. The client A/V communications can be limited to just the STUN UDP 3478 and TCP 443 ports, greatly simplifying the external firewall configuration. So if a current deployment already has the firewall configured for the previous 50000-59000 port range, then OCS R2 still supports using them, but new deployments can benefit from these changes off the bat.

Tuesday, October 28, 2008

Export GalContacts.DB to CSV RegKey

I was testing new normalizing rules in Company_Phone_Number_Normalization_Rules.txt but to be sure when the Communicator get's the right GalContact.db, I found this information.

You don't need to see GalContact.db in notepad, you can export it to CSV :)

Create the following reg key:

Dword: DumpContactsToCsvFile
Value= 1

sign out and back in again
You can find the Contacts.csv file directly from MOC, select Tools -> View Received Files.

Remeber to set DumpContactsToCsvFile back to 0 or delete it.

Monday, October 27, 2008

Gartner’s Top 10 Strategic Technologies for 2009

Unified Communications is number 5 on that list

Unified Communications. During the next five years, the number of different communications vendors with which a typical organization works with will be reduced by at least 50 percent. This change is driven by increases in the capability of application servers and the general shift of communications applications to common off-the-shelf server and operating systems. As this occurs, formerly distinct markets, each with distinct vendors, converge, resulting in massive consolidation in the communications industry. Organizations must build careful, detailed plans for when each category of communications function is replaced or converged, coupling this step with the prior completion of appropriate administrative team convergence. Unified communications can be used to streamline existing business processes improving operational efficiencies in the near term and supporting more aggressive transformational efforts longer term.

October 2008 Communicator Update

October 2008 Communicator Update
Description of the update for Communicator 2007: October 24, 2008
This update fixes the following issues:
958659 ( When you use telephony mode=4, you can only manually set the URI information in Communicator 2007
957793 ( A Communicator 2007 client is unusually slow at startup
956734 ( The presence status of Communicator 2007 changes to "Away" for all Terminal Server users when one user locks the desktop on a Windows Server 2008-based computer

get all info here

Sunday, October 26, 2008

Corp. users are ready to use Communicator as their primary phone

I have been working on “Exchange chat” LCS and OCS since 2003 and on phone integration since 2005.

In all this time I have met a lot of different people with different backgrounds, IT and IPT managers and a lot of different users.

One thing I notes is that when you talk with them about Unified Communication and in my case OCS, you meet all kind of different opinions on the matter if the company’s users are ready to use Communicator as their primary phone.

First of all you meet “Company’s / people” that are ready and just want it, then it’s just go ahead.

But you also meet IT /IPT manager that has forced their users to use some kind of soft phone from any IPT vendor, that decision is not that popular, and I understand, why take a picture of a phone and copy-paste in to the PC as software, without or minimum integrations to other software on the PC.

They aren’t ready do the same mistake one more time by giving the users a new “soft phone”, they are “Action paralyzed” and cannot/ or is scarred to take a new decision.

IT / IPT manager are also saying that there users aren’t ready for unified communication, my question is when will they be ready, if they never get the opportunity to use it in their daily work.

The decision makers are looking for a solution for their advanced phone users that normally are in some kind of front desk, saying that OCS doesn’t meet those users needs, but why is 5-10% of very heavy/advanced phone users take precedence for the last 90-95% of users.
You can combined solutions that can take care of the 5-10% and the last 90-95%.I think that OCS R2 and Response group & Attendant console and delegation will convince some of them.

There are users that aren’t ready for Communicator as their primary phone, for those users there are solutions, as an example Nortel CS1000 with features like Dual-forking and Remote Call Control, or the new “Tanjay” feature in OCS R2 where you have “RRC like” function.
By giving users this choice on what is there preferred device, they will over time experience that OCS is the right way to communicate, because communications isn’t just voice in old legacy phone.

Finally there is the Mobile phone user, living on/in their mobile phone, by forwarding all call to the Mobile number, let’s hope that OCS R2 take care of that, with the mobility and single-number reach, and also show “in a call” when using the mobile phone, because the presence information is the most important feature in any Unified Communication solution and you must have presence on any device in the company.

This is not the truth but just my opinion :)

OCS R2 Video

The press release on OCS R2

From VoiceCon:

Detailed Features

Here one on "RCC like functions" on Tanjay

This one is on Group chat like "ICQ on steroids" :)

Interview Eric Swift en demo Jamie Stark

Screen dumps from OCS R2

New Attendant Console in OCS R2

Can't wait to get my hands on the software.