OTPs delivered via SMS appear to originate from multiple different phone numbers

    Applies to:
  • SecureAuth Identity Platform
  • Legacy SecureAuth IdP
Deployment model:
  • Cloud
  • Hybrid
  • Version Affected:  All


    When end users are receiving OTPs via SMS the sender number is not consistent and appears to be coming from different phone numbers rather than a fixed SMS shortcode or an alphanumeric SMS sender label. 



    Normally we appear to send SMS from an alphanumeric label "SecureAuth" but that is blocked in the US.  Additionally SMS short codes are heavily blocked on Sprint and T-Mobile.



    To circumvent SMS blocking in such circumstances, our SMS provider delivers such messages via a pool of "long number" senders to ensure the SMS isn't blocked.




    SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

    Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.

    0 out of 0 found this helpful



    Please sign in to leave a comment.