Issues with inbound SIP on 5080
-
Can you edit the rule and post those screen shots? To be honest, I don't have a 1.2.3 installed any longer. Would it be possible to upgrade that to 2.0?
-
Your int. port range is wrong. It should say 5060 instead of 5080.
Delete the rule and create again.
BUT…..I would use 5060 ext. range since this is the default SIP.
-
Internal and external are both on 5080 by design. Not my preference, but sipXbridge currently requires it.
-
-
Try filling in the "to" with 5080.
-
On your advanced outbound, create a new rule above your default. Have it set so that it looks like:
Source:192.168.44.24
SPort: any
Destination: 66.241.X.Y
DPort: 5060
Translation: Interface Address
Static Port: yes -
Just tried that, no change in packet behavior.
Note that the outbound keepalives are making it through pfSense and back to the ITSP. It's the inbound 5080 that gets dropped.
-
Is that traffic in response to the keep alives or are they calls or alerts from the ISP? Are you able to make calls? Do you have one way audio? Do you have keep states set on the default rule or the rule governing the traffic?
Does a traceroute complete from either location?Do you have a range of IP addresses from your provider?
Also, do you have a spare machine you can load pfsense on for a quick load of you rules to see if that would work.
-
Outbound calls go to a different proxy and are working fine.
The packets we are sending to 5060 are intended to keep a generic firewall open to inbound SIP invites on 5080.
Only one static IP from this provider, and the ITSP is sending to that address.
I'll look for another machine to try 2.01 on. The strange thing is that this was working when we first set it up, and stopped a couple of days later with no changes to pfSense.
-
Could be hardware related or someone made an accidental change in the config.
