Article ID: 113347, created on Feb 22, 2012, last review on Aug 12, 2014

  • Applies to:
  • Operations Automation 5.4

Symptoms

Vendors (providers, resellers) should have the ability to access specific points depending on the brand the end-user is bound to.

Resolution

This is the only way to brand meeting URLs:
1. For each brand, a provider should create a separate set of Microsoft Lync 2010 application resource types (refer to the Lync Sevrer Integration Provider's guide > Creating Lync Resource Types).
2. In each branded resource type (on the "Global Settings" subtab of the "Activation Parameters" tab on the RT dashboard), a provider should specify the branded "Meeting domain name" (refer to the POA Provider's guide > Application Hosting section).
3. Each meeting domain name should be added into certificates on FE servers, Directors, and Reverse Proxy. For more information, refer to http://technet.microsoft.com/en-us/library/gg398094.aspx and http://technet.microsoft.com/en-us/library/gg429704.aspx.
4. Each meeting domain name should be added into rules on the Reverse Proxy server (the same way as the provider's "dial-in" and "meet" domains). Refer to http://technet.microsoft.com/en-us/library/gg429712.aspx.
5. Each meeting domain name should have a DNS "A" record that points to the Reverse Proxy server. It should only be resolved externally.

The branding of meeting urls for Microsoft Lync Hosting Pack package is described here.

ac82ce33439a9c1feec4ff4f2f638899 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF