Step-by-Step Guide: Connecting Analog devices with the Microsoft Teams SIP Gateway (2024)

Step-by-Step Guide: Connecting Analog devices with the Microsoft Teams SIP Gateway (1)

  • Report this article

Daniel Richter Step-by-Step Guide: Connecting Analog devices with the Microsoft Teams SIP Gateway (2)

Daniel Richter

MCT | empowering businesses through modern communication with Microsoft Teams

Published Jan 24, 2023

+ Follow

Intro

Connecting analog devices with Microsoft Teams is nothing new, but in the past customers had to rely on using an on-Prem SBC or PBX to connect the devices with the Microsoft Teams cloud. Back at Ignite, Microsoft announced that analog devices will be supported via their SIP-Gateway component which was a welcomed announcement since many of my customers are still using analog devices such as door openers or lift phones. The SIP Gateway has come a long way. Announced in December 2021, only certain SIP phones were supported but as of early 2023, that list has grown bigger quite a bit with Microsoft recently adding support for DECT devices and now analog devices.

The full list of supported vendors and devices can be found here

Supported ATAs:

  • AudioCodes (MP-112 FXS, MP-114 FXS, MP-114 FXS_FXO, MP-118 FXS, MP-118 FXS_FXO, MP-124 FXS)
  • Cisco (ATA 191, ATA 192)
  • Poly (OBI 300, OBI 302)

Note: The support for the AudioCodes M500L will be enabled in the coming months.

For this guide, I will be using an AudioCodes MP112 with a Gigaset DA210 analog phone.

Step-by-Step Guide: Connecting Analog devices with the Microsoft Teams SIP Gateway (3)

Preparing the MS Teams SIP Gateway

  1. Verify that your environment meets the network requirements listed here.

2. Enable the support for SIP devices in your tenant.

Head over to the TAC and select your Calling Policy. You can either edit an already existing one or create a new one for accounts used with the analog devices.

Step-by-Step Guide: Connecting Analog devices with the Microsoft Teams SIP Gateway (4)

You can also use Powershell with the following command:

Set-CsTeamsCallingPolicy -Identity Global -AllowSIPDevicesCalling $true 

Please beware that changes made to this setting will take up to 24 hours to complete.

Preparing the AudioCodes MP-112

  1. Update the ATA to the latest supported firmware. Contact your vendor to receive the latest updates. Do a backup of your configuration prior to updating to newer firmware. For the MP-112, version 6.60A.367.001 and upwards is required. I updated mine to 6.60A.367.005.
  2. After the update log in to your MP and open the AdminPage which can be accessed via http://<your-MP-IP>/AdminPage.
  3. On the left select INI Parameters and enter the following parameters and values

Please note: After these parameters are set the device will restart and your configuration will be replaced by a custom Microsoft configuration.

Parameter: inifileurl

Value: Choose one URL from below

EMEA

http://emea.ipp.sdg.teams.microsoft.com/mac.ini

Americas

http://noam.ipp.sdg.teams.microsoft.com/mac.ini

APAC

http://apac.ipp.sdg.teams.microsoft.com/mac.ini

If your tenant is hosted in EMEA choose http://emea.ipp.sdg.teams.microsoft.com/mac.ini as value

Parameter: AUPDResetURLOnWebConfig

Value: 1

Parameter: setdefaultoninifileprocess

Value: 1

In the end, the config should look like this

Step-by-Step Guide: Connecting Analog devices with the Microsoft Teams SIP Gateway (5)

Your MP might restart during the application of the new values, don't worry.

You can check the value of the parameter by just entering the parameter name without the value and just hit Apply new value.

The preparations are now complete and we start the provisioning in Teams Admin Center.

If you are a tech nerd like me and wondering what settings changed and have been altered by Microsoft I compared the before and after INI files. I will post the changes in an appendix chapter.

Provisioning the MP and analog phone

  1. Head back to the TAC and select SIP devices. On the top right corner select Actions and then Provision Devices.

Step-by-Step Guide: Connecting Analog devices with the Microsoft Teams SIP Gateway (6)

2. Click Add MAC addresses manually and select ID type Hardware ID. Add the MAC address of your MP device and the port number of your FXS port in the following format: 00-xx-xx-xx-xx-xx:0xx where the last three digits represent the FXS port number. Since my phone is connected to FXS port 1 my last three digits are 001.

Step-by-Step Guide: Connecting Analog devices with the Microsoft Teams SIP Gateway (7)

After the MAC address and port number have been added you should see a new entry in the Waiting on activation list. Click Generate verification code and note that a new Verification code has been created.

