SIPSTATION inbounds not working after reinstall

I recently had to reinstall my FreePBX system, due to an error, and I subscribe to SIPSTATION trunks. I also have some other SIP trunks to tandmx, as well as to another asterisk server to act as a tandem between my FreePBX and Phreaknet. All of those other trunks are working, but for some reason my SIPSTATION DIDs aren’t working at all. Outbound calls through SIPSTATION work just fine, but it’s the inbound calls that are broken. Do I need to contact Sangoma Support about this to have them reset something?

Possibly, this post will help:

If no luck, report what, if anything, appears in the Asterisk log on a failed incoming call. If nothing, report what, if anything, appears in sngrep. If also nothing, report whether incoming calls hit the WAN interface of your router/firewall.

1 Like

Nothing is showing up in the logs. I haven’t run a wireshark yet on the system, but I cannot run a packet capture on my gateway since it is a consumer grade Netgear router.

Confirmed nothing in sngrep? Does the Netgear have your public IP on its WAN interface? Have you tried rebooting it?

1 Like

Nothing. No, I have not

If the WAN side of your Netgear doesn’t have your public IPv4, most likely your “modem” is configured as a router. Or, your ISP is doing NAT, which could be problematic. I suggest powering off both modem and router, power up modem and wait for it to come ready, then the router. When it is also ready restart the PBX and retest.

If you still have trouble, use pjsip logger or sngrep to view a REGISTER request and associated replies. Check that REGISTER has your correct public IP and port in the Contact header, and check that the Via header of the 200 OK has the public IP in the received= tag, and the correct port in the rport= tag.

1 Like

My Netgear router has the public IP. I just had to reboot it. Thanks!

I ran into the same issue after a reinstall—turns out the SIPStation module didn’t auto-bind to the default inbound route. Double-check that your DID is pointed to a valid destination under Inbound Routes. Also make sure the firewall isn’t blocking SIP traffic. Restarting the trunk and re-authenticating via the SIPStation module fixed it for me. It’s easy to miss a step post-reinstall.