---
title: Receiving “Unprocessable Content” error on Mobile Cloud calling
description: "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: ..."
url: "https://supportb.kinsta.cloud/docs/receiving-unprocessable-content-error-on-mobile-cloud-calling/"
updated: "2024-09-26"
category: Cloud Calling
---

# Receiving “Unprocessable Content” error on Mobile Cloud calling

**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:
![Alert](https://static.zohocdn.com/zoho-desk-editor/static/images/exclamation.png){"Status":"Error","Message":"Unprocessable Content","ExceptionType":"CallNotConnectedException"}
**Root Cause:**

1. API call is missing a header value
2. Mapping is not set up correctly.

**Solution:**

1. Add a header value in the MCC connector's click2call API setup. The header data is as below:

![Idea](https://static.zohocdn.com/zoho-desk-editor/static/images/lights.png)Content-Type: application/json

1. Verify that the mapping (3rd step of configuring the MCC click2call setup) is done as expected.