Intel® Collaboration Suite for WebRTC
Community support and discussions on the Intel® Collaboration Suite for WebRTC (Intel® CS for WebRTC).

In Android lte network, connection fails.

tangk
Beginner
758 Views

My testing environment.

mcu: 4.2

iPhone: Success

Android: Fail

 

It works well on wifi networks in Android. However, the connection fails in the lte network.

(I think it's an ipv6 problem.)

Below is the Android log.

2019-07-23 17:19:35.743 13017-13017/com.saeha.ezview.dev E/aeha.ezview.de: No package ID ff found for ID 0xffffffff.
2019-07-23 17:19:35.793 13017-13395/com.saeha.ezview.dev D/OWT: create offer
2019-07-23 17:19:35.802 13017-13375/com.saeha.ezview.dev I/org.webrtc.Logging: Camera1Session: Available fps ranges: [[15.0:15.0], [24.0:24.0], [15.0:30.0], [30.0:30.0]]
2019-07-23 17:19:35.810 13017-13320/com.saeha.ezview.dev I/org.webrtc.Logging: NetworkMonitor: Start monitoring with native observer 529227329088
2019-07-23 17:19:35.818 13017-13320/com.saeha.ezview.dev D/ConnectivityManager: sendRequestForNetwork CallingUid : 10375, CallingPid : 13017
2019-07-23 17:19:35.819 13017-13320/com.saeha.ezview.dev D/ConnectivityManager: requestNetwork; CallingUid : 10375, CallingPid : 13017
2019-07-23 17:19:35.820 13017-13375/com.saeha.ezview.dev I/org.webrtc.Logging: Camera1Session: Create new camera1 session on camera 1
2019-07-23 17:19:35.820 13017-13375/com.saeha.ezview.dev I/org.webrtc.Logging: Camera1Session: Start capturing
2019-07-23 17:19:35.821 13017-13320/com.saeha.ezview.dev D/ConnectivityManager: requestNetwork; CallingUid : 10375, CallingPid : 13017
2019-07-23 17:19:35.834 13017-13320/com.saeha.ezview.dev W/org.webrtc.Logging: NetworkMonitorAutoDetect: Null interface name for network 601
2019-07-23 17:19:35.835 13017-13399/com.saeha.ezview.dev I/org.webrtc.Logging: NetworkMonitorAutoDetect: Network becomes available: 641
2019-07-23 17:19:35.844 13017-13399/com.saeha.ezview.dev I/org.webrtc.Logging: NetworkMonitorAutoDetect: capabilities changed: [ Transports: CELLULAR Capabilities: SUPL&INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN&VALIDATED&NOT_ROAMING&FOREGROUND&NOT_CONGESTED&NOT_SUSPENDED Unwanted:  LinkUpBandwidth>=51200Kbps LinkDnBandwidth>=102400Kbps Specifier: <1>]
2019-07-23 17:19:35.854 13017-13399/com.saeha.ezview.dev I/org.webrtc.Logging: NetworkMonitorAutoDetect: link properties changed: {InterfaceName: rmnet1 LinkAddresses: [2001:2d8:e132:5a82::16e4:40b1/64,]  Routes: [::/0 -> fe80::3 rmnet1,2001:2d8:e132:5a82::/64 -> :: rmnet1,] DnsAddresses: [fd00:613:101:c::10,fd00:e13:101:c::7,] UsePrivateDns: false PrivateDnsServerName: null Domains: null MTU: 1440 TcpBufferSizes: 2097152,4194304,8388608,1048576,3145728,4194304 Stacked: [ [{InterfaceName: v4-rmnet1 LinkAddresses: [192.0.0.5/32,]  Routes: [0.0.0.0/0 -> 192.0.0.5 v4-rmnet1,] DnsAddresses: [] UsePrivateDns: false PrivateDnsServerName: null Domains: null MTU: 0} ],] }
2019-07-23 17:19:35.859 13017-13017/com.saeha.ezview.dev E/aeha.ezview.de: No package ID ff found for ID 0xffffffff.
2019-07-23 17:19:36.093 13017-13017/com.saeha.ezview.dev E/aeha.ezview.de: No package ID ff found for ID 0xffffffff.
2019-07-23 17:19:36.169 13017-13375/com.saeha.ezview.dev I/org.webrtc.Logging: CameraCapturer: Create session done. Switch state: IDLE
2019-07-23 17:19:36.172 13017-13375/com.saeha.ezview.dev I/org.webrtc.Logging: SurfaceTextureHelper: Setting listener to org.webrtc.-$$Lambda$Camera1Session$IaCl5v4xeWNI0BnOxdpBB-kXaIc@c31a10
2019-07-23 17:19:36.260 13017-13416/com.saeha.ezview.dev I/org.webrtc.Logging: HardwareVideoEncoder: initEncode: 320 x 240. @ 300kbps. Fps: 60 Use surface mode: true
2019-07-23 17:19:36.269 13017-13416/com.saeha.ezview.dev I/ACodec:  [] Now uninitialized
2019-07-23 17:19:36.273 13017-13456/com.saeha.ezview.dev I/ACodec: [] onAllocateComponent
2019-07-23 17:19:36.282 13017-13456/com.saeha.ezview.dev I/OMXClient: IOmx service obtained
2019-07-23 17:19:36.348 13017-13456/com.saeha.ezview.dev I/ACodec: [OMX.Exynos.AVC.Encoder] Now Loaded

0 Kudos
2 Replies
YanbinZ_Intel
Employee
758 Views
Do you means this issue was found in IPv6 environment ? Could you please provide detail reproduce steps included detail test environment setup steps.
0 Kudos
tangk
Beginner
758 Views

The test phone is Android and can not be connected only in sk telecom lte environment of Korea. It works fine in the lte environment of the other carriers kt and lg. Also, sk lte works well in iOS environment. If you need more than the attached log, please ask.

0 Kudos
Reply