[Home]

Summary:ASTERISK-08604: d-channel is hardcoded to 24 and 16 for PRI T1 and E1 respectively
Reporter:Brian Degenhardt (bmdhacks)Labels:
Date Opened:2007-01-18 12:00:18.000-0600Date Closed:2011-06-07 14:08:24
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Channels/chan_zap
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:When trying to use channel 30 as the dchan for an E1/PRI link, I receive the following error in chan_zap:

[1169142779] ERROR[18377]: chan_zap.c:7681 mkintf: Channel 16 is reserved for D-channel.
[1169142779] ERROR[18377]: chan_zap.c:11725 build_channels: Unable to register channel '1-29,31'                                                                                                  

If I take channel 16 out of the b-channel group, but still use 30 as the dchan, I get the following error:

[1169142917] ERROR[18504]: chan_zap.c:10262 start_pri: D-channel 16 is not in HDLC/FCS mode.  See /etc/zaptel.conf
[1169142917] ERROR[18504]: chan_zap.c:12563 setup_zap: Unable to start D-channel on span 1                                                                                                        

****** ADDITIONAL INFORMATION ******

Here's my configs:

; /etc/zaptel.conf
span=1,0,0,ccs,hdb3
bchan=1-29,31
dchan=30

; zapata.conf
[channels]
context=default
pridialplan=national
switchtype=national
group=1
signalling=pri_cpe
channel=>1-29,31
Comments:By: Tilghman Lesher (tilghman) 2007-01-18 13:03:38.000-0600

Try using NFAS, if you want to do a weirdly positioned D-channel:

[trunkgroups]
trunkgroup => 1,30
spanmap => 1,1,1

[channels]
signalling = pri_cpe
channel => 1-29,31
By: Brian Degenhardt (bmdhacks) 2007-01-18 13:28:36.000-0600

that seems to work.
do you see any issue with using NFAS even when the dchannel is 16 or 24?
IE: why not always use [trunkgroups] to define the dchan?
By: Tilghman Lesher (tilghman) 2007-01-18 14:38:30.000-0600

Because NFAS needlessly complicates setup for 99% of all setups.
By: Tilghman Lesher (tilghman) 2007-01-18 15:00:45.000-0600

Closed by request of reporter.