Month: June 2014

Using Powershell 3.0 and REST to access Sonus SBC1000/2000

Summary

Since release 3.0 of Sonus SBC 1000/2000 firmware, REST license is free of charge and you can use it for multiple scenarios.

REST APIs are provided for developers who want to programmatically integrate the Sonus SBC 1000/2000 into their applications, and for administrators who want to script interactions with the Sonus SBC 1000/2000.

One of these scenarios is scripting provisioning, that allows you to program multiple SBCs with same parameters, in a one shot execution instead of having to program manually one by one each SBCs.

This is often the case when you need to deploy multiple SBCs in a same country, creating the same routing and transformation tables manually each time.

Here are some quick start tips to let you easily jump into REST programming through Microsoft Powershell.

Continue reading

Lync 2013 Databases and Replication

Summary

Databases and Replication are the dorsal spine of every Lync deployment since Lync server 2010. They allow a Lync environment to have only one configuration tools set (Topology Builder and Control Panel). They are used to share the information between the server, the pool and the sites, without them nothing can work on your Lync environment, but there isn’t a lot of information about it on the Web. Here is a dive into those processes that make Lync so efficient.

Continue reading

Office Web App Server – Le statut reste Unhealthy sous Windows 2012

Dans le cadre d’une intégration avec Lync 2013 chez un client , après quelques galères voici les point à vérifier si votre serveur/ferme OWAPP reste en statut “Unhealthy“.

D’après le blog : http://blogs.technet.com/b/dodeitte/archive/2014/01/12/how-to-get-office-web-apps-server-2013-to-report-a-healthy-health-status.aspx ce problème peut être causé par :

  • Un problème de certificat. Celui ci doit contenir dans l’attribut “SAN” les fqdn d’accès interne, d’accès externe et le nom du serveur
  • La fonctionnalité HTTP-Activation n’est pas installée (Add-WindowsFeature NET-WCF-HTTP-Activation45)

Malheureusement cela n’a pas résolu le problème et l’erreur suivante continue d’apparaître.

Source : Office Web Apps Monitoring
id : 1141

<?xml version=”1.0″ encoding=”utf-16″?>
<HealthReport xmlns:xsd=”http://www.w3.org/2001/XMLSchema” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”>
<HealthMessage>WebOneNoteWatchdog reported status for OneNoteMerge in category ‘Ping’. Reported status: OneNote Merge Ping test failed due to unhandled exception System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at net.pipe://localhost/MergeService that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. —&gt; System.IO.PipeException: The pipe endpoint ‘net.pipe://localhost/MergeService’ could not be found on your local machine.
— End of inner exception stack trace —

Ce problème est causé par la modification du chemin d’installation par défaut d’Office Web App. Malgré cette configuration, quelques fichiers sont tout de même installés dans le répertoire par défaut : C:\Program Files\Microsoft Office Web Apps\. (Microsoft nous cacherait un petit bug? 🙂 )

Pour résoudre le problème il suffit de copier / coller le sous répertoire OneNoteMerge dans le dossier d’installation personnalisé puis de relancer le service Office web App.

owapp_healthly

Update Microsoft certificate authorities to use the SHA-2 hashing algorithm

Summary

Microsoft is announcing a policy change to the Microsoft Root Certificate Program. The new policy will no longer allow root certificate authorities to issue X.509 certificates using the SHA-1 hashing algorithm for the purposes of SSL and code signing after January 1, 2016. Using the SHA-1 hashing algorithm in digital certificates could allow an attacker to spoof content, perform phishing attacks, or perform man-in-the-middle attacks.

Recommendation: Microsoft recommends that certificate authorities no longer sign newly generated certificates using the SHA-1 hashing algorithm and begin migrating to SHA-2. Microsoft also recommends that customers replace their SHA-1 certificates with SHA-2 certificates at the earliest opportunity.

Continue reading