SMS sending of verification codes about exposure-notifications-verification-server HOT 12 CLOSED

The SMS config will need to be in the database and configured on a per-local basis. See #104

from exposure-notifications-verification-server.

Follow up from previous comment

SMS provider and use should be database driven.
If there is no provider configured, then the dialog shouldn't be shown.

As we go multi-tenant, this is important since it is possible that different "realms" will use different SMS config and some might not use SMS at all.

from exposure-notifications-verification-server.

@mikehelmick: The label(s) priority/important-soon cannot be applied, because the repository doesn't have them

from exposure-notifications-verification-server.

One other note - best if the phone numbers don't get stored in the database.

from exposure-notifications-verification-server.

I have some experience with the Twilio API, so I can take this

from exposure-notifications-verification-server.

/assign

from exposure-notifications-verification-server.

Twilio has a some considerations to be noted if it is used for an impelemntation that is not in the US.
i.e : Creating a Numeric or Alpha Numeric Sender ID would be a requirement in some destinations and verifying that the server would use those values when posting a payload.
https://support.twilio.com/hc/en-us/articles/223133767-International-support-for-Alphanumeric-Sender-ID

from exposure-notifications-verification-server.

I think that's fine. The server operator would need to take those steps, but I don't think it would affect our code. Can you share more about your concerns?

from exposure-notifications-verification-server.

I am only noting that the Sender ID (i.e numeric or alpha numeric) is a value that should be factored in when integrating with twilio to ensure portability of the service outside of the US. So it would be set as an ENV variable for example the same way you add Twilio API Key and the application SID. Twilio mostly doesnt handle overriding that value on behalf of the sender.

from exposure-notifications-verification-server.

No no, bad GitHub. That was only part 1 of 1000.

from exposure-notifications-verification-server.

/assign

from exposure-notifications-verification-server.

/assign

from exposure-notifications-verification-server.