Legacy Teams integration on the CUCM

What it is for

This action belongs to the older way of making Teams users reachable through the CUCM. EasyUC creates a Teams device in the CUCM for a user: a CTI route point whose call forward all points to a Teams destination number, or a Remote Destination Profile. EasyUC builds the destination number from the user's number: all characters other than digits are removed, as many leading digits are cut off as specified under Strip, and the Prefix is put in front.

With Windows Connection switched on, EasyUC signs in to a Windows management host via SSH and runs PowerShell commands for Microsoft Teams there. In this way it sets the Line URI for the user and enables Enterprise Voice. On saving, EasyUC checks this sign-in.

If the function is active, the Teams options appear when creating devices and in the setup wizard, and the connection list shows the MS Teams Prefix. Setting up the integrated SBC under EasyUC Teams is independent of this.

Prerequisites

• License with provisioning (provisioning). Without it, the entry is missing from the Actions menu.
• Sign-in as an administrator. In the menu definition, the Administration menu is assigned only to the role ROLE_APP_ADMIN.
• The CUCM connection is enabled. For a disabled connection, Actions shows only Enable Connection.
• The CUCM has routing in place that takes numbers with the chosen prefix to Microsoft Teams.
• For the Windows connection: a Windows host with SSH access and Teams PowerShell, and a Teams administrator account.

Step by step

1. In the header, select the EasyUC Cisco workspace.
2. In the menu, open Administration → CUCM & Provisioning → CUCM Connections. The page is titled Manage CUCM Connections.
3. In the row of the connection you want, click Actions. The Menu popover opens.
4. Click Microsoft Teams. The Microsoft Teams dialog opens.
5. Switch on Enable. The Windows Connection and Pattern areas appear.
6. In the Pattern area, enter the Prefix that the CUCM routes to Teams.
7. In Strip, enter how many leading digits of the user's number are dropped. 0 cuts off nothing.
8. Turn on the switch in the header of the Windows Connection area if EasyUC is to set phone numbers in Teams.
9. Enter the Host, User and Password of the Windows host.
10. Enter the Teams Username and Teams Password of the Teams administrator account.
11. Click Save (top right or at the bottom of the dialog). After a successful save, the dialog closes and the message Success appears. Cancel discards your entries.
12. In the connection list, check whether MS Teams Prefix with your value is shown under the connection.

Fields and options

Checking the result and narrowing down errors

• Success: the dialog closes, the list shows MS Teams Prefix, and the Teams options are available when creating a device.
• Field error “This value must be a number greater or equal to 0”: Strip does not contain a valid number.
• Error “Could not connect to windows machine, please check user and password”: host, user or password of the Windows host are incorrect, or SSH cannot be reached.
• Other error texts in the Windows Connection area come from the PowerShell sign-in to Teams. In that case, check the Teams account.
• Calls do not reach Teams: check in the CUCM whether numbers with the prefix are routed, and compare the resulting destination number with the example above.
• These settings replace neither the Graph app nor the tenant ID or certificate of the SBC integration. Use EasyUC Teams for those.