Config Tweaks

The following configuration tweaks are optional. A restart of the RTC services is required if any changes to configs have been made.

Application Config (app.config)

Config Value	Description
`<add key="ConferenceScheduleTimeout" value="00:10:00" />` XML	Default value: 10 minutes, hh:mm:ss Should be increased if ICH is under heavy usage.
`<add key="IsActiveActiveIchSupported" value="true" />` XML	Default value: true, false Should be set if DefaultServiceEndpointSipUri is not configured on LUCS ICH side
`<add key="IsLucsConferenceUsageEnabled" value="false"/>` XML	Indicates if conference reservation for services is available, available in LUCS version >= 3.3
`<add key="ConferencePhoneIdFormat" value="pstnid:{conferencePhoneId}" />` XML	Optional, supported parameter {conferencePhoneId}, If this parameter wasn't specified this value will be used as prefix instead.
`<add key="PexipVersion" value="23" />` XML	Used only to determine if a transform_layout is needed. To disable this, please specify version less than 22

Content Security Policy (CSP)

The following CSP settings must be applied to your local site to enable requests to RTC Launcher

<meta http-equiv="Content-Security-Policy" content="script-src 'unsafe-inline' https://rtclauncherclient.domain.com; style-src 'unsafe-inline' https://rtclauncherclient.domain.com https://rtclauncherapi.domain.com; font-src https://rtclauncherclient.domain.com; img-src data: https://rtclauncherclient.domain.com https://rtclauncherapi.domain.com; connect-src https://rtclauncherclient.domain.com https://rtclauncherapi.domain.com; media-src  https://rtclauncherclient.domain.com">

XML

or

<meta http-equiv="Content-Security-Policy" content="default-src 'unsafe-inline' data: https://rtclauncherclient.domain.com https://rtclauncherapi.domain.com">

XML

where
https://rtclauncherclient.domain.com is the RTC Launcher Client URL specified during RTC Launcher Client Installation
https://rtclauncherapi.domain.com is the RTC Launcher API URL specified during RTC Launcher API Service Installation

Logging of API request headers

It's possible to enable logging for headers of all RTC Launcher API Service requests.

Make the following changes in log4net.config:

Change FileAppender_HeadersLog threshold from OFF to DEBUG:
```
<threshold value="DEBUG" />
```
XML

Change HeadersLogger level value from OFF to DEBUG:

<logger name="HeadersLogger" additivity="false">

    <level value="DEBUG" />

    <appender-ref ref="FileAppender_HeadersLog" />

</logger>

XML

Collected logs can be found in Logs\Headers.log file.

Change transport settings order for SignalR

By default, SignaIR uses transport options in the order of: 'webSockets', 'serverSentEvents', 'longPolling'.

You can change it with the third parameter in the bootstrap script:

This parameter should be an array of string items.Only valid items would be considered as a transport option for signalr, in other cases default options will be used.