Did updates now can't call outbound trunk

I did the updates to the modules this morning. Now when I try and call an outside line I get the voice message “All circuits are busy now…” The CDR log shows the following:

Timestamp Event Type Unique ID Linked ID CID Name CID Num Exten Context Channel
2018-05-31 11:16:19 CHAN_START 1527783379.14 1527783379.14 Greg Desk 202 2049754919 from-internal SIP/202-0000000a
2018-05-31 11:16:19 CHAN_START 1527783379.15 1527783379.14 s from-trunk SIP/P2569471875-0000000b
2018-05-31 11:16:19 HANGUP 1527783379.15 1527783379.14 CID:2042728654 2049754919 2049754919 from-trunk SIP/P2569471875-0000000b
2018-05-31 11:16:19 CHAN_END 1527783379.15 1527783379.14 CID:2042728654 2049754919 2049754919 from-trunk SIP/P2569471875-0000000b
2018-05-31 11:16:19 CHAN_START 1527783379.16 1527783379.14 s from-trunk-sip-voipms SIP/voipms-0000000c
2018-05-31 11:16:19 HANGUP 1527783379.16 1527783379.14 CID:2042728654 2049754919 2049754919 from-trunk-sip-voipms SIP/voipms-0000000c
2018-05-31 11:16:19 CHAN_END 1527783379.16 1527783379.14 CID:2042728654 2049754919 2049754919 from-trunk-sip-voipms SIP/voipms-0000000c
2018-05-31 11:16:22 HANGUP 1527783379.14 1527783379.14 202 h restrictedroute-7cefc053760da8a34819833b419e9785 SIP/202-0000000a
2018-05-31 11:16:22 CHAN_END 1527783379.14 1527783379.14 202 h restrictedroute-7cefc053760da8a34819833b419e9785 SIP/202-0000000a
2018-05-31 11:16:22 LINKEDID_END 1527783379.14 1527783379.14 202 h restrictedroute-7cefc053760da8a34819833b419e9785 SIP/202-0000000a

Is there an issue with restricted routes?

You need to look at /var/log/asterisk/full to troubleshoot this. CDR is just Call Details, which isn’t going to help you at all.

I tried to fix the issue, but ended up tanking the entire PBX. Decision was made to put in on VMWare, and upgrade to version 14 at the same time.

Thank you for your hints though, much appreciated!

Greg

Ive had a couple of weird things happen when upgrading to 14 like timezones resetting to UTC and the sudoers and sshd config files being reset. If you’ve already abandoned the PBX then so be it but you might check how your trunk is configured. If you’re using IP registration with voipms you might see if that trunk really is still registered, or if the register string may have gotten messed up.

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