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?
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.
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@example.com
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 firstname.lastname@example.org and they would join your conference. You can also create auto-dialed participants to match the conference name.
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...