Navigate to Settings, then click Security. Click SMS Configuration. Enter the client ID, client secret and base URL and click Save. Learn more. Click Check SMS Connection to verify the connection.

verify you were directed to the Oracle Cloud Classic console

https://www.oracle.com/cloud/sign-in.html.

CXMARKETINGAUTO_<AccountName>

You must retrieve the following Oracle Identity parameters from Oracle Identity Cloud Service (IDCS):  Client ID Client secret Base URL This must be completed by your Oracle Cloud Account administrator or service administrator.

Before you can use the SMS channel and begin sending SMS messages, you must configure the OAuth connection.

Unlike other default asset permissions, SMS code permissions can only be setup for security groups, not individual users. SMS codes are not created by users and aren't an asset type you can manage with Asset Creation controls for the security group. You can only setup default SMS code permissions for the security group at a time. You cannot grant individual users default SMS code permissions. The permissions are for the security group.

In Oracle Eloqua, contacts are created by email address and email addresses are expected to be unique. Therefore, a single phone number may be associated to multiple contacts if someone is in Oracle Eloqua under two separate emails but has only given one phone number. In this case, if that phone number is opted in, then phone opt in appears against both contacts.

By default, all your contacts become subscribed to SMS when the SMS feature is turned on for your instance.

The SMS Message Designer provides an easy-to-use interface to build your message content and easily add features like field merges, hyperlinks, and keywords. An SMS keyword is a word or phrase that your subscribers can text to an SMS code to interact with your SMS campaign. A code and keyword combination cannot be activated simultaneously on multiple campaigns.

Oracle Eloqua can only send SMS messages to valid contact Business Phone or Mobile Phone numbers. You are responsible for maintaining valid phone numbers in your contact database. Phone numbers must be in International or e.164 format. You can enable phone number validation to prevent invalid numbers from being saved in your database.

This can't be changed later, so validate your choice carefully. Ensure that the delegated branded Short URL domain is unique. It can't be shared across more than one brand in the same instance or across more than one Oracle Eloqua instances.

This branding is different from any branding you have otherwise set up in Eloqua.

Invalid keyword responses do count towards sent message volume.

For SMS messages, an invalid keyword response message can be sent to originating mobile numbers if the incoming message contains an invalid keyword or a keyword that is inactive or is not defined for the code.

Each code can only have one invalid keyword response message.

Setting up invalid keyword responses is not mandatory, but it's considered good practice.

In the full service model, Eloqua manages aggregators for you.

SMS specific filters

Key SMS terms

Send transactional and promotional messages.

Engage with customers with one-way and two-way messages.

two-way long/short codes or by using link tracking feature

multiple routing options.

Leverage multiple code types: alpha, short code, and long code (use of code is subject to country regulations).

Use shortened links

Some keywords are mandatory in some countries

Custom and Help types do not perform any system action and can be used for pure marketing orchestration setup. Custom keyword allows you to interact with your customer base via SMS content, while the Help keyword offers an intuitive way for the customer to receive assistance or clarification.

Oracle Eloqua supports the following types of keywords: Opt-Out: Automatically opts out a mobile number. Opt-In: Automatically opts in a mobile number. Help: Does not automatically perform any action. Custom: Does not automatically perform any action.

SMS

French hospital medicine came to be based on three pillars, none entirely new, but which together constituted a new way of looking at disease. The three pillars were physical diagnosis, pathologico-clinical correlation, and the use of large numbers of cases to elucidate diagnostic categories and to evaluate therapy

We strongly recommend the use of security keys and TOTPs wherever possible. SMS-based 2FA does not provide the same level of protection, and it is no longer recommended under NIST 800-63B.

We now take an opinionated stance on which second factor you should set up first – you'll no longer be asked to choose between SMS or setting up an authenticator app (known as TOTP), and instead see the TOTP setup screen immediately when first setting up 2FA.

But first, an important note — friends don't let friends use SMS 2FA.

The problem with using SMS-2FA to mitigate this problem is that there’s no reason to think that after entering their credentials, they would not also enter any OTP.

discussions about SMS-2FA get heated very quickly. I've found that SMS-2FA deployment or advocacy has been a major professional project for some people, and they take questioning it's efficacy personally

I believe that SMS 2FA is wholly ineffective, and advocating for it is harmful.

Unfortunately all SMS/voice gateway are owned by paid services, thus there is no such thing as open-source, that I can recommend.

Fortunately, we found RingCaptcha (https://ringcaptcha.com), which has a the 'starter plan' that offers free 500 OTP monthly. Just a small plug for them for providing freemium service; they are highly reliable because they are integrated with all major global, and regional providers, e.g., Twilio, Nexmo, Infobip, MessageBird, etc., and send your OTP through the best provider/route based on country/phone carrier, and can auto fallback to alternative paths. This means you just need to integrate with RingCaptcha, without the headache of deciding which SMS/voice OTP provider has best combination of price and reliability, which is a real headache when you are sending OTP world-wide.

But getting codes by phone turns out not to be not very secure at all. A vulnerability in SMS messaging is that crooks can reroute text messages(Opens in a new window).

nother good example is the SMS message, which started life as a way for Nokia engineers to keep in touch when they were out mending phone lines in the countryside.

We do know that, just like iMessage, this new approach will failover to SMS/MMS if a user cannot receive the encrypted variant or if bandwidth is insufficient on either end.

The issue, though—and it’s a big one, is that the SMS infrastructure is inherently insecure, lending itself to so-called “man-in-the-middle attacks.” Messages run through network data centres, everything can be seen—security is basic at best, and you are vulnerable to local carrier interception when travelling.

The thinking behind RCS was to deliver a best of both worlds solution—the cross-platform ubiquity of SMS with the functionality of WhatsApp and iMessage, but built right into the core network infrastructure

A couple of years after WhatsApp, Apple jumped into the game with iMessage—its obvious drawback, that senders and recipients had to be using iPhones, was overcome by integration with the standard SMS platform on those phones. If a recipient was not on iMessage or was offline, the message would revert to SMS.

WhatsApp has become the dominant messaging platform, dwarfing all other contenders with the exception of its Facebook stablemate Messenger. In doing so, this hyper-scale “over-the-top” platform has also pushed legacy SMS messaging into the background

Text messaging is very cheap in most parts of the world. In fact, in 2015, the cost of sending an SMS in Australia was calculated to be just $0.00016. While the bulk of a cell phone bill typically is its voice minutes or data usage, text messages are either included in the voice plan or are added as an extra cost.