SlackingVeteran
commented
6 years ago Error logs when LTE with IPV6: https://gist.github.com/suyashbhatt/cfb69328cd4229cc968e212351b7ea06
My suspect from the logs is that ipv6 address are being messed up with square brackets.
for example in line 140 of error log Via: SIP/2.0/TCP [fe80::3ea3:13e7:928d:857d]:5090;rport ipv6 address is enclosed in brackets and again in line 143 ipaddress and the port are enclosed in brackets like this: Contact: <sip:[fe80::3ea3:13e7:928d:857d:5090];transport=tcp;registering_acc=my-cool-domain.com>. With the port 5090 inside brackets, the sip address is invalid. I am doing some more research into this but if anyone could provide some info on where root of the cause could be, than that would help me address this issue
Update: I finally managed to get it working, had to brainstorm on how SIP is trying to communicate with RC server in first place.
I had to go back and forth by testing lots of thing. First thing was to understand how sip was sending request to RC. when wifi is connected phone/pc has 2 ip addresses, 1 is local and another is global (which remote computers can see or when you check your ip in any ipaddress checking website). when sip is sending request, this is what it sends when connected to wifi:
Sending SIP request:
REGISTER sip:envoychat.com:5080 SIP/2.0
Call-ID: 86b33fd068696cbfaaaef4902507b00c@10.0.0.67
CSeq: 1 REGISTER
From: "alice" <sip:alice@envoychat.com>;tag=1517349930988
To: "alice" <sip:alice@envoychat.com>
Via: SIP/2.0/TCP 10.0.0.67:5090;rport
Max-Forwards: 70
Route: <sip:165.227.90.178:5080;dns_route=true;transport=tcp;lr>
Contact: <sip:10.0.0.67:5090;transport=tcp;registering_acc=envoychat.com>
User-Agent: TelScale Restcomm Android Client UNOFFICIAL#1
Expires: 3600
Content-Length: 0In above example Contact is sip:10.0.0.67:5090 where 10.0.0.67 is ipaddress within my wifi network. Now in case of Cellular data devices have lot of interfaces, in my example I had rmnet-data0, rmnet-data1, rmnet-data2, rmnet-data3, rmnet-data4, rmnet-data5, rmnet-data6, rmnet-data7 and v4-rmnet-data0. But the active interface was rmnet-data0 which had 2 inet6 address (Network carrier were forcing the use of ipv6 address). One of the address being global scope ip and another being link scope. Link scope address is valid only on that device so it did not work as expected when ipv6 was allowed in sdk. Since there is no local ipv6 while in cellular network, I had to use ipv4 of local scope. now the interface I used was v4-rmnet-data0 and regex used in JainSipClient does not cover it. I have done all the possible tests I could on multiple phones and emulators and everything seems to work perfectly. I will post a pull-request with the fix soon..
atsakiridis
jaimecasero
gsaslis
RC android sdk is working great under wifi network but does not seem to support LTE network. Probably because of IPV6 in LTE? If current network is wifi it does not care if ipaddress is ipv6 or ipv4 it returns the address in either of the cases but if current network is cellular then RC connects only when on IPV4.
@atsakiridis you were helping out in issue #633 It seems to be same issue. I remember you mentioning that webrtc for media and JAIN SIP for signalling both supports ipv6, has this been tested yet? its been a long time since #633 was posted just wondering if any contributors has update on it. I am about to give ipv6 a try by myself as well just to see if everything works as expected.