Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

Rendezvous Conferencing using Conductor

Unanswered Question
Oct 2nd, 2014
User Badges:



Is there a generic way in which you can configure Rendezvous conferencing in a Conductor/CUCM deployment?

I had an idea in my head that i could use an alias of "meet.<userid>.domain" for rendezvous calls; <userid>.domain being the users SIP URI in CUCM. Then once this alias came into Conductor, i could maybe do some regex to take the <userid>.domain part and use this as the auto-dialed participant address.

Obviously after going through the latest CUCM/Conductor deployment guide this isn't possible and i'm far off the mark but am i correct in thinking that if i wanted to roll this out for 300+ users, i would have to create individual Conference Aliases, Templates and auto-dialed participants?


Thanks, Simon 

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
George Thomas Thu, 10/02/2014 - 09:09
User Badges:
  • Blue, 1500 points or more

Do you have TMS/TMSPE? If yes, you could have TMSPE create it for your else you will have to manually create it conference aliases, not sure why you would need different templates.. 

Simon Battye Fri, 10/03/2014 - 06:05
User Badges:


We have TMS but we don't have any Provisioning Extension Licenses, i'm assuming these are required in order to use the Collaboration Meeting Rooms in TMS 14.4 and Conductor XC2.3?

Thanks, Simon 

Patrick Sparkman Fri, 10/03/2014 - 07:57
User Badges:
  • Purple, 4500 points or more
  • Cisco Designated VIP,

    2017 TelePresence

I wouldn't think you'd need provisioning extension licenses, as those licenses are simply used in provisioning endpoints.  TMSPE gives you the Smart Scheduler for TMS and now CMR, so I don't think they'd prevent you from using those functions if you choose to not provisioning any endpoints because you don't have licenses.

Daniel Isham Fri, 12/05/2014 - 16:19
User Badges:

Not factoring in TMSPE at all, if you have Conductor registered to CUCM, SIP Route Patterns only route based on host portion of the URI. You can't have a SIP Route Pattern of meet.* and expect it to route based on [email protected]

That being said, you could create a SIP Route Pattern to match meet.yourdomain.com to send to Conductor. In Conductor, have a conference alias that matches (.*)@meet.yourdomain.com and you could create the conference name like Meet \1

Then anyone else dialing into the conference would just dial for example [email protected] and they would join your conference. You can also create auto-dialed participants to match the conference name.


This Discussion

Related Content