Getting Started with Direct Routing Pro
Once the new customer has been onboarded, M365 users must be applied the appropriate license and basic template configuration before they can connect calls. Users are applied basic configuration in the Onboarding scripts including a default route and default routing policy and a configured PSTN gateway for connecting calls (see figures below). Provisioning can be performed manually or automated using templates. The templates can then be applied to different user groups in the Enterprise Active Directory. The templates are mapped to Calling Policies that are mapped to Voice Routes for different site locations. The routes defined through which SBC device calls are connected to the customer or provider SIP Trunk or to the Provider IP PBX. Dial plan patterns can also be associated with the Voice Routes. The PSTN Usage maps the Voice Route to the Voice Routing Policy. You can then assign phone numbers (DIDs) and map them to Templates together with OnlineVoiceRouting and other Teams Calling policies.
● | The M365 Onboarding script by defaults creates Online VoiceroutingPolicy Unrestricted. |
● | Each user to enable Enterprise Voice requires the appropriate Microsoft Phone System license (see Microsoft Phone System Service Plan). |
● | All assigned numbers must be configured in the site location dial plan, see Manage SBC Prefixes. |
➢ | Do the following: |
1. | Open the Customer portal (see Accessing the Customer Portal (Direct Routing)) and wait for the initial replication process to complete. |
2. | In the Navigation pane, select Online Voice Routing > Voice Routes and Voice Routing Policy. See the default entries. |
If the Onboarding script for including the Site Name tag was applied
The figure below illustrates the logical associations between the different Configuration entities.
The following figure outlines the step-by-step provisioning instructions:
● | A subset of Teams Calling Policies are available for manual configuration. Provisioning of the full range of policies must be performed using template automation. |
● | During configuration, refresh the Execution queue (run Process all) to synchronize with the Live Platform database (see Monitoring M365 Replication Actions Queue). |
■ | PSTN Gateways: During Onboarding you configured a PSTN Gateway (SBC device) to connect calls with Microsoft 365 using either the service provider's SIP Trunk or IP PBX or the customer SIP Trunk provider (BYOC). This gateway is defined in the Live Platform database. This option lets you configure additional BYOC devices. See PSTN Gateways. |
The PSTN Gateway table does not display the PSTN gateway configured in the Onboarding; values are only displayed when added manually in Day Two.
■ | PSTN Usage: Mapping of Voice Routes to Voice Routing Policies. In the example below, separate Usages are defined for each site location. Routes and Policies data is filled when configured below. See PSTN Usage. |
■ | Voice Routes: Configure PSTN Gateways and PSTN Usage and Dialing patterns. In the example below, both sites are assigned to separate Online PSTN gateways and PSTN usages. See Voice Route. |
It may take a few minutes for data to process. In the meantime, proceed to configure other entities and then return to this screen.
■ | Voice Routing Policies: Configure Voice Routes and PSTN Usage. In the example below, each site is assigned a separate policy with its respective PSTN usage. See Voice Routing Policy. |
It may take a few minutes for data to process. In the meantime, proceed to configure other entities and then return to this screen.
■ | Upload Numbers: Upload numbers to the SBC Dial plan (default CustDialPlan) with the PSTN Gateway tag for the Customer Site Location (see Manage SBC Prefixes. |
■ | Assign Number Ranges: Define numbers ranges based on the uploaded numbers for automatic configuration to users in the applied templates (see Managing Number Ranges). You can also assign numbers manually , see Manually Assigning Phone Numbers to Users. In the example below, one range is defined for Site Location 'Napoli' and another range for Site Location 'Paris'. |
■ | Templates: Configure templates including Calling Policies and Number ranges (automatic Number assignment). In the examples below, custom Online Voice Routing policies defined above are applied to each respective template. In addition, Enterprise Voice is enabled and the respective number ranges defined above are applied to each template. See LifeCycle Management Templates. A subset of Calling Policies can also be applied manually to the users (see Manually Applying M365 User Policies). In the example below, respective templates are defined for Napoli and Paris. |
■ | Security Groups: Assign Security Groups to templates; Azure Active Directory Organizational User Groups. In the example below, Site One is assigned to the 'Communications' Group and Site Two is assigned to the 'Design' group. The members for each group are also shown below. See Binding Templates to Security Groups. In this example, the SiteOne Napoli Template is assigned to the 'Retail' group and SiteTwo Paris Template is assigned to the SOC Team. |
■ | Create Dial Plans and Assign Normalization Rules: Create M365 Dial plans and assign Normalization rules. See Microsoft 365 Dial Plan and Normalization Rules. |
The figure below shows the User configuration after templates have been applied:
■ | Users from the 'Retail' group are assigned with the Napoli template. One user from the SOC team is assigned with the Paris template. |
■ | Online Voice Routing Policy, Online PSTN Gateway and Site Location fields are configured for each site. Note in the example below, only one user is configured for Site Two Paris. |
■ | The Usage Location (configured in Azure) has been manually set to Italy and France (see Set Usage Location). |
■ | Phone Numbers (DIDs) are automatically assigned to users according to the defined Number ranges with Napoli and Paris dialing prefixes. |
See also Voice Routing Scenarios.