WarmTransfer
Migrations · guide

Avaya Aura to Teams Phone

Avaya Aura Communication Manager to Microsoft Teams Phone

Verified 2026-09-30 · 94 sources · tier 2–5

For Telephony and Microsoft 365 administrators moving from Avaya Aura Communication Manager to Microsoft Teams Phone.

Microsoft Teams Phone provides cloud-based call control and PBX capabilities delivered in Microsoft 365 57. Direct Routing connects an organization's existing telephony infrastructure to Teams Phone through a customer-provided Session Border Controller 58, while Operator Connect uses certified operators that have completed PSTN integration with Microsoft 59.

Before you start

  • Direct Routing is a fit when maintaining an existing PSTN carrier relationship or integrating third-party PBXs and analog devices 20.
  • Operator Connect provides a managed PSTN service without deploying or maintaining customer-owned SBCs 33.
  • Direct Routing is not supported in Islands coexistence mode 60.
  • Operator Connect requires that users hold Teams Phone licenses and be configured in Teams Only mode 61.
  • Users must be homed in the cloud to be placed in TeamsOnly mode 52.
  • A single Teams tenant supports any combination of PSTN solutions 62.

What changes by situation

Pick your answers to see only your path. Nothing is sent anywhere until you make a plan.

How will Teams Phone reach the PSTN?
Will users move in phases or all at once?
Do Avaya vectors and ACD hunt groups serve a contact center that must keep running?
What will users make calls on?

Four questions. One permanent page you can send to your manager.

Step 1 Inventory the Avaya system

Do

In the field, practitioners inventory Communication Manager objects from the SAT with commands such as list station, display station, list hunt-group, display hunt-group, and display coverage path 4. In Avaya Site Administration (ASA), export station parameters using System > Advanced > Export Data 63. ASA allows only 1 task at a time, so close any open GEDI or terminal emulator windows before running the export 6465. Because an ASA export cannot capture active service link extensions, WarmTransfer's reading of the sources is that migration discovery must also inspect the live Communication Manager configuration 6667. Note that faxing cannot be used on numbers assigned to Teams Phone or Calling Plan licenses 41. In the field, hardware gateways of the same G450 model can fall on different sides of support boundaries depending on hardware vintage, so record gateway vintage alongside model numbers 68.

Verify

Suggested check: verify that all exported stations, hunt groups, and DIDs are accounted for against active licensing records.

Rollback

Suggested rollback: delete or archive the exported inventory files; no PBX changes were applied in this step.

Step 2 Confirm Teams licensing and user readiness

Do

Assign each user making PSTN calls a Teams Phone license and provide access to a PSTN solution 6970. Direct Routing users require Microsoft Teams and Teams Phone licenses 24. License combinations granting Teams Phone include Teams Enterprise with Microsoft 365 E5 (no Teams), Teams Enterprise with Teams Phone Standard, legacy Microsoft 365 E5, and Office 365 F3 with Teams Phone Standard for Frontline Workers 71. Stand-alone Teams Phone Standard is not required if Microsoft 365 E5 is assigned 72. Every resource account used for an auto attendant or call queue that answers calls must be assigned a Teams Phone Resource Account license 73. Do not assign Teams Phone Standard to a resource account 74. Calls between Teams users in the same organization route natively without touching the PSTN 75.

Verify

Suggested check: check the tenant administration portal to verify assigned licenses and ensure pilot users are homed online.

Rollback

Suggested rollback: unassign the Teams Phone and Resource Account licenses in the admin center.

Step 3 Establish PSTN connectivity

Direct Routing through a certified SBC

Do

Follow Microsoft's Direct Routing onboarding order: review infrastructure, select a certified SBC, configure DNS, certificates, and firewall, connect the SBC, configure routing and dial plans, assign licenses and policies, and validate 23. Microsoft supports Direct Routing only with certified SBCs and may decline support cases involving uncertified devices 76. Avaya SBCE is certified at release 8.1.1 or higher, release 8.1.2 or higher for media bypass, release 10.1.2 or higher for Local Media Optimization, and release 10.2.0.2 for ELIN 23. Higher SBC firmware is supported within the same major.minor version 46. Configure public DNS for an SBC FQDN under a verified tenant domain (not *.onmicrosoft.com), install a trusted TLS certificate, and enforce TLS 1.2 using supported ECDHE-RSA cipher suites 7749. Ensure the tenant contains a user in that SBC FQDN domain licensed with E3 or E5 44. Pair the SBC using New-CsOnlinePSTNGateway or the Teams admin center 48. Configure SIP signaling to sip.pstnhub.microsoft.com, sip2.pstnhub.microsoft.com, and sip3.pstnhub.microsoft.com over port 5061 78. Configure two-way media over UDP/SRTP ports 3478-3481 and 49152-53247, opening at least 2 media ports per concurrent call on the SBC 79.

Verify

Verify the pairing by checking that Get-CsOnlinePSTNGateway shows Enabled as True and that 200 OK responses occur for SIP OPTIONS exchanged in both directions 48.

Rollback

Set the SBC Enabled parameter to False via Set-CsOnlinePSTNGateway to remove it from service, or remove the gateway using Remove-CsOnlinePSTNGateway 4548.

Operator Connect through a certified operator

Do

Choose a certified operator based on regional coverage, number availability, porting support, calling plans, and existing relationships 32. Establish an agreement with the operator and enable them within the Teams admin center 5930. The operator provides PSTN connectivity, number provisioning, porting, and PSTN support, while Microsoft manages the Teams service and integration 80.

Verify

Suggested check: confirm in the tenant administration portal that the operator shows as active and that assigned test profiles are populated.

Rollback

Suggested rollback: release assigned operator profiles from test accounts and disable the operator in the administration portal.

Step 4 Set up the coexistence path between Teams and Avaya

Phased migration running side by side

Do

WarmTransfer's reading of the sources is that calls between Teams and Aura can pass through a certified SBC such as Avaya SBCE deployed between Session Manager and Direct Routing 81. In Microsoft's hybrid architecture, Direct Routing connects to third-party PBXs while Operator Connect or Calling Plan provides PSTN calling 21. Configure Direct Routing routing elements: an online PSTN gateway pointing to the SBC, a voice route matching the Avaya extension pattern, a PSTN usage containing the route, and a voice routing policy containing the usage 53. PSTN usages evaluate sequentially and stop on the first match, so place the Avaya extension usage ahead of broad PSTN usages 56. Assign custom voice routing policies per user rather than modifying the global policy, to avoid misrouting PSTN calls from Operator Connect users 54. Note that Direct Routing ignores mid-call media re-targeting requests from an SBC 22.

