[asterisk-dev] ZAPTEL in trunk - bug/hardcoded d-chan in zaptel?E1-T1 issue.

[Paul Cadach]

Hello,

Configuration issue - to simulate E1 you should use exactly 31 timeslot instead of 30.


WBR,
Paul.

----- Original Message ----- 
From: "Anton" <anton.vazir at gmail.com>
To: "Asterisk Developers Mailing List" <asterisk-dev at lists.digium.com>
Sent: Monday, September 25, 2006 11:16 PM
Subject: [asterisk-dev] ZAPTEL in trunk - bug/hardcoded d-chan in zaptel?E1-T1 issue.


> Hi! trying to have TDMoE in trunk, and with the correct 
> configuration for E1 getting that chan 24 is configured for 
> d-chan, like in T1 - seems some hardcode value? Bug?
> 
> zaptel
> ...
> dynamic=eth,eth0/00:40:F4:89:17:CB/0,30,1
> bchan=1-15,17-30
> dchan=16
> 
> zapata.conf
> ...
> channel => 1-15,17-30
> 
> 
> Result
> 
> ...
> ...
> ...
>     -- Registered channel 20, PRI Signalling signalling
>     -- Registered channel 21, PRI Signalling signalling
>     -- Registered channel 22, PRI Signalling signalling
>     -- Registered channel 23, PRI Signalling signalling
> [Sep 25 22:07:17] ERROR[22516]: chan_zap.c:7474 mkintf: 
> Channel 24 is reserved for D-channel.
> [Sep 25 22:07:17] ERROR[22516]: chan_zap.c:11325 
> build_channels: Unable to register channel '1-15,17-30'
> 
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
> 
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev
>