On 20.7.3 and I've tried about everything I can find, but I can't get SIP up and going through the OPNsense box. Doesn't look like the traffic is getting blocked. I've set static outbound NAT. I even install the SIP proxy plugin but it did nothing at all best I could tell.
RingCental seemed to work fine but it might be using a different method. I'm using Zultys at the moment and it simply refuses to have a successful SIP connection. I think they may use more traditional connectivity where RingCental may have not been.
Any thoughts on what else to try?
Sent from my GM1917 using Tapatalk
I have a working SIP trunk to A&A in the UK. I would steer clear of the SIP proxy since most reports say that it does more harm than good.
What are you trying to connect? Any option to use AIX2 which is much more NAT friendly?
Bart...
Quote from: bartjsmit on October 12, 2020, 04:08:58 PM
I have a working SIP trunk to A&A in the UK. I would steer clear of the SIP proxy since most reports say that it does more harm than good.
What are you trying to connect? Any option to use AIX2 which is much more NAT friendly?
Bart...
I'm just trying to get a mobile SIP mobile client or softphone to connect back to our remote Zultys box.
Sent from my GM1917 using Tapatalk
Screenshot of outbound nat and port forward please
Quote from: mimugmail on October 12, 2020, 04:31:08 PM
Screenshot of outbound nat and port forward please
Do I need port forwarding for sip to function? I hadn't set up inbound anything for sip since the devices are DHCP.
I'll grab screenshots this afternoon I'm not near the box at thr moment.
Sent from my GM1917 using Tapatalk
Did you configure STUN? Here's a few servers to choose from: https://gist.github.com/mondain/b0ec1cf5f60ae726202e
Bart...
Quote from: bartjsmit on October 12, 2020, 05:42:48 PM
Did you configure STUN? Here's a few servers to choose from: https://gist.github.com/mondain/b0ec1cf5f60ae726202e
Bart...
I have no idea, I'm just pointing my softphone to my workplace pbx. The phone system admin console shows the connection and the correct public IP. But sip wont register for some reason. Seems to work everywhere except behind OPNSense.
Sent from my GM1917 using Tapatalk
Zultys documentation "marketing", "automatic NAT traversal allows any IP phone to be fully connected to the corporate network.". Sounds like stun is built into the pbx?
Sent from my GM1917 using Tapatalk
Screenshots
Quote from: mimugmail on October 12, 2020, 07:15:07 PM
Screenshots
Yup, stay tuned. Probably be another 5 hours or so before I'm at the box again.
Sent from my GM1917 using Tapatalk
Quote from: mimugmail on October 12, 2020, 07:15:07 PM
Screenshots
See static outbound NAT rules. There are no port forward rules for SIP.
And LAN Firewall everything is accepted?
Quote from: mimugmail on October 13, 2020, 07:17:26 AM
And LAN Firewall everything is accepted?
Yes I still have the default allow out rule in place. I see successful traffic. I'm starting to think maybe something upstream isn't liking the traffic. So strange other services work like RingCental. But it also seems to work from other places the OPNSense box seems like the common element for it failing to establish sip.
Sent from my GM1917 using Tapatalk
Then you'd need a packet capture and upload it here to see whats going on
Quote from: mimugmail on October 13, 2020, 05:03:48 PM
Then you'd need a packet capture and upload it here to see whats going on
I'm working from home again today (it's rare now) and again fighting to get sip to connect lol. I ran a packet capture. I'm hesitant to upload it here as it has so much sensitive information. Is there anything specifically you'd be looking for? I don't see anything that would cause alarm, I see some retransmits and some out of sync warnings but not much else.
Packet capture in UI which only displays IPs and Ports is fine
Sorry to bump an old thread.
I'm also facing the same issue, SIP being blocked by the default rule, when I run a packet capture it looks good
Interface Capture output
WAN
hn0 17:19:25.796754 IP 185.26.240.4.5060 > 188.223.75.170.5060: UDP, length 887
WAN
hn0 17:19:26.296327 IP 185.26.240.4.5060 > 188.223.75.170.5060: UDP, length 887
WAN
hn0 17:19:27.397625 IP 185.26.240.4.5060 > 188.223.75.170.5060: UDP, length 887
WAN
hn0 17:19:29.397009 IP 185.26.240.4.5060 > 188.223.75.170.5060: UDP, length 887
WAN
hn0 17:19:33.395182 IP 185.26.240.4.5060 > 188.223.75.170.5060: UDP, length 887
Did you manage to get your SIP fixed? If so how? As my SIP trunk provider gave me a SIP proxy address.
Quote from: leprejohn on February 06, 2021, 06:24:26 PM
Sorry to bump an old thread.
I'm also facing the same issue, SIP being blocked by the default rule, when I run a packet capture it looks good
Interface Capture output
WAN
hn0 17:19:25.796754 IP 185.26.240.4.5060 > 188.223.75.170.5060: UDP, length 887
WAN
hn0 17:19:26.296327 IP 185.26.240.4.5060 > 188.223.75.170.5060: UDP, length 887
WAN
hn0 17:19:27.397625 IP 185.26.240.4.5060 > 188.223.75.170.5060: UDP, length 887
WAN
hn0 17:19:29.397009 IP 185.26.240.4.5060 > 188.223.75.170.5060: UDP, length 887
WAN
hn0 17:19:33.395182 IP 185.26.240.4.5060 > 188.223.75.170.5060: UDP, length 887
Did you manage to get your SIP fixed? If so how? As my SIP trunk provider gave me a SIP proxy address.
No never got it figured out. I gave up. And I'm at a different job now so don't have the same need.
Sent from my IN2025 using Tapatalk