Verify

Dial an Avaya-hosted extension from a Teams pilot user to confirm it rings the Avaya station, and check that dialed strings without matching routes drop rather than misroute 55.

Rollback

Remove the voice route from the PSTN usage, or set the coexistence SBC gateway to Enabled: False 4553.

Single cutover event

Do

Bypass creation of an internal coexistence trunk between Teams and Avaya Communication Manager 18.

Verify

Suggested check: confirm the inventory contains no active extensions or devices scheduled to remain on-premises following the cutover date.

Rollback

Suggested rollback: no configuration was applied; proceed to dial plan creation.

Step 5 Preserve extension dialing with a dial plan

Do

Configure tenant dial plans with normalization rules to translate dialed extension digits into full destination numbers 15. Extension dialing requires this extra routing configuration even though Operator Connect preconfigures base routing 17. Ensure every user and resource account has a unique number assigned 43. A tenant supports up to 1,000 dial plans; user dial plans take precedence over the global tenant dial plan 16.

Verify

Suggested check: test dialed extension strings on a provisioned Teams client to verify that the normalization rules correctly resolve to the intended target user.

Rollback

Suggested rollback: remove the custom normalization rules from the dial plan or unassign the user-level dial plan in the Teams admin center.

Step 6 Rebuild reception and hunt groups as auto attendants and call queues

Do

WarmTransfer's reading of the sources is that Communication Manager vector and VDN call flows do not translate one-to-one into Teams objects, requiring time-of-day and menu logic to be separated into auto attendants and call queues 82. Auto attendants can transfer callers to specific people, call queues, external numbers, other auto attendants, or voicemail, with dedicated routing for business hours, after hours, and holidays 1. Because call queues have no schedule handling, place an auto attendant ahead of each call queue 12. Configure call queues using attendant, serial, round robin, or longest idle routing 14. Call queues support up to 20 individual agents, or up to 200 via groups or Teams channels (adding only the first 200 enterprise-voice-enabled users alphabetically) 8. Configure exception handling: call wait limits range from 0 to 200 calls (default 50) and timeouts range from 0 seconds to 45 minutes, with options to disconnect or redirect 10. Microsoft recommends enabling conference mode, choosing round robin or longest idle routing, enabling presence-based routing, and setting an agent alert time of at least 20 seconds 13. Conference mode requires agents to be in TeamsOnly mode 9. Assign a Teams Phone Resource Account license to every answering auto attendant or call queue resource account; nested queues reached after an initial answer do not require their own resource account 8311.

Verify

Suggested check: place test calls to the auto attendant resource accounts across business hours and after-hours schedules to verify menu prompts and overflow redirections.

Rollback

Suggested rollback: unassign telephone numbers from the resource accounts and delete the newly created call queues and auto attendants.

Step 7 Resolve contact center dependencies

No, replace with Teams auto attendants and call queues

Do

WarmTransfer's reading of the sources is that call flows are split into auto attendants and call queues rather than relying on an external contact center platform 82. Verify that call flows remain within the supported auto attendant destinations and queue routing methods 114.

Verify

Suggested check: verify that all previous ACD hunt groups and VDN numbers are accounted for in the configured queues.

Rollback

Suggested rollback: keep vectors and hunt groups active in the on-premises system.

Yes, integrate a certified contact center solution

Do

Select a platform evaluated under the contact center for Microsoft Teams certification program 5. Identify the vendor's integration model: Unify (Azure Communication Services), Extend (Teams client platform and Graph APIs), or Connect (Direct Routing and certified SBCs) 7. If a Connect-model solution is used, establish Direct Routing SBC trunks for agent audio, and ensure any Teams user receiving transfers holds a phone system license and phone number 76.

Verify

Suggested check: simulate an incoming contact center call, confirm agent call delivery, and verify consultative transfer to a Teams enterprise voice user.

Rollback

Suggested rollback: redirect contact center trunking and incoming carrier numbers back to the on-premises environment.

Step 8 Put endpoints in users' hands

Reuse Avaya J100 SIP phones via Teams SIP Gateway

Do

In the field, migration providers offer Avaya J-Series connectivity to Teams through Microsoft SIP Gateway 84. Update compatible Avaya J100 SIP phones (J129, J139, J159, J169, J179, J189) to minimum and approved firmware 4.1.11.0 50. Users logging into SIP Gateway require Microsoft Teams, Skype for Business Online (Plan 2), Microsoft Phone System, and a PSTN-enabled phone number 85. Onboarded SIP Gateway devices support inbound/outbound calls, hold/resume, two-call conferencing, blind and consultative transfer, voicemail retrieval with message waiting indication, DTMF, and Teams meeting dial-in 51. Because SIP Gateway does not publish user presence, do not configure presence-based routing for queue agents using these devices 86. SIP Gateway automatically offboards stale devices after 30 days disconnected if paired, or 14 days if unpaired 87.

Verify

Suggested check: sign in to an updated handset, place a test call, test call transfer, and confirm message waiting indicator behavior.

Rollback

Suggested rollback: perform a factory reset on the device and point its provisioning settings back to the local environment.

Deploy Teams clients and certified devices

Do

Deploy Teams desktop and mobile clients, Teams-certified phones, or Common Area Phones 19. When Common Area Phones are deployed over Direct Routing, a Calling Plan license is not required 88. Assign the Microsoft Teams Shared Device license to common area telephone devices, which includes the Phone System application 89. A Teams Enterprise license is not required for shared devices or voice applications 90.

Verify

Suggested check: sign into the Teams client or certified device with user credentials and verify successful placement and receipt of calls.

Rollback

Suggested rollback: sign out of the new devices and return users to their existing desk phones.

Step 9 Configure emergency calling

Direct Routing through a certified SBC

Do

Configure dedicated emergency call routing policies, which Direct Routing requires 91. Dynamic emergency calling is available to route calls and notify personnel based on client location 92. To assign emergency locations to network identifiers, ensure addresses are validated and carry geo codes 93. Configure security desk notifications to conference safety personnel into emergency calls 94. If using Avaya SBCE for ELIN handling, ensure the SBC runs release 10.2.0.2 or higher 2.

Verify

Suggested check: run an emergency test call following carrier and local safety desk procedures, confirming address delivery and security notification.

Rollback

Suggested rollback: reassign the prior emergency routing policy or unassign the emergency call routing policy from user profiles.

