Connecting remote phones over a VPN to an Avaya IP Office 500 V2 3

[krajcd5]

Everyone,

I am trying to get a figure out how to get the IP Route for my IP Office set up. I was reading the following post thread940-1453186 and I am not sure why this is not working.

I have a VPN Tunnel that works. From my corporate network I can ping say a printer on my remote network and get a response. From my remote network I can ping say a printer on the corp network and get a response. If I launch System Status and go into IP Networking->IP Routes and use the ping button and try to ping something on the corporate network, I get a response. If I try to ping something on the remote network I get no response.

Corporate network:
IP Addresses: 192.168.1.100 - 192.168.1.200
Subnet: 255.255.255.0
Gateway: 192.168.1.1 - the gateway is also the VPN termination point
IP Address of IP Office: 192.168.1.4

Remote Office
IP Addresses: 192.168.10.100 - 192.168.10.200
Subnet: 255.255.255.0
Gateway: 192.168.10.1 - the gateway is also the VPN termination point

Here is my IP Route information;
IP Address: 192.168.10.0
IP Mask: 255.255.255.0
Gateway IP: 192.168.1.1
Destination: LAN1

Once again with this route in place I am unable to use the ping from IP Office and get any response back from something on the remote network.

Can anyone help and let me know what it is I am doing wrong?

Thanks in advance.
Dan

 

[amriddle01]

I asked if it can ping the local gateway, if it can but not the remote then it's either 1) The other IPO LAN port is DHCP client and so routes are ignored or if that's not the case then 2) The gateway is not passing the IPOs data through....that's it (assuming you do indeed have no other routes entered or IP address conflicts going on)

 

[krajcd5]

amriddle01,

Yes the IPO can ping the local gateway, picture below. Also below is my ip route.

I want to stop and thank everyone for their help. I am new to this Avaya system and just trying to get it to work.

I an earlier message I asked about System Status not updating itself. Here is what is in System Status. I have removed all of those routes, as you can see by the photo below. I have not rebooted the system since though.

 

[amriddle01]

Your LAN2 cannot be in the same range as the remote gateway, obviously all packets for the remote network are classed as local to LAN2, that's never going to work, change that interface to a new address range and reboot

 

[krajcd5]

Before I reboot the phone system I just want to make sure I have my route correct.

I only need the one route:
IP Address: 192.168.10.0
IP Mask: 255.255.255.0
Gateway IP address: 192.168.1.1
Destination: LAN1

That is all that should be configured in the IP Route and that is all that should be showing in the System Status, correct?

 

[amriddle01]

That's all you need and the route is correct, system status always shows the directly connected networks, that's how I spotted your error

 

[krajcd5]

I will have to wait to reboot the system until later tonight and I will post updates after the system has been rebooted.

 

[amriddle01]

No need, if everything is as you say it will work

 

[amriddle01]

And this error fell into the "address conflicts" caveat I posted

 

[krajcd5]

Everyone,

I just rebooted the system and a couple of odd things appeared and hopefully what I am about to ask is correct and someone can tell me how to fix it.

When I rebooted they system the only route in the IP Route list was the following:
IP Address: 192.168.10.0
IP Mask: 255.255.255.0
Gateway IP address: 192.168.1.1
Destination: LAN1

After the reboot that route is in there but also the following:
IP Address: 192.168.99.0
IP Mask: 255.255.255.0
Gateway IP address: 0.0.0.0
Destination: RemoteManager

Not sure what that route is there for but if there is no issue I am okay with it. Now here is the real question. Under System Status->IP Networking->IP Routes there are 3 routes listed. The big issue is what is listed as the Route Priority which is Prefer Static. Is there a way that the route priority can be changed to the one I want. Am I safe in assuming this becomes the default route that the system uses and if so would this be what is causing my problem? The screen shot of what I am currently seeing in System Status is below.

Once again I truly appreciate all the help.

 

[amriddle01]

If you want free advice, take it. I told you to change the address/range of LAN2, you haven't. It's still causing a conflict, fix that and you're OK, ignore me and it'll never work. Do you think I'm making it up or something ?

 

[derfloh]

The 192.168.99.0 route is normal and OK.

 

[krajcd5]

amriddle01,

I do appreciate your help. I was told by someone else to enter the information into LAN2 and I thought that they have removed the settings. I have removed all of the settings for LAN2 but after saving and rebooting the route is still listed. I will have wait until Monday to make sure the cable is still not attached. I am rebooting the system by doing the following from Manager File->Advanced->Reboot. Is there some other way that this system needs to be restarted?

 

[derfloh]

Take some time and read the previous post again and concentrated. Everything you have to know is described.

Be aware that modern telephony is far more than only create a direct wired connection between the phone system and it's endpoints. Basic network knowledge became more and more a very important requirement for a phone engineer.

 

[amriddle01]

You need to give it an actual address, forget what's shown in SSA, put LAN2 on 192.168.43.1, make sure your 192.168.10.0 route is in and it will work, this is a networking issue, nothing to do with the IP Office.

 

[krajcd5]

Everyone,

First let me say Thank you to everyone for your help.

I set LAN2 as was described by amriddle01 and rebooted and now I can say the IPO can ping something on the remote network and get a response and vice versa.

Thank you all for the help. You succeeded where others did not. I will not be able to test if an actually phone works until Monday but I am pretty sure it will.

Once again my sincerest thanks to everyone.

Dan

 

[derfloh]

You succeeded where others did not.

There have been more people trying to find out why it not works and haven't be able? Unbelievable with such an obvious issue...

 

[intrigrant]

He was on the Avaya forum as well were he was told to get the answer here.
TBH I think he should be a bit ashamed making such a basic and stupid fault.