VoIP.ms Teams Connector
From VoIP.ms Wiki
| Article en Français | Artículo en Español |
|---|---|
| Français | Español |
YouTube Video
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 within Teams. 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.
Types of Connectors
We currently offer three different types of connectors, each designed for a specific purpose. Two of them provide voice integration with Microsoft Teams, while the third one enables SMS messaging directly within Teams.
Make sure to review the details of each connector below to determine which option best fits your needs.
PBX Connector
The PBX Connector links Microsoft Teams users to VoIP.ms sub-accounts, effectively allowing Teams to operate as an extension of your VoIP.ms environment. Each Teams user is registered on a VoIP.ms server using their sub-account credentials. Calls can then be placed and received through Microsoft Teams while still taking advantage of all cloud PBX features available in the VoIP.ms portal, such as voicemail, ring groups, IVRs, and call routing.
For example, you can configure an IVR in VoIP.ms that directs callers to specific Teams users. This connector provides the most flexibility but requires a broader set of Microsoft permissions to complete the setup.
See PBX Connector Configuration for the full setup instructions.
Operator Connect
The Operator Connect integrates Microsoft Teams with VoIP.ms in a SIP trunking model. Instead of registering individual sub-accounts, a single trunk profile handles the call routing between Teams and VoIP.ms. Once the DIDs are uploaded into the connector, they will appear in the Teams Admin Center and can be assigned directly to users.
The main advantage of this approach is its simplicity: it does not require Microsoft permissions or Direct Routing, making it ideal for customers concerned with security or privacy. However, with this approach calls will be fully managed by Microsoft Teams once they reach the trunk, meaning PBX features (voicemail, IVRs, ring groups, etc.) will not depend on the VoIP.ms side but on MS Teams.
See Operator Connect Configuration for the full setup instructions.
SMS Connector
The SMS Connector enables two-way text messaging directly inside Microsoft Teams through a dedicated add-on. Once deployed, Teams users can send and receive SMS messages linked to their VoIP.ms phone numbers. This connector simply requires API access to the VoIP.ms account that manages the numbers.
See SMS Connector Configuration for the full setup instructions.
PBX Connector 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 Once in VoIP.ms Portal, create sub accounts for each user that will use the Teams integration by heading over to Sub Accounts and then Create Sub Account.
-
2. Assign Microsoft licenses to each user
- You will need to 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 in 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.
🚨 Teams Trial License
- If there is a canceled/suspended trial license and a valid license is then added with the same name - please make sure that the trial license is first removed from the license listing.
3. Get your unique activation link from VoIP.ms
- To get your unique activation link, simply send an email to [email protected] and provide our team with the following information:
- The number of licenses you will need (ie. how many users), and
- The e-mail address of the user who has the "Microsoft Global Administrator" role.
- To get your unique activation link, simply send an email to [email protected] and provide our team with the following information:
-
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 ConnectToTeams 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.
- 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.
- 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
🚨 Requirements for the Direct Routing
- To be able to complete the Direct Routing you must have at least 1 available AND unassigned User license with the Phone System or comparable add-on.
- This User license can be recoup after the Direct Routing is fully completed. Just make sure not to delete the Direct Routing user that will be created.
- If you don't have one available and unassigned User license with the Phone System or comparable add-on, you can temporarily unassign one to complete the Direct Routing and recoup this after the Direct Routing process is fully completed.
- For more information please visit:
- 5.1 Still in the ConnectToTeams Portal, and still logged in as the Global Administrator, 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 and then click Complete Direct Routing.
- 5.4 Wait until the verification process succeeds, and then click Complete Direct Routing.
- 5.5 You will then be greeted with the following page where the Direct Routing will be processing. Even if the button FINISH appears, Do not press it yet. Make sure that you mouseover Details under Status to see the exact progress. When it confirms it's been complete, click on Finish.
- 5.6 Once you've clicked Finish, there will be a green notification label that will appear confirming you that the setup is complete. Additionally, the administrator will also receive an email confirming that the setup was complete.
🚨 Stuck on process?
- If the process takes longer than an hour, open a ticket with our technical support by emailing [email protected] requesting to unfreeze the process, as this indicates Microsoft's servers were under heavy traffic and timed out.
-
6. Configure your PBX Settings
- 6.1 Still in the ConnectToTeams Portal, navigate to the PBX section on the left menu and add a new PBX connection with the "Add PBX" button.
- 6.2 Input the VoIP.ms parameters required for the PBX connector.
- 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 or G711u (Be sure the sub-account is set with the same codec)
- Reg Expires: 600
- Caller ID on Forwarding: User's CallerID Number
- Caller Name Policy: Other
- Custom Caller Name: CallerID Name. It cannot exceed 15 characters, including spaces.
🚨 Important
- The PBX SIP Domain and PBX SIP Domain Proxy must be the same server as the one used for your DID number(s).
-
7. Add Users to your VoIP.ms Teams Connector Account
- For this process, you will need the information about each user's sub account username and password before proceeding. This process can also take some time to complete. You will receive a confirmation email once the user has been fully configured.
- 7.1 On Your Teams Connector admin page, go to Users on the left menu.
- 7.2 Click on Add User on the top right of the page.
- 7.3 Fill in all the following information for creating your user:
🚨 Important
- The Phone number of the user does not have any impact on the Caller ID number used for outgoing calls or on the DID used for incoming calls, so you can use any number or extension number as long as it starts with prefix +1 (E.g. +12052550000 or +1101).
- The Caller ID number is defined from the Sub Account settings on the VoIP.ms Customer Portal.
- Incoming calls are controlled by the Routing of your DID number on the VoIP.ms Customer Portal.
- User Tag: Used to find your user easily. Put the name you wish for reference purpose.
- SIP User: Your sub account userID. E.g: 111111_subaccount.
- Phone Number: Any phone number starting with prefix +1. This can be a Phone number in your VoIP.ms account or an extension number (E.g. +12052550000 or +1101).
- Disable Voicemail in Teams: If you want to use Teams voicemail, keep it unchecked. If you want to use your VoIP.ms voicemail, checkbox it.
- Custom Caller Name: Only for Canada. Pass the callerID Name you wish to pass. For United States, refer to [this article].
- SIP Authentication ID: Your sub account userID. E.g: 111111_subaccount.
- SIP Password: Your sub account password you entered while creating the sub account.
- Confirm SIP Password: Confirm your sub account password.
- 7.4 Once you have filed all the information, press Save User. Repeat the process for all of your users and you are done with the integration! Make sure to ask your users to fully close Microsoft Teams and re-open it.
Operator Connect Configuration
- Please follow the instructions below to get started.
- Although this process does not require granting Microsoft permissions to the connector, it does require actions from a Microsoft administrator. Specifically, only a Global Administrator or a Teams Administrator can assign phone numbers to users in the Teams Admin Center. Without one of these roles, you won’t be able to complete the setup.
-
1. Prepare the VoIP.ms environment
- 1.1 Log into your VoIP.ms Portal and create a Sub Account for the trunk that is going to be configured in the Teams Connector Dashboard.
- 1.2 Make sure to use this configuration for the Sub Account:
-
-
- Authentication type: User/Password Authentication
-
- Device type: Asterisk, IP PBX, Gateway or VoIP Switch
-
- Dialing mode: American Numbering Plan Administration (NANPA)
-
- CallerID Number: I use a system capable of passing its own CallerID
-
- 1.3 Go to DID Numbers >> Manage DIDs and edit the DID numbers you'll use with the connector as follows:
-
-
- Main Routing: SIP/IAX - Sub Account created on Step 1.2
-
- DID Point of Presence: Any VoIP.ms server of your preference
-
- Dialing Mode for Inbound Calls: E164
-
- 1.3 Go to DID Numbers >> Manage DIDs and edit the DID numbers you'll use with the connector as follows:
-
2. Configure the Trunk on the Teams Connector Dashboard
- 2.1 Log into your Teams Connector Dashboard and go to Trunks >> Profiles.
- 2.2 Click on Add Provider Trunk.
- 2.3 Use this configuration for the trunk:
-
-
- Trunk type: SIP Registration
-
- Description: Any description of your choice
-
- Outbound Proxy and Port: [SERVER NAME]@voip.ms:5060. Must be the same POP Server of the DIDs
-
- Codecs: G711 U-law (Used by default) or G722. Must be the same codec enabled for the Sub Account
-
- Auth User: The Sub Account username (E.g. 100000_SubAccount)
-
- Auth Password: The password of the Sub Account.
-
- Domain: [SERVER NAME]@voip.ms:5060. Must be the same POP Server of the DIDs
-
- SIP User ID: The Sub Account username (E.g. 100000_SubAccount)
-
- Keep all other options with the default settings.
-
- 2.4 Click on Add Provider Trunk when done.
🚨 Important
- Currently, Operator Connect will not allow using a server that is already being used by another trunk. If you get an error saying the server entered is already in use just try using a different one and then set the same as the POP server of your DID numbers in the VoIP.ms Customer Portal.
-
3. Upload the DID numbers to your Teams Connector Dashboard
- 3.1 Now, on the Teams Connector Dashboard go to Phone Numbers and click on Upload Phone Numbers.
- 3.2 Download and fill out the Sample File Format with the DID numbers you'll add as shown in the image.
- 3.3 Once the file is ready, back on the Teams Connector Dashboard upload the Phone Numbers using the form. Select these values:
-
-
- Voice Carrier Name: TeamMate
-
- Device type: Asterisk, IP PBX, Gateway or VoIP Switch
-
- SMS Carrier Profile: Assign SMS Carrier Later
-
- Upload Phone Numbers: Attact the Sample File Format with your DID numbers
-
- 3.3 Click on Upload when done.
🚨 Important
- Make sure to have an Emergency Address configured on your Teams Admin Center as it is required for the next step.
-
4. Configure Operator Connect for the DID Numbers
- 4.1 Once all the numbers are uploaded you'll see them listed on Teams Connector Dashboard. To set them up click on Configure Number (Operator Connect).
- 4.2 Make sure the configuration is as follows:
-
-
- Phone Number: Your DID number
-
- Reseller: VoIP.ms
-
- Enterprise: Your Enterprise
-
- Provider Trunk: Select the trunk configured on Step #2
-
- Regions: Any region available
-
- Civic Address: Any Emergency Address available in your Teams Admin Center
-
- 4.3 Click on Save when done.
After the DID is configured the status will be displayed as "in progress" - a process that can take several minutes to complete. To update the status, reload the Phone Numbers page.
-
5. Manage the DIDs in the Teams Admin Center
- 5.1 After DID activation is complete, the DIDs will be available in Teams Admin Center for further configuration. To see them, go to the Voice >> Phone Numbers menu option.
- 5.2 To assign a DID to an user, select the number and click on Edit at the top.
- 5.3 Select the user you'll assign the DID to and click on Apply.
SMS Connector Configuration
🚨 Important
- The SMS Teams Connector is an additional service and is activated separately. To request the activation of the SMS Teams Connector send us an email to [email protected]
Instructions for Resellers
- The Reseller must log on his interface to configure the API credentials for the new SMS profile, enabling the SMS service, deploying the SMS App, and enabling Phone number’ SMS Capabilities to the Enterprise.
- To do so, follow these steps:
-
1. Enabling the VoIP.ms API and creating the password
- 1.1 In your VoIP.ms customer portal head into Main Menu >> SOAP and REST/JSON API.
- 1.2 On the field API Password, set the password you will define for the API and confirm it.
- 1.3 On Enable API click on Enable/Disable API and make sure this says Enabled afterwards.
- 1.4 On Enable IP address make sure to add Teammate’s IP address 52.255.203.36 (You can use 0.0.0.0 to allow any IP).
-
2. Configure the SMS App to deploy
- 2.1 In your Teams Connector portal and go to the Enterprise tab.
- 2.2 Find the enterprise and click on it.
- 2.3 On the left menu click on App Management and go to the tab SMS App.
- a. The information there can be customized or leave as default if is the way you want.
- b. To set the template, click the blue button that says Save SMS Settings for....
🚨 Important
- Once Done, the Enterprise Global Admin must Sync the app to his tenant.
Instructions for Enterprise (Global Admin)
The Global Admin has the ability to deploy the SMS app to his own tenant, and enabling or disabling the SMS service for a specific End-User.
The Global Admin must log on his Dashboard in order to complete the Deployment of the SMS App by “Syncing the SMS App” with his Tenant, to have the End-user being all to add it to his Teams App.
-
1. Syncing the app to the Microsoft Tenant
-
2. Enabling the SMS feature and Phone number to a Teams User
-
3. Configure the Webhook URL
- 3.1 Log into your VoIP.ms Customer portal.
- 3.2 Go to DID numbers >> Manage DIDs.
- 3.3 Click on Edit (the pencil icon) for the DID you will connect to teams for SMS.
- a. Scroll down until you see the SMS configuration and check the option Message Service (SMS/MMS): Enable SMS/MMS.
- b. Check the option SMS/MMS Webhook URL (3CX) and paste this URL: https://smsbot.connecttoteams.com/inbound-message?provider=voipms
- c. Set the option Dialing Mode for SMS (API) to E164.
- d. Apply changes when done and repeat the process for any other DID number the end-user will use for SMS through MS Teams.
Instructions for End-user
The End-user must log into his teams and add the SMS app that has been deployed to the organization.
-
1. Installing the SMS App
Related Articles