Everything is completed. The firewall is pfsense with Tony's xml file modified 
to my 
network. There must be something I have overlooked because connections don't 
seem to be 
making it past the firewall.

Calls work fine from inside phones, consistent two way audio, calls to/from 
pstn over 
pri/sip gateway work just fine also.

Remote trying to connect cannot connect. For the fun of it, I asked them to try 
port 80 
since it's enabled on pfsense and I see the same STATE as when trying to 
connect using 
soft phone.

tcp In  69.19.14.31:9623   192.168.10.100:80   CLOSED:SYN_SENT
tcp Out 69.19.14.31:9623   192.168.10.100:80   SYN_SENT:CLOSED
udp In  67.46.113.30:17243 192.168.10.100:5060 NO_TRAFFIC:SINGLE
udp Out 67.46.113.30:17243 192.168.10.100:5060 SINGLE:NO_TRAFFIC
tcp In  69.19.14.31:14006  192.168.10.100:80   CLOSED:SYN_SENT
tcp Out 69.19.14.31:14006  192.168.10.100:80   SYN_SENT:CLOSED

The remote was trying from the Hughes satellite network as we tend to use it 
now and then 
for testing. While the audio is very delayed and pretty much unusable, it is 
still a vable 
test network.
Now, what is weird above is that both sets of IPs which start with 69.x.x.x and 
67.x.x.x 
are both from the same network and user. When she would try the sip phone, the 
IP would 
show up as 67.x.x.x and when she would try the web connection, it would show up 
as 
69.x.x.x. My guess is that they use cache servers.

Anyhow, if I can get some input on why connections aren't making it, I can 
continue on 
this.

Thanks again.

Mike


_______________________________________________
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/

Reply via email to