Configuring access to IP Office features over MTCTI messaging

Last Updated : Nov 02, 2020 |

About this task

IP Office uses a Multi-Tenancy Computer Telephony Integration (MTCTI) interface to provide support for specific telephony features. For example, Avaya Workplace Client uses MTCTI to provide features such as hunt groups.

Avaya SBC supports the MTCTI interface. It relays MTCTI messages from clients of a specific tenant to an IP Office instance for the tenant through a Reverse Proxy in a Network Address Translation (NAT) environment. Avaya SBC applies NAT on these messages and relays the payload without modification. Distribution of MTCTI messages is done using a host-header in HTTP messages and server name indication (SNI) information in a certificate. That is, Avaya SBC has different SNI and host header for a specific tenant and uses it to route these messages for that tenant.

Procedure

  1. Configure multiple SIP IP Office servers use for multi-tenancy as described in Adding a new SIP server profile.
  2. Configure a reverse proxy relay service using XMPP to the IP Office systems for each tenant as described in Creating reverse proxy service for multi-tenant or IP Office powered deployments.
  3. Configure an SNI group for each IP Office system as described in About configuring SNI groups and Creating a new SNI group.
  4. Configure multi-tenant TLS server profiles with an SNI group as described in Creating a TLS server profile. Note that the server profile must have another certificate to be used along with the certificates already administered in the SNI group.
  5. Configure multi-tenant TLS client profiles with an SNI group as described in Creating a TLS client profile. The TLS client profiles must have certificates for each tenant.
  6. Configure a network signaling interface to use the tenant profiles as described in Adding a new signaling interface.
  7. Configure a subscriber flow with URI groups for SIP routing as described in Creating a subscriber flow and Creating a new URI group.