[cisco-voip] One CM and several identical networks

[Andrius Kislas]

Hi,

my situation was that client _already_ has some IP addresses and do not
want to change them. And it so happens that one CM has to reach two
networks that actually has same address space.

If we cannot put secondary IP address, we still virtually can make this
secondary and so on IP addresses using NAT with SCCP/H323 fixup as
offered Ryan.

Andrius

ash AD wrote:
> Andrius,
> 
> I have to echo what Ryan wrote. We tried to implement the second
> interface on the MCS server and killed our CCM (CCM 3.3(4)) in Iraq. Is
> there a reason you couldn't use more private address space i.e..:
>  
> Site 1 Voice Net/VLAN: 192.168.0.0/24
> Site 2 Voice Net/VLAN: 192.168.1.0/24
> Site 3 Voice Net/VLAN: 192.168.2.0/24
>  
> I know this is much like a private VLAN approach but, it seems simple
> and heck, the IPs are free.
>  
> V/R,
> PETER CASANAVE
> WAN / VoIP Network Engineer
> U.S. Army
> 
> */Ryan Ratliff <rratliff at cisco.com>/* wrote:
> 
>     Your CM server should never have multiple IP addresses. I've
>     certainly no experience deploying IPT but it sounds to me like NAT
>     w! ith skinny/H.323 fixup is what you need.
> 
>     Did I mention to absolutely NEVER put multiple IP addresses on your
>     CM? Well, at least if you want it to work...
> 
>     -Ryan
> 
>     On Dec 5, 2005, at 1:38 AM, Andrius Kislas wrote:
> 
>     Hello,
> 
>     I have a question about CallManager working as a SCCP signaling provider
>     for several networks using VPN over Internet. It so happens that two
>     networks are with the same IP adresses (192.168.0.x/24). What is the
>     "best practice" in such situation for CM to distinguish these networks?
>     I thought about two solutions:
> 
>     1) Put a secondary IP address on CM for the second identical network.
>     Then the make policy routing on a router, so that packets FROM one CM
>     address goes to the first network, and packets FROM the second address
>     goes to the second network.
> 
>     2) Configure NAT on VPN tunnels, so that packets from first network
>     reaches CM as one IP address and packets from second networks reaches CM
>     w! ith second address.
> 
>     I haven't tried neither of these solutions. Maybe there is more
>     intelligent way of solving the problem?
> 
>     Andrius
>     _______________________________________________
>     cisco-voip mailing list
>     cisco-voip at puck.nether.net
>     https://puck.nether.net/mailman/listinfo/cisco-voip
> 
>     _______________________________________________
>     cisco-voip mailing list
>     cisco-voip at puck.nether.net
>     https://puck.nether.net/mailman/listinfo/cisco-voip
> 
> 
> ------------------------------------------------------------------------
> *Yahoo! Personals*
> Skip the bars and set-ups and start using Yahoo! Personals for free
> <http://us.rd.yahoo.com/evt=36107/*http://personals.yahoo.com/us/reg/free7days
>>
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip