Cross country outbound calls initiated from Lambda have issues.
Since today, some agents complain that they cannot hear the sound of the call they received from the connect outbound initiated by a Lambda (response = cclient.start_outbound_voice_contact....) Specifically called to France from a source in UK. Note that calls from UK to my french mobile in Norway work fine.
To workaround, I have changed the source number to a french number but there is many possible combinations and I don' t have source numbers in all the countries I outbound to... Are you aware of limitations or known current issues with international calls ? Two weeks ago I had to remove the Caller ID transfer for similar issue in transfers to Luxembourg.
My workaround is to change the source number to a compatible number with the destination number. I'll probably make a mapping table to avoid the problematic borders.
Error using the AWS Connect Streams API to create an outbound call leg for initiating a transfer: "QuotaExceededException: Cannot dial third party destination: The agent is at maximum capacity."asked 2 months ago
Static IP for all outbound calls from LambdaAccepted Answerasked 4 months ago
Quick Connect Transfers Failing in Amazon Connectasked 4 months ago
Cross country outbound calls initiated from Lambda have issues.asked a month ago
Amazon Connect CCP - Softphone call failed, WebRTC issue, Red screen of deathasked 6 months ago
Amazon Connect - Outbound calls onlyasked 2 years ago
Quota Exceeded when making an outbound call from AWS Connectasked 2 months ago
Specify outbound caller ID using Connect Streams?asked 3 months ago
Instead of Outbound Calling It is making Inbound Calling while using StartOutboundVoiceContact API!asked a month ago
Ring agents using the shotgun approachasked 3 years ago