Documentation Index
Fetch the complete documentation index at: https://docs.famulor.io/llms.txt
Use this file to discover all available pages before exploring further.
Genesys Cloud Integration
Connect a Genesys Cloud BYOC Carrier trunk to FamulorThis guide walks you through connecting Genesys Cloud (formerly Genesys Cloud CX / PureCloud) to Famulor using the BYOC Carrier external trunk model. Genesys generates an org-specific FQDN on its side, and Famulor exposes a unique SIP address you point Genesys at.
Two-leg setup: Genesys requires both an inbound termination identifier (so external traffic can land on your Genesys org from Famulor) and an outbound SIP server (so Genesys can reach Famulor for outbound). You configure both on the same External Trunk.
Step 1: Create the BYOC Carrier external trunk
- Sign in to Genesys Cloud Admin.
- Go to Admin → Telephony → Trunks → External Trunks → Create New.
- Trunk Type:
BYOC Carrier→ subtypeGeneric BYOC Carrier. - Name: e.g.
Famulor AI. - Trunk State:
In Service. - Protocol:
UDP(orTLSfor encrypted signaling — recommended).
Step 2: Inbound configuration
In the same trunk, fill in the Inbound section:famulor.byoc.usw2.pure.cloud. You will give this FQDN to Famulor in step 5.
Assign a Number Plan / Site that contains the DIDs you want the AI to handle.
Step 3: Outbound configuration (from Genesys → Famulor)
In the Outbound section, point Genesys at your Famulor SIP address:Find your Famulor SIP address: Famulor dashboard → Phone Numbers → Integrate SIP trunk → Our SIP address.
Step 4: SIP Access Control
Under the trunk’s SIP Access Control tab, whitelist Famulor’s SIP origin (LiveKit’s SIP egress range, available from Famulor support).Step 5: Import the number into Famulor
- Open your Famulor dashboard and go to Phone Numbers → Integrate SIP trunk.
-
Fill in:
-
Outbound settings:
- Authorization type: Username and password.
- Country: the country of the assigned DID.
Step 6: Verify
- Assign the number to a
Receive phone callsassistant. Call your Genesys DID — the AI should answer. - Create a
Make phone callsassistant with the same number and trigger an outbound test call.
Common issues
488 Not Acceptable Here
488 Not Acceptable Here
Codec mismatch. Genesys’s BYOC trunk supports PCMU, PCMA and G.722. Famulor’s LiveKit backend prefers PCMU/PCMA. Set the trunk’s codec preferences to PCMU first, PCMA second, and remove G.722 if you see this error persist.
Calls connect but no audio in either direction
Calls connect but no audio in either direction
RTP firewall. The trunk uses bidirectional RTP on UDP — make sure outbound UDP is open from Genesys to Famulor and that any corporate firewall in front of Genesys’s edge is not stripping RTP.
403 Forbidden on outbound
403 Forbidden on outbound
SIP Access Control rejection. Verify the Famulor egress IPs are in the trunk’s ACL list, and that the Realm/Username/Password match what you put into Famulor exactly.
Inbound calls go to the wrong queue
Inbound calls go to the wrong queue
Your Number Plan / Site assignment routes the DID. Check the Site has a matching Outbound Routes entry that maps the DID’s prefix to the Famulor BYOC trunk.
Need help with setup? Our support team can supply Famulor’s current SIP egress IP ranges and walk you through the Genesys ACL.

