|
| 1 | +# Bosch Dicentis Companion Module |
| 2 | + |
| 3 | +#### Config |
| 4 | +- **Transport**: Select `DICENTIS API (WebSocket)` for server API or `DICENTIS Wireless (REST)` for DCNM-WAP HTTP API |
| 5 | +- **Server IP**: IP address of the Bosch Dicentis server |
| 6 | +- **REST Port / Protocol**: Used in REST mode (defaults: `80`, `http`) |
| 7 | +- **REST Login Path**: Login endpoint used in REST mode (default: `/api/login`) |
| 8 | +- **REST Command Path**: Command endpoint used for operation payloads in REST mode (default: `/api`) |
| 9 | +- **Username**: Login credentials for API access |
| 10 | +- **Password**: Authentication password |
| 11 | + |
| 12 | +##### User Credentials |
| 13 | +You need to add a user in Dicentis meeting application and give the user permissions, you can also log in as default admin as well. |
| 14 | +The permissions of logged in user will appear in log for viewing. |
| 15 | + |
| 16 | +#### Debug Messages |
| 17 | +- Enable debug messages to track WebSocket connections, API interactions, and system events |
| 18 | +- Debug logs provide detailed information about: |
| 19 | + - WebSocket connection status |
| 20 | + - Authentication attempts |
| 21 | + - API request and response details |
| 22 | + - Microphone state changes |
| 23 | + - Permission validation |
| 24 | +- Useful for troubleshooting connection issues, permission problems, and unexpected system behavior |
| 25 | + |
| 26 | +#### Variables |
| 27 | +- `$(dicentis:{seatName_screenLine})`: seatId - gives seatId of each seat for internal processing and for further possibilities to interact with triggers |
| 28 | +- `$(dicentis:Active_Microphone_screenLine)`: Indicates the active microphone's screenLine |
| 29 | +- `$(dicentis:Active_Microphone_screenName)`: Indicates the active microphone's screenName |
| 30 | + |
| 31 | + |
| 32 | +#### Actions |
| 33 | +- Toggle microphone for each seat |
| 34 | +- Activate/Deactivate individual microphones |
| 35 | +- Activate/Deactivate interpreter desks |
| 36 | +- Custom command for testing purposes |
| 37 | +- REST Request (GET/POST/PUT/DELETE with optional JSON body) for wireless REST API endpoints |
| 38 | + |
| 39 | +#### Permissions |
| 40 | + |
| 41 | +`canManageMeeting` |
| 42 | + In order to have canManageMeeting permission, web client seat needs to have Manage Meeting rights and logged in user needs to have activate meeting rights or logged in Participant needs to have manage meeting. |
| 43 | + |
| 44 | +`canControlInterpretation` |
| 45 | + In order to have canControlInterpretation permission, web client seat needs to have Manage Meeting rights, system should have special licenses, premium licenses or ultimate licenses and logged in user needs to have ActivateMeeting or logged in participant needs to have manage meeting. |
| 46 | + |
| 47 | +`canEditSynoptic` |
| 48 | + In order to have canEditSynoptic permission, logged in user needs to have ConfigureSystem rights. |
| 49 | + |
| 50 | +`canSelect` |
| 51 | + In order to have canSelect permission, logged in user needs to have ConfigureSystem rights. |
| 52 | + |
| 53 | +`canAddDevicesToSeats` |
| 54 | + In order to have canAddDevicesToSeats permission, logged in user needs to have ConfigureSystem rights. |
| 55 | + |
| 56 | +`canViewVoting` |
| 57 | + In order to have canViewVoting permission, system should have special licenses, premium licenses or ultimate licenses, the synoptic seat needs to have Can Vote, and Voting Scripts should be configured to have rights for External System. |
| 58 | + |
| 59 | +`canEnableSeatIllumination` |
| 60 | + In order to have canEnableSeatIllumination permission, logged in user needs to have ConfigureSystem rights. |
| 61 | + |
| 62 | +`canSwitchSystemPowerOn` |
| 63 | + In order to have canSwitchSystemPowerOn, web client seat needs to have Power On rights. Logged in participant needs to have manage meeting rights. |
| 64 | + |
| 65 | +`canSwitchSystemPowerOff` |
| 66 | + In order to have canSwitchSystemPowerOff, web client seat needs to have Power Off rights. Logged in participant needs to have manage meeting rights. |
| 67 | + |
| 68 | +`canViewRequestItems` |
| 69 | + In order to have canViewRequestItems, logged-in user either needs to have Manage Meeting rights or logged-in user needs to have Special permission. |
| 70 | + |
| 71 | +`canViewFirstRequestOnSeat` |
| 72 | + In order to have canViewRequestItems, logged in user either needs to have Manage Meeting rights or logged-in user needs to have Special permission. |
| 73 | + |
| 74 | +`canDeactivateMicrophone` |
| 75 | + This permission only gets enabled in Response mode, logged in user needs to have Manage rights. |
| 76 | + |
| 77 | +`hasSpecialPermission` |
| 78 | + In order to have hasSpecialPermission. Web client seat needs to have special permission. |
| 79 | + |
| 80 | +`canViewInterpretation` |
| 81 | + In order to have canViewInterpretation, Logged in user either needs to have Activate meeting rights. Logged in participant needs to have Manage Meeting rights. |
| 82 | + |
| 83 | +`canControlMasterVolume` |
| 84 | + In order to have canControlMasterVolume, web client seat needs to have Volume Control rights. Logged in user either needs to have Activate meeting rights. Logged in participant needs to have Manage Meeting rights. |
| 85 | + |
| 86 | +`canControlVoting` |
| 87 | + In order to have canControlVoting, system should have LVPM license, web client seat needs to have Voting Control rights. Logged in user needs to have Activate meeting rights. Logged in participant needs to have Manage Meeting rights and Vote rights. |
0 commit comments