<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>Message</TITLE>
<META content="MSHTML 6.00.2900.2769" name=GENERATOR></HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=965582814-11112005>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.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=965582814-11112005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=965582814-11112005>--Eric</SPAN></FONT></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT
face=Tahoma size=2>-----Original Message-----<BR><B>From:</B>
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net]
<B>On Behalf Of </B>Wes Sisk<BR><B>Sent:</B> Friday, November 11, 2005 5:41
AM<BR><B>To:</B> IT<BR><B>Cc:</B>
cisco-voip@puck.nether.net<BR><B>Subject:</B> Re: [cisco-voip] Device pools
and Meet-me conference<BR><BR></FONT></DIV>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.<BR><BR>/Wes<BR><BR>IT wrote:
<BLOCKQUOTE
cite=midB487D4C1FE6D04439061018C6EBC109B023F908E@exchange.cimgroup.com
type="cite">
<META content="Microsoft Word 11 (filtered medium)" name=Generator><!--[if !mso]>
<STYLE>v\:* {
BEHAVIOR: url(#default#VML)
}
o\:* {
BEHAVIOR: url(#default#VML)
}
w\:* {
BEHAVIOR: url(#default#VML)
}
.shape {
BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]--><O:SMARTTAGTYPE name="PersonName"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"><!--[if !mso]>
<STYLE>st1\:* {
BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal
}
SPAN.EmailStyle18 {
COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
page: Section1
}
</STYLE>
</O:SMARTTAGTYPE>
<DIV class=Section1>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Some more
information.<O:P></O:P></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">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?<O:P></O:P></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><O:P></O:P></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Thanks,<O:P></O:P></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Avidan<O:P></O:P></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><O:P></O:P></SPAN></FONT></P>
<DIV>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><FONT
face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">
<HR tabIndex=-1 align=center width="100%" SIZE=2>
</SPAN></FONT></DIV>
<P class=MsoNormal><B><FONT face=Tahoma size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT
face=Tahoma size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> <A
class=moz-txt-link-abbreviated
href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</A>
[<A class=moz-txt-link-freetext
href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</A>]
<B><SPAN style="FONT-WEIGHT: bold">On Behalf Of </SPAN></B><ST1:PERSONNAME
w:st="on">IT</ST1:PERSONNAME><BR><B><SPAN
style="FONT-WEIGHT: bold">Sent:</SPAN></B> Thursday, November 10, 2005 8:59
PM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> <A
class=moz-txt-link-abbreviated
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR><B><SPAN
style="FONT-WEIGHT: bold">Subject:</SPAN></B> [cisco-voip] Device pools and
Meet-me conference</SPAN></FONT><O:P></O:P></P></DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"><O:P></O:P></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">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).<O:P></O:P></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Eg. Phone in device
pool LosAngeles starts a meet-me, only phones in LosAngeles pool can join,
and SanFran pool phones get a busy...<O:P></O:P></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Has anyone else
experienced this? Is there a workaround?<O:P></O:P></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><O:P></O:P></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Thanks,<O:P></O:P></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Avidan
<O:P></O:P></SPAN></FONT></P></DIV><!--[object_id=#cimgroup.com#]-->
<P><FONT
size=-1>******************************************************<BR>This email
may contain trade secrets and/or other information that is <BR>proprietary
and/or confidential. Use of this by anyone other than the <BR>intended
recipient(s) is prohibited and may be unlawful. If you are not <BR>the
intended recipient, delete the e-mail and notify us
immediately.<BR>******************************************************</FONT>
</P><PRE wrap=""><HR width="90%" SIZE=4>
_______________________________________________
cisco-voip mailing list
<A class=moz-txt-link-abbreviated href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A>
<A class=moz-txt-link-freetext href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A>
</PRE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>