SCN using NAT to one site

[BMB1475]

Hello Community, I have a question and please be aware that I haven’t done this in some time so if it’s a dumb question I apologize.
I have two IPO IP500V2 systems 7.0.23 on both. They were connected on a single network using a dedicated PTP circuit.
Site A has the control unit (192.168.0.250) and VMPro (192.168.0.253) and site B just a control unit (192.168.0.57)
We recently acquired this setup and had to build new network on site A and bring their PC's and Server onto our domain. Phase one of two phases.
Doing this lead to changing the IP addresses of site A's control unit and VMPro as moving the desktops to the new domain cause soft console to stop working and NAT didn’t work with Soft Console. So Site A changed control unit to (10.39.87.100) and VMPro to (10.39.87.101) but site B is still on the old network segment with a (192.168.0.57) address. I changed the IP trunk target IP address at site A to a NAT IP (10.39.80.252) in order to route the request to the old network segment and get to the IPO at site B via an uplink from our new network and we left the old IP in the IP trunk of site B then modified the route to send the request to the new network and new IPO control unit IP address.
I can ping site B from the control unit at site A and vise versa but SCN is down at both sites. I didn’t know if trying to connect like this even works but since I didn’t have the new network in place at site B I figured I would give it a try.
Please note, I did not program the network side of this, I just told them what I needed to do and what ports I needed open.
When in monitor I don’t see any Tx or Rx for AVRIP.
Can SCN work like this?


Brian M Battagliola

http://www.chsli.org

 

[Gunnaro]

Sounds like one or more of the required ports are blocked, or the IP routing is not fully functional.

If Site A has a free LAN port you could make that 192.168.0.250 and connect directly to the old PTP.

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

 

[BMB1475]

Thank you for the reply. I can't remove the point to point at this time as it is still in use for data connectivity for site B to access serves still on the old network at site A. I had my network team even remove the ACL on my new VLAN to test and I still couldn't get SCN up.

 

[janni78]

Can you NAT H.323 trunk? It might be that you need to have the external IP on you IPO interface.

At least H.323 phones showed their internal IP during H.323 register so it wouldn't work through NAT unless you set them as Remote Extensions.

"Trying is the first step to failure..." - Homer

 

[Gunnaro]

Not that I've tried, but I think Janni is right.

My point was:
Establish a physical connection to the old network from the IPO LAN2 port and set it to 192.168.0.250.
Then put back the old destination on the H323 trunk at Site B, and it should work again.

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

 

[mattKnight]

NAT and Media generally don't play nice.... (becaus the media streams that are setup don't contain the correct ie.e natted ip addresses)

I'm assuming the PTP link is a layer 2 thing? if so, can you create the site B address range as a separate VLAN at site B and route that way.

Making Site B and Site A distinct network ranges is a better idea from a network Point of view anyway. In this case it woudl solve your problem!

Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

 

[BMB1475]

So, i am currently doing some of this real time,I have tried the WAN port or LAN 2 port option:
1. I set the LAN 2 port to the systems original IP address of 192.168.0.250
2. I set the target IP of the IP Trunk at Site A to the IP of the control unit at Site B of 192.168.0.57
3. I changed an IP route in the system for requests to 192.168.0.0/24 Gateway 192.168.0.1 to LAN 2
4. I plugged the systems LAN 2 port back into the old network.
5. I rebooted the system.
I run a ping on the IP trunk in System Status and the pings are failing....

What

 

[Gunnaro]

Did you changed Site B IP Trunk gateway back to 192.168.0.250 as well?

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

 

[mattKnight]

I'm assuming the PTP link is a layer 2 thing...

You have the same IP range at both sites 192.168.0.x Is this correct or a typo?


Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

 

[BMB1475]

That is correct. The old setup was a flat network and the system at both sites A & B were on the same subnet. I think we have found and issue on the physical connectivity on the old network. If I resolve then I think the wan port option should work.

 

[BMB1475]

Hello all. First I would like to thank you all for jumping in here with you input. I am happy to report that I was able to utilize the WAN port into the old network in order to get the site to site SCN up and working. We ran a direct line into the old network switch into the WAN port and as it turns out that from the network there was a NAT in place for the traffic from site B to site A. Once I had this NAT to the old phone system IP reoved the connectivity came right up and SCN came up as well.

 

[Gunnaro]

You're welcome

Did you check that VMPro is accessible from Site B too?

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam