Advanced Proxy Set Configuration for Operator Connect Service
By default, Operator Connect is pre-configured to work with Microsoft Operator Connect ‘peering’ mode with two IP Groups, one for Teams side and the other for the SIP Trunk Operator side. If customers require SIP registration, you can configure the Advanced mode to create an additional unique IP group for the customer service. This can be done using the following scripts:
|
■
|
'OC Essential default SBC Onboarding script' adds an Operator Connect service for a customer using the Service Providers' SIP Trunk. This script applies a common Proxy Set for all services configured with the Service Provider SIP Trunk. The script creates an IP Group for the Service Provider SIP Trunk leg and another for the Microsoft Teams leg. It uses the customers' Tenant Id for dial plan tagging. If Carrier registration is configured, a rule is added to the Account Table for registration of the new IP Group towards the carrier IP Group. |
|
■
|
The Operator Connect BYOC Customer onboarding scripts adds an Operator Connect service for a customer using the customers' BYOC SIP Trunk. The script configures a unique Proxy Set for each BYOC trunk according to configured values (see below). The script creates an IP Group for the BYOC trunk and another for the Microsoft Teams leg. It uses the customers' Tenant Id for dial plan tagging. If Carrier registration is configured, a rule is added to the Account Table for registration of the new IP Group towards the carrier IP Group. |
|
●
|
These scripts are currently not available in database for applying in Day One onboarding. |
|
●
|
All numbers uploaded to Operator Connect customers are added to the OCDialplan . |