From VoIP.ms Wiki

Contents 1 Related Articles 2 What is VoIP.ms Teams Connector? 3 How to order a subscription through VoIP.ms 4 General Inquiries, Questions and Pricing 5 Prerequisites 5.1 Microsoft Minimal Requirements 5.2 VoIP.ms Technical Requirements 6 VoIP.ms Team Connector configuration 6.1 PBX Connector Installation 6.1.1 [1] Assign MS licenses to each planned user of ConnecttoTeams. 6.1.2 [2] Grant permissions. 6.1.3 [3] Confirm Microsoft licensing. 6.1.4 [4] Configure Direct Routing. 6.1.5 [5] Configure PBX settings 6.1.6 [6] Add Users 6.1.7 [7] Build and deploy the custom Teams Application. 6.2 SMS Connector 6.2.1 To be released. Expected by Q2 2024. 7 Useful Resources

Related Articles

[Licenses available to use VoIP.ms with Microsoft Teams]

[How to connect VoIP.ms with Microsoft Teams Call Valet]

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

How to order a subscription through VoIP.ms

Since we partnered with TeamMate you can get your connector subscription from us!

If you're interested in using VoIP.ms through MS Teams, simply send us an email to [email protected] mentioning you want to get this service and provide 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.

General Inquiries, Questions and Pricing

Contact us at [email protected].

Prerequisites

Consider these prerequisites before requesting your product subscription.

Microsoft Minimal Requirements

• Microsoft licenses: here for more information
• Number of users to set up.

• Microsoft Global Administrator

- The initial sign-in and activation must be done by clicking on the button in the email that will be sent to the Microsoft Global Admin for the Enterprise you will connect.

- The Microsoft Global Administrator must be the one to register the enterprise, grant permissions, and finalize changes for the end users.

• For PBX Connector

- Proper license by User + Phone System Standard or Add-On.

• CallApp / Valet

- Phone resources license for each user that will use the CallApp. For more information on this product, click here.

VoIP.ms Technical Requirements

• For PBX Connector

- Dialing mode of the VoIP.ms account must be set to E.164.

- One sub-account per user with the following specs:

Authentication: Username/Password.

Device type: ATA device IP Phone or Softphone.

Caller ID: A DID as the caller ID or a verified Caller ID.

Codecs: G722.

VoIP.ms Team Connector configuration

Please follow the instructions that you will find in this section to set up the product you subscribed for.

Please note this process requires the complete 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.

PBX Connector Installation

[1] Assign MS licenses to each planned user of ConnecttoTeams.

Before beginning with ConnecttoTeams, each planned MS Teams User must have the correct licenses assigned to them.

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.

Also, ensure there is one additional set of licenses available and unassigned.

Don’t worry, you can recover these extra licenses once the setup is done.

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

[2] Grant permissions.

Once your subscription is active, you will receive an email to start the configuration process.

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

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

Then log into the Enterprise portal with your Global Administrator credentials, and authorize the requested permissions.

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)

Once logged in there are prompts to sync a group of users then on the dashboard to grant optional additional permissions that enhance ConnecttoTeams call troubleshooting and presence syncing.

1)

2)

You must click on the "Grant consent" button of each setting and you'll be prompted to go over Microsoft's "Permissions requested" pop-up window for all the settings.

3)

4)

[3] Confirm Microsoft licensing.

Upon logging in as the Global Administrator, use the sidebar menu to navigate to Direct Routing Management >> Direct Routing.

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

1)

• What if the portal says there are negative licenses available?
• What if the portal says I don’t have any available licenses when I know that I do?

[4] Configure Direct Routing.

[1] Click on the “Direct Routing” tab.

[2] Select the desired Gateway then Click “Complete Direct Routing,” ensure the verification process succeeds, and then click "Complete."

1)

2)

Wait until the process is done.

3)

Continue to wait until the green popup and the email confirmation.

4)

[3] Wait for the notification on the dashboard that lets you know the set-up is complete.

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.

Once completed, the green popup will appear in the corner.

5)

And an email will be received confirming the Direct Routing configuration.

6)

Note that when everything looks completed, it may still have a delay. It is possible to click "FINISH"

[4] Decide if allowing SIP REFER or Media Encryption is desired for the Direct Route.

Benefits of enabling REFER:

- Call park and Transferring will work as is typical.

If desired it is possible to configure additional Direct Routes. Decide if the enterprise wants to opt into Microsoft's secondary routes for redundancy.

• What if I have already set up Direct Routing in Teams before and it is blocking the new configuration process?
• What if I previously used the Microsoft Calling Plan and it is blocking the new configuration?
• What if the Direct Routing user is created but the Direct Routing fails to be established?
• Why is the domain I chose not working?

[5] 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.

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.

:::   

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

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

NOTE: 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.

• If you are a reseller, you can add users for your enterprise customers, but we will need to finalize the process for you to perform a sync to complete Teams registration and calling.

• What does disabling voicemail for a user do?

• What if the user does not have a direct phone number, but only has an extension?.

• What if the dialpad doesn’t appear?

• Confirm the user has been properly assigned to the voice routing policy.

[7] 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. Expected by Q2 2024.

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

Useful Resources

• TeamMate FAQ

• Youtube - TeamMate PBX Connector - How it Works

• Connect to Teams knowledge base