innovaphone Apps SDK Developer Forum

Registered 3 years 93 days

nickname Wednesday, 26 April 2023, 10:55 AM

Trouble sending DTMF consistent

Dear Innovaphone forum,

is there a possibility to send DTMF via client side/api on existing calls?

We tried the RCC api on the service side, but when the call needs more time to connect it happens to fail. We found it to be more consistent when the DTMF gets triggerd via the softphone.

We also found a not documented api, called "callkit" which happens to have some kind of DTMF functionality. We assume that this api is for confrences, but if not: How can we get the needed uuid to access the api functions?

Moderator

Registered 13 years 109 days

Andreas Fink (innovaphone) Friday, 28 April 2023, 11:21 AM

Re: Trouble sending DTMF consistent

Hello Nick,

the RCC API would be the correct way to send DTMF in an active call. I would track down the issue ("but when the call needs more time to connect it happens to fail") and stick on this API. I would help you in this issue.

The callkit, as i know, is part of iOS myApps client integration. Not sure, if it fulfil your requirements.

Best Regards

Andreas Fink

Registered 3 years 93 days

nickname Wednesday, 3 May 2023, 10:34 AM

Re: Trouble sending DTMF consistent

Hello,

Lets say: I have a client-side hidden app which has the job to send DTMF to an existing call for an user.

I see two Options:

1. phoneApi.send({mt: "SendDTMF", dtmf: "123"}); via the the phoneapi in the front-end.

2. RCC on service side - init user, caching the rcc call id and then sending the DTMF with the correct conf id.

Currently we solved it with the second option, but it feels laborious.

To make things easier I would prefer a solution like option one or the ability to control the rcc api with the guid of the call (so that we dont have to init a user with rcc and also dont have to track the corret conf id).

Moderator

Registered 13 years 109 days

Andreas Fink (innovaphone) Wednesday, 3 May 2023, 11:48 AM

Re: Trouble sending DTMF consistent

Well, this is how the RCC API is implemented in the PBX. With the call id, the PBX can directly assign the incoming RCC request to specific call, without looking up a user via guid first. This is a matter of performance and efficiency.

This is the same way, how the PBX SOAP API works.

Best Regards

Andreas Fink

You are here