• Article for your preferred language does not exist. Below is international version of the article.

Article ID: 116038, created on Apr 30, 2013, last review on Aug 12, 2014

  • Applies to:
  • Operations Automation

Symptoms

An user experiences problems with external communications in the Lync 2013 client.

Cause

External communications may be disabled for a customer Lync organization.

Resolution

Check if external communications are enabled for the Lync tenant the problem user belongs to - make sure that the Enable External Communications parameter is enabled in the POA Customer Control Panel at Microsoft Lync Hosting Pack > Configuration > Settings:

Your text to link here...

Use the Get-CsTenantFederationConfiguration PowerShell cmdlet to verify the AllowedDomains and AllowFederatedUsers parameters for the problem tenant (customer Lync organization):

PS C:\> Get-CsTenantFederationConfiguration -Tenant <TENANT_ID>
Identity              : Global
AllowedDomains        : Microsoft.Rtc.Management.WritableConfig.Settings.Edge.AllowAllKnownDomains
BlockedDomains        : {}
AllowFederatedUsers   : True
AllowPublicUsers      : True
SharedSipAddressSpace : False

Replace <TENANT_ID> with the actual Lync tenant ID, use the Knowledgebase article #116032 How to get list of users and tenant ID to get tenant ID.

The example above shows that external communications are enabled for a Lync tenant:

AllowedDomains        : Microsoft.Rtc.Management.WritableConfig.Settings.Edge.AllowAllKnownDomains
AllowFederatedUsers   : True

In case external communications are disabled you will see the following output of the Get-CsTenantFederationConfiguration cmdlet:

PS C:\> Get-CsTenantFederationConfiguration -Tenant <TENANT_ID>
Identity              : Global
AllowedDomains        : Microsoft.Rtc.Management.WritableConfig.Settings.Edge.AllowList
BlockedDomains        : {}
AllowFederatedUsers   : False
AllowPublicUsers      : True
SharedSipAddressSpace : False

PS C:\> (Get-CsTenantFederationConfiguration -Tenant <TENANT_ID>).AllowedDomains
AllowedDomain : {}

If the Enable External Communications parameter is enabled in the POA Customer CP and nevertheless the actual configuration listed by the Get-CsTenantFederationConfiguration PowerShell cmdlet does not match the Control Panel setting then consider to disable and enable back the setting in the Control Panel and make sure that generated APS tasks for the problem subscription were processed successfully.

As the last resort use the Set-CsTenantFederationConfiguration PowerShell cmdlet to change external federation settings for a particular Lync tenant. Refer to the Microsoft Technet article http://technet.microsoft.com/en-us/library/jj994080.aspx for the details on the cmdlet.

Search Words

Federation

Lync tenant

external communication

Lync 2013 client

caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF