Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Device Reachability Status - Is it mandatory to support all values? #217

Open
MsOlaAjibola opened this issue Oct 15, 2024 · 1 comment
Open

Comments

@MsOlaAjibola
Copy link

Currently there are 3 reachability status values - CONNECTED_SMS, CONNECTED_DATA and NOT_CONNECTED. Is it mandatory for an Operator to support all 3? For example could an Operator choose to not support CONNECTED_SMS?

Thanks.

@eric-murray
Copy link
Collaborator

Hi @MsOlaAjibola

It depends on the use case the API is being used for.

If a mobile device was connected to your network, but the user of that device had disabled mobile data, then what would your API return? If you did not support CONNECTED_SMS, then you could either:

  • return CONNECTED_DATA to indicate that the device was connected the network; or
  • return NOT_CONNECTED to indicate that the device does not have data connectivity?

Neither response is entirely correct, but may be suitable for the use case intended by the API consumer.

In practise, checking whether the device has packet switched and/or circuit switched connectivity is not so difficult.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants