Problem:
Post configuring Mobile Cloud calling connector within LSQ, and even after receiving a success response while testing the click2call API, the call would not initiate. On searching through the Telephony logs, the below message is received:
{“Status”:”Error”,”Message”:”Unprocessable Content”,”ExceptionType”:”CallNotConnectedException”}
Root Cause:
- API call is missing a header value
- Mapping is not set up correctly.
Solution:
- Add a header value in the MCC connector’s click2call API setup. The header data is as below:
Content-Type: application/json
- Verify that the mapping (3rd step of configuring the MCC click2call setup) is done as expected.
