SCN - kindly request some help 1

[raist3001]

Unable to get my SCN up and connected. Here is my current set up on 9.1:

SCN - LAN to WAN - routing via VPN
IPO A = 192.168.42.1
IPO B = 192.168.43.1

IPO A IP Office Line(SCN) with gateway address of IPO B
IPO B IP Office Line(SCN) with gateway address of IPO A

IP routes
IPO A Routes
192.168.43.0 / 255.255.255.0 / <Gateway IP>
0.0.0.0 / 0.0.0.0 / <Gateway IP>

IPO B Routes
192.168.42.0 / 255.255.255.0 / <Gateway IP>
0.0.0.0 / 0.0.0.0 / <Gateway IP>

In system Status for both Sites, Trunks are reporting as Out of Service.

Wierd thing is when I go to IP routes in System Status for Site A and try to ping the gateway of Site B, the ping fails with 100 percent packet loss.
I can ping the IPO in Site B from system status, Just not the gateway in Site B.
However, from the PC in Site A, I can ping both the GW and the IPO in Site B.

When I go to IP routes in System Status for Site B and try to ping the gateway of Site A, the ping is successful.
I can also ping the IPO in Site A from system status (Site B) and gateway in Site A.

Any thoughts on what I am missing?

Edit:
I have the SCN networking licenses installed at both sites

 

[Avalon100]

Do you have the SCN networking licenses?

 

[Avalon100]

Do you have the SCN networking license?

 

[raist3001]

My apologies for not listing the licenses.

I do have the SCN networking licenses installed at both sites.

 

[AACon]

Do you still have the default IP Address applied to the LAN2 interface? It's 192.168.43.1 by default, that would cause issues.

-Austin
I used to be an ACE. Now I'm just an Arse.

 

[raist3001]

Yes I do still have the default IP address applied to LAN 2 on both sites.
But without anything connected to LAN 2, and IP routes destinations to LAN 1, would this still cause issues?

 

[amriddle01]

Yes, it will not route as it's valid locally, you need to re-address something.

P.s this is not an Avaya specific issue, it's basic networking

 

[raist3001]

How is the IP office routing with 192.168.43.1 when there are no IP routes built to use this IP address, nor is this IP address being used in any subnet, nor is the LAN 2 connected to anything?

Basic Networking aside, my VPN is up and running. I have zero issues with connections over my VPN.

 

[amriddle01]

Because you have 43.1 assigned to a local interface, you are telling the system that everything 43.x is connected to that port, so any traffic for 43.x will just queue on that interface as the fact it's unplugged doesn't change the fact you have told the system to use it.

It isn't routing anywhere, it doesn't need to, as far as the system is concerned the problem is that the LAN port is unplugged.
If you don't believe us put both sides of your VPN on the same subnet range and see how well it works

 

[raist3001]

Oh, I see what you mean AMriddle. My fault for not displaying the proper IP addresses for the IPO's.

In order to not to expose the real IP's of the IPO's I unknowingly introduced an error into the very help I sought. This is why I could not understand the routing issues with LAN 2 since technically I did not have any.

My apologies folks, my sincerest apologies.

This is my true configuration

SCN - LAN to WAN - routing via VPN
IPO A = 192.168.0.9
IPO B = 192.168.3.30

IPO A IP Office Line(SCN) with gateway address of IPO B
IPO B IP Office Line(SCN) with gateway address of IPO A

IP routes
IPO A Routes
192.168.0.0 / 255.255.255.0 / <Gateway IP>
192.168.3.0 / 255.255.255.0 / <Gateway IP>
0.0.0.0 / 0.0.0.0 / <Gateway IP>

IPO B Routes
192.168.3.0 / 255.255.255.0 / <Gateway IP>
192.168.0.0 / 255.255.255.0 / <Gateway IP>
0.0.0.0 / 0.0.0.0 / <Gateway IP>

In system Status for both Sites, Trunks are reporting as Out of Service.

Wierd thing is when I go to IP routes in System Status for Site A and try to ping the gateway of Site B, the ping fails with 100 percent packet loss.
I can ping the IPO in Site B from system status, Just not the gateway in Site B.
However, from the PC in Site A, I can ping both the GW and the IPO in Site B.

When I go to IP routes in System Status for Site B and try to ping the gateway of Site A, the ping is successful.
I can also ping the IPO in Site A from system status (Site B) and gateway in Site A.

