Plan SIP Gateway

Publisher

Microsoft

URL

https://learn.microsoft.com/en-us/microsoftteams/devices/sip-gateway-plan

Published

2025-02-28

Updated

unknown

Accessed

2026-09-16

HTTP status

200

License

not stated on page; Microsoft Learn Terms of Use apply; no-redistribution; short excerpts and locators only

Source notes citing this source

• The 2N Lift IP 2.0 elevator communicator appears in the Teams SIP Gateway compatible device list with firmware 2.46.1. in context
• Teams SIP Gateway lists the Algo 8301, 8373 and 8305 as compatible paging adapters, and Microsoft directs support queries for listed Algo endpoints to Algo. in context
• On Teams SIP Gateway several AudioCodes MediaPack ATAs expose fewer than all ports: MP114 3 of 4, MP118 6 of 8 and MP124 18 of 24, while MP112, MP1288 and the MP50x models have all ports available. in context
• Teams SIP Gateway lists Cisco ATA191-MPP and ATA192-MPP as compatible devices with minimum firmware 11.2.2MPP and approved firmware 11-3-1MPP. in context
• Teams SIP Gateway lists Poly ATA 400 and ATA 402 (firmware 4.0.1.6480) and Poly OBi 300 and OBi 302 (minimum 3.2.4.8441, approved 3.2.5.8732) as compatible. in context
• Teams users must have a phone number with PSTN calling enabled to use SIP Gateway, and SIP Gateway is not yet available for DoD. in context
• On Teams SIP Gateway the listed ATAs (Cisco ATA191/192, Poly ATA 40x and OBi 30x, AudioCodes MP series) and Algo paging adapters carry footnote 3, meaning they support only static location, not dynamic location discovery. in context
• 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. in context
• 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. in context
• To use SIP Gateway, Teams users must have a phone number with PSTN calling enabled. in context
• Cisco ATA191-MPP and ATA192-MPP carry footnote marker 3 in the compatible devices table, whose definition is that the device supports only static location with SIP Gateway. inferred in context
• SIP Gateway automatically offboards stale devices provisioned for a tenant: paired devices not connected for 30 days, and unpaired devices after 14 days; an offboarded device can be onboarded again after a factory reset. in context
• Compatible Cisco SIP IP phones support dynamic location discovery over LLDP only, and the page's footnote markers show the Cisco MPP phones and the ATA191/192-MPP as supporting dynamic location discovery through LLDP. in context
• For Cisco, devices running enterprise firmware must be converted to multiplatform firmware, and the compatible table lists 6821, 6841, 6851, 6861, 6871, 7811, 7821, 7841, 7861, 8811, 8841, 8845, 8851, 8861, 8865 and 8832 with minimum 11.1.1MPP and approved 12-0-7MPP, ATA191-MPP and ATA192-MPP at minimum 11.2.2MPP and approved 11-3-1MPP, and 8875 plus the 9841/9851/9861/9871 at PhoneOS 3.3.1. in context
• SIP Gateway lets an organisation use any compatible SIP device with Microsoft Teams, including Skype for Business IP phones with standard SIP firmware, Cisco IP phones with multiplatform SIP firmware, and SIP devices from Poly, Yealink and AudioCodes. in context
• Customers can use SIP devices as call queue agents with restrictions, for instance SIP Gateway does not publish presence for devices so presence-based routing is not supported. in context
• Teams users must have a phone number with PSTN calling enabled to use SIP Gateway, and SIP Gateway is not yet available for DoD. in context
• SIP Gateway supports compatible SIP devices including Cisco IP phones, but Cisco devices running enterprise firmware must first be converted to multiplatform (MPP) firmware. in context
• 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. in context
• 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. in context
• 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. in context
• SIP Gateway lets compatible third-party SIP devices sign in to Teams and make and receive calls. Examples are Cisco IP phones on multiplatform (MPP) firmware, Poly VVX and Trio, Yealink T-series and AudioCodes 400HD; Cisco phones on enterprise firmware must be converted to MPP first. in context
• SIP Gateway devices can be call queue agents, but SIP Gateway does not publish presence for devices, so presence-based routing is not supported for them. in context
• To use SIP Gateway, a Teams user must have a phone number with PSTN calling enabled; the licence requirements listed are Teams, Skype for Business Online Plan 2, Microsoft Phone System and PSTN connectivity. SIP Gateway is not yet available for DoD. in context
• SIP Gateway automatically offboards stale devices: signed-in (paired) devices after 30 days without a connection, signed-out (unpaired) devices after 14 days. An offboarded device can be onboarded again after a factory reset. in context

Cite this source record

APA

WarmTransfer. (2025, February 28). Plan SIP Gateway. WarmTransfer. https://warmtransfer.net/knowledge/sources/ms-learn-sip-gateway-plan

BibTeX

@misc{warmtransfer-ms-learn-sip-gateway-plan,
  title  = {Plan SIP Gateway},
  author = {{WarmTransfer}},
  year   = {2025},
  url    = {https://warmtransfer.net/knowledge/sources/ms-learn-sip-gateway-plan},
  note   = {Microsoft, accessed 2026-09-16}
}