[cisco-voip] CUCM 9+ and SIP trunk provider w/o CUBE

[Ryan Ratliff (rratliff)]

+1

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.

-Ryan

On Aug 12, 2014, at 10:29 PM, Brian Meade <bmeade90 at vt.edu<mailto:bmeade90 at vt.edu>> wrote:

Robert,

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.

It's also nice to be able to completely hide your internal network behind the CUBE.

Brian


On Tue, Aug 12, 2014 at 7:41 PM, Robert Blayzor <rblayzor.bulk at inoc.net<mailto:rblayzor.bulk at inoc.net>> wrote:
I am planning on replacing an again CallManager deployment with SCCP phones with a new CUCM 10.x and SIP phones.

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).

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.

Since the phones are native SIP as is the CallManager I'm trying to understand why a CUBE is required? (or is it not?)

TIA

-Robert



_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto: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/20140813/0bffbc70/attachment.html>