00 · Header

T5 · Dedicated Instance

DI Architecture & Peering

Color-coded sequence: Site → Peering → Dedicated UC → Calling. A packet moves along the arrows. Reduced motion keeps every step visible.

Dedicated Instance is a regional Unified CM stack you activate on purpose. Peering is two Edge Connect links, not a diagram with one happy line. This room keeps both the two-link rule and the Edge Connect 3.0 sentence that talks about a consolidated path.

Room T5-R02 Version v0.1 last-verified: TODO Difficulty L3 Est. time 90–110 min Prereq T2-R02 Reading 18 min

01 · Executive summary

Five lines, then why it matters

Dedicated Instance is an optional Webex Calling add-on. Activating a region is permanent, and the first voice service domain sticks. [cite:1]
Activation deploys Unified CM, Unity Connection, Expressway Core and Edge, and Emergency Responder only in AMER. The access article also names IM and Presence and optional SME. [cite:1] [cite:2]
There are no new EMEA deployments. Choose EU or UK. [cite:1]
Edge Connect peers through Equinix or Megaport. Webex ASN 13445. Your peering subnet is a public /30 or /31. Dedicated Instance orders need two connections. [cite:3]
Do not steer every DI prefix at one link. Each data center advertises its own /25. Private ASN prepending is stripped. [cite:4] [cite:3]

Why it matters. A design review fails when someone orders one link, prepends a private ASN, or treats EMEA as still open. Those three are documented, not taste.

02 · Architecture map

Two data centers, two links

Mermaid source (not rendered)

flowchart LR
  CE[Customer edge] --> EC[Edge Connect]
  EC --> DC1[Data center A]
  EC --> DC2[Data center B]

03 · Core concepts

What is dedicated, and what is peered

Not multi-tenant calling

Multi-tenant Webex Calling does not hand you a Unified CM publisher. Dedicated Instance does, inside the region you activated. [cite:1] [cite:2]

Two lists of applications

Activation names four deploy items, with Emergency Responder only in AMER. The access article’s architecture list also includes IM and Presence and optional SME. Teach both lists. Do not merge them into one sentence. [cite:1] [cite:2]

Two links, and also a 3.0 sentence

Order and practice articles require two Dedicated Instance connections to two data centers. The deployment-model article says Edge Connect 3.0 can put multi-tenant, Dedicated Instance, and Meetings on one peering capability, and describes a customer who used one peer toward DI and WxCCE. Keep both. A single physical link is still the wrong order. [cite:3] [cite:4] [cite:5]

Melbourne ASN cell

Most rows in the location table print Cisco ASN 13445, which matches the Edge Connect article. The Melbourne row prints 399937. Retrieved again on 2026-10-14. The Melbourne cell still prints 399937. Sydney still prints 13445. Edge Connect still states public BGP ASN 13445. Both prints stay. Do not type 399937 as the Edge Connect public ASN. [cite:6] [cite:3]

Pairs the location article names

Region table	Locations printed	Note	Cite
AMER	Los Angeles 011, Ashburn 021	LA UC network printed 69.168.17.0/24 and per-DC 69.168.17.0/25	[cite:6]
APJC	Singapore 051, Tokyo 062	ASN cell 13445 on the Singapore row	[cite:6]
AUS	Melbourne 071, Sydney 081	Retrieved again 2026-10-14. Melbourne ASN cell still prints 399937. Sydney still prints 13445. Both prints stay.	[cite:6]
EU	Frankfurt 141, Amsterdam 143	New EU pair. Not the frozen EMEA table.	[cite:6]
UK	London 133, Manchester 131	Separate from the EMEA London/Amsterdam rows.	[cite:6]
KSA	Jeddah 231, Riyadh 233	Jeddah IaaS cell prints Coming soon.	[cite:6]
EMEA	London 031/032, Amsterdam 041/042	Heading: no new customer deployments.	[cite:6] [cite:1]

04 · Ecosystem & sister technologies

Glossary, map, sisters, edges

Mini map of the neighbors named on this room’s sequence. Orientation sketch, not a new product claim.

Glossary

