Thanks for the no-nonsense answers Anthony, you have been a big help! On Wed, Mar 25, 2015 at 9:58 PM, Anthony Holloway < [email protected]> wrote:
> 1) RTU, nothing to add to the router (just like SRST) > 2) The 100 sessions is for any supported codec. If Cisco says a 2911 can > do 100 sessions, they mean it. It's not: "well, it's 100, but only if > you're using g729" > > Check the data sheet for CUBE session limits per platform: > > > http://www.cisco.com/c/en/us/products/collateral/unified-communications/unified-border-element/data-sheet-c78-729692.html > > Now, if you're wondering about layering on other services: routing > protocol, http server, tufts server, PRI, MGCP, H323, transcoding, > Firewall, VPN, etc, etc, etc, then that's a different story and I'm not > sure if Cisco will provide you with a tool that will evaluate your router > to see if it's CUBE-able or not. I would think that anything above 200 > sessions is pretty significant and I would lobby for a dedicated device. > You can see that this question is address here, but with no specifics: > > > https://supportforums.cisco.com/document/69976/frequently-asked-questions-cisco-unified-border-element-cube#Q11:_Does_CUBE_have_to_be_run_on_a_dedicated_devicerouter > > On Wed, Mar 25, 2015 at 8:09 PM Barry Howser <[email protected]> > wrote: > >> Thanks, that helps! >> >> So when it comes to calculating number of SIP sessions that can be >> supported ... lets use your example of100 sessions; >> >> 1.) So if I bought 100 sessions, that is just an RTU right? Or is it an >> actual license I have to add to the router? >> 2.) Say I'm doing all g.711ulaw, how I am verifying that my ISR can >> physically support that? Is there a magic Cisco calculator like there is >> for DSP? >> >> thanks, >> >> -LostInTheWeeds >> >> On Wed, Mar 25, 2015 at 6:56 PM, Anthony Holloway < >> [email protected]> wrote: >> >>> You don't need the mod border-element command in order for a router to >>> have CUBE turned on. Simply having the UC license and allowing voip to >>> voip connections gets you CUBE functionality. The mode border-element >>> command does have it's purposes, for example CUBE HA, and Local Transcoding >>> Interface (LTI). >>> >>> 1) Honor based licensing, and you can police it yourself with commands >>> on your dial peers (it's part of the CAC functions of CUBE) >>> 2) First you start with hardware, and then you look at licensing. So, >>> if my router can do 100 Sessions, but I only bought 50, then the limit is >>> 50. >>> 3) Correct. E.g., A single employee makes a single PSTN call from their >>> single IP Phone. That's two VoIP legs on the CUBE, but only one CUBE >>> session. >>> >>> >>> >>> On Wed, Mar 25, 2015 at 4:54 PM Barry Howser <[email protected]> >>> wrote: >>> >>>> Trying to wrap my head around how cube manages sip sessions. >>>> >>>> So when a router is in cube mode (mode border-element); >>>> >>>> 1.) How are sessions policed? Is it an honor system or is there a >>>> functional restriction? >>>> 2.) What determines how many sessions are supported, licensing or >>>> resources or both? >>>> 3.) A single connected call represents one session, correct? >>>> >>>> >>>> thanks. >>>> _______________________________________________ >>>> 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
