connect-rtc-js - GitLite

KO | EN

gitlite — search

#hacktoberfest #react #llm #machine-learning #rust #deep-learning #linux #java #kubernetes #vue #pytorch #mcp #ios #openai

connect-rtc-js

(★ 90)

Provide softphone support to AmazonConnect customers when they choose to directly integrate with our API and not using our web app.

파일 탐색기

최종 버전 다운로드 (.zip)

- PULL_REQUEST_TEMPLATE.md
- index.html
- index.js
- dcv-webrtc-redir-client-bundle.js
- connect-rtc-debug.js
- connect-rtc.js
- connect-rtc.min.js
- - constants.js
- - AzureVDIStrategy.ts
  - CCPInitiationStrategyInterface.js
  - CitrixVDIStrategy.js
  - DCVWebRTCStrategy.js
  - FailedVDIStrategy.ts
  - OmnissaVDIStrategy.js
  - StandardStrategy.js
- call_session.js
- connect-rtc.js
- credential_resolver.ts
- exceptions.js
- media_devices.js
- rtc_const.js
- rtc_peer_connection_factory.js
- rtc_peer_connection_manager.js
- rtc_peer_connection_manager_v2.ts
- rtc_session.js
- rtc_session_talking_substates.js
- rtp-stats.js
- session_report.js
- shared_media_session.js
- shared_media_session_talking_substates.js
- shared_media_signaling.js
- signaling.js
- signaling_channel_manager.js
- standby_peer_connection_manager.ts
- user_agent_data.js
- utils.js
- virtual_wss_connection_manager.js
- - pcm.spec.ts
  - pcm_v2.spec.ts
  - test-setup.ts
- - call_session.ts
  - credential_resolver.ts
  - globalMock.ts
  - rtc-stats.ts
  - rtc_peer_connection_factory.ts
  - rtc_peer_connection_manager.ts
  - rtc_peer_connection_manager_v2.ts
  - rtc_session.ts
  - rtc_session_talking_substates.ts
  - session_report.ts
  - shared_media_session.ts
  - shared_media_session_talking_substates.ts
  - shared_media_signaling.ts
  - signaling.ts
  - signaling_channel_manager.ts
  - standby_peer_connection_manager.ts
  - test-setup.ts
  - utils.ts
  - virtual_wss_connection_manager.ts
- Session.puml
- Signaling.puml
.babelrc
.eslintrc
.gitignore
.npmignore
CODE_OF_CONDUCT.md
CONTRIBUTING.md
Gruntfile.cjs
LICENSE.txt
NOTICE.txt
package.json
README.md
THIRD-PARTY.txt
tsconfig.json

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

[![Build Status](https://travis-ci.org/aws/connect-rtc-js.svg)](https://travis-ci.org/aws/connect-rtc-js)

# Amazon Connect connect-rtc-js #
**connect-rtc.js** provides softphone support to AmazonConnect customers when they choose to directly integrate with AmazonConnect API and not using AmazonConnect web application.
It implements Amazon Connect WebRTC signaling protocol and integrates with browser WebRTC APIs to provide a simple contact session interface which can be integrated with [Amazon Connect StreamJS](https://github.com/aws/amazon-connect-streams) seemlessly.

## Usage ##
### Prebuilt releases
In the [gh-pages branch](https://github.com/aws/connect-rtc-js/tree/gh-pages) prebuilt ready to use files can be downloaded/linked directly.

## Working with GitHub registry for Omnissa

**Ensure this step is followed before running** ```npm install```

Please refer to this [GitHub article](https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-npm-registry) to authenticate your project and use our public registry.

You will need to create a github token and either authenticate directly or use/create an .npmrc file within your project. An example .npmrc
file is as follows:

```
@euc-releases:registry=https://npm.pkg.github.com
//npm.pkg.github.com/:_authToken=<GITHUB_TOKEN>
```

### Build your own
1. Install latest LTS version of [NodeJS](https://nodejs.org)
2. Install [Grunt](https://gruntjs.com/)
3. `git clone https://github.com/aws/connect-rtc-js.git`
4. `cd connect-rtc-js`
5. `npm install`
5. To build:
    1. `grunt`
    2. Find build artifacts in **out** directory
6. To run unit tests:
    1. `npm test`
7. To run demo page:
    1. `grunt demo`
    2. Open the URL printed out by connect task, it looks like "Started connect web server on <https://localhost:9943>"
    3. Click **demo** folder

## Amazon Connect StreamJS integration ##
In a typical [amazon-connect-streams](https://github.com/aws/amazon-connect-streams) integration, connect-rtc-js is not required on parent page. Softphone call handling is done by embedded CCP.

However the following steps could further customize softphone experience.
1. Load connect-rtc-js along with amazon-connect-streams on parent page
2. Following [amazon-connect-streams instructions](https://github.com/aws/amazon-connect-streams/blob/master/README.md) to initialize CCP
3. Replace the softphone parameter (within the second parameter of ***connect.core.initCCP()***) with
    `allowFramedSoftphone: false`
    This would stop embedded CCP from handling softphone call
4. Add this line after initCCP
    `connect.core.initSoftphoneManager({allowFramedSoftphone: true});`
    This would allow your page to handle softphone call with the connect-rtc-js loaded by your page. ***allowFramedSoftphone*** is necessary if your page also lives in a frame, otherwise you can remove that parameter.
5. Add this HTML element to your web page
    `<audio id="remote-audio" autoplay></audio>`
    amazon-connect-streams library will look for this element and inject it into connect-rtc-js so that connect-rtc-js can play downstream audio through this element.
6. Customize it (some ideas below)
    * Customize audio device for `remote-audio` element
    * Look at all the documented APIs in [RtcSession](https://github.com/aws/connect-rtc-js/blob/master/src/js/rtc_session.js) class, modify [softphone.js](https://github.com/aws/amazon-connect-streams/blob/master/src/softphone.js) as you need
    * Revert step 4, add your own glue layer between amazon-connect-streams and connect-rtc-js (use [softphone.js](https://github.com/aws/amazon-connect-streams/blob/master/src/softphone.js) as a template)