Please note that this code is only valid for 24 hours, after that a new code needs to be generated.

Step-by-Step Guide: Connecting Analog devices with the Microsoft Teams SIP Gateway (8)

3. Now go to Waiting for sign in and select Sign in a user.

Step-by-Step Guide: Connecting Analog devices with the Microsoft Teams SIP Gateway (9)

Plug in your analog phone and call *55*<verification code>, in my case *55*246948. You will hear a confirmation tone. Afterward, put the phone back down and continue in your browser with the remote login.

Open https://microsoft.com/devicelogin in your browser and copy the displayed code.

Step-by-Step Guide: Connecting Analog devices with the Microsoft Teams SIP Gateway (10)

When asked by the browser enter the code and login with your shared device account. Please note that remote sign-in is only supported for shared device accounts.

After the Sign-In the following message should appear.

Step-by-Step Guide: Connecting Analog devices with the Microsoft Teams SIP Gateway (11)

Congratulations, your analog phone can now be reached from outside and do outbound calls to the PSTN.

When you make a test call you will notice that calls to the analog line will also be logged by the activity center.

Step-by-Step Guide: Connecting Analog devices with the Microsoft Teams SIP Gateway (12)

Appendix

Changes made by the custom Microsoft INI

[Voice Engine Params]RFC2833TxPayloadType = 101RFC2833RxPayloadType = 101ENABLEMEDIASECURITY = 1[SIP Params]ENABLECALLERID = 1MAXDIGITS = 18ISSPECIALDIGITS = 1REGISTRATIONTIME = 60ISREGISTERNEEDED = 1GWDEBUGLEVEL = 5ENABLEMWI = 1HOLDFORMAT = 1MEDIASECURITYBEHAVIOUR = 1ENABLE3WAYCONFERENCE = 1ENABLEGRUU = 1DNSQUERYTYPE = 1PROXYDNSQUERYTYPE = 1OOSONREGISTRATIONFAIL = 1ENABLESIPREMOTERESET = 1SetDefaultOnIniFileProcess = 03WAYCONFERENCEMODE = 2[ PREFIX ]FORMAT PREFIX_Index = PREFIX_DestinationPrefix, PREFIX_DestAddress, PREFIX_SourcePrefix, PREFIX_ProfileId, PREFIX_MeteringCode, PREFIX_DestPort, PREFIX_SrcIPGroupID, PREFIX_DestHostPrefix, PREFIX_DestIPGroupID, PREFIX_SrcHostPrefix, PREFIX_TransportType, PREFIX_SrcTrunkGroupID, PREFIX_DestSRD, PREFIX_CostGroup, PREFIX_ForkingGroup, PREFIX_CallSetupRulesSetId;PREFIX 0 = "*", "obsbc-euwe.sdg.teams.microsoft.com", "*", 0, 255, 0, -1, "", -1, "", -1, 1, -1, "", -1, -1;PREFIX 1 = "*", "obsbc-euwe.sdg.teams.microsoft.com", "*", 0, 255, 0, -1, "", -1, "", -1, 2, -1, "", -1, -1;[ \PREFIX ][ TrunkGroup ]FORMAT TrunkGroup_Index = TrunkGroup_TrunkGroupNum, TrunkGroup_FirstTrunkId, TrunkGroup_FirstBChannel, TrunkGroup_LastBChannel, TrunkGroup_FirstPhoneNumber, TrunkGroup_ProfileId, TrunkGroup_LastTrunkId, TrunkGroup_Module;TrunkGroup 0 = 1, 255, 1, 1, "removed", 0, 255, 255;TrunkGroup 1 = 2, 255, 2, 2, "removed", 0, 255, 255;[ \TrunkGroup ][ PstnPrefix ]FORMAT PstnPrefix_Index = PstnPrefix_DestPrefix, PstnPrefix_TrunkGroupId, PstnPrefix_SourcePrefix, PstnPrefix_SourceAddress, PstnPrefix_ProfileId, PstnPrefix_SrcIPGroupID, PstnPrefix_DestHostPrefix, PstnPrefix_SrcHostPrefix, PstnPrefix_SrcSRDID, PstnPrefix_TrunkId, PstnPrefix_CallSetupRulesSetId;PstnPrefix 0 = "removed", 1, "", "*", 0, -1, "", "", "", -1, -1;PstnPrefix 1 = "removed", 2, "", "*", 0, -1, "", "", "", -1, -1;[ \PstnPrefix ][ ProxyIp ]FORMAT ProxyIp_Index = ProxyIp_IpAddress, ProxyIp_TransportType, ProxyIp_ProxySetId;ProxyIp 0 = "obsbc-euwe.sdg.teams.microsoft.com", 2, 1;ProxyIp 1 = "mainsbc-euwe.sdg.teams.microsoft.com", 2, 2;[ \ProxyIp ][ TxDtmfOption ]FORMAT TxDtmfOption_Index = TxDtmfOption_Type;TxDtmfOption 0 = 4;[ \TxDtmfOption ][ TrunkGroupSettings ]FORMAT TrunkGroupSettings_Index = TrunkGroupSettings_TrunkGroupId, TrunkGroupSettings_ChannelSelectMode, TrunkGroupSettings_RegistrationMode, TrunkGroupSettings_GatewayName, TrunkGroupSettings_ContactUser, TrunkGroupSettings_ServingIPGroup, TrunkGroupSettings_DedicatedConnectionMode, TrunkGroupSettings_MWIInterrogationType, TrunkGroupSettings_TrunkGroupName;TrunkGroupSettings 0 = 1, 0, 0, "onboarding.org", "", 1, 0, 255, "";TrunkGroupSettings 1 = 2, 0, 0, "onboarding.org", "", 1, 0, 255, "";[ \TrunkGroupSettings ][ CallerDisplayInfo ]FORMAT CallerDisplayInfo_Index = CallerDisplayInfo_DisplayString, CallerDisplayInfo_IsCidRestricted, CallerDisplayInfo_Port, CallerDisplayInfo_PortType;CallerDisplayInfo 0 = "Sign In", 0, 1, "FXS";CallerDisplayInfo 1 = "Sign In", 0, 2, "FXS";[ \CallerDisplayInfo ][ Authentication ]FORMAT Authentication_Index = Authentication_UserId, Authentication_UserPassword, Authentication_Port, Authentication_PortType;Authentication 0 = "removed", "removed", 1, "FXS";Authentication 1 = "removed", "removed", 2, "FXS";[ \Authentication ][ ProxySet ]FORMAT ProxySet_Index = ProxySet_EnableProxyKeepAlive, ProxySet_ProxyKeepAliveTime, ProxySet_ProxyLoadBalancingMethod, ProxySet_IsProxyHotSwap, ProxySet_SRD, ProxySet_ClassificationInput, ProxySet_ProxyRedundancyMode, ProxySet_KeepAliveFailureResp, ProxySet_HomingSuccessDetectionRetries;ProxySet 0 = 0, 60, 0, 0, 0, 0, -1, "", 1;ProxySet 1 = 0, 60, 0, 1, 0, 0, -1, "", 1;ProxySet 2 = 0, 60, 0, 1, 0, 0, -1, "", 1;[ \ProxySet ][ IPGroup ]FORMAT IPGroup_Index = IPGroup_Type, IPGroup_Description, IPGroup_ProxySetId, IPGroup_SIPGroupName, IPGroup_ContactUser, IPGroup_EnableSurvivability, IPGroup_ServingIPGroup, IPGroup_SipReRoutingMode, IPGroup_AlwaysUseRouteTable, IPGroup_RoutingMode, IPGroup_SRD, IPGroup_MediaRealm, IPGroup_ClassifyByProxySet, IPGroup_ProfileId, IPGroup_MaxNumOfRegUsers, IPGroup_InboundManSet, IPGroup_OutboundManSet, IPGroup_RegistrationMode, IPGroup_AuthenticationMode, IPGroup_MethodList, IPGroup_EnableSBCClientForking, IPGroup_SourceUriInput, IPGroup_DestUriInput, IPGroup_ContactName;IPGroup 1 = 0, "", 1, "", "", 0, -1, -1, 0, -1, 0, "", 1, 0, -1, -1, -1, 0, 0, "", 0, -1, -1, "";IPGroup 2 = 0, "", 2, "", "", 0, -1, -1, 0, -1, 0, "", 1, 0, -1, -1, -1, 0, 0, "", 0, -1, -1, "";[ \IPGroup ][ CodersGroup0 ]FORMAT CodersGroup0_Index = CodersGroup0_Name, CodersGroup0_pTime, CodersGroup0_rate, CodersGroup0_PayloadType, CodersGroup0_Sce;CodersGroup0 0 = "g711Alaw64k", 20, 0, -1, 0;CodersGroup0 1 = "g711Ulaw64k", 20, 0, -1, 0;[ \CodersGroup0 ] 
Like
Comment

