CanonT2

00 · Header

Calling security & compliance

Gateway Calling T2-R06 PhoneControl HubCUBEPSTN
Illustrated scene for Calling Security & Compliance. Original drawing, not a product screenshot.
Sequence · Phone → Control Hub → CUBE → PSTN PhoneControl HubCUBEPSTN 123
Color-coded sequence: Phone → Control Hub → CUBE → PSTN. A packet moves along the arrows. Reduced motion keeps every step visible.

T2-R06. Commercial TLS and SRTP, opportunistic Calling E2EE, the recording-provider conflict, and RedSky for Calling and for WxCC WebRTC. Retrieved 2026-10-14.

Reading 11 minDraftStudy notes

01 · TL;DR

Three locks, and they do not stack

  • Secure SIP is TLS 1.2 or 1.3. Media suite in that article is AES_CM_128_HMAC_SHA1_80. [cite:1]
  • Calling E2EE is off until you enable it, and recording turns it back off. [cite:2]
  • The recording article names both Webex and Dubber as the default. [cite:3]
  • WebRTC agents reach 911 through RedSky. Test with 933. [cite:5]

02 · Map

What protects a call

03 · Core

Keep the articles in their lanes

jwkbt2, header April 28, 2026, lists TLS 1.2 and TLS 1.3 and the SRTP key AES_CM_128_HMAC_SHA1_80. Certificates need Server Authentication EKU; Webex does not require Client Authentication EKU. The FQDN in the CN or SAN must match Control Hub, without the port. The SRV example advertises port 5061 for endpoint edge discovery. That is not trunk destination 5062 or 8934. [cite:1] [cite:4]

5h5d8ab, header July 13, 2026, says Webex Calling currently uses SRTP. Calling E2EE is opportunistic and disabled by default. Enable it under Services > Calling > Settings, Webex App tab, Security, “Enable end-end encryption when making calls.” It is not enabled for 1:1 PSTN calls, including between organizations, or for 1:1 premises trunks. A conference mixer drops it. Recording, auto attendant, voice portal, pre-answer early media, connected-line privacy, and an assistant answering for an executive prevent it. Call queue may allow it after an agent connects. Shared and virtual lines do not get it. Escalating to a meeting ends the Calling E2EE session. Zero-trust meetings are a different mechanism: MLS, up to 1000 participants, no PSTN or SIP devices, and no in-meeting AI Assistant or network recording. [cite:2]

nhvl4hw tells you to select the provider before enabling users, and it contains both default sentences. Webex retention is one year and 100 GB. Dubber Go is 30 days. Do not paste either number onto contact-center QM. [cite:3]

nvfbjts, header September 08, 2024, is the WxCC WebRTC procedure: Calling or the $0 PSTN add-on plus Contact Center, RedSky password at least 16 characters, buildings, alerts, wiremap, 933, then Enhanced emergency calling. RedSky access tests. Emergency call routing activates. The agent’s identification type is Device User Id equal to the email. b2exve, revision line February 23, 2026 and still present on the October 14 retrieval, names the RedSky hosts on port 443. [cite:4] [cite:5]

04 · Ecosystem

Ecosystem and sister technologies

