# OTAA ok, 12h later I get denied, reboot gateway --\> OK again ...!?

**URL:** <https://www.thethingsnetwork.org/forum/t/otaa-ok-12h-later-i-get-denied-reboot-gateway-ok-again/2025>\
**Category:** End Devices (Nodes)\
**Created:** [May 3, 2016, 3:17pm UTC](https://www.thethingsnetwork.org/forum/t/otaa-ok-12h-later-i-get-denied-reboot-gateway-ok-again/2025 "2016-05-03T15:17:35Z")\
**Posts on this page:** 1\
**Showing post:** 32

<div class="post-metadata">

**Author:** ![kersing](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/kersing/32/44777_2.png) [@kersing](https://www.thethingsnetwork.org/forum/u/kersing)\
**Post date:** [January 24, 2017, 6:07pm UTC](https://www.thethingsnetwork.org/forum/t/otaa-ok-12h-later-i-get-denied-reboot-gateway-ok-again/2025/32 "2017-01-24T18:07:33Z")

</div>

> [@salvatore\_forte](#):
>
> the two pictures above are referred to an unsuccessful join attempt!

Ok, looked at the screenshots again, the issue you are having is timing related. The packet at 11:49:26.3… should have been sent by the gateway exactly 5 seconds after the packet of 11:49:20.8 arrived. The time between the sending the first and receiving the second packet exceeds 5 seconds so the gateway receives the data after it should have been transmitted. As a result the node will never receive the data at the time it expects it and the join fails.

Looking at the ‘PULL\_ACK’ lines in the second screen shot I notice the turn around times vary wildly and are rather large. For my gateways the results are 20-40ms, your results are 240-882ms. The lower value might work, the high value is too large.

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/otaa-ok-12h-later-i-get-denied-reboot-gateway-ok-again/2025)._
