Attention is currently required from: osmith, fixeria.
3 comments:
Commit Message:
it is fine for the BTS to ACK
the RSL CONNECT despite later on failing to connect the RSL link
> RSL_CONNECT is really just setting the attributes ... and connect happens later on […]
We discussed this intenrally with @fixeria.
I tested again and I confirm that nanoBTS doesn't attempt TCP connecting until it is sent the OPSTART command for the BBTRANSC object from the BSC.
Hence, IP address in RSL CONNECT message is not really tested because no TCP socket is created, and 0.0.0.0 is considered to be "use same remote address as per OML link) which is inherently valid since the OML link is up.
I also just checked: nanoBTS sends OPSTART ACK even before sending the TCP SYN to port 3003 (RSL), so yeah, it ACKs and then attempts creating the RSL socket, as I expected.
The real knowledge that the nanoBTS is prepared comes from the fact that it sends a StateChng Report to EnabledOk once it has a successful connect on the TCP/IPA/RSL link. That happens after the IPA handshake is successful apparently.
Patch Set #2, Line 23: Change-Id: I10df611f0086d34a5482f7c8a79703938313ab3d
Related: OS#5964
Ack
Patchset:
(not resolved)
ACK, I'll move the test to the end.
To view, visit change 32269. To unsubscribe, or for help writing mail filters, visit settings.