PhoneControl HubCUBEPSTN This room
Mini map of the neighbors named on this room’s sequence. Orientation sketch, not a new product claim.
TLS 1.2 and 1.3
The SIP security article’s supported TLS versions for secure SIP. [cite:1]
SRTP suite
AES_CM_128_HMAC_SHA1_80 is the SRTP key the same article lists for secure media. [cite:1]
Calling E2EE
Opportunistic. Disabled by default. Calls start on SRTP and upgrade when clients support it and nothing forces media processing. [cite:2]
end-end encryption toggle
The article’s hyphenation. Services > Calling > Settings > Webex App tab > Security. [cite:2]
Recording defeats E2EE
Call recording makes the service process media, so E2EE is disabled. [cite:2]
Webex recording provider
nhvl4hw says both “Webex is the default value” and “Dubber is chosen by default.” Quote both. Retention one year and 100 GB. [cite:3]
Dubber Go
30 days, with a user portal, in the same recording article. [cite:3]
RedSky
Emergency provider for Webex Calling and for WxCC WebRTC desktops. Hosts api.wxc.e911cloud.com and wxc.e911cloud.com, port 443. b2exve does not name TCP on that row. [cite:4] [cite:5]
933
nj0abhbb, header September 24, 2025, says United States and Canada locations dial 933 to test emergency-call email generation without alerting public safety personnel. That sentence is the Calling notification test. nvfbjts, header September 08, 2024, says place 933 calls, then activate Emergency call routing, and uses RedSky access to test location configuration. Read nvfbjts before you say whether that WxCC 933 call reaches a PSAP. The article does not say. re-check [cite:5] [cite:6]
Device User Id
For a contact-center agent in RedSky, the identification type must be Device User Id and it must equal the agent email. Then install myE911. [cite:5]
Kari and RAY BAUM
nvfbjts: direct 911, internal notification, and a dispatchable location for WebRTC desktops that have no traditional phone. [cite:5]
mTLS FQDN
The certificate CN or SAN must match the Control Hub FQDN. The article’s example strips :5061 off london.lgw.cisco.com. [cite:1]
Server Authentication EKU
Supported alone. Webex does not require Client Authentication EKU. Some third-party SBCs reject that certificate. [cite:1]
Edge SRV port 5061
The nslookup example in jwkbt2 advertises 5061 for endpoint discovery. Trunk destinations in the port reference are 5062 and 8934. Do not merge them. [cite:1] [cite:4]
Zero-trust meetings
MLS, up to 1000 participants. PSTN and SIP devices are not in those meetings. In-meeting AI Assistant, NBR, and transcription need decrypted media and are not in ZT meetings. Not the same switch as Calling E2EE. [cite:2]
Government cloud
Read the government port and crypto page on help.webex.com before you build an ACL. Commercial and government clouds publish different destinations, which is why this room keeps them apart.

Sister-technology matrix

