<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'>I've always thought of the AS5000 as service provider type gateways, independent of call control. If the cost of the 3900 is an issue, you can consider the 2900 series. As long as the total call volume can handle things, then you're good to go. The licensing can get tricky, but if you read the datasheets it can help.<br><br>How are you handling conference calling and trans-coding on your campus? Not sure if the AS5000 can do stuff like this.<span><br><br><br><span name="x"></span>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>Cooking with unix is easy. You just sed it and forget it. <br> - LFJ (with apologies to Mr. Popeil)<br><span name="x"></span><br></span><br><hr id="zwchr"><b>From: </b>"Adam Pawlowski" <ajp26@buffalo.edu><br><b>To: </b>cisco-voip@puck.nether.net<br><b>Sent: </b>Thursday, August 2, 2012 10:35:55 AM<br><b>Subject: </b>[cisco-voip] Cisco AS5000 vs ISR3900<br><br><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--><div class="WordSection1"><p class="MsoNormal"><font face="Calibri" size="2"><span style="font-size:11.0pt">I’m looking at some products to try and replace our 6509s and CMMs, which will eventually be EoS/EoL. The notification recommends the ISR series of devices, with PVDMs and VWICs. Since our goal is to eventually operate a CUBE, and transition to SIP trunking, with potential for fallback to a couple of PRIs, this platform would appear capable. Unfortunately, it looks like it also can do “a bunch of other stuff”, which would imply that it is expensive, and licensing will be involved for many of the features of the device.</span></font></p><p class="MsoNormal"><font face="Calibri" size="2"><span style="font-size:11.0pt"> </span></font></p><p class="MsoNormal"><font face="Calibri" size="2"><span style="font-size:11.0pt">The AS5350XM seems like it would do the same thing? The session count is listed at 800 sessions each for CUBE, and it’s a platform license, which would mean that should we configure 3 of these at unique sites, where we have 6-8 PRIs now, that we would be able to more-than dump the entire call capacity to one of these units in case of failure, with room to spare.</span></font></p><p class="MsoNormal"><font face="Calibri" size="2"><span style="font-size:11.0pt"> </span></font></p><p class="MsoNormal"><font face="Calibri" size="2"><span style="font-size:11.0pt">It doesn’t appear it does ISDN backhaul to CCM, not that it was designed to, so it would have to be configured with a SIP trunk to the UCM, is that right?</span></font></p><p class="MsoNormal"><font face="Calibri" size="2"><span style="font-size:11.0pt"> </span></font></p><p class="MsoNormal"><font face="Calibri" size="2"><span style="font-size:11.0pt">Any other comments? Would this put us on the pain train?</span></font></p></div><br>_______________________________________________<br>cisco-voip mailing list<br>cisco-voip@puck.nether.net<br>https://puck.nether.net/mailman/listinfo/cisco-voip<br></div></body></html>