Port Forwarding on RV345 - can't open port despite configuring rules

[McGarry20949]

Desperate plea to help - I have spent weeks on and off trying to get remote access to my VOIP telephone system via my RV345 to no avail.

This is my problem

1) I have the RV345 Small Business router with the following settings under Port Forwarding:

and Service Management with required Ports (the Voip phone uses the Port in image using UDP):

and basic settings with UPnP enabled:

2) I have ddns service through no-ip which all appears to be working fine on the router

I had understood that these settings would allow me to access my internal Voip service via this Port but I haven't been able to. I know my VOIP system has blocked a few intruders with it's own firewall but these have not been through my efforts!! I would expect to be able to connect and the Voip firewall would stop me initially (but i'd see it). My objective is to access the admin screens of the Voip system remotely.

However, it doesn't seem that I am even opening up that port successfully as port checker websites say it's not available. Whereas they do say the remote access port is open (so I know it's possible and not a problem elsewhere in the network eg. ISP).

Anyone help?! I'm sure this is straightforward to someone who knows more than me (not hard)!

M

[balaji.bandi]

So if i understand your post correctly :

1. you have VOIP PBX running inside Lan network, User trying external to register to your LAN IP address

2. You portforwarding enabled,

above setup not working, here is the questions :

1. What you see the Logs on the RV device, do you see the Logs coming in ?

2. what kind of PBX is this, do you see any Logs on PBX that request reached Server ?

3. is the PBX working Locally in the same LAN and confirmed PBX working as expected, before we look externally ?

4. not sure what kind of Service added to your IPBPX and IPPBx_External ( what ports ?)

here is the Guide to help you., ( for testing, try all Service/ External and internal test confirm atlease working as expected) - list like allowing all traffic.

https://www.cisco.com/c/en/us/support/docs/smb/routers/cisco-rv-series-small-business-routers/smb5818-configure-port-forwarding-port-triggering-nat-on-rv34x-serie.html

there is also link down in the same document for 1 to 1 NAT in case if you have dedicated Public IP.

[McGarry20949]

Hi BB,

1. you have VOIP PBX running inside Lan network, User trying external to register to your LAN IP address - YES

2. You portforwarding enabled - TRYING TO GET IT WORKING YES

1. What you see the Logs on the RV device, do you see the Logs coming in ?

I am getting a whole load of logs like these in the RV (the login failure may have been an attach):

2020-05-09T22:08:10-04:00 <error>PnP: [9293]: pnp.infra.network.HTTPConnClient ERROR HELLO failed
2020-05-09T22:08:10-04:00 <warning>PnP: [9293]: pnp.discovery.mechanisms.dns_discovery WARNING Attempting HTTPS DNS Discovery without NTP sync
2020-05-09T22:08:10-04:00 <error>PnP: Last message '[9293]: pnp.infra.ne' repeated 2 times, supressed by syslog-ng on router4470FF
2020-05-09T22:06:55-04:00 <error>PnP: [9293]: pnp.infra.network.HTTPConnClient ERROR HELLO failed
2020-05-09T22:06:54-04:00 <warning>PnP: [9293]: pnp.discovery.mechanisms.dns_discovery WARNING Attempting HTTPS DNS Discovery without NTP sync
2020-05-09T22:06:54-04:00 <error>PnP: Last message '[9293]: pnp.infra.ne' repeated 2 times, supressed by syslog-ng on router4470FF
2020-05-09T22:05:39-04:00 <error>PnP: [9293]: pnp.infra.network.HTTPConnClient ERROR HELLO failed
2020-05-09T22:05:39-04:00 <warning>PnP: [9293]: pnp.discovery.mechanisms.dns_discovery WARNING Attempting HTTPS DNS Discovery without NTP sync
2020-05-09T22:05:39-04:00 <error>PnP: Last message '[9293]: pnp.infra.ne' repeated 2 times, supressed by syslog-ng on router4470FF
2020-05-09T22:04:19-04:00 <error>PnP: [9293]: pnp.infra.network.HTTPConnClient ERROR HELLO failed
2020-05-09T22:04:19-04:00 <warning>PnP: [9293]: pnp.discovery.mechanisms.dns_discovery WARNING Attempting HTTPS DNS Discovery without NTP sync
2020-05-09T22:04:19-04:00 <error>PnP: Last message '[9293]: pnp.infra.ne' repeated 2 times, supressed by syslog-ng on router4470FF
2020-05-09T22:04:09-04:00 <error>jsonrpc: User cisco login fail from 192.168.236.10

The time has been set correctly using the default cisco NTP servers.

2. what kind of PBX is this, do you see any Logs on PBX that request reached Server ?

XBlue QB system. Yes, the firewall on the PBX is detecting the odd intruder and at one point it did detect my login and rejected me (but it hasn't detected me in a while now, I must have been lucky at one point)

3. is the PBX working Locally in the same LAN and confirmed PBX working as expected, before we look externally ?

PBX is working perfectly internally

4. not sure what kind of Service added to your IPBPX and IPPBx_External ( what ports ?)

The PBX vendor said they use 5060 port (- 12000). But this is where I assume my mistake is.

Thank you for link, I will take a look again. This was my first avenue but it didn't help me. 

[balaji.bandi]

"I am getting a whole load of logs like these in the RV (the login failure may have been an attach):"

For now this is not related to your issue, this need to address cisco TAC some other issue.

As i have suggested before try 2 Option let us know.

1. Allow All Service and check is this working.

2. Try to disable any IPS/ IDS or Advanced FW features and test and let us know.

Last and least - not really suggest, reboot the device and test it

[JosephGolobic96737]

I had a similar problem with same router (your note actually let to the solution). I have a VOIP home service and was convinced by the phone provider to connect the phone set to Internet modem and the use the passthru to connect to router. I had tried everything including standing on my head and it just would not work.

Based on what you said I connected the modem to Router and connected VOIP phone to a router port and 'magic' it works. 

Not sure if this does anything for you  but it may point you ina direction that will lead to the fix.