SisterWhat it isWhy it mattersConfig touchpointTypical failureCite
TLS / SRTPCommercial Calling media and signalingTLS 1.2 and 1.3. SRTP AES_CM_128_HMAC_SHA1_80.jwkbt2Assuming a 256-bit GCM SRTP suite because a TLS cipher is 256-bit.[cite:1]
Calling E2EEOpportunistic upgrade from SRTPOff until the Webex App toggle is saved.Services > Calling > SettingsLeaving recording on and expecting the shield.[cite:2]
Zero-trust meetingsMLS meeting key the service cannot readEnds when a Calling call escalates to a meeting.Meeting type, not the Calling toggleTeaching meeting ZT as the trunk cipher.[cite:2]
Webex recordingOne provider sentenceOne year, 100 GB.Services > Calling > Settings > ServicesIgnoring the Dubber-default sentence in the same article.[cite:3]
Dubber GoThe other provider sentence30 days.Same provider controlPasting 30 days onto WxCC QM.[cite:3]
RedSkyE911 location and routingPort 443 to the two wxc.e911cloud.com hosts. b2exve does not name TCP on that row.Calling emergency settings, and nvfbjts for WebRTC agentsActivating routing before a 933 test.[cite:4] [cite:5]
WxCC WebRTCAgents with no desk phoneNeeds Calling or the $0 PSTN add-on, plus Contact Center.nvfbjts readiness checkDialing 911 from a browser with no RedSky user.[cite:5]
Local GatewaymTLS trunkFQDN in CN/SAN. Server EKU is enough for Webex.Control Hub trunkPutting :5061 into the certificate name.[cite:1]
Workforce managementpy6u9h, header June 09, 2026, lists WFO SKUs for Webex Contact Center Enterprise, Contact Center Enterprise, and Contact Center Express.Those SKUs are not a Calling TLS setting and are not a multi-tenant license.Leave A-FLEX-WFO-NWFM2 on the products that sentence names.Adding a WFO SKU because E2EE was turned off for recording.[cite:8]
AnalyticsAnalyzer’s clock is not this Calling security page. Real-time reports stay available, a new one refreshes every 5 seconds, and the drop-down is 5 to 60 seconds in steps of 5. Historical reports stay active 8 hours.A recording retention number is not a report refresh.Read tajemk when the question is a WxCC visualization. Read nhvl4hw when the question is Calling storage.Using the 8-hour Analyzer session as the Dubber Go retention.[cite:9]
CRMThe Dynamics 365 connector is a WxCC screen pop. CIF 1 is single-session. CIF 2 is multi-session. On-premises Dynamics is not supported.It does not change TLS 1.2, TLS 1.3, or the SRTP suite.Channel host wxcc-crmconnectors.ciscoccservice.com.Expecting the connector to encrypt the trunk.[cite:10]
AI agentss0qro1, header August 25, 2026, limits autonomous voice-agent access to specific customers. nvvv1zb, header October 06, 2026, is the paid Agent Desktop add-on.Neither article is the Calling E2EE toggle.Keep the E2EE decision on 5h5d8ab. Build agents only where those articles say.Turning on Calling E2EE and expecting the AI Assistant icon to appear.[cite:11] [cite:12]
Google CCAIn6gaghu: configure the Google CCAI connector in Control Hub and create a CCAI configuration. The config ID is for Flow Control.That is WxCC virtual-agent voice. It is not a Calling certificate.Dialogflow CX or ES through that connector. Do not put the config ID on the local gateway.Treating a Dialogflow project as the trunk trustpool.[cite:13]
Amazon ConnectNo Amazon Connect connector is named in jwkbt2, 5h5d8ab, or n6gaghu.Search help.webex.com for an Amazon Connect connector before you copy a flow. These Calling security articles do not name one, and an Amazon contact flow is not the E2EE toggle.Do not copy an Amazon flow into the Calling security settings.Using an Amazon contact flow as the E2EE design.[cite:13]
Teams callingn0l9q2z, header July 08, 2026, uses Cisco Call inside Teams. Sign-in is Teams SSO, then Webex. The Teams email or UPN should match the Control Hub primary email.Presence sync is not SRTP, and it is not Dynamics 365 Contact Center.Allow Cisco Call under Teams apps > Manage apps. Pin it in a setup policy. Control Hub: Webex App tab, Microsoft Teams integration, Presence sync. Unified CM backends need 12.5 SU7 or 14 SU3.Sign-in fails when the IdP SAML attributes do not resolve to a Webex user. VDI requires Cisco Call and Teams in the same virtual machine.[cite:14]

Integration edges

FromToMechanismWhat movesCite
Webex AppSRTPDefault Calling mediaAES_CM_128_HMAC_SHA1_80[cite:1]
SRTPCalling E2EEUpgrade when the toggle is on and the call type allows itDowngrade if the service must process media[cite:2]
Call recordingSRTPRecording disables E2EEProvider is still Webex or Dubber[cite:2] [cite:3]
Phone or Webex clientRedSkyPort 443. b2exve does not name TCP on that row.api.wxc.e911cloud.com and wxc.e911cloud.com[cite:4]
933RedSky testDoes not alert public safetyThen enable Emergency call routing[cite:5]
Agent emailRedSky Device User IdIdentification type for a contact-center agentThen myE911[cite:5]
EndpointEdge SRV_sips._tcp example advertises 5061Not the trunk destination 5062 or 8934[cite:1]
Calling callMeetingEscalation ends Calling E2EEMeeting E2EE depends on the meeting type[cite:2]
Google CCAIFlow ControlConnector plus CCAI config IDDialogflow. Not a Calling certificate.[cite:13]
Cisco CallMicrosoft TeamsAllow, pin, Presence sync, matching emailCalling inside Teams. Not a trunk ACL.[cite:14]
Dynamics 365WxCC desktopCIF 1 or CIF 2Screen pop. On-premises is unsupported.[cite:10]

