Outbound calls suddenly stopped

Middle of the day today we suddenly stopped being able to call out of our building. Incoming calls are working just fine. Calling other extensions works just fine. Calling out stopped working while everyone was out to lunch it seems. We got back from a company lunch and no outside calling. I checked with Vitelity to make sure there wasn’t a problem on their end and they are not even seeing those calls we are trying to do reach their system. It appears to be in FreePBX as it is not leaving our network to theirs at all.

I have FreePBX 14.0.1.20

Nothing in our system should have changed, as I am the only one that has access to the server, and things just suddenly stopped working. Any ideas on where to check first? I made sure the Dial Patterns were still there in Outbound Routes. I made sure we still had all other settings for the trunk and such there. Not sure where to go from here. Any help will be appreciated.

Show us some call logs, then we might be able to help.

Try rebooting your internet router/firewall?

[2017-11-01 07:58:25] VERBOSE[26949][C-00000007] pbx.c: Executing [[email protected]:1] ResetCDR("SIP/7070-00000008", "") in new stack
[2017-11-01 07:58:25] VERBOSE[26949][C-00000007] pbx.c: Executing [[email protected]:2] NoCDR("SIP/7070-00000008", "") in new stack
[2017-11-01 07:58:25] VERBOSE[26949][C-00000007] pbx.c: Executing [[email protected]:3] Progress("SIP/7070-00000008", "") in new stack
[2017-11-01 07:58:25] VERBOSE[26949][C-00000007] pbx.c: Executing [[email protected]:4] Wait("SIP/7070-00000008", "1") in new stack
[2017-11-01 07:58:26] VERBOSE[26949][C-00000007] pbx.c: Executing [[email protected]:5] Playback("SIP/7070-00000008", "silence/1&cannot-complete-as-dialed&check-number-dial-again,noanswer") in new stack
[2017-11-01 07:58:26] VERBOSE[26949][C-00000007] file.c: <SIP/7070-00000008> Playing 'silence/1.ulaw' (language 'en')
[2017-11-01 07:58:27] VERBOSE[26949][C-00000007] file.c: <SIP/7070-00000008> Playing 'cannot-complete-as-dialed.ulaw' (language 'en')
[2017-11-01 07:58:27] VERBOSE[26949][C-00000007] file.c: <SIP/7070-00000008> Playing 'check-number-dial-again.ulaw' (language 'en')
[2017-11-01 07:58:27] VERBOSE[26949][C-00000007] pbx.c: Executing [[email protected]:1] Macro("SIP/7070-00000008", "hangupcall") in new stack
[2017-11-01 07:58:27] VERBOSE[26949][C-00000007] pbx.c: Executing [[email protected]:1] GotoIf("SIP/7070-00000008", "1?theend") in new stack
[2017-11-01 07:58:27] VERBOSE[26949][C-00000007] pbx.c: Executing [[email protected]:3] ExecIf("SIP/7070-00000008", "0?Set(CDR(recordingfile)=)") in new stack
[2017-11-01 07:58:27] VERBOSE[26949][C-00000007] pbx.c: Executing [[email protected]:4] NoOp("SIP/7070-00000008", " monior file= ") in new stack
[2017-11-01 07:58:27] VERBOSE[26949][C-00000007] pbx.c: Executing [[email protected]:5] AGI("SIP/7070-00000008", "attendedtransfer-rec-restart.php,,") in new stack
[2017-11-01 07:58:28] VERBOSE[26949][C-00000007] res_agi.c: <SIP/7070-00000008>AGI Script attendedtransfer-rec-restart.php completed, returning 0
[2017-11-01 07:58:28] VERBOSE[26949][C-00000007] pbx.c: Executing [[email protected]:6] Hangup("SIP/7070-00000008", "") in new stack
[2017-11-01 07:58:28] VERBOSE[26949][C-00000007] app_macro.c: Spawn extension (macro-hangupcall, s, 6) exited non-zero on 'SIP/7070-00000008' in macro 'hangupcall'
[2017-11-01 07:58:28] VERBOSE[26949][C-00000007] pbx.c: Spawn extension (from-internal, h, 1) exited non-zero on 'SIP/7070-00000008'

That is what I get in the logs from one of the phones trying to call out. Is there something else I can do to get a little more information?

Take a look at your outbound route configuration and see if anything strange shows up there. You might also double check your trunks, just to make sure they are all configured correctly.

From the log, it looks like your system doesn’t know it has any outbound routes, which is disconcerting to say the least.

