Closed larry-voicefoundry closed 11 months ago
Thanks for pointing this out. I will look into this and update it here.
This is one of the known issue and this will be fixed as part of the Contact Center 13.
This should be fixed with the latest contact center release.
There is an issue with the Lambda that handles contact events and sends cancel omni-flow events to telephony integration Lambda. That function sends the contact id over as Details.Parameters.ContactID but the invokeTelephony lambda expects Details.ContactData.ContactId to exist if Details.Parameters.contactId doesn’t.
This causes the invoke telephony Lambda to error out when attempting to log on that line. This appears to be causing issues with contacts correctly wrapping up in Salesforce after the contact disconnects.