to deploying Pexip Infinity with Cisco Unified Communications Manager
The Cisco Unified Communications Manager (CUCM) is a SIP registrar and call control device. This guide describes how to integrate a single Pexip Infinity location with a single CUCM by setting up a SIP trunk between the two systems, so that calls can be routed between endpoints registered to the CUCM, and Pexip Infinity services.
In larger deployments where you may have multiple CUCM nodes, and where you have a distributed Pexip Infinity architecture with many Conferencing Nodes deployed across various locations in your network, you should ensure that calls from CUCM-registered devices are routed to their nearest Pexip Infinity Conferencing Nodes when they dial a Virtual Meeting Room alias.
Please contact your Pexip authorized support representative if you want help in designing a distributed setup with Pexip Infinity and CUCM.
This guide assumes that you are familiar with
It assumes that Pexip Infinity and
The examples used in this guide assume a dial plan where all Virtual Meeting Room aliases are in one of the following two formats:
It assumes that a Virtual Meeting Room, named meet.alice, has been configured with two aliases: email@example.com and firstname.lastname@example.org.
Note that Pexip Infinity supports aliases that include a domain (e.g. email@example.com), as well as aliases without a domain (e.g. just 555123). To match a received destination alias that includes a domain, the aliases configured within Pexip Infinity must also include the same domain. If an alias configured on Pexip Infinity does not include a domain:
- calls to <alias> without any domain portion (e.g. 555123) will be matched
- calls to <alias>@<IPaddress> (e.g. firstname.lastname@example.org) will be matched
- calls to <alias>@<domain> (e.g. email@example.com) will not be matched.
Depending on your dial plan, you may need to configure CUCM's Call Routing to ensure the Virtual Meeting Room aliases are in the expected format when received by Pexip Infinity.