Hi, I’ve had this ticket (#E-001933721) open for over a month with no response so far, so I’m reposting the question here in case anyone has encountered something similar.
We are currently implementing an SMS integration using a custom provider in AJO. During the onboarding process, the provider requested the following information:
“To proceed with the activation of the instance, we need to know from which IP or domain we’ll receive the requests so we can allow them through our firewall.”
Can you help me with that information required by sms provider?
Thanks!
Solved! Go to Solution.
Views
Replies
Total Likes
I reviewed the support case and the related discussion with the core team. As noted in the case, Adobe Journey Optimizer (AJO) does not use a single static egress IP per customer.
Outbound HTTPS requests to your API may originate from the Adobe IP addresses or ranges shared in the case, and all of these should be allowlisted to ensure uninterrupted connectivity.
We will also work toward getting this behavior formally documented.
@Silvio6 Did you escalate the ticket through CSM? @Sukrity_Wadhwa
Additionally, take a look at this information
Hi @Silvio6,
Thank you for sharing your question with us. I understand how important this is for your implementation, and I’ve raised this internally using your support ticket number to help expedite resolution.
We will keep you updated as soon as I hear back. Appreciate your patience while we work on getting this resolved for you!
And, thanks @SatheeskannaK for flagging this 🙂
I reviewed the support case and the related discussion with the core team. As noted in the case, Adobe Journey Optimizer (AJO) does not use a single static egress IP per customer.
Outbound HTTPS requests to your API may originate from the Adobe IP addresses or ranges shared in the case, and all of these should be allowlisted to ensure uninterrupted connectivity.
We will also work toward getting this behavior formally documented.
Views
Likes
Replies