Home / Cloud voice and CCaaS SIP / Genesys BYOC and NICE CXone SIP
Genesys BYOC and NICE CXone SIP
BYOC Cloud and BYOC Premises can be combined. NICE CXone documents SIP trunks on 5060 and 5061 with dynamic RTP and SRTP. Confirm carrier details with NICE.
Learn in 5 minutes
- Separate BYOC Cloud from BYOC Premises
- Keep the hardware date on the Genesys Hardware Solution
- State CXone ports without inventing a BYOC menu
Visual
December 1, 2026 applies to the Genesys Hardware Solution.
Worked example
Whose date is it? Play the BYOC Cloud ladder, then answer from the Premises article rather than from the SIP itself.
- Play the four hops.
- Notice RTP addresses are public stand-ins.
- Apply the hardware date only where the article puts it.
Vendor menus, ports, and license names change. Confirm before relying on a sentence that is not an RFC.
Fault
A maintenance plan decommissions Customer Hardware Edges on December 1, 2026 because that date appears in the BYOC Premises article.
The article names one hardware program.
Quiz
Ecosystem
Glossary, sister systems, and the integration seam for this room.
Workforce management WFM forecasts volume and builds schedules. It consumes contact-center events. It does not parse Via headers. When a forecast is wrong, the SIP symptom is usually queue delay and 480 or carrier congestion, not a broken dialog ID.
Programmable communications APIs Twilio’s docs home is API reference, tutorials, and integration for Twilio products. Elastic SIP Trunking is the SIP-shaped product already cited in this lab. This page does not define the word CPaaS from an RFC. Read the vendor page before you copy a diagram that uses that word.
Sources and go deeper
- Genesys BYOC Cloud overview — last checked 2026-10
- About BYOC Cloud — last checked 2026-10
- About BYOC Premises — last checked 2026-10
- BYOC Cloud with BYOC Premises — last checked 2026-10
- NiCE CXone connectivity — last checked 2026-10
- NiCE CXone ports — last checked 2026-10