UC LabFree University

T4 · T4-R01

Expressway-C and Expressway-E

Learn it in 5 minutes

  • Expressway-C lives on the inside, next to CUCM.
  • Expressway-E lives at the edge.
  • A traversal zone connects them.
  • They are not a SIP proxy you insert in every PSTN call.
  • Clustering and certificates are part of the design, not an afterthought.

Visual

Expressway-C and Expressway-E diagram

What is going on

The pair exists so devices on the internet can reach CUCM services without exposing CUCM. Traversal keeps the connection initiated from the inside. If you treat C and E as two unrelated servers, MRA will not come up.

Confirm before relying. Hybrid Calling architectures have changed. Confirm the current Webex hybrid document before you build one.

Worked example

Phones on the LAN register straight to CUCM. Phones off the LAN use the Expressway pair. A PSTN call from a LAN phone does not need to hairpin through Expressway unless you designed it that way.

Quiz

1. Every CUCM call must pass through Expressway.

Ecosystem

Sister pieces sit on the ecosystem page: the glossary, the mind map, the integration map, and the sibling labs.

  • Traversal zone — The zone that joins Expressway-C and Expressway-E.
  • Expressway-E — The edge server.

Config. Name the zone, the peer addresses, and which side is the client.

Troubleshooting. Certificate names that do not match the traversal peer fail quietly until you read the zone status.

Bridge. Expressway is also used in some hybrid calling designs. Confirm whether your tenant still uses that hybrid path.

Mind map, sister technologies, and future hooks live on the ecosystem page.

Sources

Product screens move. Confirm the guide for your release before you change a live system.

Sources and go deeper

Opened 2026-10. A row marked confirm has no link, because that page was not verified.

sources.json Markdown