On Tue, 2009-06-16 at 12:00 -0400, Tim Byng wrote: > I was originally able to register remote workers from home when I had > a D-Link DI-624 router without any modifications to the router > settings. However, a few weeks ago lightning struck the house across > the street, came through the cable lines and fried everything that was > attached to the cable line, including the router and network card in > the computer. > > > > I have since replaced both (the DI-624 with a DIR-655) and was > initially not able to register remote workers. I set up a Wireshark > capture and found that only the register request was going out, but > nothing was coming back. > > > > I have since been able to resolve this issue by disabling SIP under > the application level gateway settings (Advanced -> Firewall). Once > this was done, I was able to register successfully to a remote sipXecs > box. I thought I’d share this, just in case someone else runs into the > same problem. > > > > Note: So far, this is the only default setting that needs to be > changed in the DIR-655. However, I’m at a remote location, so I am not > able to test audio at this time. If any other settings need to be > adjusted, I will update this thread.
Thanks for sharing that Tim. In general, having more than one thing trying to compensate for NATs doesn't work very well. The sipXecs 4.0 NAT traversal mechanisms will have the best chance of working if _nothing_ (phone, router, firewall, ...) else in the network is "SIP aware" or doing any kind of NAT compensation. Figuring out what those somethings are and turning them off can sometimes be challenging... _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
