accessToken is well received. After that, 500 Server Error appears when requesting placeCall. How can you resolve the issue?

[robbie-ai]

accessToken is well received. After that, 500 Server Error appears when requesting placeCall. How can you resolve the issue?

[bobiechen-twilio]

Hi @robbie-ai

It seems like you are getting authentication error when calling the REST API.

Can you check your account credentials from the System.getProperty() method when executing the callUsingRestClient() method?

Thanks,
bobie

[bobiechen-twilio]

Hi @robbie-ai

Glad that the original API issue has been resolved.

If I am understanding the new issue correctly, after creating the VoIP certificate and setting up the Push Credential, you were able to register and receive incoming call push notifications on your mobile client but somehow you are still seeing the errors (20103) in your Twilio developer console. Is this correct?

I've removed your last comment since your account credentials have been exposed. Please update your Twilio auth token, API key and secret as soon as possible.

Thanks.

[robbie-ai]

thank you.

An error occurs when you try to call the app after proceeding according to the guide order.
However, it is successful when proceeding makeCall in the browser.
What is the problem with inferring the above process?

[bobiechen-twilio]

Hi @robbie-ai

An error occurs when you try to call the app after proceeding according to the guide order.

Did you mean that you followed the guide and registered the mobile client? Were you able to receive an incoming call on the client? Where and what is the error you are seeing?

However, it is successful when proceeding makeCall in the browser.

Can you describe what happened when successfully calling the makeCall endpoint in the browser? The makeCall endpoint is meant for Twilio Voice service to fetch the TwiML response in order to determine the next, in this case it tells Twilio to make a call to a client or a number, or play a short message using the verb.