Dedicated Instance: An optional add-on to Webex Calling. You purchase it before activation. It is a private-cloud UC stack for a region, not the multi-tenant calling service. [cite:1]
Region activation: Once a region is activated it cannot be reversed or moved. The voice service domain from the first region applies to later regions in the same Control Hub org. The UC applications domain cannot be changed after submit or activate. [cite:1]
EMEA freeze: The activation article says there are no new Dedicated Instance deployments in the EMEA region. Choose EU or UK. [cite:1]
Unified CM: Deployed and sized at activation from the professional, standard, and workspace counts you enter for that region. [cite:1]
Unity Connection: Deployed with the region. Listed again on the application-access article. [cite:1] [cite:2]
Expressway: Expressway Core and Edge are part of the activation set and of the application list. Expressway Edge is the node the access article ties to a public IP. [cite:1] [cite:2]
Emergency Responder: Deployed only in the AMER region. [cite:1] [cite:2]
IM and Presence: Named in the application-access article as part of the architecture. The activation article’s numbered deploy list that this pass read is Unified CM, Unity Connection, Expressway, and Emergency Responder in AMER. Do not treat those two lists as the same sentence. [cite:2]
SME: Session Management Edition is optional. The cluster can span regions. It is listed under the publisher’s region on Manage. [cite:2]
UC application pane: Calling → Dedicated Instance → Manage → UC application. It shows datacenter, voice service domain, and the Expressway Edge public IP. [cite:2]
Over-the-top launch: You can cross-launch the UC apps from Control Hub before peering is finished, so onboarding of the apps can start. [cite:2]
Service list: The access article lists Provisioning (publisher only), Call Processing, CTI Manager, Music on Hold, and TFTP. Application changes sync on a 24-hour schedule. [cite:2]
Edge Connect: Private peering through Equinix or Megaport from the customer edge to the Webex backbone. [cite:3]
Webex BGP ASN: The Edge Connect article states the Webex public BGP ASN is 13445. [cite:3]
Peering subnet: Customer BGP peering link address space is a public IP with a /30 or /31 prefix. [cite:3]
Two DI links: The migration-practice article says two Dedicated Instance links are a must. Four links are an option in pairs, and crossing is not allowed. Do not prefer one link for DI traffic. Each data center advertises its own /25. [cite:4]
Redundancy checkbox: For an Edge Connect for Dedicated Instance order, the redundancy option is mandatory so the second connection lands in a different Webex data center in the region. [cite:3]
Data-center pair: Primary and secondary Dedicated Instance data centers are grouped as a pair in each region. Either site in the pair can be primary. [cite:3]
Private ASN prepend: AS-PATH prepending is not supported with private ASNs, because Webex strips the ASN after ingress. The article points at link-priority communities instead. [cite:3]
Link-priority community: Edge Connect honors 13445:200, 13445:300, and 13445:400 as local preference 200, 300, and 400. [cite:3]

Mind map

Mermaid source (not rendered)

mindmap
  root((Dedicated Instance))
    UC apps
    Edge Connect
    Regions

Sister-technology matrix

Sister	What it is	Why it matters here	Config touchpoint	Typical failure	Cite
Multi-tenant Webex Calling	The shared calling cloud, not this private UC stack.	Users can exist in both designs. Compare Calling → Dedicated Instance → Manage with the multi-tenant locations. They are different objects, and the mixed dial plan is T5-R05 because the activation article does not print one.	Open Calling → Dedicated Instance → Manage for the private UC apps, and the multi-tenant location for the shared cloud. Coexistence dial-plan detail is T5-R05 because the two products keep separate objects.	Treating a DI region activation as a multi-tenant location.	[cite:1]
Local Gateway	The customer SBC for PSTN in the deployment-model stories.	ny65x1bb uses a local gateway for PSTN on both DI and the contact-center side of one customer story.	Do not paste the sample LGW password from the IOS article into a DI trunk.	[cite:5]
Webex Contact Center Enterprise	A different product from multi-tenant WxCC.	The same customer story says one Edge Connect 3.0 peer can reach DI and WxCCE. That sentence does not cancel the two-link DI rule.	Read both articles before you order one link.	[cite:5] [cite:4]
Webex Meetings	Edge Connect also carries Meetings routes.	A DI order can include Meetings and Calling. Route filters belong in the Edge Connect article, not in a CUCM route pattern.	Filtering to a stale prefix list.	[cite:3]
Survivability / WAN	Peering is the private path. It is not phone registration through a local gateway.	Calling endpoints still do not register through LGW. DI phones register to the dedicated Unified CM.	Pointing phones at the peering subnet as if it were TFTP for multi-tenant MPP.	[cite:2]
Emergency calling	CER is in the AMER deploy list only.	Other regions are not given a CER node by the activation article.	Assuming CER exists in EU because the AMER cluster has it.	[cite:1]
Identity	Control Hub still owns the org. UC apps have their own admin pages.	Cross-launch is over the top. LDAP inside Unified CM is not Directory Connector.	Compare the SSO attribute in Control Hub with LDAP on the dedicated Unified CM. They are separate directories, so an attribute name in one does not fill a field in the other.	[cite:2]
BGP communities	How you influence return-path preference.	13445:200, :300, and :400.	Prepending a private ASN and expecting it to survive.	[cite:3]

