00 · Header
T5 · Dedicated Instance
Connectivity Options
Three official articles describe how a Dedicated Instance region is reached: Partner Connect, Virtual Connect, and Edge Connect. Each one assumes the region is already activated. T5-R02 keeps the peering deep dive.
01 · Executive summary
Five lines, then why it matters
- Partner Connect addressing is a public /31 or /30 per physical link, four subnets per geo for Direct and four for Equinix Fabric, a public or private ASN, and a /16 per geo for partner management of the UC applications. Link subnets are not routed outside the service. [cite:1]
- Partner Connect cannot carry Webex Calling and Meetings unless the customer also has the Dedicated Instance add-on. To carry those as well, the partner hosts a NAT server and an extra Dot1Q connection. The datacenter timeline is 10 business days. [cite:1]
- Virtual Connect private ASNs come from 64512 through 65534. Cisco assigns a public but not Internet-routable /24, split into two /25s, one per data center. The CPE advertises a default route on each tunnel. [cite:2]
- Only a Customer Full admin activates Virtual Connect. A Customer read-only admin can view status. One CPE with two tunnels is supported. Two CPEs is the recommended design. [cite:2]
- Link-priority communities on the current Edge Connect article run from 13445:200 through 13445:900, and 900 is the most desirable path. T5-R02 is the room that already walks the two-link rule in more depth. [cite:3]
02 · Architecture map
Three ways into a region
- 1Partner-aggregated private connection
- 2Internet VPN with a hard combined ceiling
- 3Private peering, two connections for Dedicated Instance
Mermaid source (not rendered)
flowchart LR CPE[Customer CPE] --> T1[Tunnel to DC1 /25] CPE --> T2[Tunnel to DC2 /25] T1 -.-> B[/24 backup/] T2 -.-> B
03 · Core concepts
Same region, three contracts
The partner aggregates customer networks and extends them to Dedicated Instance. Two options: a direct physical cross-connect at an Equinix facility, with VRF and BGP, or Equinix Cloud Exchange Fabric, a virtual connection from any Equinix Fabric location. Direct facilities are listed for North America, Europe, Australia, and APJC. Activate Dedicated Instance in the region before the peering request. [cite:1] re-check
An add-on. Point-to-point IP VPN over the internet using existing CPE. Each order in a region is two GRE-over-IPsec tunnels, one to each redundant data center. Bandwidth is 250 Mbps per tunnel and the article recommends it for smaller deployments. All cloud traffic passes the customer headend, so it may not suit many remote sites. Cisco hosts the redundant tunnels and internet access in the Dedicated Instance data center. The customer provides internet bandwidth, public IPs for two IPsec tunnels, and GRE transport addresses. Devices must support BGP and GRE over IPsec. [cite:2] re-check
The current article says Edge Connect bypasses the public Internet and connects to Webex Meetings, Webex Calling, and Webex Contact Center Enterprise data centers, through Equinix or Megaport. For an Edge Connect for Dedicated Instance link, the redundancy checkbox is mandatory, and the second connection goes to a different Webex data center in the region. A customer-story article says Edge Connect 3.0 can consolidate multi-tenant, Dedicated Instance, and Meetings over a single peering capability, and the same article says Cisco requires peering at two sites in a region. Keep both sentences. [cite:3] [cite:4]
The Partner Connect table says Fabric has 30 or more points in the Americas and EMEAR, and that APJC is targeted for Q1CY2020. That date is in the article retrieved on 2026-10-14. Treat the APJC timing as re-check, not as a current forecast. KSA partner connectivity options are stated as currently unavailable. [cite:1]
Side-by-side facts
| Question | Partner Connect | Virtual Connect | Edge Connect |
|---|---|---|---|
| Who orders the path | Partner, after the region is active. Control Hub: Calling, Dedicated Instance, Cloud Connectivity, Activate for Partner Connect. Provide region and Dot1Q tags. | Add-on SKU A-FLEX-DI-VC. Quantity must not exceed Dedicated Instance regions. One order per region. Customer Full admin activates. | Equinix or Megaport physical and data-link work, then the Edge Connect portal. Dedicated Instance requires two connections. |
| Bandwidth the article states | Direct 1 G or 10 G. Fabric 200 MB to 10 GB. | 250 Mbps per tunnel. Combined traffic must not exceed 250 Mbps. | The current article describes guaranteed bandwidth. It does not reuse the 250 Mbps ceiling. Do not copy Virtual Connect’s number here. |
| Addressing | Public /31 or /30 per link. Four subnets per geo. Public or private ASN. /16 per geo for UC app management. | Private ASN 64512–65534. Public, not Internet-routable /24, split into two /25s. | Public /30 or /31. Webex ASN 13445. Private prefixes such as RFC 1918 are not accepted. |
| Cite | [cite:1] | [cite:2] | [cite:3] |
04 · Ecosystem
What rides these links
Glossary
- Partner Connect
- Partner-aggregated private connection. Direct cross-connect or Equinix Fabric. [cite:1]
- Direct cross-connect
- Physical connection at Equinix. Charge is the physical connection. Two points per listed geo. 1 G or 10 G. [cite:1]
- Equinix Fabric
- Virtual connection. Charge for the physical connection and each virtual connection, one virtual connection per customer. 200 MB to 10 GB. [cite:1]
- Dot1Q
- Partner gear must support Layer 3 subinterfaces with dot1q. The partner provides a tag when activating a customer. [cite:1]
- Virtual Connect
- Two GRE-over-IPsec tunnels per region over the customer’s internet. Hub design. [cite:2]
- Dual-tier headend
- Virtual Connect routing and GRE on one device, IPsec on another. [cite:2]
- /25 per data center
- Cisco splits the assigned /24 into two /25s and advertises each over its tunnel. [cite:2]
- Edge Connect
- Private peering that bypasses the public Internet. Equinix or Megaport. ASN 13445. [cite:3]
- Link-priority community
- 13445:200 through 13445:900. 900 is the most desirable path. AS-path prepending is not supported with private ASNs. [cite:3]
- Edge Connect 3.0
- The customer-story article says one peering capability can carry multi-tenant, Dedicated Instance, and Meetings. Two sites in the region are still required. [cite:4]
- BFD
- Default 300 ms times 3 on Edge Connect for Dedicated Instance links, and the same default on Meetings and Calling links. [cite:3]
Mind map
Mermaid source (not rendered)
mindmap
root((Connectivity))
Partner Connect
Virtual Connect
Edge Connect
Sister matrix
| Sister | What the cited page says | Why it matters | Config touchpoint | Typical failure | Cite |
|---|---|---|---|---|---|
| Workforce management | None of the three connectivity articles size WFM. | A peering link does not provision agents. | py6u9h if the workload is contact center. | Sizing a tunnel from an agent forecast alone. | [cite:5] |
| Quality management and recording | Not in these connectivity articles. | Recording bandwidth is extra traffic on whichever tunnel you chose. | Add it to the Virtual Connect combined 250 Mbps test before you assume the link fits. | Ignoring recording when the failure case collapses onto one tunnel. | [cite:2] |
| E911, RAY BAUM, Kari, RedSky | Partner Connect’s application list includes Emergency Responder for the Americas only. The connectivity articles do not build the RedSky trunk. | The link has to exist before CER can be reached. The trunk names are in T5-R01’s base configuration. | T5-R01 for x-prefixed RedSky objects. | Expecting Partner Connect to enable CER outside the Americas. | [cite:1] |
| Analytics and reporting | Not a CUIC or Analyzer path in these articles. | Control traffic and media both count against Virtual Connect’s ceiling. | T5-R02 for the peering design already written. | Opening a report to debug a down BGP session. | [cite:2] |
| Salesforce, Dynamics 365, ServiceNow | Not named in the connectivity articles read here. | CRM screen-pops are application traffic, not a fourth connectivity product. TODO-verify any CRM-specific peering SKU. | The CRM guide after the link is up. | Ordering a fourth “CRM connect” option that these articles do not list. | [cite:1] |
| Virtual agents | Not a connectivity option. | Bot media still needs a path into the region. | T4-R10 if the bot is Webex CCE Hybrid IVR. | Treating Dialogflow as a substitute for the second tunnel. | [cite:2] |
| IVR and self-service | Edge Connect’s current opening sentence includes Webex Contact Center Enterprise data centers. | A contact-center media path can share the peering capability the 3.0 story describes, and still needs two sites. | n68tcpb and ny65x1bb together. | Using one Equinix site because the 3.0 sentence said “single.” | [cite:3] [cite:4] |
| Digital channels | Not provisioned by these VPN or peering articles. | Digital channel lists stay on the contact-center what’s-new page. | T4-R10. | Adding a messenger product to the Dot1Q form. | [cite:1] |
| Identity and SSO | Virtual Connect activation is limited to the Customer Full admin role. Read-only admin can view status. | That is a Control Hub role, not a phone-user IdP. | Control Hub roles before you hand the activation form to a read-only admin. | Asking a read-only admin to submit the Virtual Connect form. | [cite:2] |
Integration edges
| From | To | Mechanism | What moves | Cite |
|---|---|---|---|---|
| Partner edge | Equinix | Direct or Fabric | VRF and BGP. Customer networks the partner aggregates. | [cite:1] |
| Partner | Customer UC apps | /16 per geo | Management of the UC applications. Link /30s stay inside the service. | [cite:1] |
| CPE | Two Dedicated Instance data centers | GRE over IPsec, eBGP | Default route from the CPE. /25 from Cisco on each tunnel. | [cite:2] |
| Customer WAN | Webex backbone | Edge Connect | Public prefixes only. Communities 13445:200 through 13445:900 set local preference. | [cite:3] |
| One Edge Connect capability | Multi-tenant, Dedicated Instance, Meetings | Edge Connect 3.0 as described in the customer-story article | Consolidated peering. Two sites still required. | [cite:4] |
| Partner Connect | Webex Calling and Meetings | Extra Dot1Q plus partner NAT | Only when Dedicated Instance is also purchased. Otherwise the model cannot be used for Calling and Meetings. | [cite:1] |
Bridges
| This room | Neighbor | Peer label | Cite |
|---|---|---|---|
| Three options | T5-R02 already teaches two links, ASN 13445, and the Melbourne versus Sydney peering note. | T5-R01 defines the applications the link reaches. | [cite:3] |
| January 2025 Webex CCE early-access sentence | T4-R10 quotes it beside the current Edge Connect definition. | Do not import “Virtual Connect via VPN” into this room’s Edge Connect column. | [cite:3] |
| Customer aggregation examples | MPLS, SD-WAN including Viptela, Meraki, or another SD-WAN, and VPN such as DMVPN or site-to-site IPsec. | The article says the list is not exhaustive, and that VPN is not suitable for more advanced multi-site WANs. | [cite:1] |
Future hooks
- Re-read the Partner Connect APJC “Q1CY2020” cell before you tell someone Fabric is unavailable there. The sentence is old wording on a June 27, 2025 article.
- A peering questionnaire is named in partner process notes outside the article body used here. Steps that exist only on that questionnaire stay TODO-verify until that page is the source.
- Direct-site city pairs below are copied from the June 27, 2025 table and stay re-check.
Ecosystem troubleshooting
| Symptom | Likely mix-up | Check | Move | Cite |
|---|---|---|---|---|
| Virtual Connect falls over and the call quality collapses | Each tunnel was filled to 250 Mbps | Combined traffic must stay within 250 Mbps because one tunnel carries both | Lower the steady-state total, or move to another option. | [cite:2] |
| A private 10.x prefix is rejected on Edge Connect | RFC 1918 was advertised | The article says Edge Connect does not accept private prefix advertisements like RFC 1918 | Advertise provider-independent public space. | [cite:3] |
| Partner Connect was ordered for Meetings only | The add-on rule was skipped | Partner Connect cannot be used for Webex Calling and Meetings without Dedicated Instance | Add Dedicated Instance, or choose Edge Connect for those workloads. | [cite:1] |
| One Equinix site is declared enough because of Edge Connect 3.0 | “Single peering capability” was read as one site | The customer-story article still requires two sites in the region | Order the redundant connection. | [cite:4] |
05 · Flow
From an active region to a tested path
| Step | From | To | Mechanism | Notes | Cite |
|---|---|---|---|---|---|
| 1 | Dedicated Instance | The region | Activation | Required before a Partner Connect or Virtual Connect peering request. | [cite:1] [cite:2] |
| 2 | Partner | Control Hub | Activate for Partner Connect | Region and Dot1Q tag ranges. 10 business days in the Webex data centers. | [cite:1] |
| 3 | Customer Full admin | Virtual Connect form | Control Hub activation | Cisco configures its side, then the customer configures CPE. eBGP. | [cite:2] |
| 4 | CPE | Both data centers | Two tunnels | Active/active when healthy. Split toward each /25. | [cite:2] |
| 5 | Customer | Equinix or Megaport | Edge Connect layers | Physical, then data link, then BGP to Webex ASN 13445. | [cite:3] |
| 6 | Dedicated Instance order | Second data center | Redundancy checkbox | Mandatory. Different data center in the region. | [cite:3] |
06 · Config
Values you can copy from the articles
| Item | Option | Value | Cite |
|---|---|---|---|
| Direct city pairs | Partner Connect | Americas: Dallas and San Jose. EMEA: London and Amsterdam. APJC row in the table: Tokyo and Singapore. Australia: Sydney and Melbourne. EU: Frankfurt and Amsterdam. UK: Manchester and London. | [cite:1] re-check |
| KSA | Partner Connect | Partner connectivity options currently unavailable. | [cite:1] |
| Customer aggregation | Partner Connect | MPLS. SD-WAN (Viptela, Meraki, or other). VPN (DMVPN, site-to-site IPsec). VPN is called out as unsuitable for more advanced multi-site WANs. List is not exhaustive. | [cite:1] |
| Calling and Meetings on Partner Connect | Partner Connect | Host a NAT server and add a Dot1Q connection. Dedicated Instance add-on is required. | [cite:1] |
| Tunnel count | Virtual Connect | Two per region. One CPE with both tunnels is supported. Two CPEs, one tunnel each, is recommended. | [cite:2] |
| BGP | Virtual Connect | eBGP. CPE advertises a default route on each tunnel. Cisco is the neighbor on the GRE tunnel interface. | [cite:2] |
| ASN | Edge Connect | Webex public BGP ASN 13445. Customer may use a public or private ASN. Private ASN: Webex strips it after ingress, so use communities instead of AS-path prepending. | [cite:3] |
| Communities | Edge Connect | 13445:200, 300, 400, 500, 600, 700, 800, and 900. Higher local preference is more desirable. 900 is the most desirable path. | [cite:3] |
| BFD | Edge Connect | Default 300 ms times 3 for Dedicated Instance links and for Meetings and Calling links. | [cite:3] |
07 · Limits
Ceilings that must not be swapped
| Limit | Figure | Applies to | Cite |
|---|---|---|---|
| Direct bandwidth | 1 G or 10 G | Partner Connect cross-connect | [cite:1] |
| Fabric bandwidth | 200 MB to 10 GB | Partner Connect Equinix Fabric | [cite:1] |
| Datacenter lead time | 10 business days | Partner Connect activation | [cite:1] |
| Subnets per geo | 4 | Direct and Fabric, public /31 or /30 links | [cite:1] |
| Management block | /16 per geo | Partner management of UC applications | [cite:1] |
| Tunnel bandwidth | 250 Mbps | Each Virtual Connect tunnel, and the combined total | [cite:2] |
| Orders per region | One | Virtual Connect. Quantity cannot exceed Dedicated Instance regions. | [cite:2] |
| Private ASN range | 64512–65534 | Virtual Connect, assigned by Cisco | [cite:2] |
| Dedicated Instance connections | Two | Edge Connect redundancy checkbox is mandatory | [cite:3] |
| Advertised prefixes | Public, provider-independent | Edge Connect rejects RFC 1918 | [cite:3] |
| Sites per region | Two | Even when Edge Connect 3.0 consolidates services on a peering capability | [cite:4] |
08 · Troubleshooting
Rows you can check against the option you bought
| Symptom | What to inspect | What the page implies | Cite |
|---|---|---|---|
| Peering request is refused | Whether Dedicated Instance is activated in that region | Both Partner Connect and Virtual Connect say to activate first. | [cite:1] [cite:2] |
| Virtual Connect activate button is missing | Control Hub role | Customer Full admin activates. Read-only admin can only view status. | [cite:2] |
| One tunnel down and the far data center is unreachable | Whether the CPE still has the /24 backup and a default route on the live tunnel | Cisco uses the /24 and its internal WAN when a /25 tunnel is down. | [cite:2] |
| Remote sites are slow on Virtual Connect | Whether they hairpin through the hub CPE | The article says this may not suit many remote sites. Cisco is not responsible for the customer WAN back to the hub. | [cite:2] |
| Private ASN prepending does nothing on Edge Connect | Community versus AS-path | Webex strips a private ASN after ingress. Use link-priority communities. | [cite:3] |
| A second Dedicated Instance connection was left unchecked | The redundancy checkbox | It is mandatory for an Edge Connect for Dedicated Instance link. | [cite:3] |
| KSA partner links are missing | The availability note | The article says partner connectivity options are currently unavailable in KSA. | [cite:1] |
09 · Self-question
Twelve rungs
L0Which three articles define the options in this room?
Partner Connect, Virtual Connect, and Edge Connect. [cite:1] [cite:2] [cite:3]
L1What must already be true before a Partner Connect or Virtual Connect request?
Dedicated Instance is activated in that region. [cite:1] [cite:2]
L1What are the two Partner Connect bandwidth pairs?
Direct is 1 G or 10 G. Fabric is 200 MB to 10 GB. [cite:1]
L2Why is Virtual Connect’s combined ceiling equal to one tunnel?
Failover puts all traffic on the remaining tunnel, and that tunnel is 250 Mbps. [cite:2]
L2What does the CPE advertise on Virtual Connect?
A default route on each tunnel. Cisco advertises a /25 per data center. [cite:2]
L2Which Control Hub role activates Virtual Connect?
Customer Full admin. Read-only admin can view status. [cite:2]
L3What is Webex’s public BGP ASN, and what prefix length is the peering link?
13445. A public /30 or /31. [cite:3]
L3Which community is the most desirable Edge Connect path?
13445:900. The set runs from 13445:200 through 13445:900. [cite:3]
L3Can Partner Connect carry Meetings without Dedicated Instance?
No. The article says it cannot be leveraged for Webex Calling and Meetings without the Dedicated Instance add-on. [cite:1]
L4How do you hold both Edge Connect 3.0 sentences at once?
One peering capability can carry multi-tenant, Dedicated Instance, and Meetings. Cisco still requires two sites in the region. [cite:4]
L4What happens to a private ASN on Edge Connect?
Webex strips it after ingress. AS-path prepending is not supported. Use link-priority communities. [cite:3]
10 · Lab
Paper lab: pick one option and refuse the other ceilings
11 · Quiz
Twelve checks
Partner Connect Direct bandwidth is:
- 1 G or 10 G
- 250 Mbps combined
- A /25
- 300 ms
Reveal
A. Fabric is 200 MB to 10 GB. [cite:1]
Virtual Connect tunnels per region are:
- Two GRE-over-IPsec tunnels
- One unprotected GRE tunnel
- Eight call-processing servers
- A single /16
Reveal
A. [cite:2]
Both Virtual Connect tunnels are up and each is carrying 200 Mbps. What does the failure rule say?
Reveal
Combined traffic must not exceed 250 Mbps, because failover puts everything on one tunnel. This design is over the ceiling. [cite:2]
Cisco’s Virtual Connect private ASN range is:
- 64512 through 65534
- 13445 only
- 1 through 100
- Any public ASN the customer picks, assigned by Cisco as public
Reveal
A. 13445 is the Webex public ASN on Edge Connect. [cite:2]
Edge Connect’s Webex public BGP ASN is:
- 13445
- 64512
- The customer’s only
- Not published
Reveal
A. [cite:3]
For Dedicated Instance, the Edge Connect redundancy checkbox is:
- Mandatory, and the second link goes to a different data center
- Optional
- Only for Meetings
- A Virtual Connect setting
Reveal
A. [cite:3]
The most desirable link-priority community is:
- 13445:900
- 13445:200
- 64512:900
- There is no community
Reveal
A. [cite:3]
Edge Connect 3.0 is described as one peering capability for multi-tenant, Dedicated Instance, and Meetings. How many sites does that article still require?
Reveal
Two sites in the region. [cite:4]
Partner Connect for Webex Calling and Meetings without Dedicated Instance is:
- Not allowed by the article
- The default
- Free with Fabric
- The same as Virtual Connect
Reveal
A. [cite:1]
Who can activate Virtual Connect?
- Customer Full admin
- Any read-only admin
- The end user
- Only a phone
Reveal
A. [cite:2]
Draw Virtual Connect addressing.
Reveal
One /24, split into two /25s, one advertised per data center. CPE sends a default route on each tunnel. [cite:2]
Edge Connect rejects:
- Private prefix advertisements such as RFC 1918
- Public /30s
- BGP
- Equinix
Reveal
A. [cite:3]
12 · Audio
Slots for Studio
Transcript slot
Studio fills this from the cites.
Transcript slot
Studio fills this from the cites.
Transcript slot
Studio fills this from the cites.
13 · Interview
Oral answers
30 seconds. Dedicated Instance has three connectivity articles. Partner Connect is the partner’s aggregated private connection. Virtual Connect is two GRE-over-IPsec tunnels over the internet. Edge Connect is private peering through Equinix or Megaport. I activate the region before I request the first two.
2 minutes. Partner Connect Direct is a 1 or 10 gigabit cross-connect. Fabric is 200 megabits to 10 gigabits, and each customer needs a virtual connection. Addressing is a public /30 or /31, four subnets per geo, and a /16 for managing the UC apps. I cannot use Partner Connect for Calling and Meetings unless Dedicated Instance is on the order, and then I still add NAT and another Dot1Q tag. The data-center work is quoted as 10 business days. KSA is called out as unavailable.
30 seconds, Virtual Connect. Two tunnels, 250 Mbps each, and the sum also stays at 250 Mbps because a failure lands everything on one tunnel. Cisco gives me a private ASN from 64512 to 65534 and a /24 cut into two /25s. My CPE sends a default route.
2 minutes, Edge Connect. Webex ASN 13445. My peering subnet is a public /30 or /31. I do not advertise RFC 1918. If I use a private ASN, Webex strips it, so I steer with communities from 13445:200 up to 13445:900. A Dedicated Instance link must check redundancy and land on two data centers. Edge Connect 3.0 can put multi-tenant, Dedicated Instance, and Meetings on one peering capability, and the article that says so still requires two sites. Partner Connect and Virtual Connect were updated in 2025, so those rows stay re-check. The Edge Connect header I used is September 17, 2026.
What you will not say. You will not put the 250 Mbps ceiling on an Edge Connect order, and you will not drop the second site because a sentence said “single peering.”
14 · Citations
Ledger
Retrieved 2026-10-14. Study notes from public sources.
- Dedicated Instance Partner Connect — help.webex — article 74f47cb — header June 27, 2025 — Partner Connect. Direct and Fabric, bandwidth, addressing, Dot1Q, 10 business days, NAT note, KSA, aggregation examples, application list including Emergency Responder for the Americas. re-check
- Dedicated Instance Virtual Connect — help.webex — article v8jhcv — header September 22, 2025 — Virtual Connect. Two GRE-over-IPsec tunnels, 250 Mbps, /24 and /25s, private ASN range, eBGP default route, Customer Full admin, SKU A-FLEX-DI-VC, hub design. re-check
- Webex Edge Connect — help.webex — article n68tcpb — header September 17, 2026 — Webex Edge Connect. Private peering to Meetings, Calling, and Webex Contact Center Enterprise data centers. ASN 13445. Public /30 or /31. RFC 1918 rejection. Communities 13445:200 through 13445:900. Mandatory redundancy for Dedicated Instance. BFD 300 ms times 3.
- Dedicated Instance – customer deployment models — help.webex — article ny65x1bb — header August 4, 2025 — Customer deployment models. Edge Connect 3.0 can consolidate multi-tenant, Dedicated Instance, and Meetings. Cisco still requires two sites in a region. re-check
- Webex WFO: Feature Specific SKUs — help.webex — article py6u9h — help.webex.com article py6u9h. WFO scope. Not a connectivity design.
15 · Re-engineer later
Still open
- Open questions: the Partner Connect peering questionnaire steps are TODO-verify until that article is the source. A CRM-specific peering SKU is TODO-verify.
- Facts still marked re-check: Partner Connect (June 27, 2025), Virtual Connect (September 22, 2025), the customer-story article (August 4, 2025), and the APJC Q1CY2020 wording.
- Assets missing: three-option SVG export, audio, a redacted Control Hub connectivity card.
- Ideas for v1.0: a ceiling card that prints 250 Mbps only in the Virtual Connect column.
- Next review: re-read 74f47cb and v8jhcv when Cisco updates them. n68tcpb was current on September 17, 2026 at retrieval.
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 Partner Connect last checked 2026-10
- Vendor doc Virtual Connect last checked 2026-10
- Vendor doc Webex Edge Connect last checked 2026-10
- Vendor doc Customer deployment models last checked 2026-10
- Vendor doc help.webex.com article py6u9h last checked 2026-10
sources.json for this page.