Can not ping to public IP address on LAN2 - SIP Config 1

[ega218]

Setting up SIP configuration on IP500 R5.0.15.

However, before I can even try to setup the SIP with my provider, I can not ping the WAN port on LAN2. I think it it has to do with my IP Route.

I have an IP route with all 0's execept for the gateway where I have the gateway form my internet router gateway WAN IP address and also have destination as LAN2.

I do see litup status lights.

Don't know what else to do to be able to ping that port.

Any comments or suggestions is appreciated.

Thanks in advance.

 

[Bas1234]

Turn off the firewall on the WAN port.

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________

 

[ega218]

Bas1234 thank you for your reply.

I thought it was that and had already temporarily deleted all firewall profiles that were default when I installed R5.0

In the System-LAN2-LAN Settings tab I have select <none> for Firewall Profile. Then in the Network Topology tab I have selected "Unkown" for the Firewall/NAT Type.

So I don't know where else where I can turn off the firewall for the LAN2 port.

Let me know if I have missed something. Thanks.

 

[Bas1234]

You could give you PC the ip address of the IPOffice, then check if it replies on a ping. Also check the router/firewall (not the avaya one) if it blocks ICMP. Ping does not have a port.

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________

 

[Pepp77]

ega - on the ip route what is the address you have for the gateway - it sounds like you are using the public IP address of the firewall rather than the local IP address?

 

[IPOfficeIreland]

it might be easier if you post your ip settings and ip routes.

 

[AVAYAPro]

the ip office won't know how to get to the public IP without knowing where to go on its own LAN segment...

ACS - IP Office Implement
ACA - IP Telephony Implement
CCNA - Cisco Certified Network Associate
MCP - Microsoft Certified Professional

I like stars

 

[ega218]

I have tested the public IP Address on a laptop and was able to ping the IP address from the WAN. However, not able to do so when the line was moved to the WAN port of the IP500 unit.

My setup is as follows:

For the LAN1 I have all of the necessary information for the local area network and this has worked find for years. I also use it for remote VOIP phones with no problem. I am now trying to setup the LAN2 port for a WAN connection.

On the LAN2 Tab (used for WAN) in the SYSTEM section under the LAN Settings Tab I have the following:

IP Address: "Public IP Address" (which I will not list here for obvious reasons, but is pingable on my laptop)
IP Mask: 255.255.255.248
Primar Trans. IP Address: 0.0.0.0
Firewall Profile: <none>
Rip Mode: None
Enable NAT is "NOT" checked off
DHCP Mode is disabled

For Routes I have the following, among other internal routes needed for my remote VOIP phones which will not be necessary to list:

IP Address IP Mask Gateway Destination Metric
0.0.0.0 0.0.0.0 "LAN Firewall IP address" LAN1 0
0.0.0.0 0.0.0.0 "WAN Router IP Address" LAN2 0

I have not even started to figure out any possible problems with my SIP setup. I first need to make sure that the IP Office can ping the provider and the provider can ping the WAN IP Address for the IP Office. That's where I stand.

It just seems as if the LAN2 port is not being configured correctly. Is there any way to ping out from the IP Office?

Any comments is appreciated.

 

[amriddle01]

0.0.0.0 0.0.0.0 "LAN Firewall IP address" LAN1 0
0.0.0.0 0.0.0.0 "WAN Router IP Address" LAN2 0

those two routes are clashing, this will cause issues and may well be the cause of your current issue, make the LAN1 route more specific

ACS - IP Office Implement

"What the Crocodile Hat....was that?

 

[tlpeter]

Indeed, done it once myself


ACS IP Office or is it ACSS
ACA - Implement IP Telephony -- ACA - Design IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[ega218]

Thank you all for your input. Especially amriddle01.

That was the problem. I had that entry since my IP403 & 3.x days. After removing the LAN route, I was able to ping the WAN port. Surprisingly, I was also able to connect through my VPN using VOIP alot better as well. Not sure if that was a coincidence or not. However, it seems that that route could have been causing many routing problems for me in that past as well and I did not even know it.

I already have individual routes for all of our other locations.

Again, amriddle01 thank you very much.

 

[amriddle01]

No problems, we aim to please

ACS - IP Office Implement

"What the Crocodile Hat....was that?

 

[hairlessupportmonkey]

I need to have two routes, simple use specific routes for different destinations

192.168.41.0 /255.255.255.0 / 192.168.41.254 / LAN 1

82.xxx.xxx.101 / 255.255.255.240 / 82.xxx.xxx.100 / WAN1 (LAN2)