Any thoughts on what I am missing?

Edit:
I have the SCN networking licenses installed at both sites

 

[amriddle01]

To put it another way, as we are talking addresses here:

Imagine you live on number 7 Smith road, and I told you to take a parcel to Number 9 Smith Road, you would take it down the road, you wouldn't break out the Atlas and start looking for another Smith Road because you already know where it is

 

[amriddle01]

My above was posted without seeing your last.

But what about the other LAN ports? The system has 2, what address is assigned to the other port on each system
Also you do not need local routes, they aren't even checked, so on the 3.x system you can remove the 3.x route and on the 0.x system you can remove the 0.x route, they're pointless, for the reason I posted above

 

[raist3001]

LAN 1 for both sites is assigned with the proper Local LAN IP (not on 43.xxx)
Lan 2 for both sites is assigned with the default 192.168.43.1

 

[amriddle01]

Well if ping isn't working to the router, that's the issue, the network isn't functioning correctly, forget the IPO, sort that out, and check for address clashes while you're at it.

What is the gateway address? And have you chose the correct port in the IP Route?

P.S Posting IP's from an internal network is not a security risk, nobody can do anything with that information. It's only your external IP's you need to worry about

 

[raist3001]

Ping is only failing for Site A
Cannot Ping GW of Site B from Site A from System Status
Can ping IPO IP of Site B from Site A from System Status

Ping is successful for Site B
Can Ping GW of Site A from Site B from System Status
Can ping IPO IP of Site A from Site B from System Status

IPO IP of Site A is 192.168.0.9
Gateway of Site A is 192.168.0.20

IPO IP of Site B is 192.168.3.30
Gateway of Site B is 192.168.3.1

Site A
IP Office Line
Line number and outgoing Group ID is 99
Networking Level is set to SCN
Gateway address is set to 192.168.3.30 (Site B IPO) - I thought this would be the gateway of Site B but I am being told by our distributor (Jenne) that this is the IPO IP of Site B

Site B
IP Office Line
Line number and outgoing Group ID is 98
Networking Level is set to SCN
Gateway address is set to 192.168.0.9 (Site A IPO) - I thought this would be the gateway of Site A but I am being told by our distributor (Jenne) that this is the IPO IP of Site A

 

[amriddle01]

Jenne is correct, the SCN gateway is the other system, it's not an IP route.
You need to find out why it can't ping the gateway, something is wrong there.
Also are you sure the ping response is coming from the IP Office?

You have narrowed it down to being a network issue at this point. Also many VPN routers block ports, so even when all you're routing is spot on they still block it (especially Sonicwalls)

 

[raist3001]

Thanks for confirming the SCN gateway IP.

On Site A
In System Status/IP Networking/IP Routes
I am selecting PING
I select LAN1 as the source interface
I enter the gateway of site B - 192.168.3.1 and press OK
System Status returns with 3 packets sent and 3 packets lost.

From a PC on site A I can ping GW and IPO at site B just fine.

Site B is fine.

I have asked the IT person to open the following ports
1718-1720
49152-53246

Being that they do have sonicwalls in place these ports may be being blocked at Site B.

 

[amriddle01]

But the fact the router isn't replying to pings is nothing to do with the IPO, can't be.
Sonicwalls are an absolute pain, but I've found the biggest issue is the IT companies that use them don't actually know how they work to enough of a degree, yes they can set them up and get basic web and email etc working, but anything that requires more knowledge like voice and video links and they're clueless when it doesn't work

 

[raist3001]

Since the IPO at Site A does not respond to GW pings to Site B, assuming it is not the IPO, I would believe there are blocked ports on SonicWall at Site B.
Since the IPO at Site B does respond to GW pings to Site A, I would believe the proper ports are open on Site A SonicWall. Since I have not yet requested any ports open, this may be by accident.

 

[raist3001]

In System Status/Trunks/Line:99 or 98, the current state of the trunks show out of service.
Just want to confirm that this is because of the network issue and not something I missed in configuration.
Obviously for SIP trunks I need to put the SIP trunk line in service. I do not see such an option for the IP Office Line.

Site B can ping both the PBX and Gateway of Site A. Shouldn't this line (98) show in service at least? Or will it only show in service once both lines can communicate?