> For the complete documentation index, see [llms.txt](https://docs-conversational-ai.syntphony.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-conversational-ai.syntphony.com/channels/add-a-channel/genesys-cloud-cx.md).

# Genesys Cloud CX

Connect Genesys Cloud CX to Syntphony CAI through Voice Gateway. This lets Genesys route calls to your virtual assistant and receive transferred calls back.

This guide supports Genesys Cloud CX only. For Genesys Engage, contact Syntphony CAI Technical Support.

### Basic configuration

Set up the SIP trunk, inbound numbers, call routing, and number plan. These settings establish the connection between Genesys and Voice Gateway.

Voice Gateway supports these preconfigured Genesys regions:

* Europe (Ireland) — `euw1`
* South America (São Paulo) — `sae1`
* Canada (Central) — `cac1`

#### Add the Genesys SIP trunk to Voice Gateway

First, ask Syntphony CAI Technical Support to configure the Genesys SIP trunk and assign your virtual assistant in Voice Gateway.

Submit your request through the support portal:

{% embed url="<https://shori-public.clonika.com/>" %}

Attach the configuration file and complete the **Template DNIS** tab.

<figure><img src="https://4008706377-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fn6zS4HeuuVpRHZEvDiFU%2Fuploads%2FRHpcaTkmTkQqmUEipuwi%2Fimage.png?alt=media&amp;token=07c404d9-8b95-4c5a-8368-549d05493885" alt=""><figcaption></figcaption></figure>

Select **Genesys Pure Cloud** as the origin. You do not need to complete **Customer SBC Data**.

After the configuration is ready, Technical Support provides the values needed in Genesys.

#### Create the voice connection in Genesys

1. **Add the Voice Gateway SIP trunk**

   In Genesys, go to **Admin → Telephony → Trunks → External Trunks**. Add the Voice Gateway SIP trunk using the values provided by Technical Support.

   Configure these fields:

   * **External Trunk Name** — the name shown for this trunk in Genesys
   * **Inbound SIP Termination Identifier** — the unique termination URI for your Genesys region. Voice Gateway uses it to send SIP traffic to Genesys
   * **SIP Servers or Proxies** — add at least one Voice Gateway port. Genesys sends outbound SIP requests to this address
   * **SIP Access Control** — add all three Voice Gateway IP addresses.

   <figure><img src="https://4008706377-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fn6zS4HeuuVpRHZEvDiFU%2Fuploads%2FTi5BCMULcFYtEBpJIPlR%2Fimage.png?alt=media&amp;token=06f188d4-e607-45d6-ae80-1da55831a916" alt=""><figcaption></figcaption></figure>
2. **Configure DID numbers**

   Go to **Telephony → DID Numbers**. Assign each number to a person, phone, or call flow. If callers enter a queue, assign the number to the relevant call flow.

   <figure><img src="https://4008706377-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fn6zS4HeuuVpRHZEvDiFU%2Fuploads%2FCk7jSezLmDrc9Rf8ea4n%2Fimage.png?alt=media&amp;token=32b42dc6-6f81-4217-8883-6ad6af1e923e" alt=""><figcaption></figcaption></figure>
3. **Create call routes**

   Go to **Architect → Flows** and create an **Inbound Call** flow. Define whether the call goes to a number or a queue.

   <figure><img src="https://4008706377-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fn6zS4HeuuVpRHZEvDiFU%2Fuploads%2FNTnITPjhJuIkT6c6u1rX%2Fimage.png?alt=media&amp;token=f207e921-2018-451c-981c-322c90ddc7a2" alt=""><figcaption></figcaption></figure>
4. **Configure a number plan**

   Go to **Telephony → Sites → Number Plans** and configure a number plan. You need this number when configuring the Genesys SIP trunk in Voice Gateway.

   <figure><img src="https://4008706377-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fn6zS4HeuuVpRHZEvDiFU%2Fuploads%2FoLqeq1R1GqdHDm62GQYx%2Fimage.png?alt=media&amp;token=181b9523-2532-45b5-bd1a-904ee9677458" alt=""><figcaption></figcaption></figure>

### Transfer calls from Syntphony to Genesys

Transfer a call back to Genesys when a caller needs a human agent. Configure the handover in your Syntphony CAI voice flow.

Add a cell response. In its technical text field, add the SIP details for the [**call transfer**](https://docs-conversational-ai.syntphony.com/scai-voice-gateway/design-voice-interactions/control-what-happens-next.md#transfer).

Use the `transfer` property. Replace the quoted values with your destination details.

<figure><img src="https://4008706377-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fn6zS4HeuuVpRHZEvDiFU%2Fuploads%2FStpk43pyw3AyyJj3Zbr8%2Fimage.png?alt=media&amp;token=c2022ae7-e07c-4957-877a-f66573b6ab2f" alt=""><figcaption></figcaption></figure>

`dest` sets the transfer destination. `uui` sends a custom message in the SIP User-to-User header.

In Genesys Architect, filter by UUI to identify returned calls. To route by DID number, use a separate dedicated number.

<figure><img src="https://4008706377-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fn6zS4HeuuVpRHZEvDiFU%2Fuploads%2FmPMmwvyDfyIlUR8EDnp0%2Fimage.png?alt=media&amp;token=c3339569-1e00-4462-bfdc-e05499baabfa" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs-conversational-ai.syntphony.com/channels/add-a-channel/genesys-cloud-cx.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
