[c-nsp] MPLS VPNS and access to shared network resource

[Jack Parks]

We have used a new class/type of device called a session border
controller.  It usually operates as a back-to-back user agent (BBUA)
and provides topology hiding and NATing for realtime protocols.  A
Cisco PIX has SIP and H323 fix-up which might be all you need to bring
your customers into a common call manager.  Many of today's firewalls
can act as Application Layer Gateways (ALG) but their performance is
lack luster.

I think you need:
1) a common Voice VPN
2) an ALG (or firewall) to perform Topology Hiding and NAT.

We have used PIX for low performance applications and ACME Packet
Net-SD for a large deployment.

Just google for "session border controller"  and you will get some
good reading material.


On Mon, 21 Feb 2005 10:22:50 +1300, Davey Goode <dg at phoenixfreight.co.nz> wrote:
> 
> 
> Hi all
> 
> I have a situation where we have multiple customer MPLS VPN`s all
> needing to access a core Cisco Call manager in our core. The call
> manager cluster needs to talk back to the customers ISR running SRST,
> but we have multiple customers with the same network addresses. Has
> anyone done anything like this before and what were the pitfalls to
> watch out for ????
> 
> Cheers
> 
> Davey
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>