Deploy to another environment outside of Azure about botbuilder-realtimemediacalling

[kronwell]

Thanks. It would be nice to have a sample, that can be deployed as an Asp.Net web application, or at least some checklist what needs to be done. Has anyone tried to do this?

[MalarGit]

When we took a look a while back, ILPIP needed by the platform SDK was not supported in Azure App services. I think it is supported now. We plan to take a look at it soon. If that works, I will post a sample here. please watch out for updates. thanks

[MalarGit]

The samples are only for Azure cloud service. But the platform SDKs does not have any restrictions. You will have to configure the public IP, provide an equivalent of InstanceInputEndpoint, open up corresponding ports, etc.

[gfclaveria]

@MalarGit

If the RealTimeMediaCalling bot application will be deployed other than Azure cloud, is certificate still needed?

Do you now have sample that doesn't require certificate?

[MalarGit]

@gfclaveria yes a certificate is a must. The platform requires a certificate in order to communicate securely with the Skype calling cloud.

[gfclaveria]

@MalarGit I see, Thanks.

[prabhakarreddy1234]

@MalarGit
Can we deploy the application built using Platform SDKs on Azure App Services ? If yes, what precautions do we need to take ? Any sample or steps on how to do it would be great.

[prabhakarreddy1234]

Cool. That would be great. Any ETA on that ? Rather than sample, Pre-requisites and steps to follow should be enough initially i guess.

[ssulzer]

Hi @prabhakarreddy1234

We don't know if supporting Azure App Service is feasible for real-time media bots, and that is not in our plans currently. Supporting real-time media bots on Azure Service Fabric with VM scale sets is on our internal backlog but we cannot offer an ETA for when the SDK would have official support. However, with the recent Azure networking updates (https://github.com/Azure/vm-scale-sets/tree/master/preview/network), there is now support to assign each VM in the set a public IPv4 address - which is required for hosting real-time media bots. So Azure Service Fabric is something you could try out if you want. Please see the section "Public IPv4 per virtual machine" in the following article:
https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-networking

Thanks,
Stephen

[kronwell]

Are there any news on this topic? Meanwhile we were able to move our complete bot stack to docker containers except real time bot channel which is still nasty and obsolete cloud service. Is anybody in MS still working on real-time bot sdk or it is already abandoned?

[ssulzer]

Hi @kronwell

There are no updates on this. Use of the Skype Real-Time Media Bot platform requires Azure running Windows Server and the .NET Framework, along with certain provisioned VM resources:

• a public IP address (ILPIP) for each VM (https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-networking#public-ipv4-per-virtual-machine);

• a mapping from a public port on the service's VIP to a private port for each VM; known as an Instance InputEndpoint for Classic Cloud Services, or Inbound NAT pools for VM Scale Sets (https://github.com/rbitia/azure-content/blob/master/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-windows-autoscale.md).

The BotBuilder-RealTimeMediaCalling SDK docs and samples have not been updated to demonstrate building and deploying a real-time media bot using Azure Resource Manager (ARM) or VM Scale Sets (with ILPIP and Inbound NAT pools configured), but these can be used. You do not have to use a Classic (ASM-based) Cloud Service.

To my knowledge, using a Docker for Windows container to deploy a real-time media bot does not work, unfortunately. Docker for Windows does not provide/support a full Windows Server 2016 OS container, only Windows Server 2016 Core and Nano, but these are insufficient for the real-time media bot platform.