Guest

Preview Tool

Cisco Bug: CSCul19411 - Conductor to work with MCU's Auto-attendant

Last Modified

May 03, 2017

Products (1)

  • Cisco TelePresence Conductor

Known Affected Releases

XC2.2

Description (partial)

Symptom:
The conductor is used to manage the resources on different MCUs and allocates the port as per the availability. The conductor does not have any idea about the auto-attendant on the MCU. The conductor will be called from the VCS only if the user dials the designed dial plan during the VCS-Conductor deployment. If the user is dialing the auto-attendant of any one of the MCU, the conductor will not be used as VCS will not be sending the information to Conductor but will directly pass the information to the MCU.
The only way to utilize conductor with 2 MCUs with all the resources availability, the user will have to dial the designed dial plan for the conductor to initiate the call.
CU would like to request this feature that MCU auto attendant to be managed by Conductor.

Conditions:
none

Related Community Discussions

Customise users options under CMR portal
Hello Guys, i have MCU (4510) deployement with TMSPE (1.5)/Conductor (XC4.0). Users have been asking about CMR portal customisation. is possible to Customise option like: - Remove auto-dial option from CMR user Portal (to avoid miss use of this option by users) - Change user audio entrance for CMR - Custumise background image for conference room. Any information from you will be very helpfull regards,
Latest activity: Mar 01, 2016
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.