Operator Connect through a certified operator

Do

Configure dynamic emergency calling by creating validated, geocoded emergency addresses in the Teams admin center 9392. Confirm routing responsibilities with the operator, as the carrier manages primary emergency call routing under Operator Connect 91. Configure security desk notifications via emergency calling policies 94.

Verify

Suggested check: coordinate with the Operator Connect partner to place a test emergency call validating received location records.

Rollback

Suggested rollback: adjust or remove emergency policy assignments in the Teams admin center.

Step 10 Move the phone numbers

Direct Routing through a certified SBC

Do

WarmTransfer's reading of the sources is that existing carrier trunks can be repointed to the certified SBC instead of initiating a carrier port 81. Assign unique numbers to each user and resource account 43.

Verify

Confirm inbound and outbound PSTN calls function, voice routing policies match, and call quality is validated 25.

Rollback

Suggested rollback: request the carrier restore the trunk delivery route back to the existing on-premises SBC interfaces.

Operator Connect through a certified operator

Do

Acquire numbers by ordering new ranges or submitting port requests through the certified operator 31. Number provisioning and porting is the operator's operational responsibility 80. Microsoft's port order guidance (documented for Calling Plans) recommends clearing advanced features like Call Hunt or Distinctive Ring prior to porting 36, submitting ports for a single customer account one at a time to prevent carrier rejection 42, choosing a conservative port date at least 15 business days out 34, and keeping existing provider lines active until all porting is finished 40. Assign unique numbers to individual users or resource accounts in Teams 43.

Verify

Suggested check: place inbound test calls to ported numbers to verify delivery to assigned Teams users and resource accounts.

Rollback

Suggested rollback: coordinate with the losing carrier and Operator Connect partner to initiate a snapback or return port if routing fails.

Step 11 Cut users over

Phased migration running side by side

Do

Assign Teams Phone licenses, voice routing policies, dial plans, and numbers to each user batch 23. If porting numbers from the same carrier account, submit batches sequentially because losing carriers reject overlapping requests 42. Update inbound DID routing on the SBC or carrier trunk to direct the batch's numbers to Teams, and route calls from remaining Avaya stations across the coexistence SBC trunk 18.

Verify

Complete Microsoft's verification checks for each batch: verify SBC health, test inbound and outbound PSTN calls, verify emergency calling, test SIP connection point failover, confirm policy assignments, and check call quality 25. Suggested check: verify bi-directional extension calls between the migrated batch and remaining on-premises users.

Rollback

Suggested rollback: revert trunk routing on the SBC to send the batch's DIDs back to the on-premises system and remove assigned phone numbers.

Single cutover event

Do

Assign Teams Phone licenses, voice routing policies, dial plans, and numbers across the organization 23. Repoint all carrier trunks or complete operator number activation to land all DIDs in Teams 3018. Calling Plan porting processing typically takes 7 to 14 days (up to 30 days) with a minimum 5-day lead time in the US and 10 days in Canada, capped at 30 days in advance 39. Large port requests of 1,000 or more numbers require manual submission 38.

Verify

Perform the full verification checklist: healthy SBC connection, working inbound and outbound PSTN calls, functional emergency calling, tested connection point failover, verified policy assignments, and validated call quality 25.

Rollback

Suggested rollback: revert carrier routing back to the existing trunks before any on-premises infrastructure is powered down.

Step 12 Decommission coexistence and Avaya

Do

Remove the temporary Avaya voice routes and PSTN usages from Teams voice routing policies 53. After all porting and routing transfers are complete, cancel legacy Avaya carrier trunks 40. For Calling Plan ports, issues noticed within 24 to 48 hours of completion are handled by the Phone Number Service Center, while later issues go to Microsoft Support 37. If the coexistence SBC trunk carries no further third-party PBX or analog connections, set its gateway Enabled status to False and remove it 4548.

Verify

Suggested check: verify that test calls to former DIDs terminate correctly in Teams and confirm no residual traffic traverses the coexistence gateway.

Rollback

Suggested rollback: re-enable the coexistence voice route and gateway on the SBC if unmigrated endpoints or services are discovered.

Applicability

Applies to: Microsoft Teams Phone, Avaya Aura Communication Manager, Microsoft Teams SIP Gateway, Microsoft Teams, Avaya Site Administration, Avaya Communication Manager, Avaya G430, and Avaya J100 Series IP Phones. Deployments: on-premises, hybrid, multi-tenant, dod, gcc, and gcc-high. Sources checked 2026-09-30. Microsoft lists Direct Routing SBC certification for Avaya SBCE starting at release 8.1.1, with release 8.1.2 required for media bypass, release 10.1.2 for Local Media Optimization, and release 10.2.0.2 for ELIN 23. Avaya J100 SIP phones (J129, J139, J159, J169, J179, J189) require firmware 4.1.11.0 for SIP Gateway compatibility 50. Microsoft is not accepting new nominations for Direct Routing SBC certification until further notice 47.

What remains uncertain

Communication Manager dial patterns, Session Manager routing policies, and SIP entity administration toward the SBC are not covered by the sources below. Translation rules for Avaya vector commands, Call Management System (CMS) real-time reports, and Avaya Aura Messaging mailboxes are not covered by the sources below. Configuration details for analog gateways, overhead paging systems, and elevator lines are not covered by the sources below. Carrier lead times for repointing Direct Routing trunks are not covered by the sources below.

See also

Migrates to

  • Microsoft teams phone — Target platform; this guide reuses the microsoft-teams-phone registry claims for licensing; PSTN models; Direct Routing infrastructure; SIP Gateway and emergency calling.

Referenced by

