[cisco-voip] What is diff between Integrated Session Border Controller and Cisco Unified Border Element SP Edition

[GregW]

Mark,
 
Thank you so much. Looks like I may get the opportunity to gain some knowledge on this product at the carrier level.




GregW 
 
 
 

--- On Mon, 7/13/09, Mark Holloway <mh at markholloway.com> wrote:


From: Mark Holloway <mh at markholloway.com>
Subject: Re: [cisco-voip] What is diff between Integrated Session Border Controller and Cisco Unified Border Element SP Edition
To: gwenzit at yahoo.com
Cc: cisco-voip at puck.nether.net
Date: Monday, July 13, 2009, 3:46 PM



One main difference is CUBE is intended to function as a back-to-back user agent and manipulates SIP headers by re-writing them making it appear as if the SIP messages are originated from the router.  The integrated SBC of an ASR can function as a stateful SIP proxy which allows peering with multiple ASR's, multiple service providers, and higher session capacity.  The ASR also lets you create rules for things such as DoS attacks (H.323 or SIP excessive registration attempts) and demote the offending host.  The ASR has specific features built in for QoS accounting and billing as well.  


On Jul 13, 2009, at 10:43 AM, GregW wrote:






I know Service Provider edition is a simple ios upgrade...
 
This is on the new ASR 1000 series.
 
I know 1002 can not have redundant processors.
 
does anyone have core differences.
 
I have been on cisco.com a few hours this weekend and found that HA and ISSU are the main diff's between (high avail) and (in-service software ugrade) 
 
What does pay as you grow mean, is that you just purchase one size and your software licensing grows???
 
Thanks in Advance




GregW 
 
 _______________________________________________
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/20090713/93686c07/attachment.html>