Showing results for 
Search instead for 
Did you mean: 

Succeeded in creating dial-in conferences, but failed in ad hoc conferences


Dear all,

We're a collaboration partner with Cisco and have our apps register to CUCM in the collaboration project. 

With our apps registering to CUCM, we can make video calls with Cisco endpoints like DX80. Currently, 

we attempting to leverage the telepresence server and conductor to enable our apps to have video conferencing 

calls with DX80. However, in the current setting of CUCM, telepresence server, and conductor, our apps and DX80 

can make a video conferencing call in a dial-in conference room, but fail to use the ad hoc conference. For 

the ad hoc conference, only audio is successfully merged among DX80 and our apps (no video).

Is this a setting issue of CUCM/telepresence server/conductor? Or the hardware resource issue? 

Can anyone kindly point out the potential directions on solving this issue? Any comment is greatly appreciated.

Best regards,


2 Replies 2

Jaime Valencia
Hall of Fame Cisco Employee Hall of Fame Cisco Employee
Hall of Fame Cisco Employee

Do you see the SIP trunk you configured for ad-hoc as up in CUCM??

Do you have configured the proper configuration in Conductor for ad-hoc?

Do you see errors in the conference creation event logs?



if this helps, please rate

Hi Jaime,

The first two should be correctly configured, but we did see ``conference.creat'' failed message (AUTHENTICATION FAILURE). However, we are sure that we set the same username/password in the Conductor and CUCM. Why the authentication fails when the username/password are set to the same? Can you kindly point out the possible reason? Thanks for your kind help.

Best regards,


Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Recognize Your Peers