[cisco-voip] sip & cube question

[Barry Howser]

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 <
avholloway+cisco-voip at gmail.com> 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 <bhowser5050 at gmail.com>
> 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
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150325/79e697f6/attachment.html>