[cisco-voip] Device pools and Meet-me conference

[Fretz, EA Eric at IS]

For what it is worth, I am going through a VERY similar issue right now.  If
you have a 6500 series chassis laying around, the CMM card with ACT
daughtercards will give you the best bang for the buck in transcoding
resources.  The 6608 is $25K and only yeilds 32 conference participants.
The CMM with 1 ACT (it can support up to four) costs $18K and will support
upto 128 conference participants.  Another drag on the 6608 cards is that
your switch must be running CatOS.  The CMM supports CatOS or IOS.
 
--Eric

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Wes Sisk
Sent: Friday, November 11, 2005 5:41 AM
To: IT
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Device pools and Meet-me conference


The default confernce resource that ships with CallManager is hosted in the
IP Voice Media Stream App process on the CallManager server.  This resource
only supports the g711 codec.  If you wish to host g729 members in
conference you must provide g729 conference resource or transcoders.  There
are IOS versions of both available for smaller scale deployments and modules
like the CMM and 6608 for large deployments.

/Wes

IT wrote: 

Some more information.

It appears this is related to the Codecs for calling between regions. When I
set all the regions to use the same codecs to call between themselves,
multiple regions/devicepools could join the same conference.  Is this a
technical limitation of the meet-me conference? Will a bridge solve the
problem?



Thanks,

Avidan




  _____  


From: cisco-voip-bounces at puck.nether.net
<mailto:cisco-voip-bounces at puck.nether.net>
[mailto:cisco-voip-bounces at puck.nether.net
<mailto:cisco-voip-bounces at puck.nether.net> ] On Behalf Of IT
Sent: Thursday, November 10, 2005 8:59 PM
To: cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net> 
Subject: [cisco-voip] Device pools and Meet-me conference



For some reason, phones in different device pools cannot join the same
meet-me conference. Whatever device pool the originator is in, becomes the
only device pool from which joining parties can join (but any outside
caller).

Eg. Phone in device pool LosAngeles starts a meet-me, only phones in
LosAngeles pool can join, and SanFran pool phones get a busy...

Has anyone else experienced this? Is there a workaround?



Thanks,

Avidan 

******************************************************
This email may contain trade secrets and/or other information that is 
proprietary and/or confidential. Use of this by anyone other than the 
intended recipient(s) is prohibited and may be unlawful. If you are not 
the intended recipient, delete the e-mail and notify us immediately.
****************************************************** 



  _____  


_______________________________________________

cisco-voip mailing list

cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net> 

https://puck.nether.net/mailman/listinfo/cisco-voip
<https://puck.nether.net/mailman/listinfo/cisco-voip> 

  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20051111/3805daab/attachment-0001.html