Hi, I have a problem whenever my WRT54G V3 router reboots - my Sipura VoIP box can't register anymore. I sniffed packets and can see that Sipura sends registration requests but never gets a response back from SIP server. I checked with my VSP (VoIP Service provider - FWIW, its VoicePulse) as this was happening and they confirm their servers are sending the response back; but it never reaches my Sipura. I've tried forwarding UDP 5060-5061 to Sipura's IP, enabled port-triggering, DMZ - nothing helps. VoicePulse support tells the router is blocking the SIP traffic going to my Sipura. And, I think that is true. My best guess is its SPI or something. How do I fix this problem ? I've been running OpenWRT before I switched to Tomato 2 weeks ago and never had this issue. Rebooting Sipura doesn't help either - again, sniffing packets tells that the Sipura successfully gets DHCP address from router, successfully gets DNS responses, and sends registration request - but never gets a response back. To get Sipura working, I need to do one of the following: - power down Sipura, reboot router, then power-up Sipura. - force a IP change for Sipura (via static IP or diff static DHCP address or any other methods) - power down Sipura for a min or so and then power-up again. The last one above makes me think that the router mistakes responses from my VSP's servers as bad-traffic and blocks it (I may not have the terminologies here ...). I love the features in Tomato and want to use it - but only if I can find a solution to this problem. Please help. Misc. info: - I have static DHCP and Sipura always gets the same LAN IP. - VoicePulse Sipura uses outbound SIP proxy; no STUN - My other SIP box (PAP2) isn't effected by this issue. It uses STUN and I forward ports on router - I noticed that when I hard-reset Sipura, it doensn't NTP-update its time (when this issue happens) - FWIW, I've seen this behavior with one other firmware when I was firmware-hopping - don't remember which exactly - think it was some HyperWRT flavor.