[cisco-voip] Conference bridge How to in CCM 6.x???

[Stone Cold]

We did this before and the method we used was to make the 1800 number point
to a call handler in unity. When Unity answered the first promt said
something like, Welcome to xyz company conference bridge please enter your
conference passkey, then when they entered the passkey it would transfer
them to the meet-me conference. The passkey was just one of the extensions
of the meet-me conference. An IP phone had to first log into the bridge to
initiate it. Its been a while since I tried it and there may be a better way
to do it now but it worked and has been that way for a few years. I think we
created 6-7 meet-me bridges that got used and reserved from an echange
calendar. No integration to CM here this was just the method they used to
manage it.

On Fri, Apr 11, 2008 at 5:01 PM, omar parihuana <omar.parihuana at gmail.com>
wrote:

> Hi guys,
>
> I'm newbie in CCM (now CUCM) currently, I'm working in a LAB with CUCM6.0.
> After some test, all seems working well so far!.  However, today my friend
> ask me about conferencing, here the situation:
>
> He need create a conference bridge, for example, an internal extension and
> the others participants dial to internal extension and then all are in
> conference... easy meet-me!!!! But, he asked, I need also a key in order to
> connect to the conference.... so I think that meet-me don't work with
> passwords/keys to dial a conference... so how can I create a conference
> bridge that need the internal extension or toll-free number and one
> password/key to join the conference.... pls... only I have CUCM6.0 and Unity
> 5.x...
>
> Thanks....
>
> --
> Omar E.P.T
> -----------------
> Certified Networking Professionals make better Connections!
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20080411/12e26b78/attachment.html