asterisk users - Jun 2010 - Anybody using TE410P on BT ISDN with DAHDI?

Is anybody else using the following combination:

* a TE410P card  (wct4xxp driver)
* a BT ISDN connection
* DAHDI 2.3.0.1
* Asterisk 1.6.2.9

I'm trying to configure a new box to replace a legacy system  (same
hardware;
some old version of Asterisk with Zaptel; works lovely but hopelessly 
out-of-date)  and not having much joy.  Specifically, I couldn't get it to 
see a D-channel on channel 16 of span 1.  And without a D-channel, there is 
no way I'm going to be able to get a call in or out.

This could well be because the syntax of modern /etc/dahdi/system.conf 
and /etc/asterisk/chan_dahdi.conf is slightly incompatible with the old 
zapata.conf and zaptel.conf files.

So I guess the first question should be, has anybody else managed to make this 
combination work?

(I'm new here and I may have missed some important information, so please 
ask.)

-- 
AJS

On Tue, Jun 22, 2010 at 12:26:28PM +0100, A J Stiles
wrote:
> Is anybody else using the following combination:
> 
> * a TE410P card  (wct4xxp driver)
> * a BT ISDN connection
> * DAHDI 2.3.0.1
> * Asterisk 1.6.2.9
> 
> I'm trying to configure a new box to replace a legacy system  (same
hardware;
> some old version of Asterisk with Zaptel; works lovely but hopelessly 
> out-of-date)  and not having much joy.  Specifically, I couldn't get it
to
> see a D-channel on channel 16 of span 1.  And without a D-channel, there is
> no way I'm going to be able to get a call in or out.
> 
> This could well be because the syntax of modern /etc/dahdi/system.conf 
> and /etc/asterisk/chan_dahdi.conf is slightly incompatible with the old 
> zapata.conf and zaptel.conf files.
The old ones should work just as well. Apart from 'echocanceller' lines
in system.conf. Those may prevent you from having a working echo
canceller, but nothing worse.

What do you have in those files?

What's the output of lsdahdi ?

-- 
               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 Tue, Jun 22, 2010 at 12:26:28PM +0100, A J Stiles
wrote:
> Is anybody else using the following combination:
> 
> * a TE410P card  (wct4xxp driver)
> * a BT ISDN connection
> * DAHDI 2.3.0.1
> * Asterisk 1.6.2.9
> 
> I'm trying to configure a new box to replace a legacy system  (same
hardware;
> some old version of Asterisk with Zaptel; works lovely but hopelessly 
> out-of-date)  and not having much joy.  Specifically, I couldn't get it
to
> see a D-channel on channel 16 of span 1.  And without a D-channel, there is
> no way I'm going to be able to get a call in or out.
What version of libpri? What does it mean 'no D-Channel'? What is the
output of "pri show span 1'?

-- 
               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 Tuesday 22 Jun 2010, Tzafrir Cohen wrote:
> On Tue, Jun 22, 2010 at 12:26:28PM +0100, A J Stiles wrote:
> > Is anybody else using the following combination:
> >
> > * a TE410P card  (wct4xxp driver)
> > * a BT ISDN connection
> > * DAHDI 2.3.0.1
> > * Asterisk 1.6.2.9
> >
> > I'm trying to configure a new box to replace a legacy system 
(same
> > hardware; some old version of Asterisk with Zaptel; works lovely but
> > hopelessly out-of-date)  and not having much joy.  Specifically, I
> > couldn't get it to see a D-channel on channel 16 of span 1.  And
without
> > a D-channel, there is no way I'm going to be able to get a call in
or
> > out.
>
> What version of libpri?
Libpri version is 1.4.11.1.  Sorry.
> What does it mean 'no D-Channel'?
The message I get is

WARNING[3502]: chan_dahdi.c:4160 pri_find_dchan: No D-channels available!  
Using Primary channel 16 as D-channel anyway!

which is the same message I get if I attempt to start up Asterisk with the 
ISDN disconnected.  (I transferred the cable from one machine to the other, 
so that eliminates that as a cause.  Could the card be the problem?)
> What is the  
> output of "pri show span 1'?
With the ISDN disconnected, I get:

Primary D-channel: 16
Status: Provisioned, Down, Active
Switchtype: EuroISDN
Type: CPE
Overlap Dial: 0
Logical Channel Mapping: 0
Timer and counter settings:
  N200: 3
  N202: 3
  K: 7
  T200: 1000
  T202: 10000
  T203: 10000
  T303: 4000
  T305: 30000
  T308: 4000
  T309: 6000
  T313: 4000
  T-HOLD: 4000
  T-RETRIEVE: 4000
  T-RESPONSE: 4000
Overlap Recv: No

On the working box  (connected to ISDN and calls going in and out; running 
older versions of all software),  the same command produces:

Primary D-channel: 16
Status: Provisioned, Up, Active
Switchtype: EuroISDN
Type: CPE
Window Length: 0/7
Sentrej: 0
SolicitFbit: 0
Retrans: 0
Busy: 0
Overlap Dial: 0
T200 Timer: 1000
T203 Timer: 10000
T305 Timer: 30000
T308 Timer: 4000
T313 Timer: 4000
N200 Counter: 3

-- 
AJS

On 6/22/2010 4:26 AM, A J Stiles wrote:
> Is anybody else using the following combination:
>
> * a TE410P card  (wct4xxp driver)
> * a BT ISDN connection
> * DAHDI 2.3.0.1
> * Asterisk 1.6.2.9
>
> I'm trying to configure a new box to replace a legacy system  (same
hardware;
> some old version of Asterisk with Zaptel; works lovely but hopelessly
> out-of-date)  and not having much joy.  Specifically, I couldn't get it
to
> see a D-channel on channel 16 of span 1.  And without a D-channel, there is
> no way I'm going to be able to get a call in or out.
>
> This could well be because the syntax of modern /etc/dahdi/system.conf
> and /etc/asterisk/chan_dahdi.conf is slightly incompatible with the old
> zapata.conf and zaptel.conf files.
>
> So I guess the first question should be, has anybody else managed to make
this
> combination work?
>
> (I'm new here and I may have missed some important information, so
please
> ask.)
>
>    
Hi-
I've been going through the same upgrade process recently, and had the 
same error (shown in your other message).  I had forgotten that the 
equipment I was plugged in to was CPE, so I had to change my new setting 
for that span to "NET" rather than CPE.  I notice in your old zapata 
files that you had CPE for two spans and NET for the other two, and your 
dahdi_chan setup is set up the same.  But I'm thinking perhaps during 
testing you plugged a CPE on your new setup to a CPE on the other, which 
would produce the symptoms you see.

-Scott