SMS Provider

Hi,

We have received some complaints from customers that are not receiving the OTP in their signature process.

We already raised a ticket to OneSpan support with the incident, and they told us that apparently the sms is being triggered without any issue from their systems. 

We are using OneSpan REST API to create and process all the transaction mostly based on the OOTB rulesets you provide.

We'd like to configure an internal SMS Provider into our "on premise" eSignLive platform. The Platform Administrators guide suggests that this can be done by simply making the appropriate settings to the core.properties file. It also seems we would then need to engage this service via SOAP. Are there any other configuration steps, or considerations for setting up an internal SMS Provider solution for our eSignature on premise solution? Thanks, Todd