anthturner
commented
7 years ago SMS, exposed bidirectionally, as close to send-time as possible
⚠️ This is exposed via sendSMSMessage(imsi, messageText) to send and the onSMSReceived event to receive, but doesn't get sent to the controller (and similarly can't accept messages from the controller to be sent to the handset)
MCC/MNC/LAC/TAC for network identification changes
⚠️ PLMN changes are done and functional but not linked with the Javascript (as far as I know) or integrated with the controller. We need to finish this end-to-end as soon as possible since the primary use case from our customer seems to be that they would have PLMN information up-front.
Band selection (optionally pre-seeded with preferable bands from CellMapper or similar)
✅ Band selection is done in the config and I don't think we need to change this, since PLMN changes can happen live and these are more "regional" settings anyways
IMSI whitelisting & blacklisting features
❓ Access control is currently done through sar.conf. We should talk with our customer on how they intend to run missions with this to see if doing all this ACL work up-front is realistic. At the very least, if we leave it here, we need to add a startup task that runs dos2unix on the sar.conf file to fix any inconsistencies
One-touch "debug" mode to throw the BTS into a non-US configuration for testing without absorbing nearby phones
✅ Done through sar.conf, and I don't think there's a good reason to change this right now
Ability to change SMS greeting
✅ Changable with the "helloText" parameter in sar.conf (which I don't think is documented right now, I may want to fix that) -- this is good enough since it'll likely stay generic between missions
axis7818
We need a few critical features for the SDK that will interface with the JS sitting on YateBTS: