Last week, our forum was buzzing with engaging discussions ranging from technical challenges to process improvements. Members shared insights on reducing repeat customer calls after outages, and there was a lively debate on the implications of “deprioritized” on unlimited data plans. Technical anecdotes, such as a coffee machine accidentally prioritized in a QoS setup, also sparked interest. Meanwhile, an intriguing issue about a teleporting asset tag captured the community’s curiosity.
This Week’s Hot Topics
When asset tag 04137 learned to teleport
This quirky incident has everyone scratching their heads and discussing the implications of asset tracking anomalies in telecom environments. Read more here
Cutting repeat calls after outages
Members are exchanging strategies on how to minimize follow-up calls after service outages, a common pain point for telecom operators. Read more here
Windy swap at 220 feet today
This thread highlights the challenges faced by field techs performing equipment swaps in high places under adverse weather conditions. Read more here
The immortal “temporary” firewall rule
The community is discussing best practices for managing firewall rules that tend to overstay their welcome. Read more here
When ‘seamless’ meets the change window
Here, the focus is on navigating the tricky balance between seamless operations and scheduled change windows. Read more here
What belongs in a pre-launch audit trail
Join the conversation on essential elements that should be in every pre-launch checklist to ensure accountability and thoroughness. Read more here
QoS gave my coffee machine priority
An amusing yet educational thread on how QoS settings can inadvertently prioritize non-essential devices, sparking a discussion on network management. Read more here
What ‘deprioritized’ really means on unlimited plans
A thought-provoking discussion on how “unlimited” plans are marketed versus their actual performance during network congestion. Read more here
Looking forward to another week of engaging discussions. Keep sharing your experiences and insights.
We cut repeat calls after outages by texting customers every 30 minutes with the current ETR and a link to https://status.example.com, plus a short ‘all clear’ at restore. It works, but we had to dial back to 30–60 min intervals and add opt-out so phones don’t turn into slot machines.
But had a ‘teleporting’ BLE asset tag last quarter too — turned out two APs were feeding the same location group and the smoothing/Kalman filter was off, so the tag kept jumping buildings (). We fixed it by adding a -65 dBm RSSI floor and a 10-second dwell before position updates; small downside is first-move latency, but it stopped the ghost jumps.