amazon-connect / video-call-escalation Goto Github PK
View Code? Open in Web Editor NEWLicense: MIT No Attribution
License: MIT No Attribution
Encountered a number of issues trying to npm run build:frontend
ERROR in ./node_modules/styled-components/dist/styled-components.browser.esm.js 1:0-73
Module not found: Error: Can't resolve 'react-is' in 'C:\Users\crijm\Documents\code\video-call-escalation\agent-app\node_modules\styled-components\di
st'
resolve 'react-is' in 'C:\Users\crijm\Documents\code\video-call-escalation\agent-app\node_modules\styled-components\dist'
resolved by running in agent-app directory:
npm install react-is
> [email protected] build
> NODE_ENV=production webpack --config=webpack.config.prod.js --mode=production
Error: error:0308010C:digital envelope routines::unsupported
at new Hash (node:internal/crypto/hash:67:19)
at Object.createHash (node:crypto:135:10)
at BulkUpdateDecorator.hashFactory (C:\Users\crijm\Documents\code\video-call-escalation\demo-website\node_modules\webpack\lib\util\createHash.js:
145:18)
at BulkUpdateDecorator.update (C:\Users\crijm\Documents\code\video-call-escalation\demo-website\node_modules\webpack\lib\util\createHash.js:46:50
)
at RawSource.updateHash (C:\Users\crijm\Documents\code\video-call-escalation\demo-website\node_modules\webpack-sources\lib\RawSource.js:70:8)
at NormalModule._initBuildHash (C:\Users\crijm\Documents\code\video-call-escalation\demo-website\node_modules\webpack\lib\NormalModule.js:888:17)
at handleParseResult (C:\Users\crijm\Documents\code\video-call-escalation\demo-website\node_modules\webpack\lib\NormalModule.js:954:10)
at C:\Users\crijm\Documents\code\video-call-escalation\demo-website\node_modules\webpack\lib\NormalModule.js:1048:4
at processResult (C:\Users\crijm\Documents\code\video-call-escalation\demo-website\node_modules\webpack\lib\NormalModule.js:763:11)
at C:\Users\crijm\Documents\code\video-call-escalation\demo-website\node_modules\webpack\lib\NormalModule.js:827:5
Browserslist: caniuse-lite is outdated. Please run:
npx browserslist@latest --update-db
resolved by running in demo-website directory
npx browserslist@latest --update-db
> [email protected] build
> NODE_ENV=production webpack --config=webpack.config.prod.js --mode=production
Error: error:0308010C:digital envelope routines::unsupported
at new Hash (node:internal/crypto/hash:67:19)
at Object.createHash (node:crypto:135:10)
at BulkUpdateDecorator.hashFactory (C:\Users\crijm\Documents\code\video-call-escalation\demo-website\node_modules\webpack\lib\util\createHash.js:
145:18)
at BulkUpdateDecorator.update (C:\Users\crijm\Documents\code\video-call-escalation\demo-website\node_modules\webpack\lib\util\createHash.js:46:50
)
at RawSource.updateHash (C:\Users\crijm\Documents\code\video-call-escalation\demo-website\node_modules\webpack-sources\lib\RawSource.js:70:8)
at NormalModule._initBuildHash (C:\Users\crijm\Documents\code\video-call-escalation\demo-website\node_modules\webpack\lib\NormalModule.js:888:17)
at handleParseResult (C:\Users\crijm\Documents\code\video-call-escalation\demo-website\node_modules\webpack\lib\NormalModule.js:954:10)
at C:\Users\crijm\Documents\code\video-call-escalation\demo-website\node_modules\webpack\lib\NormalModule.js:1048:4
at processResult (C:\Users\crijm\Documents\code\video-call-escalation\demo-website\node_modules\webpack\lib\NormalModule.js:763:11)
at C:\Users\crijm\Documents\code\video-call-escalation\demo-website\node_modules\webpack\lib\NormalModule.js:827:5
node:internal/crypto/hash:67
this[kHandle] = new _Hash(algorithm, xofLen);
^
resolved by setting
export NODE_OPTIONS=--openssl-legacy-provider
Hi
When trying to import the VideoCallEscalationQueue Contact Flow, it fails to import.
It just keeps saying that the file can't be read.
No issue importing the VideoCallEscalationChat Contact Flow
Hi there,
Trying to deploy the CDK backend (step 2) and get thrown the below error upon building the backend, all lambdas successfully build up until the last one "utility-layer". I cannot for the life of me get this to build and cannot figure out why. I managed to successfully build manually the other lambdas, but cannot get this last one to work.
Account is an IAM admin configured correctly. Running on windows.
Any insight?
Cheers
build utility-layer
[email protected] build C:\Users\Jay\video-call-escalation\cdk-backend\lambdas\utility-layer
esbuild *.js --bundle --platform=node --external:aws-sdk --outdir=build --target=node12
error: Cannot read directory "node_modules/*.js": The filename, directory name, or volume label syntax is incorrect.
error: Cannot read directory "../../node_modules/*.js": The filename, directory name, or volume label syntax is incorrect.
error: Cannot read directory "../../../../node_modules/*.js": The filename, directory name, or volume label syntax is incorrect.
error: Cannot read directory "*.js": The filename, directory name, or volume label syntax is incorrect.
error: Could not resolve "*.js"
5 errors
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] build: esbuild *.js --bundle --platform=node --external:aws-sdk --outdir=build --target=node12
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Jay\AppData\Roaming\npm-cache_logs\2021-04-12T22_46_03_383Z-debug.log
utility-layer build failed
bash: prompt: command not found
/c/Users/Jay/video-call-escalation/cdk-backend
INFO: cdk.context.json not present, nothing to remove
Deploying cdk-backend
`
Hi. I got that error - Something went wrong, We’re unable to load chat at this time. Please refresh the page to retry, or try again later - on the demo site and after clicking on the Video Call Now. On the agent side, I can see the agent CCP and I can start a meeting, see my camera content.
Any idea where to look at. Thanks for your help.
Looks like the SSO Auth is working, but for some reason I am getting this dup error (only one user exists in both Cognito and Azure AD) but somehow it looks like a dup. If I do not create the user in Cognito, then it throws a "doesn't exist" error.
CloudWatch Logs:
2021-06-03T14:43:46.647Z aeb12ac4-0785-4f6f-99bf-9be928a0320e INFO AuthUtility >> claim confirmed for 302d5f63-8bda-4e53-a97c-db0bde6546bb
2021-06-03T14:43:47.804Z aeb12ac4-0785-4f6f-99bf-9be928a0320e ERROR CCPLogin >> Connect: DuplicateResourceException: The user [email protected] is already associated with the Amazon Connect instance 828026a9-bb21-45fc-a0bb-2af6c326b977
at Object.extractError (/var/runtime/node_modules/aws-sdk/lib/protocol/json.js:52:27)
at Request.extractError (/var/runtime/node_modules/aws-sdk/lib/protocol/rest_json.js:55:8)
at Request.callListeners (/var/runtime/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
at Request.emit (/var/runtime/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
at Request.emit (/var/runtime/node_modules/aws-sdk/lib/request.js:688:14)
at Request.transition (/var/runtime/node_modules/aws-sdk/lib/request.js:22:10)
at AcceptorStateMachine.runTo (/var/runtime/node_modules/aws-sdk/lib/state_machine.js:14:12)
at /var/runtime/node_modules/aws-sdk/lib/state_machine.js:26:10
at Request. (/var/runtime/node_modules/aws-sdk/lib/request.js:38:9)
at Request. (/var/runtime/node_modules/aws-sdk/lib/request.js:690:12) {
code: 'DuplicateResourceException',
time: 2021-06-03T14:43:47.798Z,
requestId: 'bef05f24-eb7f-43c8-8957-be38e2d31c64',
statusCode: 409,
retryable: false,
retryDelay: 79.3485627907506
}
2021-06-03T14:43:47.805Z aeb12ac4-0785-4f6f-99bf-9be928a0320e ERROR ErrorHandler: CCP Login Error, please try again later
at /var/task/index.js:14953:13
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at async Object.ccpLogin (/var/task/index.js:14948:27)
at async Runtime.exports.handler (/var/task/index.js:15121:28) {
statusCode: 500
}
POST Request:
2021-06-03T14:43:45.985Z aeb12ac4-0785-4f6f-99bf-9be928a0320e DEBUG Event: {
version: '2.0',
routeKey: 'POST /ccplogin',
rawPath: '/ccplogin',
rawQueryString: '',
headers: {
accept: 'application/json, text/plain, /',
'accept-encoding': 'gzip, deflate, br',
'accept-language': 'en-US,en;q=0.5',
authorization: 'AWS4-HMAC-SHA256 Credential=ASIAUKSQ3MKX4WBLZHSR/20210603/us-east-1/execute-api/aws4_request, SignedHeaders=cognitoidtoken;content-type;host;x-amz-date;x-amz-security-token, Signature=1aa798571710d76ad3a94fc3685ecb7489911ee38bd8dc8390a5e6ec8c017799',
cognitoidtoken: 'eyJraWQiOiJaZ1B4ZjdpRVN4dEl3bE5ETGNQUlNlS013ZThCdTd4VXY4eklYR3ZBXC9qaz0iLCJhbGciOiJSUzI1NiJ9.eyJzdWIiOiIzMDJkNWY2My04YmRhLTRlNTMtYTk3Yy1kYjBiZGU2NTQ2YmIiLCJlbWFpbF92ZXJpZmllZCI6dHJ1ZSwiaXNzIjoiaHR0cHM6XC9cL2NvZ25pdG8taWRwLnVzLWVhc3QtMS5hbWF6b25hd3MuY29tXC91cy1lYXN0LTFfb0l4UlZtU0VyIiwicGhvbmVfbnVtYmVyX3ZlcmlmaWVkIjp0cnVlLCJjb2duaXRvOnVzZXJuYW1lIjoiMzAyZDVmNjMtOGJkYS00ZTUzLWE5N2MtZGIwYmRlNjU0NmJiIiwiYXVkIjoiM3MwdTh1MDQzc2o2ZWgzcm1zbDFodXBrbWgiLCJldmVudF9pZCI6IjhmOTU2YWNiLTI4ZGUtNGZmMy1iMWJjLTQzOGVkZThhMTgzZCIsInRva2VuX3VzZSI6ImlkIiwiYXV0aF90aW1lIjoxNjIyNzMxNDI0LCJwaG9uZV9udW1iZXIiOiIrMTU2MTM3NjIzMTkiLCJleHAiOjE2MjI3MzUwMjQsImlhdCI6MTYyMjczMTQyNCwiZW1haWwiOiJQcm9waGVaZWVAUHJvcGhlWmVlLm9ubWljcm9zb2Z0LmNvbSJ9.rUnvOF3QVoDTkJASZ-bqKjcZCypJr2ELAqMkxgyviF6n6Tc-C4BdZAWTqnfd_YiCIvbwumE1u0BnEtd4iN-sDYZ-DjtGmcKckUCXRT_cKVD-rWi3-4wAeF3zYndU3tJSLrLFLUvOpfDzr3Zx4rzrmp1Jy2U07z8wW_48OgHuIoXwP-dhxo-3VuhHz-2M3kI4Yzp4uR2fP70_AHZ9Df063hXIFTelhnFNiJDHcZKvl-65mpEUDWil82rH2ZfBpgtX5ctw_4DNsthwgmWJ_geAc8NeuLdX1fYeVPoMc5vQB1q35W1PjbllhFpSaVrOA6MABm8pzBhQ5oEyaGjyuQnbnA',
'content-length': '28',
'content-type': 'application/json; charset=UTF-8',
host: '4b0kza49jc.execute-api.us-east-1.amazonaws.com',
origin: 'https://d3chaersslqhc6.cloudfront.net',
referer: 'https://d3chaersslqhc6.cloudfront.net/',
'user-agent': 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:88.0) Gecko/20100101 Firefox/88.0',
'x-amz-date': '20210603T144344Z',
'x-amz-security-token': 'IQoJb3JpZ2luX2VjEEcaCXVzLWVhc3QtMSJIMEYCIQCpjXs/lHghRVx4tii7U3DSDcDcTemdc4M6iVcF29A3XQIhAIvYYwCtX7V7tE2DiK2Mm93poNNvyvYb5hWFKBdchRSbKs0ECPD//////////wEQABoMMjk3NTk2MDUyMTQzIgzPEjtFQIB6zFyv+LYqoQTbjcxXzHZ6d53LhC+OUFsjJZodlEygV+XH0/UPOWKYgjHg4oLGdMvAoEjoYj1PXlN43CxUsFA4s2BldPmBd8cvv9ZQE5s9vY82Yy2y0yWzcazKYoX/XHiZKclOZWnu76SWMrB4G79gcpcSz7JSC2cO/8v2EL6CjPvjgz6AmqavCDsKcpdmv+BljBoKTkI2EIlWZBKAPM9gInO7DGjJdRDbPvjiBEkPUijkaT55Jr0Y2zlp66uQD4vuLjEofwa/+nmh2q5em6xvAQwMdRWOWdsdCJA/PszLQtKQj+7FTI0TVtB7RKCsDrTfxjNB6brZY/Y+gqW7T6eUCg6KRjyaAIf0PsbS50GyD8XgVyIC/Q9Si5UHtj/D6RbLkrUkDjxFPxA2gIUOmPo9oMpcaLC3ikTz92NB6Il3u4Jb3GbtbdFQ84FJQd21HBnZeMfLhA/UmJGU5yJK2b084LqQcs2FHMsEP2ym94sDNjCTZ5v79ZC40TmNuZbXhcmCWYPoLmbcaksJzTaQ9iJUHRzsX9VZGTRb5WJ1bQDin5NvFCKgwBHdZkshg7vvboT8X624LzZg2qeiewkkTYkUzzDTo8uIUMEN4dBOXJIzV/TzpzsXowdz6vCOdo0OohQ6X+Tcs7nCk96LZ1eqHuqBFwK/XKAW/e0NaXXtF6fejF2z7otvAu+1A1EqLU5ab7s47duxOYIGzt79acSnAhB8Bf5kqOjMGBHSRTCg1eOFBjqEAhDfgKenhfmD/IpEpfdkT/wd+OHpS1mzwniQzAHC6THZgaTdWf8OZDvtBM4xL4ql6xBFbhrnj1s6uTFs8w+ydaSK+uFeqA9DMOIPyrdyppk4JCtmiILmFn8+G3bDRJQAWWET4im9EH2wgzr/s/qUz4aWDBSgnEOOLP/eFEFZxkgOEfZdYYkMxi8d37Ylw8YAa3eC8UHbBNlgE3BAjBsPjiudxgav43Ezg9xPR63KGZG2ni+pE+g2170o006wd3MzJ2EHFxsts/k+Mlli2h5itW8+mbxzA8GiCzHX/XEiffMDLrzpToNlgIlS3FR2/wSlkf/Xj6Cr6u4/UH03Ea1nKjCjjpeK',
'x-amzn-trace-id': 'Root=1-60b8eaa1-5b774afe1250bdc76f0bcd01',
'x-forwarded-for': '99.114.225.80',
'x-forwarded-port': '443',
'x-forwarded-proto': 'https'
},
requestContext: {
accountId: '297596052143',
apiId: '4b0kza49jc',
authorizer: { iam: [Object] },
domainName: '4b0kza49jc.execute-api.us-east-1.amazonaws.com',
domainPrefix: '4b0kza49jc',
http: {
method: 'POST',
path: '/ccplogin',
protocol: 'HTTP/1.1',
sourceIp: '99.114.225.80',
userAgent: 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:88.0) Gecko/20100101 Firefox/88.0'
},
requestId: 'AWmZOhQEIAMEMnA=',
routeKey: 'POST /ccplogin',
stage: '$default',
time: '03/Jun/2021:14:43:45 +0000',
timeEpoch: 1622731425242
},
body: '{"connectLoginByEmail":true}',
isBase64Encoded: false
}
I set up everything according to the README.
With one exception:
I fixed a minor issue in which the ccpLogin lambda was not permitted to assume its own role due to a recent global IAM change. The trust relationships tab for the lambda role is instead:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Principal": {
"Service": "lambda.amazonaws.com"
},
"Action": "sts:AssumeRole"
},
{
"Effect": "Allow",
"Principal": {
"AWS": "<ARN of the role it self>"
},
"Action": "sts:AssumeRole"
}
]
}
After logging in with cognito to the agent-app. It is stuck on "Please wait while we onboard your profile...". When I look in the console I see:
I have double-checked that the credentials are correct. I can see in the lambda logs that it successfully retrieved amazon connect credentials. I also ensured the approved domains contained the URL of the agent app. It looks like a very similar to this issue.
Could someone confirm that this repo still works for them? And if yes, if you have any suggestions on what to adjust it would be much appreciated!
Hello,
Is this solution ready to start a cognito session with "own" conect users (without SSO/SAML)?
Thanks
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.