# Multi-tech conduit OTAA joinRequest is ok, but joinAccept not received by node

**URL:** <https://www.thethingsnetwork.org/forum/t/multi-tech-conduit-otaa-joinrequest-is-ok-but-joinaccept-not-received-by-node/2318>\
**Category:** MultiTech Gateways\
**Created:** [May 31, 2016, 10:43pm UTC](https://www.thethingsnetwork.org/forum/t/multi-tech-conduit-otaa-joinrequest-is-ok-but-joinaccept-not-received-by-node/2318 "2016-05-31T22:43:35Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [June 1, 2016, 5:39am UTC](https://www.thethingsnetwork.org/forum/t/multi-tech-conduit-otaa-joinrequest-is-ok-but-joinaccept-not-received-by-node/2318/2 "2016-06-01T05:39:23Z")

</div>

> [@jverhoeven](#):
>
> 1. The Radio frequencies listed in the poly-packet-fwd are different from the ones used in the basic pkt forwarder. Why is that? What is correct?

The frequencies for the poly forwarder are the TTN frequency plan. Those are correct when using TTN backend.

[quote=“jverhoeven, post:1, topic:2318”]2. The second radio channel has value ‘tx\_enable’ set to false. No such value exists in the basic pkt forwarder. Given the fact that I am not receiving downlink messages, including the joinAccept message could this have something to to with it since I am getting my joinAccept message delivered at 869.525 Mhz, i.e. not the joinRequest frequency, so my guess the second radio.  
[/quote]

You might need to set the frequency and spread factor for receive window 2. Quoting from a message by one of the members of the core team:

> [@Over-the-air-activation OTAA with LMIC](https://www.thethingsnetwork.org/forum/t/over-the-air-activation-otaa-with-lmic/1921/23):
>
> The reason for missing some join (accepts) is probably because the TTN backend can respond in the RX2 window and then uses data rate SF9. This is not compliant, and I just opened an issue for it. Before the join, the backend should respond with the LoRaWAN default values (=SF12 for RX2), and then it can change from the defaults by setting the new configuration parameters in the join accept message. After the join accept, it can then use the TTN values (=SF9 for RX2).

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/multi-tech-conduit-otaa-joinrequest-is-ok-but-joinaccept-not-received-by-node/2318)._
