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.

Sign up for GitHub

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

Jump to bottom

Capabilities and Settings for DTMF #177

Closed
aboba opened this issue Feb 9, 2015 · 2 comments
Closed

Capabilities and Settings for DTMF #177

aboba opened this issue Feb 9, 2015 · 2 comments
Labels
1.0 compatibility issue PR exists

Comments

@aboba
Copy link
Contributor

aboba commented Feb 9, 2015

The current ORTC API document does not define capabilities and settings for DTMF (RFC 4733). This should be added to Section 9.3.2.

Useful properties would include ptime as well as the DTMF Named Events supported (e.g. 0-15).
@aboba
Copy link
Contributor Author

aboba commented Feb 9, 2015

Proposed solution is to add a section 9.3.2.1:

9.3.2.1 DTMF

The following capabilities are defined for DTMF, as noted in [RFC4733] Section 2.4:

Property Name Values Notes
events DOMString An indication of what telephony events are supported (or configured). Events are listed as one or more comma-separated elements. Each element can be either a single integer providing the value of an event code or an integer followed by a hyphen and a larger integer, presenting a range of consecutive event code values. The list does not have to be sorted. No white space is allowed in the argument. The union of all of the individual event codes and event code ranges designates the complete set of event numbers supported by the implementation.

@aboba
Copy link
Contributor Author

aboba commented Mar 11, 2015

Slight update to the text: change "capabilities" to "capabilities and settings".

robin-raymond pushed a commit that referenced this issue Mar 25, 2015
- Added Section 8.3.1 on RTP matching rules, as noted in: Issue #48
b03c129 
- Revised the text relating to RTCDtlsTransport.start(), as noted in: Issue #168
- Clarified pruning of local candidates within the RTCIceGatherer, as noted in: Issue #174
- Clarified handling of incoming connectivity checks by the RTCIceGatherer, as noted in: Issue #170
- Added Section 9.3.2.1, defining DTMF capabilities and settings, as noted in: Issue #177
- Clarified pre-requisites for insertDTMF(), based on: Issue #178
- Added Section 8.3.2 and updated Section 9.5.1 to clarify aspects of RTCP sending and receiving, based on: Issue #180
@aboba aboba closed this as completed Apr 15, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
1.0 compatibility issue PR exists
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@aboba @robin-raymond