Integration map

From	To	Mechanism	What moves	Cite
Customer router	Equinix or Megaport	Layer 1 and 802.1Q	Physical cross-connect, or a circuit to a facility that colocates with Webex, or a remote connection when your facility does not.	[cite:3]
Cloud exchange	Webex backbone	BGP	Customer ASN, Webex ASN 13445, public /30 or /31 on the peering link.	[cite:3]
Each DI data center	Customer	Advertised /25	The practice article says each side advertises its unique /25 and you must not prefer one link.	[cite:4]
Control Hub	UC application	Cross-launch	Onboarding can start before peering is complete.	[cite:2]
Publisher region	SME subscribers	Manage pane	The cluster is listed where the publisher lives. Subscribers in other regions show in the right pane.	[cite:2]
Dedicated Instance	Webex Meetings and multi-tenant	Edge Connect 3.0	The deployment-model article says one peering path can carry those services. DI redundancy articles still require two connections.	[cite:5] [cite:3]
Local gateway	PSTN	SIP	In the cited customer story both DI and WxCCE use a local gateway for PSTN.	[cite:5]
UC app change	Control Hub view	24-hour sync	The access article schedules the sync every 24 hours.	[cite:2]

Cross-platform bridges

This room	Legacy	Peer orientation	Cite
Dedicated Unified CM	On-premises CUCM is the familiar admin model. Open CSS on the dedicated Unified CM and LDAP on that same cluster. A help page does not print a field crosswalk because those screens change with the UC application version.	Teams Phone is not this private cluster. No parity matrix.	[cite:2]
Edge Connect	An MPLS WAN into an on-prem publisher is a different design. Do not reuse its QoS numbers here.	A cloud-exchange provider is Equinix or Megaport in the article, not a generic VPN claim.	[cite:3]
CER in AMER	On-prem CER is a product you may already run. The cloud deploy statement is AMER-only.	Emergency vendors on other platforms stay unnamed.	[cite:1]

Future-integration hooks

Canon plan: T5-R03 can go deeper on partner connect. This room already holds the peering rules those pages must not contradict.
Prefix lists on the Edge Connect page change. The February 25, 2026 note on that article added Calling ranges. re-check any copied prefix. [cite:3]
Check Calling → Dedicated Instance → Manage against the multi-tenant locations when a user exists in both. The mixed dial plan is T5-R05 because the activation article does not print coexistence patterns.

Ecosystem troubleshooting

Symptom	Likely sister-system cause	Check	Fix	Cite
Meetings work on the peering and DI does not	DI still needs its two regional connections and its own /25s.	Order type versus a Meetings-only link.	Confirm the solution was Edge Connect for Dedicated Instance, with two data centers.	[cite:3] [cite:4]
WxCCE and DI were drawn as one cluster	They are different products that can share an Edge Connect 3.0 peer in the customer story.	ny65x1bb versus the UC application list.	Peer them. Do not merge the admin planes.	[cite:5]
Firewall uses a prefix list from last year	Advertisements change. The article says not to filter on a prefix list.	Allow 500 routes. Prefix length ≤ /24 is the encouragement.	Rebuild policy from the current network requirements.	[cite:3]
Publisher was made a call-processing subscriber	The guideline says not to start CallManager on the publisher.	CM group membership across both data centers.	Move call processing onto subscribers in both data centers.	[cite:7]

