VoIP.ms Teams Connector
From VoIP.ms Wiki
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” & “Skype Admin”, but due to Microsoft's security policies there is no way to complete setup without the Global Administrator initial involvement.
-
1. Create the respective users in the VoIP.ms portal
- 1.1 Create VoIP.ms sub accounts for each user that will use the Teams integration.
- 1.2 Once you are done, head to Main Menu, Account Settings, General tab and set the option ‘’’Dialing Mode’’’ to E164, and then apply the change.
-
2 - Assign adequate Microsoft licenses to each user.
- Before beginning with ConnecttoTeams, each planned Teams User must have the correct licenses assigned to them.
- Note: 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 more streamlined.
- If there is a canceled/suspended trial license and a valid license is added with the same name - you should make sure that the canceled trial subscription is removed from the license listing. If not, Microsoft only returns the canceled/suspended SKU and the software will erroneously claim that the proper licenses are not available.
3 - Get your unique link from VoIP.ms Microsoft Teams onboarding team
- To get started, simply send us an activation email to [email protected] and provide our team with the following information:
- The number of licenses/seat you will need (users).
- The e-mail address of the user who has the "Microsoft Global Administrator" role.
- To get started, simply send us an activation email to [email protected] and provide our team with the following information:
-
4 - Grant permissions.
- 1. Once our team processed your request, the global administrator will receive an email and will need click the “Complete” button at the bottom of the e-mail.
- 2. You will then need to log into the Enterprise portal with your Global Administrator credentials, and authorize the requested permissions.
- 3. There are 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. Once logged in, there are prompts to sync a group of users and then on the dashboard to grant optional additional permissions that enhance ConnecttoTeams call troubleshooting and presence syncing.
- 1)
2) 
- 1)
- 5. You must click on the "Grant consent" button of each setting.
- 5.1 You will be prompted to go over Microsoft's "Permissions requested" pop-up window for all the settings.
-
5 - Confirm Microsoft licensing.
- 1. Upon logging in as the Global Administrator, use the sidebar menu to navigate to Direct Routing Management >> Direct Routing.
- 2. Confirm there is one available Microsoft license free to be assigned.
-
6 - Configure Direct Routing.
- 1. Click on the “Direct Routing” tab.
- 2. Select the desired Gateway then Click “Complete Direct Routing”.
- 3. ensure the verification process succeeds, and then click "Complete."
- 4. Wait until the notification on the dasboard lets you know that the setup is complete and the administrator receives an email confirming.
- 5. The notification on the dasboard will appear as follow.
- 5.1 The administrator will also receive an email confirming the Direct Routing configuration.
- 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.2 Note that when everything looks completed, it may still have a delay. It is possible to click "FINISH"
- 5.3 If you mouseover Details, it will provide you the current status.
- 6. We strongly recommend enabling REFER. This will allow you to transfer calls and use VoIP.ms call park feature.
-
7 Configure PBX settings
- 1. Navigate to “PBX Settings” section to add a new PBX connection.
- 2. Input the VoIP.ms parameters required for the PBX connector.
- 2.1 This task can be delegated to someone other than the Microsoft Global Administrator.
- Necessary PBX information includes:
- PBX SIP Domain (required): 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 Procy Port: 5060
- Codecs: G722 Only (Be sure the sub-account is set with this codec)
- Reg Expires: 600
- Caller ID on Forwarding: User's Caller ID
- Important: The SIP Domain and Proxy must be the same server used Point of Presence for your DID number(s)
- Caller Name Policy: Other
- Custom Caller Name: See the requirements below.
- Necessary PBX information includes:
- 2.1 This task can be delegated to someone other than the Microsoft Global Administrator.
-
8 - 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.
- This can be done individually or in bulk. You will need the information about each user's PBX/SIP profile available for configuration.
-
9 - 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
- This will enable advanced PBX features such as SIP softkeys, notifications, presence syncing, and portals within Teams.
SMS Connector To be released by Q2 2024
- The proper instructions will be available when this feature becomes available.
Related Articles
