A few options:<br><br>1. Upgrade to CCM 6.Xor 7.X so you don't need the MTP anymore.<br>2. Provision a separate CallManager (or 2) for the sole purpose of acting as an MTP and increase the number of possible channels on it.<br>
3. Purchase some CMMs<br>4. Purchase some 3845s loaded with DSPs.<br><br>Options 2, 3, and 4 don't really make much sense. As soon as you had CMMs, 3845s, or extra IPVMSApp CallManagers you wouldn't really need your SIP conference solution anymore.<br>
<br><div class="gmail_quote">On Wed, Nov 19, 2008 at 3:46 PM, c3voip <span dir="ltr"><<a href="mailto:c3voip@nc.rr.com">c3voip@nc.rr.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p>I am considering a purchase of a SIP audio conference bridge
to connect via a SIP trunk from CCM <a href="http://4.1.3." target="_blank">4.1.3.</a> </p>
<p> </p>
<p>Since the SIP trunk requires an MTP, what could I use for
MTP resources to get up to 500 SCCP G.711 calls across my SIP trunk? From
what I have read the CCM software MTP's are only good for 48 calls, what
would be a better solution?</p>
<p> </p>
<p>Thanks,</p>
<p>-C</p>
<p> </p>
</div>
</div>
<br>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br>