# LinkAdrReq how to get join response with channel config? **URL:** \ **Category:** End Devices (Nodes)\ **Created:** [May 24, 2019, 7:54pm UTC](https://www.thethingsnetwork.org/forum/t/linkadrreq-how-to-get-join-response-with-channel-config/26442 "2019-05-24T19:54:10Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![arjanvanb](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/arjanvanb/32/46626_2.png) [@arjanvanb](https://www.thethingsnetwork.org/forum/u/arjanvanb)\ **Post date:** [June 15, 2019, 9:53am UTC](https://www.thethingsnetwork.org/forum/t/linkadrreq-how-to-get-join-response-with-channel-config/26442/4 "2019-06-15T09:53:26Z")
> [@disk91](#): > > I get the ADR message only during the next communication and not during Join Procedure That makes sense: this really is a workaround for the flaw in the 1.0.2 specifications that for US915 do not include the CFList with network settings in the Join Accept. A Join Accept message [does not have the option to include additional MAC commands](https://lora-alliance.org/sites/default/files/2018-05/lorawan1_0_2-20161012_1398_1.pdf#page=34), so an additional downlink is needed, which can only be sent after receiving another uplink: > ![1.0.2 Join Accept](https://www.thethingsnetwork.org/forum/uploads/default/original/3X/3/8/38857dff09f6581a87c3bf4d1b00f81fe6ac6665.png) As for the first revision of your post in which you thought the actual ADR message was not okay: if you still have doubts then see an example for AU915 in [LMIC Library Always Does Unwanted Downlink - #10 by arjanvanb](https://www.thethingsnetwork.org/forum/t/lmic-library-always-does-unwanted-downlink/21293/10) and for EU868 in [ADR problems - node of the same type have different ADR behaviour - #11 by arjanvanb](https://www.thethingsnetwork.org/forum/t/adr-problems-node-of-the-same-type-have-different-adr-behaviour/22825/11). --- _[View the full topic](https://www.thethingsnetwork.org/forum/t/linkadrreq-how-to-get-join-response-with-channel-config/26442)._