asterisk users - Feb 2009 - TDM400P Circuit/channel congestion problem

Hello,

I have an issue with Digium TDM 400 card series. When I try to make  
outgoing call (PSTN call) for example, the Zap channel could not be  
created and busy channel message appeared. Below is the full log :

[Feb  5 09:26:17] VERBOSE[3047] logger.c:     -- Executing [s at macro- 
dialout-trunk:20] Dial("SIP/213-09648720",
"ZAP/g1/08170709XXX|300|")
in new stack
[Feb  5 09:26:17] WARNING[3047] app_dial.c: Unable to create channel  
of type 'ZAP' (cause 34 - Circuit/channel congestion)
[Feb  5 09:26:17] VERBOSE[3047] logger.c:   == Everyone is busy/ 
congested at this time (1:0/1/0)
[Feb  5 09:26:17] DEBUG[3047] app_macro.c: Executed application: Dial
[Feb  5 09:26:17] VERBOSE[3047] logger.c:     -- Executing [s at macro- 
dialout-trunk:21] Goto("SIP/213-09648720", "s-CONGESTION|1")
in new
stack
[Feb  5 09:26:17] VERBOSE[3047] logger.c:     -- Goto (macro-dialout- 
trunk,s-CONGESTION,1)

The problem is fixed (outgoing call will work fine) when the PSTN  
cable attached to card are _manually_ unplugged and then plugged back  
to card. Of course, I don't want to do this job everytime when server  
restarted :-). Searching over internet, it say that I must disable  
echotraining, but the problem still persist.

System: Asterisk 1.4.22-rc5 (Elastix 1.3-2)
OS: Centos 5.2 Core 2 Duo Processor E6750  @ 2.66GHz

$ dmesg | egrep '(echo|tone|Zap|Zap|TDM|Module)'
zaptel: no version for "oslec_echo_can_traintap" found: kernel
tainted.
Zapata Telephony Interface Registered on major 196
Zaptel Version: 1.4.11
Zaptel Echo Canceller: OSLEC
Zaptap registered 'sample' char driver on major 33
Module 0: Installed -- AUTO FXO (FCC mode)
Module 1: Installed -- AUTO FXO (FCC mode)
Module 2: Installed -- AUTO FXO (FCC mode)
Module 3: Installed -- AUTO FXO (FCC mode)
Found a Wildcard TDM: Wildcard TDM400P REV I (4 modules)
Registered tone zone 0 (United States / North America)
-- Setting echo registers: 
-- Set echo registers successfully
-- Setting echo registers: 
-- Set echo registers successfully
no echo canceller being monitored - make a new call

---------
File zaptel.conf:

fxsks=1
fxsks=2
#fxsks=3
#fxsks=4

loadzone	= us
defaultzone	= us

-------
File zapata.conf:

[trunkgroups]

[channels]
context=from-zaptel
signalling=fxs_ks
rxwink=300              ; Atlas seems to use long (250ms) winks
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=no
faxdetect=incoming
echotraining=800
;rxgain=0.0
;txgain=0.0
group=0
callgroup=1
pickupgroup=1

;Uncomment these lines if you have problems with the disconection of  
your analog lines
;busydetect=yes
;busycount=3


immediate=yes

#include zapata_additional.conf
#include zapata-channels.conf

Thank you.

Rgds,
Asfihani

On Thu, Feb 05, 2009 at 02:22:12PM +0700, Asfihani
wrote:
> Hello,
> 
> I have an issue with Digium TDM 400 card series. When I try to make  
> outgoing call (PSTN call) for example, the Zap channel could not be  
> created and busy channel message appeared. Below is the full log :
> 
> [Feb  5 09:26:17] VERBOSE[3047] logger.c:     -- Executing [s at macro- 
> dialout-trunk:20] Dial("SIP/213-09648720",
"ZAP/g1/08170709XXX|300|")
> in new stack
> [Feb  5 09:26:17] WARNING[3047] app_dial.c: Unable to create channel  
> of type 'ZAP' (cause 34 - Circuit/channel congestion)
> [Feb  5 09:26:17] VERBOSE[3047] logger.c:   == Everyone is busy/ 
> congested at this time (1:0/1/0)
> [Feb  5 09:26:17] DEBUG[3047] app_macro.c: Executed application: Dial
> [Feb  5 09:26:17] VERBOSE[3047] logger.c:     -- Executing [s at macro- 
> dialout-trunk:21] Goto("SIP/213-09648720",
"s-CONGESTION|1") in new
> stack
> [Feb  5 09:26:17] VERBOSE[3047] logger.c:     -- Goto (macro-dialout- 
> trunk,s-CONGESTION,1)
> 
> The problem is fixed (outgoing call will work fine) when the PSTN  
> cable attached to card are _manually_ unplugged and then plugged back  
> to card. Of course, I don't want to do this job everytime when server  
> restarted :-). Searching over internet, it say that I must disable  
> echotraining, but the problem still persist.
Known issue of 1.4.22 . Fixed in 1.4.23 . 

If you want to fix it yourself, you can find a patch for it in our SRPM:

http://updates.xorcom.com/astribank/elastix/repo/

-- 
               Tzafrir Cohen
icq#16849755              jabber:tzafrir.cohen at xorcom.com
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir

On Feb 5, 2009, at 6:19 PM, Tzafrir Cohen wrote:
> Known issue of 1.4.22 . Fixed in 1.4.23 .
>
> If you want to fix it yourself, you can find a patch for it in our  
> SRPM:
>
> http://updates.xorcom.com/astribank/elastix/repo/
Thank you. Problem solved.

Rgds,
Asfihani