The router doesn't block any outgoing traffic unless there is any firewall rules are configured to do so. Have you setup any filter rules regarding traffic on those ports?

And also can't see the reason for port forwarding/open ports fails, but you can check a couple of things when the problem reappears, check the NAT session table on router to see if the router is still forwarding those ports back to your server.

gruffle wrote: just a thought folks - I am as fed up with Draytek firmware issues (multiple sites all over the country!) as the next user here and I am assessing TCO for these routers, and frankly likely to move away at the next upgrade cycle (getting sooner every flawed fw release!), but just to say the guys in the uk are really only pawns in this (sorry lads!). I do believe they genuinely try to replicate issues and feed this back to Draytek themselves.

Really - try to work with them constructively and you will find them very co-operative, better to direct your frustrations directly to Draytek direct.

What to me is clearly unacceptable is the tardy response from Draytek to these issues. Draytek really need to get their s**t together and fast.

The router doesn't block any outgoing traffic unless there is any firewall rules are configured to do so. Have you setup any filter rules regarding traffic on those ports?

And also can't see the reason for port forwarding/open ports fails, but you can check a couple of things when the problem reappears, check the NAT session table on router to see if the router is still forwarding those ports back to your server.

stevenball wrote: Further to Reado's post.....

When my phone is registered and working OK the SIP port and IP address of the phone are listed in the NAT session table, BTW these ports are also port forwarded.

The router doesn't block any outgoing traffic unless there is any firewall rules are configured to do so. Have you setup any filter rules regarding traffic on those ports?

And also can't see the reason for port forwarding/open ports fails, but you can check a couple of things when the problem reappears, check the NAT session table on router to see if the router is still forwarding those ports back to your server.

I waited for my phone to lose it's registration and checked the NAT session table, no port 5060 there, rebooted the phone and it still failed to register, so back to the NAT session table and still no mention of the ports in question. The phone doesn't register, so the only assumption is that the router is now blocking this port at this point.

Hard reboot the router and low and behold, the port will then appear in the NAT session list and the phone will register.

Hopefully this will be enough for Draytek to sit up and take notice, this never happened under the previous firmware, it only started happening once I installed the current version.