Karsten Palmvig's blog : OCS

Troubleshoot: CWA publishSelfPresence request error

kpalmvig — Thu, 01 Oct 2009 13:52:00 GMT

If you encounter the publishSelfPresence request error (Error Code = 0-1-492) in the CWA client, you most likely have a problem with the SPN (Service Principal Name) of the CWA Service Account.

To correct this problem; open AdsiEdit and navigate to the CWA Service Account, right click and select Properties.

Scroll down to the servicePrincipalName attribute. The SPN must contain the host name that users are connecting to as well as the physical server. In many scenarios CWA is published as cwa.domain.com while the actual host name may be something like ocscwasrv01.domain.com.

Double click the servicePrincipalName attribute to edit it and make sure both names are registered like this:

http/cwa.domain.com
http/ocscwasrv01.domain.com

Note the single slash, do not type the address as “http://” – and replace host names and domain with your actual values.

How To: Connect to MSN Public IM from OCS

kpalmvig — Wed, 23 Sep 2009 10:20:12 GMT

Most customers know what boxes to check on the Access Edge Server to enable federation and Public IM Connectivity (PIC) but many ask what to do next to sign up to the service.

Signing up is quite easy, you simply need to follow this link:

https://ocspic.livemeeting.com/

Sign in using a Live ID and check the box to agree that your organization is a Microsoft Volume Licensing customer, then input the Volume License agreement number of your company and follow directions on the site.

Simple as that, when you know where to go…. :o)

How To: Telephony enabling users - continued

kpalmvig — Mon, 20 Jul 2009 19:49:55 GMT

It turned out to be significantly easier to find users without an assigned LineURI than I expected. Thanks to Nick Smith for pointing me in the right direction when answering something else. :o)

The Powershell script takes no parameters and will display the primary SIP URI for all OCS enabled users without a phone number (or LineURI). The count displayed at the end is written to the host so it won’t show in the file if you redirect.

$OCSUsers = Get-WmiObject -Query "Select * from MSFT_SIPESUserSetting where LineURI IS NULL"
$i=0
foreach ($OCSUser in $OCSUsers) {
$OCSuser.PrimaryURI
$i++
}
Write-Host $i OCS enabled users without LineURI

The output will be correctly formatted for use with OCSAssignTelUri.wsf

Happy enabling…

How To: Generate multiple phone numbers when telephony enabling users

kpalmvig — Fri, 17 Jul 2009 16:52:53 GMT

Ever needed to generate a list of 100+ phone numbers for use with e.g. OCSAssignTelUri.wsf? I have but couldn’t be bothered with inventing a new method every time anymore, so I wrote a little ps script:

param ([string] $Series, [string] $Width, [string] $Count)
if(("-?","-help","-h") -contains $args[0]) {
    Write-Host "This script will generate phone numbers based on a number series"
    Write-Host "Example: .\generatephone.ps1 -Series +1-800-555-1299 -Width 3 -Count 10"
    exit 0
}
[int]$Counter = $Series.SubString($Series.Length - $Width, $Width)
$Base = $Series.Substring(0, $Series.Length - $Width)
for ($i=1; $i -le $Count; $i++) {
    [string]$strlen = $Counter
    [string]$padding = ""
        for ($x = $strlen.Length; $x -le $Width - 1; $x++) {
            $padding = "0" + $padding
        }
    $Number = $Base + $padding + $Counter
    Write-Output $Number
    $Counter++
}

The script will take your base number series, in this case +1-800-555-1299 the width of 3 which allows the script to modify the last 3 digits and finally the count of phone numbers you need.

Needless to say, there’s no error handling, so if your width goes beyond dashes you get funny results. And if you only allow editing of 2 digits with a count of 100+ – well, you do the math… :o)

Anywho, just redirect the output to a file with the standard > operator, and Bob’s your uncle. Then you just need a file full of sip:user@domain.com, maybe a fun little project for my summer vacation to extract users without phone numbers…

Enjoy…

OCS 2007 R2 Downloads

kpalmvig — Tue, 10 Mar 2009 16:04:06 GMT

The OCS 2007 R2 binaries were recently released for public download. The table below is a compiled list of currently available R2 downloads:

Title

Microsoft Office Communications Server 2007 R2 Trial Download

Microsoft Office Communicator 2007 R2 Trial Download

Microsoft Office Communications Server 2007 R2 Attendant

Office Communicator Phone Edition (2007 R2)

Microsoft Office Communicator Mobile 2007 R2 - Pocket PC

Microsoft Office Communicator Mobile 2007 R2 - Smartphone

Microsoft Unified Communications Managed API 2.0 SDK (32 bit)

Microsoft Unified Communications Managed API 2.0 SDK (64-bit)

Microsoft Office Communications Server 2007 R2 UCMA 2.0 Speech Language Packs

Microsoft Office Communications Server 2007 R2 Group Chat server

Microsoft Office Communications Server 2007 R2 Group Chat client

Microsoft Office Communications Server 2007 R2, Group Chat Administration Tool

Conferencing Add-in for Microsoft Office Outlook

Microsoft Office Live Meeting 2007 client

Microsoft Office Communications Server 2007 R2 Group Policy Documentation

Microsoft Office Communications Server 2007 R2 SDK

OCS 2007 R2 Launched

kpalmvig — Wed, 04 Feb 2009 13:12:30 GMT

On February 3rd 2009, OCS 2007 R2 launched globally. To find more information about the launch, visit the virtual launch experience at: www.ocsr2launch.com

Future posts on my blog will be R2 related, please check back for updates…

How To: Build an OCS and UM lab with phone integration