Sources

  1. 1
    A Teams auto attendant can send callers to specific people, call queues, external numbers, other auto attendants and shared or personal voicemail, with separate routing for business hours, after hours and holidays.
    Planning - Overview of voice applications · section 'Auto Attendant' · Checked 2026-09-30
  2. 2
    Microsoft lists Avaya Session Border Controller for Enterprise (ASBCE) as certified for Direct Routing at release 8.1.1 or higher, with 8.1.2 or higher for media bypass and 10.2.0.2 for ELIN.
    Session Border Controllers certified for Direct Routing - Microsoft Teams · section 'Certified SBC vendors', Avaya row · Checked 2026-09-30
  3. 3
    Microsoft lists Avaya ASBCE release 10.1.2 or higher as supporting Local Media Optimization for Direct Routing.
    Session Border Controllers certified for Direct Routing - Microsoft Teams · section 'Support for Local Media Optimization', Avaya row · Checked 2026-09-30
  4. 4
    Practitioners inventory Avaya Communication Manager from the SAT with commands such as list station, display station, list hunt-group, display hunt-group and display coverage path.field report
    SAT Command Cheat Sheet · sections 'Stations', 'Hunt Groups', 'Coverage Paths' · Checked 2026-09-30
  5. 5
    Microsoft runs a contact center for Microsoft Teams certification program and publishes a list of certified contact center solutions for organizations choosing a solution to use with Teams.
    Teams Contact Center - Microsoft Teams · section 'Contact center for Microsoft Teams certification program' · Checked 2026-09-30
  6. 6
    In the Connect contact center model the agent's contact center solution does not need a phone system license, but a Teams user needs a phone system license and a phone number for agent call transfer.
    Teams Contact Center - Microsoft Teams · Connect integration model tab, Note · Checked 2026-09-30
  7. 7
    Microsoft defines three integration models for contact center solutions with Teams: Unify (Azure Communication Services based), Extend (Teams client platform and Graph communications APIs, with Teams Phone handling contact center calls) and Connect (certified SBCs and Direct Routing).
    Teams Contact Center - Microsoft Teams · section 'Integration models for solution providers' and its three tabs · Checked 2026-09-30
  8. 8
    A Teams call queue accepts up to 20 individually added agents and up to 200 agents via groups or a Teams channel; beyond 200 members only the first 200 enterprise-voice-enabled members in alphabetical order are added.
    Setup - Call Queue - Microsoft Teams · Advanced setup 'Step 3: Call answering', Teams channel and Users and groups · Checked 2026-09-30
  9. 9
    Call queue conference mode requires agents in TeamsOnly mode, is required for Teams users to consult or transfer with call queues, is not supported for calls from a Direct Routing gateway enabled for Location-Based Routing, and is Microsoft's recommended setting.
    Setup - Call Queue - Microsoft Teams · Advanced setup 'Step 3: Call answering', Conference mode · Checked 2026-09-30
  10. 10
    A Teams call queue's maximum calls waiting defaults to 50 and ranges from 0 to 200, and its call timeout ranges from 0 seconds to 45 minutes, with overflow, timeout and no-agents exceptions each able to disconnect or redirect.
    Setup - Call Queue - Microsoft Teams · Advanced setup 'Step 6: Exception handling' · Checked 2026-09-30
  11. 11
    Call queues that directly answer calls need a resource account with a Teams Phone Resource Account license, but nested auto attendants and call queues reached from one that already answered do not require a resource account.
    Setup - Call Queue - Microsoft Teams · Advanced setup 'Step 1: General info', Add an existing resource account · Checked 2026-09-30
  12. 12
    Teams call queues do not provide separate off-hours or holiday routing, and Microsoft recommends placing an auto attendant in front of a call queue even if the queue is staffed 24/7.
    Planning - Overview of voice applications · section 'Call Queue', final paragraph · Checked 2026-09-30
  13. 14
    Teams call queues offer four routing methods: attendant (ring all at once), serial (one by one in list order), round robin (equal distribution) and longest idle (the agent Available longest).
    Setup - Call Queue - Microsoft Teams · Advanced setup 'Step 4: Agent selection', Routing method · Checked 2026-09-30
  14. 15
    A custom Teams dial plan is typically needed to support non-E.164 dialing such as extensions or abbreviated national dialing, and only patterns not already in the service country dial plan need to be defined.
    Microsoft Teams Dial plans for phone call routing · section 'Planning for tenant dial plans', steps 1 and 3 · Checked 2026-09-30
  15. 16
    A Teams tenant can have a maximum of 1,000 tenant dial plans, and a user dial plan takes precedence over the tenant Global dial plan, which takes precedence over the service dial plan.
    Microsoft Teams Dial plans for phone call routing · sections 'Dial plan scopes and a user's effective dial plan' and 'Dial plans and routing considerations' · Checked 2026-09-30
  16. 17
    With Calling Plan, Operator Connect or Teams Phone Mobile, dial plans and voice routing policies are preconfigured at the service level, while Direct Routing or extension dialing requires additional routing configuration.
    Microsoft Teams Dial plans for phone call routing · sections 'User dial plans with Calling Plans and Operator Connect' and 'User dial plans with Direct Routing or extension dialing' · Checked 2026-09-30
  17. 18
    Microsoft's Direct Routing architecture shows a certified SBC connecting Teams Phone to both an existing PSTN carrier and an existing PBX, analog devices and SIP trunks.
    Plan Direct Routing · section 'Direct Routing architecture' (diagram) · Checked 2026-09-30
  18. 19
    Direct Routing supports Teams desktop and mobile clients, Teams-certified phones and Common Area Phones.
    Plan Direct Routing · section 'Supported endpoints' · Checked 2026-09-30
  19. 20
    Microsoft lists Direct Routing as a good fit for organizations that have an existing PSTN carrier relationship or require integration with third-party PBXs or analog devices.
    Plan Direct Routing · section 'Why choose Direct Routing?' · Checked 2026-09-30
  20. 21
    Microsoft describes a common hybrid pattern in which Calling Plan or Operator Connect provides PSTN calling while Direct Routing carries calls to third-party PBXs, analog devices and specialized routing.
    Plan Direct Routing · section 'Direct Routing with Calling Plan and Operator Connect' · Checked 2026-09-30
  21. 22
    Direct Routing does not support media re-targeting: if the SBC sends a new media IP mid-call, Teams never sends media to the new address.
    Session Border Controllers certified for Direct Routing - Microsoft Teams · final note on the page · Checked 2026-09-30
  22. 23
    Microsoft's recommended Direct Routing onboarding order is: review infrastructure, networking and licensing; select a certified SBC; configure DNS, certificates, firewall and connectivity; connect the SBC to Teams; configure voice routing and dial plans; assign Teams Phone licenses and voice routing policies; validate and expand.
    Plan Direct Routing · section 'Onboarding' table steps 1-7 · Checked 2026-09-30
  23. 24
    Direct Routing users require Microsoft Teams and Teams Phone licensing, with additional licensing possibly required depending on the deployment.
    Plan Direct Routing · section 'Licensing requirements' · Checked 2026-09-30
  24. 25
    Microsoft's Direct Routing verification list is: SBC reports a healthy connection, inbound and outbound PSTN calls work, emergency calling works if configured, failover between SIP connection points is tested, voice routing policies are assigned correctly and call quality is validated.
    Plan Direct Routing · section 'Verify your deployment' · Checked 2026-09-30
  25. 26
    Practitioners report that Avaya Aura to Teams Direct Routing integrations are not limited to Avaya SBCE (for example AudioCodes Mediant VE in Azure) and that published guidance on the Teams side is thin.field report
    Avaya Aura Integration with Microsoft Teams Direct Routing Docs · thread posts, November 2023 · Checked 2026-09-30
  26. 27
    Under Direct Routing the numbers can stay with the existing carrier, and cutover is likely a carrier-side change that delivers the numbers to the certified SBC rather than to Avaya, not a port to Microsoft.inferred
    Plan Direct Routing · sections 'Why choose Direct Routing?' and 'Direct Routing architecture' (basis for inference) · Checked 2026-09-30
  27. 28
    An organization that picks Operator Connect for PSTN but migrates from Avaya in phases likely still needs a Direct Routing SBC trunk to Avaya Communication Manager for calls between migrated Teams users and remaining Avaya extensions during coexistence.inferred
    Plan Direct Routing · sections 'Direct Routing with Calling Plan and Operator Connect' and 'Example deployment' (basis for inference) · Checked 2026-09-30
  28. 29
    With Operator Connect and a single cutover that leaves no Avaya extensions in service, the customer likely needs no SBC of its own for Teams PSTN calling, since the operator manages the PSTN infrastructure.inferred
    Plan for Operator Connect · introduction and 'Benefits' (basis for inference) · Checked 2026-09-30
  29. 30
    Operator Connect is configured by enabling the selected operator in the Teams admin center and then assigning phone numbers to users.
    Plan for Operator Connect · section 'Onboarding', 'Step 4: Configure Operator Connect' · Checked 2026-09-30
  30. 31
    Under Operator Connect, users can receive numbers by purchasing new numbers from the operator, porting existing numbers, or migrating from another Teams Phone PSTN connectivity option.
    Plan for Operator Connect · section 'Onboarding', 'Step 3: Plan your phone numbers' · Checked 2026-09-30
  31. 32
    When choosing an Operator Connect provider, Microsoft advises weighing country and regional availability, phone number availability and porting support, calling plans and existing business relationships.
    Plan for Operator Connect · section 'Onboarding', 'Step 2: Choose a certified operator' · Checked 2026-09-30
  32. 33
    Microsoft positions Operator Connect as a good choice when an organization wants a managed PSTN solution without deploying and maintaining its own SBCs, or wants to keep an existing operator that offers Operator Connect.
    Plan for Operator Connect · introduction, second paragraph · Checked 2026-09-30
  33. 34
    Microsoft recommends a conservative port target date at least 15 business days after submission for all ports, trading speed for predictability.
    What's a port order? - Microsoft Teams · section 'Plan for port event date', Approach 2 · Checked 2026-09-30
  34. 35
    Microsoft's port order process moves numbers to Microsoft Calling Plans, with Microsoft managing fulfilment with the losing provider and becoming the service provider of record.
    What's a port order? - Microsoft Teams · APPLIES TO banner and introduction · Checked 2026-09-30
  35. 36
    Before a Calling Plan port, Microsoft advises disabling advanced call control features such as Call Hunt or Distinctive Ring on the numbers with the current provider and clearing open service orders or pending disconnects.
    What's a port order? - Microsoft Teams · section 'Common mistakes' · Checked 2026-09-30
  36. 37
    Issues with ported numbers noticed within 24 to 48 hours of port completion go to the Phone Number Service Center; later issues go to Microsoft Support.
    Transfer phone numbers to Microsoft Teams · section 'Report phone number issues' · Checked 2026-09-30
  37. 38
    A Calling Plan port request of 1,000 numbers or more must bypass the Teams admin center wizard and be submitted manually to Telephone Number Services.
    What's a port order? - Microsoft Teams · section 'Large port requests' · Checked 2026-09-30
  38. 39
    A Calling Plan port typically takes 7 to 14 days end to end and up to 30 days depending on the losing provider, needs a minimum 5-day lead time in the US and 10 days in Canada, and cannot target a date more than 30 calendar days out.
    What's a port order? - Microsoft Teams · section 'Plan lead-time for port request processing' · Checked 2026-09-30
  39. 40
    Microsoft advises not arranging disconnection with the current provider until all porting is complete, because inactive or disconnected numbers cannot be ported and a port might be rejected.
    What's a port order? - Microsoft Teams · section 'When to disconnect your existing phone lines with your current service provider' · Checked 2026-09-30
  40. 41
    Numbers dedicated to faxing can be ported to Calling Plans but fax will not work, because faxing is not available through Phone System or Calling Plan licenses.
    What's a port order? - Microsoft Teams · section 'Numbers eligible for porting', You can't transfer · Checked 2026-09-30
  41. 42
    Port requests for the same account number are processed one at a time; overlapping requests for one account are rejected by the losing provider, so batches from one account must be submitted only after the previous batch completes.
    What's a port order? - Microsoft Teams · section 'How port requests are processed' · Checked 2026-09-30
  42. 43
    Inbound routing to Teams users requires every user and resource account to have a unique number (and extension if used); extensions are only needed when users share a main number without Shared Calling and are otherwise not required or recommended.
    Microsoft Teams Dial plans for phone call routing · section 'Number lookup for inbound calls' · Checked 2026-09-30
  43. 44
    Besides the SBC FQDN's domain being registered in the tenant, there must be a user in that domain with an E3 or E5 license assigned, otherwise pairing fails with a domain-not-configured error.
    Connect your Session Border Controller (SBC) to Direct Routing · section 'Connect the SBC to the tenant', Considerations bullet 2 · Checked 2026-09-30
  44. 45
    The SBC's Enabled setting turns the SBC on for outbound calls and can be used to temporarily remove it from service during updates or maintenance.
    Connect your Session Border Controller (SBC) to Direct Routing · section 'SBC settings', row 'Enabled' · Checked 2026-09-30
  45. 46
    Direct Routing SBC certification is granted to specific firmware versions, and higher firmware versions are supported as long as the major.minor version is the same.
    Session Border Controllers certified for Direct Routing - Microsoft Teams · intro note above 'Certified SBC vendors' · Checked 2026-09-30
  46. 47
    Microsoft states it is not accepting new nominations for Direct Routing SBC certification until further notice.
    Session Border Controllers certified for Direct Routing - Microsoft Teams · paragraph immediately above 'Certified SBC vendors' · Checked 2026-09-30
  47. 48
    An SBC is paired with New-CsOnlinePSTNGateway (FQDN, SIP signaling port, max concurrent sessions, Enabled) or in the Teams admin center, and the pairing is verified by Get-CsOnlinePSTNGateway showing Enabled True and by the SBC receiving 200 OK to SIP OPTIONS in both directions.
    Connect your Session Border Controller (SBC) to Direct Routing · sections 'Connect the SBC to the tenant' and 'Verify the SBC connection' · Checked 2026-09-30
  48. 49
    Microsoft forces TLS 1.2 on the Direct Routing SIP interface and lists the ECDHE-RSA AES-GCM and AES-CBC cipher suites the SBC must support.
    Connect your Session Border Controller (SBC) to Direct Routing · section 'Connect the SBC to the tenant', Considerations TLS bullet · Checked 2026-09-30
  49. 50
    Microsoft lists Avaya J100 SIP phones (J129, J139, J159, J169, J179, J189) as compatible with Teams SIP Gateway, with minimum and approved firmware 4.1.11.0.
    Plan SIP Gateway · section 'Compatible devices', Avaya row · Checked 2026-09-30
  50. 51
    SIP Gateway devices can make and receive PSTN and Teams calls, hold and resume, conference two calls, do blind and consultative transfers, retrieve voicemail with message waiting indication, send DTMF and dial in to Teams meetings.
    Plan SIP Gateway · section 'Benefits of SIP Gateway' · Checked 2026-09-30
  51. 52
    Only users homed in the cloud can have TeamsOnly coexistence mode; the other coexistence modes apply only to users homed in Skype for Business Server on-premises.
    Set your coexistence and upgrade settings · section 'Set upgrade options for a single user in your organization', step 3 · Checked 2026-09-30
  52. 53
    Direct Routing call routing is built from voice routing policies that contain PSTN usages, PSTN usages that contain voice routes, voice routes that pair a number pattern with online PSTN gateways, and online PSTN gateways that point to SBCs.
    Configure call routing for Direct Routing · section 'Call routing overview' · Checked 2026-09-30
  53. 54
    If the global (Org-wide default) online voice routing policy is configured, all voice-enabled users inherit it, which can route Calling Plan and Operator Connect users' PSTN calls to a Direct Routing trunk; Microsoft advises custom policies assigned to individual users instead.
    Configure call routing for Direct Routing · section 'Voice routing policy considerations', Caution item 1 · Checked 2026-09-30
  54. 55
    For a user with Teams Phone but no Calling Plan, a dialed number that matches no voice route in the assigned policy is dropped; a Calling Plan user falls through to the Calling Plan route.
    Configure call routing for Direct Routing · section 'Example 1: Voice routing with one PSTN usage', notes · Checked 2026-09-30
  55. 56
    PSTN usages in a voice routing policy are applied in order, and once a match is found in one usage the later usages are never evaluated.
    Configure call routing for Direct Routing · section 'Example 2: Voice routing with multiple PSTN usages', Note · Checked 2026-09-30
  56. 57
    Microsoft describes Teams Phone as its technology for call control and PBX capabilities delivered in the Microsoft 365 cloud.
    What is Teams Phone · What is Teams Phone, opening paragraph · Checked 2026-09-24
  57. 58
    Microsoft Direct Routing connects an organization's own telephony infrastructure to Teams Phone through a supported, customer-provided Session Border Controller.
    Plan Direct Routing · Plan Direct Routing, introduction · Checked 2026-09-25
  58. 59
    Operator Connect uses certified third-party operators that have already completed PSTN integration with Microsoft; the customer needs a contract with the operator and enables the operator in the Teams admin center, with no customer-deployed SBC.
    Plan for Operator Connect · Plan for Operator Connect, introduction and section 'Step 4: Configure Operator Connect' · Checked 2026-09-24
  59. 60
    Direct Routing is not supported in Islands coexistence mode.
    Plan Direct Routing · Plan Direct Routing, section 'Licensing requirements', Note · Checked 2026-09-24
  60. 61
    Operator Connect requires users to have Teams Phone licenses and to be configured in Teams Only mode, and a certified operator must serve the countries or regions being deployed.
    Plan for Operator Connect · Plan for Operator Connect, section 'Step 1: Verify prerequisites' · Checked 2026-09-24
  61. 62
    A single Teams tenant can have more than one PSTN integration, and Microsoft states that any combination of PSTN solutions is supported.
    What is Teams Phone · What is Teams Phone, add-on options list, PSTN operator solution sub-bullets · Checked 2026-09-24
  62. 63
    Avaya's knowledge base gives System > Advanced > Export Data in Avaya Site Administration as the way to export station parameters from Communication Manager.
    How to export the active 'station service link extension' from a station from the Communication Manager with Site Administration? · FAQ116513, Answer section · Checked 2026-09-25
  63. 64
    ASA exports of station, VDN and vector data fail with 'Waiting for connection' if a GEDI or terminal emulator session is still open, because ASA only performs one task at a time.
    Unable to export station, VDN, vector information using Avaya Site Administration (ASA). · SOLN329388, Problem and Cause sections · Checked 2026-09-25
  64. 65
    Closing the GEDI or emulator window allowed ASA to export the station, VDN and vector data.
    Unable to export station, VDN, vector information using Avaya Site Administration (ASA). · SOLN329388, Solution section · Checked 2026-09-25
  65. 67
    An ASA field export is not a complete configuration capture, because at least one station attribute (service link extension) cannot be exported, so migration discovery should also read the live CM configuration.inferred
    How to export the active 'station service link extension' from a station from the Communication Manager with Site Administration? · FAQ116513, Answer section · Checked 2026-09-25
  66. 68
    Gateways of the same G450 model can fall on opposite sides of a support boundary because support depends on hardware vintage, so migration inventories need the vintage and not just the model.field report
    Avaya End of Life List: Models & EOL Dates (2026) · G430/G450 section, emphasis note on identical-looking G450s · Checked 2026-09-25
  67. 69
    To use PSTN telephony with Teams Phone, a user account must be licensed with the Teams Phone application and also be equipped with a PSTN solution from a PSTN service provider.
    PSTN connectivity options · PSTN connectivity options, section 'What is the Public Switched Telephone Network (PSTN)?' · Checked 2026-09-24
  68. 70
    A PSTN solution is separate from a Teams Phone license: the PSTN solution supplies phone numbers and domestic, international and emergency PSTN access, while the Teams Phone license entitles the user to enhanced calling capabilities and access to that PSTN solution.
    What is Teams Phone · What is Teams Phone, Note block after the add-on options list · Checked 2026-09-24
  69. 71
    Examples of license combinations that grant Teams Phone to end users include Teams Enterprise plus Microsoft 365 E5 (no Teams), Teams Enterprise plus Teams Phone Standard, a legacy Microsoft 365 E5, and Office 365 F3 plus Teams Phone Standard for Frontline Workers.
    Teams Phone licensing · Teams Phone licensing, section 'Licensing Teams Phone - for end users', example list · Checked 2026-09-24
  70. 72
    Where any Microsoft 365 E5 license is used, it is not necessary to also assign the stand-alone Microsoft Teams Phone Standard license.
    Teams Phone licensing · Teams Phone licensing, section 'Licensing Teams Phone - for end users', paragraph after the example list · Checked 2026-09-24
  71. 73
    Every resource account for an auto attendant or call queue must be assigned a Teams Phone Resource Account license, whether or not it will be assigned a telephone number; a Calling Plan is needed only if the resource account must dial out.
    Microsoft Teams Phone Resource Account licenses · Microsoft Teams Phone Resource Account licenses, paragraphs 1-2 and second Note · Checked 2026-09-24
  72. 74
    Teams Phone Standard must not be assigned to resource accounts; when converting, remove Teams Phone Standard and assign the Resource Account license in the same license activity, otherwise the resource account (and its auto attendants and call queues) may stop working.
    Microsoft Teams Phone Resource Account licenses · Microsoft Teams Phone Resource Account licenses, section 'Change an existing resource account to use a Microsoft Teams Phone Resource Account license', Warning block · Checked 2026-09-24
  73. 75
    By default, calls between Teams users in the same organization are handled natively within Teams and never go to the PSTN.
    What is Teams Phone · What is Teams Phone, second paragraph · Checked 2026-09-24
  74. 76
    Microsoft supports Teams Phone with Direct Routing only when certified SBCs are used, expects the SBC vendor to investigate first and escalate, and may decline support requests involving non-certified SBCs.
    Plan Direct Routing · Plan Direct Routing, sections 'Supported Session Border Controllers (SBCs)' and 'Support boundaries' · Checked 2026-09-24
  75. 77
    Direct Routing requires a Microsoft-certified SBC, PSTN trunks to it, users homed online, a public IP, an SBC FQDN in a verified tenant domain (not *.onmicrosoft.com) with public DNS, and a publicly trusted TLS certificate.
    Plan Direct Routing · Plan Direct Routing, section 'Infrastructure requirements' table and section 'SBC domain names' · Checked 2026-09-24
  76. 78
    For Microsoft 365, Office 365 and GCC, the SBC connects to sip.pstnhub.microsoft.com, sip2.pstnhub.microsoft.com and sip3.pstnhub.microsoft.com in priority order over SIP/TLS to port 5061; GCC High uses sip.pstnhub.gov.teams.microsoft.us and DoD uses sip.pstnhub.dod.teams.microsoft.us.
    Plan Direct Routing · Plan Direct Routing, sections 'SIP signaling: FQDNs', 'SIP signaling: GCC High', 'SIP signaling: DoD', 'SIP signaling ports' · Checked 2026-09-24
  77. 79
    Direct Routing media between Microsoft media processors and the SBC uses UDP/SRTP ports 3478-3481 and 49152-53247 in both directions, and Microsoft recommends at least two media ports per concurrent call on the SBC.
    Plan Direct Routing · Plan Direct Routing, section 'Media ports' table and Tip · Checked 2026-09-24
  78. 80
    Under Operator Connect, the operator is responsible for PSTN connectivity, number provisioning and porting, calling services and PSTN-related support; Microsoft is responsible for Teams services, Teams Phone administration, the Teams admin center and the Teams-to-operator integration.
    Plan for Operator Connect · Plan for Operator Connect, section 'Support boundaries' · Checked 2026-09-24
  79. 81
    A Teams coexistence design can pass calls between Teams and Aura users through a certified SBC such as Avaya SBCE between Session Manager and Direct Routing, since Microsoft positions Direct Routing for third-party PBX integration and certifies ASBCE.inferred
    Plan Direct Routing · Plan Direct Routing, 'Why choose Direct Routing?' and architecture diagram · Checked 2026-09-25
  80. 82
    Communication Manager vector/VDN call flows have no one-to-one Teams or Webex Calling object; a typical rebuild splits time-of-day and menu logic into auto attendants and queueing into call queues or hunt groups, and complex vectors (skills, database lookups) need a contact center platform.inferred
    Planning - Overview of voice applications · Planning overview, 'Auto Attendant', 'Call Queue' and 'Summary' · Checked 2026-09-25
  81. 83
    Auto attendants and call queues are not available with a Teams Enterprise license alone; they require Teams Phone licensing, with resource accounts using Teams Phone Resource Account licenses.
    Teams Phone features · Teams Phone features, table 'Teams calling features', rows 'Auto attendants' and 'Call queues' · Checked 2026-09-24
  82. 84
    Migration providers pitch connecting Avaya J-Series handsets directly to Teams through Microsoft SIP Gateway as a hardware-reuse path, with Aura coexisting with Teams in a phased or long-term hybrid model.field report
    Migrate from Avaya Aura to Microsoft Teams Phone · Landing page bullets 'Strategic Interoperability' and hardware reuse · Checked 2026-09-25
  83. 85
    To use SIP Gateway, Teams users must have a phone number with PSTN calling enabled, plus Microsoft Teams, Skype for Business Online (Plan 2), Microsoft Phone System and PSTN connectivity; SIP Gateway is not yet available for DoD.
    Plan SIP Gateway · Plan SIP Gateway, section 'Requirements to use SIP Gateway' and subsection 'Hardware, software, and licenses' · Checked 2026-09-24
  84. 86
    SIP devices on SIP Gateway can be call queue agents, but SIP Gateway does not publish presence for them, so presence-based routing is not supported.
    Plan SIP Gateway · Plan SIP Gateway, section 'Benefits of SIP Gateway', bullet 'Call Queues and voice apps support' · Checked 2026-09-24
  85. 87
    SIP Gateway automatically offboards stale devices: paired (signed-in) devices after 30 days without a connection and unpaired (signed-out) devices after 14 days, and an offboarded device can be onboarded again after a factory reset.
    Plan SIP Gateway · Plan SIP Gateway, section 'Benefits of SIP Gateway', bullet 'Off board stale devices' · Checked 2026-09-24
  86. 88
    When Direct Routing is used, a Calling Plan license is not required for Common Area Phones.
    Plan Direct Routing · Plan Direct Routing, section 'Supported endpoints' · Checked 2026-09-24
  87. 89
    The Microsoft Teams Shared Device license (for common area phones) and the Microsoft Teams Rooms Pro license both include the Microsoft 365 Phone System application, and Shared Device licenses are supported only for telephone devices.
    Teams Phone licensing · Teams Phone licensing, sections 'Licensing Teams Phone - for shared devices' and 'Considerations' · Checked 2026-09-24
  88. 90
    A Microsoft Teams Enterprise license is not required when licensing Teams Phone for shared devices or for voice applications.
    Teams Phone licensing · Teams Phone licensing, section 'Considerations', first paragraph · Checked 2026-09-24
  89. 91
    Direct Routing requires specific emergency call routing policies, whereas with the other PSTN options the carrier handles much of the emergency call routing configuration.
    Plan and manage emergency calling · Plan and manage emergency calling, section 'Emergency call routing' · Checked 2026-09-24
  90. 92
    Dynamic emergency calling, which routes emergency calls and notifies security personnel based on the Teams client's current location, is available for Microsoft Calling Plans, Operator Connect, Teams Phone Mobile and Direct Routing.
    Plan and manage emergency calling · Plan and manage emergency calling, section 'Dynamic emergency calling' · Checked 2026-09-24
  91. 93
    To assign an emergency location to a network identifier for dynamic emergency calling, the emergency address must be validated and carry a geo code; addresses created with the Teams admin center map search get both automatically.
    Plan and manage emergency calling · Plan and manage emergency calling, sections 'Emergency address validation' and 'Emergency address geo codes', Important block · Checked 2026-09-24
  92. 94
    Microsoft lists security desk notifications for emergency calls as available with Microsoft Calling Plans, Operator Connect and Direct Routing; the security desk is conferenced into the call as set by the Teams emergency calling policy.
    Plan and manage emergency calling · Plan and manage emergency calling, section 'Security desk notifications' · Checked 2026-09-24

