Enable core Microsoft Teams calling functionality on compatible legacy SIP phones with SIP Gateway

Published Dec 06 2021 11:40 AM 57.5K Views

While Microsoft Teams phone devices provide the richest and most complete Teams experience, we understand that there are many customers with existing investments in legacy devices. To help customers leverage their existing telephony hardware as they move to Teams Phone, we are excited to announce that SIP Gateway, a solution that enables core Teams calling functionality on compatible SIP phone models from Cisco, Poly, Yealink and AudioCodes is now generally available.

Cisco IP Phones with MPP firmware (6821, 7800 series, 8800 series), Polycom SIP phones (VVX series 100, 200, 300, 400, 500, 600 etc.), Yealink (T20 series, T30 series, T40 series, T50 series), AudioCodes 400 HD series.Cisco IP Phones with MPP firmware (6821, 7800 series, 8800 series), Polycom SIP phones (VVX series 100, 200, 300, 400, 500, 600 etc.), Yealink (T20 series, T30 series, T40 series, T50 series), AudioCodes 400 HD series.

 

Currently, SIP Gateway supports the following core Teams calling functionality

  • Inbound and outbound calls
  • Call transfer
  • Meeting dial-in and dial-out
  • Device-based “do not disturb”
  • Voicemail with message waiting indicator

There is no additional cost for organizations to use SIP Gateway, and any users meeting the following requirements can use SIP Gateway

  • Users must be licensed for Teams Phone (via any Office 365 E5, Microsoft 365 license that includes Teams Phone, or as a standalone license)
  • PSTN enablement (i.e., phone number assigned) via a Microsoft Teams Calling Plan, Direct Routing, or Operator Connect
  • Common area devices require a Common Area Phone license

Follow the steps below to enable and manage SIP Gateway

  • Turn on SIP devices can be used for calls calling policy in Teams admin center and go to SIP devices under Teams devices to manage your SIP phones connected to Teams
  • Reset devices to factory settings and point them to SIP Gateway provisioning server
  • Ensure that your firewall is open to traffic from Microsoft 365 and Teams
  • Ensure that SIP devices are not behind a proxy
  • Open UDP ports 49152 to 53247, and TCP port 5061 for IP range 52.112.0.0/14 to 52.120.0.0/14
  • Onboarded SIP devices are visible in Teams admin center SIP devices tab after first sign-in

Learn more about planning for and configuring SIP Gateway in your organization.

 

Teams support for third-party IP (3PIP) phones will continue beyond 2023

Customers who use Skype for Business phones to sign into Teams via 3PIP Gateway will be able to do so beyond 2023. However, no new investments are planned for 3PIP Gateway, and 3PIP phones will be enabled via SIP Gateway after 3PIP Gateway end of life. No additional setup is needed for core functionality such as authentication, calling, calendar and presence, and meetings, using 3PIP phones.


Upgrade to Teams phone devices

While SIP Gateway and 3PIP Gateway provide valuable flexibility for organizations with SIP phone investments, Teams phone devices provide the most complete Teams experience. Upgrade to Teams phone devices today!