kpalmvig — Thu, 03 Jan 2008 14:56:40 GMT

To quickly set up a lab for testing phone integration you need at least three servers for OCS and Exchange roles. One additional server is needed for Active Directory and Certificate Authority.

I would recommend using a 64-bit machine installed with Windows Server 2003 x64 and Virtual Server 2005 R2. Virtual Server can then host the Office Communication Server 2007 roles and even the Domain Controller if needed. Exchange Server 2007 will be installed on the host machine (all roles for this setup can co-exist on the same machine).

Then you need a VOIP/SIP gateway, for this documentation I'll be referring to the Audiocodes MP-114 FXO SIP Gateway but other products with same capabilities exist.

Note: The Audiocodes MP-114 product is not supported for enterprise deployment of OCS, the setup described here is only for lab use. Virtualization of OCS2007 is not supported in a production environment.

For this simple lab your existing desk phone will be handled by whatever PBX you have installed and the SIP gateway will "listen in" on a second line that the PBX has been configured to use for the same extension as your desk phone. You can also use a completely different extension for testing.

A very high level diagram of the communication flow in the lab set up will look like this:

Configuring the SIP gateway

First you need to download the OCS compatible .ini file from AudioCodes' web site - you need the "FXO (One-to-One option)" download for this setup.

Follow the quick guide available on the same page for basic setup of the MP-114. (Default IP address of the device may be 10.1.10.10 - it was in my case).

When configuring endpoint phone number, use your full phone number.

I prefer to do as little phone number manipulation as possible in the MP-114 but you need to convert the incoming phone extension into a full E.164 compliant number so it will match your phone number in OCS.

It is by far the easiest to do all your phone number normalization in OCS and just pass on the "finished" number to the MP-114, more about this in the Mediation Server section.

Just let the MP-114 route all inbound calls to your number.

As this is a test setup you may want your desk phone to ring a couple of times before your lab environment kicks in, this can be done by configuring the FXONumberOfRings under http://mp-114/AdminPage to the number of rings you want before the MP-114 reacts.

A good way to see what happens when inbound calls are made is to monitor the ports on the main page of the administration interface. Click the port (Port 3 in this case as only FXO ports should be connected to a PBX), select port settings and then SIP. This way you can see if inbound calls are translated and routed properly (fields are only populated during a call).

The MP-114 will allow you to connect an analog phone directly and use that for dialing in but it makes more sense to connect it to a PBX for testing.

Install Mediation Server

Essential reading before starting is the Enterprise Voice Planning and Deployment Guide.

I assume that you already have an OCS2007 front end server running with client connectivity so just install the Mediation Server role on a different server using the OCS2007 Deployment Wizard.

Configure listening IP address for both Communication Server and Gateway to the servers address. Leave location profile as "(None)" - we'll configure that later.

Next Hop Connections: FQDN of your front end server and IP address of the SIP gateway (MP-114 in this scenario).

Create a certificate for the the server from the same CA as you did for the front end server.

Assign a Line URI telephone number to your users in E.164 format through the OCS2007 console or ADUC; select "Enable Enterprise Voice" and input the full phone number as: "tel:+4544890100" (this is an example number, use one that fits into your numbering scheme).

Configuring Exchange UM

Under Organization Configuration\Unified Messaging:

Create a UM Dial Plan (Shell cmdlets are documented in the deployment guide so I'll show the GUI):

Give the dial plan a name and use as many digits for extension as you desire.

Add the dial plan to the UM server object under Server Configuration\Unified Messaging.

Create a new UM Auto Attendant; simply name it AutoAttendant and select the dial plan you created before. Associate an extension number with your Auto Attendant that doesn't conflict with other numbers. Make sure you enable and speech enable the Auto Attendant by checking the two checkboxes at the bottom.

Run the ExchUCUtil.ps1 script.

This will set permissions on the Exchange Org and UM containers and add the OCS front end server as IP gateway for the UM server.

Don't forget to enable users for UM... ;o)

Configure Mediation Server

Run the Exchange UM Integration Utility (found under: C:\Program Files\Microsoft Office Communications Server 2007\Server\Support\OcsUMUtil.exe on your front end server)

Press "Load Data"

If the list shows your Exchange UM dial plan, press "Add" and select phone number defined in Exchange UM under phone number and "Auto-Attendant" under Contact Type.

Press OK

The tool will say that no matching location profile exists so lets go ahead and create one now:

Right click the forest name in the OCS2007 console, select Properties; Voice Properties

Add a new profile, using the name OcsUMUtil found.

Add as many Normalization Rules to the profile as you need. This is very well documented in the deployment guide but a fast one to get you going:

Name: Local extension

Phone pattern regular expression: ^([1-9]\d{3})$

Translation pattern regular expression: +454489$1

The pattern regular expression will look for any 4 digit number starting with 1-9 and pass it on to the translation as variable $1 - the translation will prefix it with +454489 (so it conforms to E.164 numbering this way OCS can match a 4 digit local extension to the full number you have configured on your OCS/UM users).

Phone Usages and Policies are not very important for this small lab setup just assign "Default Usage" to "Default Policy".

In Routes, create a new route called "Default Route", set the Target regular expression to ".*" to let all numbers that does not match an internal user to be routed. (You can set it to "^\+45" to only allow national calls, other country codes will then fail to route).

Set the gateway address to your Mediation Server and select "Default Usage" under Phone usages.

Assign the Location Profile to the Mediation Server object in the OCS2007 console.

A very good tool to verify that your call routing is working is the Enterprise Voice Route Helper available for download in the Office Communications Server 2007 Resource Kit Tools.

Your OC client should look like this if phone integration is configured properly:

Enjoy...