25977 2014-06-04 09:33:44 +0000 DTMFSender should have an onerror event handler 2014-06-11 07:19:43 +0000 1 1 1 Unclassified WebRTC Working Group WebRTC API unspecified All All RESOLVED WONTFIX P2 normal --- 1 kiran.guduru public-webrtc adam.bergkvist juberti public-webrtc oldest_to_newest 107250 0 kiran.guduru 2014-06-04 09:33:44 +0000 Errors on a DTMFSender need to be reported through an error event, say DTMFError. 1. Invalid DTMF values 2. Values of duration and interToneGap with out of range values. 107280 1 juberti 2014-06-04 18:28:52 +0000 Shouldn't those throw an exception? Those can be easily detected synchronously. 107332 2 kiran.guduru 2014-06-05 09:47:15 +0000 (In reply to Justin Uberti from comment #1) > Shouldn't those throw an exception? Those can be easily detected > synchronously. I agree that duration and interToneGap ranges can be detected and thrown as exceptions. But onerror seems still required for reporting error in case of inserting invalid DTMF values [1], Bug: 25837. [1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=25837 107388 3 juberti 2014-06-05 17:46:05 +0000 It's not required - we could parse the string synchronously and return an error, which would be nicer than playing out some tones and then stopping with an error. 107634 4 adam.bergkvist 2014-06-11 07:19:43 +0000 (In reply to Kiran from comment #0) > 1. Invalid DTMF values Updated insertDTMF() algorithm to ignore unrecognized characters. Proposed fix [1] > 2. Values of duration and interToneGap with out of range values. This was fixed in [2]. Closing this bug as WONTFIX. [1] https://github.com/fluffy/webrtc-w3c/commit/d58a8bcf7ac4998dea3f670ccd278ce1c0b6c89e [2] https://www.w3.org/Bugs/Public/show_bug.cgi?id=25976