Documents

tier 2 current vendor documentation

Configure call routing for Direct Routing

Microsoft · 2026-09-10 · accessed 2026-09-21

tier 2 current vendor documentation

Connect your Session Border Controller (SBC) to Direct Routing

Microsoft · 2026-04-26 · accessed 2026-09-21

tier 2 current vendor documentation

How to export the active 'station service link extension' from a station from the Communication Manager with Site Administration?

Avaya · 2019-09-12 · accessed 2026-09-25

tier 2 current vendor documentation

Microsoft Teams Dial plans for phone call routing

Microsoft · 2025-08-11 · accessed 2026-09-23

tier 2 current vendor documentation

Microsoft Teams Phone Resource Account licenses

Microsoft · 2026-04-26 · accessed 2026-09-24

tier 2 current vendor documentation

Plan and manage emergency calling

Microsoft · 2026-03-23 · accessed 2026-09-16

tier 2 current vendor documentation

Plan Direct Routing

Microsoft (Microsoft Learn) · 2026-08-21 · accessed 2026-09-06

tier 2 current vendor documentation

Plan for Operator Connect

Microsoft (Microsoft Learn) · 2026-08-24 · accessed 2026-09-06

tier 2 current vendor documentation

Plan SIP Gateway

Microsoft · 2026-07-06 · accessed 2026-09-30

