Unable to reach IceConnectionState "completed" in new chrome browser "Version 52.0.2743.116 m" only getting IceConnectionState "checking", but same code working fine with chrome browser Version 51.0.2704.103 m media is flowing in this version.
I'm using kurento media server 6.0 and libnice version 0.1.13. Is this is the problem of kurento do I need to update anything ? (Server is returning SDP and IceCandidate in both browser version)
Chrome 52 changed the DTLS handshake (see the release notes) which might cause this if the servers ssl lib is too old.
Related
when I ran quic-go-0.18.1(https://github.com/lucas-clemente/quic-go) with command: go run main.go -bind=127.0.0.1:443 -qlog -tcp in dir /example.
I use the client to visit https://127.0.0.1/demo/tile, I could get response:(Proto:"HTTP/3"),
when I use chrome and chrome beta to visit https://127.0.0.1/demo/tile, I find chrome only use http/1.1 to visit my server.
My Question is : How I can use chrome to visit https://127.0.0.1/demo/tile through HTTP/3?
My environment: Ubuntu 20.04 LTS
Chrome switch on enable-quic.
GO version: 15
reading https://www.chromium.org/quic/quic-faq it says:
How do I aim Chrome at the test server? If you have an HTTP server,
you'll need it to emit a response header that looks like:
Alternate-Protocol: quic:< QUIC server port >
Then you can just run chrome as usual and it will automatically start
using QUIC.
If you're testing only with the toy quic server, you can do something
like:
% chrome --disable-setuid-sandbox --enable-quic
--origin-to-force-quic-on=localhost:6121 http://localhost:6121/
If you need help troubleshooting, try running the QUIC server with
--v=1 or check out playing-with-quic
does it solve your issue ? Please report for others.
I've seen that headless Chrome came out in some form last month and I've seen that it can be interacted with via Selenium but the articles I've seen mostly mention Linux and MacOS. Is this available for windows (7 and /or 10) yet?
The Headless mode for Windows is available in Chrome 60 beta, and the stable version is likely to be also in the 60th version.
https://www.google.com/chrome/browser/beta.html
There are no differences in the launch of Selenium
Yes, I use it on windows but with version 59 (beta) there is still an empty window popping up.
I've been using Chrome in headless mode for months, with Chrome 59 on Windows.
My Karma config (for a custom Chrome headless) is as follows:
browsers: ['Chrome_headless'],
customLaunchers: {
Chrome_headless: {
base: 'Chrome',
flags: ['--headless', '--disable-gpu', '--disable-plugins', '--window-size=0,0', '--window-position=-9999,0']
}
},
There is no visible window with these commands.
However, updating to Chrome 60 seems to have killed this config as it no longer works (as of today)
I am using Chromedriver headless mode with the version 2.33 with the following config for Capybara:
Capybara.register_driver :chrome_headless do |app|
args = ["--window-size=1280,1696", "--no-sandbox", "--headless", "--disable-gpu", "--disable-infobars", "--disable-notifications"]
Capybara::Selenium::Driver.new(app, {:browser => :chrome, :args => args})
end
It's working right now in chrome 59 with chromedriver 2.31 (just released). The only annoying thing is an empty window popping up at the beginning (just a visual effect) which will be removed in chrome 60 (should be about to release)
I have an ASP.NET application Hosted on server 2008.
Recently After latest chrome update to 53.0.2785.116m All of my downloads from server get fail.
I tested chrome version 52, firefox and IE! all of them work.
Any idea for this problem?
Finally I find the solution.
web servers by default set the "content-length" in header and also most of the browser auto correct the file size if its wrong.
in new version of google chrome (v53) the auto correct doesn't work.
And at the end I had to set "content-length" property in HTTP Context while flushing the file to client.
I am a newbie to webrtc2sip. I have setup my webrtc2sip gateway and registered to sip2sip.info as my domain. The problem is when I make video calls from chrome to any SIP client(ekiga/jitsi) the call gets connected but I am unable to see videos on both the sides.
==================================================================================
Case 1: Chrome calls SIP client
Result: No video shown on both transmit and receive side
==================================================================================
On the chrome JS console it says that :
State machine: tsip_dialog_register_InProgress_2_Connected_X_2xx SIPml-api.js?svn=179:1
==session event = m_stream_video_local_added SIPml-api.js?svn=179:1
==session event = m_stream_video_remote_added SIPml-api.js?svn=179:1
==session event = m_stream_audio_local_added SIPml-api.js?svn=179:1
==session event = m_stream_audio_remote_added SIPml-api.js?svn=179:1
I have attached the JS console logs(case1_web2SIPClient_JSLogs.txt), wireshark trace(case1_web2SIPClient_WStrace.pcap) , webrtc2sip gateway console logs(case1_web2SIPClient_gatewayLogs.txt), sipml5 expert settings (Expert_settings.png) and config.xml (config.xml) for this case. I did not change anything in the config.xml that was generated after i built the source as mentioned in the instructions of this page (http://linux.autostatic.com/installing-webrtc2sip-on-ubuntu-1204).
I gave a try making calls between chrome and a android SIP client (CSipSimple) and the problem remains the same.
==================================================================================
case 2: SIP client calling chrome.
Result: as soon as I click answer button on chrome, the calls gets rejected.
==================================================================================
The JS console logs states that:
State machine: tsip_transac_ist_Proceeding_2_Completed_X_300_to_699 SIPml-api.js?svn=179:1
SEND: SIP/2.0 603 Failed to get local SDP
Via: SIP/2.0/WS 172.21.128.118:10060;rport=10060;branch=z9hG4bK-1441398960
From: <sip:tata#172.21.229.127>;tag=300647977
To: <sip:amshyam320#sip2sip.info>;tag=ZxQFfM7fIIP3rT1HINzb
Call-ID: fbdf5a11-ff9e-0072-fa8b-09525220cec6
CSeq: 1670757835 INVITE
Content-Length: 0
Reason: SIP; cause=603; text="Failed to get local SDP"
For this case I am attaching JS logs(case2_SIPClient2WebJSLogs.txt), wireshark dump(case2_jitsiToWeb_WStrace.pcap)
Configuration:
Chrome Version: checked on 30.0.1599.114 and even on Latest chrome version
Webrtc2sip version: 2.6.0
sipml5 Version: svn=203
ubuntu version: 12.04 (checked on both desktop and server editions)
Am I missing something in my setup or configuration please guide and help in moving further.
Thanks,
Shyam
Case2:
You're using RTCWeb-capable browser(Chrome) and trying to call a SIP client which may not be implementing some mandatory features like ICE,SRTP. Chrome uses SRTP-SDES and Firefox uses SRTP-DTLS.
Enable RTCWeb Breaker in sipml5 expert settings and check.
The RTCWeb Breaker is used to enable audio and video transcoding when the endpoints do not support the same codecs or the remote server is not RTCWeb-compliant.
Case:1:
Is audio working? and I can't see your logs.
I am launching chrome browser using
selenium = new DefaultSelenium("localhost", 4444, "*googlechrome",
"https://example.com/");
But i get a popup with following message and it freezes:
An administrator has installed Google Chrome on this system, and it is available for all users. The system-level Google Chrome will replace your user-level installation now.
Console Log till point of freeze:
Server started
16:06:37.792 INFO - Command request: getNewBrowserSession[*googlechrome, https://example.com/, ] on session null
16:06:37.796 INFO - creating new remote session
16:06:38.081 INFO - Allocated session beb925cd0418412dbe6319fedfb28614 for https://example.com/, launching...
16:06:38.082 INFO - Launching Google Chrome...
Any suggestions?
Try giving location of your chrome exe too along with browser name like this :
selenium=new DefaultSelenium("localhost", 4444, "*googlechrome C:\\Program Files\\Google\\Chrome\\Application\\chrome.exe", "https://example.com");