Well, they aren't coming through port 5080... they are coming through 5060 and
using the NAT traversal piece on sipXecs (which I lump in with sipXbridge...
in my head anyway).
I turned off all of the NAT traversal in eyebeam have static NAT on the local
and remote firewall... no siproxd or anything on the far-end firewall.
Thanks,
Mike
-----Original Message-----
From: Scott Lawrence [mailto:[email protected]]
Sent: Thursday, December 31, 2009 8:44 AM
To: Picher, Michael
Cc: [email protected]
Subject: Re: [sipx-users] config problem or sipxbridge problem?
On Thu, 2009-12-31 at 08:20 -0500, Picher, Michael wrote:
> Not sure if this is something with my config or sipXbridge.
>
>
>
> Trying to call remote worker to remote worker that are connected in
> via sipXbridge.
> From the log it almost looks to me like sipXbridge is getting confused
> about the remote teleworker IP address, but Internet Dialing is setup
> properly with the correct subnets. My remote teleworker subnet
> happens to be 172.16.1.x/24 and the subnet that the internal subnet
> that they sipX system is on is 172.16.128.0/20. Then it thinks
> 172.16.1.x (my remote pc’s internal IP address) is supposed to be an
> ITSP account.
Remote workers should _not_ be coming in through sipXbridge (port 5080);
they must come in directly to the proxy (port 5060).
It looks to me as though you may have NAT compensation happening in the
remote phones or somewhere before they hit the proxy, because the
Contact addresses are marked as not NATted.
_______________________________________________
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/