tier 2 current vendor documentation

Plan SIP Gateway

Microsoft · 2025-02-28 · accessed 2026-09-16

tier 2 current vendor documentation

Planning - Overview of voice applications

Microsoft · 2026-08-31 · accessed 2026-09-24

tier 2 current vendor documentation

Planning - Overview of voice applications

Microsoft · 2026-08-31 · accessed 2026-09-21

tier 2 current vendor documentation

PSTN connectivity options

Microsoft (Microsoft Learn) · 2026-08-06 · accessed 2026-09-06

tier 2 current vendor documentation

Session Border Controllers certified for Direct Routing - Microsoft Teams

Microsoft · 2026-05-27 · accessed 2026-09-14

tier 2 current vendor documentation

Set your coexistence and upgrade settings

Microsoft · 2026-02-04 · accessed 2026-09-21

tier 2 current vendor documentation

Setup - Call Queue - Microsoft Teams

Microsoft · 2026-08-31 · accessed 2026-09-24

tier 2 current vendor documentation

Teams Contact Center - Microsoft Teams

Microsoft · 2026-07-29 · accessed 2026-09-14

tier 2 current vendor documentation

Teams Phone features

Microsoft · 2025-04-25 · accessed 2026-09-24

tier 2 current vendor documentation

Teams Phone licensing

