Skip to main content

Sites

Navigation: Admin → Telephony → Sites Last verified: Genesys Cloud Resource Center — March 2026


What Is a Site?

A site is the home of a set of phones. It defines the telephony dialing properties, call classification rules, and outbound routing rules for the phones assigned to it. Every phone in Genesys Cloud belongs to a site, and the site determines where calls go and how numbers are interpreted.

Sites are used across all telephony deployment models: BYOC Cloud, Genesys Cloud Voice, and BYOC Premises.

⚠️ The Media Model (Cloud or Premises) cannot be changed after site creation. Choose carefully.


Site Tabs

TabPurpose
GeneralDescription, default site toggle, media regions, Relay/TURN behavior, outbound caller ID
Number PlansClassify and normalize dialed numbers; default plans provided; max 200 per site
Outbound RoutesRoute calls to external trunks; Sequential or Random distribution
Simulate CallValidate routing configuration without placing an actual call

Navigation

TaskPath
Open sitesAdmin → Telephony → Sites
Create siteSites → Create New
Configure General settingsSites → [Site] → General
Add number plansSites → [Site] → Number Plans
Create outbound routeSites → [Site] → Outbound Routes
Run call simulatorSites → [Site] → Simulate Call

Creating a Site — Field Reference

Create Form

FieldDescriptionNotes
Site NameUnique name for the siteRequired
LocationLocation assigned to the siteOnly locations marked as available for sites appear; required
Time ZoneTime zone for the siteRequired
Media ModelCloud or PremisesCannot be changed after creation

General Tab

FieldDescriptionNotes
DescriptionFree-text descriptionOptional
Make this Site my default SiteSets org-wide defaultOnly one default site allowed
Media RegionsSelect media regions for WebRTC / Global Media FabricRelevant for WebRTC deployments
Relay/TURN BehaviorControls TURN relay region selection for WebRTC callsTwo options: Any media region set on this site / Lowest latency via Geo-Lookup
Caller AddressOutbound caller numberMust be in E.164 format
Caller NameOutbound caller nameText

Number Plans Tab

Genesys provides default number plans. Custom plans can be added to control what users can dial and how numbers are normalized before route selection. Maximum of 200 number plans per site.

Outbound Routes Tab

FieldDescription
Route NameName for the outbound route
ClassificationNumber plan classification this route handles
External Trunk(s)One or more trunks the route uses
DistributionSequential (ordered failover) or Random (load distribution)
StateEnable/disable the route

Simulate Call Tab

Enter a destination number or SIP address and click Simulate. The tool validates:

  • Number normalization
  • Number plan classification
  • Outbound route selection
  • Trunk settings
  • In-service Edges (BYOC Premises)
  • Destination site

ℹ️ Simulate Call validates configuration but does not place an actual call.


Media Model Selection

DeploymentMedia Model
BYOC CloudCloud
Genesys Cloud VoiceCloud
BYOC PremisesPremises

Step-by-Step: Create a Site

StepAction
Step 1Navigate to Admin → Telephony → Sites
Step 2Click Create New
Step 3Enter Site Name, select Location, Time Zone, and Media Model
Step 4Click Create Site
Step 5On General, add description and optionally set as default site
Step 6Configure Caller Address (E.164) and Caller Name
Step 7Configure Media Regions and Relay/TURN Behavior if using WebRTC
Step 8Add number plans on Number Plans tab
Step 9Create one or more outbound routes on Outbound Routes tab
Step 10Run Simulate Call to validate routing before going live

Key Constraints

ConstraintDetail
Media ModelCannot be changed after creation
Location availabilityOnly locations marked available for sites appear in the selector
Default siteOnly one site can be the default
Number plans per siteMaximum 200
Caller Address formatMust be E.164 (e.g. +528181234567)

Troubleshooting

IssueCauseResolution
Location not visible in selectorLocation not marked as available for sitesUpdate the location setting
Caller ID not displaying correctlyCaller Address not in E.164 or overridden by Prioritized Caller SelectionRecheck format and caller selection config
Calls not routingNumber plan or outbound route mismatchUse Simulate Call to trace normalization, classification, and route selection
No route selectedRoute disabled or no matching classificationVerify route state, classification, and selected trunks
Simulator shows failureSite, trunk, Edge, or destination settings incompleteReview each simulator output field in order

Quick Reference

QuestionAnswer
What is a Site?The home of a set of phones; defines classification, routing, and dialing rules
What are the four tabs?General, Number Plans, Outbound Routes, Simulate Call
What media models exist?Cloud and Premises
Can you change the media model later?No
What does Simulate Call do?Validates routing config without placing a real call
What distribution patterns exist for outbound routes?Sequential and Random
What format must Caller Address use?E.164

Naming Convention

ResourceExample
Cloud siteMTY_Main_Cloud
Premises siteMTY_Branch_Prem
Outbound routePSTN_Main
Number planMX_National_Dialing

Pattern: <Location>_<Purpose>_<MediaModel>


See Also

  • Trunks — create trunks before configuring outbound routes
  • Locations & Floor Plans — locations must exist before creating sites
  • Edges & Edge Groups — BYOC Premises sites use Edge assignments
  • WebRTC Phone Management — Media Regions and Relay/TURN Behavior are configured here
  • Architectural Build Order — Sites are built in Phase 2

Screenshots