Being able to have a BlackList in the Coverage policies
in progress
A
Alejandro Dirgan
Have within the integration menu and the "Coverage Policies", to be able to add a BlackList to a "Coverage Policies" profile that allows placing operators that are not allowed to connect to every endpoint that is found with that "Coverage Policies"
Log In
Pasha
in progress
Hi everyone.
We have an update for this product request.
New API that allows you to block and unblock Operators and RAT (Radio Access Technology) types on a Coverage Policy level is LIVE
More details and docs can be found here: https://emnify.canny.io/changelog/new-api-that-allows-you-to-block-operators-and-rat-radio-access-technology-types
We will add Portal interface in a next step.
Pasha
planned
Michael Streiner
Hi Alejandro Dirgan and thanks a lot for your request!
We do have this functionality on our list and will work on it in the future, but we still need to define how we build it so that it does not break the existing option per device.
What's your use case and could you live without a per device option or would you need it to be combined - like with a default setting in the policy and overwriting settings per device or so?
We may add a bulk option to remove blacklisted operators before that, to reduce the effort as an interim workaround (like requested here: https://emnify.canny.io/feature-requests/p/unblacklist-sims-in-bulk )
A
Alejandro Dirgan
Michael Streiner: In my case, the ideal would be to overwrite the blacklists of each device.
My example would be in the following case, recently I have problems with an operator that does not have the best coverage, but when the endpoint connects to that network, in 5% it is trapped in the network and does not allow it to start a PDP connection and It also doesn't let you connect to another network, it's completely blocked.
Therefore, as I have more than 800 devices that I would like to place in the BlackList of that operator, with the Bulk option I cannot do them all, therefore, if the BlackList option were at the Coverage Policies level, I could without any problem. place in BlackList for all the endpoints that have said Coverage Policies, and when the problem is solved by support, I can remove the operator from the BlackList again, and it would be much simpler and faster than making a script that changes the almost 8000 endpoints that I have registered for activation.
When you work with more than 5000 endpoints, the scripted operations can take some time.