Posts Tagged ‘Office Communications Server’

Since I lasted posted on the subject, I’ve come up with what I think are all the possibilities. You can change the users SIP ID to match their AD account name. This makes it so that: NT Account name is domainjimsmith SMTP Address is jsmith@domain.com SIP ID is jimsmith@domain.com CallManager userID is jimsmith Under this […]

The current Office Communications Server 2007 documentation doesn’t go into very much detail regarding the configuration and behavior of Phone Normalization in the Address Book Service. I won’t be going into any details regarding customization of normalization rules and how they operate, as the purpose of this blog entry is just to understand how to […]

I recently ran into a deployment problem for a customer where we attempted to use just two network interfaces for a single Edge Server configuration. If you follow the deployment documentation for the Office Communications Server 2007 Edge server, you’ll see that they require the Edge server to have up to four separate network interface […]

Between the OCS 2007 Deployment documentation, official Resource Kit, and blog/forum posts I’ve seen some discrepancies regarding the exact names (and order) of lookups performed by an Office Communicator 2.0 client when attempting to connect to an Office Communications Server when utilizing Automatic Configuration. Specifically I’ve seen reference to the automatic fall-back of looking for […]

…is not a good idea. In a production deployment a second server should be built using the desired server name, and then all OCS users moved over to it. Or a temporary staging server can be stood up in order to rebuild the original server. Either way, simply renaming an Office Communications Standard Server 2007 […]

I came across something interesting with the CUPS to OCS integration… In OCS, you have a SIP ID for each user; it’s usually best to have that match the SMTP address. So it would be something like: Jim@domain.com. That’d be the SIP and SMTP addresses. No problem there. And this can even be different from […]

UPDATED WITH NEW LINK to CISCO DOC I’ve just finished up a CUPS-to-OCS 2007 integration. We are using CUPS 6.0, Cisco CallManager 5.1, and OCS 2007 RTM. We have implemented Remote Call Control (RCC) and presence. This lets you do a few really, really, cool things: Look up any user in your corporate directory and […]

Just recently, I’ve integrated Office Communications Server 2007 and the IP-PBX PBXNSIP (http://www.pbxnsip.com). The integration went really well: I pointed the mediation server to the PBXNSIP’s IP address, configured all the OCS dial plan and voice components (normalization rules, usages, policies, routes) and very quickly was able to route calls from OCS to PBXNSIP extensions. […]

In a previous post, I had linked to a whitepaper that I found on the Microsoft site that went into some detail about Office Communications Server 2007 and Quality of Service (QoS). At the time, it was the best doc I could find out there. However, there is a newer document that goes into a […]

Briefly… If you are trying to install OCS and you would like to configure the service accounts with a password containing a " or a space: your install will fail. Kind of strange… I changed the password to not have the quote mark and it worked. Matt

Ethan M. brought an interesting point to my attention. He had scheduled a LiveMeeting though Outlook and invited an outside (non-employee) person to the LiveMeeting. When the person tried to join, they got an error message saying "you do not have permission to join the meeting". See the screencap below: Now this was strange because […]

After a bit of trial and error, and some help from PSS, we at PointBridge now have a fully function Office Communication Server 2007 environment! The implementation went quite well, with the exception of one spot: getting audio and video conferencing to work with external users. For some reason, we couldn’t have LiveMeeting 2007 bridge […]