<div>Where in the SRND is the call limit for various gateways listed? I'd like to take a look.</div>
<div> </div>
<div>The environment I was referring to was a UCCE build performed by Cisco AS. 4 gateways w/ 10-12 PRI's each handling upwards of 50K calls/day inbound and outbound - all calls were transcoded on these gateways after the IVR and before heading to agents. During busy hour call volumes weren't above 250 calls/gateway but I'd like to see the reference.</div>
<div><br clear="all">Matthew Saskin<br><a href="mailto:msaskin@gmail.com">msaskin@gmail.com</a><br>203-253-9571<br><br>July 18, 2010 - 1500m swim (in the hudson), 40k bike, 10k run<br>Please support the Leukemia & Lyphoma Society<br>
<a href="http://pages.teamintraining.org/nyc/nyctri10/msaskin">http://pages.teamintraining.org/nyc/nyctri10/msaskin</a><br><br><br></div>
<div class="gmail_quote">On Wed, Feb 10, 2010 at 4:53 PM, Rhodium <span dir="ltr"><<a href="mailto:rhodium_uk@yahoo.co.uk">rhodium_uk@yahoo.co.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi Matthew,<br><br>Appreciate the feedback. I am just concerned that as this is for a call centre, when the number of calls per second (CPS) increases, the number of simultaneous calls decreases... so I can see a deployment with 1 to 3 CPS working with the setup you have described but with something close to around 15 CPS, then according to the SRND, that is a maximum of 255 calls (for a 3845). As we are decking out the ISDN router with 210 channels, then that only leaves headroom for 45 calls not including CPU overhead of SCCP, which led to my mistaken recollection of transcoders and ISDN GWs when it was transcoders and CUBEs.<br>
<br>I guess based on the setup I described, the more I think about it, the more I am inclined to make it "off box". Am I over riding financial judgement with caution too much?<br><br>Regards,<br><br>J<br><br><br>
--- On Wed, 2/10/10, Matthew Saskin <<a href="mailto:msaskin@gmail.com">msaskin@gmail.com</a>> wrote:<br><br>> From: Matthew Saskin <<a href="mailto:msaskin@gmail.com">msaskin@gmail.com</a>><br>
<div class="im">> Subject: Re: [cisco-voip] Transcoding/Conferencing on the same ISDN Gateway<br>> To: "Rhodium" <<a href="mailto:rhodium_uk@yahoo.co.uk">rhodium_uk@yahoo.co.uk</a>><br></div>> Cc: "Peter Slow" <<a href="mailto:peter.slow@gmail.com">peter.slow@gmail.com</a>>, <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> Date: Wednesday, February 10, 2010, 9:37 PM<br>
<div>
<div></div>
<div class="h5">> I regularly see single gateways handle<br>> all functions (PSTN termination, conferencing, transcoding)<br>> for sites of all sizes. I know of nothing [design-wise]<br>> preventing you from doing this. In fact, I can think of<br>
> some very large installations I've seen that were done<br>> by advanced services where 3845's were being used to<br>> terminate 10-12 PRI's plus handle a few hundred<br>> transcoding sessions.<br>
><br>><br>> Matthew Saskin<br>> <a href="mailto:msaskin@gmail.com">msaskin@gmail.com</a><br>> 203-253-9571<br>><br>> July 18, 2010 - 1500m swim (in the hudson), 40k bike, 10k<br>> run<br>> Please support the Leukemia & Lyphoma Society<br>
><br>> <a href="http://pages.teamintraining.org/nyc/nyctri10/msaskin" target="_blank">http://pages.teamintraining.org/nyc/nyctri10/msaskin</a><br>><br>><br>><br>> On Wed, Feb 10, 2010 at 4:24 PM,<br>> Rhodium <<a href="mailto:rhodium_uk@yahoo.co.uk">rhodium_uk@yahoo.co.uk</a>><br>
> wrote:<br>><br>> Hi Peter,<br>><br>> Thank you for your reply.<br>><br>> I dug out a report from Cisco Advanced Services that stated<br>> that CUBEs should only be used for SIP trunks and not for<br>
> transcoding/mtp. Knew I read something somewhere. Just not<br>> the details... :)<br>><br>><br>> So we are all definite that for an ISDN GW, we can use<br>> re-use the DSPs for transcoding in line with Cisco's<br>
> recommendations? I want to recommend getting a dedicated<br>> router for these functions but need to justify the cost so<br>> if there are no design recommendations, then I guess I can<br>> just put it all on one box.<br>
><br>><br>> Regards,<br>><br>> J<br>><br>><br>> --- On Wed, 2/10/10, Peter Slow <<a href="mailto:peter.slow@gmail.com">peter.slow@gmail.com</a>><br>> wrote:<br>><br>> > From: Peter Slow <<a href="mailto:peter.slow@gmail.com">peter.slow@gmail.com</a>><br>
><br>> > Subject: Re: [cisco-voip] Transcoding/Conferencing on<br>> the same ISDN Gateway<br>> > To: "Rhodium" <<a href="mailto:rhodium_uk@yahoo.co.uk">rhodium_uk@yahoo.co.uk</a>><br>> > Cc: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
><br>> > Date: Wednesday, February 10, 2010, 5:02 PM<br>><br>><br>><br>> > That is not necessarily correct. It<br>> > depends heavily on the type of<br>> > gateway you're talking about, and the number of<br>
> transcoding<br>> > or<br>> > conferencing sessions you might be needing.<br>><br>> ><br>> > -peter<br>> ><br>> > On Wed, Feb 10, 2010 at 7:24 AM, Rhodium <<a href="mailto:rhodium_uk@yahoo.co.uk">rhodium_uk@yahoo.co.uk</a>><br>
> > wrote:<br>> > > Hi Experts, :)<br>> > ><br>> > > I am sure I read somewhere in a design doc or the<br>> SRND<br>><br>> > that it is not advocated to put transcoding or<br>> conferencing<br>
> > resources on a voice gateway handling about 150<br>> calls.<br>> > ><br>> > > Am I recalling right or are the old brain cells<br>> > getting weaker with age.<br>><br>> > ><br>
> > > If that is correct, a link would be appreciated<br>> as I<br>> > can't find it.<br>> > ><br>> > > Regards,<br>> > ><br>> > > Jason<br>> > ><br>> > ><br>
> > ><br>> > ><br>><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>> > ><br>> ><br>><br>><br>><br>><br>
> _______________________________________________<br>> cisco-voip mailing list<br>> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> https://puck.nether..net/mailman/listinfo/cisco-voip<br>
><br>><br>><br>><br><br><br><br><br></div></div></blockquote></div><br>