call manager conferencing

[torledo]

What is the difference between a cisco call manager conference bridge and a cisco conference connecion (ccc)server. We cannot afford the cost of conference connection 1.2 which is $15000 on the cisco global price list, but we would still like the ability to perform meet-me and adhoc conferences thru call manager. How do we go about doing this without CCC ?

MA

 

[MG2005]

you need a hardware (transcoders for mixing different compression protocols and DSP resources) or sofware (G.711 only i believe) conference bridge resources to do ad-hoc conferencing.

Secure scheduled dial-up/dial-in conference bridges require the conference conenction or similar system

i use a blade solution in a 6500 switch
part # ws-svc-cmm-act and i have 7960G phones with ccm 4.1.2 that have built in bridge capabilites as well (G.711 streams only)

 

[lui3]

I have done up to 6 meet me and ad hoc conference attendees in software. I believe the limit on the CCM server itself si 48 users in one conference. Haven't ever maxed it out though. Meet me is the way to go since the CCM hosts the conference instead of the phone which can be affect by max calls tied to the phone i believe.

Lui3
CCNP,CCDA,A+/Net+
Cisco Wireless Specialization

 

[pndscm]

Cisco default MeetMe settings are version dependent. Cisco doesn't recommend more than 10 users in a MeetMe I believe but I have a customer doing 20 with no problems. It just isn't supported.
Both maximum MeetMe and AD-HOC conference attendee's is changeable in software and is dependent on conference resource types and numbers.

 

[MG2005]

problem with meet me is its not secure, no passcodes...someone can fat finger a Dn and get in your conference!!!

conf connection can be passcode protected, toll-free pilot number, etc..

 

[ys211]

I'm not sure where I got this info, on this forum or others, but this might help.


MeetMe password restriction
There are a few ways. Once way to do it natively in CCM is:
1) Create a new partition to secure the conference and assign it to the MeetMe number
2) Create and assign a CSS with that partition to the MeetMe initiator(s) (also include other partitions this caller would need, of course).
3) Create a Translation Pattern of 1xxxx.xxxx (assuming 1 does not overlap with other things in your dial plan and you have a 4 digit extension assigned to the MeetMe Conference). Put this TP into a partition accessible by all. Choose 'block this pattern'. Create another translation pattern of 12345.2222 (where 12345 is the access code and 2222 is the MeetMe number). Also put this TP into a partition accessible by all. Route this translation pattern, give the translation pattern a CSS that includes the new partition(s) created for the MeetMe numbers, and discard pre-dot. Of course, the auth code part and the extension part can be any length. Start the TP with a digit or digits that do not overlap with your current dial plan.

The reason for the wild-card translation pattern is so that if someone is guessing at codes they won't get reorder until they've completed dialing. The specific TP allows access to the MeetMe conference only by dialing the correct digits. For additional MeetMe numbers/auth codes just copy the specific TP and replace the code part with the new auth code and the DN part with the MeetMe DN. Make sure all MeetMe partitions are in the CSS assigned to the TP. Note that the MeetMe originator needs the restricted partition in their CSS in order to initiate the conference.

Another way to limit access is to create MeetMe numbers per department and put them in a partition specific to that department. Give users in that dept a CSS that includes that partition. Now those users can just dial in to the MeetMe but others can't (they don't have permission to dial that number b/c they don't have that partition in their CSS).

You can also use CRS (IP-IVR) to enforce auth codes, or Unity. With Unity you can require the callers to record their names and have Unity play the name in the conference before connecting the caller (name announce). The administration of an auth code is a bit cumbersome in Unity, however. You could use the TP approach above to get the call to Unity, then have Unity record the name and transfer to the MeetMe number. CTI and/or Unity ports need to have the MeetMe partitions in their CSS.