TeamMate - VoIP.ms Wiki

Check out our YouTube channel to watch our simple tutorials that will help you set up most of our features.

TeamMate

From VoIP.ms Wiki

(Difference between revisions)
Jump to: navigation, search
[checked revision][checked revision]
(Phone System or comparable add-on Licenses)
(Phone System or comparable add-on Licenses)
Line 274: Line 274:
             width:750px;">
             width:750px;">
-
'''💬NOTE:'''<br/>
+
'''💬Good To Know:'''<br/>
* Alternatively, you can leverage the "Call App" in Teams for your members. All you need is the Phone System Resources for each, and this license is free.  
* Alternatively, you can leverage the "Call App" in Teams for your members. All you need is the Phone System Resources for each, and this license is free.  

Revision as of 14:44, 22 March 2024

TeamMate Logo


Contents


TeamMate-Architecture White.png

What is TeamMate?

The VoIP.ms Teams connector lets you link your VoIP.ms account (sub-account) to Microsoft Teams, so you can make and receive calls via your Microsoft Teams application.
For each Microsoft Teams member, the PBX service lets you take advantage of VoIP.ms hosted features. Or with the Trunk service it gives you the ability to use Microsoft Teams' built-in PBX functionality and call routing.
In other words, your Microsoft Teams becomes your softphone, giving you the option of using the built-in dial pad to make or receive calls, or even taking advantage of the Calls application, for those with limited licenses.

What are their different products?

PBX connector

Client is using VoIP.ms PBX to decide the call routing strategy.

Trunk connector

The customer can leverage Microsoft Teams PBX features such as auto-attendant, calling queues, call routing, etc.

Call App (Valet)

Gives the ability to make and receive calls without the needs of E5 (or Phone System License).
This only use Phone resources free license. Ideal for user that have minimal MS Licenses.
This app provides Call Management Services for the Teams User.
A complete suite of Call Control services are offered by this Service.

How to order a TeamMate 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 service you're interested in (PBX connector, SIP trunk connector, Valet App).
  • The number of licenses/seat you will need (users).
  • The e-mail address of the user who has the "Microsoft Global Administrator" role.

Pricing

PBX connector:

  • $4.50/user/month

Trunk connector:

  • $3.50/user/month

CallApp/Valet connector:

  • $6.00/user/month
 Contact us at [email protected] for bulk pricing.

Prerequisites

Consider these prerequisites before requesting your TeamMate product subscription.

Microsoft Minimal Requirements

  • Microsoft licenses:
- See the licensing section of this article.
  • 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 (See licensing section).
  • For Trunk Connector
- Proper license by User + Phone System Standard or Add-On (See licensing section).
  • CallApp / Valet
- Phone resources license for each user that will use the CallApp.

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.
  • For Trunk 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: Asterisk, IP PBX, Gateway or VoIP Switch.
Caller ID: I use a system capable of passing its own CallerID.
Codecs: G722.
  • For CallApp / Valet
- Requires PBX or Trunk Connector..
- If using the PBX Connector. The user must have one sub-account per user with the following specs. (Trunk connector will handle the user).:
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.

Licensing - MS Licensing for the PBX and SIP Trunk Connector

These are the licenses and combinations that allow the use of Microsoft Direct Routing. The Phone System add-on license is required per user to enable the native dial-pad in Teams.

💬 NOTE

Note that other licenses may work: Teammate' system will dynamically evaluate license contents when an Enterprise commences Direct Routing setup and adds suitable licenses to the lists when new Microsoft licenses are encountered.


💬 NOTE

When purchasing phone add-on licenses we recommend purchasing ones that do NOT include the Microsoft Calling Plan. ConnecttoTeams replaces the need for this additional cost. Additionally, the Calling Plan can interfere with the provisioning process and cause delays. As of June 2022 Microsoft is in the process of retiring the "Business Voice" licenses. The most appropriate replacement for this license is "Microsoft Teams Phone Standard." Microsoft's documentation is aggressively promoting the (more expensive) license with Calling Plan. Do not accept the upselling attempts.


TeamsPhoneLicense.png


💬 NOTE

Additionally, as Microsoft retires the older Business Voice and Phone System licenses existing customers will be forced to migrate to the newer ones.

After the licenses are updated this may disable calling for the user. If this occurs the solution is for the global administrator to disable and re-enable each user in the ConnecttoTeams Portal. Allow propagation time between the disable and the re-enable.


TeamMate DisableUser.png


Inclusive Licenses (User license + Phone System add-on)

