Looking for something?

You will find your answers here!

Sorry, we didn't find any relevant articles for you.

Send us your question using the form below and we will get back to you with a solution.

Integrations & SSO

How To: TeamMate Connector - Setup Integration for Teams

Objective

This article explains how to configure Teams Integration in TeamMate Connector, connect the PBX, and set up users for Microsoft Teams calling.
 

User Context

  • Teams integration setup
  • I need to setup my Teams integration
     

Procedure

Follow these 3 sections to complete the Teams Integration setup:

  • Initial Setup
  • PBX Setup
  • User Setup
     

Initial Setup

  1. Log in to TeamMate Connector
  2. At the top-right corner, click Add Enterprise

  3. Fill out the Add Enterprise fields

  4. For Services, select PBX

  5. Set the PBX type to Netsapiens by moving it from the unassigned list to the assigned list.

  6. Check Allow External Numbers.

  7. Click Submit. 

    NOTE: An email has been sent to the MGA requesting access for integration to move forward. The email will come from no-reply@connecttoteams.com. 

     
  8. Have the customer set up the Direct Routing user with a Microsoft user license and Microsoft Teams license.

    NOTE: Allow up to 48 hours for Direct Routing to complete.

     

PBX Setup

After the Direct Routing user is created, we need to connect the PBX to the TeamMate Connector. 

  1. Within the enterprise, select PBX from the left-hand navigation panel.

  2. Click the blue Add PBX button.

  3. Complete the General Settings tab using the following values:
    • PBX Type: Netsapiens
    • PBX Location: PBX HG
    • PBX DNS Lookup Type: Host
    • PBX Outbound Transport Type: UDP
    • PBX SIP Domain: Customer domain
    • PBX SIP Domain Proxy: Customer domain proxy
    • Voicemail Feature Code: *62
    • PBX SIP Domain Proxy Port: 5080
    • Codecs: G.711 A-law and G.711 U-law
    • Topology Hiding: Leave blank
    • Reg Expires: 600
    • Delay ACK Relay: Checked
    • Caller Name Policy: Transparent
    • Caller ID on Forwarded Calls: User's Caller ID
    • Pause inbound Calling based on Teams Presence: Leave blank
    • Encoded Feature Codes Supported: Leave blank

  4. Fill out the Advanced Settings tab using the following values:
    • Portal Authorization URL: https://usw.crexendovip.com/ns-api/oauth2/token/
    • Client ID: Teammates
    • Client Secret: ca7d6ada9a7b0e7c99e76f7969a9fa91
    • API Access Username: teammates@crexendo.com
    • API Access Password: hxy@hqr4BMG1pma3afa
  5. Click Save Settings.

TIP: To edit the PBX, click the ellipsis (3 horizontal dots) button under the Action column, then select Edit.

 

User Setup

Once the PBX is connected, proceed to setting up the user.

  1. Select Users in the left-hand navigation panel.
  2. Click the blue Add User button.


    IMPORTANT: Before creating the user, create a new Teams extension in VIP.

     
  3. Fill out the user section using the following:
    • PBX Location: PBX HG

      TIP: Complete this field first because selecting it later clears the other settings.

       
    • Available Voice Route: US WEST
    • User Tag: Leave blank
    • Teams User: Select the email address of the user being set up
    • SIP User: Select the user's extension in VIP
    • Phone Number: Enter the user's extension
    • Disable VM in Teams: Check this box
    • Caller Name Policy: Transparent
    • Caller ID on Forwarded Calls: User's Caller ID
    • Assign Default DialPlan Policy: Check the box
    • User Devices: Select the user's Teams extension
       
  4. Click Save User
  5. Repeat the process for all remaining users.


    NOTE: Once all users are created, have the MGA sign in to TeamMate Connector and run a user sync from the dashboard.

     
  6. Have users log out of Microsoft Teams and log back in.

    TIP: The Calls icon will appear in the left-hand navigation upon re-login. If they accepted consent earlier, you can do this from your own dashboard.

     

 

Escalation Information

Escalation Information: SD3

If you have any questions, concerns, or issues, contact the Service Desk III (SD3) team.

 

Change Log

Date Description
Apr 30, 2026 Article migrated and revamped.

 

Was this article helpful?