Ecosystem troubleshooting

SymptomLikely sister-system causeCheckFixCite
Teams Cisco Call will not sign inThe Teams email or UPN does not match the Control Hub primary email, or SAML does not resolve to a Webex user.The two addresses, then IdP mapping.Match the emails. Use a different account on the Cisco Call sign-in screen only when the Teams account is not the calling account.[cite:14]
Presence in Teams stays stalePresence sync is off, or the user has not opened Cisco Call.Webex App tab, Microsoft Teams integration.Toggle Presence sync. The article says users must use Cisco Call at least once every 90 days to keep presence sync working.[cite:14]
Recording retention quoted as 8 hoursThat 8-hour figure is an Analyzer historical session, not Dubber Go.Which article the number came from.Dubber Go is 30 days. Webex Calling recordings are one year and 100 GB per organization.[cite:3] [cite:9]
Dynamics pop-up never loads on a Calling-only phonen1lsqvu is the WxCC CRM connector, not a Calling TLS feature.Whether the user is in Agent Desktop inside Dynamics.Use a cloud Dynamics instance and the CIF version that matches the app. Do not expect this connector on a premises phone.[cite:10]

05 · Flow

Decide in an order

  1. Confirm TLS 1.2 or 1.3 and AES_CM_128_HMAC_SHA1_80. [cite:1]
  2. Decide whether this call type is eligible. PSTN, premises trunk, conference, recording, auto attendant, voice portal, shared line, and virtual line are named exclusions. [cite:2]
  3. If the design requires a recording, say that E2EE is off because the service processes media. [cite:2]
  4. Choose a recording provider and quote both default sentences. [cite:3]
  5. For WebRTC agents, nvfbjts says test with 933 before Emergency call routing. That article’s header is September 08, 2024. re-check [cite:5] The agent article mwjlgk, header September 03, 2025, prints the MyE911 Cirrus host https://wxc.e911cloud.com and an email verification code. It does not reprint the password length, Device User Id, the $0 add-on, or 933-then-activate. [cite:7]

06 · Config

Paths

  • E2EE: Services > Calling > Settings > Webex App > Security. [cite:2]
  • Recording provider: Services > Calling > Settings > Services. [cite:3]
  • After RedSky account creation, details under Calling > Service Settings. [cite:5]
  • Activate under Calling tab, Emergency calling, Enhanced emergency calling. [cite:5]
  • RedSky users: https://wxc.e911cloud.com Configuration > Users. [cite:5]
  • Trunk certificate: FQDN only, Server Authentication EKU accepted by Webex. [cite:1]

07 · Limits

Limits

ItemValueSourceVerified?
TLS1.2 and 1.3jwkbt2 header April 28, 2026Quoted [cite:1]
SRTPAES_CM_128_HMAC_SHA1_80jwkbt2Quoted [cite:1]
Calling E2EE defaultDisabled5h5d8ab header July 13, 2026Quoted [cite:2]
ZT meeting sizeUp to 10005h5d8abQuoted [cite:2]
Webex recording1 year, 100 GBnhvl4hwQuoted [cite:3]
Dubber Go30 daysnhvl4hwQuoted [cite:3]
RedSky passwordAt least 16 charactersnvfbjts header September 08, 2024Quoted. re-check [cite:5]
RedSky portPort 443. The row does not name TCP.b2exveQuoted as of 2026-10-14 [cite:4]
Phone signaling source5060–5280 on the devices sub-row under Call signaling to Webex Calling (SIP TLS). The parent row’s protocol cell is TCP. The devices sub-row leaves protocol blank.b2exve history September 07, 2026Quoted [cite:4]
Trunk signaling destinationsTCP 5062 certificate, TCP 8934 registrationb2exveQuoted [cite:4]

08 · Trouble

Trouble

