No relay (TURN) candidate in SDP with iOS when being connected in LTE/4G

See attached file for log (with an Android comparison)sdpios-andoid.log

To reproduce: Be connected on LTE/4G, make a call.

btw, why all the addresses are twice as candidate?

changed milestone to %Next major release

cause it's for media so, you're negotiating 4 links

Ok, I diggued a little and I saw 2 problems:

1. daemon's code is bugguy. This should be fixed by: https://review.jami.net/c/ring-daemon/+/15540
2. Something is wrong with our coturn instances and I need more digging for this. The allocation request is correct

[0m[22;36m[1599580626.820|0x16b6cb000|manager.cpp       :248  ] [0m11:57:06.820      tcprel0x112013600  ..TX 116 bytes STUN message to [2607:5300:201:3000::29cc]:3478:\
--- begin STUN message ---\
STUN Allocate request\
 Hdr: length=96, magic=2112a442, tsx_id=0000027d2592b43238e042cb\
 Attributes:\
  REQUESTED-TRANSPORT: length=4, value=100663296 (0x6000000)\
  REQUESTED-ADDRESS-FAMILY: length=4, value=33554432 (0x2000000)\
  SOFTWARE: length=13, value="pjnath-2.10.0"\
  USERNAME: length=4, value="ring"\
  REALM: length=4, value="ring"\
  NONCE: length=16, value="6409a6b5f2c80355"\
  MESSAGE-INTEGRITY: length=20, data=ecefb4f6af2c56211dffff2f86530f567874ab0b\
--- end of STUN message ---\

And try to ask an IPv4 address to perform ipv4->ipv6 translation, however the request is rejected:

[0m[22;36m[1599580626.876|0x16b6cb000|manager.cpp       :248  ] [0m11:57:06.876      tcprel0x112013600 !.RX 112 bytes STUN message from [2607:5300:201:3000::29cc]:3478:\
--- begin STUN message ---\
STUN Allocate error response\
 Hdr: length=92, magic=2112a442, tsx_id=0000027d2592b43238e042cb\
 Attributes:\
  ERROR-CODE: length=32, err_code=440, reason="Unsupported address family"\
  SOFTWARE: length=26, value="Coturn-4.5.0.3 'dan Eider'"\
  MESSAGE-INTEGRITY: length=20, data=1e382e3e5b8a5fd50347cd6b73c19f5e9270fe3e\
--- end of STUN message ---\

And this can be related to https://github.com/coturn/coturn/issues/154

mentioned in commit 6ce8a7ce

To conclude:

1. For the daemon, our work is done because the commit is merged
2. For the infra part, the ticket is opened and will be closed as soon as the turn got the new config
3. For ipv6->ipv4 support, this will need some work but related to another issue

To be fully functional, we need a new ios release + changes in TURN's conf, after that I will close the ticket

Ok, so some news:

1. Our infra is ok now, and candidate are correctly added
2. However I needed to revert the patch, this cause issues in pjsip when using a network without IPv6. Currently investigating with them. So now we need to wait this
3. Maybe will try something today for this ipv6->ipv4 bridge

Update we removed the modification on TURN servers due to certainly some connectivity issues

So the process will be:

1. Fix pjsip
2. Merge my patch in daemon + pjsip
3. Fix coturn config

mentioned in issue #309 (closed)

added connectivity label

mentioned in epic &22

added to epic &22

removed milestone %Next major release

changed milestone to %Backlog

changed title from No relay (Turn) candidate in SDP with IOS when being connected in LTE/4G to No relay (TURN) candidate in SDP with iOS when being connected in LTE/4G

changed title from No relay (TURN) candidate in SDP with iOS when being connected in LTE/4G to No relay (TURN) candidate in SDP with iOS when being connected in LTE/4G