Non-Inclusive Licenses (User license only.) Requires Phone System add-on.

Phone System or comparable add-on Licenses

💬Good To Know:

  • Alternatively, you can leverage the "Call App" in Teams for your members. All you need is the Phone System Resources for each, and this license is free.


TeamMate configuration

Please follow the instructions that you will find in this section to set up the TeamMate 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 TeamMate 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,
003 GlobalAdmin Email1.png.png
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) 004 GlobalAdminPermissions1.png 2) 004 GlobalAdminPermissions2.png 3) 004 GlobalAdminPermissions3.png
4) 004 GlobalAdminPermissions2.png 5) 004 GlobalAdminPermissions5.png
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) 005 GlobalAdmin SyncUser.png
2) 005 GlobalAdmin GrantConsent2.png
Must do this for each.
3) 004 GlobalAdminPermissions2.png
4) 005 GlobalAdmin GrantConsent4.png

[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) 006 GlobalAdmin DirectRouting ValidateLicensesAreGreen.png

[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) 006 GlobalAdmin DirectRouting ChooseGateway.png
2) 006 GlobalAdmin DirectRouting ChooseGateway2.png
Wait until the process is done.
3) 006 GlobalAdmin DirectRouting ChooseGateway3.png
Continue to wait until the green popup and the email confirmation.
4) 006 GlobalAdmin DirectRouting ChooseGateway4.png
[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) 006 GlobalAdmin DirectRouting ChooseGateway5.png
And an email will be received confirming the Direct Routing configuration.
6) 006 GlobalAdmin DirectRouting ChooseGateway6.png
Note that when everything looks completed, it may still have a delay. It is possible to click "FINISH"
006 GlobalAdmin DirectRouting InProgress1.png
006 GlobalAdmin DirectRouting InProgress2.png
[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.
350px
If desired it is possible to configure additional Direct Routes. Decide if the enterprise wants to opt into Microsoft's secondary routes for redundancy.

[5] Configure PBX settings

[1] Navigate to the “PBX Settings” tab.
[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
  • PBX SIP Domain Proxy: VoIP.ms POP Server Hostname
  • 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
  • Caller Name Policy: Other
  • Custom Caller Name: See the requirements below.

IMPORTANT - Custom Caller Name

  • Entering outbound Caller ID Name, it must be in CAPITAL LETTERS. This will appear more clearly/visible on some devices.
  • You must NOT use any special characters. They will not be displayed and it prevents potential outbound call issues.
  • Do NOT exceed 15 characters. Traditional Canadian providers will not show more than 15 characters. We suggest shrinking or adapting the name.
  • Spaces are allowed in a caller ID name but count as characters. (do not exceed 15 chars. in total).


006 PBX Settings.png

[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


SIP Trunk Configuration

This article is a step-by-step guide to the initial provisioning of the ConnecttoTeams SIP Trunk. Start here, and follow links as needed for additional details and troubleshooting.

[1]: Assign Microsoft licenses to each planned user of ConnecttoTeams. Before beginning with ConnecttoTeams.

Each planned Microsoft 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 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 their 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 TeamMate subscription is active, you will receive an email to start the configuration process.
The global administrator must click the link provided in the email that will receive, log into the Enterprise portal with their 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. Once logged in there are prompts on the dashboard to grant optional additional permissions that enhance ConnecttoTeams' call troubleshooting and presence syncing.

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

Click the “Direct Routing” tab. Select the desired Gateway then click “Complete Direct Routing,” ensure the verification process succeeds, and click "Complete.". Wait for the notification on the dashboard that lets you know 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.
Decide if allowing SIP REFER or Media Encryption is desired for the Direct Route. If desired it is possible to configure additional Direct Routes. Decide if the enterprise wants to opt into Microsoft's secondary routes for redundancy.

[5]: Add Trunk Profile.

After the enterprise has configured Direct Routing, responsibility switches back to the reseller. They will need to set up the trunk profile with information from the customer's telecom account.

[6]: Manage Trunk.

Once the trunk is created you will need to add DIDs and choose a default. Note: The Trunk DID page has been retired and replaced by the Phone Numbers page.
Please see the Upload and Assign Phone Number section in this KB for reference - https://docs.connecttoteams.com/en/articles/200-centralized-did-management

[7]: Configure Trunk Settings For Users.

(Individual or in Bulk). Enable trunk(s) for each user, choose a default trunk, and assign DIDs.


Other Useful Articles


Personal tools
Namespaces
Variants
Actions
VoIP.ms Wiki
Guides 🇨🇦
Guías 🇲🇽