A Unified Communication Blog
Get Adobe Flash player

Update (December 2008)
After a lot of troubleshooting I have to admit that this is not going to work. See the follow-up article here: http://it-proknowledge.blogspot.com/2008/12/federation-branding.html

After some investigation, i found that even if it isn’t documented anywhere in the OCS 2007 doc kit, its is possible to brand incoming and outgoing federation connections, with a logo or icon. This works well for federations, where it is possible to show a icon next to your users name in the federated partners MOC client. Also it is possible to “brand” incoming federation traffic, with an icon that shows this contact is external from the company (this works only if the specific federation partner don’t use branding, in this case, there icon will be shown) Branding also works for public IM, so that Windows live/MSN users can see an logo next to the contact in the chat session.

It pretty basic:

All you need is to get hold of the ResKit from LCS2005, and install this package. It will install the necessary files, and you just need to follow the instructions in the readme

From the readme file:

===========================================================================

Microsoft Office Live Communications Server 2005 with SP1 SDK

Branding Sample

Copyright (C) 2005 Microsoft Corporation. All rights reserved.

===========================================================================

Sample Description
——————

Branding.am is an SPL script that demonstrates adding a branding URL to the
presence body of SIP messages. The Branding URL is added as an
tag in the presence body for all messages that contain presence documents that are
leaving the enterprise network and are destined to a partner network. The application
also allows a URL to be added to messages that are entering the enterprise network if
an tag was not inserted by the federated network. Supporting
clients can then contact this url and download the branding image for display.

A default federation branding URL may also be specified. This URL will be added
to all messages entering the enterprise from a federated network if the message
does not have one already. This feature is optional.

This sample demonstrates:

- Modifying the presence body of NOTIFY messages
- Network edge awareness

Creating and deploying icons
——————————-

Before the Branding application can be deployed, the icon itself must be
created and deployed. If the icon is to be displayed in Microsoft Office
Communicator 2005, the icon must conform to the following rules-

- File format is .png.
- File size does not exceed 8 KB.
- Icon dimensions must be 16 x 16 pixels.
- Maximum 32 bits per pixel.

This program supports deployment of two icons for federated traffic,
one for presence documents leaving the network and one for presence documents
entering the network. The external icon is the one displayed to external
users on behalf of local users. Both icons must be deployed on an external facing
Web server that allows browsers to display the image from inside and outside
the local domain by using the URLs specified in the BrandingUrl and
IncomingDefaultFederationBrandingUrl variables, respectively. Only HTTPS
(secure HTTP) URLs will work with all supported clients.

Configuration and Setup
———————–

To install and run this sample, you will need the following software:

- Microsoft® Windows Server™ 2003
- Microsoft Office Live Communications Server 2005[MC1], Access Proxy
- Microsoft Office Live Communications Server 2005 SDK

1. First, open the Branding.am script and change the BrandingUrl property [MC2]to contain
the appropriate branding image for your deployment.
2. Optionally, edit the IncomingDefaultFederationBrandingUrl property to contain the
appropriate default federation branding image for your deployment. For details, see the Remarks section
3. Click Start, click Control Panel, and then double-click Administrative Tools.
4. Double-click Computer Management. In the navigation pane, expand Services and Applications, and then click Microsoft Live Communications
Server 2005.
5. Right-click the Applications node, and then click Properties and then click add.
6. Click Browse, and then locate Branding.am.
7. In the Application Name box, type Branding.
8. In the URI box, type http://www.microsoft.com/LC/SDK/Samples/Branding
9. Click OK.
10. Start the Live Communications Server service.

Remarks
——-

By default, the branding application is configured to add the branding URL only
to outgoing messages that are bound for federated partners.

By specifying an incoming default federation branding URL, you can add a
branding URL to messages that enter the enterprise from federated [MC3]partners. This behavior
is helpful in the following scenario:

- Fabrikam[MC4].com is federated with Contoso.com.
- Contoso.com does not add a “Contoso” brand icon, so Contoso users in Fabrikam.com
will look like any other enterprise user.
- If the Fabrikam.com administrator decides that such federated users should be
distinguishable from enterprise users, he or she can choose to
supply a default federation URL that will be appended to all messages from federated partner domains.
- Fabrikam.com users will see the default federation icon if none is supplied
by the federated domain.

What you need is the LCS 2005 Resource Kit (http://www.microsoft.com/downloads/details.aspx?FamilyID=D21C38E5-5D8F-44C7-BA17-2CC4F85D8B51&displaylang=en) witch include the script (branding.am) file and the complete read me.

Have fun!

0 Responses to OCS federation branding

  • Hi Rasmus,

    Have you successfully implemented this?

    From what I can tell it definately doesn’t work out of the box. The content type response from an OCS 2007 Access Edge is in “application/rlmi+xml” format which is not supported by the branding.am script.

    The schema is also very different, and from what I can tell from the limited doco available the cwaCategory element doesn’t include any attributes for you to point a http/https url to for an icon.

    Only way I can imagine a solution is to catch all 200/Notify outbound requests on the Access Edge, and completely re-write the response in “application/pidf+xml” or “text/xml+msrtc.pidf” format??? so that the remote Communicator client processes the data as if the remote Edge server is an LCS Access Proxy?

    Karl

  • Hi Karl

    Yes, i have set it up at several sites.

    You need to put the icon on a website that has a valid SSL certificate.

    You need to set the HTTPS URL in that .am file, but thats about all the customization you need in that file.

    Please let me know if you still have problems!

  • I did put an HTTPS URL pointing to a 16×16 8 bit PNG file, but it doesn’t seem to be working. I’m still getting the default globe. I have verfied the URI and application are input properly and restarting services, the app is showing in ‘yes’ state. Does the domain that the HTTPS url comes from have to match the OCS domain in any way?

  • Hi Matt

    I have seen this issue many time before, and i dont have a complete solution yet. Officialy it is not supported, but it works sometimes.

    I havn´t figured out what is causing this (not found the time yet ;) ) but I will post it as soon as i have.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Search

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 71 other subscribers

Follow me on Twitter