Couldn't he tweak public SRV records to report _sip._tcp.domain.name and _sip._udp.domain.name as being on port 7070?
Then leave the internal DNS alone for the internal SRV records... Mike -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Scott Lawrence Sent: Thursday, August 06, 2009 6:29 AM To: Peter Selc Cc: [email protected] Subject: Re: [sipx-users] remote worker can't register On Thu, 2009-08-06 at 09:10 +0200, Peter Selc wrote: > Therefore I tried to register Twinkle softphone behind NAT. As SIP > registrar - publicIP:port was configured. When the "SIP account -> > domain" was set to publicIP:port - phone didn't register as well > (401). If i set only publicIP - phone registered, but can't make any > outbound call, because publicIP:5060 is not the real public port. > > Later I changed the public port to 5060, and Twinkle registered > correctly. But i would prefer to have it on non-standard port because > of security reasons. Does sipxecs have some security features (ddos > prevention...)? > Is it known to be a working scenario, if public port is not 5060? The trick is that you need to get your phone to send a message that has a valid domain in the To header field (must match how the registrar is configured), but actually transmit the packet to the public port. It would be much easier if you'd make the public port match the private one. Is there some reason that you've not used the default port numbers everywhere? _______________________________________________ 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/ _______________________________________________ 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/
