Issue making outbound calls

ive been trying to make outbound calls with freepbx and have tried troubleshooting myself for over 2 days now just to end up no where, everytime i make an outbound call using any softphone it calls for a couple of seconds and disconnects, my IAX2 trunk says unmonitored instead of online so i swapped to pjsip but still no luck
here are some of the logs:

10463 [2025-02-11 03:13:35] NOTICE[687745] res_pjsip/pjsip_distributor.c: Request ‘REGISTER’ from ‘sip:[email protected]’ failed for ‘172.56.28.0:1554’ (callid: sv7G6GR90uZAtrVVsRxFqg…) - No matching endpoint found
10464 [2025-02-11 03:13:35] VERBOSE[687745] res_pjsip_logger.c: <— Transmitting SIP response (502 bytes) to UDP:172.56.28.0:1554 —>
10465 SIP/2.0 401 Unauthorized
10466 Via: SIP/2.0/UDP 192.0.0.1:56515;rport=1554;received=172.56.28.0;branch=z9hG4bK-524287-1—2183dfb2e2832dd8
10467 Call-ID: sv7G6GR90uZAtrVVsRxFqg…
10468 From: sip:[email protected];tag=22131e58
10469 To: sip:[email protected];tag=z9hG4bK-524287-1—2183dfb2e2832dd8
10470 CSeq: 1 REGISTER
10471 WWW-Authenticate: Digest realm=“asterisk”,nonce=“1739243615/fac223092e9e99f72667ad66bef05f47”,opaque=“62d4fc906b946a91”,algorithm=MD5,qop=“auth”
10472 Server: FPBX-17.0.19.23(21.7.0)
10473 Content-Length: 0
10474
10475
10476 [2025-02-11 03:13:35] VERBOSE[635020] res_pjsip_logger.c: <— Received SIP request (981 bytes) from UDP:172.56.28.0:1554 —>
10477 REGISTER sip:143.110.235.6;transport=UDP SIP/2.0
10478 Via: SIP/2.0/UDP 192.0.0.1:56515;branch=z9hG4bK-524287-1—f3ccd1539814f44b;rport
10479 Max-Forwards: 70
10480 Contact: sip:[email protected]:1554;transport=UDP;rinstance=80e1e5fc6757ad18
10481 To: sip:[email protected];transport=UDP
10482 From: sip:[email protected];transport=UDP;tag=22131e58
10483 Call-ID: sv7G6GR90uZAtrVVsRxFqg…
10484 CSeq: 2 REGISTER
10485 Expires: 60
10486 Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
10487 Supported: replaces, norefersub, extended-refer, timer, sec-agree, outbound, path, X-cisco-serviceuri
10488 User-Agent: Z 5.6.6 v2.10.20.5
10489 Authorization: Digest username=“123”,realm=“asterisk”,nonce=“1739243615/fac223092e9e99f72667ad66bef05f47”,uri=“sip:143.110.235.6;transport=UDP”,response=“8e4484845d303e9b4a1f6dc947f67efb”,cnonce=“01c33e261a30cca23f35a0c9ba74cafc”,nc=00000001,qop=auth,algorithm=MD5,opaque=“62d4fc906b946a91”
10490 Allow-Events: presence, kpml, talk, as-feature-event
10491 Content-Length: 0
10492
10493
10494 [2025-02-11 03:13:35] NOTICE[682169] res_pjsip/pjsip_distributor.c: Request ‘REGISTER’ from ‘sip:[email protected]’ failed for ‘172.56.28.0:1554’ (callid: sv7G6GR90uZAtrVVsRxFqg…) - No matching endpoint found
10495 [2025-02-11 03:13:35] NOTICE[682169] res_pjsip/pjsip_distributor.c: Request ‘REGISTER’ from ‘sip:[email protected]’ failed for ‘172.56.28.0:1554’ (callid: sv7G6GR90uZAtrVVsRxFqg…) - Failed to authenticate
10496 [2025-02-11 03:13:35] VERBOSE[682169] res_pjsip_logger.c: <— Transmitting SIP response (502 bytes) to UDP:172.56.28.0:1554 —>
10497 SIP/2.0 401 Unauthorized
10498 Via: SIP/2.0/UDP 192.0.0.1:56515;rport=1554;received=172.56.28.0;branch=z9hG4bK-524287-1—f3ccd1539814f44b
10499 Call-ID: sv7G6GR90uZAtrVVsRxFqg…
10500 From: sip:[email protected];tag=22131e58
10501 To: sip:[email protected];tag=z9hG4bK-524287-1—f3ccd1539814f44b
10502 CSeq: 2 REGISTER
10503 WWW-Authenticate: Digest realm=“asterisk”,nonce=“1739243615/fac223092e9e99f72667ad66bef05f47”,opaque=“43a9b23239e4dc0f”,algorithm=MD5,qop=“auth”
10504 Server: FPBX-17.0.19.23(21.7.0)
10505 Content-Length: 0
10506
10507
10508 [2025-02-11 03:13:44] VERBOSE[682169] res_pjsip_logger.c: <— Transmitting SIP request (465 bytes) to UDP:54.172.60.3:5060 —>
10509 OPTIONS sip:[email protected]:5060 SIP/2.0
10510 Via: SIP/2.0/UDP 143.110.235.6:5060;rport;branch=z9hG4bKPj44870dec-dfdd-489e-8bfb-54f14ebed5db
10511 From: sip:[email protected];tag=6af3a8b6-4704-423a-8e68-83d6de0c4cde
10512 To: sip:[email protected]
10513 Contact: sip:[email protected]:5060
10514 Call-ID: ed54e577-7458-4a27-ab5d-cca4c1fc15cf
10515 CSeq: 45017 OPTIONS
10516 Max-Forwards: 70
10517 User-Agent: FPBX-17.0.19.23(21.7.0)
10518 Content-Length: 0
10519
10520
10521 [2025-02-11 03:13:44] VERBOSE[635020] res_pjsip_logger.c: <— Received SIP response (420 bytes) from UDP:54.172.60.3:5060 —>
10522 SIP/2.0 200 OK
10523 Via: SIP/2.0/UDP 143.110.235.6:5060;rport=5060;branch=z9hG4bKPj44870dec-dfdd-489e-8bfb-54f14ebed5db;received=143.110.235.6
10524 From: sip:[email protected];tag=6af3a8b6-4704-423a-8e68-83d6de0c4cde
10525 To: sip:[email protected];tag=3f9aa8b68dc167e625b20004464ea4b5.9f7636e0
10526 Call-ID: ed54e577-7458-4a27-ab5d-cca4c1fc15cf
10527 CSeq: 45017 OPTIONS
10528 Server: Twilio Gateway
10529 Content-Length: 0

Hi ! When you say “it calls”, you mean it connects the call and then drops?
If so, could be a NAT issue.
Is it happening only with softphones and all of them are outside your pbx network ?

the call connects but nothing’s happening to the number i call, no rings, nothing, and when i used zoiper instead of linphone it says the error 408 call rejected.

408 is timed out, not rejected. It normally means there is a network configuration error which means either the request, or its response, never reach their destination.

would you happen to know how i can fix this or how i can troubleshoot this issue please?

You capture packets at various places in the network until you find where they get lost. You also check that they are being sent to the right addresses. You fix any wrong address, then looks at the configuration of routers and firewalls around the point of loss.

Basically you have a symptom. You have to find the cause, and fix that cause. There are rarely easy answers where the correction for a message is obvious and precise, and in most such cases, the answer is in the message.

I’ve described the more common case, where the 408 is faked, at the sending end. It can also be generated by the remote end, and for internal time outs, there.

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.