[asterisk-bugs] [Asterisk 0016568]: Always get network congestion on second group using .call file

Asterisk Bug Tracker noreply at bugs.digium.com
Thu Jan 7 15:30:01 CST 2010


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16568 
====================================================================== 
Reported By:                western55
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16568
Category:                   Channels/chan_dahdi
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.1.12 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-01-07 15:24 CST
Last Modified:              2010-01-07 15:30 CST
====================================================================== 
Summary:                    Always get network congestion on second group using
.call file
Description: 
Using NFAS I have set up two groups. The first group appears to process
calls fine but always get Call failed to go through, reason (8) Congestion
(circuits busy) when it trys to go out 2nd group. I believe this may be a
bug in the way Asterisk handles multiple groups with .call files...

**chan_dahdi**
[trunkgroups]
trunkgroup => 1,24
trunkgroup => 2,120

spanmap => 1,1,0
spanmap => 2,1,1
spanmap => 3,1,2
spanmap => 4,1,3
spanmap => 5,2,4
spanmap => 6,2,5
spanmap => 7,2,6
spanmap => 8,2,7

[channels]
context=default
usecallerid=yes
hidecallerid=no
callwaiting=no
usecallingpres=yes
callwaitingcallerid=no
threewaycalling=no
transfer=no
canpark=no
cancallforward=no
callreturn=no
echocancel=no
echocancelwhenbridged=no
relaxdtmf=yes
rxgain=0.0
txgain=0.0
;group=1
callgroup=1
pickupgroup=1
immediate=no

switchtype=national
context=default
group=1
echocancel=no
signalling=pri_cpe

channel =>1-23

switchtype=national
context=default
group=1
echocancel=no
signalling=pri_cpe
channel =>25-48

switchtype=national
context=default
group=1
echocancel=no
signalling=pri_cpe
channel =>49-72

switchtype=national
context=default
group=1
echocancel=no
signalling=pri_cpe
                                                             
switchtype=national
context=default
group=2
echocancel=no
signalling=pri_cpe
channel =>97-119

switchtype=national
context=default
group=2
echocancel=no
signalling=pri_cpe
channel =>121-144

switchtype=national
context=default
group=2
echocancel=no
signalling=pri_cpe
channel =>145-168

switchtype=national
context=default
group=2
echocancel=no
signalling=pri_cpe
channel =>169-192

====================================================================== 

---------------------------------------------------------------------- 
 (0116278) western55 (reporter) - 2010-01-07 15:30
 https://issues.asterisk.org/view.php?id=16568#c116278 
---------------------------------------------------------------------- 
Nevermind - please close this issue. It looks like my provider may have
been at fault... Thanks.. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-01-07 15:30 western55      Note Added: 0116278                          
======================================================================




More information about the asterisk-bugs mailing list