05 · Flow

From purchase to a routed call

Step	From	To	Mechanism	Notes	Cite
1	Subscription	Region	First Time Setup	Counts of professional, standard, and workspace devices size that region. The sum cannot exceed the subscription.	[cite:1]
2	Cisco	UC apps	Deploy	Unified CM, Unity Connection, Expressway, CER in AMER.	[cite:1]
3	Administrator	App UI	Cross-launch	Allowed before peering completes.	[cite:2]
4	Customer	Equinix or Megaport	Physical and 802.1Q	Cross-connect, building circuit, or remote connection.	[cite:3]
5	Customer BGP	Webex ASN 13445	eBGP	Public /30 or /31. Allow about 500 routes.	[cite:3]
6	Data center	Customer	Prefix advertisement	Unique /25 per data center. No single-link preference.	[cite:4]
7	Phone	Unified CM	Registration	To the dedicated call-processing nodes, in a CM group that spans both data centers.	[cite:7]
8	PSTN	Local gateway	SIP	The deployment-model story uses the local gateway for PSTN on the DI side.	[cite:5]

06 · Config

Order and router facts you can cite

Purchase Dedicated Instance, then activate only the regions you will keep. Enter professional, standard, and workspace counts. Standard appears only if it was ordered. [cite:1]
Do not plan an EMEA activation for a new customer. Choose EU or UK. [cite:1]
Open Calling → Dedicated Instance → Manage → UC application to see datacenter, voice service domain, and Expressway Edge public IP. [cite:2]
Order Edge Connect for Dedicated Instance with redundancy. Pick a primary and secondary data center in the regional pair. [cite:3]
On the customer router, run BGP and 802.1Q. Peer with Webex ASN 13445. Use a public /30 or /31. [cite:3]
Accept Webex routes. The article asks you to allow 500 routes and discourages prefix-list filters. If you must influence return preference, use community 13445:200, 13445:300, or 13445:400. [cite:3]
Build CM groups with nodes from both data centers. Do not start the CallManager service on the publisher. [cite:7]

Edge Connect peering (n68tcpb / tf6kpq). No customer secrets.
  provider:          Equinix | Megaport
  webex asn:         13445
  customer asn:      public or private (private prepend will be stripped)
  link addresses:    public /30 or /31
  di connections:    2, different data centers in the region
  optional 4:        pairs only, no crossing
  di prefixes:       unique /25 advertised by each data center
  communities:       13445:200 | 13445:300 | 13445:400
  route budget:      allow 500 from Webex

07 · Limits

What is quantified

Item	Value	Source	Verified?
Region move after activation	Cannot be reversed or moved	[cite:1]	Quoted
New EMEA	No new deployments	[cite:1]	Quoted
DI Edge Connect links	Two required	[cite:3] [cite:4]	Quoted
Webex public ASN	13445	[cite:3]	Quoted
Peering link	Public /30 or /31	[cite:3]	Quoted
Routes to allow	500 recommended	[cite:3]	Quoted as a recommendation
DI prefix per data center	Unique /25	[cite:4]	Quoted
UC pane sync	Every 24 hours	[cite:2]	Quoted
Melbourne ASN cell	Prints 399937. Sydney prints 13445. Retrieved again 2026-10-14. Both prints stay.	[cite:6]	Quoted on retrieval
Jeddah IaaS	Coming soon, as printed	[cite:6]	re-check
Max regions or users	Read the subscription and the region you activated under Calling → Dedicated Instance. The activation article prints no user or region cap, and the first region cannot be moved, so scale follows the order.	Not taken from a sizing calculator in this pass	Open

08 · Troubleshooting

Ten design failures