SymptomWrong storyWhat the article supportsDo thisCite
The shield never appearsThe cluster is down.The toggle is off by default, or the call is PSTN, a trunk, a conference, a shared line, or being recorded.Name the call type before you open a ticket.[cite:2]
Recording and E2EE were both promisedThe article says recording disables E2EE because the service processes media.Pick the compliance requirement.Say which one the design keeps.[cite:2]
Dubber and Webex are both “the default”The article prints both sentences.Quote both. Do not pick one from memory.Read nhvl4hw before you train the help desk.[cite:3]
A certificate with only Server Authentication fails on a third-party SBCWebex accepts that EKU. The SBC may not.The article states the mismatch. Choosing to relax the SBC or to add Client Authentication EKU is Canon advice, not a printed command.Do not blame the Calling CA list first.[cite:1]
The trunk certificate includes :5061The article’s example says the port is not part of the name.CN or SAN is the FQDN only.Reissue the certificate.[cite:1]
911 from Agent Desktop goes nowhereWebRTC has no traditional phone.RedSky via Control Hub. Bundled Cisco PSTN makes RedSky mandatory.Run the readiness check.[cite:5]
933 was skippedThe article says test, then activate Emergency call routing.RedSky access is the test option.Place 933 first.[cite:5]
The agent’s RedSky user is a MACContact-center identification type is Device User Id equal to the email.Then install myE911.Fix the user before the laptop.[cite:5]
Someone built the ACL from a 2024 slideThe port reference moved phone signaling to 5060–5280 on September 07, 2026.Use b2exve as of 2026-10-14.See T2-R02.[cite:4]
Meeting ZT is used to explain a SIP trunkZT meetings exclude PSTN and SIP devices.Trunks use TLS and SRTP from jwkbt2.Split the two diagrams.[cite:2]

09 · Self-question

Oral ladder

L1Which TLS versions does jwkbt2 list?

TLS 1.2 and TLS 1.3. [cite:1]

L2Which SRTP suite does that article list?

AES_CM_128_HMAC_SHA1_80. [cite:1]

L3Is Calling E2EE on by default?

No. Turn on Enable end-end encryption when making calls. [cite:2]

L4What does opportunistic mean?

Start on SRTP, upgrade when clients can, downgrade if the service must process media. [cite:2]

L5Name three call types that do not get Calling E2EE.

1:1 PSTN, 1:1 premises trunk, conference mixer. Also recording, auto attendant, voice portal, shared or virtual lines. [cite:2]

L6What does recording do to E2EE?

Disables it. [cite:2]

L7What does the recording article say is the default?

Both Webex and Dubber, in different sentences. Webex retention is one year and 100 GB. Dubber Go is 30 days. [cite:3]

L8Which RedSky hosts and port?

api.wxc.e911cloud.com and wxc.e911cloud.com, port 443. b2exve does not name TCP on that row. [cite:4]

L9What is 933?

933 on the Calling notification test, nj0abhbb header September 24, 2025, checks emergency-call email generation in the United States and Canada without alerting public safety personnel. [cite:6] nvfbjts says place 933 calls, then activate Emergency call routing. [cite:5] Read nvfbjts for whether that WxCC test reaches a PSAP. The article does not say.

L10How is a WxCC agent identified in RedSky?

Device User Id equal to the agent email, then myE911. [cite:5]

L11Why is edge port 5061 not the trunk port?

jwkbt2’s SRV example is endpoint discovery. Trunk destinations in b2exve are 5062 and 8934. [cite:1] [cite:4]

L12Are zero-trust meetings the same as Calling E2EE?

No. Meetings use MLS. Calling E2EE is the opportunistic SRTP upgrade, and escalation into a meeting ends the Calling session. [cite:2]

10 · Lab

Do not stack the locks

11 · Quiz

Quiz

Q1MCQ

Commercial SRTP in jwkbt2 is:

Answer

Commercial SRTP in jwkbt2 is: AES_CM_128_HMAC_SHA1_80. [cite:1]

Q2MCQ

