CODEWITHSUNDEEP
botframeworkazure-bot-service
Pravin Ambekar.
Pravin Ambekar.

Reputation: 112

Is there an issue with Bot Framework Virtual Assistant template when Direct Line App Service Extension is enabled

I have Azure Bot deployed with Virtual Assistant Template, which was working fine (And still working in Portal's Test In Web Chat feature) until I enabled Direct Line App Service Extension.

Primary objective to enable DL App Service extension is to isolate bot access and secure app service.

I have followed MS documentation https://learn.microsoft.com/en-us/azure/bot-service/bot-service-channel-directline-extension-net-bot?view=azure-bot-service-4.0 and ensured every step is configured correctly.

Primary step to make sure DL app service is working correctly is to check if https://xxx.azurewebsites.net/api/messages or https://xxx.azurewebsites.net/.bot/ url return correct json result f.x: {"v":"123","k":true,"ib":true,"ob":true,"initialized":true} But instead i am getting Error Response 400 Bad Request and error message appeared in browser is : "Upgrade to WebSocket is required."

I couldn't even reach to a step where troubleshooting guide mentioned here : https://learn.microsoft.com/en-us/azure/bot-service/bot-service-channel-directline-extension-net-bot?view=azure-bot-service-4.0#troubleshooting could help to resolve.

As i said earlier Bot is still working and the url : https://xxx.azurewebsites.net loads site correctly , can be seen in below enter image description here

Any help is appreciated

Upvotes: 2

Views: 548

Answers (1)

Sanjeevi Subramani
Sanjeevi Subramani

Reputation: 571

These are the changes I have done and it worked:

Refer Repo With sample code: https://github.com/SSanjeevi/VirtualAssistantDirectlineExtn

Wrote detailed here.

Project file:

 <PropertyGroup>
<TargetFramework>netcoreapp3.1</TargetFramework>
<AspNetCoreHostingModel>OutOfProcess</AspNetCoreHostingModel>
<NoWarn>NU1701</NoWarn>
<Version>1.0.3</Version>

BotController.cs

 private readonly IBotFrameworkHttpAdapter adapter;

 public BotController(IBotFrameworkHttpAdapter httpAdapter, IBot bot)

Startup.cs

Configure Services method:

 // Register the Bot Framework Adapter with error handling enabled.
            // Note: some classes use the base BotAdapter so we add an extra registration that pulls the same instance.
            services.AddSingleton<IBotFrameworkHttpAdapter, DefaultAdapter>();
            services.AddSingleton<BotAdapter>(sp => sp.GetService<BotFrameworkHttpAdapter>());
            // Configure channel provider

Configure method:

using Microsoft.Bot.Builder.Integration.AspNet.Core; app.UseHsts();

            app.UseCors(x => x.AllowAnyOrigin()
                .AllowAnyHeader()
                .AllowAnyMethod());
            // Allow the bot to use named pipes.
            app.UseNamedPipes(System.Environment.GetEnvironmentVariable("APPSETTING_WEBSITE_SITE_NAME") + ".directline");

Webchat:

   let directLineConnection = await window.WebChat.createDirectLineAppServiceExtension({
                domain: domainUrl,
                token
            });

The attached repo code also contains serilog implementation to have logging in log stream in app service where you can see the error logs if you face any issues.

Follow this article and implement serilog in bot api and deploy . https://www.lkgforit.com/2022/10/troubleshooting-by-writing-logs-at_15.html

Upvotes: 1

Related Questions