<div dir="ltr"><div>Rashmi Patel ( <a href="mailto:rashmika.patel@zones.com">rashmika.patel@zones.com</a> ) - 12:31 PM</div><div>Q: Does that mean conference resource will be used from NIM DSP not from mother board DSP resources</div><div>Priority: N/A</div><div><span style="white-space:pre"> </span> Dolan Spitler - 12:57 PM</div><div><span style="white-space:pre"> </span>A: When it comes to IP services (xcoding, conferencing, MTP) The motherboard DSP can be pooled with the NIM DSPs to increase the DSPfarm scale</div><div><br></div><div>Source: <a href="https://communities.cisco.com/docs/DOC-7823">https://communities.cisco.com/docs/DOC-7823</a> (look for the 4000 event on Oct 16th)</div><br><div class="gmail_quote"><div dir="ltr">On Fri, May 12, 2017 at 1:17 PM Brian Meade <<a href="mailto:bmeade90@vt.edu">bmeade90@vt.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">My understanding is any dspfarm resources such as conferencing/transcoding use the motherboard resources while the ones on the NIM are just for the voice ports themselves.</div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 12, 2017 at 11:51 AM, Jose Colon II <span dir="ltr"><<a href="mailto:jcolon424@gmail.com" target="_blank">jcolon424@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">If you will be using DSP's you will need to decided if you will need them on the motherboard or on the T1 NIM. On the motherboard I believe it can only be used for conferencing. You will need them on the NIM for transcoding.</div><div class="m_-4514633425061402314HOEnZb"><div class="m_-4514633425061402314h5"><div class="gmail_extra"><br><div class="gmail_quote">On May 12, 2017 6:42 AM, "Ryan Huff" <<a href="mailto:ryanhuff@outlook.com" target="_blank">ryanhuff@outlook.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="auto">
<div>T1 PRI commands are substantially different if that is in play.<br>
<br>
Sent from my iPhone</div>
<div><br>
On May 12, 2017, at 7:35 AM, Matthew Loraditch <<a href="mailto:MLoraditch@heliontechnologies.com" target="_blank">MLoraditch@heliontechnologies.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div class="m_-4514633425061402314m_-1900097389058718772m_3367617388779846226WordSection1">
<p class="MsoNormal"><span style="color:#1f497d">The vast majority of commands are the same. Netflow stuff is changed completely if you use that. Outside of updating interface names, most of our templates just worked.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#1f497d">Matthew G. Loraditch – CCNP-Voice, CCNA-R&S, CCDA<br>
Network Engineer<br>
Direct Voice: <a href="tel:(443)%20541-1518" value="+14435411518" target="_blank">443.541.1518</a></span><span style="color:#1f497d"><br>
<br>
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><a href="https://www.facebook.com/heliontech?ref=hl" target="_blank"><span style="font-size:8.0pt">Facebook</span></a></span><span style="font-size:8.0pt;color:#1f497d"> |
</span><span style="color:#1f497d"><a href="https://twitter.com/HelionTech" target="_blank"><span style="font-size:8.0pt">Twitter</span></a></span><span style="font-size:8.0pt;color:#1f497d"> |
</span><span style="color:#1f497d"><a href="https://www.linkedin.com/company/helion-technologies?trk=top_nav_home" target="_blank"><span style="font-size:8.0pt">LinkedIn</span></a></span><span style="font-size:8.0pt;color:#1f497d"> |
</span><span style="color:#1f497d"><a href="https://plus.google.com/+Heliontechnologies/posts" target="_blank"><span style="font-size:8.0pt">G+</span></a><u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span style="color:#1f497d"><u></u> <u></u></span></p>
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> cisco-voip [<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">mailto:cisco-voip-bounces@puck.nether.net</a>]
<b>On Behalf Of </b><a href="mailto:norm.nicholson@kitchener.ca" target="_blank">norm.nicholson@kitchener.ca</a><br>
<b>Sent:</b> Friday, May 12, 2017 7:31 AM<br>
<b>To:</b> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> [cisco-voip] Migrating a Cisco 2901 to a Cisco 4321<u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">We have a base config we use for building our 2901/11’s . Will this work on the 4321 or do I have to start from scratch.
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Thanks<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><b><span style="color:#00b050">Norm Nicholson<u></u><u></u></span></b></p>
<p class="MsoNormal"><b><span style="color:#00b050">Telecom Analyst<u></u><u></u></span></b></p>
<p class="MsoNormal"><b><span style="color:#00b050">City of Kitchener<u></u><u></u></span></b></p>
<p class="MsoNormal"><b><span style="color:#00b050"><a href="tel:(519)%20741-2200" value="+15197412200" target="_blank">(519) 741-2200 x 7000</a><u></u><u></u></span></b></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>cisco-voip mailing list</span><br>
<span><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a></span><br>
<span><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span><br>
</div>
</blockquote>
</div>
<br>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div></div>
</div></div><br>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br></div>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</blockquote></div></div>