Unable to make outbound calls since 16.5 update

[RichB]

Hi

I'm unable to make outbound calls since the 16.5 update, whether it's via a desk phone or app. The android app reports temporarily unavailable. Call log says not answered. Inbound still works and so do internal calls.

• 3CX Version, 16.0.5.611
• Server OS, Windows 10 Pro 1909
• Is the 3CX Server Hosted and where? Onsite
• IP Phone Make/Model/Firmware: Fanvil X7 1.1.2
• Provisioning Method: Local
• Trunk Provider or Gateway Make/Model: Gradwell
• Has the Firewall Checker passed: YES
• Are custom Phone Templates being used: NO

Thanks

Richard

 

[Alphabetic]

Have you looked in the logs from the management console to see whats happening?

 

[RichB]

23/04/2020 10:23:36 - Line 10000 has been updated from DB

23/04/2020 10:23:36 - Failed to add outbound CID reformating rule for DN:10000: <Rules />

23/04/2020 10:23:36 - Failed to add outbound CID reformating rule for DN:10000: <Rules /> 23/04/2020 10:26:55 - : Failed to create outbound lines to call 07*********

 

[Alphabetic]

is your SIP trunk registered? Call you call the dial test to voipfone on 152

 

[RichB]

is your SIP trunk registered? Call you call the dial test to voipfone on 152

I think this comment was for NickG's post.

 

[Alphabetic]

I'd turn up your logging and run your test again.

 

[RichB]

3/04/2020 12:12:01 - Leg L:5.1[Extn:215] is terminated: Cause: BYE from PBX

23/04/2020 12:12:01 - Terminated from "RB"<sip:[email protected]>;tag=6a686c6c-b303-4ab0-b3df-4dc14dadf117 to <sip:07*******@127.0.0.1;tag3cx=2df0e45c-4ac5-4c75-92d3-d3acda6ab1de>;tag=140d5d65; reason: Rejected

23/04/2020 12:12:01 - L:5.1[Extn:215] Sending: OnSendResp Send 480/INVITE from 0.0.0.0:0 tid=Pj6e7191e0-7704-4381-b237-defd29a6c5de Call-ID=386ff588-3ed4-48be-8321-34697654af2e: SIP/2.0 480 Temporarily Unavailable Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK-524287-2---Pj6e7191e0-7704-4381-b237-defd29a6c5de;rport=5080 Via: SIP/2.0/UDP [::ffff:80.229.26.135]:51428;branch=z9hG4bK-524287-1---tunneltid;rport;tnlid=clnt.0-5d10a480-c52c-4a76-8a37-9010dcbd733d_9070481 Via: SIP/2.0/TCP 127.0.0.1:50195;rport;branch=z9hG4bKPj6e7191e0-7704-4381-b237-defd29a6c5de;alias To: <sip:07*********@127.0.0.1;tag3cx=2df0e45c-4ac5-4c75-92d3-d3acda6ab1de>;tag=140d5d65 From: "RB"<sip:[email protected]>;tag=6a686c6c-b303-4ab0-b3df-4dc14dadf117 Call-ID: 386ff588-3ed4-48be-8321-34697654af2e CSeq: 6516 INVITE Warning: 499 N-PHONE "Not available" Content-Length: 0

23/04/2020 12:12:01 - SendMsg from <sip:07*******@127.0.0.1;tag3cx=2df0e45c-4ac5-4c75-92d3-d3acda6ab1de>;tag=140d5d65 to "RB"<sip:[email protected]>;tag=6a686c6c-b303-4ab0-b3df-4dc14dadf117

23/04/2020 12:12:01 - Call(C:5) is terminated

23/04/2020 12:12:01 - [CM503020]: Call(C:5): Normal call termination. Call originator: Extn:215. Reason: Not available

23/04/2020 12:12:01 - [CM503016]: Call(C:5): Attempt to reach <sip:07*******@127.0.0.1:0> from Extn:215 has failed. Reason: Temporarily Unavailable

23/04/2020 12:12:01 - [Flow] Current call diversion path:[]

23/04/2020 12:12:01 - L:5.1[Extn:215] failed to reach Out#:>>Rule{07}>>07*******, reason Temporarily Unavailable

23/04/2020 12:12:01 - RerouteReq

23/04/2020 12:12:01 - [CM503016]: Call(C:5): Attempt to reach <sip:07*******@127.0.0.1:0> from Extn:215 has failed. Reason: Temporarily Unavailable

23/04/2020 12:12:01 - ~Target=UnknownTrunk:2

23/04/2020 12:12:01 - [CM503026]: Call(C:5): Route 1 to UnknownTrunk:2 is not active (Busy/Not registered)