Symptom	Likely cause	Evidence	Fix	Cite
Activation will not move to another region	The region choice is permanent.	Activation article: cannot be reversed or moved.	Activate the region you mean. Later regions keep the first voice service domain.	[cite:1]
A new customer asks for EMEA	No new EMEA deployments.	The activation article names EU or UK instead.	Pick EU or UK. The old EMEA rows in the location table are labeled no new deployments.	[cite:1] [cite:6]
Only one DI peering link was ordered	Redundancy is mandatory for Dedicated Instance Edge Connect.	Order guide: two connections, two data centers.	Order the pair. Do not select a single connection for that solution.	[cite:3]
Return traffic ignores a private-ASN prepend	Webex strips a private ASN on ingress.	Edge Connect routing section.	Use link-priority communities 13445:200, :300, or :400.	[cite:3]
One link is preferred for all DI subnets	The practice article says that prioritization is not supported.	Each data center’s /25.	Accept both advertisements. Do not engineer all DI prefixes toward one link.	[cite:4]
Four links were crossed between pairs	Four links are allowed only as pairs. Crossing is not allowed.	Practice article.	Keep each pair intact.	[cite:4]
CER is missing in EU	Emergency Responder is deployed for AMER only, in the articles read here.	Activation list and the access article.	Do not expect the AMER node list in EU.	[cite:1]
Control Hub UC status looks empty on day one	Peering can still be in progress. Cross-launch is allowed before it finishes. Sync is every 24 hours.	Manage pane versus the app you cross-launched.	Use the app for onboarding. Wait for the documented sync before you call the pane wrong.	[cite:2]
A prefix filter blocked a new Webex route	The Edge Connect article says advertisements change and customers should not filter on a prefix list.	Allow 500 routes. Accept prefixes ≤ /24.	Build firewall policy from the network-requirements pages, not from a copied prefix list in this room.	[cite:3]
Phones were aimed at the local gateway to register	Registration to Dedicated Instance Unified CM is not registration through the local gateway.	T2’s registration fact, plus this room’s UC apps.	Register to the dedicated call-processing node. Use the gateway for the PSTN role the deployment story describes.	[cite:5]

09 · Self-question ladder

Twelve rungs

L1What do you buy before you can activate Dedicated Instance?

The optional add-on. Activation is not available as a substitute for the purchase. [cite:1]

L1Which UC applications does the activation article say it deploys?

Unified CM, Unity Connection, Expressway Core and Edge, and Emergency Responder only in AMER. [cite:1]

L2Can you move a live region to another region later?

No. The activation article says it cannot be reversed or moved. [cite:1]

L2What happens to the voice service domain on the second region?

The domain from the first activation applies to later regions in that org, and the UC applications domain cannot be edited after submit or activate. [cite:1]

L2Why is EMEA not a choice for a new customer?

The activation article says there are no new Dedicated Instance deployments in EMEA. Choose EU or UK. [cite:1]

L3Where do you open the UC applications?

Calling → Dedicated Instance → Manage → UC application. Cross-launch works before peering is done. [cite:2]

L3How many Edge Connect links does Dedicated Instance require?

Two. The redundancy option is mandatory on that order, and the practice article calls two links a must. [cite:3] [cite:4]

L3What ASN does Edge Connect publish for Webex?

13445. Retrieved again on 2026-10-14, the location table still prints 13445 on most rows and 399937 on Melbourne. Both prints stay. [cite:3] [cite:6]

L4What prefix do you use on the BGP peering link itself?

A public /30 or /31. That is the link subnet, not the UC application /25. [cite:3]

L4Why does a private ASN prepend fail?

Webex strips the private ASN after ingress. Use the local-preference communities instead. [cite:3]

L5How can one sentence say a single Edge Connect 3.0 path and another require two DI links?

ny65x1bb describes consolidating services on the Edge Connect 3.0 capability, including a single peer used for DI and WxCCE in that customer story. n68tcpb and tf6kpq still require two Dedicated Instance connections to two data centers. Quote both. Do not delete either. [cite:5] [cite:3] [cite:4]

L5What must a CM group contain?

The deployment guidelines say a CM group must include Unified CM nodes from both data centers in the region, and that you should not start the CallManager service on the publisher. [cite:7]

10 · Lab

A paper lab. Do not activate a region to learn this.

Goal: read a DI order and a peering design without activating a production region.
Prereq: a design packet, not a customer org you do not own. Activation is permanent. [cite:1]
Step 1. Write the region. If the packet says EMEA for a new customer, stop. Expected: EU or UK.
Step 2. Count Dedicated Instance Edge Connect connections. Expected: two, in a regional pair, redundancy selected.
Step 3. Write the peering subnet size and Webex ASN. Expected: public /30 or /31, ASN 13445.
Step 4. Confirm you are not steering every DI /25 at one link.
Evidence: the pair of data-center names, the community you would use instead of a private prepend, and the CM-group note.
Break it: design a single link and a private-ASN prepend. Recovery: restore two links and a 13445 community.
Reflection: which sentence about “one peering path” you still have to keep beside the two-link rule.