80

16 Comments

Henry Torres Rosario

Global Network Voice Manager at Leggett & Platt

1mo

  • Report this comment

I'm unable to get a confirmation tone after inputting the *55*<code> nor I can see it on the sign in page.

Like Reply

1Reaction

Steve Petroski

Platform Engineer - Meeting Experience & Telephony

5mo

  • Report this comment

Is fax supported?

Like Reply

1Reaction

Ramesh Srinivasan

Senior Consultant - M365 Workplace Products & Solutions

6mo

  • Report this comment

I added the following parameters inifileurl, AUPDResetURLOnWebConfig and setdefaultoninifileprocess with the mentioned value. However the device doesn't retart.Not sure what am I missing here. Requesting your assistance here Daniel RichterHere is the version details,Version ID:6.60A.369.002DSP Type:0DSP Software Version:66015DSP Software Name:204IM3Flash Version:199

Like Reply

1Reaction

İsmail Budak

Bircom Telekomünikasyon ve Bilişim Hizmetleri A.Ş. şirketinde Technical Services Team Lead

7mo

  • Report this comment

Hello,I am using mp112. The device gets the configuration from http://emea.ipp.sdg.teams.microsoft.com/mac.ini.But when ı start calling,Teams gives 500 error.(SIP ;cause=500 ;text="General Routing Failure")In teams, the device appears to be offline.What are your comments about this problem?note :I haveE1 and Phone System licences and I use teams direct routing on my system.Also, I can add Sip phones without any problems. (Example yealink T30)So I don't think it's a firewall or network issue..

