<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="https://www.w3.org/2005/Atom" xmlns:sy="https://purl.org/rss/1.0/modules/syndication/" xmlns:dc="https://purl.org/dc/elements/1.1/" xmlns:content="https://purl.org/rss/1.0/modules/content/" xmlns:wfw="https://wellformedweb.org/CommentAPI/" xmlns:slash="https://purl.org/rss/1.0/modules/slash/"
  version="2.0">
  <channel>
    <title>Amit's Blog</title>
    <atom:link
      href="https://docs.microsoft.com/archive/blogs/amitanand/feed.xml"
      rel="self"
      type="application/rss+xml" />
    <link>https://docs.microsoft.com/archive/blogs/amitanand/feed.xml</link>
    <description>Just another Technet site</description>
    <lastBuildDate>Wed, 17 Apr 2019 03:28:55 GMT</lastBuildDate>
    <language>en-US</language>
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <item>
      <title>Skype Room System dropping from meeting with in 1-2 seconds.</title>
      <link>https://docs.microsoft.com/archive/blogs/amitanand/skype-room-system-dropping-from-meeting-with-1-2-seconds</link>
      <pubDate>Sun, 04 Mar 2018 02:13:19 GMT</pubDate>
      <dc:creator><![CDATA[Amit_An]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.technet.microsoft.com/amitanand/?p=195</guid>
      <description><![CDATA[Recently worked on multiple occurrence of an issue with SRS V2. Where SRS joins a meeting for few...]]></description>
      <content:encoded><![CDATA[Recently worked on multiple occurrence of an issue with SRS V2. Where SRS joins a meeting for few seconds usually 1-2 seconds and then abruptly disconnects.

Generally it keeps on happening until device is rebooted but this is not seen to be done in all instances. Some times meeting join works with a reattempt.

If you are facing this issue would suggest to take logs from a Device. To take logs you may need to run Powershell Scripts as defined in below link.

https://technet.microsoft.com/en-us/library/mt790549.aspx

And in UCC API logs of SRS, file name usually would be like SkypeRoom-Lync-0. Filter out session for failed attempt and if you see that BYE message is sent out by SRS with in few seconds after receiving 2ooOK .

&nbsp;

<img width="295" height="307" class="alignnone size-full wp-image-205" alt="" src="https://msdnshared.blob.core.windows.net/media/2018/03/Capture.jpg" />

&nbsp;

And Diagnostic message in BYE is printed as

&nbsp;

reason="Media session terminated on internal client error"

With ICE warning as ICEWarn=0x40400a or ICEWarn=0x404000

You could also fetch these details from monitoring reports as well.

It may be related to same issue where SRS application is actually becoming victim instead of causing issue. I observed form additional logs analysis that apparently it seems like SRS is failing while getting hold of network interface. And thus disconnects the call due to internal client error.

If you are observing same issue i would suggest to update OS on SRS surface device. In multiple cases where similar issue is observed updating Windows on Surface which in my case installed following KBs. Helped and resolved the issue.

<span style="color: #b00000;font-family: Calibri">KB4023057</span>

<span style="color: #b00000;font-family: Calibri"><span style="color: #b00000"></span>KB4056887</span>

<span style="color: #b00000;font-family: Calibri"><span style="color: #b00000"></span>KB4056891</span>

<span style="color: #b00000;font-family: Calibri"><span style="color: #b00000"></span>KB4033631</span>

<span style="color: #b00000;font-family: Calibri"><span style="color: #b00000"></span>KB4053580</span>

<span style="color: #b00000;font-family: Calibri"><span style="color: #b00000"></span>KB4053577</span>

<span style="color: #b00000;font-family: Calibri"><span style="color: #b00000"></span>KB4049011</span>

<span style="color: #b00000;font-family: Calibri"><span style="color: #b00000"></span>KB890830</span>

You may need to open a ticket with Microsoft if even after updating OS you still face this issue.

&nbsp;]]></content:encoded>
    </item>
    <item>
      <title>LPE Devices signing out and getting stuck on sign in</title>
      <link>https://docs.microsoft.com/archive/blogs/amitanand/lpe-devices-signing-out-and-getting-stuck-on-sign-in</link>
      <pubDate>Sat, 17 Feb 2018 19:12:25 GMT</pubDate>
      <dc:creator><![CDATA[Amit_An]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.technet.microsoft.com/amitanand/?p=175</guid>
      <description><![CDATA[If you are seeing a sporadic issue with Polycom LPE ( Lync Phone Edition ) Devices. Where user signs...]]></description>
      <content:encoded><![CDATA[If you are seeing a sporadic issue with Polycom LPE ( Lync Phone Edition ) Devices. Where user signs out abruptly and getting stuck on sign in. And could not sign in back unless phone reset is done.

In that case when issue happens try to look at the logs what is the response phone is getting form server side. If Registration is failing with following response.

ms-diagnostics: 4172;reason="No cert found for the user"

It shows that server is not able to find certificate used by client in TLS-DSK method. As now a days users sign in form multiple devices most probably cause is that user reached max number of devices cert could be issued and cert which was issues for phone got deleted as a new device may have requested cert from server for this user.

This issue is limited to Polycom LPE devices as they could do only TLS/DSK based authentication. Other clients type could move to NTLM or Kerberos but that could not happen with LPE devices.

&nbsp;

So that's about issue but the solution is fairly simple, it may need to increase Max endpoints per user on server side.

&nbsp;

<img width="1024" height="354" class="alignnone size-large wp-image-185" alt="" src="https://msdnshared.blob.core.windows.net/media/2018/02/Capture2-1024x354.jpg" />

Max value of MaxEndpointPerUser could go to 64. It's usually not recommended to increase this value without any necessity.

<a href="https://docs.microsoft.com/en-us/powershell/module/skype/set-csregistrarconfiguration?view=skype-ps">https://docs.microsoft.com/en-us/powershell/module/skype/set-csregistrarconfiguration?view=skype-ps</a>

<span style="float: none;background-color: transparent;color: #333333;cursor: text;font-family: Georgia,'Times New Roman','Bitstream Charter',Times,serif;font-size: 16px;font-style: normal;font-variant: normal;font-weight: 400;letter-spacing: normal;line-height: 24px;text-align: left;text-decoration: none;text-indent: 0px">You could gradually increase this value in chunks instead of straight setting to 64 and see if that reduce frequency of issue or take it away. </span>

&nbsp;

&nbsp;

&nbsp;

&nbsp;

&nbsp;]]></content:encoded>
    </item>
    <item>
      <title>Push notifications attempts even though disabled in PushNotificationConfiguration</title>
      <link>https://docs.microsoft.com/archive/blogs/amitanand/push-notifications-attempts-even-though-disabled-in-pushnotificationconfiguration</link>
      <pubDate>Sat, 17 Feb 2018 06:16:14 GMT</pubDate>
      <dc:creator><![CDATA[Amit_An]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.technet.microsoft.com/amitanand/?p=75</guid>
      <description><![CDATA[Looks like in CU4 of SFB 2015 new settings are introduced with platform wide scope. You can see...]]></description>
      <content:encoded><![CDATA[Looks like in CU4 of SFB 2015 new settings are introduced with platform wide scope. You can see these through command.

Get-CsPlatformServiceSettings

<img width="530" height="173" class="alignnone wp-image-145" alt="" src="https://msdnshared.blob.core.windows.net/media/2018/02/Capture-300x98.jpg" />

It also has a parameter for Push notifications.

&nbsp;

If you are observing that client is registering to Push notification services even though you have disabled Push notifications in PushNotificationConfiguration.

&nbsp;

<img width="783" height="107" class="alignnone wp-image-155" alt="" src="https://msdnshared.blob.core.windows.net/media/2018/02/Capture1-300x41.jpg" />

&nbsp;

On the Client side you may see below in logs,

&nbsp;

<span style="margin: 0px;font-family: 'Courier New'"><span style="color: #000000">2018-01-04 18:41:36.332 00000001b6493b80 INFO UI SFBApnsPushNotificationsManager.m:52 VoIP APNS push registration initiated.^M</span></span>

<span style="margin: 0px;font-family: 'Courier New'"><span style="color: #000000">2018-01-04 18:41:36.757 00000001b6493b80 INFO UI SFBApnsPushNotificationsManager.m:62 VoIP push registration succeeded.</span></span>

It seems like settings in Platform level triggers and act as global settings as well. Which cause clients to see Pushnotification is enabled.

<span style="margin: 0px;font-family: 'Courier New'"><span style="color: #000000">pushNotificationEnabled(1)</span></span>

&nbsp;

Incase you want to disable Push Notifications it needs to be disabled at Platform level using command.

&nbsp;

<span style="margin: 0px;font-family: 'Courier New'"><span style="color: #000000">Set-CsPlatformServiceSettings -EnablePushNotifications $False</span></span>]]></content:encoded>
    </item>
    <item>
      <title>Hello world!</title>
      <link>https://docs.microsoft.com/archive/blogs/amitanand/hello-world</link>
      <pubDate>Fri, 12 Jan 2018 16:24:02 GMT</pubDate>
      <dc:creator><![CDATA[Amit_An]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.technet.microsoft.com/amitanand/?p=1</guid>
      <description><![CDATA[Welcome to Technet. This is your first post. Edit or delete it, then start blogging!]]></description>
      <content:encoded><![CDATA[Welcome to <a href="https://blogs.technet.microsoft.com/">Technet</a>. This is your first post. Edit or delete it, then start blogging!]]></content:encoded>
    </item>
  </channel>
</rss>