Trying to use SMS integration with Twilio in Node-RED in CF on IBM Cloud to drive individual SMS messages from mobile devices to Assistant. Here is my configuration of the Assistant v2 node:
When configured this way, the Assistant API call works and I get the Assistant conversation_start response. However, when I send a different input in reply to the conversation_start response, I once again get the conversation_start response instead of a response from the appropriate Assistant flow.
This sequence makes me think that Assistant is resetting the session each time since the response is always the conversation_start response. I never can get to any farther in Assistant.
The note at the bottom of the image makes me think I need to set msg.params.session_id, but I would also think checking Multiple Sessions and Return Context would handle setting the session_id correctly.
However, when I uncheck the Multiple Sessions box, the Assistant API call gets this error on the Assistant v2 node: "URL sessionid parameter '+1303xxxyyyy' is not a valid GUID." The '+1303xxxyyyy' is the SMS device phone number.
I'm confused on how to configure the Assistant v2 node to handle multiple sessions with the input coming from the Twilio API. Can you shed some light on this?
Can you explain further how Multiple Sessions, Return Context and msg.params.session_id work together?
Note: With Multiple Sessions and Return Context set, I also tried setting msg.user ahead of the Assistant node per @chughts January '18 reply here: https://developer.ibm.com/answers/questions/424697/watson-conversation-links-to-node-red-and-then-to/. That didn't change anything, unfortunately.