- Newest
- Most votes
- Most comments
This mean you need to open a ticket to raise the Outbound Campaign Active Calls to unblock your workload. Only with the StartOutboundVoiceContact API work, will then Pinpoint work.
You can do a sanity check on your syntax by NOT using TYPE=Campaign and remove AMD so it will dial to your destination with the flow. The AMD will not kick in but at least you know it can make outbound call with the flow. Then the only reason will be the limit for Outbound Campaign Active Calls (this is not a listed limit)
Thank you so much! So with above syntax, i get outbound call and it gets disconnected in a second and that's due to CPC check in my connect flow which is as expected. Could you please help with specific ask to be raised with AWS team on this?
Raise a ticket with aws support team and tell them to increase Threeshold limit for outbound calls.
You should test if CAMPAIGN calling is working using the CLI command "aws connect start-outbound-voice-contact" which is at the end of the blog post. You can omit the campaign-id when using the CLI directly but make sure you have both answer-machine-detection-config to be true and traffic-type to be CAMPAIGN. If this works, then it is a communication from Pinpoint to Connect, make sure the permission to the keys are setup properly, https://docs.aws.amazon.com/connect/latest/adminguide/enable-outbound-campaigns.html
Since you started the journey in Pinpoint, check if your campaign status in Connect to be Active (green)
https://docs.aws.amazon.com/connect/latest/adminguide/how-to-create-campaigns.html#campaign-state
If the CLI failed above, open a ticket and ask specifically for Campaign active calls and Campaign count to be raised.
Hi, Thank you for that input! I did run the CLI command with/without Campaign ID, contact ID got created in both the scenario without any errors. However those contact ID was not available in cloud watch or CTR logs search. Also there was no outbound call triggered.
I see that the "Amazon Connect High-Volume Outbound Communications campaign count" quota Utilization is "Not-available". Applied and Default quota value is set to "25". Please let me know your comments. Thanks in advance!
Relevant content
- Accepted Answerasked a year ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 2 years ago
We had the same issue exactly and couldn't work it out. I reached out to a few people at AWS and no one seemed to have worked with outbound. Considering this was mostly just for my own learning I gave up for the time being. If you do get it working please please please post something about it as I'm curious.