When using dial tones for the send digits, they do not play the audio, instead the following is thrown in Firefox.
Chrome plays audio fine without throwing this error.
TypeError: note1.noteOn is not a function
|
|
note1.noteOn(0.0);
|
This can even be tested with the kitchen sink demo.
Hello,
Can you please relay the full console logs and your code? We need a bit more information then what was given. Once we have that we will investigate further, thank you!
DTMF tones is not audible in browser, but successfully send to remote. I think, it is not implemented in mozilla firefox.
Log from firefox-26 with WebRTC:
20:20:14.580 "20:20:14.579 INFO - [EVENT] answer[undefined]" jquery.phono.js:8825
20:20:14.580 "20:20:14.580 DEBUG - [INVOKE] Call.onanswer([object Object],undefined)" jquery.phono.js:8825
20:20:14.580 "20:20:14.580 DEBUG - [PSTROPHE] _throttledRequestHandler called with 0 requests" jquery.phono.js:8825
20:20:14.829 "20:20:14.829 DEBUG - [PSTROPHE] request id 12.0 posting" jquery.phono.js:8825
20:20:14.830 "20:20:14.830 DEBUG - [PSTROPHE] request id 12.0 state changed to 1" jquery.phono.js:8825
20:20:14.830 "20:20:14.830 DEBUG - WIRE <body rid="191666305" sid="e8493095-3051-42a7-b9ce-2f8450d5f8fd"><iq type="result" id="359239d3-f828-440a-9266-3e23bb64befb" to="821071\40ekiga.net@sip"/></body>" jquery.phono.js:8825
20:20:15.979 POST http://pgw-v11f.phono.com:8080/http-bind [HTTP/1.1 200 OK 10409мс]
20:20:16.500 "20:20:16.500 INFO - onAddStream. Attaching" jquery.phono.js:8825
20:20:16.576 Unhandled state type: 1
20:20:16.617 "20:20:16.617 DEBUG - remoteDescription happy" jquery.phono.js:8825
20:20:24.706 TypeError: note1.noteOn is not a function jquery.phono.js:6801
20:20:24.691 "20:20:24.691 DEBUG - [INVOKE] Call.digit(2)" jquery.phono.js:8825
20:20:24.693 "20:20:24.692 DEBUG - [PSTROPHE] _throttledRequestHandler called with 1 requests" jquery.phono.js:8825
20:20:24.693 "20:20:24.693 DEBUG - [PSTROPHE] _processRequest: first request has readyState of 1" jquery.phono.js:8825
20:20:24.693 "20:20:24.693 DEBUG - freep 2" jquery.phono.js:8825
20:20:24.846 "20:20:24.845 DEBUG - [PSTROPHE] request id 13.0 posting" jquery.phono.js:8825
20:20:24.846 "20:20:24.846 DEBUG - [PSTROPHE] request id 13.0 state changed to 1" jquery.phono.js:8825
20:20:24.847 "20:20:24.847 DEBUG - WIRE <body rid="191666306" sid="e8493095-3051-42a7-b9ce-2f8450d5f8fd"><iq type="set" to="821071\40ekiga.net@sip" id="4701:sendIQ"><jingle action="session-info" initiator="webcallwebrtc" sid="21d1d65d08ed62c6b4ad7a8a962239b8"><dtmf code="2" duration="50" volume="42"/></jingle></iq></body>"
As stated from the above user, tones are sent to the recipient, but not audible to the user on the latest Firefox.
You don't need my code, as it is also the case with your Kitchen Sink example: http://s.phono.com/releases/1.1/samples/kitchen-sink/www/index.html#
Called using the default example sip.
See attached log.
Look for:
jquery.phono.js (line 8825)
TypeError: note1.noteOn is not a function
note1.noteOn(0.0);
Hi there,
I was able to reproduce the issue. We'll escalate to our engineers for further investigation and post back when we have additional information on this.
Any update on this?
Hello,
When I am send the digits for dialing extension number to the remote party, some times it does not connect. I checked the log, it seems like as below.
11:43:50.241 DEBUG - [INVOKE] Call.digit(1) webphone_1.0.js?t=1393481518:9733
11:43:50.968 DEBUG - [INVOKE] Call.digit(3) webphone_1.0.js?t=1393481518:9733
11:43:52.033 DEBUG - [INVOKE] Call.digit(9) webphone_1.0.js?t=1393481518:9733
I am quite not understand why it's happening like that some times connects and disconnects. Anybody knows about this please help me.Thanks! surya
I can reproduce it from my Firefox 27.0.1 (I can hear the dial tone from my Chrome 30.0.1599.0 dev). I'll ask our engineers to take a check about it, and we will update here as soon as possible.
@Surya, your problem might be different, as we can indeed send/receive DTMF press. Could you please open an account ticket or send us an email at support@tropo.com with the browser console logs and Tropo logs (if Tropo is involved in your project) so that we can look into further? Note please donot post any logs/script here since they may contains your personal information (This is a public forum). Thanks!
Our phono engineer said that this was a known limitation of Firefox due to partial webaudio support. We will get the current release finished. Thanks!