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

John Bittenbender kisanth88 at gmail.com
Sun Feb 20 19:08:15 EST 2005


If you are NAT'ing and using SIP (or even MGCP) your NAT device will
need special SIP implementation because of the IP messages in the SIP
datagram (SDP) not just the IP header. Watch for that.

JB

On Sun, 20 Feb 2005 14:04:41 -0800 (PST), Yasser Aly
<yaseraly00 at yahoo.com> wrote:
> Davey,
>
>  For your customers to reach your call manager they will need to be terminated at a common CE. As they all pass through the same common CE then their address space will need to be different and overlapping should be removed. Thinking for other alternatives, maybe Natting can solve this problem for you.
>
> Yasser
>
> 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/
> _______________________________________________
> 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/
>


More information about the cisco-nsp mailing list