Calling E2EE ships:

Answer

Disabled. The path is Services > Calling > Settings > Webex App > Security. [cite:2]

Q3Scenario

A recorded compliance call shows no E2EE shield.

Answer

Expected. Recording disables E2EE. [cite:2]

Q4Oral

Quote the recording default without picking a winner.

Answer

The article says Webex is the default and also says Dubber is chosen by default. [cite:3]

Q5MCQ

Dubber Go retention in that article:

Answer

Dubber Go retention in that article: 30 days. Webex is one year and 100 GB. [cite:3]

Q6Scenario

WebRTC agents have no desk phone and must dial 911.

Answer

WebRTC agents have no desk phone and must dial 911.: nvfbjts: Control Hub and RedSky. Test 933. Device User Id is the email. [cite:5]

Q7MCQ

RedSky port and hosts:

Answer

Port 443 to api.wxc.e911cloud.com and wxc.e911cloud.com. b2exve does not name TCP on that row. [cite:4]

Q8Oral

Server Authentication EKU only.

Answer

Server Authentication EKU only.: Webex supports it. Some SBCs do not. [cite:1]

Q9MCQ

The certificate name for london.lgw.cisco.com:5061 is:

Answer

london.lgw.cisco.com. The port is not part of the name. [cite:1]

Q10Scenario

A three-way call drops the shield.

Answer

A three-way call drops the shield.: A conference mixer cannot keep opportunistic Calling E2EE. [cite:2]

Q11Draw it

Draw SRTP, Calling E2EE, and meeting ZT as three boxes.

Answer

SRTP is the floor. [cite:1] Calling E2EE upgrades some 1:1 Webex calls and is disabled by default. [cite:2] Meeting ZT is MLS, up to 1000, and excludes PSTN and SIP devices. [cite:2]

Q12MCQ

Phone signaling source ports as of the September 07, 2026 history line:

Answer

Phone signaling source ports as of the September 07, 2026 history line: 5060–5280, not the older 5060–5080. [cite:4]

12 · Audio

Studio fills these

Transcript slot

Studio fills this. The prompt is the spoken outline.

Transcript slot

Studio fills this. The prompt is the spoken outline.

Transcript slot

Studio fills this. The prompt is the spoken outline.

13 · Interview

Oral-ready

30 seconds. Commercial Calling media is SRTP with AES_CM_128_HMAC_SHA1_80. [cite:1] Calling E2EE starts on SRTP, is off until the toggle, and ends when the service must record or mix. [cite:2] WebRTC emergency setup is nvfbjts, header September 08, 2024. re-check [cite:5]

2 minutes. I quote both recording defaults. I keep Dubber’s 30 days off contact-center QM. I do not put :5061 in a certificate name, and I do not use the edge SRV port as the trunk ACL. Meeting zero-trust is MLS and excludes PSTN and SIP devices.

14 · Citations

Ledger

