On Thu, Jul 22, 2010 at 12:58 PM, Tony Graziano < [email protected]> wrote:
> You speak "cryptically". I am without my decrypting fluid (coffee) to > decrypt your statement. > I apologize. This seems to be a common problem of mine lately. I'm working on it. I blame it on the kids for not letting me get enough sleep. ;) > > Firewall translation is one thing, those are correct statements. > > Your ITSP should send calls to port 5080 (not 5060). The proxy runs on port > 5060 and remote users connect via port 5060. > Yes, my ITSP is sending inbound calls to port 5080 (not 5060) and remote users are connecting via port 5060. No issues here. My issue is with inbound SIP URI calls. Calls via port 5060 aren't being connected but ones via 5080 are. Here are my test results: x-lite -> sip2sip -> [email protected] - Call failed: Request timeout x-lite -> sip2sip -> [email protected]:5060 - Call failed: Request timeout x-lite -> sip2sip -> [email protected]:5080 - Successful My network is set up similarly to the one shown in "DNS Concepts for sipXecs" - "Scenario 1" found here: http://wiki.sipfoundry.org/display/xecsuser/DNS+Concepts+for+sipXecs > > Noone seems to know who the ITSP is, what firewall you are using... more > information is better here... > My ITSP is voip.ms. My firewall is a Siemens SpeedStream 6520. I have port forwarding rules for 5060 udp, 5060 tcp, 5080 udp and ports 30000 - 31000 udp. There's no other inbound/outbound traffic on this line (it's dedicated to voip). I just finished installing and configuring pfSense. I don't think it's the Siemens router, but I'll try it with pfSense as the firewall/gateway to see if makes a difference.
_______________________________________________ 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/
