2020 Mar 16 12:16 PM - edited 2024 Feb 03 6:36 PM
Hi all,
We're using SAP DI for the SMS & E-mail campaigns in Marketing Cloud.
E-mail part works perfectly fine.
However, for the SMS configurations I have an error as given in the title during the test SMS sending process.
I followed the steps as written in the link given below.
Has anybod face with this issue before? Did I miss something? Otherwise I'll raise a ticket?
Regards,
Cagri
Hi schneidert & saurabhkabra2009 ,
Thanks for your responses. I also raised the ticket and today I got a response.
They told me that, we need to have a "full setup" which is also considering the sms bounce set up (SAP_COM_0299).
Once I set up this communication system & set up for bounces from below help link, the issue was fixed.
Regards,
Cagri
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Cagri,
thanks for the update.
Hi Cagri,
Can you please download the SSL certificate from https://community.sapdigitalinterconnect.com/t5/Enterprise-Services-Knowledgebase/NEW-SSL-Certificat... and import it in Security app of SAP Marketing Cloud? ( This is a less probable case but just 2 min task, so I owuld rather perform this)
Also as far as I remember from the past, SAP DI needs to whitelist IPs which will be calling their endpoints in order to send out the SMS due to local laws. Furthermore, I saw a similar text in OnPrem Marketing system help:
To access the http service from SAP Digital Interconnect, you must populate the externally visible IP address of your server to SAP Digital Interconnect and you must know the ID, so that it can be added to the whitelist of allowed callers for your account. If you are using a proxy for sending, you must populate the external IP address of the proxy.
As mentioend in above link, you can reach out to "sapdigitalinterconnect@sap.com" with the detail to get quick support from them.
Thanks
Saurabh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey cagreply,
do you have any other information provided at the end of the error message? (e.g. something with "SSL handshake...")
I only had that error for the AWS integration because there was a certificate missing.
Otherwise I think you have to open an incident if you are not able to analyze further.
BR Tobias
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
11 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.