# Migrating from Avaya Aura

Canonical: https://warmtransfer.net/knowledge/avaya-aura-migration

Last verified: 2026-09-25

Avaya announced Avaya Aura 10.3 on August 4, 2026, with expected general availability on September 28, 2026[^16][^17]. Migration planning away from Avaya Aura encompasses hardware and software lifecycle milestones, discovery of existing Communication Manager configurations, and coexistence or target routing on platforms such as Microsoft Teams Phone and Webex Calling[^8][^23][^49].

## Aura Platform and Hardware Lifecycle

WarmTransfer's reading of the sources is that 10.2 was the newest generally available Aura release as of 2026-09-25, because Release 10.3 had not yet reached its stated expected GA date on that date[^4]. Aura 10.3 continues Joint Interoperability Test Command (JITC) certification for U.S. federal and military environments, implements 4096-bit RSA keys for certificates, extends Trellix antivirus support to JITC-compliant environments, moves to Red Hat Enterprise Linux 9.6, and supports VMware ESXi 9.x[^2][^6][^5]. The Aura 10.3 announcement does not state an end-of-support date or support duration for the release[^3]. For earlier releases, an independent Avaya lifecycle compilation lists end of manufacturer support for Avaya Aura 8.x as March 6, 2023[^19].

Media gateway hardware support boundaries depend on physical provenance: in the field, gateways of the same G450 model can fall on opposite sides of a support boundary because support depends on hardware vintage, requiring migration inventories to capture the vintage and not just the model[^34].

## Configuration Discovery via Avaya Site Administration

Avaya's knowledge base gives System > Advanced > Export Data in Avaya Site Administration (ASA) as the way to export station parameters from Communication Manager[^8]. The ASA export cannot export or show a station's active service link extension directly[^9]. Furthermore, On ASA 6.0.07 with CM R016x, 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[^10]. Closing the GEDI or emulator window allows ASA to export the station, VDN, and vector data[^7]. WarmTransfer's reading of the sources is that an ASA field export is not a complete configuration capture, because at least 1 station attribute (service link extension) cannot be exported, requiring migration discovery to also read the live Communication Manager configuration[^31].

## Microsoft Teams Direct Routing and Coexistence

Microsoft Direct Routing connects an organization's own telephony infrastructure to Teams Phone through a supported, customer-provided Session Border Controller (SBC)[^23]. Microsoft lists integration with third-party PBXs or analog devices as a reason to choose Direct Routing, and describes a common pattern in which Calling Plan or Operator Connect carries PSTN calling while Direct Routing carries calls to third-party PBXs and analog devices in the same tenant[^30][^24]. Direct Routing is not supported in Islands mode[^25].

For commercial Microsoft 365 tenants, the SBC signals over SIP/TLS to port 5061 on sip.pstnhub.microsoft.com, sip2.pstnhub.microsoft.com, and sip3.pstnhub.microsoft.com in priority order, and the SBC FQDN must belong to a verified Microsoft 365 domain rather than the default *.onmicrosoft.com domain[^28][^29]. Direct Routing supports SILK, G.711, G.722, G.729, and AMR-WB (non-bypass only) between Teams and the SBC[^22]. Direct Routing does not support media re-targeting: if the SBC signals a new media IP mid-call, Teams never sends media to it[^27].

Microsoft supports Teams Phone with Direct Routing only when certified SBCs are used, and may decline support cases involving non-certified SBCs[^21]. Certification applies to specific SBC firmware versions, with higher firmware supported as long as the major.minor version is the same, though Microsoft states it is not accepting new nominations for Direct Routing SBC certification until further notice[^20][^26]. Avaya Session Border Controller for Enterprise (ASBCE) is certified for Direct Routing at Release 8.1.1 or higher, Release 8.1.2 or higher for media bypass, and Release 10.2.0.2 for ELIN, with Microsoft listing ASBCE 10.1.2 or higher as supporting Local Media Optimization[^11][^12]. WarmTransfer's reading of the sources is that 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[^40].

## Endpoint and Voice Application Translation

Microsoft's SIP Gateway compatible-devices list includes Avaya J100 SIP phones (J129, J139, J159, J169, J179, J189) with a minimum and approved firmware of 4.1.11.0[^36]. To use SIP Gateway, Teams users must have a phone number with PSTN calling enabled[^38]. SIP Gateway devices can serve as call queue agents, but because SIP Gateway does not publish presence for devices, presence-based routing is not supported for them[^37]. In the field, 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[^35].

A Teams auto attendant directs callers from menu options to people, call queues, external numbers, other auto attendants, or voicemail, with separate routing for business hours, after hours, and holidays[^39]. Teams call queues do not provide separate routing for off hours and holidays, and Microsoft recommends putting an auto attendant in front of a call queue even when staffed around the clock[^42]. Call queue exception handling can redirect calls when no agents are logged in, when the number waiting exceeds a set limit, or when wait time exceeds a set limit[^41].

WarmTransfer's reading of the sources is that Communication Manager vector and VDN call flows have no 1-to-1 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, while complex vectors with skills or database lookups require a contact center platform[^43].

## Webex Calling Coexistence

Webex Calling trunks, route groups, and dial plans support migration and coexistence with premises PBXs, including mixed sites with both premises and Webex Calling users, with dial plans routing calls to on-premises destinations through trunks or route groups[^49][^44]. A Local Gateway is an on-premises device that interconnects the trunk with on-premises PSTN and/or a PBX[^47]. Webex Calling trunks are either registration-based (where the SBC performs SIP registration) or certificate-based (where Webex trusts the Local Gateway by its FQDN and certificate)[^50].

Only SBCs shown in the Control Hub device type list are validated by Cisco's partners as compatible Webex Calling Local Gateways, and a deployment using a third-party SBC requires support from both Cisco and the SBC vendor partner[^51][^45]. Cisco's Local Gateway documentation names Oracle, AudioCodes, Ribbon, anynode, and Italtel SBCs as validated third-party Local Gateways for certificate-based trunks[^48]. For hunt routing, Webex Calling hunt groups offer circular, top down, and longest idle routing (up to 1,000 agents), weighted routing (up to 100 agents), and simultaneous routing (up to 50 agents)[^46].

## See also

See also [Microsoft teams direct routing](https://warmtransfer.net/knowledge/microsoft-teams-direct-routing).
See also [Teams sip gateway](https://warmtransfer.net/knowledge/teams-sip-gateway).
See also [AudioCodes Mediant SBC](https://warmtransfer.net/knowledge/audiocodes-mediant-sbc).
See also [CUCM to Webex Calling migration](https://warmtransfer.net/knowledge/cucm-to-webex-calling).
See also [Microsoft Teams auto attendants and call queues](https://warmtransfer.net/knowledge/teams-auto-attendant-call-queue).

## Applicability

Applies to: Avaya Aura, Avaya Site Administration, Microsoft Teams Phone, Cisco Webex Calling, Avaya G430, Avaya Communication Manager, Microsoft Teams SIP Gateway, and Avaya J100 Series IP Phones. Deployments: on-premises, hybrid, and multi-tenant. Sources checked 2026-09-25. The JITC certification stated for Avaya Aura 10.3 applies to U.S. federal and military environments[^2]. Avaya Site Administration export task failure when GEDI or terminal emulator sessions remain open is documented for ASA performing only 1 task at a time[^10]. Avaya SBCE Direct Routing certification applies to 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[^11][^12]. Avaya J100 series SIP Gateway support requires firmware 4.1.11.0 on J129, J139, J159, J169, J179, and J189 devices[^36].

## What remains uncertain

End of sale and end of manufacturer support dates for Avaya Aura 10.3 are not covered by the sources below, and the Aura 10.3 announcement does not state an end-of-support date or support duration[^3]. Authoritative mapping of Communication Manager vectors, VDNs, and hunt groups to Teams auto attendants, call queues, and Webex Calling features is not covered by the sources below. Whether Avaya SBCE appears in the Control Hub Local Gateway device-type list is not covered by the sources below. Whether Avaya J100 phones can register to Webex Calling as generic or third-party SIP devices is not covered by the sources below. A cloud PBX target for Avaya Aura migrations including BYOC coexistence is not covered by the sources below. Number porting sequencing when exiting Avaya carrier trunks to Teams Calling Plan or Operator Connect is not covered by the sources below. Migrating Avaya Aura Messaging or Modular Messaging mailboxes and greetings is not covered by the sources below. Replacing Avaya CMS reporting for vector and skill traffic after migration is not covered by the sources below.

## Sources

[^1]: An organization still on Aura 10.1 during a multi-quarter migration is running an Aura release past end of manufacturer support, so it must either upgrade to 10.2 as an interim step or accept running without manufacturer fixes until cutover (inferred). Source: [End of Manufacturer Support Notice (Avaya Aura Platform Release 10.1)](https://support.avaya.com/css/public/documents/101090414), End of Manufacturer Support Notice, effective-date and options paragraphs (PDF; not text-verified). Checked 2026-09-25.
[^2]: Avaya says Aura 10.3 continues Joint Interoperability Test Command (JITC) certification for U.S. federal and military environments. Source: [Avaya Aura 10.3 Gives Enterprises a Secure, Long-Term Path to Modernize](https://www.avaya.com/en/newsroom/2026/pr-us-260804/), Press release, security highlights paragraph. Checked 2026-09-25.
[^3]: The Aura 10.3 announcement does not state an end-of-support date or support duration for the release. Source: [Avaya Aura 10.3 Gives Enterprises a Secure, Long-Term Path to Modernize](https://www.avaya.com/en/newsroom/2026/pr-us-260804/), Whole press release (absence of lifecycle date). Checked 2026-09-25.
[^4]: As of 2026-09-25 Avaya Aura 10.3 had not yet reached its stated expected GA date, so 10.2 was the newest generally available Aura release on that date (inferred). Source: [Avaya Aura 10.3 Gives Enterprises a Secure, Long-Term Path to Modernize](https://www.avaya.com/en/newsroom/2026/pr-us-260804/), Press release, availability paragraph (compared against access date). Checked 2026-09-25.
[^5]: Avaya says Aura 10.3 moves to Red Hat Enterprise Linux 9.6 and supports VMware ESXi 9.x. Source: [Avaya Aura 10.3 Gives Enterprises a Secure, Long-Term Path to Modernize](https://www.avaya.com/en/newsroom/2026/pr-us-260804/), Press release, operating system and virtualization paragraph. Checked 2026-09-25.
[^6]: Aura 10.3 implements 4096-bit RSA keys for certificates and extends Trellix antivirus support to JITC-compliant environments. Source: [Avaya Aura 10.3 Gives Enterprises a Secure, Long-Term Path to Modernize](https://www.avaya.com/en/newsroom/2026/pr-us-260804/), Press release, security highlights paragraph. Checked 2026-09-25.
[^7]: Closing the GEDI or emulator window allowed ASA to export the station, VDN and vector data. Source: [Unable to export station, VDN, vector information using Avaya Site Administration (ASA).](https://support.avaya.com/public/index?page=content&id=SOLN329388&actp=LIST), SOLN329388, Solution section. Checked 2026-09-25.
[^8]: Avaya's knowledge base gives System > Advanced > Export Data in Avaya Site Administration as the way to export station parameters from Communication Manager. Source: [How to export the active 'station service link extension' from a station from the Communication Manager with Site Administration?](https://support.avaya.com/public/index?page=content&id=FAQ116513&actp=LIST), FAQ116513, Answer section. Checked 2026-09-25.
[^9]: The ASA export cannot export or show a station's active service link extension directly. Source: [How to export the active 'station service link extension' from a station from the Communication Manager with Site Administration?](https://support.avaya.com/public/index?page=content&id=FAQ116513&actp=LIST), FAQ116513, Answer section. Checked 2026-09-25.
[^10]: 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. Source: [Unable to export station, VDN, vector information using Avaya Site Administration (ASA).](https://support.avaya.com/public/index?page=content&id=SOLN329388&actp=LIST), SOLN329388, Problem and Cause sections. Checked 2026-09-25.
[^11]: Avaya Session Border Controller for Enterprise is certified for Direct Routing at Release 8.1.1 or higher, 8.1.2 or higher for media bypass, and 10.2.0.2 for ELIN. Source: [Session Border Controllers certified for Direct Routing - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-border-controllers), Certified SBC vendors table, Avaya row. Checked 2026-09-25.
[^12]: Microsoft lists Avaya SBCE 10.1.2 or higher as supporting Local Media Optimization for Direct Routing. Source: [Session Border Controllers certified for Direct Routing - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-border-controllers), Support for Local Media Optimization table, Avaya row. Checked 2026-09-25.
[^13]: Avaya SBCE does not appear among the named validated Webex Calling Local Gateway vendors, so a Webex coexistence design likely needs Cisco CUBE or a listed third-party SBC between Session Manager and Webex Calling (inferred). Source: [Get started with Local Gateway](https://help.webex.com/en-us/article/t9xctu/Get-started-with-Local-Gateway), Get started with Local Gateway, third-party SBC support section (absence of Avaya). Checked 2026-09-25.
[^14]: Avaya ended manufacturer support for Avaya Aura Platform Release 10.1 (covering Communication Manager, Session Manager and System Manager) effective January 1, 2026. Source: [End of Manufacturer Support Notice (Avaya Aura Platform Release 10.1)](https://support.avaya.com/css/public/documents/101090414), End of Manufacturer Support Notice, effective-date statement (PDF body; not text-verified). Checked 2026-09-25.
[^15]: Avaya Aura 10.2 has been available since December 18, 2023 and is the upgrade target Avaya named for customers leaving 10.1. Source: [End of Manufacturer Support Notice (Avaya Aura Platform Release 10.1)](https://support.avaya.com/css/public/documents/101090414), End of Manufacturer Support Notice, customer options / upgrade path paragraph (PDF body; not text-verified). Checked 2026-09-25.
[^16]: Avaya announced Avaya Aura 10.3 on August 4, 2026. Source: [Avaya Aura 10.3 Gives Enterprises a Secure, Long-Term Path to Modernize](https://www.avaya.com/en/newsroom/2026/pr-us-260804/), Press release dateline. Checked 2026-09-25.
[^17]: Avaya stated that Avaya Aura 10.3 is expected to be generally available on September 28, 2026. Source: [Avaya Aura 10.3 Gives Enterprises a Secure, Long-Term Path to Modernize](https://www.avaya.com/en/newsroom/2026/pr-us-260804/), Press release, availability paragraph. Checked 2026-09-25.
[^18]: The Aura 10.1 end-of-manufacturer-support notice described Avaya Aura 10.3 as tentatively planned for October 2026. Source: [Avaya End of Life List: Models & EOL Dates (2026)](https://contactcenterguide.com/avaya-end-of-life), Aura release support dates section, Aura 10.3 entry. Checked 2026-09-25.
[^19]: An independent Avaya lifecycle compilation lists end of manufacturer support for Avaya Aura 8.x as March 6, 2023. Source: [Avaya End of Life List: Models & EOL Dates (2026)](https://contactcenterguide.com/avaya-end-of-life), Aura release support dates section, Aura 8.x entry. Checked 2026-09-25.
[^20]: Direct Routing certification applies to specific SBC firmware versions, and higher firmware is supported as long as the major.minor version is the same. Source: [Session Border Controllers certified for Direct Routing - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-border-controllers), Introduction, Note on certification and firmware versions. Checked 2026-09-25.
[^21]: Microsoft supports Teams Phone with Direct Routing only when certified SBCs are used and may decline support cases involving non-certified SBCs. Source: [Plan Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan), Plan Direct Routing, 'Support boundaries'. Checked 2026-09-25.
[^22]: Direct Routing supports SILK, G.711, G.722, G.729 and AMR-WB (non-bypass only) between Teams and the SBC. Source: [Plan Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan), Plan Direct Routing, 'Supported codecs'. Checked 2026-09-25.
[^23]: Microsoft Direct Routing connects an organization's own telephony infrastructure to Teams Phone through a supported, customer-provided Session Border Controller. Source: [Plan Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan), Plan Direct Routing, introduction. Checked 2026-09-25.
[^24]: Microsoft describes a common pattern in which Calling Plan or Operator Connect carries PSTN calling while Direct Routing carries calls to third-party PBXs and analog devices in the same tenant. Source: [Plan Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan), Plan Direct Routing, 'Direct Routing with Calling Plan and Operator Connect'. Checked 2026-09-25.
[^25]: Direct Routing isn't supported in Islands mode. Source: [Plan Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan), Plan Direct Routing, Licensing requirements, Note. Checked 2026-09-25.
[^26]: Microsoft states it is not accepting new nominations for Direct Routing SBC certification until further notice. Source: [Session Border Controllers certified for Direct Routing - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-border-controllers), Introduction, sentence before 'Certified SBC vendors'. Checked 2026-09-25.
[^27]: Direct Routing does not support media re-targeting: if the SBC signals a new media IP mid-call, Teams never sends media to it. Source: [Session Border Controllers certified for Direct Routing - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-border-controllers), Closing Note on media re-targeting. Checked 2026-09-25.
[^28]: The Direct Routing SBC FQDN must belong to a verified Microsoft 365 domain; the default *.onmicrosoft.com domain can't be used. Source: [Plan Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan), Plan Direct Routing, 'SBC domain names'. Checked 2026-09-25.
[^29]: For commercial Microsoft 365 tenants the SBC signals over SIP/TLS to port 5061 on sip.pstnhub.microsoft.com, sip2.pstnhub.microsoft.com and sip3.pstnhub.microsoft.com in priority order. Source: [Plan Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan), Plan Direct Routing, 'SIP signaling: FQDNs' and 'SIP signaling ports'. Checked 2026-09-25.
[^30]: Microsoft lists integration with third-party PBXs or analog devices as a reason to choose Direct Routing. Source: [Plan Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan), Plan Direct Routing, 'Why choose Direct Routing?'. Checked 2026-09-25.
[^31]: 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). Source: [How to export the active 'station service link extension' from a station from the Communication Manager with Site Administration?](https://support.avaya.com/public/index?page=content&id=FAQ116513&actp=LIST), FAQ116513, Answer section. Checked 2026-09-25.
[^32]: Avaya ended manufacturer support for older G430 and G450 gateway vintages running Aura 10.1 and earlier effective January 1, 2026. Source: [End of Manufacturer Support Notice (G430 and G450 Media Gateway vintages)](https://support.avaya.com/css/public/documents/101094955), EoMS notice body (PDF; not text-verified). Checked 2026-09-25.
[^33]: On Aura 10.2, G430 vintages 1 and 2 and G450 vintages 1, 2 and 3 reach end of manufacturer support on June 30, 2026, while G430 vintage 3 and G450 vintage 4 continue to be supported. Source: [End of Manufacturer Support Notice (G430 and G450 Media Gateway vintages)](https://support.avaya.com/css/public/documents/101094955), EoMS notice body, vintage table (PDF; not text-verified). Checked 2026-09-25.
[^34]: 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). Source: [Avaya End of Life List: Models & EOL Dates (2026)](https://contactcenterguide.com/avaya-end-of-life), G430/G450 section, emphasis note on identical-looking G450s. Checked 2026-09-25.
[^35]: 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). Source: [Migrate from Avaya Aura to Microsoft Teams Phone](https://www.sippio.io/resources/migrate-from-avaya-aura-to-microsoft-teams-phone/), Landing page bullets 'Strategic Interoperability' and hardware reuse. Checked 2026-09-25.
[^36]: Microsoft's SIP Gateway compatible-devices list includes Avaya J100 SIP phones (J129, J139, J159, J169, J179, J189), with minimum and approved firmware 4.1.11.0. Source: [Plan SIP Gateway](https://learn.microsoft.com/en-us/microsoftteams/devices/sip-gateway-plan), Compatible devices table, Avaya row. Checked 2026-09-25.
[^37]: SIP Gateway devices can be call queue agents, but because SIP Gateway doesn't publish presence for devices, presence-based routing isn't supported for them. Source: [Plan SIP Gateway](https://learn.microsoft.com/en-us/microsoftteams/devices/sip-gateway-plan), Benefits of SIP Gateway, 'Call Queues and voice apps support'. Checked 2026-09-25.
[^38]: To use SIP Gateway, Teams users must have a phone number with PSTN calling enabled. Source: [Plan SIP Gateway](https://learn.microsoft.com/en-us/microsoftteams/devices/sip-gateway-plan), Requirements to use SIP Gateway. Checked 2026-09-25.
[^39]: A Teams auto attendant directs callers from menu options to people, call queues, external numbers, other auto attendants or voicemail, with separate routing for business hours, after hours and holidays. Source: [Planning - Overview of voice applications](https://learn.microsoft.com/en-us/microsoftteams/aa-cq-plan-overview), Planning overview, 'Auto Attendant'. Checked 2026-09-25.
[^40]: 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). Source: [Plan Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan), Plan Direct Routing, 'Why choose Direct Routing?' and architecture diagram. Checked 2026-09-25.
[^41]: Teams call queue exception handling can redirect calls when no agents are logged in, when the number waiting exceeds a set limit, or when wait time exceeds a set limit. Source: [Planning - Overview of voice applications](https://learn.microsoft.com/en-us/microsoftteams/aa-cq-plan-overview), Planning overview, 'Call Queue', exception handling list. Checked 2026-09-25.
[^42]: Teams call queues don't provide separate routing for off hours and holidays, and Microsoft recommends putting an auto attendant in front of a call queue even when it is staffed around the clock. Source: [Planning - Overview of voice applications](https://learn.microsoft.com/en-us/microsoftteams/aa-cq-plan-overview), Planning overview, 'Call Queue', final paragraph. Checked 2026-09-25.
[^43]: 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). Source: [Planning - Overview of voice applications](https://learn.microsoft.com/en-us/microsoftteams/aa-cq-plan-overview), Planning overview, 'Auto Attendant', 'Call Queue' and 'Summary'. Checked 2026-09-25.
[^44]: Webex Calling dial plans route calls to on-premises destinations through trunks or route groups. Source: [Configure trunks, route groups, and dial plans for Webex Calling](https://help.webex.com/article/n0xb944/Configure-Trunks-Route-Groups-and-Dial-Plans-for-Cisco-Webex-Calling), Configure trunks, route groups, and dial plans, Dial plans section. Checked 2026-09-25.
[^45]: A Webex Calling deployment using a third-party SBC requires support from both Cisco and the SBC vendor partner. Source: [Get started with Local Gateway](https://help.webex.com/en-us/article/t9xctu/Get-started-with-Local-Gateway), Get started with Local Gateway, third-party support model. Checked 2026-09-25.
[^46]: Webex Calling hunt groups offer circular, top down and longest idle routing (up to 1,000 agents), weighted (up to 100) and simultaneous (up to 50). Source: [Manage hunt groups in Control Hub](https://help.webex.com/en-us/article/o6rfjeb/Manage-hunt-groups-in-Control-Hub), Manage hunt groups in Control Hub, call routing options. Checked 2026-09-25.
[^47]: In Webex Calling, a Local Gateway is an on-premises device that interconnects the trunk with on-premises PSTN and/or a PBX. Source: [Configure trunks, route groups, and dial plans for Webex Calling](https://help.webex.com/article/n0xb944/Configure-Trunks-Route-Groups-and-Dial-Plans-for-Cisco-Webex-Calling), Configure trunks, route groups, and dial plans, Local Gateway definition. Checked 2026-09-25.
[^48]: Cisco's Local Gateway article names Oracle, AudioCodes, Ribbon, anynode and Italtel SBCs as validated third-party Local Gateways for certificate-based trunks. Source: [Get started with Local Gateway](https://help.webex.com/en-us/article/t9xctu/Get-started-with-Local-Gateway), Get started with Local Gateway, third-party SBC support section. Checked 2026-09-25.
[^49]: Webex Calling trunks, route groups and dial plans support migration and coexistence with premises PBXs, including mixed sites with both premises and Webex Calling users. Source: [Configure trunks, route groups, and dial plans for Webex Calling](https://help.webex.com/article/n0xb944/Configure-Trunks-Route-Groups-and-Dial-Plans-for-Cisco-Webex-Calling), Configure trunks, route groups, and dial plans, overview benefits list. Checked 2026-09-25.
[^50]: Webex Calling trunks are either registration-based, where the SBC performs SIP registration, or certificate-based, where Webex trusts the Local Gateway by its FQDN and certificate. Source: [Configure trunks, route groups, and dial plans for Webex Calling](https://help.webex.com/article/n0xb944/Configure-Trunks-Route-Groups-and-Dial-Plans-for-Cisco-Webex-Calling), Configure trunks, route groups, and dial plans, trunk type descriptions. Checked 2026-09-25.
[^51]: Only SBCs shown in the Control Hub device type list are validated by Cisco's partners as compatible Webex Calling Local Gateways. Source: [Configure trunks, route groups, and dial plans for Webex Calling](https://help.webex.com/article/n0xb944/Configure-Trunks-Route-Groups-and-Dial-Plans-for-Cisco-Webex-Calling), Configure trunks, route groups, and dial plans, device type note. Checked 2026-09-25.