Installed new fresh v18 - outbound calls does not work

[BenTen]

Hello,

we did install new, fresh debian 9 with latest 3cx version. Backup has been restored and everything is working, except outbound calls. Was there any change in outbound calls flow?

Error was generic, "there is no lines available" or something similar. Im not right now connoted to this server as we still use v16.

What can i check, regarding this issue, having in mind that nothing has changed after backup apply.

 

[leejor]

You'll want to check the Activity Log, to see if the call is being sent to the provider (assuming the trunk shows as registered), and if so, is there a rejection message being returned?

 

[ChrisC_3CX]

we did install new, fresh debian 9 with latest 3cx version

In addition to what @leejor said, please clarify what you mean here. How did you deploy 3CX? Is it an on-prem install and if yes, did you use the 3CX ISO? I'm asking because the latest 3CX version (v18 U2) ISO will install Debian 10 and not debian 9. Did you perhaps install Debian 9 and then 3CX manually?

You can SSH and confirm the OS with:

cat /etc/os-release

Im not right now connoted to this server as we still use v16.

Also, are you running a second instance with the same license key or same Register based provider? Can you provide more info on this?

 

[BenTen]

Sorry, misstyped. Debian 10

It is same licence key, as this is failout server. First instance is shutdown during testing. Can reccive inbound calls,but for outbound error message is Failed to create outbound lines to call


PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=debian

 

[cobaltit]

As this is the failover server, is it on a different internet connection? If so, are you using IP authenticated trunks

 

[BenTen]

For testing, I did replicated all IP setup, same network, same rules. As I wrote, i can reccive calls, so SIP is working, but outbound calls give error.

Maybe im looking something wrong, but cant understand why incoming calls works, but outbound does not.

19/02/2022 18:03:11 - [Flow] Call(C:6): making call from L:6.1[Extn:704] to T:EndCall:EndCall@[Dev:sip:[email protected]:5483;rinstance=69ad6dcaa0f7905a]
19/02/2022 18:03:11 - [CM503016]: Call(C:6): Attempt to reach <sip:[email protected]:0> from Extn:704 has failed. Reason: Temporarily Unavailable
19/02/2022 18:03:11 - [Flow] Current call diversion path:[]
19/02/2022 18:03:11 - L:6.1[Extn:704] failed to reach Out#:>>Rule{ShortCodes}>>1444, reason Temporarily Unavailable
19/02/2022 18:03:11 - RerouteReq
19/02/2022 18:03:11 - [CM503016]: Call(C:6): Attempt to reach <sip:[email protected]:0> from Extn:704 has failed. Reason: Temporarily Unavailable
19/02/2022 18:03:11 - ~Target=UnknownTrunk:2
19/02/2022 18:03:11 - [CM503026]: Call(C:6): Route 1 to UnknownTrunk:2 is not active (Busy/Not registered)

 

[leejor]

Call(C:6): Attempt to reach <sip:[email protected]:0> from Extn:704 has failed.

Why does the call appear to be routing to your own FQDN and not your provider?

 

[BenTen]

To be honest, im not quite sure. As I wrote, i did new fresh install of Debian 10 with 3cx official ISO latest version. After I did apply backup from previous instance, everything work, no issue, but except outbound calls.

Can anyone point me where to start troubleshooting to try to find solution?

Thank you all for help

 

[leejor]

Is the name of the trunk group you are trying to call out on actually called UnknownTrunk:2 ? That seem to be where your outbound rule is sending the call. Is the call using the correct rule?

 

[BenTen]

Thank you. There is some issue and I will need to take all steps to try to find issue. Im just not sure why would incoming calls work, but outbound (SIP) does not work. 3cx outbound (not sip) between extensions does work.

To ansswer, yes, call use right rule. I will try to copy in next response difference between two instance, one working, another does not.

 

[NickD_3CX]

I will try to copy in next response difference between two instance, one working, another does not.

I think this is the best idea, if you have another 3CX installation with the same Trunk that Outbound Calls work, this is great.
I think I agree with what @leejor spotted, I think that the Registrar/Destination that you are sending the calls to is wrong, that would explain why incoming calls are OK, but outgoing are failing.