Microsoft · 2026-04-28 · accessed 2026-09-16

tier 2 current vendor documentation

Transfer phone numbers to Microsoft Teams

Microsoft · 2026-05-28 · accessed 2026-09-21

tier 2 current vendor documentation

Unable to export station, VDN, vector information using Avaya Site Administration (ASA).

Avaya · 2018-09-12 · accessed 2026-09-25

tier 2 current vendor documentation

What is Teams Phone

Microsoft (Microsoft Learn) · 2026-03-03 · accessed 2026-09-06

tier 2 current vendor documentation

What's a port order? - Microsoft Teams

Microsoft · 2026-05-28 · accessed 2026-09-24

tier 4 archived vendor documentation

Avaya End of Life List: Models & EOL Dates (2026)

ContactCenterGuide.com (Foretel Solutions) · 2026-08-14 · accessed 2026-09-25

tier 4 archived vendor documentation

SAT Command Cheat Sheet

PBXbook · 2026-09-30 · accessed 2026-09-30

tier 5 independent technical research

Avaya Aura Integration with Microsoft Teams Direct Routing Docs

Tek-Tips forum · 2023-11-17 · accessed 2026-09-30

tier 5 independent technical research

Migrate from Avaya Aura to Microsoft Teams Phone

SIPPIO · accessed 2026-09-25

Cite this page

APA

WarmTransfer. (2026, September 30). Avaya Aura to Teams Phone. WarmTransfer. https://warmtransfer.net/guides/avaya-aura-to-teams-phone

BibTeX

@misc{warmtransfer-avaya-aura-to-teams-phone,
  title  = {Avaya Aura to Teams Phone},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/guides/avaya-aura-to-teams-phone},
  note   = {Verified 2026-09-30}
}