104 Comments
%3CLINGO-SUB%20id%3D%22lingo-sub-3030196%22%20slang%3D%22en-US%22%3EEnable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gateway%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3030196%22%20slang%3D%22en-US%22%3E%3CP%3EWhile%20Microsoft%20Teams%20phone%20devices%20provide%20the%20richest%20and%20most%20complete%20Teams%20experience%2C%20we%20understand%20that%20there%20are%20many%20customers%20with%20existing%20investments%20in%20legacy%20devices.%20To%20help%20customers%20leverage%20their%20existing%20telephony%20hardware%20as%20they%20move%20to%20Teams%20Phone%2C%20we%20are%20excited%20to%20announce%20that%20SIP%20Gateway%2C%20a%20solution%20that%20enables%20core%20Teams%20calling%20functionality%20on%20compatible%20SIP%20phone%20models%20from%20Cisco%2C%20Poly%2C%20Yealink%20and%20AudioCodes%20is%20now%20generally%20available.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Cisco%20IP%20Phones%20with%20MPP%20firmware%20(6821%2C%207800%20series%2C%208800%20series)%2C%20Polycom%20SIP%20phones%20(VVX%20series%20100%2C%20200%2C%20300%2C%20400%2C%20500%2C%20600%20etc.)%2C%20Yealink%20(T20%20series%2C%20T30%20series%2C%20T40%20series%2C%20T50%20series)%2C%20AudioCodes%20400%20HD%20series.%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F331530iAC4081A81A4C9C7B%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Phones.png%22%20alt%3D%22Cisco%20IP%20Phones%20with%20MPP%20firmware%20(6821%2C%207800%20series%2C%208800%20series)%2C%20Polycom%20SIP%20phones%20(VVX%20series%20100%2C%20200%2C%20300%2C%20400%2C%20500%2C%20600%20etc.)%2C%20Yealink%20(T20%20series%2C%20T30%20series%2C%20T40%20series%2C%20T50%20series)%2C%20AudioCodes%20400%20HD%20series.%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3ECisco%20IP%20Phones%20with%20MPP%20firmware%20(6821%2C%207800%20series%2C%208800%20series)%2C%20Polycom%20SIP%20phones%20(VVX%20series%20100%2C%20200%2C%20300%2C%20400%2C%20500%2C%20600%20etc.)%2C%20Yealink%20(T20%20series%2C%20T30%20series%2C%20T40%20series%2C%20T50%20series)%2C%20AudioCodes%20400%20HD%20series.%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ECurrently%2C%20SIP%20Gateway%20supports%20the%20following%20core%20Teams%20calling%20functionality%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EInbound%20and%20outbound%20calls%3C%2FLI%3E%0A%3CLI%3ECall%20transfer%3C%2FLI%3E%0A%3CLI%3EMeeting%20dial-in%20and%20dial-out%3C%2FLI%3E%0A%3CLI%3EDevice-based%20%E2%80%9Cdo%20not%20disturb%E2%80%9D%3C%2FLI%3E%0A%3CLI%3EVoicemail%20with%20message%20waiting%20indicator%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSTRONG%3EThere%20is%20no%20additional%20cost%20for%20organizations%20to%20use%20SIP%20Gateway%2C%20and%20any%20users%20meeting%20the%20following%20requirements%20can%20use%20SIP%20Gateway%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EUsers%20must%20be%20licensed%20for%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FMicrosoftTeams%2Fwhat-is-phone-system-in-office-365%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3ETeams%20Phone%3C%2FA%3E%20(via%20any%20Office%20365%20E5%2C%20Microsoft%20365%20license%20that%20includes%20Teams%20Phone%2C%20or%20as%20a%20standalone%20license)%3C%2FLI%3E%0A%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fpstn-connectivity%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EPSTN%20enablement%3C%2FA%3E%20(i.e.%2C%20phone%20number%20assigned)%20via%20a%20Microsoft%20Teams%20Calling%20Plan%2C%20Direct%20Routing%2C%20or%20Operator%20Connect%3C%2FLI%3E%0A%3CLI%3ECommon%20area%20devices%20require%20a%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fset-up-common-area-phones%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3ECommon%20Area%20Phone%20license%3C%2FA%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSTRONG%3EFollow%20the%20steps%20below%20to%20enable%20and%20manage%20SIP%20Gateway%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ETurn%20on%20%3CSTRONG%3ESIP%20devices%20can%20be%20used%20for%20calls%3C%2FSTRONG%3E%20calling%20policy%20in%20Teams%20admin%20center%20and%20go%20to%20%3CSTRONG%3ESIP%20devices%3C%2FSTRONG%3E%20under%20%3CSTRONG%3ETeams%20devices%3C%2FSTRONG%3E%20to%20manage%20your%20SIP%20phones%20connected%20to%20Teams%3C%2FLI%3E%0A%3CLI%3EReset%20devices%20to%20factory%20settings%20and%20point%20them%20to%20SIP%20Gateway%20provisioning%20server%3C%2FLI%3E%0A%3CLI%3EEnsure%20that%20your%20firewall%20is%20open%20to%20traffic%20from%20Microsoft%20365%20and%20Teams%3C%2FLI%3E%0A%3CLI%3EEnsure%20that%20SIP%20devices%20are%20not%20behind%20a%20proxy%3C%2FLI%3E%0A%3CLI%3EOpen%20UDP%20ports%2049152%20to%2053247%2C%20and%20TCP%20port%205061%20for%20IP%20range%2052.112.0.0%2F14%20to%2052.120.0.0%2F14%3C%2FLI%3E%0A%3CLI%3EOnboarded%20SIP%20devices%20are%20visible%20in%20Teams%20admin%20center%20%3CSTRONG%3ESIP%20devices%3C%2FSTRONG%3E%20tab%20after%20first%20sign-in%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3ELearn%20more%20about%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FPlanSIPGateway%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Eplanning%20for%3C%2FA%3E%20and%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FConfigureSIPGateway%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Econfiguring%20SIP%20Gateway%3C%2FA%3E%20in%20your%20organization.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ETeams%20support%20for%20third-party%20IP%20(3PIP)%20phones%20will%20continue%20beyond%202023%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3ECustomers%20who%20use%20Skype%20for%20Business%20phones%20to%20sign%20into%20Teams%20via%203PIP%20Gateway%20will%20be%20able%20to%20do%20so%20beyond%202023.%20However%2C%20no%20new%20investments%20are%20planned%20for%203PIP%20Gateway%2C%20and%203PIP%20phones%20will%20be%20enabled%20via%20SIP%20Gateway%20after%203PIP%20Gateway%20end%20of%20life.%20No%20additional%20setup%20is%20needed%20for%20core%20functionality%20such%20as%20authentication%2C%20calling%2C%20calendar%20and%20presence%2C%20and%20meetings%2C%20using%203PIP%20phones.%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3E%3CSTRONG%3EUpgrade%20to%20Teams%20phone%20devices%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EWhile%20SIP%20Gateway%20and%203PIP%20Gateway%20provide%20valuable%20flexibility%20for%20organizations%20with%20SIP%20phone%20investments%2C%20Teams%20phone%20devices%20provide%20the%20most%20complete%20Teams%20experience.%20Upgrade%20to%20%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fmicrosoft-teams%2Facross-devices%2Fdevices%2Fcategory%2Fdesk-phones-teams-displays%2F34%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3ETeams%20phone%20devices%3C%2FA%3E%20today!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-3030196%22%20slang%3D%22en-US%22%3E%3CP%3EWhile%20Microsoft%20Teams%20phone%20devices%20provide%20the%20richest%20and%20most%20complete%20Teams%20experience%2C%20we%20understand%20that%20there%20are%20many%20customers%20with%20existing%20investments%20in%20legacy%20devices.%20To%20help%20customers%20leverage%20their%20existing%20telephony%20hardware%20as%20they%20move%20to%20Teams%20Phone%2C%20we%20are%20excited%20to%20announce%20that%20SIP%20Gateway%2C%20a%20solution%20that%20enables%20core%20Teams%20calling%20functionality%20on%20compatible%20SIP%20phone%20models%20from%20Cisco%2C%20Poly%2C%20Yealink%20and%20AudioCodes%20is%20now%20generally%20available.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Phones.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F331529i49D033CBA229ACA7%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Phones.png%22%20alt%3D%22Phones.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3030196%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECalling%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3034506%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3034506%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F445155%22%20target%3D%22_blank%22%3E%40tratz1210%3C%2FA%3E%26nbsp%3B%26nbsp%3BHi%20Tracy%2C%3C%2FP%3E%0A%3CP%3EApologies%20for%20the%20confusion%2C%20we%20will%20also%20edit%20the%20document%20for%20clarity%20-%20the%20feature%20code%20is%20*55*%20as%20described%20in%20the%20doc.%20You%20cannot%20set%20it%20to%20something%20else.%20From%20the%20SIP%20phone%20you%20must%20dial%20the%20*55*%26lt%3B6%20digit%20verification%20code%20generated%20in%20TAC%20for%20the%20device%26gt%3B.%20As%20the%20example%20states%2C%20if%20the%20verification%20code%20is%20123456%2C%20then%20you%20will%20have%20to%20dial%20*55*123456%20to%20enroll%20the%20device%20for%20remote%20sign-in.%20You%20will%20not%20need%20to%20perform%20the%20enrollment%20step%20if%20the%20device%20has%20been%20signed-in%20locally%20at%20least%20once.%20Hope%20this%20clarifies.%3CBR%20%2F%3E%3CBR%20%2F%3ECheers%2C%3C%2FP%3E%0A%3CP%3EChandranshu%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3034508%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3034508%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F972382%22%20target%3D%22_blank%22%3E%40AValenzuela%3C%2FA%3E%3CBR%20%2F%3EAlex%2C%20we%20only%20support%20one%20line%20per%20device.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3034509%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3034509%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1499%22%20target%3D%22_blank%22%3E%40Peter%20Farrell%3C%2FA%3E%26nbsp%3BE911%20is%20on%20the%20roadmap%20for%20SIP%20Gateway.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3034510%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3034510%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1241803%22%20target%3D%22_blank%22%3E%40bshvk%3C%2FA%3E%26nbsp%3BThe%26nbsp%3B%3CSPAN%3EAllowCallRedirect%3C%2FSPAN%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%20attribute%20is%20very%20much%20there.%20It's%20not%20listed%20in%20the%20cmdlet%20documentation%20yet.%20However%2C%20if%20you%20update%20the%20version%20of%20your%20PS%20module%20to%20the%20latest%20one%20and%20view%20the%20CsTeamsCallingPolicy%2C%20you%20will%20find%20it.%20It%20needs%20to%20be%20set%20to%20allow%20local%20forwarding%2C%20as%20well%20as%20to%20enable%20basic%20SIP%20Gateway%20functionality.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3034539%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3034539%22%20slang%3D%22en-US%22%3E%3CP%3EAny%20plans%20to%20support%20cordless%20SIP%20handsets%3F%26nbsp%3B%20I%20have%20dozens%20of%20Yealink%20handsets%20running%20off%20W52P%20base%20stations%20going%20to%20waste.%26nbsp%3B%20These%20users%20have%20all%20been%20moved%20to%20expensive%20mobile%20devices%20that%20provide%20a%20very%20average%20experience%20via%20the%20Teams%20app.%26nbsp%3B%20Support%20for%20cordless%20handsets%20would%20be%20a%20game%20changer.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3034678%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3034678%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EWe%E2%80%99ve%20found%20that%20these%20SIP%20devices%2C%20they%20are%20not%20able%20to%20get%20calls%20from%20the%20call%20queues.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EIs%20this%20feature%20in%20the%20roadmap%20already%20%3F%20If%20yes%20is%20there%20a%20way%20to%20get%20a%20delivery%20date%20%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EMany%20thanks%20in%20advance%20for%20taking%20care%20of%20this.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3034907%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3034907%22%20slang%3D%22en-US%22%3E%3CP%3EUPDATE%201%2F13%2F2022%3A%20The%20reason%20I%20was%20having%20the%20issue%20below%20is%20because%20I%20was%20attempting%20to%20provision%20to%20Teams%20while%20the%20Skype%20for%20Business%20firmware%20was%20installed%20on%20the%20Yealink%20phone.%20Apparently%2C%20it%20is%20necessary%20to%20request%20an%20unlocked%20'SIP%20Phone'%20license%20from%20Yealink%20(using%20the%20device%20MAC%20address)%2C%20and%20then%20apply%20the%20'SIP'%20version%20of%20the%20firmware.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHere%20Yealink's%20KB%20on%20how%20to%20switch%20to%20the%20SIP%20edition%20firmware%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fsupport.yealink.com%2Fen%2Fportal%2Fknowledge%2Fshow%3Fid%3D1d124b50a40b7b0471180dd1%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3EYealink%20Support%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20original%20post%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHas%20anyone%20had%20any%20luck%20provisioning%20a%20Yealink%20T41s%20phone%20to%20Teams%3F%20My%20Polycom%20phones%20work%20fine%20with%20this%20method.%20After%20factory%20resetting%20and%20pointing%20the%20Yealink%20to%20the%20provisioning%20server%20URL%2C%20it%20seems%20to%20provision.%20However%2C%20when%20I%20sign%20in%20as%20a%20Teams%20user%2C%20it's%20still%20signing%20in%20as%20a%20'Skype%20for%20Business%20Certified%20Phone'%20and%20doesn't%20show%20up%20in%20Teams%20admin%20center%26gt%3BSIP%20devices.%20What%20could%20I%20be%20missing%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3034970%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3034970%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1245213%22%20target%3D%22_blank%22%3E%40Chandranshu%3C%2FA%3E%26nbsp%3BThanks%20for%20the%20confirmation.%20Can%20you%20elaborate%20on%20where%20the%20limitation%20exists%3F%20Is%20this%20something%20that%20is%20not%20possible%20on%20the%20SIP%20gateway%20or%20was%20there%20something%20changed%20on%20the%20phones%20firmware%20to%20prevent%20this%20functionality%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3035441%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3035441%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CUL%3E%3CLI%3EI%20have%20managed%20to%20get%20a%20yealink%20t53w%20working%20on%20sip%20gateway%2C...%20This%20is%20great!%26nbsp%3B%20However%2C%20jus%20looking%20at%20it%20from%20an%20end%20user%20functionality%2C%20traditionally%2C%20with%20SIP%20phones%20we%20had%204%20digit%20ext.%20number%20to%20make%20internal%20calls%20....%20Is%20there%20anyway%20with%20the%20SIP%20device%20we%20could%20search%20MS%20Outlook%20contacts%3F..%20at%20the%20moment%20it%20appears%20calling%20INTERNAL%20users%20would%20mean%20we%20would%20need%20to%20dial%20their%20full%20DDI%20Teams%20number%20or%20update%20eaxh%20sip%20phone%20local%20phonebook%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3035535%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3035535%22%20slang%3D%22en-US%22%3E%3CP%3Eawesome%20update%26nbsp%3B%3CIMG%20class%3D%22lia-deferred-image%20lia-image-emoji%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Fhtml%2F%40B71AFCCE02F5853FE57A20BD4B04EADD%2Fimages%2Femoticons%2Fcool_40x40.gif%22%20alt%3D%22%3Acool%3A%22%20title%3D%22%3Acool%3A%22%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3035550%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3035550%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F972382%22%20target%3D%22_blank%22%3E%40AValenzuela%3C%2FA%3E%26nbsp%3BThis%20feature%20is%20not%20supported%20on%20SIP%20Gateway.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1045061%22%20target%3D%22_blank%22%3E%40Az3ncloud625%3C%2FA%3E%26nbsp%3BDirectory%20search%20is%20a%20roadmap%20item%20for%20us.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3035624%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3035624%22%20slang%3D%22en-US%22%3E%3CP%3ETrying%20to%20enroll%20a%20Poly%20VVX411.%3CBR%20%2F%3EHave%20the%20Teams%20sign%20in%20option.%3CBR%20%2F%3Ecan't%20get%20passed%20it%2C%20always%20shows%3A%26nbsp%3B%20An%20error%20occurred.%20please%20try%20again%20later.%3CBR%20%2F%3Eanyone%20else%20had%20similar%20problems%20and%20was%20able%20to%20resolve%20it%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3035710%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3035710%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRONG%3E%5BEDIT%3A%20Oooh%20I%20take%20that%20back!%20Apparently%2C%20other%20engineers%20have%20it%20working%20with%20Conference%20Mode%20disabled%20on%20the%20Call%20Queue...%20I%20need%20to%20go%20test%20this%5D%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F45624%22%20target%3D%22_blank%22%3E%40Pietro%20Rossini%3C%2FA%3E%26nbsp%3BI%20wouldn't%20expect%20to%20see%20this%20feature%20anytime%20soon.%3CBR%20%2F%3EMicrosoft%20has%20stated%20very%20clearly%20from%20the%20initial%20announcement%20of%20the%20SIP%20gateway%20that%20the%20feature%20was%20for%20%22Basic%20Calling%20Only%22%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20way%20that%20AutoAttendants%20works%20in%20Teams%20is%20ALOT%20different%20from%20how%20a%20more%20traditional%20PBX%20like%20Asterisk%20works%20in%20that%20it%20just%20forks%20invites%20over%20and%20over.%20The%20AutoAttendant%20relies%20heavily%20on%20talking%20to%20the%20Teams%20Presence%20system%2C%20which%20the%20current%20implementation%20of%20the%20SIP%20gateway%20doesn't%20have%20(remember%20DND%20is%20not%20a%20status%2C%20it%20just%20rejects%20any%20invites%20sent%20to%20the%20phone)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3035806%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3035806%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F122929%22%20target%3D%22_blank%22%3E%40Wilfried%20van%20Oosterhout%3C%2FA%3E%26nbsp%3Bi've%20the%20same%20error%20on%20the%20VVX411%20in%20corporate%20environment.%3C%2FP%3E%3CP%3EAs%20I%20was%20able%20on%20same%20phone%20to%20sign%20in%20from%20home%20just%20today%2C%20I%20suggest%20to%20take%20a%20look%20at%20firewall%20exceptions%3C%2FP%3E%3CP%3EI%20was%20not%20able%20to%20enroll%20it%20for%20CAP%20phone%2C%20probably%20for%20same%20reason%20but%20as%20it%20work%20as%20a%20user%20%2C%20i%20know%20where%20to%20dig%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3036326%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3036326%22%20slang%3D%22en-US%22%3E%3CP%3EHow%20about%20using%20Algo%20devices%20such%20as%20loud%20ringers%2C%20strobes%20and%20door%20stations%20along%20with%20Fanvil%20door%20stations%3F%20Would%20it%20be%20worth%20trialling%20these%20devices%20or%20is%20it%20a%20definite%20%22no%20they%20won't%20work%22%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3037071%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3037071%22%20slang%3D%22en-US%22%3E%3CP%20data-unlink%3D%22true%22%3E%40%3CSPAN%20class%3D%22%22%3E%3CSPAN%20class%3D%22%22%3EVertebre85%26nbsp%3B%20and%26nbsp%3B%3C%2FSPAN%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F122929%22%20target%3D%22_blank%22%3E%40Wilfried%20van%20Oosterhout%3C%2FA%3E%26nbsp%3B%3CSPAN%3E%26nbsp%3B%2C%26nbsp%3B%20I%20have%20the%20same%20problem%2C%20do%20an%20hard%20reset%20of%20the%20VVX%20(boot%20vvx%2C%20when%20application%20launch%20cancel%20and%20maintained%26nbsp%3B1%20%2B%203%20%2B%205%20key%20pad%20until%20it%20ask%20password.%20%3CA%20href%3D%22https%3A%2F%2Fwww.3cx.fr%2Fsip-phones%2Freinitialiser-polycom-vvx%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3ECe%20guide%20vous%20explique%20comment%20r%C3%A9initialiser%20un%20Polycon%20VVX%3C%2FA%3E)%26nbsp%3B%26nbsp%3B%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3E%3CSPAN%20class%3D%22%22%3E%3CSPAN%3EAfter%20this%2C%20the%20provisionning%20works%20and%20the%20logon%20too.%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3E%3CSPAN%20class%3D%22%22%3E%3CSPAN%3Eregards%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3037180%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3037180%22%20slang%3D%22en-US%22%3E%3CP%3E%40%3CSPAN%20class%3D%22%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F526576%22%20target%3D%22_self%22%3E%3CSPAN%20class%3D%22%22%3EGAUGAGNEUR%26nbsp%3B%3C%2FSPAN%3E%3C%2FA%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22%22%3E%3CSPAN%20class%3D%22%22%3EThis%20trick%20work!%20Merci%7C%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3038019%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3038019%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1248046%22%20target%3D%22_blank%22%3E%40Bonester%3C%2FA%3E%26nbsp%3BI'm%20doing%20a%20write%20up%20on%20it%20now%2C%20but%20the%20way%20that%20Microsoft%20is%20doing%20it%2C%20they%20never%20actually%20give%20you%20the%20sip%20details%20they%20setup%20a%20provisioning%20server%20profile%20for%20the%20phone%20and%20you%20login%20with%20that.%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThen%20the%20phones%20web%20interface%20hits%20the%20sign%20in%20page%2C%20which%20updates%20the%20provisioning%20server%20config%20and%20that%20passes%20the%20SIP%20details%20to%20your%20phone.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThere%20is%20also%20user%20agent%20checking%20on%20the%20provisioning%20server%20to%20stop%20you%20from%20just%20say%2C%20opening%20a%20browser%20to%20your%20phones%20mac%20address%20and%20reading%20the%20config%20by%20hand.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI'm%20working%20on%20something%20however.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3039084%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3039084%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20James%2C%20I%20will%20be%20interested%20to%20see%20what%20comes%20out%20of%20that.%20The%20Algo%20devices%20do%20support%20provisioning%20servers.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3039271%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3039271%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20testing%20a%20VVX%20410%20were%20I'm%20able%20to%20log%20in%20with%20a%20user%20account%2C%20but%20when%20I%20try%20with%20a%26nbsp%3Bcommun%20area%20phone%20account%20the%20VXX%20stay%20at%20the%20login%20screen%20where%20we%20see%20the%20pairing%20code...%20No%20error%20appear%20on%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fmicrosoft.com%2Fdevicelogin%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmicrosoft.com%2Fdevicelogin%3C%2FA%3E%26nbsp%3Band%20I%20get%20the%20confirmation%20on%20this%20web%20page%20that%20the%20phone%20is%20nw%20connected%20to%20this%20SIP%20gateway%2C%20but%20on%20the%20VVX%20itself%20nothing%20happens.%20Anyone%20else%20have%20issue%20dealing%20with%20CAP%20account%3F%20Thanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3039319%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3039319%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3C%2FP%3E%3CP%3EAnyone%20has%20any%20idea%20why%20several%20Yealink%20T42x%20signout%20without%20any%20user%20intervention%3F%3C%2FP%3E%3CP%3ERegards%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3040093%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3040093%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3EI%20have%20Yealink%20T42S%20which%20is%20working.%26nbsp%3B%20What%20do%20I%20need%20to%20do%20put%20BLF%20on%20the%20LineKeys%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBest%20regards%3C%2FP%3E%3CP%3E%C3%93li%20Ragg%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3041046%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3041046%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F71053%22%20target%3D%22_blank%22%3E%40Rafael%20Jimenez%3C%2FA%3E%26nbsp%3BPossibly%20the%20IP%20address%20of%20the%20device%20changed%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3041051%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3041051%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1252773%22%20target%3D%22_blank%22%3E%40Oliragg%3C%2FA%3E%26nbsp%3BBLF%20is%20currently%20not%20in%20scope%20for%20SIP%20Gateway.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3041054%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3041054%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F328541%22%20target%3D%22_blank%22%3E%40ga_poupart205%3C%2FA%3E%26nbsp%3B%22%3CSPAN%3EI'm%20testing%20a%20VVX%20410%20were%20I'm%20able%20to%20log%20in%20with%20a%20user%20account%2C%20but%20when%20I%20try%20with%20a%26nbsp%3Bcommun%20area%20phone%20account%20the%20VXX%20stay%20at%20the%20login%20screen%20where%20we%20see%20the%20pairing%20code...%20No%20error%20appear%20on%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fmicrosoft.com%2Fdevicelogin%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmicrosoft.com%2Fdevicelogin%3C%2FA%3E%3CSPAN%3E%26nbsp%3Band%20I%20get%20the%20confirmation%20on%20this%20web%20page%20that%20the%20phone%20is%20nw%20connected%20to%20this%20SIP%20gateway%2C%20but%20on%20the%20VVX%20itself%20nothing%20happens.%20Anyone%20else%20have%20issue%20dealing%20with%20CAP%20account%3F%20Thanks%22%3CBR%20%2F%3E%3CBR%20%2F%3ECan%20you%20please%20check%20if%20the%20phone%20shows%20up%20under%20the%20Common%20Area%20phone%20stab%20on%20Teams%20Admin%20Center%3F%20The%20device%20login%20app%20doesn't%20display%20any%20error%20messages%20at%20this%20point%2C%20we%20are%20working%20on%20that.%20One%20possible%20reason%20could%20be%20that%20your%20common%20area%20account%20may%20not%20be%20enabled%20via%20policy%20for%20SIP%20Gateway.%20See%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fsip-gateway-configure%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EConfigure%20SIP%20Gateway%20-%20Microsoft%20Teams%20%7C%20Microsoft%20Docs%3C%2FA%3E%26nbsp%3Bfor%20more%20details.%20If%20the%20issue%20persists%2C%20please%20reach%20out%20to%20support%20and%20share%20device%20logs%20to%20help%20us%20investigate%20further.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3ECheers%2C%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EChandranshu%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3041055%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3041055%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1248046%22%20target%3D%22_blank%22%3E%40Bonester%3C%2FA%3E%26nbsp%3BIt's%20not%20a%20%22definite%20no%22.%20We%20are%20committed%20to%20enabling%20customers'%20scenarios.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3041359%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3041359%22%20slang%3D%22en-US%22%3E%3CP%3EAnyone%20tried%20this%20with%20a%20MPP%20ATA%20device%3F%20Like%20Cisco%20ATA%20191%2C%20or%20192%3F%20I%20have%20a%20special%20analog%20phone%20I%20would%20like%20to%20use%20but%20no%20session%20border%20controller%20to%20enable%20ATA.%26nbsp%3B%20I%20am%20needing%20some%20kind%20of%20phone%20to%20put%20in%20an%20elevator%20-%20maybe%20there%20is%20a%20SIP%20%2F%20MPP%20phone%20that%20will%20work%20if%20anyone%20has%20any%20ideas.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3041428%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3041428%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20testing%20with%20a%20Poly%20VVX%20400%2C%20AC%20440HD%2C%20and%20Yealink%20T48S.%26nbsp%3B%20I'm%20able%20to%20add%20the%20provisioning%20server%20to%20each%20device%20manually%20through%20the%20web%20interface%2C%20but%20they%20all%20fail%20to%20register%20%2Fonboard%20with%20the%20SIP%20Gateway.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EFor%20example%2C%20the%20Poly%20VVX%20400%20restarts%20after%20entering%20the%20provisioning%20server%20info%2C%20boots%20to%20the%20main%20screen%20displaying%20the%20Teams%20Logo%20and%20Sign-In%20button%2C%20but%20presents%20an%20error%20saying%20%22Line1%3A%20%5BSIP%5D%20(Not%20Registered)%20*SIP%3AServer-1%3A%20obsbc-usea.sdg.teams.micosoft.com%20(Not%20Registered%200)%22%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20AudioCodes%20440HD%20boots%20and%20displays%20%22Registration%20in%20Progress%22%2C%20then%20immediately%20goes%20to%20%22Registration%20Failure%22%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3ESince%20the%20device%20won't%20onboard%2Fregister%20with%20the%20SIP%20Gateway%20service%2C%20it%20can't%20proceed%20to%20activate%20with%20Teams%20using%20the%20activation%20code.%26nbsp%3B%20I've%20already%20verified%20the%20SIP%20Gateway%20service%20is%20enabled%20in%20the%20TAC%20Calling%20Policy%2C%20and%20ensured%20all%20ports%20are%20open.%26nbsp%3B%20I%20have%20a%20premier%20case%20open%20with%20MSFT%2C%20so%20we'll%20see%20how%20this%20progresses.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3042397%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3042397%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F64047%22%20target%3D%22_blank%22%3E%40Jeremy%3C%2FA%3E%26nbsp%3BAs%20the%20phone%20shows%20Teams%20logo%2C%20and%20the%20sign-in%20soft%20key%2C%20it%20appears%20to%20be%20onboarded%20to%20SIP%20Gateway.%20At%20what%20point%20do%20you%20get%20the%20registration%20error%3F%20Have%20you%20tried%20initiating%20user%20sign-in%20from%20the%20device%3F%20Also%2C%20could%20you%20please%20explain%20what%20is%20the%20Teams%20activation%20code%20you%20are%20referring%20to%3F%3CBR%20%2F%3E%3CBR%20%2F%3EAn%20onboarded%20device%20must%20be%20signed-in%20to%20with%20valid%20user%20credentials%20locally%2C%20or%20remotely%20through%20Teams%20Admin%20Center%2C%20for%20it%20to%20be%20registered.%20When%20you%20press%20the%20sign-in%20key%20on%20the%20device%2C%20it%20will%20display%20a%20pairing%20code%2C%20and%20an%20authentication%20URL.%20The%20user%20must%20authenticate%20on%20another%20device%20(desktop%2Fmobile)%20by%20navigating%20to%20the%20URL%20displayed%20on%20the%20phone%2C%20and%20enter%20the%20pairing%20code%20to%20pair%20the%20device%20with%20user's%20credentials.%20If%20this%20didn't%20work%2C%20please%20share%20additional%20details%20to%20help%20investigate%20further.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3042402%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3042402%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1245213%22%20target%3D%22_blank%22%3E%40Chandranshu%3C%2FA%3E%26nbsp%3B%3CSPAN%20style%3D%22font-family%3A%20inherit%3B%22%3EI've%20been%20trying%20to%20discuss%20this%20with%20the%20team%20internally%20and%20haven't%20gotten%20answers%20to%20my%20thread.%20Can%20someone%20check%20my%20questions%20in%20the%20Teams%20MVP%20channel%2C%20please%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3042411%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3042411%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F37201%22%20target%3D%22_blank%22%3E%40James%20Arber%3C%2FA%3E%26nbsp%3BApologies.%20Please%20tag%20me%20on%20the%20the%20thread%2C%20and%20I%20will%20be%20happy%20to%20respond.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3044975%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3044975%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%26nbsp%3B%20Cisco%203905%20models%20will%20be%20compatible%2C%20any%20plan%20for%20it%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3044977%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3044977%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F64047%22%20target%3D%22_blank%22%3E%40Jeremy%3C%2FA%3E%26nbsp%3B%20did%20you%20run%20an%20hard%20reset%20on%20you%20phone%20%3F%26nbsp%3B%20it%20is%20mandatory%20to%20purge%20all%20previous%20provisionning%20cache%20and%20else.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eand%20do%20an%20Hard%20reset%2C%20not%20the%20reset%20option%20in%20web%20interface%20!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Efor%20Poly%20%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.3cx.fr%2Fsip-phones%2Freinitialiser-polycom-vvx%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3ECe%20guide%20vous%20explique%20comment%20r%C3%A9initialiser%20un%20Polycon%20VVX%20(3cx.fr)%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Efor%20audiocode%20%3A%26nbsp%3B%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.manualslib.com%2Fmanual%2F1631734%2FAudiocodes-C450hd.html%3Fpage%3D27%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3ERestoring%20The%20Phone%20To%20Default%20Settings%3B%20Performing%20A%20Hard%20Restore%20-%20AudioCodes%20C450HD%20User%20And%20Administrator%20Manual%20%5BPage%2027%5D%20%7C%20ManualsLib%3C%2FA%3E%26nbsp%3B%20page%2027%20and%2028%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3045486%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3045486%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20I%20am%20trying%20to%20register%20a%20Poly%20VVX201%20and%20I%20am%20not%20able%20to.%20I%20do%20have%20doubts%20about%20the%20network%20requirements.%20Could%20you%20please%20clarify%20what%20are%20the%20port%20requirements%20that%20need%20to%20be%20configured%20on%20the%20firewall%3F%20I%20have%20not%20clear%20if%20those%20mentioned%20ports%20are%20incoming%20or%20outgoing%20traffic.%20Someone%20asked%20this%20question%20at%20the%20beging%20of%20the%20conversation%20but%20I%20haven't%20seen%20that%20answered.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3046747%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3046747%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1258077%22%20target%3D%22_blank%22%3E%40Ahmet_61%3C%2FA%3E%26nbsp%3BCisco%203905%20is%20not%20in%20scope.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3046755%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3046755%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F9346%22%20target%3D%22_blank%22%3E%40Jordi%20Pera%3C%2FA%3E%26nbsp%3B%3CSPAN%3ESIP%20Gateway%20is%20a%20cloud%20based%20solution%2C%20so%20customers%20need%20to%20open%20their%20firewall%20to%20SIP%20Gateway%20cloud%20endpoints.%20Endpoints%20described%20in%20O365%20connectivity%20guide%20are%20not%20sufficient%20as%20SIP%20devices%20do%20not%20support%20ICE%20(which%20Teams%20Phone%20devices%20do)%2C%20so%20we%20need%20to%20open%20additional%20endpoints%20to%20support%20SIP%20devices.%3CBR%20%2F%3E%3CBR%20%2F%3EFollowing%20are%20for%20both%20inbound%20and%20outbound%20traffic%20-%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSPAN%3E%3CSTRONG%3EOpen%20the%20UDP%20ports.%3C%2FSTRONG%3E%26nbsp%3BOpen%20UDP%20ports%20in%20the%20range%2049152%20to%2053247.%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CPRE%3E%3CSPAN%3ENote%2C%20SIP%20devices%20can%E2%80%99t%20leverage%20Teams%20media%20relay%20infrastructure%2C%20based%20on%20IETF%20ICE%20RFC%2C%20%26nbsp%3B(i.e.%20route%20media%20through%20ports%203478-3481).%3C%2FSPAN%3E%3C%2FPRE%3E%0A%3CUL%3E%0A%3CLI%3E%3CSPAN%3E%3CSTRONG%3EOpen%20the%20TCP%20port.%3C%2FSTRONG%3E%26nbsp%3BOpen%20TCP%20port%205061%20for%20IP%20ranges%2052.112.0.0%2F14%20to%2052.120.0.0%2F14.%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%3ENote%2C%20SIP%20devices%20can%E2%80%99t%20fallback%20to%20HTTPS%20(port%20443)%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSTRONG%3E%3CSPAN%3EOpen%20the%20following%20https%20endpoints%20(IP%20addresses%20and%20URLs)%3A%3C%2FSPAN%3E%3C%2FSTRONG%3E%3CUL%3E%0A%3CLI%3E%3CSPAN%3E13.75.175.145%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E52.189.219.201%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E51.124.34.164%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E13.74.250.91%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E13.83.55.36%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E23.96.103.40%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%3CA%20tabindex%3D%22-1%22%20title%3D%22https%3A%2F%2Fblobsdgapac.blob.core.windows.net%2F%22%20href%3D%22https%3A%2F%2Fblobsdgapac.blob.core.windows.net%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20nofollow%22%20aria-label%3D%22Link%20https%3A%2F%2Fblobsdgapac.blob.core.windows.net%22%3Ehttps%3A%2F%2Fblobsdgapac.blob.core.windows.net%3C%2FA%3E%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%3CA%20tabindex%3D%22-1%22%20title%3D%22https%3A%2F%2Fblobsdgemea.blob.core.windows.net%2F%22%20href%3D%22https%3A%2F%2Fblobsdgemea.blob.core.windows.net%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20nofollow%22%20aria-label%3D%22Link%20https%3A%2F%2Fblobsdgemea.blob.core.windows.net%22%3Ehttps%3A%2F%2Fblobsdgemea.blob.core.windows.net%3C%2FA%3E%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%3CA%20tabindex%3D%22-1%22%20title%3D%22https%3A%2F%2Fblobsdgnoam.blob.core.windows.net%2F%22%20href%3D%22https%3A%2F%2Fblobsdgnoam.blob.core.windows.net%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20nofollow%22%20aria-label%3D%22Link%20https%3A%2F%2Fblobsdgnoam.blob.core.windows.net%22%3Ehttps%3A%2F%2Fblobsdgnoam.blob.core.windows.net%3C%2FA%3E%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%3CA%20tabindex%3D%22-1%22%20title%3D%22https%3A%2F%2Fhttpblobsdgapac.blob.core.windows.net%2F%22%20href%3D%22https%3A%2F%2Fhttpblobsdgapac.blob.core.windows.net%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20nofollow%22%20aria-label%3D%22Link%20https%3A%2F%2Fhttpblobsdgapac.blob.core.windows.net%22%3Ehttps%3A%2F%2Fhttpblobsdgapac.blob.core.windows.net%3C%2FA%3E%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%3CA%20tabindex%3D%22-1%22%20title%3D%22https%3A%2F%2Fhttpblobsdgemea.blob.core.windows.net%2F%22%20href%3D%22https%3A%2F%2Fhttpblobsdgemea.blob.core.windows.net%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20nofollow%22%20aria-label%3D%22Link%20https%3A%2F%2Fhttpblobsdgemea.blob.core.windows.net%22%3Ehttps%3A%2F%2Fhttpblobsdgemea.blob.core.windows.net%3C%2FA%3E%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%3CA%20tabindex%3D%22-1%22%20title%3D%22https%3A%2F%2Fhttpblobsdgnoam.blob.core.windows.net%2F%22%20href%3D%22https%3A%2F%2Fhttpblobsdgnoam.blob.core.windows.net%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20nofollow%22%20aria-label%3D%22Link%20https%3A%2F%2Fhttpblobsdgnoam.blob.core.windows.net%22%3Ehttps%3A%2F%2Fhttpblobsdgnoam.blob.core.windows.net%3C%2FA%3E%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3047183%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3047183%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1245213%22%20target%3D%22_blank%22%3E%40Chandranshu%3C%2FA%3E%26nbsp%3B-%20In%20testing%20with%20a%20Poly%20VVX%20500%2C%20here%20are%20the%20steps%20I've%20followed%2C%20and%20the%20results.%26nbsp%3B%3C%2FP%3E%3CP%3E1)%20Factory%20Reset%20the%20device%3C%2FP%3E%3CP%3E2)%20Installed%20the%20supported%20firmware%20version%205.9.6.2327%3C%2FP%3E%3CP%3E3)%20Enabled%20Web%20Interface%3C%2FP%3E%3CP%3E4)%20Set%20the%20provisioning%20server%20%22%3CSPAN%3E%3CA%20href%3D%22http%3A%2F%2Fnoam.ipp.sdg.teams.microsoft.com%26quot%3B%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Fnoam.ipp.sdg.teams.microsoft.com%22%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E5)%20Device%20auto%20restarts%2C%20boots%2C%20and%20st%3C%2FSPAN%3E%3CSPAN%3Eates%20%22Contacting%20Provisioning%20Server%22%20%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E6)%20Then%20%22Provisioning%20Successful%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E7)%20Device%20shows%20the%20Teams%20Logo%20and%20%22Sign%20In%20to%20make%20an%20emergency%20call%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E8)%3C%2Fimg%3E%20Then%20displays%20%22Line%20Unregistered%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3ELine1%3A.%5BSIP%5D%20(Not%20Registered)%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E*SIP%3AServer-1%3Aobsbc-usea.sdg.teams.microsoft.com%20(Not%20Registered%200)%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E9)%20Selecting%20%22Sign%20In%22%20displays%20%22An%20error%20occurred.%20Please%20try%20again%20later%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CDIV%3EWhat%20I%E2%80%99ve%20found%2C%20is%20if%20I%20leave%20the%20device%20powered%20on%20and%20in%20this%20%22Unregistered%22%20state%20%2C%20it%20will%20eventually%20register%20successfully%2C%20but%20typically%20takes%208-10%20hours%20to%20do%20so.%26nbsp%3B%20A%20subsequent%20reboot%20produces%20the%20same%20results.%26nbsp%3B%20Successful%20Provisioning%2C%20but%20failed%20Registration.%26nbsp%3B%20Let%20the%20device%20sit%20for%2010%20hours%2C%20it%20eventually%20registers%20successfully.%26nbsp%3B%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E10)%20After%20this%20waiting%20game%2C%20selecting%20Sign%20In%20will%20display%20the%20Sign%20in%20URL%20and%20Pair%20Code.%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3EI've%20verified%20there%20are%20no%20firewalls%20blocking%20the%20required%20sites%2C%20protocols%2C%20or%20ports%2C%20or%20proxies%20in%20the%20middle.%26nbsp%3B%20I'm%20not%20ruling%20out%20the%20network%20yet%20though.%26nbsp%3B%20I%20will%20try%20on%20another%20network%20after%20the%20holiday%20break%20and%20see%20if%20there%20are%20any%20different%20results.%20I'm%20also%20still%20working%20with%20Premier%20support...%3C%2FDIV%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3047504%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3047504%22%20slang%3D%22en-US%22%3E%3CP%3EAre%20tenant%20dial%20plans%20supported%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3047722%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3047722%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F64047%22%20target%3D%22_blank%22%3E%40Jeremy%3C%2FA%3E%26nbsp%3BDoesn't%20look%20like%20an%20issue%20on%20our%20side%2C%20we'll%20keep%20an%20eye%20out%20just%20in%20case.%20Since%20you%20already%20have%20a%20support%20case%20open%2C%20we%20will%20look%20at%20it%20once%20it%20comes%20to%20us.%20Please%20do%20share%20device%20logs%20etc.%20to%20help%20us%20resolve%20it%20faster.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3047733%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20core%20Microsoft%20Teams%20calling%20functionality%20on%20compatible%20legacy%20SIP%20phones%20with%20SIP%20Gatew%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3047733%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1261065%22%20target%3D%22_blank%22%3E%40Corni365%3C%2FA%3E%26nbsp%3BYes.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Version history
Last update:
‎Dec 07 2021 10:28 AM
Updated by:
We support Ukraine and condemn war. Push Russian government to act against war. Be brave, vocal and show your support to Ukraine. Follow the latest news HERE