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.

VoIP.ms Technical Requirements

You require a PBX Connector in order to have the CallApp / Valet. For more information, visit this article to get started.

Valet (Call App) provisioning

1 - Verify licenses

1. Make sure a Phone System Resource Account license is available. Phone System Resource Account licenses are only available if you have a subscription for a Phone System license.

2. Make sure that you have an available PBX extension to assign to the Application instance.

2 - Grant permissions.

1. The global administrator must click the link provided in the email they receive.

1.1 For this, at the bottom of the email you will find a button with the text "Complete".

2. ConnecttoTeams performs certain limited tasks with the Microsoft Global Administrators' consent. It allows for automated provisioning via PowerShell of Direct Routing, User Calling activation and Teams Application setup in Microsoft.

2.1 The initial request when the Microsoft Enterprise Global Administrator is asked for permission looks like this:

3 - User Groups Sync.

1. On the initial login to the Enterprise Portal, the enterprise Global Administrator will be redirected to the User Group Sync page and must select whether Users will be synchronized by specifying one or more Groups to serve as filters.

If no Group(s) are selected, then all Users of the enterprise will be synchronized.
If any Group(s) are selected, then only Users that belong to the Group(s) will be synchronized.

Note The Portal WILL NOT synchronize or store Users that are not part of the selected Group(s).

1.1 The image below shows a case where two Microsoft Groups (Accounting and Billing) have been selected to be synchronized.

4 - Save The App Template.

1. You need to create a template for the Teams Application that will house the Valet App interface. This template will set your default settings for any applications that are deployed to your enterprises.

2. Save it first via the "App Template".

5 - Set Up Direct Routing.

1. Make sure you have at least 1 available AND unassigned User license with the Phone System, or comparable, add-on that allows you to use Direct Routing.

2. Select the desired Gateway, paste the invitation code from the email then click the Complete Direct Routing.

3. The "Verify Tenant" will pop up, this will verify the connection to the DNS Provider and will validate licenses. Click "Complete Direct Routing" as soon as it is done with the verification.

4. Direct Routing provisioning will take a few minutes, refresh the dashboard page after 2-3 minutes to check progress.

6 - 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.

Note This task can be delegated to someone other than the Microsoft Global Administrator.

2.1 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.

7 - Create/Configure Application Instance.

1. The Global Administrator commences the process by clicking the Setup button in the Enterprise Admin Action Items. This step enables the Valet Application Service and the Application Instance for Enterprise. This process automatically creates the "valetservice" user and assigns the Phone System Resource Account made available as part of the prerequisite.

2. Once complete you will see the ‘valetservice’ in the users page.

3. Still under the Enterprise Admin Action Items, configure the Valet Service Account by clicking the Configure button. This will take you to the Configure Valet Service Account page where you can select the Application Instance user. This step assigns a Phone Number to the "valetservice" user created as part of the ‘Setup’.