Server-Specific Configuration
Set basic server settings on the LiveSwitch Console, but some server-specific settings are set in a configuration JSON file.
Each service has a configuration file in its install location:
- Gateway:
FM.LiveSwitch.Gateway.Service.config.json - Media Server:
FM.LiveSwitch.MediaServer.Service.config.json - SIP Connector:
FM.LiveSwitch.Connector.Sip.Service.config.json - Recording Monitor:
FM.LiveSwitch.Recording.Monitor.Service.config.json - Recording Mover:
FM.LiveSwitch.Recording.Mover.Service.config.json - Recording Muxer:
FM.LiveSwitch.Recording.Muxer.Service.config.json
These settings are available in every service's configuration JSON file:
Connection Strings
The ConnectionStrings section contains database connection strings to your PostgreSQL and Redis instances. This field is mandatory and all your LiveSwitch services must connect to the same database instances.
"ConnectionStrings": {
"Default": "postgresql://<postgresql_connection_string>",
"Cache": "redis://<redis_connecting_string>",
"RecordingStorage": "postgres://<postgresql_connection_string>",
"RecordingQueue": "amqp://<rabbitmq_connecting_string>"
}
Each connection string has its own format dependent on its system:
- PostgreSQL connection string format
- Redis connection string format
- RabbitMQ connection string format
If SSL is required for your PostgreSQL server, you must provide the Trusted Certificate SHA-1 Fingerprint in the configuration string:
"ConnectionStrings": {
"Default": "postgres://postgres-server-with-ssl-enabled",
"Cache": "redis://<redis_connecting_string>",
"RecordingStorage": "postgres://<postgresql_connection_string>",
"RecordingQueue": "amqp://<rabbitmq_connecting_string>"
},
"TrustedServerCertificateSha1Fingerprints": [ "trusted_sha1_fingerprint" ]
For example:
"ConnectionStrings": {
"Default": "postgresql://user:password@10.37.129.2:25061/postgres_server?sslmode=require&Server_Compatibility_Mode=Redshift",
"Cache": "redis://lxjis.redis.cache.windows.net:6380,password=2KfYkEQOCYH8sdfdsfdsfdsEdMV18nSvtE4FrMqnncAFZNsRc=,ssl=True,abortConnect=False",
"RecordingStorage": "postgres://user:password@10.37.129.2:5432/recording",
"RecordingQueue": "amqp://user:password@10.37.129.2:5672"
},
"TrustedServerCertificateSha1Fingerprints": [ "trusted_sha1_fingerprint" ]
To generate the fingerprint, download the trusted certificate file from the server and run this command:
openssl x509 -in ca-certificate.crt -outform DER | sha1sum
Note
This command requires that openssl and sha1sum are installed.
Deployment ID
deploymentId specifies the deployment configuration to use for this service. If this value isn't set, LiveSwitch uses the default deployment configuration.
"deploymentId": "Deployment1"
Region
Region specifies the region of the server.
"Region": "Europe"
Media Server Configuration
The Media Server configuration includes extra settings required for the embedded TURN Server.
External IP Address
The local IP addresses of the Media Server.
"External": {
"IPAddresses": []
}
Public IP Address
The IP address of the Media Server seen by remote clients. If this value isn't set, the external STUN URLs configured in the Deployment Configuration are used to retrieve it.
"External": {
"PublicIPAddress": ""
}
Public Hostname
The hostname of the Media Server. This value is mandatory if you have configured TURNS Bindings.
"External": {
"PublicHostname": ""
}
TURNS must have a public host name. All traffic to the Media Server must include this host name, which is then compared to the host name in your certificate. A TURNS connection can only happen when these two match.
Note
When you start a Media Server to accommodate increasing load, you must create the host name for the embedded TURNS server that the new Media Server uses. You must create the necessary DNS record and also supply the new host name as part of the TURNS configuration of the new Media Server. When you remove Media Servers, you can clean up the DNS records for the TURNS domain names that are no longer required.
Reset Configuration Console Password
You can reset the password to your LiveSwitch Console using the LiveSwitch command-line tool that's installed with your Gateways.