Contribute in GitHub:

Accessing Voice Gateway images

IBM Voice Gateway images must be pulled from the public IBM Cloud Container Registry from April 24, 2023.

To install the ibmcloud CLI with the IBM Cloud Container Registry follow see Step 1 of these instructions.

For security and compliance concerns, an IBM Cloud account is now required to access the images. The following table shows the new image names and registry for each of the IBM Voice Gateway images:

Docker Hub Registry image name	ICR Registry image name
`ibmcom/voice-gateway-so`	`icr.io/voice-gateway/sip-orchestrator`
`ibmcom/voice-gateway-mr`	`icr.io/voice-gateway/media-relay`
`ibmcom/voice-gateway-sms`	`icr.io/voice-gateway/sms-gateway`
`ibmcom/voice-gateway-stt-adapter`	`icr.io/voice-gateway/stt-adapter`
`ibmcom/voice-gateway-stt-adapter`	`icr.io/voice-gateway/tts-adapter`
`ibmcom/voice-gateway-codec-g729`	`icr.io/voice-gateway/codec-g729`
`ibmcom/voice-agent-tester`	`icr.io/voice-gateway/agent-tester`
`ibmcom/voice-agent-insights`	`icr.io/voice-gateway/agent-insights`
`ibmcom/voice-agent-oidc-provider`	`icr.io/voice-gateway/agent-oidc-provider`

Accessing the images will depend on your deployment pattern.

Note: This only applies to non-CP4D deployments of IBM Voice Gateway.

Kubernetes or OpenShift deployments

For IBM Voice Gateway deployed in the IBM Cloud Kubernetes Service, only the image references need to be changed. No credentials need to be set up to access the images.

See Accessing IBM Voice Gateway images from Kubernetes or OpenShift

Docker Compose

See the Deploying to Docker. For more information on how to access the IBM Cloud Registry from Docker, see Registry Access.