From VoIP.ms Wiki

Contents 1 What is VoIP.ms Teams Connector? 2 Step-by-step Configuration 2.1 1. Prepare the VoIP.ms environment 2.2 2. Assign Microsoft licenses to each user 2.3 3. Get your unique activation link from VoIP.ms 2.4 4. Grant permissions 2.5 5. Configure Direct Routing 2.6 6. Configure PBX settings 2.7 7. Add Users 2.8 8. Build and deploy the custom Teams Application. 3 SMS Connector To be released by Q2 2024 4 Related Articles 5 Useful Resources

What is VoIP.ms Teams Connector?

The VoIP.ms Teams connector lets you link your VoIP.ms account to Microsoft Teams, so you can make and receive calls via your Microsoft Teams application, whether it’s on mobile, tablet or desktop, while still taking advantage of VoIP.ms hosted features. This connector is powered by TeamMate Technology, a third-party solution enabling seamless integration with Teams. Practically speaking, your Microsoft Teams becomes your softphone, giving you the option of using the built-in dial pad to make or receive calls. You may also link your VoIP.ms account to Microsoft Teams to send and receive text messages directly from Teams - see more. Please note that you will need a Microsoft E1 license at the very minimum to be able to leverage this connector. For more information on Microsoft licenses, please check here.

Step-by-step Configuration

Please follow the instructions below to get started. Note that this process requires the involvement of the Microsoft Global Administrator. Some tasks can be delegated from the global admin to the Microsoft Teams Service Admin or Skype Admin, but due to Microsoft's security policies there is no way to complete setup without the Global Administrator initial involvement.

1. Prepare the VoIP.ms environment

1.1 Create sub accounts for each user that will use the Teams integration by heading over to Sub Accounts and then Create Sub Account.

1.2 Once done, change the Dialing Mode to E.164 by heading to Main Menu, Account Settings, General tab and set the option ‘’’Dialing Mode’’’ to E164, and then apply the change.

2. Assign Microsoft licenses to each user

Assign the proper Microsoft licenses to the users that will be using this integration. Please note that sometimes due to high traffic Microsoft can take up to 24 hours to activate licenses after they have been assigned, so doing this ahead of time will make the rest of the process much smoother.

2.1 Once at your [| Microsoft Admin Center], select Microsoft Teams Phone Standard.

2.2 Then press on the button Assign Licenses which will prompt with a new side window to find the user(s) you wish to add. You can search the users with their name or email address. Once you have selected the users to have the license, proceed on assigning the licenses by pressing Assign.

3. Get your unique activation link from VoIP.ms

To get your unique activation link, simply send us an email to [email protected] and provide our team with the following information:

• The number of licenses/seats you will need (users), and
• The e-mail address of the user who has the "Microsoft Global Administrator" role.

4. Grant permissions

4.1 Once our team processed your request, the global administrator will receive an email and will need to click the “Complete” button at the bottom of the e-mail.

4.2 You will then need to log into the Enterprise portal with your Global Administrator credentials, and authorize the requested permissions.

4.3 There will be two permission screens that are mandatory and will need to be granted before the enterprise can log into the connector.

1) 2) 3) 4) 5)

4.4 Once logged in, there will be prompts to sync a group of users and then on the dashboard to grant optional additional permissions that enhances call troubleshooting and presence syncing.

1) 2)

4.5 You must click on the "Grant consent" button of each setting.

4.6 You will then be prompted to go over Microsoft's "Permissions requested" pop-up window for all the settings.

5. Configure Direct Routing

5.1 Upon logging in as the Global Administrator into the Enterprise portal, use the sidebar menu to navigate to Direct Routing.

5.2 Confirm there is at least one available Microsoft license free to be assigned.

5.3 Once confirmed, select the desired Gateway then Click “Complete Direct Routing”.

5.4 Ensure the verification process succeeds, and then click "Complete".

5.5 Wait until the notification on the dashboard lets you know that the setup is complete and the administrator receives a confirmation email.

1) 2)

Note: If the process takes longer than an hour open a ticket with ConnecttoTeams so we can unfreeze the process, as this indicates Microsoft's servers were under heavy traffic and timed out. The global administrator will receive an email when it is complete.

5.6 Note that when everything looks completed, there may still be a slight delay. It is possible to click "FINISH"

5.7 If you mouseover Details, it will provide you the current status.

5.8. We strongly recommend enabling REFER. This will allow you to transfer calls and use VoIP.ms call park feature.

6. Configure PBX settings

6.1 Still in the Enterprise portal, navigate to the “PBX" section and add a new PBX connection with the "Add PBX" button.

6.2 Input the VoIP.ms parameters required for the PBX connector. Note that this task can be delegated to someone other than the Microsoft Global Administrator.

The necessary PBX parameters includes:

• PBX SIP Domain: VoIP.ms POP Server Hostname - See full list of servers
• PBX SIP Domain Proxy: VoIP.ms POP Server Hostname - See full list of servers
• Voicemail Feature Code: *97
• PBX SIP Domain Proxy Port: 5060
• Codecs: G722 Only (Be sure the sub-account is set with this codec)
• Reg Expires: 600
• Caller ID on Forwarding: User's CallerID Number
• Caller Name Policy: Other
• Custom Caller Name: CallerID Name. Please note that CallerID Name must be in CAPITAL LETTERS, and cannot exceed 15 characters including spaces.

7. Add Users

This can be done individually or in bulk. You will need the information about each user's PBX/SIP profile available for configuration.

Note: This task takes some time to process, please wait for a confirmation email telling you it is completed.

Note2: This task can be delegated to someone other than the Microsoft Global Administrator, but the Global Admin will have to log in to sync the users once they are uploaded.

Necessary PBX SIP user credentials include:

• SIP User: The sub-account username.
• SIP Authentication ID: The sub-account username.
• SIP Password: The sub-account username.
• Phone Number or Extension Number: If using PBX, the user could enter the internal extension number. Or, the Phone number if they have dedicated phone number per user.

8. Build and deploy the custom Teams Application.

This will enable advanced PBX features such as SIP softkeys, notifications, presence syncing, and portals within Teams.

• Ensure you have custom apps enabled for Teams
• If you want to use presence syncing ensure you have granted that permission before building the app
• Delete an existing app from Teams

SMS Connector To be released by Q2 2024

The proper instructions will be available when this feature becomes available.

Related Articles

• License requirement to use VoIP.ms Teams Connector
• Call Valet with VoIP.ms Teams Connector

Useful Resources

• TeamMate FAQ
• Youtube - TeamMate PBX Connector - How it Works
• Connect to Teams knowledge base