Contribute in GitHub:

Setting up a multi-tenant JSON configuration

In a multi-tenant JSON configuration, a single IBM® Voice Gateway instance can host multiple tenants, or phone numbers that customers can call. For example, from a single Voice Gateway instance, an insurance provider might provide one phone number for car insurance and another phone number for homeowners insurance. Because there's only a single deployment, a multi-tenant JSON configuration offers simpler, centralized administration over deploying multiple single-tenant environments, where each instance corresponds with a particular phone number.

Multitenancy is supported in Version 1.0.0.2 and later by using an advanced JSON configuration.

Configure the tenants in a JSON file

Tenant configuration is specified and stored in a separate JSON file, which is then referenced in the Voice Gateway configuration. Configuration that isn't related to a tenant, such as server configuration, continues to be specified in the core Voice Gateway configuration. By separately specifying the tenant configuration as JSON objects, distinct configuration settings can be mapped to each individual tenant.

For detailed information and a list of all tenant configuration properties, see Configuring tenants in a multi-tenant JSON configuration.

Deploy your multi-tenant JSON configuration

You can deploy your multi-tenant JSON configuration on-premises with Docker Engine, in IBM Cloud Pak for Data, or in the public cloud with IBM Cloud Kubernetes Service. For more information, see Deploying a multi-tenant JSON configuration.

After you deploy Voice Gateway, each tenant is available at the configured tenant URI. When using a JSON configuration file, only calls to the specified tenants can connect, effectively whitelisting the configured tenants.

Configuring multiple service providers

To support disaster recovery and ensure no interruption of service in the event of a Watson service provider failure, you can configure IBM® Voice Gateway to support multiple Watson services. See Configuring multiple service providers.