On a hotspot connected to BM, the last TG keyed up is set to "auto-static" if no static TGs are set in selfcare or via the BM API in pi-star (for example). That TG will persist if no others are keyed up or if no changes are made via selfcare.VK3KYY wrote: ↑Fri Jan 03, 2020 7:18 amOn BM with a Simplex Hotspot, the default seems to be an infinite time-out on the TG assigned by transmitting on that TG.kd2lh wrote: ↑Fri Jan 03, 2020 3:23 amWhen the hotspot is operating dynamically, and it receives incoming RF for a given talkgroup, that talkgroup will continue to be forwarded by the VOIP infrastructure to the hotspot through the conversation and not reset until there is no local RF activity on that talkgroup for a timeout period.
However with a Duplex Hotspot (on BM) there is a definite time-out period, but I don't know what the default value is.
IMHO. The BM dynamically allocated route system on Simplex Hotspots is somewhat buggy, as if you change TG and transmit for a second or two, the dynamic route will appear to have change, and you can sometime even transmit an over of 30 seconds or more, only to find that in the next minute, the dynamically allocated TG reverts back to the TG prior to the TG you are currently on.
This bug/feature causes a lot of confusion on BM.
Even using the BM Selfcare dashboard to remove a dynamically allocated TG, e.g. TG91, its very common for that dynamic route to be reactivated within 30 seconds, and you end up hearing the traffic on TG 91 again.
And it can take multiple attempts of removing the TG91 dynamic route from the Selfcare dashboard before it finally stops routing that traffic to your Hotspot.
Also. On the BM Selfcare dashboard, if you roll over the dynamic route with your mouse, it shows a message saying that transmitting on TG4000 will remove the dynamic route. However this has never worked for me.
If a second TG is then keyed up, that second TG becomes the auto-static TG, but the previous TG is now dynamic with a 15 minute time out. If traffic comes in over that previous TG, the 15 minute timer is reset, I think. But here is the thing that complicates it that most people do not know: there is a 5 minute "hold-off timer" on the first TG (set by the master server) such that when the second TG is keyed up, the first TG is silenced for 5 minutes, after which time it can receive traffic again. That is the part that confuses most people.
Because of these BM features, I usually advise people with simplex hotspots to *not* set any static TGs and just use the auto-static feature and disconnect. With duplex hotspots however, it makes sense to set static TGs on each TS if you like. Then using digital monitor/promiscuous mode, it is easy to monitor multiple TGs across timeslots. This is something that you cannot easily do on a simplex hotspot.