23/04/2020 12:12:01 - : Failed to create outbound lines to call 07*******

23/04/2020 12:12:01 - Call(C:5): Call from Extn:215 to 07******* matches outbound rule '07'

23/04/2020 12:12:01 - [Flow] Call(C:5): has built target endpoint: Out#:>>Rule{07}>>07******* for call from L:5.1[Extn:215]

23/04/2020 12:12:01 - [Flow] Target endpoint for 07******* is Out#:>>Rule{07}>>07*******

23/04/2020 12:12:01 - Selected prefix: 07

23/04/2020 12:12:01 - Looking for outbound rule: dialed = [07*******], processed: [07*******]; from-ext:

23/04/2020 12:12:01 - [Flow] Building target endpoint to 07******* from "RB" <sip:[email protected]:0>

23/04/2020 12:12:01 - [CM503010]: Call(C:5): Making route(s) from Extn:215 to <sip:07*******@127.0.0.1:0/UDP>

23/04/2020 12:12:01 - Remote SDP is set for leg L:5.1[Extn:215] Some of the logs when I attempt to make a call out, don't know if it'll be much help.

 

[RichB]

Strange, I don't understand, I created another sip trunk with all the same details as my usual one. Changed one outbound rule to use it and see if it would dial and it did. I then tried another call that hadn't had it's outbound rule changed to use the new sip trunk and that now works as well.

 

[Alphabetic]

I saw in your log that it was rejected. I was going to suggest checking your outbound rules. Are you going to change to use your new SIP trunk?

 

[RichB]

I saw in your log that it was rejected. I was going to suggest checking your outbound rules. Are you going to change to use your new SIP trunk?

For the moment it's working, so I'll leave it alone but when I'm next onsite, I'll attempt to tidy it up one way or the other.

 

[RichB]

Further update, restarting Windows breaks it again. If I recreate the SIP Trunk with a previously used named it doesn't seem to like to work but use a new unique name and it does. Also I can see the firewall DNS proxy deny traffic so I have changed it to a packet filter for the time being. I'm also seeing Windows event logs that the PostgreSQL cannot be found and that it either isn't installed or corrupt. Are there any DB repair utilities?

 

[centre1]

Just adding my 2 cents. We too had the same issue this morning after our 3cx automatically updated, where inbound calls worked fine, as did all internal phone calls. What we had to do was:

- add a new duplicate SIP Trunk as per normal with standard entries
- export the Inbound Rules
- then delete old (non-working) SIP Trunk
- amend the Inbound Rule csv with the new Trunk ID
- import Inbound Rule csv
- worked straight away

We haven't rebooted the server yet. will do that in the coming days.

 

[RichB]

Just adding my 2 cents. We too had the same issue this morning after our 3cx automatically updated, where inbound calls worked fine, as did all internal phone calls. What we had to do was:

- add a new duplicate SIP Trunk as per normal with standard entries
- export the Inbound Rules
- then delete old (non-working) SIP Trunk
- amend the Inbound Rule csv with the new Trunk ID
- import Inbound Rule csv
- worked straight away

We haven't rebooted the server yet. will do that in the coming days.

I think that I was experiencing the same issue as others have reported where 3CX starts before the network stack is ready. Changing the services to a delayed start sometimes helps but I changed the trunk to use an IP address rather than a domain name and it started working fine. I think that the Windows event logs possibly always display these errors just because of the way the DB has been installed and 3CX was probably sending corrupt DNS entries to the firewall as the network stack hadn't finished loading. Thanks for your thoughts.

 

[daveatgower]

Rich, I think you are just in the same boat as many of us right now. It's a bug with v16 update 5. Changing DNS to IP address will get it back up and running even after a reboot. We hope 3CX fixes this soon.

 

[360CTM]

Hi all,
Where are you making this 'DNS to IP change' and where are you adjusting the delayed start for the server? Just want to confirm I make the correct changes.

Thank you.

 

[AWS2P]

in trunk setting

 

[360CTM]

Thanks! if my provider uses multiple IP addresses can I enter all of them or separate trunks for each IP? Sorry for all the questions but working this issue on a live system and want to ensure I don't bugger up a system that is otherwise working except for the app.

 

[RichB]

Thanks! if my provider uses multiple IP addresses can I enter all of them or separate trunks for each IP? Sorry for all the questions but working this issue on a live system and want to ensure I don't bugger up a system that is otherwise working except for the app.

I'm not sure sorry, however I do know a fix is being tested, if you have support I suggest you log a ticket, if not YiannisH_3CX (3CX Support) suggested private messaging him via the forum for help.