> > rjoly > I've sent you email. Even twice :) I've seen it and I think we came to the same conclusion. Read on...
> > Tony Graziano > > Quote: > > What does the registration look like for the remote user in sipxecs? > > Account tab > username: xxx > password: xxx > domain: yukon.cv.ua > Register with domain and receive incoming calls: checked Send > outbound via: proxy > Address: yukon.cv.ua > > Topology tab > IP adress: use local ip adress > Enable ICE: unchecked > > Quote: > > Have you edited the subnets in sipxecs to reflect yours? > > Yes, its 192.168.0.0/24. My sipXecs ip 192.168.0.66. My home > ip 192.168.30.2 > > [/quote] > What is the remote phone? > [/quote] > Its X-Lite 3.0 > > Maybe there is a problem with router ip? Its 192.168.0.100. > I see that all incoming from outside traffic is marked as > comming from 192.168.0.100. At least in sipXproxy.log: > "2010-03-19T13:46:46.747999Z":2361:SIP:DEBUG:yukon.cv.ua::B6CA > 5B90:SipXProxy: > "Patterns::IPv4subnet - 192.168.0.100 matches subnet > 192.168.0.0/24 (mask=00ffffff in_network=0000a8c0 in_address=6400a8c0" Your observation is correct. Every SIP message sent by your remote x-lite (192.168.30.2) appears to be originating from your router's private IP address (192.168.0.100) when they should in reality appear to be originating from your Remote Router's public IP address. This unexpected subtitution of IP addresses leads the NAT traversal feature to believe that your x-lite resides inside same private network as the sipxecs and therefore will not provide any NAT compensation. I do not know why your router would actually re-write the source IP addresses of packets entering the private network, but if you find a way to disable that behavior, you'll be one step closer to success. _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org 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/
