To better understand how the call is processed at the CMS level, let’s take the following scenario:
- User jsmith@lab.local is registered using Cisco Jabber to HQ-CUCM.
- Active Directory is integrated to CMS Cisco Meeting Server and the user jsmith@lab.local is imported into CMS.
- Another user join a conference named room using a web browser.
- An administrator tries to add the user jsmith@lab.local to meeting using the “Add Participant” option in Cisco Meeting Management CMM
The Cisco Jabber jsmith@lab.local does not receive an incoming call from CMS and the administrator receives the following log on CMS’s Event Log.
This specific flow does not reach HQ-CUCM. It’s using the path from the CMS.The user jsmith@lab.local has an account to CMS and must be logged in using the Cisco Meeting App.
For users not imported into CMS, the Dial Out will ring the Jabber Client registred into HQ-CUCM. In other words the CMS will use an outbound rule to send the call to HQ-CUCM and the Jabber Client will ring.
To better understand let’s take another scenario:
- User pperez@lab.local is registered using Cisco Jabber to CUCM.
- Active Directory is integrated to CMS Cisco Meeting Server and the user pperez@lab.local is NOT imported into CMS.
- Another user join a conference named room using a web browser.
- An administrator tries to add the user pperez@lab.local to meeting using the “Add Participant” option in Cisco Meeting Management CMM.
- The CMS will try to find an Outbound Call Rule with Domain lab.local and the SIP Proxy to use (in this case hq-cucm.lab.local) to route out the call, an Outbound Call Rule is similar to SIP Route Pattern on CUCM.
- The HQ-CUCM will receive the call and find that the user pperez@lab.local is registered and the Client Jabber rings.
Therefore to allow the CMS-1 and CMS-2 to dial out or to send a call to the user pperez@lab.local Jabber Client or any user not imported into CMS, an Outbound Call is mandatory with the domain lab.local.
