Search

AnotherUCBlog > Exchange, S4B, O365

Share my findings in the Microsoft unified communication world

Category

Lync

EXCHANGE/SFB/UM – Callee voicemail language issue

Hello all,

I had an interesting behavior found by customer recently, he tolds me that when he is reaching the voicemail of one of his user (skype call), voicemail language is in English no matter the UM dialplan…

When I tried to call the user from my mobile, I got the voicemail in the right language (french in our example).

I performed multiple tests and got those results :

  • Internal Skype call -> wrong voicemail language
  • Skype call from federated partner -> right voicemail language
  • PSTN call -> right voicemail language

I compared the Skype for Business logs between internal call and federated partner call and found no difference, the same UM diapl plan was called…

Then I finally found that it was due to the caller mailbox language ! If the caller is having an Exchange mailbox in English then he will reach a voicemail in English.

So this is not an issue but it is per design !

Bye

Lync/SfB – Simultaneous ringing not working

Hi all,

New day, new challenge !

We faced an issue where users who use/used the Skype for Business mobile client were not able to get simultaneous ringing working…

Even they disconnect and uninstall the application, simultaneous ringing was no more working for their mobile device set in AD but it was working with another number.

Then I launched the lync debug tool and saw that it was trying to reach the sip address push@push.lync.com (the phone number to reach was on an iPhone)

So I tried to test the push notification with this command on the front-end server :

Test-CsMcxPushNotification -AccessEdgeFqdn EdgeServerFQDN

So I followed the article to configure push notifications : https://technet.microsoft.com/en-us/library/hh690047%28v=ocs.15%29.aspx?f=255&MSPPError=-2147217396

Then simultaneous ringing start to work again for those users who were using the mobile app.

Bye

 

LYNC/SKYPE FOR BUSINESS – Powerpoint/Whiteboard/Poll not working

Hello all,

It has been a long time since I have not write a new post but that day I got a new issue.

On a fresh new Skype for Business environment, I had an issue with the Powerpoint sharing no more working (was working some days ago…).

So I started to check all my config and check what changes I have done since it is no more working, I haven’t found something related to this issue.

So I used fiddler to check what is happening on the client side and see that the client never tried to reach the Office Web App server so I understood that the error was between the Lync/S4B client and the front-end.

Then I saw that article -> http://tomtalks.uk/2016/05/microsoft-net-security-update-ms16-065-breaks-lync-server-20102013-skype-business-server-conferencing/#comment-100590

And remember that the admin installed some updates in the last days.

So I followed the MS article -> https://support.microsoft.com/en-us/kb/3165438

In my case, the key “HKEY_LOCAL_MACHINE\Software\Microsoft\.NETFramework\v4.0.30319\System.Net.ServicePointManager.SchSendAuxRecord” wasn’t existing on my front-end so I created it and created the DWORD value. I restarted the RCTDATAMCU and after restarting my S4B client, the powerpoint sharing worked again !!!!!

I would like to thanks Tom for his help.

Bye

LYNC – External users connected to a different AD domain cannot sign in Lync

Hi all,

We faced a new issue recently with some users unable to sign-in Lync, they were stuck at the sign-in step.

Those users are connecting to Lync through our Edge servers as they are not in our local network and they are also joined to their own AD domain.

We found a temporary workaround by launching the Lync client as an administrator, then entering the user’s credentials make him able to connect successfully.

According to MS engineer, here is the explanation of this behavior :

I have analyzed logs captured so far and the problem seems that in scenario that is working (admin account) client is using already cached Lync certificate from credential manager. In non-working scenario client is not able to retrieve certificate from credential manager and fallback to NTLM. As client is connected externally, Kerberos can’t be used.

                NTLM authentication then request for credentials if already stored credential in credential manager is not up-to-date or account just doesn’t have permissions.

So now, how can we correct this issue :

You need to create the following value: HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\15.0\Lync

Name: DisableNTCredentials  Type: REGDWORD Value:1

This value will force Lync to prompt for credentials in case no valid certificate can be found.

Enjoy !

Lync – Import contacts from a user account to another one

Hey,

Usually, we need to perform an export/import of the contacts of a user for a migration purposes.

Today, someone asked me to delete a Lync account and enable a Lync Account on a new AD account and migrate the contacts from the old one to the new one.

This is something possible with the commands “Export-csUserData” and “Update-csUserData”. Don’t use the command “import-csUserData” because it will not work.

The difference between the two commands is that “import” replace while “update” just append the data (which is not a problem as the destination is new).

The process is like this :

  1. Launch the command “Export-CsUserData -PoolFQDN poolname -FileName filepath.zip -UserFilter UserSipAddress
  2. A zip is created containing the data
  3. Launch the command “Update-CsUserData -FileName filepath.zip -UserFilter UserSipAddress
  4. The contacts are now in the new Lync account

If the user also changed his SIP address, then there is an extra step where you need to edit the file called DocItem in the zip file before launching the command to update.

  1. Open the zip file created
  2. Extract the file DocItemSet.xml
  3. Open it with text editor and replace any occurence of the old SIP address with the new one then save it.
  4. Replace the file previously edited in the zip file and launch the update.

LYNC SKYPE FOR BUSINESS – EWS Not Deployed

Hello,

Having the “EWS not deployed” issue can cause those issues :

  • Unable to change your profile picture in Exchange
  • Unable to get your voicemail
  • Unable to get your conversation history
  • Unable create contacts in Exchange (unified contact store)

EWSNotDeployed

If you are having this issue, try the following things :

  • Try to get your Exchange autodiscover xml with your browser (usually something like : “https://autodiscover.SMTPdomain.com/autodiscover/autodiscover.xml”)
  • If you can get the xml content without getting an Exchange form authentication, you are good with autodiscover. If you are getting a form, change the setting in your Exchange organization or remove the pre-auth in your TMG rule (external access).
  • Try to access your Exchange web services with your browser (usually something like : “https://EXCHANGE_SERVER_HOSTNAME/EWS/Exchange.asmx”)
  • If you are getting a prompt for authentication, you are good. If you are getting a form then same thing as autodiscover, change the setting in your Exchange organization or remove the pre-auth in your TMG rule (external access).

Indeed, when starting your Lync or Skype for Business client, in order to retrieve the EWS URL it is launching an autodiscover request based on your primary SMTP address which is getting thanks to in-band provisioning process.

LYNC – OWA IM Error “Your instant message couldn’t be delivered”

Update 08/06/2015 : I found another technet page explaining that the same federation route need to be set for every pool in the organization -> https://technet.microsoft.com/en-us/library/JJ204800(v=OCS.15).aspx

technetFederation

It is also explaining that even you set up only one federation route A/V traffic will go through each respective Edge pool, only SIP, IM will go through the Edge pool set for the federation route.

Hi,

Some weeks ago, we found that our OWA(O365)-Lync(On-Prem) integration was not working completely.

Here is the status :

  • Presence -> OK
  • IM with someone in the same Lync pool -> OK
  • IM with someone in another Lync pool -> NOK

I was getting this error message :

IM OWA Error message Federation

After troubleshooting with MS, we found that the issue was the fact that we had for each front-end pool a different federation route. Each front-end pool was using it’s own Edge pool for federation and that caused the issue.

This is also wrote in the followed technet page : https://technet.microsoft.com/en-us/library/jj688121(v=ocs.15).aspx

FederationNote

Blog at WordPress.com.

Up ↑