Correction in sending DTMF via SIP INFO

[luan-evangelista]

Problem:

When using the sendDTMF function, sending multiple DTMFs failed because the position was not being correctly reset after sending each tone, which resulted in tones being ignored or not sent properly.

Previous behavior:

In the previous state, the logic was not adequate to correctly handle the sending of multiple tones, causing interruptions in the sequential sending of DTMFs. The specific problem was that the code used incorrect logic for manipulating the position index, which caused errors when DTMFs were queued.

Solution:

The implemented correction restructures the management of the position variable and ensures that DTMFs are sent correctly, one at a time, respecting the configured duration and interToneGap values.

Additionally, new logic resets position to ensure that all tones in the queue are sent correctly, resolving the issue of tones being omitted or ignored during the send sequence.

Tests:

After the correction, DTMF sending was validated and all tones were sent as expected without interruptions.

[jmillan]

This must remain as it it, because there may already be tones being sent by other previous calls to this method.

What we want to do is:

• remove the variable position. It's local to this function and breaks things when there are already tones being sent.
• substitute code above

  const tone = this._tones[position];
  position += 1;

by

// Retrieve the next tone.
const tone = this._tones[0];
 
// Remove the tone from this._tones.
this._tones.substring(1);