11 · Quiz

Twelve questions

Q1MCQ

Dedicated Instance activation is:

Answer

An optional add-on you purchase first. A region cannot be moved after activation. [cite:1]

Q2MCQ

Emergency Responder is deployed where?

Answer

Emergency Responder is deployed where: AMER only, in both the activation article and the application-access article. [cite:1] [cite:2]

Q3MCQ

New customers who wanted EMEA are told to choose:

Answer

New customers who wanted EMEA are told to choose: EU or UK. [cite:1]

Q4MCQ

Webex public BGP ASN on the Edge Connect article is:

Answer

Webex public BGP ASN on the Edge Connect article is: 13445. [cite:3]

Q5MCQ

The customer’s BGP peering addresses are:

Answer

The customer’s BGP peering addresses are: Public address space with a /30 or /31. [cite:3]

Q6Scenario

Someone prepends a private ASN so Webex prefers link A. What does the article say happens?

Answer

Webex strips the private ASN. Use 13445:200, :300, or :400 instead. [cite:3]

Q7Scenario

All DI prefixes are local-pref’d onto one of the two regional links. What is wrong?

Answer

All DI prefixes are local-pref’d onto one of the two regional links. What is wrong: The practice article says DI traffic prioritization toward one link is not supported, because each data center advertises its own /25. [cite:4]

Q8MCQ

How often does the access article say UC application data syncs to the Control Hub view?

Answer

How often does the access article say UC application data syncs to the Control Hub view: Every 24 hours. [cite:2]

Q9Scenario

Peering is not up and the partner wants to start Unity Connection. Is cross-launch allowed?

Answer

Yes. The access article says you can cross-launch over the top until peering is complete. [cite:2]

Q10MCQ

SME is listed under which region?

Answer

The publisher’s region. Subscribers elsewhere are in the right pane. [cite:2]

Q11Draw

Name the AMER pair and one UC prefix the location article prints for Los Angeles.

Answer

Los Angeles (data center id 011) and Ashburn (021). Los Angeles UC application network is printed as 69.168.17.0/24, and the per-data-center prefix as 69.168.17.0/25. re-check before you build a filter. [cite:6]

Q12Scenario

A design starts the CallManager service on the publisher to “use the node.” What does the deployment guideline say?

Answer

Do not. Additional services such as CallManager on the publisher can affect scale. CM groups must include nodes from both data centers. [cite:7]

12 · Audio

Slots for Studio

Transcript slot

Studio fills this. The prompt is the spoken outline, not a second article.

Transcript slot

Studio fills this. The prompt is the spoken outline, not a second article.

Transcript slot

Studio fills this. The prompt is the spoken outline, not a second article.

13 · Interview

Oral answers

30 seconds. Dedicated Instance is a purchased add-on that deploys a regional Unified CM, Unity Connection, and Expressway pair. Emergency Responder is in the AMER list. You do not get to move the region later.

2 minutes. Peering is Edge Connect on Equinix or Megaport. Webex ASN is 13445. You bring a public /30 or /31 and two connections to the two data centers. Each data center advertises its own /25, so preferring one link is unsupported. Private ASN prepending is stripped. Communities 13445:200, 300, and 400 set local preference.

30 seconds, the contradiction people hear. One article shows Edge Connect 3.0 carrying several services, including a single peer used toward DI and WxCCE. The order articles still require two DI connections. You quote both.

2 minutes, operations. Cross-launch the UC apps before BGP is up. The Control Hub pane syncs every 24 hours. CM groups include both data centers. You do not run CallManager on the publisher. SME, if you bought it, is listed in the publisher’s region.

What you will not say. You will not type 399937 as the Edge Connect public ASN. Retrieved 2026-10-14, Melbourne still prints 399937 and Sydney still prints 13445. You will not publish the location table as a firewall ACL.

14 · Citations

