In the agentless SMS integreation this is my response when sending a test message. This is after I sent the *unstop* *start* and *yes* text messages. Any ideas on how to clear this issue are appreciated.
Thank you!
{
"message": "The request could not be understood by the server due to malformed syntax.",
"code": "bad.request",
"status": 400,
"messageParams": {},
"contextId": "b63254ec-43ff-43e2-83c5-c8cc90fd255d",
"details": [
{
"errorCode": "ACTION.REMOTE_ENDPOINT"
}
],
"errors": [
{
"message": "REST call for action execute failed. Message: Request to backend service failed. Response from web service: {\"message\":\"Bad request: An active conversation is already in progress\",\"code\":\"bad.request\",\"status\":400,\"contextId\":\"23fe2bca-af6b-497f-81c5-8b9daf26150a\",\"details\":[],\"errors\":[]} [b63254ec-43ff-43e2-83c5-c8cc90fd255d]",
"code": "BAD_REQUEST",
"status": 400,
"messageParams": {},
"details": [],
"errors": []
}
]
------------------------------
Michele Russo
NTT America, Inc
------------------------------
Original Message:
Sent: 01-23-2023 14:53
From: Michele Russo
Subject: SMS blocked numbers
Hi,
I am working with a client on an SMS implementation. We are testing the *help* and *stop* built in functions. When I send a *stop* request all new messages are blocked, but when I send an *unstop* request messages are still not being delivered.
Does anyone know if there is a timer associated with the built in *stop* fuctionality? Will this expire in 24 hours?
I cant really find much documentation on this online.
Thank you in advance.
Michele Russo
michele.russo@global.ntt
#Unsure/Other
------------------------------
Michele Russo
NTT America, Inc
------------------------------