Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

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

Status
Not open for further replies.

krajcd5

IS-IT--Management
Oct 8, 2015
15
US
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

 
Your IP route looks OK, are there any other IP Routes programmed?
Give your PC a fixed IP Address and use the IP Office as the default gateway then do a traceroute to see where it breaks.
 
Make sure you also have the reverse routes in place.
 
Everyone,

Thanks for the information. I know have the following routes entered:
IP Address: 192.168.10.0
IP Mask: 255.255.255.0
Gateway IP: 192.168.1.1
Destination: LAN1

IP Address: 192.168.1.0
IP Mask: 255.255.255.0
Gateway IP: 192.168.10.1
Destination: LAN1

When I open up System Status it is still showing all of my old route information. Is there a way to force that to update. After I made the route changes, I saved and merged and then relogged into System Status but it has not updated and I am still not getting a ping response. I have not rebooted the system because the office is open.
 
The second route is not possible since your IPO is not in the same subnet like 192.168.10.1

I'm east that the remot site phone must use their local gateway (192.168.10.1) to reach the IPO. I guess that is the cause.
 
derfloh,

Thanks for the update. What would the reverse route be then?

Dan
 
Your IPO routes at each location should point to the gateway for that network, then the gateway should have a route to the next hop, then your two VPN endpoints should have a route between each other.

The IPO at 192.168.1.x should have
192.168.1.0
255.255.255.0
192.168.1.1

as it's route for the interface connected to that network (LAN1 or LAN2???)

The remote should be

192.168.10.0
255.255.255.0
192.168.10.1

as it's route for the interface connected to that network (LAN1 or LAN2???)


Just curious, what are the devices doing the VPN? Do you have control/access to them?
 
I am using Kerio Control firewalls for the VPN Tunnel. I do have control over them. The tunnel appears to be working correctly because I can access devices on each of the networks from either location. Just cannot access the Avaya IP office. I will add the 2 routes now.
 
nnaarnn,

Thanks for the information. I just re-read it again. I only have 1 instance of IPO installed, just at the corporate network. LAN1 is what is connected to that network at corporate. Do I need to configure LAN2 with IP information for the 192.168.10.x network?
 
So, to clarify, there's only 1 IPO, which is on the 192.168.1.0 network and you have phones on the 192.168.10.0 network that you need to connect to that IPO?


If yes, then you will need to manually enter call server, http, https addresses in your phone, or have your DHCP server provide those details under option 242 or 176 depending on your phone model.

What phone model are you using at the remote site?
 
Your IP Office routing is correct assuming that is the correct gateway and you aren't in fact using LAN2/WAN, your issue lies in the far end gateway or the fact you have multiple gateways at the far end and DHCP assigns the wrong one for communication etc. Forget the IPO Use other devices to ping between then you'll know the IPO is fine :)

 
nnaarnn,

Yes that is what I am trying to do. I have only the IPO on the corp network at 192.168.1x and I need phones on the remote network 192.168.10.x to connect to the IPO. Here is what I set up on the remote phone. This did not work. The phone would just get stuck in Discovering xxx.xxx.xxx.xxx which was my IPO office.

This was manually configured
Remote site phone: Avaya 1608
IP Address - 192.168.10.201
Subnet: 255.255.255.0
FileServ: 192.168.10.112 - local computer with just the upgrade images installed on a web server
CallServer: 192.168.1.4

The phone boots up but just gets hung at Discovery 192.168.1.4. This is what made me think that even though I am able to connect to other devices on both networks, something with IPO set up was incorrect.

 
amriddle01,

Thanks for the information. This is where I am getting confused. I can ping between both networks and get a response. I can sit in my corp office and screen share a computer on the remote office connection via it local IP address. The only thing that is not responding is the IP Office from a ping from the remote network to the IPO. It responds as it should from the corp network.

Dan
 
What happens when you ping the IPO from a PC on that network?
 
Can the IPO ping the router? Also here is a gotcha, if the other system LAN port is a DHCP client then IP Routes are ignored and the system always uses the gateway received via DHCP :)

 
If I ping the IPO from the remote office I get no response. I send 4 packets and lose 4 packets. If I ping a printer on the same network as the IPO I do get a response. I send 4 packets to 192.168.1.142 and I get 4 back
 
BTW, this is not an IPO or handset issue, it's your config and/or network at fault but we are geeky so help anyway :)

 
Then I would say that 192.168.1.1 us not the correct gateway. Or you have shine blocking firewall rules.
 
amriddle01,

The IPO cannot ping the remote gateway at 192.168.10.1. A computer on the same network as my IPO can ping the gateway. Image of the ping and trace route to a printer on the remote network is attached.

ping2.png
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top