Conductor currently only supports the below MCU’s. Its has also been noted as a limitation in the release notes for Conductor Software XC1.2
Cisco TelePresence MCU 4200 Series, version 4.2 or later
Cisco TelePresence MCU 4500 Series, version 4.2 or later
Cisco TelePresence MCU 4501 Series, version 4.2 or later
Cisco TelePresence MCU MSE 8420, version 4.2 or later
Cisco TelePresence MCU MSE 8510, version 4.2 or later
Cisco TelePresence MCU 5300 Series, version 4.3 or later
By using a SIP trunk between Cisco Unified Communications Manager and the VCS, endpoints registered to the CUCM, as well as endpoints registered to the VCS, will be able to join a conference call using the Conductor. Third Party Standards based (H323, SIP, TIP) enpoints are also supported.
Just small correction that current release version (XC1.1 and XC1.2) support following MCU.
- Cisco TelePresence MCU 4200 Series, version 4.2 or later
- Cisco TelePresence MCU 4500 Series, version 4.2 or later
- Cisco TelePresence MCU MSE 8420, version 4.2 or later
- Cisco TelePresence MCU MSE 8510, version 4.2 or later
- Cisco TelePresence MCU 5300 Series, version 4.3 or later
This is limitation due to API integration on TelePresence Conductor to manage MCU (TelePresence Conductor manage configured MCU to control conference setup, configuration, termination, etc.)
We are planning to support Cisco TelePresence Server in next major release first then investigate 3rd party MCU support follow by it.
TelePresence Conductor will allocate MCU resource automatically within configured MCU pool so will perform as load balancing the call on MCU, if multiple MCU configured on MCU pool. (It will automatically cascade the MCU as needed).
Also from X1.2 release, TelePresence Conductor support geographically cascade so that customer able to optimize video traffic between countries/theater (i.e. large conference call cross theater).
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...
Understanding Media Negociation in Interworking / Traversal Call : SIP <-> H323 through Expressway. Inside SDP and H245. Both signaling and Media goes through the Expressway so the IP address of expressway is offered to both SIP and H.323 endpoin...
Sometimes you troubleshoot the phone presence status issue, or you are wondering how the status is retrieved by IMP, the best place to start is to look at the SIP Publish message sent by the CUCM to IMP, Capture the SIP Publish message using wireshark, in...
The translation pattern is the most important tool in the Call Routing Process on Cisco Unified Communication manager.By definition a Translation Pattern is used to match the DIALED NUMBER (CALLED). After a match is found we perform a digits manipulation....
Sometimes, you want to populate the Self Service User ID and the Primary Extension + the Conference Now Meeting Number automatically with the IpPhone or Telephone Number LDAP Attribute used in the LDAP Directory configuration page when importing AD users ...