Outbound Calls Error - "All Circuits Are Busy Now, Please.."

Asterisk Asterisk Support
1

I’m in need of some assistance with our PBX system. I’m including the relevant information below, with the steps that we took and the outputs that was suggested by your Wiki. Please help us diagnose this problem.

/// SYMPTOMS

  • Outbound calls stopped working for all phones and all outbound numbers, getting an error message that “All Circuits Are Busy Now, Please Try Your Call Again Later”.
  • Inbound calls appear to be working
  • Checked PBX system and it was up and online
  • T1s are all up and ISP states the issue is on our end
  • No network changes were made and no Asterisk changes were made

/// SYSTEM INFORMATION

  • Asterisk 1.2.18
  • Zaptel 1.2.22
  • Wanpipe (Sangoma) 3.2.3.

OS – CentOS release 4.4 (Final)
Kernel - Linux pbx.assia-inc.com 2.6.9-34.0.2.ELsmp #1 SMP Fri Jul 7 19:52:49 CDT 2006 i686 i686 i386 GNU/Linux
Memory – 1,008,488 kB
Network – AT&T 3 x Bonded T1s

/// TROUBLESHOOTING

  • We’ve had some issues before but nothing in this capacity and rebooting and restarting Asterisks typically fixes this issue. In this case we’ve rebooted the system several times, restarted services as per standards and we’re still not able to dial outbound calls.
2

/// TROUBLESHOOTING

  • We’ve had some issues before but nothing in this capacity and rebooting and restarting Asterisks typically fixes this issue. In this case we’ve rebooted the system several times, restarted services as per standards and we’re still not able to dial outbound calls.

The following output is the result of this checklist to give information regarding the problem :

-the output from “wanrouter version”
-the output from “wanrouter restart” (asterisk needs to be turned off for this so it may need to be done after hours)
-the file /var/log/messages (the entire file containing a wanrouter restart)
-the output from “wanrouter hwprobe verbose”
-the output from “wanrouter status”
-the file(s) /etc/wanpipe/wanpipeX.conf (where X is the wanpipe number)
-the file /etc/zaptel.conf (Zaptel/Asterisk ONLY)
-the file(s) /etc/asterisk/zapata*.conf (Zaptel/Asterisk ONLY)
-the file /etc/dahdi/system.conf (Dahdi/Asterisk ONLY)
-the file(s) /etc/asterisk/chan_dahdi.conf (Dahdi/Asterisk ONLY)
-the output from “ifconfig”, (re run a couple of times with a second or so delay in between each run)
-the output from “cat /proc/interrupts” (re run a couple of times with a second or so delay in between each run)
-the output from “wanpipemon -i wXg1 -c Ta” (where X is the interface number 1,2,3,etc)
-log all output from the Asterisk console to a file:
=>open up the file /etc/asterisk/logger.conf
=>look for the line “messages=> notice,warning …” and add this one line below “sangoma => notice,warning,error,event,verbose”
=>save the file and restart Asterisk
-increase the verbosity of Asterisk using “set verbose 10”
-the output from “pri show span X” from the Asterisk console, where X is the span having problems (i.e. 1,2,3,4,etc)
-run “pri intense debug span X” from the Asterisk console so that Asterisk captures debug information, where X is the span having problems (i.e. 1,2,3,4,etc)
-make a call out to reproduce the problem or leave the system running until it occurs
-turn off Asterisk logging to the file /var/log/asterisk/sangoma by:
=>open up the file /etc/asterisk/logger.conf
=>look for the line “sangoma => notice,warning,error,event,verbose”, and either remove it or uncomment it
=>save the file and restart Asterisk
-send me the file /var/log/asterisk/sangoma
To turn of the debugging in Asterisk run “pri no debug span X”, where X is the span in question

[root@pbx wanpipe]# wanrouter version

WANPIPE Release: 3.2.3

[root@pbx wanpipe]# /etc/init.d/asterisk stop
Shutting down asterisk: [ OK ]
[root@pbx wanpipe]# wanrouter restart

STOPPING ASTERISK

