Create call conversation fails

Platform API JavaScript SDK
1

I use the following code to create a call conversation:

function placeCall(phoneNumber) {
  console.log('calling', phoneNumber);
  var conversationsApi = new ConversationsApi(pureCloudSession);
  var body = {
    "phoneNumber": phoneNumber
  };
  conversationsApi.postCalls(body).done(function(result) {
    console.log(result);
  }).error(function(error) {
    console.error(error);
  });
}

Console.log shows this:

calling +33680854089
index.js:103 Object {id: "e6fc0fd4-d6aa-4200-afe6-7e54630a3236", selfUri: "/api/v2/conversations/calls/e6fc0fd4-d6aa-4200-afe6-7e54630a3236"}

No errors are reported.

When I check in PC, I see this:

It times out after 60 seconds with a Call Connection Timeout error.

If I try to dial the same number from PC directly, it works:

I see that all parameters (except phoneNumber) are optional. I use a WebRTC station in that org. Are there any other parameters that should be populated when calling postCalls()?

Thanks.

2

Tried myself and got the same response. The difference you are seeing is the sdk is using v2 and the client is using v1, let me check with the dev team.

3

I use a WebRTC station in that org

Can you try with a physical phone and see what happens? I've seen the same timeout behavior when dialing from the purecloud UI and using a WebRTC station; my guess is that it isn't an API issue but an issue with the WebRTC station/edge.

4

That worked with a physical phone. Thanks!

5

Hi - is there an update on this? I had the same issue yesterday and wondered if it was being investigated as a bug?

6

I have same issues with webRTC phone and placing a call with API.

7

This is an issue with the WebRTC softphone, not the API. The API simply sends a dial request to PureCloud; it is entirely ignorant of the station being used. For further assistance, please Contact PureCloud Support.

edit: For a little background, this is currently a technical limitation of WebRTC stations and there is a very technical explanation of why it is that way. However, there are use cases that require the dial request to be made from a client that is not also a webrtc endpoint. The dev team for the WebRTC softphone is working on options to support these use cases.

8