Baseline Widely available
The RTCDTMFSender
interface's toneBuffer property returns a string containing a list of the DTMF tones currently queued for sending to the remote peer over the RTCPeerConnection
. To place tones into the buffer, call insertDTMF()
.
Tones are removed from the string as they're played, so only upcoming tones are listed.
ValueA string listing the tones to be played. If the string is empty, there are no tones pending.
ExceptionsInvalidCharacterError
DOMException
Thrown if a character is not a DTMF tone character (0-9
, A-D
, #
, or ,
).
The tone buffer is a string which can contain any combination of the characters that are permitted by the DTMF standard.
DTMF tone charactersThese characters represent the digit keys on a telephone keypad.
These characters represent the "A" through "D" keys which are part of the DTMF standard but not included on most telephones. These are not interpreted as digits. Lower-case "a"-"d" automatically gets converted to upper-case.
These correspond to the similarly-labeled keys which are typically on the bottom row of the telephone keypad.
This character instructs the dialing process to pause for two seconds before sending the next character in the buffer.
Note: All other characters are unrecognized and will cause insertDTMF()
to throw an InvalidCharacterError
DOMException
.
For example, if you're writing code to control a voicemail system by sending DTMF codes, you might use a string such as "*,1,5555"
. In this example, we would send "*"
to request access to the VM system, then, after a pause, send a "1" to start playback of voicemail messages, then after a pause, dial "5555" as a PIN number to open the messages.
Setting the tone buffer to an empty string (""
) cancels any pending DTMF codes.
tbd
Specifications Browser compatibility See alsoRetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.3