STOPPING FOP SERVER
FOP Server Stopped
Shutting down wanpipe1 interface: w1g1
Shutting down device: wanpipe1
No devices running, Unloading Modules

Starting WAN Router…
Loading WAN drivers: wanpipe done.
Starting up device: wanpipe1
–> Waiting for ec device /dev/wanec…
–> Waiting for ec device /dev/wanec…
–> Waiting for ec device /dev/wanec…
–> Waiting for ec device /dev/wanec…
–> Waiting for ec device /dev/wanec…
–> Waiting for ec device /dev/wanec…
–> Loading ec image OCT6116-64S.ima…
Configuring interfaces: w1g1
done.

3

[root@pbx ~]# cat /etc/wanpipe/wanpipe1.conf
#================================================

WANPIPE1 Configuration File

#================================================

Date: Wed Dec 6 20:29:03 UTC 2006

Note: This file was generated automatically

by /usr/local/sbin/setup-sangoma program.

If you want to edit this file, it is

recommended that you use wancfg program

to do so.

#================================================

Sangoma Technologies Inc.

#================================================

[devices]
wanpipe1 = WAN_AFT_TE1, Comment

[interfaces]
w1g1 = wanpipe1, , TDM_VOICE, Comment

[wanpipe1]
CARD_TYPE = AFT
S514CPU = A
CommPort = PRI
AUTO_PCISLOT = NO
PCISLOT = 0
PCIBUS = 6
FE_MEDIA = T1
FE_LCODE = B8ZS
FE_FRAME = ESF
FE_LINE = 1
TE_CLOCK = NORMAL
TE_REF_CLOCK = 0

TE_HIGHIMPEDANCE = NO
LBO = 0DB
FE_TXTRISTATE = NO
MTU = 1500
UDPPORT = 9000
TTL = 255
IGNORE_FRONT_END = NO
TDMV_SPAN = 1
TDMV_DCHAN = 0
TDMV_HW_DTMF = NO

[w1g1]
ACTIVE_CH = ALL
TDMV_ECHO_OFF = NO
TDMV_HWEC = YES

[root@pbx ~]# cat /etc/zaptel.conf

Autogenerated by /usr/local/sbin/genzaptelconf – do not hand edit

Zaptel Configuration File

This file is parsed by the Zaptel Configurator, ztcfg

It must be in the module loading order

Autogenerated by /usr/local/sbin/sangoma/setup-sangoma – do not hand edit

Zaptel Channels Configurations (zaptel.conf)

loadzone=us
defaultzone=us

#Sangoma A101 port 1 [slot:0 bus:6 span:1]
span=1,1,0,esf,b8zs
bchan=1-14
dchan=24

Span 2: WCTDM/0 “Wildcard TDM400P REV I Board 1”

fxoks=25
fxoks=26
fxoks=27
fxoks=28

Span 3: ZTDUMMY/1 “ZTDUMMY/1 1”

Global data

loadzone = us
defaultzone = us

[root@pbx ~]# cat /etc/zaptel.conf

Autogenerated by /usr/local/sbin/genzaptelconf – do not hand edit

Zaptel Configuration File

This file is parsed by the Zaptel Configurator, ztcfg

It must be in the module loading order

Autogenerated by /usr/local/sbin/sangoma/setup-sangoma – do not hand edit

Zaptel Channels Configurations (zaptel.conf)

loadzone=us
defaultzone=us

#Sangoma A101 port 1 [slot:0 bus:6 span:1]
span=1,1,0,esf,b8zs
bchan=1-14
dchan=24

Span 2: WCTDM/0 “Wildcard TDM400P REV I Board 1”

fxoks=25
fxoks=26
fxoks=27
fxoks=28

Span 3: ZTDUMMY/1 “ZTDUMMY/1 1”

Global data

loadzone = us
defaultzone = us

4

Okay this was bizarre. After a long call with our ISP, AT&T they were telling me that the call was terminating with a quotation mark in the Caller ID section. In our Caller ID section we had the following

" COMPANY <123-123-1234>"

This was the same way that it has always been and was configured per documentation. I tested this and removed the quotations and outbound calls started to work. This must have been something on the ISP side where this is a new dependency.