Nothing different in the Outbound Route Configuration, Trunk configuration looks good and verified with Vitelity for correctness to connect to them as well. It just seems that they are not going to Vitelity at all as they are not seeing them hit their system.

I created another Outbound Route fresh just to see if that would change anything, and nothing changed at all. Created a new Trunk, no change. This is getting real frustrating as everything appears to be configured perfectly, with things just not working. The only thing that happened before this change, was we created a new Time Condition and Time Group for a temporary time period where no one would be in the office. It seems that broke everything for some reason. We have since deleted both of those that were added, but still no outside calling is being allowed.

The call trace you posted is not right at all, I can’t fathom how a from-internal call can result in those log lines unless you added bad custom dialplan to the system.

I did not change the dialplan in the system from when it was working before. It suddenly stopped working in the middle of the workday. Now, I do see my Extension Routes is not registered now where I could work with the extension routes before. I am thinking this is the culprit, but I don’t even see the option to fix it anywhere.

[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'sub-hr12format' tries to include nonexistent context 'sub-hr12format-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'app-speakextennum' tries to include nonexistent context 'app-speakextennum-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'app-echo-test-echo' tries to include nonexistent context 'app-echo-test-echo-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'app-echo-test' tries to include nonexistent context 'app-echo-test-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'app-calltrace-perform' tries to include nonexistent context 'app-calltrace-perform-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'app-calltrace' tries to include nonexistent context 'app-calltrace-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'app-hotelwakeup' tries to include nonexistent context 'app-hotelwakeup-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'sub-fmsetcid' tries to include nonexistent context 'sub-fmsetcid-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'followme-sub' tries to include nonexistent context 'followme-sub-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'followme-check' tries to include nonexistent context 'followme-check-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'fmgrps' tries to include nonexistent context 'fmgrps-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'ext-findmefollow' tries to include nonexistent context 'ext-findmefollow-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'app-fmf-toggle' tries to include nonexistent context 'app-fmf-toggle-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'ext-featurecodes' tries to include nonexistent context 'ext-featurecodes-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'ext-did-0002' tries to include nonexistent context 'ext-did-0002-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'ext-did-0001' tries to include nonexistent context 'ext-did-0001-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'app-fax' tries to include nonexistent context 'app-fax-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'ext-fax' tries to include nonexistent context 'ext-fax-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'ext-dnd-hints' tries to include nonexistent context 'ext-dnd-hints-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'app-dnd-toggle' tries to include nonexistent context 'app-dnd-toggle-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'app-dnd-on' tries to include nonexistent context 'app-dnd-on-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'app-dnd-off' tries to include nonexistent context 'app-dnd-off-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'disa-dial' tries to include nonexistent context 'disa-dial-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'app-dictate-send' tries to include nonexistent context 'app-dictate-send-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'app-dictate-record' tries to include nonexistent context 'app-dictate-record-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'c-x-3-operator-panel-pjsip-auto-answer-redirect' tries to include nonexistent context 'c-x-3-operator-panel-pjsip-auto-answer-redirect-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'c-x-3-operator-panel-pjsip-auto-answer-headers' tries to include nonexistent context 'c-x-3-operator-panel-pjsip-auto-answer-headers-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'c-x-3-operator-panel-spy' tries to include nonexistent context 'c-x-3-operator-panel-spy-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'c-x-3-operator-panel-listen-to-recording' tries to include nonexistent context 'c-x-3-operator-panel-listen-to-recording-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'c-x-3-operator-panel-listen-to-voice-mail' tries to include nonexistent context 'c-x-3-operator-panel-listen-to-voice-mail-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'c-x-3-operator-panel-park-announce-answer' tries to include nonexistent context 'c-x-3-operator-panel-park-announce-answer-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'c-x-3-operator-panel-park' tries to include nonexistent context 'c-x-3-operator-panel-park-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'c-x-3-operator-panel-confbridge' tries to include nonexistent context 'c-x-3-operator-panel-confbridge-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'c-x-3-operator-panel-meetme' tries to include nonexistent context 'c-x-3-operator-panel-meetme-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'c-x-3-operator-panel-voice-mail' tries to include nonexistent context 'c-x-3-operator-panel-voice-mail-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'c-x-3-operator-panel-hold' tries to include nonexistent context 'c-x-3-operator-panel-hold-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'cidlookup' tries to include nonexistent context 'cidlookup-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'app-callwaiting-cwon' tries to include nonexistent context 'app-callwaiting-cwon-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'app-callwaiting-cwoff' tries to include nonexistent context 'app-callwaiting-cwoff-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'macro-one-touch-record' tries to include nonexistent context 'macro-one-touch-record-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'sub-record-hh-check' tries to include nonexistent context 'sub-record-hh-check-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'sub-record-check' tries to include nonexistent context 'sub-record-check-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'sub-record-cancel' tries to include nonexistent context 'sub-record-cancel-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'ext-cf-hints' tries to include nonexistent context 'ext-cf-hints-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'app-cf-prompting-on' tries to include nonexistent context 'app-cf-prompting-on-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'app-cf-on' tries to include nonexistent context 'app-cf-on-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'app-cf-unavailable-off' tries to include nonexistent context 'app-cf-unavailable-off-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'app-cf-unavailable-on' tries to include nonexistent context 'app-cf-unavailable-on-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'app-cf-unavailable-prompt-on' tries to include nonexistent context 'app-cf-unavailable-prompt-on-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'app-cf-off-any' tries to include nonexistent context 'app-cf-off-any-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'app-cf-off' tries to include nonexistent context 'app-cf-off-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'app-cf-busy-off' tries to include nonexistent context 'app-cf-busy-off-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'app-cf-busy-off-any' tries to include nonexistent context 'app-cf-busy-off-any-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'app-cf-busy-on' tries to include nonexistent context 'app-cf-busy-on-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'app-cf-busy-prompting-on' tries to include nonexistent context 'app-cf-busy-prompting-on-custom'
[2017-11-01 11:06:21] WARNING[26641] pbx.c: Context 'app-cf-toggle' tries to include nonexistent context 'app-cf-toggle-custom'
[2017-11-01 11:06:21] VERBOSE[26641] loader.c: Reloading module 'res_pjproject.so' (PJPROJECT Log and Utility Support)
[2017-11-01 11:06:21] ERROR[26641] res_sorcery_config.c: Unable to load config file 'pjproject.conf'
[2017-11-01 11:06:21] VERBOSE[26641] loader.c: Reloading module 'res_pjsip.so' (Basic SIP resource)
[2017-11-01 11:06:21] VERBOSE[8130] config.c: Parsing '/etc/asterisk/pjsip.conf': Found
[2017-11-01 11:06:21] VERBOSE[8130] config.c: Parsing '/etc/asterisk/pjsip_custom.conf': Found
[2017-11-01 11:06:21] VERBOSE[8130] config.c: Parsing '/etc/asterisk/pjsip.transports.conf': Found
[2017-11-01 11:06:21] VERBOSE[8130] config.c: Parsing '/etc/asterisk/pjsip.transports_custom.conf': Found
[2017-11-01 11:06:21] WARNING[8130] logger: Log queue threshold (1000) exceeded. Discarding new messages.
[2017-11-01 11:06:21] WARNING[24050] logger: Logging resumed. 61 messages discarded.

This is what I came into in the logs with my latest testing. Is there something in this that explains what happened to my system?

I have the Extension Routes module registered again, and it is still not allowing outbound calls.

[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:1] Macro("SIP/7070-00000018", "user-callerid,LIMIT") in new stack
[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:1] Set("SIP/7070-00000018", "TOUCH_MONITOR=1509556273.24") in new stack
[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:2] Set("SIP/7070-00000018", "AMPUSER=7070") in new stack
[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:3] GotoIf("SIP/7070-00000018", "0?report") in new stack
[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:4] ExecIf("SIP/7070-00000018", "1?Set(REALCALLERIDNUM=7070)") in new stack
[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:5] Set("SIP/7070-00000018", "AMPUSER=7070") in new stack
[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:6] GotoIf("SIP/7070-00000018", "0?limit") in new stack
[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:7] Set("SIP/7070-00000018", "AMPUSERCIDNAME=Eric Pace") in new stack
[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:8] ExecIf("SIP/7070-00000018", "0?Set(__CIDMASQUERADING=TRUE)") in new stack
[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:9] GotoIf("SIP/7070-00000018", "0?report") in new stack
[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:10] Set("SIP/7070-00000018", "AMPUSERCID=7070") in new stack
[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:11] Set("SIP/7070-00000018", "__DIAL_OPTIONS=Ttr") in new stack
[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:12] Set("SIP/7070-00000018", "CALLERID(all)="Eric Pace" <7070>") in new stack
[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:13] GotoIf("SIP/7070-00000018", "0?limit") in new stack
[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:14] ExecIf("SIP/7070-00000018", "1?Set(GROUP(concurrency_limit)=7070)") in new stack
[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:15] ExecIf("SIP/7070-00000018", "0?Set(CHANNEL(language)=)") in new stack
[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:16] NoOp("SIP/7070-00000018", "Macro Depth is 1") in new stack
[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:17] GotoIf("SIP/7070-00000018", "1?report2:macroerror") in new stack
[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:19] GotoIf("SIP/7070-00000018", "1?continue") in new stack
[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:37] Set("SIP/7070-00000018", "CALLERID(number)=7070") in new stack
[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:38] Set("SIP/7070-00000018", "CALLERID(name)=Eric Pace") in new stack
[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:39] GotoIf("SIP/7070-00000018", "0?cnum") in new stack
[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:40] Set("SIP/7070-00000018", "CDR(cnam)=Eric Pace") in new stack
[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:41] Set("SIP/7070-00000018", "CDR(cnum)=7070") in new stack
[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:42] Set("SIP/7070-00000018", "CHANNEL(language)=en") in new stack
[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:2] Set("SIP/7070-00000018", "ROUTEUSER=7070") in new stack
[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:3] Set("SIP/7070-00000018", "ROUTEUSER=7070") in new stack
[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:4] GotoIf("SIP/7070-00000018", "1?notblind") in new stack
[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:7] GotoIf("SIP/7070-00000018", "1?restrictedroute-98c6f2c2287f4c73cea3d40ae7ec3ff2,4357572247,2:outbound-allroutes,4357572247,2") in new stack
[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Channel 'SIP/7070-00000018' sent to invalid extension: context,exten,priority=restrictedroute-98c6f2c2287f4c73cea3d40ae7ec3ff2,4357572247,2
[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:1] Goto("SIP/7070-00000018", "bad-number,s,1") in new stack
[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:1] Goto("SIP/7070-00000018", "11,1") in new stack
[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:1] ResetCDR("SIP/7070-00000018", "") in new stack
[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:2] NoCDR("SIP/7070-00000018", "") in new stack
[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:3] Progress("SIP/7070-00000018", "") in new stack
[2017-11-01 11:11:13] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:4] Wait("SIP/7070-00000018", "1") in new stack
[2017-11-01 11:11:14] VERBOSE[17404][C-0000000b] pbx.c: Executing [[email protected]:5] Playback("SIP/7070-00000018", "silence/1&cannot-complete-as-dialed&check-number-dial-again,noanswer") in new stack
[2017-11-01 11:11:14] VERBOSE[17404][C-0000000b] file.c: <SIP/7070-00000018> Playing 'silence/1.ulaw' (language 'en')
[2017-11-01 11:11:15] VERBOSE[17404][C-0000000b] file.c: <SIP/7070-00000018> Playing 'cannot-complete-as-dialed.ulaw' (language 'en')
[2017-11-01 11:11:16] VERBOSE[17404][C-0000000b] file.c: <SIP/7070-00000018> Playing 'check-number-dial-again.ulaw' (language 'en')

Apparently I have a restricted route now. I am so confused on how this all works now.

Here is a screenshot of my Dial Patterns - can anyone tell me what I have wrong here to call out? What would be giving me a restricted route when I follow the pattern in here?

Is there any chance the Firewall on the server got turned on and that you’re now on the black list?

No records showing in the Blacklist Module - is there somewhere else I need to check for this? I do have my local IP address list in the Trusted (Excluded from Firewall) Assigned Zone. The Firewall has been on since I first installed this.

I finally found the culprit. It appears there was something wrong with the link between my Time Condition and my Time Group. When I click on the Linked Item of Time Group on the Time Conditions page, it took me to a completely blank Time Group, though it was saying it was my particular Time Group in the address bar. Once I fixed the entry there following the link, everything started working. This seems to be a bug as you can have things connected and not truly connected at the same time.

1 Like

Nice to know you cgot it working, but I don’t see how time conditions and time groups affect outbound calls unless you have some funky routing.

Also, looking at the outbound routing rules, you seem to have every imaginable combination. Might just be easier to add . which takes everything. and of course your special 911 lines.

Take care

We had the exact same problem yesterday, after upgrading framework some 4 days ago.
I found the time group empty as well, but thought I had goofed around myself.
I rolled a back-up, and everything works.
But I can figure out it will happen again.
Thank you.