i'm getting trouble understanding which license PMP or SMP would be employed for scheduled meetings.
I have read MultipartyLicenseCallflow document and this could be the answer to my question:
LDAP directory is mandatory for PMP to operate with scheduled conference.
Anyway some doubts.
My deployment is made of the following:
-Cucm integrated with Conductor for rendezvous only conferences (no ad hoc conferences). Conferences hosted on vTelepresence Server.
-TMS, and TMS-PE integrated with company LDAP for users import (under Systems>Provisioning>Users). For any imported user a CMR is assigned (1 PMP license for any of these is employed). Users are imported from this corporate Base Dn: DC=corp DC=local.
- Our Windows Server hosting TMS is joined to corporate Domain (domain.local). The joining, allows Users (under Administrative Tools>User Administration>Users) to login to Smart Scheduler with their own domain account.
As for the description above, imported users (under Systems>Provisioning>Users) are different from Administrative Users (under Administrative Tools>User Administration>Users).
My question is:
To have 1 PMP consumed per schedulable meeting (triggered by Smart Scheduler), do i need to have matching users under Systems>Provisioning>Users and Administrative Tools>User Administration>Users?
Other questions about configuration of schedulable meeting:
- Conference template and aliases can be configured under Conductor views? Can i set up 2 different aliases (one for extension and one for URI) to reach the same conference? (From Conductor admin guide this should be).
- For schedulable conferences usage, the Location under Conductor should be Redezvous?
As mentioned previously in my previous article and following the same idea of certificate pinning in Cisco Meeting Server, to demonstrate this concept added since version 3.0. I used two different CA to sign :1-The WebBridge certificate with CA's certific...
Certificate pinning is introduced on cisco meeting server starting in CMS 3.0 to help prevent man in the middle attack.But what is the Certificate Pinning?Traditionally, SSL Handshake consists on the validation of the server's certificate, let's say colla...
In a Clustering over the WAN deployment, securing the ICCS (Intra-Cluster Communication Signaling) traversing the WAN can be a requirement. The IPSEC VPN Policy between nodes can be configured to secure the ICCS Traffic.To quickly verify that the IPSEC is...
Attracted by the concept of dial plan and the passion of writing, I launched a challenge to write a workbook with practical scenarios covering in details this concept, the result is a workbook with 30 practice labs treating many components such route patt...