Activate Dedicated Instance — help.webex — article nefkee9 — help.webex.com article nefkee9 — retrieved 2026-10-14. Optional add-on. Region cannot be reversed or moved. First voice service domain sticks. No new EMEA deployments; choose EU or UK. Deploys Unified CM, Unity Connection, Expressway Core and Edge, and Emergency Responder only in AMER.
Access Dedicated Instance applications from Control Hub — help.webex — article n2hzeox — help.webex.com article n2hzeox — retrieved 2026-10-14. Application list includes IM and Presence and optional SME. Path Calling → Dedicated Instance → Manage → UC application. Cross-launch before peering. Services include publisher-only provisioning. Sync every 24 hours.
Webex Edge Connect — help.webex — article n68tcpb — help.webex.com article n68tcpb — retrieved 2026-10-14. Equinix or Megaport. Public or private customer ASN. Public /30 or /31 peering. Webex ASN 13445. Allow 500 routes. Private ASN prepend is stripped. Communities 13445:200, :300, :400. Dedicated Instance orders require two connections.
Best practices in preparation and migration to Webex Calling Dedicated Instance — help.webex — article tf6kpq — help.webex.com article tf6kpq — retrieved 2026-10-14. Two DI links are a must. Four links only in pairs; crossing is not allowed. Do not prioritize DI traffic onto one link. Each data center advertises its own /25.
Dedicated Instance – customer deployment models — help.webex — article ny65x1bb — help.webex.com article ny65x1bb — retrieved 2026-10-14. Edge Connect 3.0 can carry multi-tenant, Dedicated Instance, and Meetings. The same article describes one peer used for Dedicated Instance and Webex Contact Center Enterprise, and local gateways for PSTN.
Dedicated Instance data center locations — help.webex — article nx91ljh — help.webex.com article nx91ljh — retrieved 2026-10-14. Pairs include Los Angeles/Ashburn, Singapore/Tokyo, Melbourne/Sydney, Frankfurt/Amsterdam, London/Manchester, Jeddah/Riyadh, plus an EMEA table marked no new customer deployments. Prefixes are in that table. Melbourne’s Cisco ASN cell prints 399937 beside 13445 on other rows.
Dedicated Instance deployment guidelines — help.webex — article 0ppivs — help.webex.com article 0ppivs — retrieved 2026-10-14. CM groups must include nodes from both data centers in the region. Do not start the CallManager service on the publisher.

15 · Re-engineer later

Open questions: full IM and Presence deploy timing versus the activation list; KSA IaaS when “Coming soon” changes.
Check the region under Calling → Dedicated Instance, the dial plan in T5-R05, and CSS plus LDAP on the dedicated Unified CM. Those values vary by subscription and by UC version, and these articles do not freeze them.
Assets missing: Manage-pane screenshot, peering SVG export, audio.
Ideas for v1.0: a one-page pair table generated from nx91ljh at review time, with the review date in the caption.
Next review: re-check prefixes. The Melbourne ASN cell was retrieved 2026-10-14 and still prints 399937 beside Sydney 13445.

Sources and go deeper

Checked links were opened this month. A confirm row has no address because that page was not opened.

Wikipedia Webex (Wikipedia) last checked 2026-10
Vendor doc Webex Help Center last checked 2026-10
DevDocs Webex developer documentation last checked 2026-10
DevDocs Webex developer getting started last checked 2026-10
Community Webex community last checked 2026-10
SRND Cisco Collaboration design zone last checked 2026-10
RFC RFC 3261 SIP: Session Initiation Protocol last checked 2026-10
Port table IANA service name and port number registry last checked 2026-10
Port table Port reference for Webex Calling last checked 2026-10
Release notes What's new in Webex Calling last checked 2026-10
Vendor doc help.webex.com article nefkee9 last checked 2026-10
Vendor doc help.webex.com article n2hzeox last checked 2026-10
Vendor doc help.webex.com article n68tcpb last checked 2026-10
Vendor doc help.webex.com article tf6kpq last checked 2026-10
Vendor doc help.webex.com article ny65x1bb last checked 2026-10
Vendor doc help.webex.com article nx91ljh last checked 2026-10
Vendor doc help.webex.com article 0ppivs last checked 2026-10

sources.json for this page.