Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix for WebRTC 1.0 Issue 391 A-D in DTMF (and change log additions) #285

Merged
merged 3 commits into from Dec 1, 2015

Conversation

aboba
Copy link
Contributor

@aboba aboba commented Nov 28, 2015

The following issue was filed against WebRTC 1.0 relating to DTMF support:
w3c/webrtc-pc#391

It was resolved in the following PR:
w3c/webrtc-pc#402

The following issue was filed against WebRTC 1.0 relating to DTMF support: 
w3c/webrtc-pc#391

It was resolved in the following PR: 
w3c/webrtc-pc#402
@aboba aboba changed the title Fix for WebRTC 1.0 Issue 391 A-D in DTMF Fix for WebRTC 1.0 Issue 391 A-D in DTMF (and change log additions) Nov 28, 2015
@rshpount
Copy link

There is no reason not to support A-D. Support for A-D DTMF tone generation requires no additional code. These codes, even though they are not present on standard DTMF keypads, are still used by some of the IVR systems for automated entry. It makes no sense to remove already implemented features with no discussion. It probably makes more sense to harmonize in the opposite direction (i.e. change the IETF draft).

@robin-raymond
Copy link
Contributor

I agree there's no reason not to support. Takes more effort to not support (mostly). However, this is about mandatory support of legacy devices and nothing stops implementations doing the full support (which they likely will if they intend to support DTMF). I know ortc-lib will support it for example.

robin-raymond pushed a commit that referenced this pull request Dec 1, 2015
Fix for WebRTC 1.0 Issue 391 A-D in DTMF (and change log additions)
@robin-raymond robin-raymond merged commit 5f786dd into master Dec 1, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants