Set Up CallApp User (Bulk)

Prev Next

Once Direct Routing and CallApp settings are completed, you can configure CallApp users individually or in bulk. This article presents the steps to configure users individually.  

Before You Begin

  • Ensure that you have configured your desired Sync User Groups. Listing your sync user groups is a way for you to only share user data to limited set of users who are to use ConnecttoTeams services. If no user groups are defined, all your organization’s Teams Users will be sync’d into ConnecttoTeams systems.

Part I: Import the File

  1. Log in to the ConnecttoTeams Enterprise Portal.

  2. From the Enterprise Admin Menu, navigate to the "Bulk Upload".

  3. Select “Call App” for User Type.

  4. Select the appropriate Voice Routes specific to the Call App service, PBX Locations and check or uncheck the box for Assign Default DialPlan Policy?

    Note

    If you have multiple PBX locations and/or voice routes, prepare CSV files with users from only one combination at a time, and do additional bulk upload(s) later to add users to the different one(s).


  5. Open the sample file format and prepare your CSV file for upload.

     
     
    TeamsUserID: The Microsoft Office 365 email address of the user.

    SIP UserID: from the PBX of the account to be linked to the TeamsUserID above. This can be entered with or without the domain.

    PhoneNumber: Will appear prefixed by an E164 format based on the Location of the User as identified in the User Microsoft Profile. For instance, in the US Phone Number 10077 would appear as +110077 in Microsoft Teams.

    Use Teams Voicemail:  Enter “FALSE”.  Note that the Call App only supports the PBX Voicemail option at this time.

    SIPAuthenticationID

    Password: the SIP Password

    PortalLoginName (optional: leave blank if not desired): Username credentials for a PBX portal if available.

    PortalLoginPassword (optional: leave blank if not desired): Password for a PBX portal if available.

    MACAddress - This portion is for the Auto Provisioning Settings. Leave this field blank if you are not using the SIP auto-provisioning process.

    Caller Name

    Caller ID on Forwarded Calls

  6. Select Upload when you have successfully uploaded your desired Bulk Upload CSV file.


  7. You will see a screen with the users extracted from the CSV file. Click "Validate" in the upper right-hand corner. This will analyze the file and ensure there are no obvious data entry failures, such as invalid email addresses, an extension that is already in use, or an attempt to configure a user who is not properly licensed. Hovering over the error will give guidance about what specific error is preventing configuration.

  8. If there are no detectable errors the blue "Validate" button will change to say "Submit", as shown below. Click Submit to kick off the user addition process.

Part II. Sync Changes to Microsoft

If changes to user/s were made by a Service Provider without Service Provider management consent, the Enterprise Admin must log into the Enterprise Portal and click on Sync Teams Users.

If changes user/s were made by the Enterprise Admin or a Service Provider with management consent, the system automatically syncs the changes. No further action is required.

Check Sync Status

The user provisioning status will be reflected in the Enterprise Dashboard. Click here for more info about User Provisioning Status Indicators.

Expect:
- That the first time sync will take up to 24 hours. Come back to check the status.
- That succeeding syncs will take up to 4 hours. Come back to check the status.
If sync is not completing within these wait times, contact your Service Provider.

Part III. Monitor User Sync Status

The user provisioning status will be reflected in the Enterprise Dashboard. Click here for more info about User Provisioning Status Indicators.

Note to the Service Provider

If sync is not completing within these wait times, request from help from ConnecttoTeams Support.


When the sync status shows completed, the Teams User can start utilizing the CallApp.