I was under the same assumption of why there was a dsp slot on the NIM. I know I read a Cisco doc somewhere that lead me that direction.
On May 12, 2017 2:28 PM, "Ryan Huff" <[email protected]> wrote: > So this is interesting; I was under the impression the backplane DSP could > not extend to the NIM (and is the fundamental reason, among others, that > the NIM has its own DSP) .... looks like I have a new lab task :). > > On May 12, 2017, at 3:09 PM, Anthony Holloway < > [email protected]> wrote: > > Rashmi Patel ( [email protected] ) - 12:31 PM > Q: Does that mean conference resource will be used from NIM DSP not from > mother board DSP resources > Priority: N/A > Dolan Spitler - 12:57 PM > 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 > > Source: https://communities.cisco.com/docs/DOC-7823 (look for the 4000 > event on Oct 16th) > > On Fri, May 12, 2017 at 1:17 PM Brian Meade <[email protected]> wrote: > >> 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. >> >> On Fri, May 12, 2017 at 11:51 AM, Jose Colon II <[email protected]> >> wrote: >> >>> 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. >>> >>> On May 12, 2017 6:42 AM, "Ryan Huff" <[email protected]> wrote: >>> >>>> T1 PRI commands are substantially different if that is in play. >>>> >>>> Sent from my iPhone >>>> >>>> On May 12, 2017, at 7:35 AM, Matthew Loraditch <MLoraditch@ >>>> heliontechnologies.com> wrote: >>>> >>>> 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. >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> Matthew G. Loraditch – CCNP-Voice, CCNA-R&S, CCDA >>>> Network Engineer >>>> Direct Voice: 443.541.1518 <(443)%20541-1518> >>>> >>>> Facebook <https://www.facebook.com/heliontech?ref=hl> | Twitter >>>> <https://twitter.com/HelionTech> | LinkedIn >>>> <https://www.linkedin.com/company/helion-technologies?trk=top_nav_home> >>>> | G+ <https://plus.google.com/+Heliontechnologies/posts> >>>> >>>> >>>> >>>> *From:* cisco-voip [mailto:[email protected] >>>> <[email protected]>] *On Behalf Of * >>>> [email protected] >>>> *Sent:* Friday, May 12, 2017 7:31 AM >>>> *To:* [email protected] >>>> *Subject:* [cisco-voip] Migrating a Cisco 2901 to a Cisco 4321 >>>> >>>> >>>> >>>> >>>> >>>> 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. >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> Thanks >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> *Norm Nicholson* >>>> >>>> *Telecom Analyst* >>>> >>>> *City of Kitchener* >>>> >>>> *(519) 741-2200 x 7000 <(519)%20741-2200>* >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> cisco-voip mailing list >>>> [email protected] >>>> https://puck.nether.net/mailman/listinfo/cisco-voip >>>> >>>> >>>> _______________________________________________ >>>> cisco-voip mailing list >>>> [email protected] >>>> https://puck.nether.net/mailman/listinfo/cisco-voip >>>> >>>> >>> _______________________________________________ >>> cisco-voip mailing list >>> [email protected] >>> https://puck.nether.net/mailman/listinfo/cisco-voip >>> >>> >> _______________________________________________ >> cisco-voip mailing list >> [email protected] >> https://puck.nether.net/mailman/listinfo/cisco-voip >> > _______________________________________________ > cisco-voip mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/cisco-voip > >
_______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