Retrieved 2026-10-14. Mirrors cites/T2-R06.md.

  1. Security requirements for Webex Calling — help.webex — article jwkbt2 — help.webex.com article jwkbt2 — retrieved 2026-10-14. Header April 28, 2026.
  2. End-to-end encryption for Webex Meetings and Webex Calling — help.webex — article 5h5d8ab — help.webex.com article 5h5d8ab — retrieved 2026-10-14. Header July 13, 2026.
  3. Manage call recording for Webex Calling — help.webex — article nhvl4hw — help.webex.com article nhvl4hw — retrieved 2026-10-14. Both default sentences. Webex one year and 100 GB. Dubber Go 30 days.
  4. Port Reference for Cisco Webex Calling — help.webex — article b2exve — help.webex.com article b2exve — retrieved 2026-10-14. RedSky hosts use port 443. That row does not name TCP. Phone signaling source 5060–5280 as of the September 07, 2026 history line.
  5. Provision Emergency Calling in Webex Contact Center — help.webex — article nvfbjts — help.webex.com article nvfbjts — retrieved 2026-10-14. Header September 08, 2024.
  6. Configure emergency call notifications in Control Hub — help.webex — article nj0abhbb — help.webex.com article nj0abhbb — retrieved 2026-10-14. Header September 24, 2025. 933 tests emergency-call email generation without alerting public safety personnel. Run the Calling notification test and the WxCC RedSky test as separate checks. The Calling article’s 933 sentence is not the agent test result, and the two products use different consoles.
  7. Provision Emergency Calling in Webex Contact Center for Agents — help.webex — article mwjlgk — help.webex.com article mwjlgk — retrieved 2026-10-14. Header September 03, 2025. MyE911 Cirrus host https://wxc.e911cloud.com. Email verification code. Location from IP address and SSID. Corporate and Personal lists. Does not restate the nvfbjts password length, Device User Id, $0 add-on, or 933-then-activate steps.
  8. Webex WFO: Feature Specific SKUs — help.webex — article py6u9h — help.webex.com article py6u9h — retrieved 2026-10-14. Header June 09, 2026. Scoped to Webex Contact Center Enterprise, Contact Center Enterprise, and Contact Center Express.
  9. Cisco Webex Contact Center Analyzer User Guide — help.webex — article tajemk — help.webex.com article tajemk — retrieved 2026-10-14. Real-time remains available. Default refresh 5 seconds. Range 5 to 60 seconds in steps of 5. Historical reports stay active 8 hours.
  10. Integrate Webex Contact Center CRM Connector for Microsoft Dynamics 365 (Version 2-New) — help.webex — article n1lsqvu — help.webex.com article n1lsqvu — retrieved 2026-10-14. CIF 1 single-session. CIF 2 multi-session. On-premises Dynamics is not supported.
  11. Use AI agents for customer interactions — help.webex — article s0qro1 — help.webex.com article s0qro1 — retrieved 2026-10-14. Header August 25, 2026. Autonomous voice access is limited to specific customers.
  12. Cisco AI Assistant for Webex Contact Center — help.webex — article nvvv1zb — help.webex.com article nvvv1zb — retrieved 2026-10-14. Header October 06, 2026. Paid add-on. Not the Calling E2EE toggle.
  13. Configure Virtual Agent-Voice in Webex Contact Center — help.webex — article n6gaghu — help.webex.com article n6gaghu — retrieved 2026-10-14. Google CCAI connector and CCAI config ID. No Amazon Connect connector is named on that page.
  14. Configure Cisco Call for Microsoft Teams — help.webex — article n0l9q2z — help.webex.com article n0l9q2z — retrieved 2026-10-14. Header July 08, 2026. Teams SSO then Webex. Presence sync. Users must open Cisco Call at least once every 90 days to keep presence sync working. Unified CM backend: 12.5 SU7 or 14 SU3. VDI: Cisco Call and Teams in the same virtual machine.

15 · Re-engineer later

Open

  • re-check nvfbjts. Header September 08, 2024, older than 12 months on 2026-10-14. The password length, Device User Id, $0 add-on, and 933-then-activate steps are that article. RedSky host names were re-read on b2exve the same day. A 2026-10-14 search did not find a newer admin article that replaces nvfbjts.
  • mwjlgk, header September 03, 2025, is the agent MyE911 article. [cite:7] It confirms https://wxc.e911cloud.com, a verification email, and location by IP and SSID. It does not clear the admin re-check, and it does not say whether a WxCC 933 test alerts public safety.
  • The Calling-only article “Enhanced emergency calling for Webex Calling” (av6oo3) was fetched again on 2026-10-14. That extract did not include a header date. It confirms TCP 443 to api.wxc.e911cloud.com and wxc.e911cloud.com, and HELD. It does not reprint the nvfbjts admin steps, and Calling-only sentences are not pasted onto the WxCC 933 test.
  • WxCC quality-management retention is still not this Calling article.
  • Government SRTP is a different cloud. It is not copied here.

Sources and go deeper

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

sources.json for this page.