Understanding how Rx2 frequencies are established (trying to use AS923 instead of AU915 in Australia)

[arjanvanb (Arjan)]

Ah, my bad, I thought you were switching between AS920-923 and AS923-925. But AU915 is indeed using quite different RX2 (and RX1) settings. So:

@tuftec

For AU915 the response should only go out on 923.3.

No; the link I provided earlier states for AU915:

Downlink:

1. 923.3 - SF7BW500 to SF12BW500
2. 923.9 - SF7BW500 to SF12BW500
3. 924.5 - SF7BW500 to SF12BW500
4. 925.1 - SF7BW500 to SF12BW500
5. 925.7 - SF7BW500 to SF12BW500
6. 926.3 - SF7BW500 to SF12BW500
7. 926.9 - SF7BW500 to SF12BW500
8. 927.5 - SF7BW500 to SF12BW500

So, it seems there is no difference for RX1 and RX2.

Also, without knowing what type of gateway you’re using, the following might not apply. But it does not make sense that your gateway needs to know the RX1 and RX2 frequencies:

@kersing

The frequency for downlink data is specified by the back-end in the data packet to the gateway. There is no configuration parameter on the gateway for this.

Of course, that only applies to the frequencies used for RX1 and RX2 transmissions. To listen to the right frequencies, the gateway config should indeed be changed. And I guess you’re right that the backend router URL also determines what RX1 or RX2 is assumed by the backend; see https://www.thethingsnetwork.org/wiki/Backend/Connect/Gateway

And as an aside, “authorisation response” is called an OTAA Join Accept downlink.