Connectivity issues on native iOS app with some mobile providers

1,312 views
Skip to first unread message

Al Johensson

unread,
Nov 30, 2017, 11:46:55 AM11/30/17
to discuss-webrtc
Hi,
I am seeing connectivity problems with our iOS app. Our configuration: One app (sender, IPad device) is using hotspot from a mobile device for network connectivity, the second device (receiver, another IPad) is using wifi.  We are noticing that with certain telecom providers (not all) we cannot establish connection at all. We are noticing on the receiver side that UDP sends of 96 bytes repeatedly failing with error 65 (host unreachable) or occasionally  with 64 (host down). and after some 40 attempts connection is torn down. The first thing i notice is that the answer it receives has following options set

a=ice-options:trickle renomination


ow then we see following messages repeatedly while the IceConnection state is stuck at RTCIceConnectionStateChecking:


stunport.cc:279): Jingle:Port[0x122a2b200:audio:1:0:local:Net[en2:169.254.0.x/16:Wifi]]: UDP send of 96 bytes failed with error 64

(port.cc:995): Jingle:Conn[0x12203a000:audio:bWN24xyF:1:0:local:udp:169.254.72.x:59624->OP48hdAD:1:2122194687:local:udp:169.254.3.x:57236|C--I|0|0|9114756780654345726|-]: Failed to send STUN ping  err=-1 id=4f344f68416f6f7431775564

(port.cc:1459): Jingle:Conn[0x12203a000:audio:bWN24xyF:1:0:local:udp:169.254.72.x:59624->OP48hdAD:1:2122194687:local:udp:169.254.3.x:57236|C--I|0|0|9114756780654345726|-]: Sent STUN ping, id=4f344f68416f6f7431775564, use_candidate=0, nomination=0

(port.cc:1459): Jingle:Conn[0x1221a8400:audio:jWs3ia5e:1:0:local:udp:192.168.0.x:53563->8/HD77aF:1:1686052607:stun:udp:46.125.250.x:56753|C--I|0|0|7241540810645061119|-]: Sent STUN ping, id=2b75506f53314a3969535044, use_candidate=0, nomination=0

(port.cc:1236): Jingle:Conn[0x12204a800:audio:jWs3ia5e:1:0:local:udp:192.168.0.x:53563->XQSTInrG:1:2122260223:local:udp:192.168.43.x:63475|C--I|0|0|9115038255631187454|-]: Timed out after 15054 ms without a response, rtt=6000


and then connection is closed:


(p2ptransportchannel.cc:1472): Jingle:Channel[audio|1|__]: Transport channel state changed from 1 to 2

(transportcontroller.cc:835): audio TransportChannel 1 state changed. Check if state is complete.

(port.cc:1505): Connection deleted with number of pings sent: 37

(p2ptransportchannel.cc:1890): Jingle:Channel[audio|1|__]: Removed connection 0x122863600 (2 remaining)


(stunport.cc:88): Binding request timed out from 169.254.72.x:59624 (en2)(tcpport.cc:453): Jingle:Conn[0x122167200:audio:W58Dzq3L:1:0:local:tcp:192.168.0.x:57855->pU8JKImU:1:1518280447:local:tcp:192.168.43.x:56190|---W|0|0|6520964869057822206|-]: Connection closed with error 60

(tcpport.cc:453): Jingle:Conn[0x122979200:audio:dFur3hIF:1:0:local:tcp:169.254.72.x:57856->BRWYwQ+I:1:1518214911:local:tcp:169.254.3.x:56193|---W|0|0|6520683394080980478|-]: Connection closed with error 60


At this point ice connection state transitions to RTCIceConnectionStateFailed. I don't know how to debug it further. Anyone has any suggestions ? The issue only shows up between two native ios apps. If we use web apprtc app on the receiver side instead of native app, everything works fine. I can provide more logs we need be.


Thanks,

AJ



Philipp Hancke

unread,
Nov 30, 2017, 11:59:59 AM11/30/17
to WebRTC-discuss
have you configured a TURN server? If it works with apprtc in the browser and apprtcdemo on mobile check whether the active connection is using a turn server as described in https://testrtc.com/find-webrtc-active-connection/

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrtc+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/154b7c4a-fd6b-46ae-b085-891f25519ad4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Fred CC

unread,
Jan 5, 2018, 4:04:23 AM1/5/18
to discuss-webrtc
The reason of this issue is IOS 11.x added a reserve ip address 169.254.0.x
Filter the ip in network.cc   ::IsIgnordNetwork
Reply all
Reply to author
Forward
0 new messages