Ya no es sorpresa para nosotros esta noticia, pero si fue grato ver la demo que se realizo el dia de hoy en el MS Ignite de Microsoft Teams.
Como bien sabemos Microsoft Teams, desde ahora sera el cliente core para Comunicaciones en Office 365, quedando Skype for Business solamente para soluciones Onprem.
Pero, que de bueno le vemos a esta nueva solucion?, que Microsoft lleva con bandera de “Inteligent Communications” (y realmente estoy de acuerdo)
Por si solo y antes de integrarle cualquier capacidad de PSTN a Teams, era un producto muy completo.
Chat Persistente
Crear Teams
Crear canales
Wiki
File
Storage Services
Creacion de diferentes Tabs
Bots
etc…
En la demo que se vio hoy en el ignite, se mostro la capacidad de hacer (y por descuido, recibir) llamadas hacia la PSTN. Con esto, y con la liberacion de PSTN Conferencing en Public Preview el pasado viernes, Microsoft Teams queda completo para ser el sustituto ideal para Skype for Business.
Pues hoy nos encontramos con esta triste realidad. Si ustedes intentan ingresar al servicio de Skype for Business desde Office 365 se encontraran con 2 opciones.
1) les manda mensaje de error y no podran iniciar sesion.
2) Manda el siguiente mensaje.
Si, leyeron bien. Skype for Business ahora es Microsoft Teams.
Mucho se ha hablado y especulado sobre Microsoft Teams reemplazando por completo a Skype for Business como solucion de UC de Microsoft. Pero el dia de hoy no vamos a hacer otro post acerca de eso.
Hoy vamos a preguntarnos, que es lo que Microsoft Teams nos ofrece? Esta realmente pensado para cambiar las comunicaciones unificadas al dia de hoy, o fue Microsoft el que tuvo que cambiar para adaptarse a las necesidades de una nueva generacion?
Dentro del Webcast donde tuve el gusto de compartir con Geo Acevedo, nos mencionaron que Teams estaba diseñado para los milenials, y me parece que tiene algo de razon. Pero no tanto a los milenials en particular, sino que a la nueva generacion.
Asi es como ha estado evolucionando la tecnologia, lo podemos ver en algo tan sencillo como en la forma que escuchamos la musica, de vinilos a cassettes, de cassettes a CD, de CD a iPod etc… (entendieron el punto)
Lo mismo pasa con las comunicaciones, ya pasamos el cambio de analogico a digitil, de el telefono de casa a un celular. Sean honestos cuantos de nosotros seguimos utilizando el telefono de casa? Una llamada a celular, un whatsapp, videollamada, de hecho creo que los SMS tambien estan quedando atras…
Entonces si vemos desde ese punto de vista que Microsoft ha estado tratando de adaptarse a un mundo PBX existente, desde las versiones previas a SfB (LCS, OCS , Lync , SFB) y ha estado dando batalla a grandes competidores (todos old school), no es de sorprendernos que en algun punto esta forma de comunicacion quede obsoleta y le de paso a la nueva generacion.
Microsoft Teams, (y todos sus productos similares) ha llegado para dar ese giro a la forma de colaboracion. La comunicacion offline esta pasando a ser olvidada (perdon amantes de los correos) y la necesidad de que toda comunicacion sea en tiempo real, y ademas que se tengan mas herramientas al alcance de un simple click dentro de la misma aplicacion, hace de Microsoft Teams la solucion ideal para las empresas.
Tambien estan de acuerdo que los nuevos egresados vienen de un mundo donde las redes sociales son la forma predilecta de comunicacion, haciendo de Microsoft Teams un aliado por su interfaz y funcionalidades bastantes similares (cuando ibas a pensar agregar un Meme en SfB?) a una red social. Y aunque parezca de risa, estos detalles hacen mas facil su adopcion para las nuevas generacion y tambien para los amantes de las redes sociales.
“Te mando whats”, “Marcame por facetime”, “lo publique en face” cuantas veces en el dia no escuchamos estas frases? porque deberia de ser diferente en la empresa? Asi que en la opinion de un servidor, escucharemos en el futuro frases como “Te lo mande por Teams”, “Esta publicado en el Channel”, “Te agrego al grupo de Teams”, lo cual no suena tan descabellado.
Para los que no lo han probado aun, denle una oportunidad. Puede que cambie la opinion que tienen al respecto tal y como me paso a mi. En UC desde la version de OCS 2007 y ahora me sentia algo reservado en cuanto a probar Teams, pero me lleve una muy grata sorpresa.
Saludos.
——- ENGLISH —————
Is Microsoft Teams the Future for UC?
In past days most of us heard about Microsoft Teams, if will replace Skype for Business if MS will merge on one client, today I wont write another post about it.
Today, let’s ask us what does MS Teams offer? Was done to change today’s UC or Microsoft was the one whom change in order to adapt to new generation requirements?
On the webcast that I share mic with Geo Acevedo, a participant told us that MS Teams was designed for Millenial Generation. To be has a good point, but I belive that is for new business generation instead just Millenials.
There’s how technology evolves. We could see on something as simple as the way we listen music, from Vinils to Cassettes, from Cassettes to CDs, from CDs to iPod, etc….
The same for communications, we already have a change from analogic to digital, from home phone to cellphone. You should to be honest, who still use the home phone? Cellphone calls, whatapps, videocall, in fact I bet that SMS is still a step behind.
So if we look on that point of view, Microsoft was trying to adapt on an existing PBX world, from previous versions to SfB (LCS,OCS,Lync) y had been side-by-side with big PBX companies (all old school) so is not too surprising on one point this way to communicate will be obsolete and will leave the way free to a new generation to communicate.
Microsoft Teams, (and other brands similar products) has come to give this change to the way to collaborate. offline communication is not too far to be obsolete (sorry to email lovers) and we have the need that all communication should be on real time and if you add more features on the same app on just one click of distance much better…, all of this makes Microsoft Teams the ideal solutions for enterprise communications.
Also, you should agree that the new graduates comes from a world where social networks are the preferred way of communication, making Microsoft Teams an ally because its interface and features which are very similiar (when did you think to add a Meme on Sfb?) to a social network. And maybe sounds like a joke but all these details make easier to adopt for new generations and for social network geeks.
“Send me on whatsapp”, “Call me on facetime”, “ I post it on facebook” how many times on a day did you listen all these? why should be different on the company? so on my own opinion , we’ll listen phrases like “Send me on Teams”, “Is posted on the Channel”, “I’ll add you on Team’s group”
El dia de hoy les traigo los cambios que vienen para las actualizaciones para Office 365 ProPlus, tal y como fue anunciado el 20 de Abril de este año (para ver el post aqui)
Entre los mayores cambios estan los siguientes
Dos actualizaciones al año. Con el esquema semi-anual Microsoft reduce de tres actualizaciones al año, a solo dos. Planeadas para Marzo y Septiembre.
18 meses de soporte. Microsoft extendera el periodo de soporte para Office 365 ProPlus de 12 a 18 messes (comenzando en septiembre, con el siguiente release), asi que se podra elegir actualizar una o dos veces por año sin perder soporte.
Tambien, han sido cambiados los nombres de los update channels, haciendolos mas descriptivos.
Todos estos cambios tendran efecto en SEPTIEMBRE 2017
La liberacion por defecto para Office 365 ProPlus cambia a dos veces por año.
Actualmente , Office 365 ProPlus obtiene las actualizaciones para el First Release for Deferred Channnel en Febrero, Junio y Octubre. Y estan disponibles cuatro meses despues para Deferred Channel.
A partir de los cambios de Septiembre, obtendra las actualizaciones para Semi-annual Channel (Targeted) dos veces al año, Marzo y Septiembre. Y para el Semi-annual Channel, cuatro meses despues, en Julio y Enero.
Office 365 ProPlis, continuara recibiendo actualizaciones de seguridad y calidad mensualmente, para estos update channel on el segundo martes de cada mes.
Aqui una descripcion grafica de como es que quedaran las actualizaciones.
Proximas actualizaciones para Office 365 ProPlus
Date
First Release for Deferred Channel
Semi-annual Channel (Targeted)
Deferred Channel
Semi-annual Channel
IT Pro action to take
June 13, 2017
New features are released to First Release for Deferred
Channel.
Enterprise pilots and application validation should
begin.
This is the last release using the name “First Release
for Deferred Channel.”
The next release with new features is scheduled for
September 12, 2017.
Important:You only have 3 months, instead of 4
months, to do enterprise pilots and application validation, since the next
release is scheduled for September, so plan
accordingly.
New features are released to Deferred
Channel.
This version of Deferred Channel is supported until
January 2018.
The next release with new features is scheduled for
September 12, 2017.
Important:The next release with new features
is only 3 months away, instead of 4 months, so plan
accordingly.
Continue to deploy these update channels in your
environment as you have been doing previously.
For enterprise pilots, validate your line-of-business
applications, add-ins, and macros with First Release for Deferred
Channel.
If you find problems with First Release for Deferred
Channel, provide feedback as soon as possible to Microsoft through
yourMicrosoft Premieragreement or your
Microsoft account representative.
July 11, 2017
August 8, 2017
If needed, quality updates and security updates are
released to First Release for Deferred Channel.
This is the regular update schedule for this update
channel.
If needed, quality updates and security updates are
released to Deferred Channel.
This is the regular update schedule for this update
channel.
Continue to update these update channels in your
environment as you have been doing previously.
Continue to do enterprise pilots and application
validation with First Release for Deferred Channel, and provide feedback to
Microsoft, as needed.
September 12, 2017
The first Semi-annual Channel (Targeted) is
released.
This release contains new features.
Enterprise pilots and application validation should
begin.
This is the first release with the new name and the new
release schedule.
The next release with new features is scheduled for
March 13, 2018.
New features are released to Deferred
Channel.
This version of Deferred Channel is supported until
July 2018.
This is the last release using the name “Deferred
Channel.”
The next release with new features is scheduled for
January 9, 2018.
Continue to deploy these update channels in your
environment as you have been doing previously. Even though the names and cadence
are changing, how you deploy remains the same.
For enterprise pilots, validate your line-of-business
applications, add-ins, and macros with Semi-annual Channel
(Targeted).
If you find problems with Semi-annual Channel
(Targeted), provide feedback as soon as possible to Microsoft through
yourMicrosoft Premieragreement or your
Microsoft account representative.
Be sure to be aware of the new release schedule. There
is no longer a release in October for Deferred Channel or for First Release for
Deferred Channel.
January 9, 2018
The first Semi-annual Channel is
released.
This release contains new features.
This version of Semi-annual Channel is supported until
March 2019.
This is the first release with the new name, new
release schedule, and the new support duration.
The next release with new features is scheduled for
July 10, 2018.
Continue to deploy this update channel in your
environment as you have been doing previously. Even though the name and cadence
has changed, how you deploy remains the same.
Be sure to be aware of the new release schedule. There
is no longer a release in February or June for Deferred Channel or for First
Release for Deferred Channel.
March 13, 2018
New features are released to Semi-annual Channel
(Targeted).
Enterprise pilots and application validation should
begin.
The next release with new features is scheduled for
September 11, 2018.
Continue to deploy this update channel in your
environment as you have been doing previously. Even though the name and cadence
has changed, how you deploy remains the same.
For enterprise pilots, validate your line-of-business
applications, add-ins, and macros with Semi-annual Channel
(Targeted).
If you find problems with Semi-annual Channel
(Targeted), provide feedback as soon as possible to Microsoft through
yourMicrosoft Premieragreement or your
Microsoft account representative.
July 10, 2018
New features are released to Semi-annual
Channel.
This version of Semi-annual Channel is supported until
September 2019.
The next release with new features is scheduled for
January 8, 2019.
Continue to deploy this update channel in your
environment as you have been doing previously. Even though the name and cadence
has changed, how you deploy remains the same.
September 11, 2018
New features are released to Semi-annual Channel
(Targeted).
Enterprise pilots and application validation should
begin.
The next release with new features is scheduled for
March 12, 2019.
Continue to deploy this update channel in your
environment as you have been doing previously. Even though the name and cadence
has changed, how you deploy remains the same.
For enterprise pilots, validate your line-of-business
applications, add-ins, and macros with Semi-annual Channel
(Targeted).
If you find problems with Semi-annual Channel
(Targeted), provide feedback as soon as possible to Microsoft through
yourMicrosoft Premier agreement or your
Microsoft account representative.
Espero les sea de ayuda.
—————–
ENGLISH
—————–
Hey,
Today I bring to you some coming changes to update channels for Office 365 ProPlus, as was announced on April, 20th (you can find more info here)
Major changes are.
Two updates a year. Microsoft will reduce the number from three updates per year to only two , planned on March and September.
18 months of support. Microsoft will extend support from 12 months to 18 months for Office 365 ProPlus,(starting on next release), IT admin can choose to update once or twice a year.
Update Channel names will change
All this changes will apply on SEPTEMBER 2017
The default enterprise release schedule for Office 365 ProPlus is changing to twice a year
Currently, Office 365 ProPlus gets feature updates in First Release for Deferred Channel in February, June, and October. Those feature updates are then available in Deferred Channel four months later.
Starting in September 2017, Office 365 ProPlus will get feature updates in Semi-annual Channel (Targeted) twice a year, in March and September. Those feature updates will then be available in Semi-annual Channel four months later, in July and January.
Office 365 ProPlus will continue to receive security updates and quality updates monthly, as needed, for these update channels on the second Tuesday of each month. There are no changes to the Office 365 ProPlus release schedule for Monthly Channel.
Upcoming schedule for Office 365 ProPlus releases
Date
First Release for Deferred Channel
Semi-annual Channel (Targeted)
Deferred Channel
Semi-annual Channel
IT Pro action to take
June 13, 2017
New features are released to First Release for Deferred Channel.
Enterprise pilots and application validation should begin.
This is the last release using the name “First Release for Deferred Channel.”
The next release with new features is scheduled for September 12, 2017.
Important:You only have 3 months, instead of 4 months, to do enterprise pilots and application validation, since the next release is scheduled for September, so plan accordingly.
New features are released to Deferred Channel.
This version of Deferred Channel is supported until January 2018.
The next release with new features is scheduled for September 12, 2017.
Important:The next release with new features is only 3 months away, instead of 4 months, so plan accordingly.
Continue to deploy these update channels in your environment as you have been doing previously.
For enterprise pilots, validate your line-of-business applications, add-ins, and macros with First Release for Deferred Channel.
If you find problems with First Release for Deferred Channel, provide feedback as soon as possible to Microsoft through yourMicrosoft Premieragreement or your Microsoft account representative.
July 11, 2017
August 8, 2017
If needed, quality updates and security updates are released to First Release for Deferred Channel.
This is the regular update schedule for this update channel.
If needed, quality updates and security updates are released to Deferred Channel.
This is the regular update schedule for this update channel.
Continue to update these update channels in your environment as you have been doing previously.
Continue to do enterprise pilots and application validation with First Release for Deferred Channel, and provide feedback to Microsoft, as needed.
September 12, 2017
The first Semi-annual Channel (Targeted) is released.
This release contains new features.
Enterprise pilots and application validation should begin.
This is the first release with the new name and the new release schedule.
The next release with new features is scheduled for March 13, 2018.
New features are released to Deferred Channel.
This version of Deferred Channel is supported until July 2018.
This is the last release using the name “Deferred Channel.”
The next release with new features is scheduled for January 9, 2018.
Continue to deploy these update channels in your environment as you have been doing previously. Even though the names and cadence are changing, how you deploy remains the same.
For enterprise pilots, validate your line-of-business applications, add-ins, and macros with Semi-annual Channel (Targeted).
If you find problems with Semi-annual Channel (Targeted), provide feedback as soon as possible to Microsoft through yourMicrosoft Premieragreement or your Microsoft account representative.
Be sure to be aware of the new release schedule. There is no longer a release in October for Deferred Channel or for First Release for Deferred Channel.
January 9, 2018
The first Semi-annual Channel is released.
This release contains new features.
This version of Semi-annual Channel is supported until March 2019.
This is the first release with the new name, new release schedule, and the new support duration.
The next release with new features is scheduled for July 10, 2018.
Continue to deploy this update channel in your environment as you have been doing previously. Even though the name and cadence has changed, how you deploy remains the same.
Be sure to be aware of the new release schedule. There is no longer a release in February or June for Deferred Channel or for First Release for Deferred Channel.
March 13, 2018
New features are released to Semi-annual Channel (Targeted).
Enterprise pilots and application validation should begin.
The next release with new features is scheduled for September 11, 2018.
Continue to deploy this update channel in your environment as you have been doing previously. Even though the name and cadence has changed, how you deploy remains the same.
For enterprise pilots, validate your line-of-business applications, add-ins, and macros with Semi-annual Channel (Targeted).
If you find problems with Semi-annual Channel (Targeted), provide feedback as soon as possible to Microsoft through yourMicrosoft Premieragreement or your Microsoft account representative.
July 10, 2018
New features are released to Semi-annual Channel.
This version of Semi-annual Channel is supported until September 2019.
The next release with new features is scheduled for January 8, 2019.
Continue to deploy this update channel in your environment as you have been doing previously. Even though the name and cadence has changed, how you deploy remains the same.
September 11, 2018
New features are released to Semi-annual Channel (Targeted).
Enterprise pilots and application validation should begin.
The next release with new features is scheduled for March 12, 2019.
Continue to deploy this update channel in your environment as you have been doing previously. Even though the name and cadence has changed, how you deploy remains the same.
For enterprise pilots, validate your line-of-business applications, add-ins, and macros with Semi-annual Channel (Targeted).
If you find problems with Semi-annual Channel (Targeted), provide feedback as soon as possible to Microsoft through yourMicrosoft Premier agreement or your Microsoft account representative.
Una vez que nos registramos recibiremos un correo con las instrucciones para poder conectarnos, tanto usando el cliente de Skype for Business, como otras opciones. ( para este demo me conectare desde un Chrome en Windows, Mozilla en Ubuntu y mi celular Android)
Veremos la presencia en el cliente, y le damos clic en llamar..
Con esto ya estamos conectados con Pexip, por medio de audio, podemos incluir video, chat y screensharing.
Ahora vamos a agregar los otros endpoints.
para unirnos por medio de browser debemos escribir la siguiente direccion
pexipdemo.com/<usuario.dominio>
Nos pedira poner nuestro nombre
Para distinguir los diferentes endpoint , le pondre Web Client Windows
y le damos en conectar. Y asi de sencillo ya estamos conectados con nuestro browser, pexip y skype for business.
Hacemos lo mismo con los otros dispositivos.
Linux
Android Client
Podemos iniciar video y todos los dispositivos deberan de ser capaces de hacerlo. (Linux lo tengo en Hyper V, asi que con el no podre compartir video, pero podra ver el de los demas)
Pexip web browser Video and sharing screen
Skype for Business
Android
Como veran es bastante sencillo y funciona bastante bien.
Espero les sirva.
Saludos.
—— ENGLISH———
Hey,
Today we will try a demo from the new videosolution certified to Skype for Business. I’m talking about Pexip Inifity.
Once you register, you’ll receive an email with intructions to login, using Skype for Business client, as well as other options (for this demo I’ll login with Chrome on Windows PC, Mozilla on Ubuntu, and my Android mobile phone)
To connect with Pexip from Skype for Business client, I need to call the user on the following format <user.domain@pexipdemo.com> if you select to use a PIN, you need to dial as follow <user.domain**123123123@pexipdemo.com> just replace the number with your current PIN number
You will be able to see the presence status, now you only need to click call button.
Now, you’re connected with Pexip infinity VideoConferencing, now you can add audio, video, IM and Sharing.
Let’s add other endpoint
To join from a web browser using webrtc, you need to do as follow.
pexipdemo.com/<user.domain>
Will ask for your name
In order to differentiate endpoint I will call it Web Client Windows and click on Connect.
Easy, does it? now we are connected via Browser, to Pexip and Skype for Business.
Let’s do the same on the other clients.
Linux
Android Client
Now let’s share video and screen.. (I could’t do it on Linux because I don’t have enough devices sorry.)
Hoy les traigo un pequeno proyecto donde podran traducir los mensajes instantaneos, usando los servicios de Azure Cognitive services como servicio de traduccion. y conectarse usando powershell y en SDK de Lync.
En esta etapa temprana, este script solamente envia IM, pero no puede traducir mensajes entrantes. Puedes instalar el script en ambos puntos como workaround.
Vamos a comenzar!
Primero, necesitas crear un servicio en tu portal de Azure, (si necesitas una subcripcion de Azure)
Ve a Cognitive Service, y selecciona Translator Text API
Crea un nuevo servicio y selecciona la opcion gratuita, te permitira traducir hasta 2Millones de caracteres sin ningun costo
Una vez creado, por favor copia las llaves de acceso, ya que las necesitaras mas adelante en el script.
Sencillo, no lo creen?
Ahora vamos a crear y configurar nuestro script.
La siguiente es la funcion de Translate, la principal del script. Aqui solo necesitas reemplazar el accountKey con el de tu servicio para que comience a funcionar.
$ret = Invoke-RestMethod -Uri $uri -Method Get -Headers $header
$ret.OuterXml
$message= $ret.string.’#text’
if (-not (Get-Module -Name Microsoft.Lync.Model))
{
try
{
# you may need to change the location of this DLL
Import-Module «C:\Program Files (x86)\Microsoft Office 2013\LyncSDK\Assemblies\Desktop\Microsoft.Lync.Model.dll» -ErrorAction Stop
}
catch
{
Write-Warning «Microsoft.Lync.Model not available, download and install the Lync 2013 SDK http://www.microsoft.com/en-us/download/details.aspx?id=36824″
}
}
# Connect to the local Skype process
try
{
$client = [Microsoft.Lync.Model.LyncClient]::GetClient()
}
catch
{
Write-Host «nMust be signed-in to Skype"
break
}
# Add the contact URI
try
{
$contact = $client.ContactManager.GetContactByUri($target)
}
catch
{
Write-Host "nFailed to lookup Contact»$target
break
}
# Create a conversation
$convo = $client.ConversationManager.AddConversation()
$convo.AddParticipant($contact) | Out-Null
# Set the message mode as IM
$imModality = $convo.Modalities[1]
# Send the message
$imModality.BeginSendMessage($msg, $null, $imModality) | Out-Null
# End the Convo to suppress the UI
$convo.End() | Out-Null
$Label3.Text = «Sent the following message to $target : $message»
}
Una vez que tenemos la funcion, crearemos la interfaz grafica.
foreach ($item in $List) {
$DropDownBox2.Items.Add($item)
}
$PrtForm.ShowDialog()
Quedara algo como esto.
Muy sencillo.
Target SIP Address : Direccion a la cual enviara el mensaje
From : idioma original
To: idioma al que traducira
Message: Mensaje a ser traducido
Send: Enviar y traducir
Cancel: Cerrar y cancelar
Esta es la primer etapa, voy a continuar trabajando hasta que este script este junto con el cliente de SfB sin necesidad de tenerlo separado
Por el momento, soporta hasta 60 idiomas, mismos que Azure Translate Service
En mi script solo agregue algunos, si deseas probar algun otro solo agregalo a la lista del dropbox list
Aqui hay un video de como funciona.
Espero les sea de ayuda.
———-ENGLISH——————–
Hey,
Today I bring to you a small project so now you can translate IM only, using Azure cognitive services as Translator Service, and connecting using powershell and Lync SDK.
At this early phase, this script only sends Translated IMs, but cannot translate incoming messages. But there’s a workaround. Let’s get started.
First you need to create an Azure Cognitive services on your Azure Portal (yes, you need to have Azure subscription)
Go to Cognitive Services, and select Translator Text API
Create a new service , and select the Free pricinig Tier. It will allow you to translate up to 2M characters without payment.
once is created, please copy Access Keys, as you will need it on the script.
Easy , does it?
Now, we need to create and configure our script.
The following is our Translate function, the core of the script. Here you only need to replace your accountKey to start working.
$ret = Invoke-RestMethod -Uri $uri -Method Get -Headers $header
$ret.OuterXml
$message= $ret.string.’#text’
if (-not (Get-Module -Name Microsoft.Lync.Model))
{
try
{
# you may need to change the location of this DLL
Import-Module «C:\Program Files (x86)\Microsoft Office 2013\LyncSDK\Assemblies\Desktop\Microsoft.Lync.Model.dll» -ErrorAction Stop
}
catch
{
Write-Warning «Microsoft.Lync.Model not available, download and install the Lync 2013 SDK http://www.microsoft.com/en-us/download/details.aspx?id=36824″
}
}
# Connect to the local Skype process
try
{
$client = [Microsoft.Lync.Model.LyncClient]::GetClient()
}
catch
{
Write-Host «nMust be signed-in to Skype"
break
}
# Add the contact URI
try
{
$contact = $client.ContactManager.GetContactByUri($target)
}
catch
{
Write-Host "nFailed to lookup Contact»$target
break
}
# Create a conversation
$convo = $client.ConversationManager.AddConversation()
$convo.AddParticipant($contact) | Out-Null
# Set the message mode as IM
$imModality = $convo.Modalities[1]
# Send the message
$imModality.BeginSendMessage($msg, $null, $imModality) | Out-Null
# End the Convo to suppress the UI
$convo.End() | Out-Null
$Label3.Text = «Sent the following message to $target : $message»
}
Once you get the core function, I create a GUI for easy control.
Microsoft acaba de presentar el Skype for Business settings portal, donde los usuarios podran configurar algunas caracteristicas de SfB
Cuales caracteristicas puede configurar?
Control caller ID permite a los usuarios realizar llamadas sin mostrar su Caller ID (es decir su numero). El administrador de la organizacion tiene que habilitar a los usuarios para realizar este cambiolos detalles de como hacerlo se pueden encontrar en el siguiente articulo How can caller ID be used in your organization
si no se permite al usuario hacer el cambio, mostrara un mensaje como el siguiente.
PIN reset Permite a los usuarios resetear el PIN de conferencia, asi que no sera necesario crear in ticket de soporte, ya tendran la habilidad de hacerlo por ellos mismos.
Microsoft just introduced Skype for Business settings portal, where the user can configure some settings.
What settings can users configure?
Control caller ID allows users to call phone numbers without showing their caller ID. The administrator of an organization has to enable users to change this setting. Details can be found in this support article: How can caller ID be used in your organization
Administrators needs to allow users to change this setting. if not users will receive a message like this.
PIN reset enables users to reset their conference PIN themselves – so from now on users will not require help-desk or administrators to reset their conference PIN.
Hoy vamos a hablar un poco sobre RHM (Regionally Hosted Meetings)
Con las reuniones hospedadas localmente (RHM por sus siglas en ingles) puedes tomar ventaja de los datacenter de Microsoft ubicados alrededor del mundo y puedes elegir donde estaran localizados tus usuarios en la nube de Microsoft. Tus usuarios se registraran en los datacenter locales y tendran la ventaja de que el meeting estara en la region y con ello aumentara el performance
Por ejemplo, el siguiente diagrama compara usuarios en dos companias diferentes, una de las cuales tiene implementado RHM. Alice – que se encuentra en Sydney, Australia – tiene seleccionado el data center de Australia, aunque la compania se encuentra en USA. Ella fisicamente se encuentra en una zona geografica que cuenta con un DataCenter de Microsoft, y puede hacer uso de esta ventaja en la region, incluyendo mejoras en la red y meetings.
Yamaha presensento el YVC-1000MS para espacios grandes de conferencias con Skype for Business.
El YVC-1000MS es una solucion escalable y flexible, diseñada para soportar los requerimientos de audio para espacios grandes de conferencias, salas con configuraciones espaciales, y tambien clases de educacion a distancia o seminarios con Skype for Business. Las caracteristicas del YVC-1000MS separan el microfono y la bocina que suavemente integran el audio para una comunicacion natural y confortable. La cancelacio de eco adaptativa de Yamaha y otras tecnologias de alta calidad de procesamiento de sonido, desarrolladas a traves de los años, ayudan a facilitar una conversacion libre de estres. El diseño user-friendly provee una manera intiutiva de conexion a una llamada mediante bluetooh y puede tomarse via USB en Skype for Business.
Disponible hasta Octubre 2017, Yamaha YVC-1000MS ha pasado la estricta certificacion Version 3 Skype for Business, cumpliendo con los altos estandares que definen las reuniones de Skype for Business, con un audio natural y claro.
Especificaciones
General
Interface
Control Unit: USB 2.0 High Speed, Bluetooth, NFC (Near Field Communication) Audio Input terminal (stereo RCA pin), Audio Output terminal (stereo RCA pin), External speaker terminal (RCA pin) x 2, Power terminal, Microphone terminal Microphone: Input and output terminals
Power consumption (max)
20 W (one connected microphone), 35 W (five microphones connected)
Radio interference standard
FCC (Part 15B) Class A, ICES-003
Power source
120 V (60 Hz)
Operating environment
Temperature: 0 to 40°C (32 to 104°F)
Humidity: 20 to 85% (no condensation)
Dimensions
Control Unit (W x H x D): 332 x 95 x 162 mm (13.1 x 3.74 x 6.38 in)
Microphone (W x H x D): 136 x 36 x 136 mm (5.35 x 1.42 x 5.35 in)
Weight
Control Unit: 1.8 kg (4.0 lbs), Microphone: 0.4 kg (0.9 lbs)
Supported OS
OS: 32-bit or 64-bit Windows 10, 32-bit or 64-bit Windows 8.1, 32-bit or 64-bit Windows 7, macOS 10.12, Mac OS X 10.11, Mac OS X 10.10
USB: USB 2.0 or later
Bluetooth
Bluetooth specification version: 2.1 + EDR
Supported profile: HFP (1.6), A2DP
Supported Codec: CVSD, mSBC, SBC
Wireless output: Class 2
Maximum communication distance: 10 m (32.8 ft)
Yamaha introduces its YVC-1000MS for large meeting spaces with Skype for Business.
The YVC-1000MS is a scalable and flexible solution engineered to support the audio requirements of large meeting rooms, rooms with special table configurations, and even remote education classes or seminars within the Skype for Business application. The YVC-1000MS features separate microphone and speaker units that smoothly integrate audio for natural, comfortable remote communication. Yamaha’s adaptive echo cancellation and other unique high-quality sound processing technologies developed over the years also help facilitate a stress-free conversation. The user-friendly design provides fast, intuitive connection to a call on a smartphone by Bluetooth® and can bridge to a Skype for Business call via USB.
Available in October 2017, the Yamaha YVC-1000MS microphone and speaker system has passed Skype for Business’ stringent Certification Version 3 tests, meeting the high standards that define the Skype for Business meeting experience with natural, clear audio.
Specifications
General
Interface
Control Unit: USB 2.0 High Speed, Bluetooth, NFC (Near Field Communication) Audio Input terminal (stereo RCA pin), Audio Output terminal (stereo RCA pin), External speaker terminal (RCA pin) x 2, Power terminal, Microphone terminal Microphone: Input and output terminals
Power consumption (max)
20 W (one connected microphone), 35 W (five microphones connected)
Radio interference standard
FCC (Part 15B) Class A, ICES-003
Power source
120 V (60 Hz)
Operating environment
Temperature: 0 to 40°C (32 to 104°F)
Humidity: 20 to 85% (no condensation)
Dimensions
Control Unit (W x H x D): 332 x 95 x 162 mm (13.1 x 3.74 x 6.38 in)
Microphone (W x H x D): 136 x 36 x 136 mm (5.35 x 1.42 x 5.35 in)
Weight
Control Unit: 1.8 kg (4.0 lbs), Microphone: 0.4 kg (0.9 lbs)
Supported OS
OS: 32-bit or 64-bit Windows 10, 32-bit or 64-bit Windows 8.1, 32-bit or 64-bit Windows 7, macOS 10.12, Mac OS X 10.11, Mac OS X 10.10
USB: USB 2.0 or later
Bluetooth
Bluetooth specification version: 2.1 + EDR
Supported profile: HFP (1.6), A2DP
Supported Codec: CVSD, mSBC, SBC
Wireless output: Class 2
Maximum communication distance: 10 m (32.8 ft)
How-to como reservar numeros en Skype for Business Online.
Ir al portar de Office365
portal.office365.com
Seleccionar el icono de Admin
Ir al Portal de Administracion de Skype for Business
Ir a la pestaña de numeros en la seccion de voz.
Dar clic en el signo de +, y seleccionar el tipo de numero que quieres reservar (usuario o servicio)
Selecciona el país, estado y ciudad. Y escribe la cantidad de numeros que quieres reservar, da click en Add.
Ahora veras los numeros que Microsoft, puede reservar para ti. Tienes solo 10 minutos para confirmar antes de que Microsoft tome esos numeros de vuelta. Si estas de acuerdo con esos numeros da clic en acquire numbers, de otra forma da en cancelar e intenta de nuevo con otro rango.
Ahora puedes ver los nuevos numeros en la pestaña de Phone
Espero les sea de ayuda.
———– ENGLISH———————
How-to Reserve PSTN Number on Skype for Business Online.
Go to office 365 portal.
portal.office365.com
Click on Admin Icon.
Go to Skype for Business Admin Center
Go to Phone Numbers tab on voice section
Click on the plus sign and select what type of number you want to reserve (user or service)
Select country , state and city. And type amount of numbers you want to reserve. Click on Add Button.
Now you will see the numbers Microsoft reserve for you, you have only 10 minutes to confirm before Microsoft take back that pool of numbers. If you agree with those numbers click on acquire numbers button, otherwise click on cancel and try again to give you another range.