ZTA LabFree University

T11 · T11-R32 · Migration paths

Leaving Aura or moving toward Infinity

A move that starts on Aura can be a voice move, a contact-center move, or both. The pages you opened do not say those move together. Ask which product the numbers live on.

ExportSVGFlowSheet

Learn it in 5 minutes

  • Aura remains the enterprise voice and UC name on its page.
  • Infinity is the CX destination in the modernization sentence.
  • Experience Platform's public path redirected to Infinity.
  • OneCloud CCaaS did not resolve.
  • A side-by-side feature matrix was not opened.

Visual

Leaving Aura or moving toward Infinity From Avaya. Teaching sketch. Confirm a live system. Aura Infinity Zoom or Talkdesk SIP Names come from pages opened in 2026-10. A missing name stays confirm.

Count the boxes: 4. Each label is a name from a page or a study label marked on the drawing.

Flow

Leaving Aura or moving toward Infinity Caller SIP Called session setup session setup RTP, not required to hairpin Teaching sketch from RFC 3261 and RFC 3550. Not a packet capture.

What is going on

A move that starts on Aura can be a voice move, a contact-center move, or both. The pages you opened do not say those move together. Ask which product the numbers live on.

If the source system is Aura and the target is Zoom Phone or Talkdesk, you are leaving Avaya's voice page for another vendor's voice or contact-center page. SIP is the shared signaling citation. The feature gaps are confirm until both admin guides are open.

If the target is Infinity, you can cite Avaya's own modernization sentence and still confirm every workflow the AI is supposed to read.

Worked example

Two arrows. Aura to Infinity, cited to Avaya. Aura to Zoom Phone or Talkdesk, cited as a study path with SIP in the middle and confirm on the feature matrix.

Quiz

1. Infinity is the destination named in Avaya's modernization line.

2. OneCloud is the verified current CCaaS name.

Ecosystem

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

  • Source system — The platform that owns the number today.
  • Target system — The platform you are testing. Cite its page.

Config. Write source product and target product as page titles.

Troubleshooting. A workshop that says Avaya cloud without Infinity or Aura will not match the site you opened.

Bridge. The UC sibling lab is the Cisco-shaped course. It is not an Avaya guide.

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

Sources and go deeper

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

sources.json Markdown