Changes

==Overview==

==Overview==

All mobile carrier cells are assigned a unique ID, which is broadcasted to all connected devices. It is usually irrelevant information for the end user, as cell switching on mobile phones and routers has become very good. But sometimes in remote areas, it is beneficial to lock the LTE router to a single cell, as automatic mode may choose a cell with fewer or slower bands, as it only really looks for the best signal. For now, only devices with Quectel modems support this feature.

All mobile carrier cells are assigned a unique ID, which is broadcasted to all connected devices. It is usually irrelevant information for the end user, as cell switching on mobile phones and routers has become very good. But sometimes in '''remote areas''', it is beneficial to lock the LTE router to a single cell, as automatic mode may choose a cell with fewer or slower bands, as it only really looks for the '''best signal'''. '''For now, only devices with Quectel modems support this feature'''.

==Finding the modem manufacturer==

==Finding the modem manufacturer==

In your [[RUTX_Routers]] WebUI, go to "Status" -> "System" page. Under the "Modem" section, you'll see the "Model" row. If the model starts with EG, RG, EC, and '''not SLM''', this feature should work. However to make sure it's supported, command '''''gsmctl -A 'AT+QNWLOCK=?'''''' should not return '''ERROR''', when ran via [[Command_Line_Interfaces_RutOS#SSH|SSH]] or [[Command_Line_Interfaces_RutOS#CLI_.28WebUI.29|CLI]]. The response should look something like this:<br>

In your [[RUTX_Routers]] WebUI, go to '''Status → System''' page. Under the '''Modem''' section, you'll see the '''Model''' row.

If the model starts with '''EG, RG, EC''', and '''not SLM or RG (5G not supported yet)''', this feature should work. However to make sure it's supported, command '''''gsmctl -A 'AT+QNWLOCK=?'''''' should not return '''ERROR''', when ran via [[Command_Line_Interfaces_RutOS#SSH|SSH]] or [[Command_Line_Interfaces_RutOS#CLI_.28WebUI.29|CLI]]. The response should look something like this:<br>

[[File:Networking_Quectel_configuration_locking_cellids_on_devices_with_quectel_modems_checking_compatibility_v2.PNG|border|class=tlt-border]]

[[File:Networking_Quectel_configuration_locking_cellids_on_devices_with_quectel_modems_checking_compatibility_v2.PNG|border|class=tlt-border]]

==When to use cell locking==

==When to use cell locking==

Let's say you're setting up RUTX14, which supports up to 3CA (Carrier aggregation) and you have two cell towers within a similar distance. Let's say Cell A transmits on bands 1, 7, and 20, while Cell B transmits on bands 3 and 20.

Let's say you're setting up RUTX14, which supports '''Carrier Aggregation''' of up to 3 bands, and you have two cell towers within a similar distance. Let's say Cell A transmits on bands 1, 7, and 20, while Cell B transmits on bands 3 and 20.

Since the signal from Cell B is a little stronger, the router will connect to two bands, and the bandwidth will be lower than using three bands. This means much lower speeds and reduced throughput.

Since the signal from Cell B is a little stronger, the router will connect to two bands, and the bandwidth will be lower than using three bands. This means much lower speeds and reduced throughput.

If we lock the router into only using Cell A, we might get a little worse signal, but much better speeds due to using 3 bands at the same time.

If we lock the router into only using Cell A, we might get a little worse signal, but much better speeds due to using 3 bands at the same time.