Like Reply

1Reaction

Luke Cox

9mo

  • Report this comment

Thanks for this guide, helped me massively

Like Reply

1Reaction

See more comments

To view or add a comment, sign in

More articles by this author

No more previous content

  • How to configure Private Line in Microsoft Teams Mar 15, 2024
  • Authorize Teams Users to change Call Queue/Auto Attendant Settings Apr 7, 2023

No more next content

Sign in

Stay updated on your professional world

Sign in

By clicking Continue, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.

New to LinkedIn? Join now

Insights from the community

  • Computer Hardware What are the top Ethernet cable standards to know?
  • Telecommunications Engineering How can you design a low-latency network?
  • Unified Communications How do you optimize UC codecs and protocols for different scenarios and devices?
  • ATM Networks How do you use AAL to support multimedia and voice applications in ATM networks?
  • Telecommunications Systems How do you teach IP Suite technology to clients and staff?
  • Computer Networking How do SCTP and HTTP2 interact with other protocols and layers in the network stack?
  • IP Networking How do you train and educate your IP network team on multicast concepts and skills?
  • Signalling What are the emerging trends and standards for signalling in NGN networks?
  • Telecommunications Systems How can you upgrade and migrate IP PBX systems without disrupting service?
  • Core Network How do you implement QoS and charging policies for different types of IMS sessions and applications?

Others also viewed

  • Options Cisco Hosted Collaboration Solution (HCS) Customers Need to Consider Kevin Kieller 11mo
  • Microsoft Teams Direct Routing: Making Teams Your Phone System Ribbon Communications 1y
  • AI in Workforce Engagement Management (WEM): Five steps to success Zoom 3w
  • SharePoint Online Intranets: Azure AI or Microsoft 365 Copilot? Sousouni Bajis 1mo
  • LinkedIn becomes a goldmine of cybercrime Nethone 11mo
  • Corporate Trailblazers: In-Depth Conversations with Indrajit Ghosh (IG), CEO of ConnX Inc. Brijesh Mandan 1mo
  • 2024 Outlook: The Intersection of Multimodal AI, AGI, and Human Ingenuity Brijesh Mandan 2mo
  • Appearances Viji Iyer 1y
  • From my kitchen table to yours Viji Iyer 1y
  • Do you feel the vibe? Viji Iyer 1y

Explore topics

  • Sales
  • Marketing
  • Business Administration
  • HR Management
  • Content Management
  • Engineering
  • Soft Skills
  • See All
Step-by-Step Guide: Connecting Analog devices with the Microsoft Teams SIP Gateway (2024)
Top Articles
Latest Posts
Article information

Author: Manual Maggio

Last Updated:

Views: 6801

Rating: 4.9 / 5 (69 voted)

Reviews: 92% of readers found this page helpful

Author information

Name: Manual Maggio

Birthday: 1998-01-20

Address: 359 Kelvin Stream, Lake Eldonview, MT 33517-1242

Phone: +577037762465

Job: Product Hospitality Supervisor

Hobby: Gardening, Web surfing, Video gaming, Amateur radio, Flag Football, Reading, Table tennis

Introduction: My name is Manual Maggio, I am a thankful, tender, adventurous, delightful, fantastic, proud, graceful person who loves writing and wants to share my knowledge and understanding with you.