<div dir="ltr">I agree with you that LUA scripting is much more powerful but I use it as a last resort just do to supportability. Just because I know how to do something fancy in a LUA script doesn't mean the next guy is going to be able to maintain/troubleshoot my script whereas sip-profiles on the CUBE are much simpler and have full TAC support in case anything goes wrong.</div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Aug 13, 2014 at 12:27 PM, Anthony Holloway <span dir="ltr"><<a href="mailto:avholloway+cisco-voip@gmail.com" target="_blank">avholloway+cisco-voip@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Not to stir the pot, but it's currently my opinion that SIP normalization on CUCM via Lua scripting is more powerful than SIP profiles in IOS. That's not to say that I recommend a sans CUBE design, because I don't, but I am saying that CUBE is not a preferred solution because of its SIP normalization capabilities. Which are pretty basic, when compared to the full control, offered by Lua scripting in CUCM.<div>
<br></div><div>Does anyone think otherwise? I'm open to being corrected here. Maybe it's my misunderstanding of SIP normalization in IOS that makes me think this way. I do have real world experience solving SIP issues with both IOS and CUCM, albeit a small amount of experience.</div>
<div><br></div><div>And on the main topic, yes it would work with CUBE, but CUBE provides you with an extra layer of control, security, and simplifies your design. If you're having CUCM insert MTPs anyway (think CTI and RFC2833 incompatibilities and DO to EO conversions) might as well use that same MTP router as CUBE and have CUBE <a href="http://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-border-element/115018-configure-cube-lti.html" target="_blank">locally control the media resources</a> on itself.</div>
</div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Aug 13, 2014 at 8:59 AM, Ryan Ratliff (rratliff) <span dir="ltr"><<a href="mailto:rratliff@cisco.com" target="_blank">rratliff@cisco.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">
+1
<div><br>
</div>
<div>The IOS features to manipulate SIP headers are very powerful and will let you workaround any interworking problems between the SBC and UCM quite easily.</div><span><font color="#888888">
</font></span><div><span><font color="#888888"><br>
<div>-Ryan </div></font></span><div><div>
<br>
<div>
<div>On Aug 12, 2014, at 10:29 PM, Brian Meade <<a href="mailto:bmeade90@vt.edu" target="_blank">bmeade90@vt.edu</a>> wrote:</div>
<br>
<div>
<div dir="ltr">Robert,
<div><br>
</div>
<div>You can technically get away with just using the provider's SBC but be prepared for a lot of going back and forth with them to solve any interop issues. I like having my own SBC/CUBE so that I can modify whatever I want and have more control over the
setup.</div>
<div><br>
</div>
<div>It's also nice to be able to completely hide your internal network behind the CUBE.</div>
<div><br>
</div>
<div>Brian</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Tue, Aug 12, 2014 at 7:41 PM, Robert Blayzor <span dir="ltr">
<<a href="mailto:rblayzor.bulk@inoc.net" target="_blank">rblayzor.bulk@inoc.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I am planning on replacing an again CallManager deployment with SCCP phones with a new CUCM 10.x and SIP phones.<br>
<br>
Our service provider can provide all of our trunking and PSTN connectivity via a direct SIP trunk, so I no longer need a PSTN gateway or PRI card, etc. (or at least I should not).<br>
<br>
We will be peering SIP from the CUCM to our providers SBC, so the question begs to ask on our side is a CUBE absolutely required to make this work? Pros/Cons? I'd rather not have to add a CUBE in if I don't have to.<br>
<br>
Since the phones are native SIP as is the CallManager I'm trying to understand why a CUBE is required? (or is it not?)<br>
<br>
TIA<br>
<br>
-Robert<br>
<br>
<br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">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>
</blockquote>
</div>
<br>
</div>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">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>
</div>
</div>
<br>
</div></div></div>
</div>
<br>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">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></blockquote></div><br></div>
</div></div></blockquote></div><br></div>