在Gupshup僵尸程序对Api.ai的调用中维护会话 [英] Maintaining session in Gupshup bot calls to Api.ai

问题描述

我正在使用Api.ai集成在Gupshup中构建一个机器人.我在Api.ai中有一个具有多个意图的代理，并且每个意图都通过上下文(输入和输出上下文)链接.当我使用以下代码调用Api.ai时，将调用第一个意图，然后得到答复.但是，当给出第二条消息时，僵尸程序会将其视为一条全新的消息，而不会标识其与第一条消息的关系. 我该如何解决这个问题?请帮助

I am building a bot in Gupshup with Api.ai integration. I have an agent in Api.ai with several intents and each of them linked through contexts(input & output contexts). When I use the following code to call Api.ai, the first intent is called and I get the reply. However when the second message is given, the bot takes it as a completely new message, without identifying its relation with first. How can I solve this issue? Kindly help

function MessageHandler(context, event) {
    // var nlpToken = "xxxxxxxxxxxxxxxxxxxxxxx";//Your API.ai token
    // context.sendResponse(JSON.stringify(event));
    sendMessageToApiAi({
        message : event.message,
        sessionId : new Date().getTime() +'api',
        nlpToken : "3626fe2d46b64cf8a9c0d3bee99a9sb3",
        callback : function(res){
            //Sample response from apiai here.
            context.sendResponse(JSON.parse(res).result.fulfillment.speech);
        }
    },context)
}

function sendMessageToApiAi(options,botcontext) {
    var message = options.message; // Mandatory
    var sessionId = options.sessionId || ""; // optinal
    var callback = options.callback;
    if (!(callback && typeof callback == 'function')) {
       return botcontext.sendResponse("ERROR : type of options.callback should be function and its Mandatory");
    }
    var nlpToken = options.nlpToken;

    if (!nlpToken) {
       if (!botcontext.simpledb.botleveldata.config || !botcontext.simpledb.botleveldata.config.nlpToken) {
           return botcontext.sendResponse("ERROR : token not set. Please set Api.ai Token to options.nlpToken or context.simpledb.botleveldata.config.nlpToken");
       } else {
           nlpToken = botcontext.simpledb.botleveldata.config.nlpToken;
       }
    }
    var query = '?v=20150910&query='+ encodeURIComponent(message) +'&sessionId='+sessionId+'&timezone=Asia/Calcutta&lang=en    '
    var apiurl = "https://api.api.ai/api/query"+query;
    var headers = { "Authorization": "Bearer " + nlpToken};
    botcontext.simplehttp.makeGet(apiurl, headers, function(context, event) {
       if (event.getresp) {
           callback(event.getresp);
       } else {
           callback({})
       }
    });
}

/** Functions declared below are required **/
function EventHandler(context, event) {
    if (!context.simpledb.botleveldata.numinstance)
        context.simpledb.botleveldata.numinstance = 0;
    numinstances = parseInt(context.simpledb.botleveldata.numinstance) + 1;
    context.simpledb.botleveldata.numinstance = numinstances;
    context.sendResponse("Thanks for adding me. You are:" + numinstances);
}

function HttpResponseHandler(context, event) {
    // if(event.geturl === "http://ip-api.com/json")
    context.sendResponse(event.getresp);
}

function DbGetHandler(context, event) {
    context.sendResponse("testdbput keyword was last get by:" + event.dbval);
}

function DbPutHandler(context, event) {
    context.sendResponse("testdbput keyword was last put by:" + event.dbval);
}

推荐答案

必须为用户固定sessionId.您可以通过两种方式在Gupshup机器人代码中执行此操作-

The sessionId has to be fixed for a user. There are two ways you can do this in the Gupshup bot code -

1. 使用唯一的用户ID，该ID将发送给每个用户的机器人. 要获得此值，您可以使用-

1. Use the unique userID which is sent to the bot for every user. To get this value you can use -

event.senderobj.channelid

event.senderobj.channelid

但是此值取决于不同的消息传递渠道如何提供它，并且api.ai的限制为36个字符.

But this value is dependent on how different messaging channels provides it and api.ai has a limit of 36 characters.

示例代码-

function MessageHandler(context, event) {
sendMessageToApiAi({
    message : event.message,
    sessionId : event.senderobj.channelid,
    nlpToken : "3626fe2d46b64cf8a9c0d3bee99a9sb3",
    callback : function(res){
        //Sample response from apiai here.
        context.sendResponse(JSON.parse(res).result.fulfillment.speech);
     }
   },context)
}

为每个用户生成一个唯一的sessionId，并将其存储在数据库中以使用它.在下面的示例中，我将sessionId存储在roomleveldata中，这是Gupshup提供的默认持久性，要了解更多信息，请检查示例代码-

function MessageHandler(context, event) {
sendMessageToApiAi({
    message : event.message,
    sessionId : sessionId(context),
    nlpToken : "84c813598fb34dc5b1f3e1c695e49811",
    callback : function(res){
        //Sample response from apiai here.
        context.sendResponse(JSON.stringify(res));
    }
   },context)
}
function sessionId(context){
 var userSession = context.simpledb.roomleveldata.sessionID;
 if(!userSession){
   userSession = new Date().getTime() +'api';
    context.simpledb.roomleveldata.sessionID = userSession;
   return userSession;
 }else{
    return userSession;
 }
}

请记住，sessionId不得超过36个字符.

这篇关于在Gupshup僵尸程序对Api.ai的调用中维护会话的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！