Le Cloud de Christophe BOUCETTA

Voici le blog sur les communications unifiées et la collaboration Microsoft par un MVP nominé depuis 11 ans

Microsoft a publié une mise a jour de l'interface SDN, la derniere version est donc maintenant la 2.4.1.

Téléchargement: https://www.microsoft.com/en-us/download/confirmation.aspx?id=51195

Description des nouvelles fonctionnalités:

  • Powershell interface for provisioning: Windows Start Menu contains a Powershell shell that allows execution of provisioning commands similar to the command line provisioning interface. In addition, a SubscriberStatus and Status API has been added to allow querying some basic statistics for the overall service and each subscriber. See section on Powershell Provisioning for details.
  • Per Subscriber PII Obfuscation: You can now set an obfuscation seed for each subscriber ensuring that the feed provided contains unique identifiers representing your SIP aliases and telephone numbers. See section on Per Subscriber Obfuscation for details.
  • Schema Preview: Some new requested fields have been added to Schema D. This might break backward compatibility with some receivers and therefore requires a specific activation using a hidden schemapreview setting. These fields will be included in the next major schema revision. We have added QualityUpdate and IncallQuality messages containing Subnet, TenantId (online only) and, if traceroute is active in SfB, an attribute will give the round-trip time (RTT) for every hop. The latest provided schema definition (SDNInterface.Schema.D.xsd) allows for these new fields optionally.Note: This is NOT a supported feature but a preview for a schema change targeted in our next 3.0 release. See section on Schema Preview for details.
  • Auditing: EventLog will receive entries for changes to any SDN Manager or Dialog Listener settings as a result of provisioning activities. Eventlogs will also contain warnings 90 days before a (client) certificate being used is due to expire.
  • 0 values: In previous releases, fields containing 0 were ignored, but this release now provides fields containing 0 if 0 is a valid value and if provided by the clients. This allows better differentiation on whether a field was provided at all or not.
  • Activation of InCallQoE: Installing DialogListener on Skype for Business 2016 Server will automatically activate sending InCallQoE reports from all W16 clients. For testing and development, you can also activate InCallQoE in W16 clients if the server is an older version by adding the control files (see Configuring InCallQoE Messages). For details about how to restrict the number of InCallQoE messages, see In-call QoE algorithm and throttling.
  • Redis: This version consists of an upgraded Redis client.
  • Identifier and settings names are now case insensitive for backward compatibility.

Corrections bugs:

  • Security fix: If Redis is used with a password, the password now won’t be logged into theSDNManager logs.
  • Fixed issue when SDN Manager has schema C and schema D subscribers provisioned at the sametime.
  • Connection field "wired" will now consistently be "Ethernet".
  • Traceroute hops won’t be mirrored anymore in IncallQuality messages because the route from one endpoint is not necessarily the reverse of the other, as a given route may just be a partial route.
  • Security fix: When obfuscation is enabled (hidepii=true) in some cases PAI was not being obfuscated. This has been addressed.
  • ConferenceID field would sometimes not be populated. This has been fixed.
  • Fixed some race conditions around saving settings state that prevented settings from beingupdated correctly in an SDNManager pool.
  • Removed inconsequential errors reported in the logs.
  • Specific to SfB Online, filtering by TenantID and reporting was not handled correctly and hence wasnot being presented in InCallQoE messages. This has been addressed but needs to be enabled with the schema preview config. See section on Schema Preview for details.
  • Addressed an issue where Schema validation errors may cause messages to be dropped.
  • Schema validation has been disabled on the Dialog Listener, based on which Dialog Listener needs to be upgraded.
  • In 2.4.1 and earlier versions, the API occasionally failed to associate endpoints from a previous message to a current message. This resulted in either applying the  UserAgent and Contact headers from an incorrect endpoint or dropping the current message, whenever the expected endpoint was not found. The resulting error is ‘Writing to datastore failed after multiple retries’. This issue has been addressed in 2.4.1.
  • Addressed an issue with the Dialog Listener MSPL script, which in certain situations may affect the processing of messages on the Front End.
  • Enhanced Redis connection handling to prevent Redis connection errors specifically to lua script, added more logging and improved connectability of the SDN Managers with the Redis datastore.
  • Schema D now mentions which fields are obsolete.
  • Protocol options namely TCP-ACT and TCP-PASS are not being sent to the receiver. Only protocol option TCP will be sent for active and passive sessions

Notes et problèmes connus:

  • Support for Lync 2010 is now deprecated.
  • After installing version 2.4.1 in an active deployment, there may be some errors reported in the logs and reports lost for some calls due to a change in how QoE reports are kept in the data store. Only reports for events during the time of the upgrade may be affected.
  • InCallQoE is referred to as InCallQoS in the SfB front-end Powershell configuration, which can be misleading.
  • Due to some changes to how we store state for calls, during an upgrade, some failures may be reported for ongoing calls during the upgrade.
  • For an unattended install of SdnManager, it is required to specify the LOGPATH parameter to set the log directory.
  • For an unattended install of SdnManager, it is required to specify all the parameters including LOGPATH.
  • The AllData.log generated by the DialogListeners has some fields missing (e.g. VIA and REPLACES) hence using these logs for replay by the DialogListener is unreliable. As an alternative, use SIP logs generated by SfB or ALLManagerInput.log generated by the SDN Manager.
Facebook Like