# ADR Downlink After OTAA Join

**URL:** <https://www.thethingsnetwork.org/forum/t/adr-downlink-after-otaa-join/13477>\
**Category:** v2 Backend\
**Created:** [April 20, 2018, 8:29am UTC](https://www.thethingsnetwork.org/forum/t/adr-downlink-after-otaa-join/13477 "2018-04-20T08:29:38Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**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:** [April 20, 2018, 9:40am UTC](https://www.thethingsnetwork.org/forum/t/adr-downlink-after-otaa-join/13477/2 "2018-04-20T09:40:29Z")

</div>

If scheduling a downlink works, then sending the first uplink as a _confirmed_ uplink might work as well?

I assume you’re using EU863-870? What you want seems to be implemented for US902-928, then shown as “initial” in the Trace part of the gateway Traffic page in TTN Console:

> <https://github.com/TheThingsNetwork/ttn/blob/v2.9.2/core/networkserver/adr.go#L90-L96>

Related: [Does ADR require the use of confirmed uplinks?](https://www.thethingsnetwork.org/forum/t/does-adr-require-the-use-of-confirmed-uplinks/9640/6), [ADR is not working (nucleo - raspberry -italy)](https://www.thethingsnetwork.org/forum/t/adr-is-not-working-nucleo-raspberry-italy/10078/3) and:

> <https://github.com/TheThingsNetwork/ttn/issues/477>

(Update: I removed some unrelated things, which did not apply to this very use case.)

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/adr-downlink-after-otaa-join/13477)._