Hello,
I am encountering an issue (in the configuration of FreeSBC) with the NAPs.
Unfortunately, they remain disabled, which prevents communication tests. I also changed the number of allocated processors (as mentioned in a forum article), but nothing changed! They still remain disabled.
Hi! Could you please provide more details or share a diagnostic report?
The most likely cause of the issue is something related to your network, or it could be that the SIP servers you’re trying to reach are not responding to SIP OPTIONS keepalive messages. If those servers are under your control, I recommend checking their behavior to confirm this.
Additionally, you might want to try disabling the “Poll Remote Proxy” flag and then attempt placing calls again to see if the behavior changes.
Let us know what you find!
There are some troubleshooting information here: Troubleshooting Common Problems | ProSBC Documentation
I think some of this can help you, like the SIP signaling trace.
Hello,
thank you for your response.
Using the sngreg tool, we observe that the SIP signaling returns OK, both on our PBX side and on the operator’s side.
In the call traces on FreeSBC, we see that all incoming and outgoing calls (using the correct NAP) consistently end with the error code “503 Service Unavailable”.
Additionally, our network is fully open for testing purposes, with no firewall restrictions.
Without a SIP Capture, Call trace, or logs, it’s not possible to further assist you.
If you prefer to use sngrep, please save the .pcap file and generate a report.
Another way to get a signalling trace:
Hello,
Thank you for your help!
I am attaching the SIP capture as well as a report generated by the SBC:
report and logs :
Sip Capture :
thank you
Hi, were you able to resolve the issue?
Apologies for the delayed response — I don’t check this forum very often.
Just to clarify, I’m not part of the Telcobridges staff, so I don’t have access to their support platform or the WeTransfer account you mentioned. However, if you still need help, I’d be happy to assist as best I can.
From the SIP capture screenshot you shared, it seems the SBC isn’t routing the calls. Typically, it would return a 404 response when no matching routes are found — unless this behavior has been modified via SIP code remapping in the profile. Maybe there is also missing information on this screenshot.
Without direct access to the SBC, its configuration, and the full logs or pcap captures, it’s difficult to provide a definitive answer — we’d mostly be speculating. But let me know what you have access to, and I’ll do my best to help you troubleshoot.
